@ever-co/legal 0.1.2 → 0.2.0
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-async/en.html +778 -0
- package/dist/content/aup/ever-async/en.json +343 -0
- package/dist/content/aup/hust/en.html +9 -0
- package/dist/content/aup/hust/en.json +2 -2
- package/dist/content/cookies/ever-async/en.html +457 -0
- package/dist/content/cookies/ever-async/en.json +185 -0
- package/dist/content/cookies/ever-demand/en.html +5 -2
- package/dist/content/cookies/ever-demand/en.json +2 -2
- package/dist/content/cookies/ever-rec/en.html +5 -2
- package/dist/content/cookies/ever-rec/en.json +2 -2
- package/dist/content/cookies/ever-teams/en.html +5 -2
- package/dist/content/cookies/ever-teams/en.json +2 -2
- package/dist/content/cookies/ever-works/en.html +5 -2
- package/dist/content/cookies/ever-works/en.json +2 -2
- package/dist/content/cookies/gauzy/en.html +5 -2
- package/dist/content/cookies/gauzy/en.json +2 -2
- package/dist/content/cookies/githands/en.html +5 -2
- package/dist/content/cookies/githands/en.json +2 -2
- package/dist/content/cookies/hust/en.html +5 -2
- package/dist/content/cookies/hust/en.json +2 -2
- package/dist/content/dpa/ever-async/en.html +1848 -0
- package/dist/content/dpa/ever-async/en.json +640 -0
- package/dist/content/privacy/ever-async/en.html +1350 -0
- package/dist/content/privacy/ever-async/en.json +364 -0
- package/dist/content/privacy/ever-corporate/en.html +86 -3
- package/dist/content/privacy/ever-corporate/en.json +2 -2
- package/dist/content/privacy/ever-demand/en.html +99 -2
- package/dist/content/privacy/ever-demand/en.json +2 -2
- package/dist/content/privacy/ever-rec/en.html +110 -3
- package/dist/content/privacy/ever-rec/en.json +2 -2
- package/dist/content/privacy/ever-teams/en.html +97 -1
- package/dist/content/privacy/ever-teams/en.json +2 -2
- package/dist/content/privacy/ever-tech/en.html +86 -3
- package/dist/content/privacy/ever-tech/en.json +2 -2
- package/dist/content/privacy/ever-works/en.html +74 -5
- package/dist/content/privacy/ever-works/en.json +2 -2
- package/dist/content/privacy/everiq/en.html +107 -0
- package/dist/content/privacy/everiq/en.json +2 -2
- package/dist/content/privacy/gauzy/en.html +88 -3
- package/dist/content/privacy/gauzy/en.json +2 -2
- package/dist/content/privacy/githands/en.html +83 -2
- package/dist/content/privacy/githands/en.json +2 -2
- package/dist/content/privacy/hust/en.html +186 -37
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +93 -0
- package/dist/content/privacy/traduora/en.json +2 -2
- package/dist/content/refund/ever-rec/en.html +595 -0
- package/dist/content/refund/ever-rec/en.json +336 -0
- package/dist/content/security/ever-async/en.html +853 -0
- package/dist/content/security/ever-async/en.json +417 -0
- package/dist/content/subprocessors/ever-async/en.html +852 -0
- package/dist/content/subprocessors/ever-async/en.json +166 -0
- package/dist/content/subprocessors/ever-corporate/en.html +403 -9
- package/dist/content/subprocessors/ever-corporate/en.json +6 -2
- package/dist/content/subprocessors/ever-demand/en.html +443 -13
- package/dist/content/subprocessors/ever-demand/en.json +6 -2
- package/dist/content/subprocessors/ever-rec/en.html +493 -10
- package/dist/content/subprocessors/ever-rec/en.json +6 -2
- package/dist/content/subprocessors/ever-teams/en.html +435 -8
- package/dist/content/subprocessors/ever-teams/en.json +6 -2
- package/dist/content/subprocessors/ever-tech/en.html +443 -9
- package/dist/content/subprocessors/ever-tech/en.json +6 -2
- package/dist/content/subprocessors/ever-works/en.html +354 -13
- package/dist/content/subprocessors/ever-works/en.json +6 -2
- package/dist/content/subprocessors/everiq/en.html +484 -3
- package/dist/content/subprocessors/everiq/en.json +6 -2
- package/dist/content/subprocessors/gauzy/en.html +353 -20
- package/dist/content/subprocessors/gauzy/en.json +6 -2
- package/dist/content/subprocessors/githands/en.html +451 -13
- package/dist/content/subprocessors/githands/en.json +6 -2
- package/dist/content/subprocessors/hust/en.html +502 -12
- package/dist/content/subprocessors/hust/en.json +14 -2
- package/dist/content/subprocessors/traduora/en.html +461 -4
- package/dist/content/subprocessors/traduora/en.json +6 -2
- package/dist/content/tos/ever-async/en.html +1350 -0
- package/dist/content/tos/ever-async/en.json +687 -0
- package/dist/content/tos/ever-rec/en.html +40 -11
- package/dist/content/tos/ever-rec/en.json +5 -5
- package/dist/content/tos/hust/en.html +32 -8
- package/dist/content/tos/hust/en.json +10 -2
- package/dist/index.json +5338 -2148
- package/package.json +1 -1
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"locale": "en",
|
|
9
9
|
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "1388564cc566f6d3e748475a8dee74935236540f1270dea4091910d01d56ba70",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/cookies/010-scope",
|
|
@@ -198,5 +198,5 @@
|
|
|
198
198
|
}
|
|
199
199
|
],
|
|
200
200
|
"path": "content/cookies/ever-works/en.html",
|
|
201
|
-
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[ever.works](https://ever.works) and in Ever Works Cloud — 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.works/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.works/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## Ever Works: what is on each surface\n\nEver Works has four surfaces and they genuinely differ, so they are listed separately rather than\nmerged into one table you would have to filter in your head.\n\n**Everything below in the functional, analytics or marketing categories waits for your consent.** Only the\nstrictly necessary rows load without it. If you ever see one of the others running before you have chosen,\nthat is a defect rather than a policy — tell us at privacy@ever.co and we will fix it.\n\n### 1. The website at [ever.works](https://ever.works)\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Routing the request, absorbing attacks, telling a person apart from a hostile script | Session to 1 year, depending on the cookie |\n| reCAPTCHA | Google | Strictly necessary | Stopping automated abuse of the contact and newsletter forms. Loads only on pages carrying one | Session to 6 months |\n| Consent record | Us | Strictly necessary | Remembering what you chose here | 6 months |\n| Google Analytics 4, delivered through Google Tag Manager | Google | Analytics | Which pages and campaigns bring people to the site | Up to 2 years |\n| Product analytics | PostHog | Analytics | Which pages are read and which paths are abandoned | Up to 1 year |\n\nTwo things on this surface that are not cookies but are still disclosures. **Subscribing to the newsletter\nsends your address to Mailchimp**, which holds the list. **Writing to us through the contact form sends\nyour message through Postmark**, which delivers it. Neither happens unless you use the form.\n\n### 2. The application — app, api, admin and mcp at ever.works\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Session and refresh cookies | Us | Strictly necessary | Signing you in and keeping you signed in against the right account and Work | Session, refreshed while you are active |\n| Cross-site request forgery token | Us | Strictly necessary | Stopping another site submitting a request as you | Session |\n| Turnstile | Cloudflare | Strictly necessary | The anti-bot check on registration and onboarding. Loads only on those pages | Session to 30 minutes |\n| Edge and security cookies | Cloudflare | Strictly necessary | As above | Session to 1 year |\n| Language and interface preferences | Us | Functional | Keeping the language and layout you chose | Up to 1 year |\n| Product analytics with interaction capture and **session recording** | PostHog | Analytics | Measuring how the application is used, and reconstructing a session — with form inputs masked — when something goes wrong. Stored in both a cookie and browser local storage, and tied to your account identifier, email address and name once you are signed in | Up to 1 year |\n\n**One third-party fetch happens on the sign-in and registration pages before you have an account or a\nconsent choice.** The animation on those pages loads a WebAssembly file from a public content delivery\nnetwork — jsDelivr, falling back to unpkg. Nothing is stored on your device by it, but **the request itself\ndiscloses your IP address, your browser and the page you are on to that network.** There is no way to fetch\na file from somebody else's network and hide the request for it, so we name it here rather than let you\nfind it. We would prefer to serve the file ourselves and intend to.\n\n### 3. The documentation sites\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Theme and sidebar preferences | Us | Functional | Remembering dark mode and which sections you collapsed | Up to 1 year |\n| Webfont fetched at page load | Google | Strictly necessary for the page to render as designed | The documentation loads its typeface from Google when the page opens, so **your browser contacts Google directly and discloses your IP address, browser and the page you are reading.** Nothing is stored on your device | Not stored |\n| Documentation search | Algolia | Functional | Searching the documentation, where search is configured on that site | Session |\n\nThe application and the sites we provision do **not** do this — they build the typeface into the page and\nserve it themselves, so no request reaches Google.\n\n### 4. Sites we provision for customers\n\n**This policy does not govern a Work site.** The operator of that site is responsible for its own cookie\nnotice and its own consent mechanism, on its own domain. This section exists for two reasons: so that a\nvisitor can see what the software is capable of, and so that a Work Owner can start from a real list\ninstead of guessing.\n\nTwo things run on a provisioned site because we put them there:\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Traffic to a Work site reaches it through our proxy | Session to 1 year |\n| Viewer identifier | The site | Analytics, first-party | A random value used only to count a listing's unique views once per day. **It deliberately does not store an IP address** | 24 hours |\n\nEverything else is **off until the Work Owner configures a key for it.** Each of these is theirs to\ndisclose and, where it is not strictly necessary, to gate behind consent on their own site:\n\n- **Analytics** — PostHog, including session recording, which the template's configuration enables by\n default once a key is present; Google Analytics, which also reaches google-analytics.com and\n stats.g.doubleclick.net; Plausible; Segment; DataFast; Jitsu; and the hosting provider's own analytics\n and performance measurement where the site is deployed there.\n- **Error reporting** — Sentry in the visitor's browser, **including its own session replay**.\n- **Maps** — Google Maps or Mapbox, loaded when a listing shows a location.\n- **Bot protection** — Google reCAPTCHA on forms.\n- **Payments** — Stripe, Lemon Squeezy, Polar or SolidGate checkout scripts and frames, loaded on the pages\n where a visitor pays.\n- **Language** — a cookie recording the locale a visitor was redirected to.\n\n**A Work Owner who switches any of these on has changed what their visitors must be told and, for the\nnon-necessary ones, must be asked.** Nothing in the product does that for them.\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.works/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.works/cookies](https://ever.works/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.works](https://ever.works), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://ever.works/cookies](https://ever.works/cookies)."
|
|
201
|
+
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[ever.works](https://ever.works) and in Ever Works Cloud — 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.works/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.works/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.\n\nThe software is **Umami**, an open-source analytics package. We run it ourselves on our own hardware in\nthe European Union — we do not use its hosted service, so no third party is involved and there is no\ntransfer to disclose. Naming it matters: the exemption described below depends on how the software is\nconfigured, and you cannot check a claim about software we decline to name.\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## Ever Works: what is on each surface\n\nEver Works has four surfaces and they genuinely differ, so they are listed separately rather than\nmerged into one table you would have to filter in your head.\n\n**Everything below in the functional, analytics or marketing categories waits for your consent.** Only the\nstrictly necessary rows load without it. If you ever see one of the others running before you have chosen,\nthat is a defect rather than a policy — tell us at privacy@ever.co and we will fix it.\n\n### 1. The website at [ever.works](https://ever.works)\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Routing the request, absorbing attacks, telling a person apart from a hostile script | Session to 1 year, depending on the cookie |\n| reCAPTCHA | Google | Strictly necessary | Stopping automated abuse of the contact and newsletter forms. Loads only on pages carrying one | Session to 6 months |\n| Consent record | Us | Strictly necessary | Remembering what you chose here | 6 months |\n| Google Analytics 4, delivered through Google Tag Manager | Google | Analytics | Which pages and campaigns bring people to the site | Up to 2 years |\n| Product analytics | PostHog | Analytics | Which pages are read and which paths are abandoned | Up to 1 year |\n\nTwo things on this surface that are not cookies but are still disclosures. **Subscribing to the newsletter\nsends your address to Mailchimp**, which holds the list. **Writing to us through the contact form sends\nyour message through Postmark**, which delivers it. Neither happens unless you use the form.\n\n### 2. The application — app, api, admin and mcp at ever.works\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Session and refresh cookies | Us | Strictly necessary | Signing you in and keeping you signed in against the right account and Work | Session, refreshed while you are active |\n| Cross-site request forgery token | Us | Strictly necessary | Stopping another site submitting a request as you | Session |\n| Turnstile | Cloudflare | Strictly necessary | The anti-bot check on registration and onboarding. Loads only on those pages | Session to 30 minutes |\n| Edge and security cookies | Cloudflare | Strictly necessary | As above | Session to 1 year |\n| Language and interface preferences | Us | Functional | Keeping the language and layout you chose | Up to 1 year |\n| Product analytics with interaction capture and **session recording** | PostHog | Analytics | Measuring how the application is used, and reconstructing a session — with form inputs masked — when something goes wrong. Stored in both a cookie and browser local storage, and tied to your account identifier, email address and name once you are signed in | Up to 1 year |\n\n**One third-party fetch happens on the sign-in and registration pages before you have an account or a\nconsent choice.** The animation on those pages loads a WebAssembly file from a public content delivery\nnetwork — jsDelivr, falling back to unpkg. Nothing is stored on your device by it, but **the request itself\ndiscloses your IP address, your browser and the page you are on to that network.** There is no way to fetch\na file from somebody else's network and hide the request for it, so we name it here rather than let you\nfind it. We would prefer to serve the file ourselves and intend to.\n\n### 3. The documentation sites\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Theme and sidebar preferences | Us | Functional | Remembering dark mode and which sections you collapsed | Up to 1 year |\n| Webfont fetched at page load | Google | Strictly necessary for the page to render as designed | The documentation loads its typeface from Google when the page opens, so **your browser contacts Google directly and discloses your IP address, browser and the page you are reading.** Nothing is stored on your device | Not stored |\n| Documentation search | Algolia | Functional | Searching the documentation, where search is configured on that site | Session |\n\nThe application and the sites we provision do **not** do this — they build the typeface into the page and\nserve it themselves, so no request reaches Google.\n\n### 4. Sites we provision for customers\n\n**This policy does not govern a Work site.** The operator of that site is responsible for its own cookie\nnotice and its own consent mechanism, on its own domain. This section exists for two reasons: so that a\nvisitor can see what the software is capable of, and so that a Work Owner can start from a real list\ninstead of guessing.\n\nTwo things run on a provisioned site because we put them there:\n\n| Technology | Provider | Category | What it is for | How long |\n|---|---|---|---|---|\n| Edge and security cookies | Cloudflare | Strictly necessary | Traffic to a Work site reaches it through our proxy | Session to 1 year |\n| Viewer identifier | The site | Analytics, first-party | A random value used only to count a listing's unique views once per day. **It deliberately does not store an IP address** | 24 hours |\n\nEverything else is **off until the Work Owner configures a key for it.** Each of these is theirs to\ndisclose and, where it is not strictly necessary, to gate behind consent on their own site:\n\n- **Analytics** — PostHog, including session recording, which the template's configuration enables by\n default once a key is present; Google Analytics, which also reaches google-analytics.com and\n stats.g.doubleclick.net; Plausible; Segment; DataFast; Jitsu; and the hosting provider's own analytics\n and performance measurement where the site is deployed there.\n- **Error reporting** — Sentry in the visitor's browser, **including its own session replay**.\n- **Maps** — Google Maps or Mapbox, loaded when a listing shows a location.\n- **Bot protection** — Google reCAPTCHA on forms.\n- **Payments** — Stripe, Lemon Squeezy, Polar or SolidGate checkout scripts and frames, loaded on the pages\n where a visitor pays.\n- **Language** — a cookie recording the locale a visitor was redirected to.\n\n**A Work Owner who switches any of these on has changed what their visitors must be told and, for the\nnon-necessary ones, must be asked.** Nothing in the product does that for them.\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.works/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.works/cookies](https://ever.works/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.works](https://ever.works), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://ever.works/cookies](https://ever.works/cookies)."
|
|
202
202
|
}
|
|
@@ -168,8 +168,11 @@ Refusing is a decision we record and respect, not a negotiating position.</p>
|
|
|
168
168
|
better or worse. That is a legitimate thing for us to want, and it is also the reason most websites hand
|
|
169
169
|
their visitors to a third-party analytics company. <strong>We built ours the other way round: we run our own
|
|
170
170
|
analytics software, on our own servers, in our own infrastructure, and it is designed so that there is
|
|
171
|
-
nothing about you worth asking permission for.</strong> No third-party analytics vendor receives this data
|
|
172
|
-
|
|
171
|
+
nothing about you worth asking permission for.</strong> No third-party analytics vendor receives this data.</p>
|
|
172
|
+
<p>The software is <strong>Umami</strong>, an open-source analytics package. We run it ourselves on our own hardware in
|
|
173
|
+
the European Union — we do not use its hosted service, so no third party is involved and there is no
|
|
174
|
+
transfer to disclose. Naming it matters: the exemption described below depends on how the software is
|
|
175
|
+
configured, and you cannot check a claim about software we decline to name.</p>
|
|
173
176
|
<h3 id="what-it-does-and-what-it-deliberately-does-not-do" tabindex="-1">What it does, and what it deliberately does not do</h3>
|
|
174
177
|
<ul>
|
|
175
178
|
<li><strong>It sets no cookies.</strong> Nothing is written to your device — no cookie, no local storage entry, nothing.</li>
|
|
@@ -8,7 +8,7 @@
|
|
|
8
8
|
"locale": "en",
|
|
9
9
|
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "bc73eb76cde4f994cadd1bb652d6b6406033e9a167615198c8349c3785736040",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/cookies/010-scope",
|
|
@@ -202,5 +202,5 @@
|
|
|
202
202
|
}
|
|
203
203
|
],
|
|
204
204
|
"path": "content/cookies/gauzy/en.html",
|
|
205
|
-
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[gauzy.co](https://gauzy.co) and in Ever Gauzy Cloud — 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://gauzy.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://gauzy.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 Gauzy\n\n### Where this applies\n\nThis policy covers the gauzy.co website and the web application. **The desktop applications are\na different matter**: they are not browsers and they do not use cookies for tracking. What they capture,\nand what governs it, is set out in the privacy annex for this product rather than here.\n\n### On the website\n\nThe website is where the consent choice is offered. Nothing in the analytics, marketing or preferences\ncategories runs until you have made one.\n\n| Purpose | Category | Consent |\n|---|---|---|\n| Session, sign-in and security | Strictly necessary | Not required |\n| Remembering your cookie choice | Strictly necessary | Not required |\n| Bot and abuse protection on forms | Strictly necessary | Not required |\n| Our own self-hosted analytics | Strictly necessary | Not required — see the core section on analytics without consent |\n| Third-party product and site analytics | Analytics | Required |\n| Tag management | Analytics | Required |\n| Business visitor identification | Marketing | Required |\n| Language and interface preferences | Preferences | Required |\n\n**Business visitor identification deserves naming rather than burying.** With your consent, a third-party\nservice attempts to identify the organisation a visitor is connecting from, using the IP address, so that\nour sales team knows which companies have shown interest. It is aimed at organisations rather than\nindividuals, but an IP address is personal data and the inference is drawn from it, so it sits in the\nmarketing category and runs only on consent. Refuse it and nothing is sent.\n\n### In the web application\n\nOnce you are signed in, the cookies in use are the ones that keep you signed in, keep the session secure,\nand remember interface preferences such as language, time zone and time format. These are strictly\nnecessary or preference cookies for a service you have asked us to provide.\n\n**We do not run advertising or cross-site tracking inside the application.** Nothing you do in a workspace\nis used to target advertising anywhere, and no advertising network receives data from it.\n\n### If your employer runs Ever Gauzy\n\nCookie consent is about this website and this application in your browser. It has nothing to do with the\ndesktop monitoring features — refusing analytics cookies here does not switch off screen capture, and\naccepting them does not switch it on. Those are configured by your employer and described in the privacy\nannex.\n\n### Changing your mind\n\nThe preference centre is reachable from the footer of https://gauzy.co at any time. Withdrawing consent is\nas easy as giving it, and takes effect immediately for anything not already loaded.\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://gauzy.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://gauzy.co/cookies](https://gauzy.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[gauzy.co](https://gauzy.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://gauzy.co/cookies](https://gauzy.co/cookies)."
|
|
205
|
+
"markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[gauzy.co](https://gauzy.co) and in Ever Gauzy Cloud — 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://gauzy.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://gauzy.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.\n\nThe software is **Umami**, an open-source analytics package. We run it ourselves on our own hardware in\nthe European Union — we do not use its hosted service, so no third party is involved and there is no\ntransfer to disclose. Naming it matters: the exemption described below depends on how the software is\nconfigured, and you cannot check a claim about software we decline to name.\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 Gauzy\n\n### Where this applies\n\nThis policy covers the gauzy.co website and the web application. **The desktop applications are\na different matter**: they are not browsers and they do not use cookies for tracking. What they capture,\nand what governs it, is set out in the privacy annex for this product rather than here.\n\n### On the website\n\nThe website is where the consent choice is offered. Nothing in the analytics, marketing or preferences\ncategories runs until you have made one.\n\n| Purpose | Category | Consent |\n|---|---|---|\n| Session, sign-in and security | Strictly necessary | Not required |\n| Remembering your cookie choice | Strictly necessary | Not required |\n| Bot and abuse protection on forms | Strictly necessary | Not required |\n| Our own self-hosted analytics | Strictly necessary | Not required — see the core section on analytics without consent |\n| Third-party product and site analytics | Analytics | Required |\n| Tag management | Analytics | Required |\n| Business visitor identification | Marketing | Required |\n| Language and interface preferences | Preferences | Required |\n\n**Business visitor identification deserves naming rather than burying.** With your consent, a third-party\nservice attempts to identify the organisation a visitor is connecting from, using the IP address, so that\nour sales team knows which companies have shown interest. It is aimed at organisations rather than\nindividuals, but an IP address is personal data and the inference is drawn from it, so it sits in the\nmarketing category and runs only on consent. Refuse it and nothing is sent.\n\n### In the web application\n\nOnce you are signed in, the cookies in use are the ones that keep you signed in, keep the session secure,\nand remember interface preferences such as language, time zone and time format. These are strictly\nnecessary or preference cookies for a service you have asked us to provide.\n\n**We do not run advertising or cross-site tracking inside the application.** Nothing you do in a workspace\nis used to target advertising anywhere, and no advertising network receives data from it.\n\n### If your employer runs Ever Gauzy\n\nCookie consent is about this website and this application in your browser. It has nothing to do with the\ndesktop monitoring features — refusing analytics cookies here does not switch off screen capture, and\naccepting them does not switch it on. Those are configured by your employer and described in the privacy\nannex.\n\n### Changing your mind\n\nThe preference centre is reachable from the footer of https://gauzy.co at any time. Withdrawing consent is\nas easy as giving it, and takes effect immediately for anything not already loaded.\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://gauzy.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://gauzy.co/cookies](https://gauzy.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[gauzy.co](https://gauzy.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://gauzy.co/cookies](https://gauzy.co/cookies)."
|
|
206
206
|
}
|
|
@@ -168,8 +168,11 @@ Refusing is a decision we record and respect, not a negotiating position.</p>
|
|
|
168
168
|
better or worse. That is a legitimate thing for us to want, and it is also the reason most websites hand
|
|
169
169
|
their visitors to a third-party analytics company. <strong>We built ours the other way round: we run our own
|
|
170
170
|
analytics software, on our own servers, in our own infrastructure, and it is designed so that there is
|
|
171
|
-
nothing about you worth asking permission for.</strong> No third-party analytics vendor receives this data
|
|
172
|
-
|
|
171
|
+
nothing about you worth asking permission for.</strong> No third-party analytics vendor receives this data.</p>
|
|
172
|
+
<p>The software is <strong>Umami</strong>, an open-source analytics package. We run it ourselves on our own hardware in
|
|
173
|
+
the European Union — we do not use its hosted service, so no third party is involved and there is no
|
|
174
|
+
transfer to disclose. Naming it matters: the exemption described below depends on how the software is
|
|
175
|
+
configured, and you cannot check a claim about software we decline to name.</p>
|
|
173
176
|
<h3 id="what-it-does-and-what-it-deliberately-does-not-do" tabindex="-1">What it does, and what it deliberately does not do</h3>
|
|
174
177
|
<ul>
|
|
175
178
|
<li><strong>It sets no cookies.</strong> Nothing is written to your device — no cookie, no local storage entry, nothing.</li>
|