@ever-co/legal 0.1.0 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/content/aup/ever-corporate/en.html +2 -2
- package/dist/content/aup/ever-corporate/en.json +3 -3
- package/dist/content/aup/ever-demand/en.html +2 -2
- package/dist/content/aup/ever-demand/en.json +3 -3
- package/dist/content/aup/ever-rec/en.html +2 -2
- package/dist/content/aup/ever-rec/en.json +3 -3
- package/dist/content/aup/ever-teams/en.html +2 -2
- package/dist/content/aup/ever-teams/en.json +3 -3
- package/dist/content/aup/ever-works/en.html +2 -2
- package/dist/content/aup/ever-works/en.json +3 -3
- package/dist/content/aup/everiq/en.html +2 -2
- package/dist/content/aup/everiq/en.json +3 -3
- package/dist/content/aup/gauzy/en.html +2 -2
- package/dist/content/aup/gauzy/en.json +3 -3
- package/dist/content/aup/githands/en.html +2 -2
- package/dist/content/aup/githands/en.json +3 -3
- package/dist/content/aup/hust/en.html +2 -2
- package/dist/content/aup/hust/en.json +3 -3
- package/dist/content/aup/traduora/en.html +2 -2
- package/dist/content/aup/traduora/en.json +3 -3
- package/dist/content/cookies/ever-corporate/en.html +16 -1
- package/dist/content/cookies/ever-corporate/en.json +3 -3
- package/dist/content/cookies/ever-demand/en.html +18 -3
- package/dist/content/cookies/ever-demand/en.json +3 -3
- package/dist/content/cookies/ever-rec/en.html +18 -3
- package/dist/content/cookies/ever-rec/en.json +3 -3
- package/dist/content/cookies/ever-teams/en.html +16 -1
- package/dist/content/cookies/ever-teams/en.json +3 -3
- package/dist/content/cookies/ever-tech/en.html +18 -3
- package/dist/content/cookies/ever-tech/en.json +3 -3
- package/dist/content/cookies/ever-works/en.html +16 -1
- package/dist/content/cookies/ever-works/en.json +3 -3
- package/dist/content/cookies/everiq/en.html +16 -1
- package/dist/content/cookies/everiq/en.json +3 -3
- package/dist/content/cookies/gauzy/en.html +16 -1
- package/dist/content/cookies/gauzy/en.json +3 -3
- package/dist/content/cookies/githands/en.html +16 -1
- package/dist/content/cookies/githands/en.json +3 -3
- package/dist/content/cookies/hust/en.html +16 -1
- package/dist/content/cookies/hust/en.json +3 -3
- package/dist/content/cookies/traduora/en.html +16 -1
- package/dist/content/cookies/traduora/en.json +3 -3
- package/dist/content/dpa/ever-demand/en.html +2 -2
- package/dist/content/dpa/ever-demand/en.json +3 -3
- package/dist/content/dpa/ever-rec/en.html +2 -2
- package/dist/content/dpa/ever-rec/en.json +3 -3
- package/dist/content/dpa/ever-teams/en.html +2 -2
- package/dist/content/dpa/ever-teams/en.json +3 -3
- package/dist/content/dpa/ever-works/en.html +2 -2
- package/dist/content/dpa/ever-works/en.json +3 -3
- package/dist/content/dpa/gauzy/en.html +2 -2
- package/dist/content/dpa/gauzy/en.json +3 -3
- package/dist/content/dpa/githands/en.html +2 -2
- package/dist/content/dpa/githands/en.json +3 -3
- package/dist/content/dpa/hust/en.html +2 -2
- package/dist/content/dpa/hust/en.json +3 -3
- package/dist/content/privacy/ever-corporate/en.html +3 -9
- package/dist/content/privacy/ever-corporate/en.json +3 -3
- package/dist/content/privacy/ever-demand/en.html +3 -3
- package/dist/content/privacy/ever-demand/en.json +3 -3
- package/dist/content/privacy/ever-rec/en.html +3 -9
- package/dist/content/privacy/ever-rec/en.json +3 -3
- package/dist/content/privacy/ever-teams/en.html +3 -3
- package/dist/content/privacy/ever-teams/en.json +3 -3
- package/dist/content/privacy/ever-tech/en.html +3 -9
- package/dist/content/privacy/ever-tech/en.json +3 -3
- package/dist/content/privacy/ever-works/en.html +3 -3
- package/dist/content/privacy/ever-works/en.json +3 -3
- package/dist/content/privacy/everiq/en.html +3 -3
- package/dist/content/privacy/everiq/en.json +3 -3
- package/dist/content/privacy/gauzy/en.html +3 -3
- package/dist/content/privacy/gauzy/en.json +3 -3
- package/dist/content/privacy/githands/en.html +3 -3
- package/dist/content/privacy/githands/en.json +3 -3
- package/dist/content/privacy/hust/en.html +3 -3
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +3 -3
- package/dist/content/privacy/traduora/en.json +3 -3
- package/dist/content/refund/ever-works/en.html +2 -2
- package/dist/content/refund/ever-works/en.json +3 -3
- package/dist/content/refund/gauzy/en.html +2 -2
- package/dist/content/refund/gauzy/en.json +3 -3
- package/dist/content/refund/githands/en.html +2 -2
- package/dist/content/refund/githands/en.json +3 -3
- package/dist/content/refund/hust/en.html +2 -2
- package/dist/content/refund/hust/en.json +3 -3
- package/dist/content/security/ever-demand/en.html +1 -1
- package/dist/content/security/ever-demand/en.json +3 -3
- package/dist/content/security/ever-rec/en.html +1 -1
- package/dist/content/security/ever-rec/en.json +3 -3
- package/dist/content/security/ever-teams/en.html +1 -1
- package/dist/content/security/ever-teams/en.json +3 -3
- package/dist/content/security/ever-works/en.html +1 -1
- package/dist/content/security/ever-works/en.json +3 -3
- package/dist/content/security/gauzy/en.html +1 -1
- package/dist/content/security/gauzy/en.json +3 -3
- package/dist/content/security/githands/en.html +1 -1
- package/dist/content/security/githands/en.json +3 -3
- package/dist/content/security/hust/en.html +1 -1
- package/dist/content/security/hust/en.json +3 -3
- package/dist/content/subprocessors/ever-corporate/en.html +1 -7
- package/dist/content/subprocessors/ever-corporate/en.json +3 -3
- package/dist/content/subprocessors/ever-demand/en.html +1 -1
- package/dist/content/subprocessors/ever-demand/en.json +3 -3
- package/dist/content/subprocessors/ever-rec/en.html +1 -7
- package/dist/content/subprocessors/ever-rec/en.json +3 -3
- package/dist/content/subprocessors/ever-teams/en.html +1 -1
- package/dist/content/subprocessors/ever-teams/en.json +3 -3
- package/dist/content/subprocessors/ever-tech/en.html +1 -7
- package/dist/content/subprocessors/ever-tech/en.json +3 -3
- package/dist/content/subprocessors/ever-works/en.html +1 -1
- package/dist/content/subprocessors/ever-works/en.json +3 -3
- package/dist/content/subprocessors/everiq/en.html +1 -1
- package/dist/content/subprocessors/everiq/en.json +3 -3
- package/dist/content/subprocessors/gauzy/en.html +1 -1
- package/dist/content/subprocessors/gauzy/en.json +3 -3
- package/dist/content/subprocessors/githands/en.html +1 -1
- package/dist/content/subprocessors/githands/en.json +3 -3
- package/dist/content/subprocessors/hust/en.html +1 -1
- package/dist/content/subprocessors/hust/en.json +3 -3
- package/dist/content/subprocessors/traduora/en.html +1 -1
- package/dist/content/subprocessors/traduora/en.json +3 -3
- package/dist/content/tos/ever-corporate/en.html +3 -3
- package/dist/content/tos/ever-corporate/en.json +3 -3
- package/dist/content/tos/ever-demand/en.html +3 -3
- package/dist/content/tos/ever-demand/en.json +3 -3
- package/dist/content/tos/ever-rec/en.html +3 -3
- package/dist/content/tos/ever-rec/en.json +3 -3
- package/dist/content/tos/ever-teams/en.html +3 -3
- package/dist/content/tos/ever-teams/en.json +3 -3
- package/dist/content/tos/ever-tech/en.html +3 -3
- package/dist/content/tos/ever-tech/en.json +3 -3
- package/dist/content/tos/ever-works/en.html +3 -3
- package/dist/content/tos/ever-works/en.json +3 -3
- package/dist/content/tos/everiq/en.html +3 -3
- package/dist/content/tos/everiq/en.json +3 -3
- package/dist/content/tos/gauzy/en.html +3 -3
- package/dist/content/tos/gauzy/en.json +3 -3
- package/dist/content/tos/githands/en.html +3 -3
- package/dist/content/tos/githands/en.json +3 -3
- package/dist/content/tos/hust/en.html +3 -3
- package/dist/content/tos/hust/en.json +3 -3
- package/dist/content/tos/traduora/en.html +3 -3
- package/dist/content/tos/traduora/en.json +3 -3
- package/dist/index.json +144 -144
- package/package.json +50 -50
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "0540a9bc4b2053bba40038ae5419dccd64cc88b598de4c5e33b4869716c433f2",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/cookies/010-scope",
|
|
@@ -189,5 +189,5 @@
|
|
|
189
189
|
}
|
|
190
190
|
],
|
|
191
191
|
"path": "content/cookies/ever-corporate/en.html",
|
|
192
|
-
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[ever.co](https://ever.co) and in the Ever website — the public website, the documentation,\nthe signed-in application, and any desktop or mobile application we publish for it. The product-specific\nsection below lists what is actually in use on each of those surfaces.\n\nIt sits alongside our [Privacy Policy](https://ever.co/privacy). The two documents answer different\nquestions, and it is worth knowing which one you are reading:\n\n- **This policy is about your device.** What we store on it, what we read back from it, why, and how you\n control that.\n- **The [Privacy Policy](https://ever.co/privacy) is about the information itself.** What we do with personal\n data once we hold it, the lawful basis for each purpose, who receives it, how long we keep it, and the\n rights you can exercise over it.\n\nWhere something described here involves personal data, the Privacy Policy governs that processing.\n**Nothing in this policy narrows the rights that document gives you.**\n\n### What this policy does not cover\n\n**Other people's sites and services.** Our pages link to third-party sites, and our Service connects to\nthird-party tools when you ask it to. Once you are on someone else's site, their cookie notice applies, not\nours. We have no control over what they store on your device.\n\n**Your own workspace, your own site, your own people.** Where you use the Service as a customer to run\nsomething of your own — a workspace for your organisation, or a site we provision for you — the pages you\npublish and the people you invite are yours. **This policy is not your cookie notice to your own visitors or\npersonnel, and our banner is not your consent mechanism.** Providing those is your responsibility, on your\nown domain, under your own control.\n\n**A copy you run yourself.** Where the software behind the Service is published as open source and you run\nyour own deployment, this policy describes the service *we* operate — not yours. You choose what your\ndeployment loads and what it stores on your users' devices, and only you can describe it to them.\n\n## Cookies and the other technologies that behave like them\n\nA **cookie** is a small text file that a website asks your browser to keep and hands back to a server on\nlater requests. It is the oldest way of doing this, and the best known — but it is only one of several, and\nthe rules that matter here do not turn on which one is used.\n\n**The law we work to attaches to storing information on your device or reading information back from it,\nwhatever the mechanism.** So wherever this policy says \"cookies\", read it as covering all of the following.\n\n### The technologies\n\n- **Cookies** — as above. Set by the site you are visiting, or by another provider whose code runs on the\n page.\n- **Local storage and session storage** — key-value storage inside your browser. Larger than a cookie, not\n sent automatically with every request, and it can hold exactly the same kind of identifier.\n- **IndexedDB and the browser cache** — structured storage and cached files. Ordinarily used to make pages\n load faster and to let parts of the Service work offline, but capable of holding an identifier too.\n- **Pixels, beacons and tags** — a tiny image or a short script whose only job is to load. The act of\n loading it tells the provider that a page was opened, or an email read, along with your IP address and\n browser details. A pixel often stores nothing at all and still reports on you.\n- **Tracking parameters in links** — identifiers added to a URL so that a click can be attributed to the\n campaign or message that produced it.\n- **SDK identifiers in desktop and mobile applications** — an installed application has no cookie jar. It\n stores identifiers in its own application storage instead, and may use identifiers the operating system\n provides: an advertising identifier, an installation identifier, or a push notification token.\n- **Device and network characteristics** — your IP address, screen size, language, time zone, fonts and\n browser version. Individually unremarkable; combined, they can form a **fingerprint** that recognises a\n device without storing anything on it.\n\n### First-party and third-party\n\n**First-party** means we set it, on our own domain, and it goes to our servers.\n\n**Third-party** means it belongs to another company whose code we have chosen to run on the page — an\nanalytics provider, an embedded video player, a bot-protection service. Their technology reports to them,\nnot to us, and they decide what it does. Note the awkward part plainly: **a third-party resource embedded in\nour page discloses your IP address, your browser and the page you were on to that provider, even when it\nstores nothing on your device at all.** Loading it is the disclosure.\n\nSome third-party technologies are deliberately set up to look first-party — served from a subdomain of ours,\nor routed through our own servers. Where we do that, we say so in the table below rather than letting the\nappearance stand.\n\n### Session and persistent\n\n**Session** items are discarded when you close the browser or the application. They are typically what keeps\nyou signed in and moving through a single visit.\n\n**Persistent** items survive until they expire or you delete them, which is what lets us recognise a\nreturning visitor, remember your preferences, or remember that you refused something. Each entry in the\ntable below states how long it lasts.\n\n## Why we use them\n\nThere are six reasons, and each one maps to one of the categories in the next section. We have written the\ncategory next to each so you can see immediately which ones you control.\n\n- **To sign you in and keep you signed in.** Your session has to be attached to the right account, the right\n workspace and the right organisation as you move between pages, and it has to be protected against being\n replayed or forged by someone else. → *strictly necessary*\n- **To keep the Service secure.** Telling a person apart from an abusive script, protecting forms against\n automated submission, enforcing rate limits, and detecting fraudulent sign-ups and payments.\n → *strictly necessary*\n- **To make the Service work at all.** Routing your request to a healthy server, keeping you on the same one\n where a feature requires it, balancing load, and serving the right version of the application.\n → *strictly necessary*\n- **To remember what you decided about cookies.** Your choice has to be stored somewhere, or we would have\n to ask you on every page. → *strictly necessary*\n- **To remember your preferences.** Language, time zone, theme, layout, a panel you collapsed, a message you\n dismissed, and whether you want the support widget open. → *functional*\n- **To understand how the Service is used.** Which pages and features people actually use, which paths fail,\n and where things are slow — so that we improve the right things rather than the ones we happen to notice.\n → *analytics*\n- **To measure our marketing.** Whether a campaign reached anyone, which content leads to sign-ups, and\n which organisations show interest in the product. → *marketing*\n\nTwo things follow from that list, and we would rather state them than leave them implied.\n\n**Only the first four are needed for the Service to function.** Everything in the last three groups is\noptional. If you refuse all of it, every feature you are entitled to still works, at the same price.\n\n**Where we can achieve a purpose without storing anything on your device, we do.** That is the whole reason\nour own analytics is built the way it is — see the section on analytics without consent below.\n\n## The four categories we use\n\nEvery entry in the table below belongs to exactly one of these four categories. The banner and the\npreference centre use the same four names, so what you agree to and what this policy describes are the same\nthing.\n\n### 1. Strictly necessary — no consent, because the Service cannot run without them\n\nThese are the ones we set because you asked for a service that cannot be delivered otherwise. They are not\noptional, they are not used for analytics or marketing, and there is no switch for them in the preference\ncentre. If you block them at the browser level, parts of the Service will stop working.\n\n- **Session and authentication** — signing you in, keeping you signed in, refreshing your session, and\n binding it to the correct account, workspace and organisation.\n- **Security** — protection against cross-site request forgery, detection of abusive automated traffic, rate\n limiting, and fraud prevention on sign-up and payment.\n- **Load balancing and routing** — sending your request to a healthy server and keeping you there where a\n feature needs it.\n- **Your consent choice** — storing what you decided, so that we can honour it and stop asking.\n\nError and crash diagnostics are **not** in this category by default. Where we use a diagnostics tool that\nrecords more than a technical error — a reconstruction of what was on your screen, for example — it is\nlisted under analytics and it waits for your consent.\n\n#### reCAPTCHA is in this category, and here is our reasoning\n\nWe use Google reCAPTCHA — and on some surfaces an alternative provider, named in the table below — to stop\nautomated abuse of forms such as sign-up, password reset and contact. **We treat it as strictly necessary,\nwhich means it loads without asking you first.**\n\nThe reason is that it protects the specific form you are trying to use. You cannot meaningfully ask for the\nform and refuse the protection on it: without it, those endpoints are abused within hours, which is a\nsecurity failure that harms you as much as us.\n\nWhat that means in practice, stated plainly:\n\n- It collects device and behaviour signals from your browser — mouse and touch movement, timing, browser and\n device characteristics, and your IP address — and **sends them to Google, which acts as its own controller\n for that data under its own privacy notice.**\n- We load it only on pages carrying a protected form. It is not present across the whole site.\n- Where an equivalent provider is available on a surface, we prefer the one that collects less.\n\n**Not every data protection authority accepts that a bot-protection service belongs in the strictly\nnecessary category.** We think it does, for the reason above, and we would rather publish the reasoning and\nlet you judge it than bury the tool in a list. If you would prefer not to submit a form protected this way,\nwrite to privacy@ever.co and we will take it from you another way.\n\n### 2. Functional and preferences — consent required\n\nThese remember choices you have made so that the Service behaves the way you left it: language, time zone,\ntheme, layout, dismissed messages, and support or chat widgets where we offer them.\n\n**Refusing this category costs you convenience, not access.** Everything still works; it simply forgets your\npreferences between visits and you set them again.\n\n### 3. Analytics — consent required\n\nThese tell us how the Service is used: which pages and features are used, which paths people abandon, what\nis slow, and what fails. Depending on the surface this may include a provider's own persistent identifier\nand, where the table says so, a masked reconstruction of a session.\n\nThird-party analytics tools are **off until you turn them on**, and nothing in this category loads before you\nchoose.\n\nThere is one deliberate exception, and it is the subject of the next section: **our own analytics, running on\nour own servers, is designed to operate without a consent requirement** — cookieless, with no persistent\nidentifier and aggregate reporting only. The next section sets out exactly what that involves and the\nconditions it depends on.\n\n### 4. Marketing — consent required\n\nThese measure whether our marketing works and help us understand who is interested in the product:\nattribution of a sign-up to the campaign that produced it, and business-audience identification tools.\n\nOne of these deserves a plain sentence rather than a euphemism. **Visitor identification tools resolve a\nvisitor's IP address to the organisation it belongs to, so that we can see which companies have looked at\nthe product.** They do not tell us your name, but most people do not expect a website to work out their\nemployer, so we would rather say it here than let you find it in a table. It is off unless you consent.\n\n### No cookie walls, ever\n\n**We do not use cookie walls, and we never make access conditional on consenting to non-essential cookies.**\n\nYou can refuse everything except the strictly necessary category and the whole of the Service remains\navailable to you — the same features, the same content, the same price. We do not offer a \"consent or pay\"\nalternative. We do not degrade the experience, hide content, or nag you on every page because you said no.\nRefusing is a decision we record and respect, not a negotiating position.\n\n## Annex: Ever\n\n### The surfaces this covers\n\nTwo, and they are genuinely different: the website at [ever.co](https://ever.co) and the\ndocumentation published alongside it. **There is no signed-in application here** — no account can be\ncreated on this site, so there are no session or authentication cookies, and every page is the same page\nfor everyone.\n\n### On the website\n\n| What runs | What it does | Category | Consent |\n|---|---|---|---|\n| Our content delivery and security provider | Routes your request to the nearest edge, filters hostile traffic, and sets a short-lived cookie that tells a browser apart from a bot | Strictly necessary | Not required |\n| Our consent management provider | Presents the banner and the preference centre, stores what you chose, and holds the record of it | Strictly necessary | Not required |\n| Google reCAPTCHA | Bot protection on the enquiry, careers, notification and newsletter forms. Loads only on a page carrying one of them | Strictly necessary | Not required — for the reasons given above |\n| Google Tag Manager | A container rather than a tag: it loads the tools below, and further tags can be added through it without a change to the site's code | Analytics | Required |\n| Google Analytics | Traffic measurement — pages viewed, referrers, devices, coarse location from the IP address | Analytics | Required |\n| PostHog | Product and site analytics, with its own identifier stored on your device, sent to the provider's United States cloud | Analytics | Required |\n| Sentry | Error and performance reporting for the pages themselves | Analytics | Required |\n| Chatwoot support chat | The chat widget, and the cookie that keeps a conversation alive across a page reload | Functional | Required |\n| Dealfront (Leadfeeder) | Resolves your IP address to the organisation you are connecting from, and reports that organisation's path through the site to our sales team | Marketing | Required |\n\n### What the banner does today, and what it does not\n\n**Your consent choice is recorded and it is honoured by the preference centre — but it does not yet hold\nback every tool in the table above.** At the time of this version the analytics tags, the error reporter\nand the visitor-identification tracker are loaded by the page itself rather than by the consent gate, so\nthey start before you have chosen anything. We are moving them behind the gate.\n\nWe would rather write that down than publish a confident sentence about consent that our own pages do not\nkeep. Until the change lands, three things are worth knowing:\n\n- **Nothing in the analytics, functional or marketing rows is needed to read this site.** Blocking them at\n the browser or network level costs you nothing here, and we neither detect nor defeat it.\n- Withdrawing consent in the preference centre stops the tools that read the gate. The rows named above are\n the ones it does not yet reach.\n- If you want what one of these tools already collected about your visit deleted, write to\n privacy@ever.co with the date and roughly the time. We will have it deleted where the provider gives\n us a way to do that, and tell you plainly where it does not.\n\n### Something that is not a cookie and belongs here anyway\n\nThe site's stylesheet fetches its webfonts from Google's font service while the page loads. No cookie is\nset and nothing is stored on your device — but **every page view discloses your IP address and browser\ndetails to Google**, before any consent question arises and whatever you later choose in the banner.\n\nCourts in Germany have held that loading a font this way without consent is unlawful. The fix is to serve\nthe font from our own servers, and it is on our list. We are naming it here rather than leaving a scanner\nto find it.\n\n### There is no cookieless first-party analytics on this site\n\nSome of our other properties run a self-hosted, cookieless audience-measurement tool that is built to need\nno consent at all. **This site does not run it.** Everything that measures you here belongs to a third\nparty and sits in the analytics or the marketing category, which is why this policy carries no section\nclaiming an exemption for measurement of our own.\n\n### In the documentation\n\nA much shorter list, and it is worth checking separately rather than assuming the table above applies.\n\n| What runs | What it does | Category | Consent |\n|---|---|---|---|\n| Our content delivery and security provider | The same edge routing and bot filtering as the website | Strictly necessary | Not required |\n| Documentation search | Where search credentials are configured, your search terms and IP address reach the hosted search provider. Where they are not, the index is local and your search never leaves the page | Functional | Required |\n| Sentry, where it is configured there | Error reporting for the documentation pages | Analytics | Required |\n\n**No analytics tags, no marketing tools and no chat widget run in the documentation**, and nothing there\nsets an advertising cookie. If you have refused everything on the website and then follow a link into the\ndocumentation, you are not walking into a second set of trackers.\n\n### The system that holds the site's content\n\nThe pages you read are served from a content management system we run on our own servers. Its cookies are\nsign-in cookies for our own staff, on a separate hostname you have no reason to visit. Nothing it sets\nreaches a visitor to ever.co.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://ever.co/privacy) sets out the destinations and the safeguards we rely on for each**,\nand you can ask us for a copy of those safeguards.\n\nTwo lists keep this current, and between them they are the authoritative answer:\n\n- **The table in the product-specific section below** names every cookie and similar technology in use on\n this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,\n how long it lasts, and a link to the provider's own notice.\n- **Our Sub-processor List** covers the wider set of providers that process personal data for us, including\n the many that never touch your device at all. You can obtain the current version at any time from\n privacy@ever.co, and it names the sub-processor, what it does, and where it processes.\n\nWe update both when a provider is added, removed or changed. If you find something on our pages that is not\nin either list, tell us at privacy@ever.co — that is a defect and we will fix it.\n\n## Consent, and how to withdraw it\n\n### How the banner works\n\nOn your first visit we show a consent banner, and **nothing in the functional, analytics or marketing\ncategories is written to or read from your device until you have made a choice.** The strictly necessary\nitems load, because the page cannot be delivered otherwise. Everything else waits.\n\nThe first layer of the banner — the one you see without clicking anything further — carries both a\n**Reject all** and an **Accept all** control, presented with equal prominence. **Refusing everything takes\none click, exactly like accepting everything.** Alongside them is a route into per-category choice, so you\ncan accept analytics and refuse marketing, or any other combination.\n\nThree things that some banners do and ours does not:\n\n- **No pre-ticked boxes.** Every category except strictly necessary starts switched off.\n- **Closing the banner is not consent.** Neither is dismissing it, scrolling past it, or carrying on\n browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.\n- **No dark patterns.** We do not make the reject control smaller, greyer, slower or harder to find than the\n accept control, and we do not hide it a layer down.\n\n### Changing your mind\n\n**Withdrawing consent is as easy as giving it, and you can do it at any time.**\n\nThere is a persistent **Cookie preferences** link in the footer of every page, and an equivalent entry\ninside the application's settings. It opens the same per-category controls you saw in the banner, showing\nwhat you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we\nremove what was stored.\n\nTwo honest limits on that:\n\n- **Withdrawal works forwards, not backwards.** It does not make lawful past processing unlawful, and it\n does not reach into data a third-party provider already received. If you want that deleted too, ask us at\n privacy@ever.co and we will tell you who holds it and how to ask them.\n- **Your choice is stored on the device and browser you made it on.** A different browser, a different\n device or a private window will ask again, because there is nothing there to read. Clearing your browser\n storage deletes the record of your refusal as well, which is why the banner reappears afterwards.\n\n### The record we keep\n\nWhen you make a choice we record what you chose, when you chose it, which categories it covered, and which\nversion of this policy was in force at the time. That record exists for two reasons: so that we honour your\nchoice, and so that we can show what you were asked and what you answered.\n\nYou can ask us for a copy of your own consent record at privacy@ever.co.\n\n### How long a choice lasts before we ask again\n\nWe store a consent choice for **six months**. After that the banner appears again so you can confirm or\nchange it. We will also ask again sooner if we add a purpose or a category your earlier choice did not\ncover, or if this policy changes in a way that materially affects what you agreed to.\n\n**This is our own practice, not a legal requirement.** There is no EU-wide statutory interval for asking\nagain — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to\napply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same\nsix months, and blocking storage at the browser level stops the question permanently.\n\n## Controls in your browser and on your device\n\nOur banner is not the only way to control this, and it is not the strongest one. Your browser and your\noperating system can enforce a choice on every site at once, including ours.\n\n### In a browser\n\nEvery major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under\nprivacy or site settings:\n\n- **Delete cookies and site data**, for one site or all of them.\n- **Block cookies**, either all of them or only those set by third parties.\n- **Clear storage on exit**, so nothing survives the session.\n- **Private or incognito windows**, which discard everything when the window closes.\n- **Per-site permissions**, so you can allow storage on the sites you use and block it everywhere else.\n\nYour browser's own help pages describe exactly where these live in your version — we deliberately do not\nreproduce click-by-click instructions here, because they go stale faster than this document does.\n\nContent blockers and privacy extensions work on our sites too. **Using one is a legitimate choice**, and we\nbuild the Service so that it keeps working when the optional things are blocked.\n\n### In our desktop and mobile applications\n\nAn installed application has no browser settings to change, so the controls are at the operating-system\nlevel instead:\n\n- Reset or limit the **advertising identifier** your device provides.\n- Answer **no** to the app-tracking permission prompt on iOS, which stops access to that identifier\n entirely.\n- Withdraw **notification permission**, which stops the push token being useful.\n- Clear the application's stored data, or uninstall it, which removes everything it kept locally.\n\nThe **Cookie preferences** controls described above are also available inside the application, and they\ngovern the same categories there as on the website.\n\n### What breaks if you block the strictly necessary ones\n\nBlocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to\nexpect:\n\n- **You will not be able to sign in, or stay signed in.** Authentication needs somewhere to keep the\n session.\n- **Forms may fail their security check** and refuse to submit.\n- **Some features will behave inconsistently**, because requests can no longer be kept on the same server.\n- **We cannot remember that you refused.** The record of your choice is itself stored on your device, so\n blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and\n it comes from the mechanism rather than from us being difficult.\n\n### Do Not Track\n\nBrowsers once offered a **Do Not Track** header, and some still do. **We do not treat it, on its own, as a\nrefusal** — and we would rather explain why than quietly ignore it.\n\nNo consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether\nit expressed a considered decision or a default someone else had set, browsers behaved differently, and\nseveral have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.\n\nUse the banner or the preference centre instead. A choice made there is unambiguous, and we record it.\n\n### Global Privacy Control\n\n**Global Privacy Control (GPC)** is the later, better-specified signal, and unlike Do Not Track it is\ndefined to express an actual opt-out rather than a preference.\n\n**Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing\ncategories** on that browser, and we act on it without waiting for you to interact with a banner.\n\nTwo points of detail:\n\n- It applies to the browser or device sending it. Another browser sends its own signal, or none.\n- **An explicit choice you make later in our preference centre takes precedence**, in either direction. If\n you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as\n such. If you would rather that never happened, leave the categories switched off.\n\n## Changes to this policy\n\nWe update this policy when what we do changes — a provider added or removed, a technology retired, a\ncategory reassigned. Every update gets its own version number and effective date, recorded at the end of\nthis document.\n\n**Where a change materially affects what you agreed to** — a new purpose, a new category, or a tool moving\nout of the strictly necessary or exempt group — **we ask for your consent again rather than relying on the\nchoice you made against the old text.** Corrections, clarifications and provider renames are published with\na new version and no fresh request.\n\nEarlier versions stay available, with the dates each was in force, at\n[https://ever.co/cookies](https://ever.co/cookies). The effective date shown with this policy tells you which\nversion applies today.\n\n## How to reach us\n\nQuestions about this policy, about anything in the table above, or about a choice you have made — write to\nprivacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent\nrecord, for the current sub-processor list, or to be excluded from our own analytics, and we will do it\nwithout asking why.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\nIf you think we have handled your data badly, tell us first — we would rather fix it. **You can also\ncomplain to a data protection supervisory authority at any time.** Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the Cookie Policy for\n[ever.co](https://ever.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://ever.co/cookies](https://ever.co/cookies)."
|
|
192
|
+
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[ever.co](https://ever.co) and in the Ever website — the public website, the documentation,\nthe signed-in application, and any desktop or mobile application we publish for it. The product-specific\nsection below lists what is actually in use on each of those surfaces.\n\nIt sits alongside our [Privacy Policy](https://ever.co/privacy). The two documents answer different\nquestions, and it is worth knowing which one you are reading:\n\n- **This policy is about your device.** What we store on it, what we read back from it, why, and how you\n control that.\n- **The [Privacy Policy](https://ever.co/privacy) is about the information itself.** What we do with personal\n data once we hold it, the lawful basis for each purpose, who receives it, how long we keep it, and the\n rights you can exercise over it.\n\nWhere something described here involves personal data, the Privacy Policy governs that processing.\n**Nothing in this policy narrows the rights that document gives you.**\n\n### What this policy does not cover\n\n**Other people's sites and services.** Our pages link to third-party sites, and our Service connects to\nthird-party tools when you ask it to. Once you are on someone else's site, their cookie notice applies, not\nours. We have no control over what they store on your device.\n\n**Your own workspace, your own site, your own people.** Where you use the Service as a customer to run\nsomething of your own — a workspace for your organisation, or a site we provision for you — the pages you\npublish and the people you invite are yours. **This policy is not your cookie notice to your own visitors or\npersonnel, and our banner is not your consent mechanism.** Providing those is your responsibility, on your\nown domain, under your own control.\n\n**A copy you run yourself.** Where the software behind the Service is published as open source and you run\nyour own deployment, this policy describes the service *we* operate — not yours. You choose what your\ndeployment loads and what it stores on your users' devices, and only you can describe it to them.\n\n## Cookies and the other technologies that behave like them\n\nA **cookie** is a small text file that a website asks your browser to keep and hands back to a server on\nlater requests. It is the oldest way of doing this, and the best known — but it is only one of several, and\nthe rules that matter here do not turn on which one is used.\n\n**The law we work to attaches to storing information on your device or reading information back from it,\nwhatever the mechanism.** So wherever this policy says \"cookies\", read it as covering all of the following.\n\n### The technologies\n\n- **Cookies** — as above. Set by the site you are visiting, or by another provider whose code runs on the\n page.\n- **Local storage and session storage** — key-value storage inside your browser. Larger than a cookie, not\n sent automatically with every request, and it can hold exactly the same kind of identifier.\n- **IndexedDB and the browser cache** — structured storage and cached files. Ordinarily used to make pages\n load faster and to let parts of the Service work offline, but capable of holding an identifier too.\n- **Pixels, beacons and tags** — a tiny image or a short script whose only job is to load. The act of\n loading it tells the provider that a page was opened, or an email read, along with your IP address and\n browser details. A pixel often stores nothing at all and still reports on you.\n- **Tracking parameters in links** — identifiers added to a URL so that a click can be attributed to the\n campaign or message that produced it.\n- **SDK identifiers in desktop and mobile applications** — an installed application has no cookie jar. It\n stores identifiers in its own application storage instead, and may use identifiers the operating system\n provides: an advertising identifier, an installation identifier, or a push notification token.\n- **Device and network characteristics** — your IP address, screen size, language, time zone, fonts and\n browser version. Individually unremarkable; combined, they can form a **fingerprint** that recognises a\n device without storing anything on it.\n\n### First-party and third-party\n\n**First-party** means we set it, on our own domain, and it goes to our servers.\n\n**Third-party** means it belongs to another company whose code we have chosen to run on the page — an\nanalytics provider, an embedded video player, a bot-protection service. Their technology reports to them,\nnot to us, and they decide what it does. Note the awkward part plainly: **a third-party resource embedded in\nour page discloses your IP address, your browser and the page you were on to that provider, even when it\nstores nothing on your device at all.** Loading it is the disclosure.\n\nSome third-party technologies are deliberately set up to look first-party — served from a subdomain of ours,\nor routed through our own servers. Where we do that, we say so in the table below rather than letting the\nappearance stand.\n\n### Session and persistent\n\n**Session** items are discarded when you close the browser or the application. They are typically what keeps\nyou signed in and moving through a single visit.\n\n**Persistent** items survive until they expire or you delete them, which is what lets us recognise a\nreturning visitor, remember your preferences, or remember that you refused something. Each entry in the\ntable below states how long it lasts.\n\n## Why we use them\n\nThere are six reasons, and each one maps to one of the categories in the next section. We have written the\ncategory next to each so you can see immediately which ones you control.\n\n- **To sign you in and keep you signed in.** Your session has to be attached to the right account, the right\n workspace and the right organisation as you move between pages, and it has to be protected against being\n replayed or forged by someone else. → *strictly necessary*\n- **To keep the Service secure.** Telling a person apart from an abusive script, protecting forms against\n automated submission, enforcing rate limits, and detecting fraudulent sign-ups and payments.\n → *strictly necessary*\n- **To make the Service work at all.** Routing your request to a healthy server, keeping you on the same one\n where a feature requires it, balancing load, and serving the right version of the application.\n → *strictly necessary*\n- **To remember what you decided about cookies.** Your choice has to be stored somewhere, or we would have\n to ask you on every page. → *strictly necessary*\n- **To remember your preferences.** Language, time zone, theme, layout, a panel you collapsed, a message you\n dismissed, and whether you want the support widget open. → *functional*\n- **To understand how the Service is used.** Which pages and features people actually use, which paths fail,\n and where things are slow — so that we improve the right things rather than the ones we happen to notice.\n → *analytics*\n- **To measure our marketing.** Whether a campaign reached anyone, which content leads to sign-ups, and\n which organisations show interest in the product. → *marketing*\n\nTwo things follow from that list, and we would rather state them than leave them implied.\n\n**Only the first four are needed for the Service to function.** Everything in the last three groups is\noptional. If you refuse all of it, every feature you are entitled to still works, at the same price.\n\n**Where we can achieve a purpose without storing anything on your device, we do.** That is the whole reason\nour own analytics is built the way it is — see the section on analytics without consent below.\n\n## The four categories we use\n\nEvery entry in the table below belongs to exactly one of these four categories. The banner and the\npreference centre use the same four names, so what you agree to and what this policy describes are the same\nthing.\n\n### 1. Strictly necessary — no consent, because the Service cannot run without them\n\nThese are the ones we set because you asked for a service that cannot be delivered otherwise. They are not\noptional, they are not used for analytics or marketing, and there is no switch for them in the preference\ncentre. If you block them at the browser level, parts of the Service will stop working.\n\n- **Session and authentication** — signing you in, keeping you signed in, refreshing your session, and\n binding it to the correct account, workspace and organisation.\n- **Security** — protection against cross-site request forgery, detection of abusive automated traffic, rate\n limiting, and fraud prevention on sign-up and payment.\n- **Load balancing and routing** — sending your request to a healthy server and keeping you there where a\n feature needs it.\n- **Your consent choice** — storing what you decided, so that we can honour it and stop asking.\n\nError and crash diagnostics are **not** in this category by default. Where we use a diagnostics tool that\nrecords more than a technical error — a reconstruction of what was on your screen, for example — it is\nlisted under analytics and it waits for your consent.\n\n#### reCAPTCHA is in this category, and here is our reasoning\n\nWe use Google reCAPTCHA — and on some surfaces an alternative provider, named in the table below — to stop\nautomated abuse of forms such as sign-up, password reset and contact. **We treat it as strictly necessary,\nwhich means it loads without asking you first.**\n\nThe reason is that it protects the specific form you are trying to use. You cannot meaningfully ask for the\nform and refuse the protection on it: without it, those endpoints are abused within hours, which is a\nsecurity failure that harms you as much as us.\n\nWhat that means in practice, stated plainly:\n\n- It collects device and behaviour signals from your browser — mouse and touch movement, timing, browser and\n device characteristics, and your IP address — and **sends them to Google, which acts as its own controller\n for that data under its own privacy notice.**\n- We load it only on pages carrying a protected form. It is not present across the whole site.\n- Where an equivalent provider is available on a surface, we prefer the one that collects less.\n\n**Not every data protection authority accepts that a bot-protection service belongs in the strictly\nnecessary category.** We think it does, for the reason above, and we would rather publish the reasoning and\nlet you judge it than bury the tool in a list. If you would prefer not to submit a form protected this way,\nwrite to privacy@ever.co and we will take it from you another way.\n\n### 2. Functional and preferences — consent required\n\nThese remember choices you have made so that the Service behaves the way you left it: language, time zone,\ntheme, layout, dismissed messages, and support or chat widgets where we offer them.\n\n**Refusing this category costs you convenience, not access.** Everything still works; it simply forgets your\npreferences between visits and you set them again.\n\n### 3. Analytics — consent required\n\nThese tell us how the Service is used: which pages and features are used, which paths people abandon, what\nis slow, and what fails. Depending on the surface this may include a provider's own persistent identifier\nand, where the table says so, a masked reconstruction of a session.\n\nThird-party analytics tools are **off until you turn them on**, and nothing in this category loads before you\nchoose.\n\nThere is one deliberate exception, and it is the subject of the next section: **our own analytics, running on\nour own servers, is designed to operate without a consent requirement** — cookieless, with no persistent\nidentifier and aggregate reporting only. The next section sets out exactly what that involves and the\nconditions it depends on.\n\n### 4. Marketing — consent required\n\nThese measure whether our marketing works and help us understand who is interested in the product:\nattribution of a sign-up to the campaign that produced it, and business-audience identification tools.\n\nOne of these deserves a plain sentence rather than a euphemism. **Visitor identification tools resolve a\nvisitor's IP address to the organisation it belongs to, so that we can see which companies have looked at\nthe product.** They do not tell us your name, but most people do not expect a website to work out their\nemployer, so we would rather say it here than let you find it in a table. It is off unless you consent.\n\n### No cookie walls, ever\n\n**We do not use cookie walls, and we never make access conditional on consenting to non-essential cookies.**\n\nYou can refuse everything except the strictly necessary category and the whole of the Service remains\navailable to you — the same features, the same content, the same price. We do not offer a \"consent or pay\"\nalternative. We do not degrade the experience, hide content, or nag you on every page because you said no.\nRefusing is a decision we record and respect, not a negotiating position.\n\n## Annex: Ever\n\n### The surfaces this covers\n\nTwo, and they are genuinely different: the website at [ever.co](https://ever.co) and the\ndocumentation published alongside it. **There is no signed-in application here** — no account can be\ncreated on this site, so there are no session or authentication cookies, and every page is the same page\nfor everyone.\n\n### On the website\n\n| What runs | What it does | Category | Consent |\n|---|---|---|---|\n| Our content delivery and security provider | Routes your request to the nearest edge, filters hostile traffic, and sets a short-lived cookie that tells a browser apart from a bot | Strictly necessary | Not required |\n| Our consent management provider | Presents the banner and the preference centre, stores what you chose, and holds the record of it | Strictly necessary | Not required |\n| Google reCAPTCHA | Bot protection on the enquiry, careers, notification and newsletter forms. Loads only on a page carrying one of them | Strictly necessary | Not required — for the reasons given above |\n| Google Tag Manager | A container rather than a tag: it loads the tools below, and further tags can be added through it without a change to the site's code | Analytics | Required |\n| Google Analytics | Traffic measurement — pages viewed, referrers, devices, coarse location from the IP address | Analytics | Required |\n| PostHog | Product and site analytics, with its own identifier stored on your device, sent to the provider's United States cloud | Analytics | Required |\n| Sentry | Error and performance reporting for the pages themselves | Analytics | Required |\n| Chatwoot support chat | The chat widget, and the cookie that keeps a conversation alive across a page reload | Functional | Required |\n| Dealfront (Leadfeeder) | Resolves your IP address to the organisation you are connecting from, and reports that organisation's path through the site to our sales team | Marketing | Required |\n\n### What the banner does today, and what it does not\n\n**Your consent choice is recorded and it is honoured by the preference centre — but it does not yet hold\nback every tool in the table above.** At the time of this version the analytics tags, the error reporter\nand the visitor-identification tracker are loaded by the page itself rather than by the consent gate, so\nthey start before you have chosen anything. We are moving them behind the gate.\n\nWe would rather write that down than publish a confident sentence about consent that our own pages do not\nkeep. Until the change lands, three things are worth knowing:\n\n- **Nothing in the analytics, functional or marketing rows is needed to read this site.** Blocking them at\n the browser or network level costs you nothing here, and we neither detect nor defeat it.\n- Withdrawing consent in the preference centre stops the tools that read the gate. The rows named above are\n the ones it does not yet reach.\n- If you want what one of these tools already collected about your visit deleted, write to\n privacy@ever.co with the date and roughly the time. We will have it deleted where the provider gives\n us a way to do that, and tell you plainly where it does not.\n\n### Something that is not a cookie and belongs here anyway\n\nThe site's stylesheet fetches its webfonts from Google's font service while the page loads. No cookie is\nset and nothing is stored on your device — but **every page view discloses your IP address and browser\ndetails to Google**, before any consent question arises and whatever you later choose in the banner.\n\nCourts in Germany have held that loading a font this way without consent is unlawful. The fix is to serve\nthe font from our own servers, and it is on our list. We are naming it here rather than leaving a scanner\nto find it.\n\n### There is no cookieless first-party analytics on this site\n\nSome of our other properties run a self-hosted, cookieless audience-measurement tool that is built to need\nno consent at all. **This site does not run it.** Everything that measures you here belongs to a third\nparty and sits in the analytics or the marketing category, which is why this policy carries no section\nclaiming an exemption for measurement of our own.\n\n### In the documentation\n\nA much shorter list, and it is worth checking separately rather than assuming the table above applies.\n\n| What runs | What it does | Category | Consent |\n|---|---|---|---|\n| Our content delivery and security provider | The same edge routing and bot filtering as the website | Strictly necessary | Not required |\n| Documentation search | Where search credentials are configured, your search terms and IP address reach the hosted search provider. Where they are not, the index is local and your search never leaves the page | Functional | Required |\n| Sentry, where it is configured there | Error reporting for the documentation pages | Analytics | Required |\n\n**No analytics tags, no marketing tools and no chat widget run in the documentation**, and nothing there\nsets an advertising cookie. If you have refused everything on the website and then follow a link into the\ndocumentation, you are not walking into a second set of trackers.\n\n### The system that holds the site's content\n\nThe pages you read are served from a content management system we run on our own servers. Its cookies are\nsign-in cookies for our own staff, on a separate hostname you have no reason to visit. Nothing it sets\nreaches a visitor to ever.co.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n#### Measurement injected by that layer, which our banner cannot control\n\nThere is one thing here we would rather state plainly than have you discover in a network trace. **Our\ncontent delivery provider injects its own lightweight measurement script at the edge — into the response,\nafter it leaves our servers.** It is not in our code, our consent system never sees it, and **switching a\ncategory off in our preference centre does not stop it**, because by the time the page reaches you the\nscript is already part of it.\n\nWhat it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent\nidentifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to\nanything else we hold.\n\nWhat it is not: covered by the exemption we claim for our own analytics. That argument rests on the data\nstaying on our own infrastructure, and this is a third party receiving it. **We are not going to stretch\nthe same reasoning over both.**\n\nIf you would rather it did not run, a content blocker or a network-level block stops it, and we do not\nattempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the\ncurrent provider and exactly what it collects.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://ever.co/privacy) sets out the destinations and the safeguards we rely on for each**,\nand you can ask us for a copy of those safeguards.\n\nTwo lists keep this current, and between them they are the authoritative answer:\n\n- **The table in the product-specific section below** names every cookie and similar technology in use on\n this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,\n how long it lasts, and a link to the provider's own notice.\n- **Our Sub-processor List** covers the wider set of providers that process personal data for us, including\n the many that never touch your device at all. You can obtain the current version at any time from\n privacy@ever.co, and it names the sub-processor, what it does, and where it processes.\n\nWe update both when a provider is added, removed or changed. If you find something on our pages that is not\nin either list, tell us at privacy@ever.co — that is a defect and we will fix it.\n\n## Consent, and how to withdraw it\n\n### How the banner works\n\nOn your first visit we show a consent banner, and **nothing in the functional, analytics or marketing\ncategories is written to or read from your device until you have made a choice.** The strictly necessary\nitems load, because the page cannot be delivered otherwise. Everything else waits.\n\nThe first layer of the banner — the one you see without clicking anything further — carries both a\n**Reject all** and an **Accept all** control, presented with equal prominence. **Refusing everything takes\none click, exactly like accepting everything.** Alongside them is a route into per-category choice, so you\ncan accept analytics and refuse marketing, or any other combination.\n\nThree things that some banners do and ours does not:\n\n- **No pre-ticked boxes.** Every category except strictly necessary starts switched off.\n- **Closing the banner is not consent.** Neither is dismissing it, scrolling past it, or carrying on\n browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.\n- **No dark patterns.** We do not make the reject control smaller, greyer, slower or harder to find than the\n accept control, and we do not hide it a layer down.\n\n### Changing your mind\n\n**Withdrawing consent is as easy as giving it, and you can do it at any time.**\n\nThere is a persistent **Cookie preferences** link in the footer of every page, and an equivalent entry\ninside the application's settings. It opens the same per-category controls you saw in the banner, showing\nwhat you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we\nremove what was stored.\n\nTwo honest limits on that:\n\n- **Withdrawal works forwards, not backwards.** It does not make lawful past processing unlawful, and it\n does not reach into data a third-party provider already received. If you want that deleted too, ask us at\n privacy@ever.co and we will tell you who holds it and how to ask them.\n- **Your choice is stored on the device and browser you made it on.** A different browser, a different\n device or a private window will ask again, because there is nothing there to read. Clearing your browser\n storage deletes the record of your refusal as well, which is why the banner reappears afterwards.\n\n### The record we keep\n\nWhen you make a choice we record what you chose, when you chose it, which categories it covered, and which\nversion of this policy was in force at the time. That record exists for two reasons: so that we honour your\nchoice, and so that we can show what you were asked and what you answered.\n\nYou can ask us for a copy of your own consent record at privacy@ever.co.\n\n### How long a choice lasts before we ask again\n\nWe store a consent choice for **six months**. After that the banner appears again so you can confirm or\nchange it. We will also ask again sooner if we add a purpose or a category your earlier choice did not\ncover, or if this policy changes in a way that materially affects what you agreed to.\n\n**This is our own practice, not a legal requirement.** There is no EU-wide statutory interval for asking\nagain — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to\napply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same\nsix months, and blocking storage at the browser level stops the question permanently.\n\n## Controls in your browser and on your device\n\nOur banner is not the only way to control this, and it is not the strongest one. Your browser and your\noperating system can enforce a choice on every site at once, including ours.\n\n### In a browser\n\nEvery major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under\nprivacy or site settings:\n\n- **Delete cookies and site data**, for one site or all of them.\n- **Block cookies**, either all of them or only those set by third parties.\n- **Clear storage on exit**, so nothing survives the session.\n- **Private or incognito windows**, which discard everything when the window closes.\n- **Per-site permissions**, so you can allow storage on the sites you use and block it everywhere else.\n\nYour browser's own help pages describe exactly where these live in your version — we deliberately do not\nreproduce click-by-click instructions here, because they go stale faster than this document does.\n\nContent blockers and privacy extensions work on our sites too. **Using one is a legitimate choice**, and we\nbuild the Service so that it keeps working when the optional things are blocked.\n\n### In our desktop and mobile applications\n\nAn installed application has no browser settings to change, so the controls are at the operating-system\nlevel instead:\n\n- Reset or limit the **advertising identifier** your device provides.\n- Answer **no** to the app-tracking permission prompt on iOS, which stops access to that identifier\n entirely.\n- Withdraw **notification permission**, which stops the push token being useful.\n- Clear the application's stored data, or uninstall it, which removes everything it kept locally.\n\nThe **Cookie preferences** controls described above are also available inside the application, and they\ngovern the same categories there as on the website.\n\n### What breaks if you block the strictly necessary ones\n\nBlocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to\nexpect:\n\n- **You will not be able to sign in, or stay signed in.** Authentication needs somewhere to keep the\n session.\n- **Forms may fail their security check** and refuse to submit.\n- **Some features will behave inconsistently**, because requests can no longer be kept on the same server.\n- **We cannot remember that you refused.** The record of your choice is itself stored on your device, so\n blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and\n it comes from the mechanism rather than from us being difficult.\n\n### Do Not Track\n\nBrowsers once offered a **Do Not Track** header, and some still do. **We do not treat it, on its own, as a\nrefusal** — and we would rather explain why than quietly ignore it.\n\nNo consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether\nit expressed a considered decision or a default someone else had set, browsers behaved differently, and\nseveral have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.\n\nUse the banner or the preference centre instead. A choice made there is unambiguous, and we record it.\n\n### Global Privacy Control\n\n**Global Privacy Control (GPC)** is the later, better-specified signal, and unlike Do Not Track it is\ndefined to express an actual opt-out rather than a preference.\n\n**Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing\ncategories** on that browser, and we act on it without waiting for you to interact with a banner.\n\nTwo points of detail:\n\n- It applies to the browser or device sending it. Another browser sends its own signal, or none.\n- **An explicit choice you make later in our preference centre takes precedence**, in either direction. If\n you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as\n such. If you would rather that never happened, leave the categories switched off.\n\n## Changes to this policy\n\nWe update this policy when what we do changes — a provider added or removed, a technology retired, a\ncategory reassigned. Every update gets its own version number and effective date, recorded at the end of\nthis document.\n\n**Where a change materially affects what you agreed to** — a new purpose, a new category, or a tool moving\nout of the strictly necessary or exempt group — **we ask for your consent again rather than relying on the\nchoice you made against the old text.** Corrections, clarifications and provider renames are published with\na new version and no fresh request.\n\nEarlier versions stay available, with the dates each was in force, at\n[https://ever.co/cookies](https://ever.co/cookies). The effective date shown with this policy tells you which\nversion applies today.\n\n## How to reach us\n\nQuestions about this policy, about anything in the table above, or about a choice you have made — write to\nprivacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent\nrecord, for the current sub-processor list, or to be excluded from our own analytics, and we will do it\nwithout asking why.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\nIf you think we have handled your data badly, tell us first — we would rather fix it. **You can also\ncomplain to a data protection supervisory authority at any time.** Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the Cookie Policy for\n[ever.co](https://ever.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://ever.co/cookies](https://ever.co/cookies)."
|
|
193
193
|
}
|
|
@@ -257,8 +257,8 @@ guesswork — but it is that operator's notice to write, and ours does not do th
|
|
|
257
257
|
<td>Getting your request to the site, absorbing attack traffic, telling a person apart from a hostile script</td>
|
|
258
258
|
</tr>
|
|
259
259
|
<tr>
|
|
260
|
-
<td>Consent record</td>
|
|
261
|
-
<td>
|
|
260
|
+
<td>Consent record (<code>cg_consent</code>)</td>
|
|
261
|
+
<td>Us — first-party</td>
|
|
262
262
|
<td>Strictly necessary</td>
|
|
263
263
|
<td>Not required</td>
|
|
264
264
|
<td>Storing what you chose, so we can honour it and stop asking</td>
|
|
@@ -484,6 +484,21 @@ absorbs attacks and filters hostile traffic — along with bot protection on for
|
|
|
484
484
|
payment. These see connection metadata and may set their own security cookies.</p>
|
|
485
485
|
<p><strong>Strictly necessary</strong>, and therefore not consent-gated. Our reasoning for putting bot protection in that
|
|
486
486
|
category, including what it sends to its provider, is set out in the categories section above.</p>
|
|
487
|
+
<h4 id="measurement-injected-by-that-layer-which-our-banner-cannot-control" tabindex="-1">Measurement injected by that layer, which our banner cannot control</h4>
|
|
488
|
+
<p>There is one thing here we would rather state plainly than have you discover in a network trace. <strong>Our
|
|
489
|
+
content delivery provider injects its own lightweight measurement script at the edge — into the response,
|
|
490
|
+
after it leaves our servers.</strong> It is not in our code, our consent system never sees it, and <strong>switching a
|
|
491
|
+
category off in our preference centre does not stop it</strong>, because by the time the page reaches you the
|
|
492
|
+
script is already part of it.</p>
|
|
493
|
+
<p>What it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent
|
|
494
|
+
identifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to
|
|
495
|
+
anything else we hold.</p>
|
|
496
|
+
<p>What it is not: covered by the exemption we claim for our own analytics. That argument rests on the data
|
|
497
|
+
staying on our own infrastructure, and this is a third party receiving it. <strong>We are not going to stretch
|
|
498
|
+
the same reasoning over both.</strong></p>
|
|
499
|
+
<p>If you would rather it did not run, a content blocker or a network-level block stops it, and we do not
|
|
500
|
+
attempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the
|
|
501
|
+
current provider and exactly what it collects.</p>
|
|
487
502
|
<h3 id="where-these-providers-are-and-where-to-find-the-full-list" tabindex="-1">Where these providers are, and where to find the full list</h3>
|
|
488
503
|
<p>Some of these providers are established outside the European Economic Area, and using them involves an
|
|
489
504
|
international transfer of personal data. <strong>The transfers section of our
|
|
@@ -628,6 +643,6 @@ complain to a data protection supervisory authority at any time.</strong> Ours i
|
|
|
628
643
|
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
629
644
|
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
630
645
|
to the authority for the country where you live or work.</p>
|
|
631
|
-
<p>This document is version 1.0.
|
|
646
|
+
<p>This document is version 1.0.2 of the Cookie Policy for
|
|
632
647
|
<a href="https://everdemand.co">everdemand.co</a>, in force from 2026-08-02. Earlier versions, with the dates
|
|
633
648
|
they applied, are at <a href="https://everdemand.co/cookies">https://everdemand.co/cookies</a>.</p>
|
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "e77188faba4e700b95132eea00aaa992e54dd55279d448de037e35e94c9ccc5b",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/cookies/010-scope",
|
|
@@ -222,5 +222,5 @@
|
|
|
222
222
|
}
|
|
223
223
|
],
|
|
224
224
|
"path": "content/cookies/ever-demand/en.html",
|
|
225
|
-
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[everdemand.co](https://everdemand.co) and in Ever Demand — the public website, the documentation,\nthe signed-in application, and any desktop or mobile application we publish for it. The product-specific\nsection below lists what is actually in use on each of those surfaces.\n\nIt sits alongside our [Privacy Policy](https://everdemand.co/privacy). The two documents answer different\nquestions, and it is worth knowing which one you are reading:\n\n- **This policy is about your device.** What we store on it, what we read back from it, why, and how you\n control that.\n- **The [Privacy Policy](https://everdemand.co/privacy) is about the information itself.** What we do with personal\n data once we hold it, the lawful basis for each purpose, who receives it, how long we keep it, and the\n rights you can exercise over it.\n\nWhere something described here involves personal data, the Privacy Policy governs that processing.\n**Nothing in this policy narrows the rights that document gives you.**\n\n### What this policy does not cover\n\n**Other people's sites and services.** Our pages link to third-party sites, and our Service connects to\nthird-party tools when you ask it to. Once you are on someone else's site, their cookie notice applies, not\nours. We have no control over what they store on your device.\n\n**Your own workspace, your own site, your own people.** Where you use the Service as a customer to run\nsomething of your own — a workspace for your organisation, or a site we provision for you — the pages you\npublish and the people you invite are yours. **This policy is not your cookie notice to your own visitors or\npersonnel, and our banner is not your consent mechanism.** Providing those is your responsibility, on your\nown domain, under your own control.\n\n**A copy you run yourself.** Where the software behind the Service is published as open source and you run\nyour own deployment, this policy describes the service *we* operate — not yours. You choose what your\ndeployment loads and what it stores on your users' devices, and only you can describe it to them.\n\n## Cookies and the other technologies that behave like them\n\nA **cookie** is a small text file that a website asks your browser to keep and hands back to a server on\nlater requests. It is the oldest way of doing this, and the best known — but it is only one of several, and\nthe rules that matter here do not turn on which one is used.\n\n**The law we work to attaches to storing information on your device or reading information back from it,\nwhatever the mechanism.** So wherever this policy says \"cookies\", read it as covering all of the following.\n\n### The technologies\n\n- **Cookies** — as above. Set by the site you are visiting, or by another provider whose code runs on the\n page.\n- **Local storage and session storage** — key-value storage inside your browser. Larger than a cookie, not\n sent automatically with every request, and it can hold exactly the same kind of identifier.\n- **IndexedDB and the browser cache** — structured storage and cached files. Ordinarily used to make pages\n load faster and to let parts of the Service work offline, but capable of holding an identifier too.\n- **Pixels, beacons and tags** — a tiny image or a short script whose only job is to load. The act of\n loading it tells the provider that a page was opened, or an email read, along with your IP address and\n browser details. A pixel often stores nothing at all and still reports on you.\n- **Tracking parameters in links** — identifiers added to a URL so that a click can be attributed to the\n campaign or message that produced it.\n- **SDK identifiers in desktop and mobile applications** — an installed application has no cookie jar. It\n stores identifiers in its own application storage instead, and may use identifiers the operating system\n provides: an advertising identifier, an installation identifier, or a push notification token.\n- **Device and network characteristics** — your IP address, screen size, language, time zone, fonts and\n browser version. Individually unremarkable; combined, they can form a **fingerprint** that recognises a\n device without storing anything on it.\n\n### First-party and third-party\n\n**First-party** means we set it, on our own domain, and it goes to our servers.\n\n**Third-party** means it belongs to another company whose code we have chosen to run on the page — an\nanalytics provider, an embedded video player, a bot-protection service. Their technology reports to them,\nnot to us, and they decide what it does. Note the awkward part plainly: **a third-party resource embedded in\nour page discloses your IP address, your browser and the page you were on to that provider, even when it\nstores nothing on your device at all.** Loading it is the disclosure.\n\nSome third-party technologies are deliberately set up to look first-party — served from a subdomain of ours,\nor routed through our own servers. Where we do that, we say so in the table below rather than letting the\nappearance stand.\n\n### Session and persistent\n\n**Session** items are discarded when you close the browser or the application. They are typically what keeps\nyou signed in and moving through a single visit.\n\n**Persistent** items survive until they expire or you delete them, which is what lets us recognise a\nreturning visitor, remember your preferences, or remember that you refused something. Each entry in the\ntable below states how long it lasts.\n\n## Why we use them\n\nThere are six reasons, and each one maps to one of the categories in the next section. We have written the\ncategory next to each so you can see immediately which ones you control.\n\n- **To sign you in and keep you signed in.** Your session has to be attached to the right account, the right\n workspace and the right organisation as you move between pages, and it has to be protected against being\n replayed or forged by someone else. → *strictly necessary*\n- **To keep the Service secure.** Telling a person apart from an abusive script, protecting forms against\n automated submission, enforcing rate limits, and detecting fraudulent sign-ups and payments.\n → *strictly necessary*\n- **To make the Service work at all.** Routing your request to a healthy server, keeping you on the same one\n where a feature requires it, balancing load, and serving the right version of the application.\n → *strictly necessary*\n- **To remember what you decided about cookies.** Your choice has to be stored somewhere, or we would have\n to ask you on every page. → *strictly necessary*\n- **To remember your preferences.** Language, time zone, theme, layout, a panel you collapsed, a message you\n dismissed, and whether you want the support widget open. → *functional*\n- **To understand how the Service is used.** Which pages and features people actually use, which paths fail,\n and where things are slow — so that we improve the right things rather than the ones we happen to notice.\n → *analytics*\n- **To measure our marketing.** Whether a campaign reached anyone, which content leads to sign-ups, and\n which organisations show interest in the product. → *marketing*\n\nTwo things follow from that list, and we would rather state them than leave them implied.\n\n**Only the first four are needed for the Service to function.** Everything in the last three groups is\noptional. If you refuse all of it, every feature you are entitled to still works, at the same price.\n\n**Where we can achieve a purpose without storing anything on your device, we do.** That is the whole reason\nour own analytics is built the way it is — see the section on analytics without consent below.\n\n## The four categories we use\n\nEvery entry in the table below belongs to exactly one of these four categories. The banner and the\npreference centre use the same four names, so what you agree to and what this policy describes are the same\nthing.\n\n### 1. Strictly necessary — no consent, because the Service cannot run without them\n\nThese are the ones we set because you asked for a service that cannot be delivered otherwise. They are not\noptional, they are not used for analytics or marketing, and there is no switch for them in the preference\ncentre. If you block them at the browser level, parts of the Service will stop working.\n\n- **Session and authentication** — signing you in, keeping you signed in, refreshing your session, and\n binding it to the correct account, workspace and organisation.\n- **Security** — protection against cross-site request forgery, detection of abusive automated traffic, rate\n limiting, and fraud prevention on sign-up and payment.\n- **Load balancing and routing** — sending your request to a healthy server and keeping you there where a\n feature needs it.\n- **Your consent choice** — storing what you decided, so that we can honour it and stop asking.\n\nError and crash diagnostics are **not** in this category by default. Where we use a diagnostics tool that\nrecords more than a technical error — a reconstruction of what was on your screen, for example — it is\nlisted under analytics and it waits for your consent.\n\n#### reCAPTCHA is in this category, and here is our reasoning\n\nWe use Google reCAPTCHA — and on some surfaces an alternative provider, named in the table below — to stop\nautomated abuse of forms such as sign-up, password reset and contact. **We treat it as strictly necessary,\nwhich means it loads without asking you first.**\n\nThe reason is that it protects the specific form you are trying to use. You cannot meaningfully ask for the\nform and refuse the protection on it: without it, those endpoints are abused within hours, which is a\nsecurity failure that harms you as much as us.\n\nWhat that means in practice, stated plainly:\n\n- It collects device and behaviour signals from your browser — mouse and touch movement, timing, browser and\n device characteristics, and your IP address — and **sends them to Google, which acts as its own controller\n for that data under its own privacy notice.**\n- We load it only on pages carrying a protected form. It is not present across the whole site.\n- Where an equivalent provider is available on a surface, we prefer the one that collects less.\n\n**Not every data protection authority accepts that a bot-protection service belongs in the strictly\nnecessary category.** We think it does, for the reason above, and we would rather publish the reasoning and\nlet you judge it than bury the tool in a list. If you would prefer not to submit a form protected this way,\nwrite to privacy@ever.co and we will take it from you another way.\n\n### 2. Functional and preferences — consent required\n\nThese remember choices you have made so that the Service behaves the way you left it: language, time zone,\ntheme, layout, dismissed messages, and support or chat widgets where we offer them.\n\n**Refusing this category costs you convenience, not access.** Everything still works; it simply forgets your\npreferences between visits and you set them again.\n\n### 3. Analytics — consent required\n\nThese tell us how the Service is used: which pages and features are used, which paths people abandon, what\nis slow, and what fails. Depending on the surface this may include a provider's own persistent identifier\nand, where the table says so, a masked reconstruction of a session.\n\nThird-party analytics tools are **off until you turn them on**, and nothing in this category loads before you\nchoose.\n\nThere is one deliberate exception, and it is the subject of the next section: **our own analytics, running on\nour own servers, is designed to operate without a consent requirement** — cookieless, with no persistent\nidentifier and aggregate reporting only. The next section sets out exactly what that involves and the\nconditions it depends on.\n\n### 4. Marketing — consent required\n\nThese measure whether our marketing works and help us understand who is interested in the product:\nattribution of a sign-up to the campaign that produced it, and business-audience identification tools.\n\nOne of these deserves a plain sentence rather than a euphemism. **Visitor identification tools resolve a\nvisitor's IP address to the organisation it belongs to, so that we can see which companies have looked at\nthe product.** They do not tell us your name, but most people do not expect a website to work out their\nemployer, so we would rather say it here than let you find it in a table. It is off unless you consent.\n\n### No cookie walls, ever\n\n**We do not use cookie walls, and we never make access conditional on consenting to non-essential cookies.**\n\nYou can refuse everything except the strictly necessary category and the whole of the Service remains\navailable to you — the same features, the same content, the same price. We do not offer a \"consent or pay\"\nalternative. We do not degrade the experience, hide content, or nag you on every page because you said no.\nRefusing is a decision we record and respect, not a negotiating position.\n\n## Our own analytics, and why it runs without asking you\n\nWe want to know whether the Service works — which pages load, which fail, whether a change made things\nbetter or worse. That is a legitimate thing for us to want, and it is also the reason most websites hand\ntheir visitors to a third-party analytics company. **We built ours the other way round: we run our own\nanalytics software, on our own servers, in our own infrastructure, and it is designed so that there is\nnothing about you worth asking permission for.** No third-party analytics vendor receives this data. The\ntable below names the software and where it runs.\n\n### What it does, and what it deliberately does not do\n\n- **It sets no cookies.** Nothing is written to your device — no cookie, no local storage entry, nothing.\n- **It creates no persistent identifier.** There is no visitor ID that follows you from one day to the next.\n- **It does not track you across sites or across devices.** It measures our own site only. It has no\n presence anywhere else, so there is nothing to join up.\n- **It counts visits using a hash that is salted and rotated daily.** A one-way value is derived from your\n IP address and browser details together with a secret salt, purely to tell one visit apart from another\n within a single day. **We change the salt every day, which breaks the link between today's value and\n tomorrow's by design.** The inputs are not stored.\n- **It reports only in aggregate** — page counts, referrers, countries, browsers. No profile of you, no\n individual visitor record to open, nothing to hand to a marketing tool.\n- **It keeps data for a bounded period,** stated in the table below, after which the underlying records go\n and only aggregate statistics remain.\n- **It is never used for advertising,** and the data is not sold, shared for anyone else's purposes, or\n combined with data from another source.\n\n### Why this can run without consent, and the condition attached\n\nUnder the ePrivacy rules, storing information on your device or reading it back generally requires your\nprior consent, with a narrow exemption for what is strictly necessary. European regulators — the French CNIL\nmost explicitly — have also published criteria under which a first-party audience-measurement tool can be\ntreated as exempt: it must serve only the operator's own site, produce only aggregate statistics, avoid\ncross-site and cross-device tracking, avoid a persistent identifier, and keep data for a limited period.\n\n**Our configuration is built to meet those criteria. That is the whole basis on which it runs without\nasking you — and it is conditional on every one of the measures listed above.**\n\nWe are not claiming a general permission. If we ever changed any of it — a persistent identifier, a fixed\nsalt, measurement across more than one of our own sites, a third-party vendor, reporting at the level of an\nindividual visitor — **the exemption would no longer apply, and we would move this tool into the analytics\ncategory and ask for your consent before making the change.** The category is a configuration setting in our\nconsent system, not a paragraph in this document, precisely so that it can be changed the moment the facts\nchange.\n\nOne further distinction worth being precise about. The exemption above is about **storage on your device**.\nWhere the resulting data is still personal data, the separate question of a lawful basis under data\nprotection law arises, and ours is our legitimate interest in understanding whether our own service works —\nassessed against the fact that the measurement is aggregate, short-lived and cannot be traced back to you.\n**You can object to that processing**, and the paragraph below is how.\n\n### You can switch it off anyway\n\nYou do not have to accept our reasoning to escape the measurement.\n\n- Open **Cookie preferences** from the footer of any page. Our own analytics appears there with a switch,\n even though it runs without consent, and turning it off stops it.\n- Blocking it at the browser or network level also works, and we do not try to detect or defeat that.\n- Or write to privacy@ever.co and ask us to exclude you.\n\n**We do not ask for a reason and we do not require an account.**\n\n### Separately, and only with your consent, we also use third-party tools\n\nAlongside our own analytics we use third-party analytics and marketing products. Those are a genuinely\ndifferent proposition: another company receives the data, they typically use a persistent identifier of\ntheir own, and some are capable of following a visitor across other sites entirely.\n\n**Nothing in that group runs until you consent to it**, and none of it is covered by the exemption described\nabove. Each tool is named in the table below, with what it does, who operates it, and how long anything it\nstores lasts.\n\n## Annex: Ever Demand — what runs on each surface\n\n### Where this policy applies, and where it does not\n\nWe operate three things under this name, and this policy covers all three and nothing else:\n\n- the website at [everdemand.co](https://everdemand.co);\n- the documentation site at [docs.everdemand.co](https://docs.everdemand.co); and\n- the content management system behind the website, which only our own editors sign in to.\n\n**There is no hosted Ever Demand platform.** No shopping site, merchant console, administration console\nor courier application is operated by us at any address, so there is no application surface here for this\npolicy to describe.\n\n**A deployment somebody else runs is not covered.** The shopping site a business built on this software sets\nits own cookies, on its own domain, under its own notice. The section near the end says what the software\nstores in a browser and on a device, so that an operator can write that notice from facts rather than\nguesswork — but it is that operator's notice to write, and ours does not do the job for them.\n\n### 1. The website at [everdemand.co](https://everdemand.co)\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Edge, routing and bot-filtering cookies | Cloudflare | Strictly necessary | Not required | Getting your request to the site, absorbing attack traffic, telling a person apart from a hostile script |\n| Consent record | iubenda | Strictly necessary | Not required | Storing what you chose, so we can honour it and stop asking |\n| reCAPTCHA | Google | Strictly necessary | Not required | Stopping automated abuse of the contact, pricing-notification and newsletter forms. Read the next section — on the current build it loads on every page, not only on the ones carrying a form |\n| Google Analytics 4, delivered through a tag container | Google | Analytics | Required | Which pages and campaigns bring people to the site, and where people give up |\n| Product analytics | PostHog | Analytics | Required | Page views and events, on the environments where a key is configured |\n| Business visitor identification | Leadfeeder | Marketing | Required | Resolving your IP address to the organisation it belongs to, so that we can see which companies have looked at the product |\n\n**The last three rows say \"required\" because that is what this site is meant to do.** The next section is\nabout the fact that today it does not.\n\n### The defect on this site, named rather than left for you to find\n\n**On the build of [everdemand.co](https://everdemand.co) running as this policy is published, the consent\nbanner does not gate the analytics and marketing tools.** The tag container and the visitor-identification\nscript are loaded as ordinary page scripts sitting alongside the banner rather than behind it. Nothing\nlistens for your decision, and nothing is held back by it, so they run when the page loads whatever you\nchoose.\n\n**Two smaller things follow from the same mistake.** reCAPTCHA loads on every page of this site rather than\nonly on the pages carrying a protected form, which is narrower than the commitment made in the section above.\nAnd the consent record is stored, so your choice is captured accurately — it simply is not acted on.\n\nWe are not going to write this up as policy and hope you do not check. **The table above is what this site is\nsupposed to do, and what it will do once those scripts are moved behind the consent decision**, which is how\nour other sites already work. Until that ships:\n\n- **Blocking these tools in your browser or at the network level works**, and we do not try to detect or\n defeat it.\n- Writing to privacy@ever.co and asking to be excluded also works. We do not ask for a reason and we do\n not require an account.\n- If you have already loaded the site and want what was collected removed, the same address is the route, and\n you do not have to explain yourself.\n\n### Things on this site that are not cookies but are still disclosures\n\nNone of these stores anything on your device. Each of them still sends something about you to somebody else,\nso naming them is the point.\n\n- **Error monitoring.** When a page fails, a report goes to Sentry carrying your IP address, your browser, the\n page you were on and the context around the failure. It runs on all three surfaces and it is not waiting for\n a consent choice, because it is not measuring you — it exists so that a fault is visible to us with enough\n detail to fix it. **We do not run session replay or screen reconstruction on any of these surfaces.** If you\n would rather not be in those reports, privacy@ever.co will exclude you.\n- **Sending us a form.** Using the contact form or the pricing-notification form sends what you wrote through\n Postmark, which delivers the email to us.\n- **Subscribing.** Joining the newsletter sends your address to Mailchimp, which holds the list.\n- **Opening the chat.** The support chat widget is Chatwoot, and it starts a conversation record — your\n message, your page, your IP address — when you open it, not before.\n\n### 2. The documentation site\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Not required | Routing and filtering, as above |\n| Theme and navigation preferences, held in your browser's local storage | Us | Functional | Required | Remembering dark mode and which sections you collapsed |\n| Documentation search | Algolia | Functional | Required | Searching the documentation, where the search keys are configured for that site. **Where they are not, search runs entirely in your browser and sends nothing to anyone** |\n\nThere is no analytics and no marketing tool on the documentation site.\n\n### 3. The content management system\n\nThis is a staff surface. A visitor to the public website never reaches it, and nothing about you as a reader\nis processed there.\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Session and sign-in cookies | Us | Strictly necessary | Not required | Signing an editor in and keeping them signed in |\n| Cross-site request forgery token | Us | Strictly necessary | Not required | Stopping another site submitting a request as a signed-in editor |\n| Edge and security cookies | Cloudflare | Strictly necessary | Not required | Routing and filtering, as above |\n\nNo analytics, no marketing tools, no third-party measurement of any kind.\n\n### Our own analytics does not run here\n\nThe section above describes audience measurement we run on our own servers, cookieless and without a\npersistent identifier, and explains why it does not need to ask you. **None of it is deployed on these three\nsurfaces.** The only audience measurement on this product's website is Google's, and it belongs in the\nanalytics category where consent is required. The exemption described earlier is not doing any work here, and\nwe would rather say so than let you assume the gentler arrangement applies.\n\n### The mobile applications need a different section, because cookies are the wrong word\n\nThe shopping, merchant and courier applications are not browsers. What they hold is device identifiers rather\nthan cookies, and the operator who publishes a build decides all of it:\n\n- **A device record** — a device identifier, the platform, the language and a push channel identifier — is\n created so that the platform can send an order or an invite to the right handset.\n- **Sign-in state is held on the device**, in application storage rather than in a cookie. The website leg of\n social sign-in uses a server-side session cookie.\n- **Google Analytics, Mixpanel and Intercom are compiled into all three applications**, including the courier\n application, and the courier build additionally carries a plugin that reads a unique device identifier. Each\n of these is inert until the operator supplies a key and ships a build containing it.\n\n**Analytics inside a worker's application is a harder problem than analytics in a shopper's application, and\nit should not be treated as the same decision.** A shopper can uninstall. A courier who was given the\napplication to do a job cannot, and an in-app tracking prompt put in front of someone whose employer issued\nthe device is not a free choice. An operator switching those keys on for the courier build is measuring a\nworker, and the acceptable use annex to this product says what that requires.\n\nApp-store privacy labels and the operating system's own tracking prompt belong to whoever publishes the\nbuild. **That is the operator, not us.**\n\n### If you run the software yourself\n\nThe platform stores a signed access token and interface state in the browser or the application, and sets a\nserver-side session cookie on the social sign-in legs. Beyond that, **every tracker in a deployment is one the\noperator added**: the maps key, the analytics keys, any tag you drop into the shopping site, and anything your\nown marketing team wants.\n\nYour cookie notice, your banner and your consent record are yours. The legal pages bundled inside the software\nare not a consent mechanism and were never one, and ours governs our three surfaces rather than your shop.\n\n### Selling, sharing, and Global Privacy Control\n\n**We do not sell personal data, and we do not share it for cross-context behavioural advertising.** There is\nno sale here to opt out of, and no advertising network receives anything from these surfaces.\n\nOur banner is configured to recognise a Global Privacy Control signal as a refusal of the analytics and\nmarketing categories. **Given the defect described above, browser-level or network-level blocking is currently\nthe route that certainly works**, and we would rather tell you that than have you rely on a signal that is\nbeing recorded correctly and acted on late.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://everdemand.co/privacy) sets out the destinations and the safeguards we rely on for each**,\nand you can ask us for a copy of those safeguards.\n\nTwo lists keep this current, and between them they are the authoritative answer:\n\n- **The table in the product-specific section below** names every cookie and similar technology in use on\n this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,\n how long it lasts, and a link to the provider's own notice.\n- **Our Sub-processor List** covers the wider set of providers that process personal data for us, including\n the many that never touch your device at all. You can obtain the current version at any time from\n privacy@ever.co, and it names the sub-processor, what it does, and where it processes.\n\nWe update both when a provider is added, removed or changed. If you find something on our pages that is not\nin either list, tell us at privacy@ever.co — that is a defect and we will fix it.\n\n## Consent, and how to withdraw it\n\n### How the banner works\n\nOn your first visit we show a consent banner, and **nothing in the functional, analytics or marketing\ncategories is written to or read from your device until you have made a choice.** The strictly necessary\nitems load, because the page cannot be delivered otherwise. Everything else waits.\n\nThe first layer of the banner — the one you see without clicking anything further — carries both a\n**Reject all** and an **Accept all** control, presented with equal prominence. **Refusing everything takes\none click, exactly like accepting everything.** Alongside them is a route into per-category choice, so you\ncan accept analytics and refuse marketing, or any other combination.\n\nThree things that some banners do and ours does not:\n\n- **No pre-ticked boxes.** Every category except strictly necessary starts switched off.\n- **Closing the banner is not consent.** Neither is dismissing it, scrolling past it, or carrying on\n browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.\n- **No dark patterns.** We do not make the reject control smaller, greyer, slower or harder to find than the\n accept control, and we do not hide it a layer down.\n\n### Changing your mind\n\n**Withdrawing consent is as easy as giving it, and you can do it at any time.**\n\nThere is a persistent **Cookie preferences** link in the footer of every page, and an equivalent entry\ninside the application's settings. It opens the same per-category controls you saw in the banner, showing\nwhat you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we\nremove what was stored.\n\nTwo honest limits on that:\n\n- **Withdrawal works forwards, not backwards.** It does not make lawful past processing unlawful, and it\n does not reach into data a third-party provider already received. If you want that deleted too, ask us at\n privacy@ever.co and we will tell you who holds it and how to ask them.\n- **Your choice is stored on the device and browser you made it on.** A different browser, a different\n device or a private window will ask again, because there is nothing there to read. Clearing your browser\n storage deletes the record of your refusal as well, which is why the banner reappears afterwards.\n\n### The record we keep\n\nWhen you make a choice we record what you chose, when you chose it, which categories it covered, and which\nversion of this policy was in force at the time. That record exists for two reasons: so that we honour your\nchoice, and so that we can show what you were asked and what you answered.\n\nYou can ask us for a copy of your own consent record at privacy@ever.co.\n\n### How long a choice lasts before we ask again\n\nWe store a consent choice for **six months**. After that the banner appears again so you can confirm or\nchange it. We will also ask again sooner if we add a purpose or a category your earlier choice did not\ncover, or if this policy changes in a way that materially affects what you agreed to.\n\n**This is our own practice, not a legal requirement.** There is no EU-wide statutory interval for asking\nagain — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to\napply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same\nsix months, and blocking storage at the browser level stops the question permanently.\n\n## Controls in your browser and on your device\n\nOur banner is not the only way to control this, and it is not the strongest one. Your browser and your\noperating system can enforce a choice on every site at once, including ours.\n\n### In a browser\n\nEvery major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under\nprivacy or site settings:\n\n- **Delete cookies and site data**, for one site or all of them.\n- **Block cookies**, either all of them or only those set by third parties.\n- **Clear storage on exit**, so nothing survives the session.\n- **Private or incognito windows**, which discard everything when the window closes.\n- **Per-site permissions**, so you can allow storage on the sites you use and block it everywhere else.\n\nYour browser's own help pages describe exactly where these live in your version — we deliberately do not\nreproduce click-by-click instructions here, because they go stale faster than this document does.\n\nContent blockers and privacy extensions work on our sites too. **Using one is a legitimate choice**, and we\nbuild the Service so that it keeps working when the optional things are blocked.\n\n### In our desktop and mobile applications\n\nAn installed application has no browser settings to change, so the controls are at the operating-system\nlevel instead:\n\n- Reset or limit the **advertising identifier** your device provides.\n- Answer **no** to the app-tracking permission prompt on iOS, which stops access to that identifier\n entirely.\n- Withdraw **notification permission**, which stops the push token being useful.\n- Clear the application's stored data, or uninstall it, which removes everything it kept locally.\n\nThe **Cookie preferences** controls described above are also available inside the application, and they\ngovern the same categories there as on the website.\n\n### What breaks if you block the strictly necessary ones\n\nBlocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to\nexpect:\n\n- **You will not be able to sign in, or stay signed in.** Authentication needs somewhere to keep the\n session.\n- **Forms may fail their security check** and refuse to submit.\n- **Some features will behave inconsistently**, because requests can no longer be kept on the same server.\n- **We cannot remember that you refused.** The record of your choice is itself stored on your device, so\n blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and\n it comes from the mechanism rather than from us being difficult.\n\n### Do Not Track\n\nBrowsers once offered a **Do Not Track** header, and some still do. **We do not treat it, on its own, as a\nrefusal** — and we would rather explain why than quietly ignore it.\n\nNo consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether\nit expressed a considered decision or a default someone else had set, browsers behaved differently, and\nseveral have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.\n\nUse the banner or the preference centre instead. A choice made there is unambiguous, and we record it.\n\n### Global Privacy Control\n\n**Global Privacy Control (GPC)** is the later, better-specified signal, and unlike Do Not Track it is\ndefined to express an actual opt-out rather than a preference.\n\n**Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing\ncategories** on that browser, and we act on it without waiting for you to interact with a banner.\n\nTwo points of detail:\n\n- It applies to the browser or device sending it. Another browser sends its own signal, or none.\n- **An explicit choice you make later in our preference centre takes precedence**, in either direction. If\n you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as\n such. If you would rather that never happened, leave the categories switched off.\n\n## Changes to this policy\n\nWe update this policy when what we do changes — a provider added or removed, a technology retired, a\ncategory reassigned. Every update gets its own version number and effective date, recorded at the end of\nthis document.\n\n**Where a change materially affects what you agreed to** — a new purpose, a new category, or a tool moving\nout of the strictly necessary or exempt group — **we ask for your consent again rather than relying on the\nchoice you made against the old text.** Corrections, clarifications and provider renames are published with\na new version and no fresh request.\n\nEarlier versions stay available, with the dates each was in force, at\n[https://everdemand.co/cookies](https://everdemand.co/cookies). The effective date shown with this policy tells you which\nversion applies today.\n\n## How to reach us\n\nQuestions about this policy, about anything in the table above, or about a choice you have made — write to\nprivacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent\nrecord, for the current sub-processor list, or to be excluded from our own analytics, and we will do it\nwithout asking why.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\nIf you think we have handled your data badly, tell us first — we would rather fix it. **You can also\ncomplain to a data protection supervisory authority at any time.** Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the Cookie Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://everdemand.co/cookies](https://everdemand.co/cookies)."
|
|
225
|
+
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[everdemand.co](https://everdemand.co) and in Ever Demand — the public website, the documentation,\nthe signed-in application, and any desktop or mobile application we publish for it. The product-specific\nsection below lists what is actually in use on each of those surfaces.\n\nIt sits alongside our [Privacy Policy](https://everdemand.co/privacy). The two documents answer different\nquestions, and it is worth knowing which one you are reading:\n\n- **This policy is about your device.** What we store on it, what we read back from it, why, and how you\n control that.\n- **The [Privacy Policy](https://everdemand.co/privacy) is about the information itself.** What we do with personal\n data once we hold it, the lawful basis for each purpose, who receives it, how long we keep it, and the\n rights you can exercise over it.\n\nWhere something described here involves personal data, the Privacy Policy governs that processing.\n**Nothing in this policy narrows the rights that document gives you.**\n\n### What this policy does not cover\n\n**Other people's sites and services.** Our pages link to third-party sites, and our Service connects to\nthird-party tools when you ask it to. Once you are on someone else's site, their cookie notice applies, not\nours. We have no control over what they store on your device.\n\n**Your own workspace, your own site, your own people.** Where you use the Service as a customer to run\nsomething of your own — a workspace for your organisation, or a site we provision for you — the pages you\npublish and the people you invite are yours. **This policy is not your cookie notice to your own visitors or\npersonnel, and our banner is not your consent mechanism.** Providing those is your responsibility, on your\nown domain, under your own control.\n\n**A copy you run yourself.** Where the software behind the Service is published as open source and you run\nyour own deployment, this policy describes the service *we* operate — not yours. You choose what your\ndeployment loads and what it stores on your users' devices, and only you can describe it to them.\n\n## Cookies and the other technologies that behave like them\n\nA **cookie** is a small text file that a website asks your browser to keep and hands back to a server on\nlater requests. It is the oldest way of doing this, and the best known — but it is only one of several, and\nthe rules that matter here do not turn on which one is used.\n\n**The law we work to attaches to storing information on your device or reading information back from it,\nwhatever the mechanism.** So wherever this policy says \"cookies\", read it as covering all of the following.\n\n### The technologies\n\n- **Cookies** — as above. Set by the site you are visiting, or by another provider whose code runs on the\n page.\n- **Local storage and session storage** — key-value storage inside your browser. Larger than a cookie, not\n sent automatically with every request, and it can hold exactly the same kind of identifier.\n- **IndexedDB and the browser cache** — structured storage and cached files. Ordinarily used to make pages\n load faster and to let parts of the Service work offline, but capable of holding an identifier too.\n- **Pixels, beacons and tags** — a tiny image or a short script whose only job is to load. The act of\n loading it tells the provider that a page was opened, or an email read, along with your IP address and\n browser details. A pixel often stores nothing at all and still reports on you.\n- **Tracking parameters in links** — identifiers added to a URL so that a click can be attributed to the\n campaign or message that produced it.\n- **SDK identifiers in desktop and mobile applications** — an installed application has no cookie jar. It\n stores identifiers in its own application storage instead, and may use identifiers the operating system\n provides: an advertising identifier, an installation identifier, or a push notification token.\n- **Device and network characteristics** — your IP address, screen size, language, time zone, fonts and\n browser version. Individually unremarkable; combined, they can form a **fingerprint** that recognises a\n device without storing anything on it.\n\n### First-party and third-party\n\n**First-party** means we set it, on our own domain, and it goes to our servers.\n\n**Third-party** means it belongs to another company whose code we have chosen to run on the page — an\nanalytics provider, an embedded video player, a bot-protection service. Their technology reports to them,\nnot to us, and they decide what it does. Note the awkward part plainly: **a third-party resource embedded in\nour page discloses your IP address, your browser and the page you were on to that provider, even when it\nstores nothing on your device at all.** Loading it is the disclosure.\n\nSome third-party technologies are deliberately set up to look first-party — served from a subdomain of ours,\nor routed through our own servers. Where we do that, we say so in the table below rather than letting the\nappearance stand.\n\n### Session and persistent\n\n**Session** items are discarded when you close the browser or the application. They are typically what keeps\nyou signed in and moving through a single visit.\n\n**Persistent** items survive until they expire or you delete them, which is what lets us recognise a\nreturning visitor, remember your preferences, or remember that you refused something. Each entry in the\ntable below states how long it lasts.\n\n## Why we use them\n\nThere are six reasons, and each one maps to one of the categories in the next section. We have written the\ncategory next to each so you can see immediately which ones you control.\n\n- **To sign you in and keep you signed in.** Your session has to be attached to the right account, the right\n workspace and the right organisation as you move between pages, and it has to be protected against being\n replayed or forged by someone else. → *strictly necessary*\n- **To keep the Service secure.** Telling a person apart from an abusive script, protecting forms against\n automated submission, enforcing rate limits, and detecting fraudulent sign-ups and payments.\n → *strictly necessary*\n- **To make the Service work at all.** Routing your request to a healthy server, keeping you on the same one\n where a feature requires it, balancing load, and serving the right version of the application.\n → *strictly necessary*\n- **To remember what you decided about cookies.** Your choice has to be stored somewhere, or we would have\n to ask you on every page. → *strictly necessary*\n- **To remember your preferences.** Language, time zone, theme, layout, a panel you collapsed, a message you\n dismissed, and whether you want the support widget open. → *functional*\n- **To understand how the Service is used.** Which pages and features people actually use, which paths fail,\n and where things are slow — so that we improve the right things rather than the ones we happen to notice.\n → *analytics*\n- **To measure our marketing.** Whether a campaign reached anyone, which content leads to sign-ups, and\n which organisations show interest in the product. → *marketing*\n\nTwo things follow from that list, and we would rather state them than leave them implied.\n\n**Only the first four are needed for the Service to function.** Everything in the last three groups is\noptional. If you refuse all of it, every feature you are entitled to still works, at the same price.\n\n**Where we can achieve a purpose without storing anything on your device, we do.** That is the whole reason\nour own analytics is built the way it is — see the section on analytics without consent below.\n\n## The four categories we use\n\nEvery entry in the table below belongs to exactly one of these four categories. The banner and the\npreference centre use the same four names, so what you agree to and what this policy describes are the same\nthing.\n\n### 1. Strictly necessary — no consent, because the Service cannot run without them\n\nThese are the ones we set because you asked for a service that cannot be delivered otherwise. They are not\noptional, they are not used for analytics or marketing, and there is no switch for them in the preference\ncentre. If you block them at the browser level, parts of the Service will stop working.\n\n- **Session and authentication** — signing you in, keeping you signed in, refreshing your session, and\n binding it to the correct account, workspace and organisation.\n- **Security** — protection against cross-site request forgery, detection of abusive automated traffic, rate\n limiting, and fraud prevention on sign-up and payment.\n- **Load balancing and routing** — sending your request to a healthy server and keeping you there where a\n feature needs it.\n- **Your consent choice** — storing what you decided, so that we can honour it and stop asking.\n\nError and crash diagnostics are **not** in this category by default. Where we use a diagnostics tool that\nrecords more than a technical error — a reconstruction of what was on your screen, for example — it is\nlisted under analytics and it waits for your consent.\n\n#### reCAPTCHA is in this category, and here is our reasoning\n\nWe use Google reCAPTCHA — and on some surfaces an alternative provider, named in the table below — to stop\nautomated abuse of forms such as sign-up, password reset and contact. **We treat it as strictly necessary,\nwhich means it loads without asking you first.**\n\nThe reason is that it protects the specific form you are trying to use. You cannot meaningfully ask for the\nform and refuse the protection on it: without it, those endpoints are abused within hours, which is a\nsecurity failure that harms you as much as us.\n\nWhat that means in practice, stated plainly:\n\n- It collects device and behaviour signals from your browser — mouse and touch movement, timing, browser and\n device characteristics, and your IP address — and **sends them to Google, which acts as its own controller\n for that data under its own privacy notice.**\n- We load it only on pages carrying a protected form. It is not present across the whole site.\n- Where an equivalent provider is available on a surface, we prefer the one that collects less.\n\n**Not every data protection authority accepts that a bot-protection service belongs in the strictly\nnecessary category.** We think it does, for the reason above, and we would rather publish the reasoning and\nlet you judge it than bury the tool in a list. If you would prefer not to submit a form protected this way,\nwrite to privacy@ever.co and we will take it from you another way.\n\n### 2. Functional and preferences — consent required\n\nThese remember choices you have made so that the Service behaves the way you left it: language, time zone,\ntheme, layout, dismissed messages, and support or chat widgets where we offer them.\n\n**Refusing this category costs you convenience, not access.** Everything still works; it simply forgets your\npreferences between visits and you set them again.\n\n### 3. Analytics — consent required\n\nThese tell us how the Service is used: which pages and features are used, which paths people abandon, what\nis slow, and what fails. Depending on the surface this may include a provider's own persistent identifier\nand, where the table says so, a masked reconstruction of a session.\n\nThird-party analytics tools are **off until you turn them on**, and nothing in this category loads before you\nchoose.\n\nThere is one deliberate exception, and it is the subject of the next section: **our own analytics, running on\nour own servers, is designed to operate without a consent requirement** — cookieless, with no persistent\nidentifier and aggregate reporting only. The next section sets out exactly what that involves and the\nconditions it depends on.\n\n### 4. Marketing — consent required\n\nThese measure whether our marketing works and help us understand who is interested in the product:\nattribution of a sign-up to the campaign that produced it, and business-audience identification tools.\n\nOne of these deserves a plain sentence rather than a euphemism. **Visitor identification tools resolve a\nvisitor's IP address to the organisation it belongs to, so that we can see which companies have looked at\nthe product.** They do not tell us your name, but most people do not expect a website to work out their\nemployer, so we would rather say it here than let you find it in a table. It is off unless you consent.\n\n### No cookie walls, ever\n\n**We do not use cookie walls, and we never make access conditional on consenting to non-essential cookies.**\n\nYou can refuse everything except the strictly necessary category and the whole of the Service remains\navailable to you — the same features, the same content, the same price. We do not offer a \"consent or pay\"\nalternative. We do not degrade the experience, hide content, or nag you on every page because you said no.\nRefusing is a decision we record and respect, not a negotiating position.\n\n## Our own analytics, and why it runs without asking you\n\nWe want to know whether the Service works — which pages load, which fail, whether a change made things\nbetter or worse. That is a legitimate thing for us to want, and it is also the reason most websites hand\ntheir visitors to a third-party analytics company. **We built ours the other way round: we run our own\nanalytics software, on our own servers, in our own infrastructure, and it is designed so that there is\nnothing about you worth asking permission for.** No third-party analytics vendor receives this data. The\ntable below names the software and where it runs.\n\n### What it does, and what it deliberately does not do\n\n- **It sets no cookies.** Nothing is written to your device — no cookie, no local storage entry, nothing.\n- **It creates no persistent identifier.** There is no visitor ID that follows you from one day to the next.\n- **It does not track you across sites or across devices.** It measures our own site only. It has no\n presence anywhere else, so there is nothing to join up.\n- **It counts visits using a hash that is salted and rotated daily.** A one-way value is derived from your\n IP address and browser details together with a secret salt, purely to tell one visit apart from another\n within a single day. **We change the salt every day, which breaks the link between today's value and\n tomorrow's by design.** The inputs are not stored.\n- **It reports only in aggregate** — page counts, referrers, countries, browsers. No profile of you, no\n individual visitor record to open, nothing to hand to a marketing tool.\n- **It keeps data for a bounded period,** stated in the table below, after which the underlying records go\n and only aggregate statistics remain.\n- **It is never used for advertising,** and the data is not sold, shared for anyone else's purposes, or\n combined with data from another source.\n\n### Why this can run without consent, and the condition attached\n\nUnder the ePrivacy rules, storing information on your device or reading it back generally requires your\nprior consent, with a narrow exemption for what is strictly necessary. European regulators — the French CNIL\nmost explicitly — have also published criteria under which a first-party audience-measurement tool can be\ntreated as exempt: it must serve only the operator's own site, produce only aggregate statistics, avoid\ncross-site and cross-device tracking, avoid a persistent identifier, and keep data for a limited period.\n\n**Our configuration is built to meet those criteria. That is the whole basis on which it runs without\nasking you — and it is conditional on every one of the measures listed above.**\n\nWe are not claiming a general permission. If we ever changed any of it — a persistent identifier, a fixed\nsalt, measurement across more than one of our own sites, a third-party vendor, reporting at the level of an\nindividual visitor — **the exemption would no longer apply, and we would move this tool into the analytics\ncategory and ask for your consent before making the change.** The category is a configuration setting in our\nconsent system, not a paragraph in this document, precisely so that it can be changed the moment the facts\nchange.\n\nOne further distinction worth being precise about. The exemption above is about **storage on your device**.\nWhere the resulting data is still personal data, the separate question of a lawful basis under data\nprotection law arises, and ours is our legitimate interest in understanding whether our own service works —\nassessed against the fact that the measurement is aggregate, short-lived and cannot be traced back to you.\n**You can object to that processing**, and the paragraph below is how.\n\n### You can switch it off anyway\n\nYou do not have to accept our reasoning to escape the measurement.\n\n- Open **Cookie preferences** from the footer of any page. Our own analytics appears there with a switch,\n even though it runs without consent, and turning it off stops it.\n- Blocking it at the browser or network level also works, and we do not try to detect or defeat that.\n- Or write to privacy@ever.co and ask us to exclude you.\n\n**We do not ask for a reason and we do not require an account.**\n\n### Separately, and only with your consent, we also use third-party tools\n\nAlongside our own analytics we use third-party analytics and marketing products. Those are a genuinely\ndifferent proposition: another company receives the data, they typically use a persistent identifier of\ntheir own, and some are capable of following a visitor across other sites entirely.\n\n**Nothing in that group runs until you consent to it**, and none of it is covered by the exemption described\nabove. Each tool is named in the table below, with what it does, who operates it, and how long anything it\nstores lasts.\n\n## Annex: Ever Demand — what runs on each surface\n\n### Where this policy applies, and where it does not\n\nWe operate three things under this name, and this policy covers all three and nothing else:\n\n- the website at [everdemand.co](https://everdemand.co);\n- the documentation site at [docs.everdemand.co](https://docs.everdemand.co); and\n- the content management system behind the website, which only our own editors sign in to.\n\n**There is no hosted Ever Demand platform.** No shopping site, merchant console, administration console\nor courier application is operated by us at any address, so there is no application surface here for this\npolicy to describe.\n\n**A deployment somebody else runs is not covered.** The shopping site a business built on this software sets\nits own cookies, on its own domain, under its own notice. The section near the end says what the software\nstores in a browser and on a device, so that an operator can write that notice from facts rather than\nguesswork — but it is that operator's notice to write, and ours does not do the job for them.\n\n### 1. The website at [everdemand.co](https://everdemand.co)\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Edge, routing and bot-filtering cookies | Cloudflare | Strictly necessary | Not required | Getting your request to the site, absorbing attack traffic, telling a person apart from a hostile script |\n| Consent record (`cg_consent`) | Us — first-party | Strictly necessary | Not required | Storing what you chose, so we can honour it and stop asking |\n| reCAPTCHA | Google | Strictly necessary | Not required | Stopping automated abuse of the contact, pricing-notification and newsletter forms. Read the next section — on the current build it loads on every page, not only on the ones carrying a form |\n| Google Analytics 4, delivered through a tag container | Google | Analytics | Required | Which pages and campaigns bring people to the site, and where people give up |\n| Product analytics | PostHog | Analytics | Required | Page views and events, on the environments where a key is configured |\n| Business visitor identification | Leadfeeder | Marketing | Required | Resolving your IP address to the organisation it belongs to, so that we can see which companies have looked at the product |\n\n**The last three rows say \"required\" because that is what this site is meant to do.** The next section is\nabout the fact that today it does not.\n\n### The defect on this site, named rather than left for you to find\n\n**On the build of [everdemand.co](https://everdemand.co) running as this policy is published, the consent\nbanner does not gate the analytics and marketing tools.** The tag container and the visitor-identification\nscript are loaded as ordinary page scripts sitting alongside the banner rather than behind it. Nothing\nlistens for your decision, and nothing is held back by it, so they run when the page loads whatever you\nchoose.\n\n**Two smaller things follow from the same mistake.** reCAPTCHA loads on every page of this site rather than\nonly on the pages carrying a protected form, which is narrower than the commitment made in the section above.\nAnd the consent record is stored, so your choice is captured accurately — it simply is not acted on.\n\nWe are not going to write this up as policy and hope you do not check. **The table above is what this site is\nsupposed to do, and what it will do once those scripts are moved behind the consent decision**, which is how\nour other sites already work. Until that ships:\n\n- **Blocking these tools in your browser or at the network level works**, and we do not try to detect or\n defeat it.\n- Writing to privacy@ever.co and asking to be excluded also works. We do not ask for a reason and we do\n not require an account.\n- If you have already loaded the site and want what was collected removed, the same address is the route, and\n you do not have to explain yourself.\n\n### Things on this site that are not cookies but are still disclosures\n\nNone of these stores anything on your device. Each of them still sends something about you to somebody else,\nso naming them is the point.\n\n- **Error monitoring.** When a page fails, a report goes to Sentry carrying your IP address, your browser, the\n page you were on and the context around the failure. It runs on all three surfaces and it is not waiting for\n a consent choice, because it is not measuring you — it exists so that a fault is visible to us with enough\n detail to fix it. **We do not run session replay or screen reconstruction on any of these surfaces.** If you\n would rather not be in those reports, privacy@ever.co will exclude you.\n- **Sending us a form.** Using the contact form or the pricing-notification form sends what you wrote through\n Postmark, which delivers the email to us.\n- **Subscribing.** Joining the newsletter sends your address to Mailchimp, which holds the list.\n- **Opening the chat.** The support chat widget is Chatwoot, and it starts a conversation record — your\n message, your page, your IP address — when you open it, not before.\n\n### 2. The documentation site\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Not required | Routing and filtering, as above |\n| Theme and navigation preferences, held in your browser's local storage | Us | Functional | Required | Remembering dark mode and which sections you collapsed |\n| Documentation search | Algolia | Functional | Required | Searching the documentation, where the search keys are configured for that site. **Where they are not, search runs entirely in your browser and sends nothing to anyone** |\n\nThere is no analytics and no marketing tool on the documentation site.\n\n### 3. The content management system\n\nThis is a staff surface. A visitor to the public website never reaches it, and nothing about you as a reader\nis processed there.\n\n| Technology | Provider | Category | Consent | What it is for |\n|---|---|---|---|---|\n| Session and sign-in cookies | Us | Strictly necessary | Not required | Signing an editor in and keeping them signed in |\n| Cross-site request forgery token | Us | Strictly necessary | Not required | Stopping another site submitting a request as a signed-in editor |\n| Edge and security cookies | Cloudflare | Strictly necessary | Not required | Routing and filtering, as above |\n\nNo analytics, no marketing tools, no third-party measurement of any kind.\n\n### Our own analytics does not run here\n\nThe section above describes audience measurement we run on our own servers, cookieless and without a\npersistent identifier, and explains why it does not need to ask you. **None of it is deployed on these three\nsurfaces.** The only audience measurement on this product's website is Google's, and it belongs in the\nanalytics category where consent is required. The exemption described earlier is not doing any work here, and\nwe would rather say so than let you assume the gentler arrangement applies.\n\n### The mobile applications need a different section, because cookies are the wrong word\n\nThe shopping, merchant and courier applications are not browsers. What they hold is device identifiers rather\nthan cookies, and the operator who publishes a build decides all of it:\n\n- **A device record** — a device identifier, the platform, the language and a push channel identifier — is\n created so that the platform can send an order or an invite to the right handset.\n- **Sign-in state is held on the device**, in application storage rather than in a cookie. The website leg of\n social sign-in uses a server-side session cookie.\n- **Google Analytics, Mixpanel and Intercom are compiled into all three applications**, including the courier\n application, and the courier build additionally carries a plugin that reads a unique device identifier. Each\n of these is inert until the operator supplies a key and ships a build containing it.\n\n**Analytics inside a worker's application is a harder problem than analytics in a shopper's application, and\nit should not be treated as the same decision.** A shopper can uninstall. A courier who was given the\napplication to do a job cannot, and an in-app tracking prompt put in front of someone whose employer issued\nthe device is not a free choice. An operator switching those keys on for the courier build is measuring a\nworker, and the acceptable use annex to this product says what that requires.\n\nApp-store privacy labels and the operating system's own tracking prompt belong to whoever publishes the\nbuild. **That is the operator, not us.**\n\n### If you run the software yourself\n\nThe platform stores a signed access token and interface state in the browser or the application, and sets a\nserver-side session cookie on the social sign-in legs. Beyond that, **every tracker in a deployment is one the\noperator added**: the maps key, the analytics keys, any tag you drop into the shopping site, and anything your\nown marketing team wants.\n\nYour cookie notice, your banner and your consent record are yours. The legal pages bundled inside the software\nare not a consent mechanism and were never one, and ours governs our three surfaces rather than your shop.\n\n### Selling, sharing, and Global Privacy Control\n\n**We do not sell personal data, and we do not share it for cross-context behavioural advertising.** There is\nno sale here to opt out of, and no advertising network receives anything from these surfaces.\n\nOur banner is configured to recognise a Global Privacy Control signal as a refusal of the analytics and\nmarketing categories. **Given the defect described above, browser-level or network-level blocking is currently\nthe route that certainly works**, and we would rather tell you that than have you rely on a signal that is\nbeing recorded correctly and acted on late.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n#### Measurement injected by that layer, which our banner cannot control\n\nThere is one thing here we would rather state plainly than have you discover in a network trace. **Our\ncontent delivery provider injects its own lightweight measurement script at the edge — into the response,\nafter it leaves our servers.** It is not in our code, our consent system never sees it, and **switching a\ncategory off in our preference centre does not stop it**, because by the time the page reaches you the\nscript is already part of it.\n\nWhat it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent\nidentifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to\nanything else we hold.\n\nWhat it is not: covered by the exemption we claim for our own analytics. That argument rests on the data\nstaying on our own infrastructure, and this is a third party receiving it. **We are not going to stretch\nthe same reasoning over both.**\n\nIf you would rather it did not run, a content blocker or a network-level block stops it, and we do not\nattempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the\ncurrent provider and exactly what it collects.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://everdemand.co/privacy) sets out the destinations and the safeguards we rely on for each**,\nand you can ask us for a copy of those safeguards.\n\nTwo lists keep this current, and between them they are the authoritative answer:\n\n- **The table in the product-specific section below** names every cookie and similar technology in use on\n this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,\n how long it lasts, and a link to the provider's own notice.\n- **Our Sub-processor List** covers the wider set of providers that process personal data for us, including\n the many that never touch your device at all. You can obtain the current version at any time from\n privacy@ever.co, and it names the sub-processor, what it does, and where it processes.\n\nWe update both when a provider is added, removed or changed. If you find something on our pages that is not\nin either list, tell us at privacy@ever.co — that is a defect and we will fix it.\n\n## Consent, and how to withdraw it\n\n### How the banner works\n\nOn your first visit we show a consent banner, and **nothing in the functional, analytics or marketing\ncategories is written to or read from your device until you have made a choice.** The strictly necessary\nitems load, because the page cannot be delivered otherwise. Everything else waits.\n\nThe first layer of the banner — the one you see without clicking anything further — carries both a\n**Reject all** and an **Accept all** control, presented with equal prominence. **Refusing everything takes\none click, exactly like accepting everything.** Alongside them is a route into per-category choice, so you\ncan accept analytics and refuse marketing, or any other combination.\n\nThree things that some banners do and ours does not:\n\n- **No pre-ticked boxes.** Every category except strictly necessary starts switched off.\n- **Closing the banner is not consent.** Neither is dismissing it, scrolling past it, or carrying on\n browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.\n- **No dark patterns.** We do not make the reject control smaller, greyer, slower or harder to find than the\n accept control, and we do not hide it a layer down.\n\n### Changing your mind\n\n**Withdrawing consent is as easy as giving it, and you can do it at any time.**\n\nThere is a persistent **Cookie preferences** link in the footer of every page, and an equivalent entry\ninside the application's settings. It opens the same per-category controls you saw in the banner, showing\nwhat you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we\nremove what was stored.\n\nTwo honest limits on that:\n\n- **Withdrawal works forwards, not backwards.** It does not make lawful past processing unlawful, and it\n does not reach into data a third-party provider already received. If you want that deleted too, ask us at\n privacy@ever.co and we will tell you who holds it and how to ask them.\n- **Your choice is stored on the device and browser you made it on.** A different browser, a different\n device or a private window will ask again, because there is nothing there to read. Clearing your browser\n storage deletes the record of your refusal as well, which is why the banner reappears afterwards.\n\n### The record we keep\n\nWhen you make a choice we record what you chose, when you chose it, which categories it covered, and which\nversion of this policy was in force at the time. That record exists for two reasons: so that we honour your\nchoice, and so that we can show what you were asked and what you answered.\n\nYou can ask us for a copy of your own consent record at privacy@ever.co.\n\n### How long a choice lasts before we ask again\n\nWe store a consent choice for **six months**. After that the banner appears again so you can confirm or\nchange it. We will also ask again sooner if we add a purpose or a category your earlier choice did not\ncover, or if this policy changes in a way that materially affects what you agreed to.\n\n**This is our own practice, not a legal requirement.** There is no EU-wide statutory interval for asking\nagain — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to\napply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same\nsix months, and blocking storage at the browser level stops the question permanently.\n\n## Controls in your browser and on your device\n\nOur banner is not the only way to control this, and it is not the strongest one. Your browser and your\noperating system can enforce a choice on every site at once, including ours.\n\n### In a browser\n\nEvery major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under\nprivacy or site settings:\n\n- **Delete cookies and site data**, for one site or all of them.\n- **Block cookies**, either all of them or only those set by third parties.\n- **Clear storage on exit**, so nothing survives the session.\n- **Private or incognito windows**, which discard everything when the window closes.\n- **Per-site permissions**, so you can allow storage on the sites you use and block it everywhere else.\n\nYour browser's own help pages describe exactly where these live in your version — we deliberately do not\nreproduce click-by-click instructions here, because they go stale faster than this document does.\n\nContent blockers and privacy extensions work on our sites too. **Using one is a legitimate choice**, and we\nbuild the Service so that it keeps working when the optional things are blocked.\n\n### In our desktop and mobile applications\n\nAn installed application has no browser settings to change, so the controls are at the operating-system\nlevel instead:\n\n- Reset or limit the **advertising identifier** your device provides.\n- Answer **no** to the app-tracking permission prompt on iOS, which stops access to that identifier\n entirely.\n- Withdraw **notification permission**, which stops the push token being useful.\n- Clear the application's stored data, or uninstall it, which removes everything it kept locally.\n\nThe **Cookie preferences** controls described above are also available inside the application, and they\ngovern the same categories there as on the website.\n\n### What breaks if you block the strictly necessary ones\n\nBlocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to\nexpect:\n\n- **You will not be able to sign in, or stay signed in.** Authentication needs somewhere to keep the\n session.\n- **Forms may fail their security check** and refuse to submit.\n- **Some features will behave inconsistently**, because requests can no longer be kept on the same server.\n- **We cannot remember that you refused.** The record of your choice is itself stored on your device, so\n blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and\n it comes from the mechanism rather than from us being difficult.\n\n### Do Not Track\n\nBrowsers once offered a **Do Not Track** header, and some still do. **We do not treat it, on its own, as a\nrefusal** — and we would rather explain why than quietly ignore it.\n\nNo consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether\nit expressed a considered decision or a default someone else had set, browsers behaved differently, and\nseveral have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.\n\nUse the banner or the preference centre instead. A choice made there is unambiguous, and we record it.\n\n### Global Privacy Control\n\n**Global Privacy Control (GPC)** is the later, better-specified signal, and unlike Do Not Track it is\ndefined to express an actual opt-out rather than a preference.\n\n**Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing\ncategories** on that browser, and we act on it without waiting for you to interact with a banner.\n\nTwo points of detail:\n\n- It applies to the browser or device sending it. Another browser sends its own signal, or none.\n- **An explicit choice you make later in our preference centre takes precedence**, in either direction. If\n you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as\n such. If you would rather that never happened, leave the categories switched off.\n\n## Changes to this policy\n\nWe update this policy when what we do changes — a provider added or removed, a technology retired, a\ncategory reassigned. Every update gets its own version number and effective date, recorded at the end of\nthis document.\n\n**Where a change materially affects what you agreed to** — a new purpose, a new category, or a tool moving\nout of the strictly necessary or exempt group — **we ask for your consent again rather than relying on the\nchoice you made against the old text.** Corrections, clarifications and provider renames are published with\na new version and no fresh request.\n\nEarlier versions stay available, with the dates each was in force, at\n[https://everdemand.co/cookies](https://everdemand.co/cookies). The effective date shown with this policy tells you which\nversion applies today.\n\n## How to reach us\n\nQuestions about this policy, about anything in the table above, or about a choice you have made — write to\nprivacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent\nrecord, for the current sub-processor list, or to be excluded from our own analytics, and we will do it\nwithout asking why.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\nIf you think we have handled your data badly, tell us first — we would rather fix it. **You can also\ncomplain to a data protection supervisory authority at any time.** Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the Cookie Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://everdemand.co/cookies](https://everdemand.co/cookies)."
|
|
226
226
|
}
|
|
@@ -242,8 +242,8 @@ products and every one of them waits for your consent.</p>
|
|
|
242
242
|
</thead>
|
|
243
243
|
<tbody>
|
|
244
244
|
<tr>
|
|
245
|
-
<td>Consent record</td>
|
|
246
|
-
<td>
|
|
245
|
+
<td>Consent record (<code>cg_consent</code>)</td>
|
|
246
|
+
<td>Us — first-party, stored on your device only</td>
|
|
247
247
|
<td>Strictly necessary</td>
|
|
248
248
|
<td>Stores what you chose in the banner so we can honour it and stop asking</td>
|
|
249
249
|
<td>Up to 12 months, or until you clear it</td>
|
|
@@ -415,6 +415,21 @@ absorbs attacks and filters hostile traffic — along with bot protection on for
|
|
|
415
415
|
payment. These see connection metadata and may set their own security cookies.</p>
|
|
416
416
|
<p><strong>Strictly necessary</strong>, and therefore not consent-gated. Our reasoning for putting bot protection in that
|
|
417
417
|
category, including what it sends to its provider, is set out in the categories section above.</p>
|
|
418
|
+
<h4 id="measurement-injected-by-that-layer-which-our-banner-cannot-control" tabindex="-1">Measurement injected by that layer, which our banner cannot control</h4>
|
|
419
|
+
<p>There is one thing here we would rather state plainly than have you discover in a network trace. <strong>Our
|
|
420
|
+
content delivery provider injects its own lightweight measurement script at the edge — into the response,
|
|
421
|
+
after it leaves our servers.</strong> It is not in our code, our consent system never sees it, and <strong>switching a
|
|
422
|
+
category off in our preference centre does not stop it</strong>, because by the time the page reaches you the
|
|
423
|
+
script is already part of it.</p>
|
|
424
|
+
<p>What it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent
|
|
425
|
+
identifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to
|
|
426
|
+
anything else we hold.</p>
|
|
427
|
+
<p>What it is not: covered by the exemption we claim for our own analytics. That argument rests on the data
|
|
428
|
+
staying on our own infrastructure, and this is a third party receiving it. <strong>We are not going to stretch
|
|
429
|
+
the same reasoning over both.</strong></p>
|
|
430
|
+
<p>If you would rather it did not run, a content blocker or a network-level block stops it, and we do not
|
|
431
|
+
attempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the
|
|
432
|
+
current provider and exactly what it collects.</p>
|
|
418
433
|
<h3 id="where-these-providers-are-and-where-to-find-the-full-list" tabindex="-1">Where these providers are, and where to find the full list</h3>
|
|
419
434
|
<p>Some of these providers are established outside the European Economic Area, and using them involves an
|
|
420
435
|
international transfer of personal data. <strong>The transfers section of our
|
|
@@ -559,6 +574,6 @@ complain to a data protection supervisory authority at any time.</strong> Ours i
|
|
|
559
574
|
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
560
575
|
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
561
576
|
to the authority for the country where you live or work.</p>
|
|
562
|
-
<p>This document is version 1.0.
|
|
577
|
+
<p>This document is version 1.0.2 of the Cookie Policy for
|
|
563
578
|
<a href="https://rec.so">rec.so</a>, in force from 2026-08-02. Earlier versions, with the dates
|
|
564
579
|
they applied, are at <a href="https://rec.so/cookies">https://rec.so/cookies</a>.</p>
|