Cookie policy.
What these technologies are
A cookie is a small text file a site asks your browser to keep and send back on later visits. Sites also use local storage, a similar store with no expiry, and scripts that read details about your device. UK law, the Privacy and Electronic Communications Regulations, treats all of these the same way: apart from what is strictly necessary for the site to work and a few narrow exceptions, we need your permission before using them. We ask before anything optional runs, analytics included.
How we ask, and how to change your answer
On your first visit a band at the bottom of the page offers three routes. “Accept all” switches on both optional categories. “Necessary only” leaves them off. “Cookie settings” lets you pick one at a time. Closing the page without choosing counts as no. We remember your answer for 6 months, then ask again, and we ask again sooner if the list below changes.
You can reopen the settings from the link in the footer of every page, or here:
If you switch a category off, we stop loading its scripts from the next page you open and delete the cookies and stored values listed below that we know about. A script that has already loaded on the page you are on keeps running until you reload. Your browser can also block or delete cookies for any site; this one works without any of the optional ones.
Necessary
These are needed for the site to work and to remember your cookie choices. They do not track you across sites and they are not used for marketing. Our host, Vercel, also keeps short-lived server logs (IP address, browser, time of request) to serve pages and defend against abuse; that happens server-side and stores nothing on your device.
| Name | Provider | Type | Purpose | Duration |
|---|---|---|---|---|
orvixo_consent | Orvixo | Cookie | Records which categories you allowed, when, and the version of this policy you answered. | 6 months |
orvixo_consent | Orvixo | Local storage | A copy of the same choice so the banner does not reappear. | Until you clear site data or change your choice |
Analytics
Vercel Web Analytics tells us which pages are read, where visitors come from (referrer and country), and what device, browser and operating system they use. Vercel Speed Insights measures how fast pages load (Core Web Vitals). Neither sets a cookie or writes to your device: Vercel counts a visit with a hash of the incoming request that is discarded after a day, so you cannot be recognised across days or sites. We still ask first: UK law now allows some aggregate statistics without consent, but the EU rules our European visitors rely on do not, and one clear rule is better than two.
| Name | Provider | Type | Purpose | Duration |
|---|---|---|---|---|
| — | Vercel Web Analytics | No storage | Page views, referrer, country, device and browser type. A visit is identified with a server-side hash of the request, not a stored identifier. | Hash discarded after 24 hours |
| — | Vercel Speed Insights | No storage | Core Web Vitals (loading, interactivity and layout stability) per page, with device and browser type. | Not applicable |
Visitor identification
When allowed, we load a script from Apollo.io that records the pages you view, your IP address and device details, stores an identifier in your browser, and matches the visit against Apollo's database of companies and business contacts. For visitors outside the United States Apollo identifies the company only; for US visitors it may identify the person. This lets our founders see which organisations are interested and follow up. Apollo's script also loads a component from LiveIntent, an identity-resolution provider, which can set the cookies listed below. Both companies are in the US; see the international transfers section of the privacy policy. If you withdraw this permission we stop loading the script and delete the values listed here on the next page load.
| Name | Provider | Type | Purpose | Duration |
|---|---|---|---|---|
apolloAnonId | Apollo.io | Local storage | Random identifier for this browser so repeat visits can be linked together. | Until cleared (no expiry) |
6a30fd2399d2ff001c3daa73_canTrack | Apollo.io | Local storage | Caches Apollo's decision on whether this visitor may be tracked. | 24 hours |
6a30fd2399d2ff001c3daa73_eventQueue | Apollo.io | Local storage | Holds page-view events until they have been sent to Apollo. | Until sent |
liveIntentData | Apollo.io | Local storage | Caches identity data returned by LiveIntent. | 30 hours |
_lc2_fpi | LiveIntent (loaded by Apollo) | Cookie | First-party device identifier for LiveIntent's identity resolution, which Apollo uses to match visitors to business contacts. | Up to 2 years (LiveIntent's default)To be confirmed |
_li_duid | LiveIntent (loaded by Apollo) | Cookie | Device identifier used by LiveIntent. | Up to 2 years (LiveIntent's default)To be confirmed |
_li_dcdm_c | LiveIntent (loaded by Apollo) | Cookie | Records the domain LiveIntent's cookies are set on. | Up to 2 years (LiveIntent's default)To be confirmed |
_li_ss | LiveIntent (loaded by Apollo) | Cookie | Stores LiveIntent identity data for the session. | Up to 2 years (LiveIntent's default)To be confirmed |
lidid | LiveIntent (loaded by Apollo) | Cookie | LiveIntent identifier. | Up to 2 years (LiveIntent's default)To be confirmed |
Rows marked “to be confirmed” name cookies we found in the vendor’s code but whose lifetime in the build we load we have not yet verified. We will update this table when we have.
Questions
How we handle personal data more generally, including what Apollo matches your visit against and your rights over it, is in the privacy policy. Anything else: write to hello@orvixo.ai.