Client Code (Web SDK) - Security & Reliability
All ForeSee client code is hosted in our high-availability CDN, backed by Fastly, whose customers include the likes of Twitter, Guardian UK, GitHub, AddThis, Wikia, Shazam, Wanelo, and Yammer. By partnering with a recognized industry-leader, we’re able to provide microsecond time-to-first-byte times.
In addition to being on a robust network, we’ve also adopted an architecture that minimizes the potential impact of an outage of our resources on your website. ForeSee gateway code is inserted asynchronously onto the page, meaning that even if the origin server was unreachable or slow, this would have zero impact on page performance. In other words, even in the unlikely worst-case scenario where ForeSee content is temporarily unreachable, this has virtually no impact on your website other than not providing the ForeSee features during the outage.
ForeSee uses what are called third-party cookies to keep track of users across their experience. Cookies are just text files that reside in the browser of the visitor to the website. The difference between first and third party cookies depends on who has the right to access the information inside the cookie. A first-party cookie can only be read by the owner of the site who created it. A third-party cookie can only be read by the external vendor who has a presence on the site. Since ForeSee is an external vendor, our cookies are defined as third-party.
In situations where clients cannot allow third-party cookies on their sites, they do have the option of hosting the code themselves, and using only 1st party cookies. Ask your ForeSee representative to learn more about this option.
Use of JSON
For pages on your site that use SSL encryption, ForeSee provides end-to-end 128-bit encryption of all hosted resources using TLS 1.2.
Clients may call (877) 224-9282 during normal business hours (Eastern time) or email support@ForeSee.com.