@ever-co/legal 0.1.0 → 0.1.1

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.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +3 -3
  3. package/dist/content/aup/ever-demand/en.html +2 -2
  4. package/dist/content/aup/ever-demand/en.json +3 -3
  5. package/dist/content/aup/ever-rec/en.html +2 -2
  6. package/dist/content/aup/ever-rec/en.json +3 -3
  7. package/dist/content/aup/ever-teams/en.html +2 -2
  8. package/dist/content/aup/ever-teams/en.json +3 -3
  9. package/dist/content/aup/ever-works/en.html +2 -2
  10. package/dist/content/aup/ever-works/en.json +3 -3
  11. package/dist/content/aup/everiq/en.html +2 -2
  12. package/dist/content/aup/everiq/en.json +3 -3
  13. package/dist/content/aup/gauzy/en.html +2 -2
  14. package/dist/content/aup/gauzy/en.json +3 -3
  15. package/dist/content/aup/githands/en.html +2 -2
  16. package/dist/content/aup/githands/en.json +3 -3
  17. package/dist/content/aup/hust/en.html +2 -2
  18. package/dist/content/aup/hust/en.json +3 -3
  19. package/dist/content/aup/traduora/en.html +2 -2
  20. package/dist/content/aup/traduora/en.json +3 -3
  21. package/dist/content/cookies/ever-corporate/en.html +16 -1
  22. package/dist/content/cookies/ever-corporate/en.json +3 -3
  23. package/dist/content/cookies/ever-demand/en.html +16 -1
  24. package/dist/content/cookies/ever-demand/en.json +3 -3
  25. package/dist/content/cookies/ever-rec/en.html +16 -1
  26. package/dist/content/cookies/ever-rec/en.json +3 -3
  27. package/dist/content/cookies/ever-teams/en.html +16 -1
  28. package/dist/content/cookies/ever-teams/en.json +3 -3
  29. package/dist/content/cookies/ever-tech/en.html +16 -1
  30. package/dist/content/cookies/ever-tech/en.json +3 -3
  31. package/dist/content/cookies/ever-works/en.html +16 -1
  32. package/dist/content/cookies/ever-works/en.json +3 -3
  33. package/dist/content/cookies/everiq/en.html +16 -1
  34. package/dist/content/cookies/everiq/en.json +3 -3
  35. package/dist/content/cookies/gauzy/en.html +16 -1
  36. package/dist/content/cookies/gauzy/en.json +3 -3
  37. package/dist/content/cookies/githands/en.html +16 -1
  38. package/dist/content/cookies/githands/en.json +3 -3
  39. package/dist/content/cookies/hust/en.html +16 -1
  40. package/dist/content/cookies/hust/en.json +3 -3
  41. package/dist/content/cookies/traduora/en.html +16 -1
  42. package/dist/content/cookies/traduora/en.json +3 -3
  43. package/dist/content/dpa/ever-demand/en.html +2 -2
  44. package/dist/content/dpa/ever-demand/en.json +3 -3
  45. package/dist/content/dpa/ever-rec/en.html +2 -2
  46. package/dist/content/dpa/ever-rec/en.json +3 -3
  47. package/dist/content/dpa/ever-teams/en.html +2 -2
  48. package/dist/content/dpa/ever-teams/en.json +3 -3
  49. package/dist/content/dpa/ever-works/en.html +2 -2
  50. package/dist/content/dpa/ever-works/en.json +3 -3
  51. package/dist/content/dpa/gauzy/en.html +2 -2
  52. package/dist/content/dpa/gauzy/en.json +3 -3
  53. package/dist/content/dpa/githands/en.html +2 -2
  54. package/dist/content/dpa/githands/en.json +3 -3
  55. package/dist/content/dpa/hust/en.html +2 -2
  56. package/dist/content/dpa/hust/en.json +3 -3
  57. package/dist/content/privacy/ever-corporate/en.html +3 -9
  58. package/dist/content/privacy/ever-corporate/en.json +3 -3
  59. package/dist/content/privacy/ever-demand/en.html +3 -3
  60. package/dist/content/privacy/ever-demand/en.json +3 -3
  61. package/dist/content/privacy/ever-rec/en.html +3 -9
  62. package/dist/content/privacy/ever-rec/en.json +3 -3
  63. package/dist/content/privacy/ever-teams/en.html +3 -3
  64. package/dist/content/privacy/ever-teams/en.json +3 -3
  65. package/dist/content/privacy/ever-tech/en.html +3 -9
  66. package/dist/content/privacy/ever-tech/en.json +3 -3
  67. package/dist/content/privacy/ever-works/en.html +3 -3
  68. package/dist/content/privacy/ever-works/en.json +3 -3
  69. package/dist/content/privacy/everiq/en.html +3 -3
  70. package/dist/content/privacy/everiq/en.json +3 -3
  71. package/dist/content/privacy/gauzy/en.html +3 -3
  72. package/dist/content/privacy/gauzy/en.json +3 -3
  73. package/dist/content/privacy/githands/en.html +3 -3
  74. package/dist/content/privacy/githands/en.json +3 -3
  75. package/dist/content/privacy/hust/en.html +3 -3
  76. package/dist/content/privacy/hust/en.json +3 -3
  77. package/dist/content/privacy/traduora/en.html +3 -3
  78. package/dist/content/privacy/traduora/en.json +3 -3
  79. package/dist/content/refund/ever-works/en.html +2 -2
  80. package/dist/content/refund/ever-works/en.json +3 -3
  81. package/dist/content/refund/gauzy/en.html +2 -2
  82. package/dist/content/refund/gauzy/en.json +3 -3
  83. package/dist/content/refund/githands/en.html +2 -2
  84. package/dist/content/refund/githands/en.json +3 -3
  85. package/dist/content/refund/hust/en.html +2 -2
  86. package/dist/content/refund/hust/en.json +3 -3
  87. package/dist/content/security/ever-demand/en.html +1 -1
  88. package/dist/content/security/ever-demand/en.json +3 -3
  89. package/dist/content/security/ever-rec/en.html +1 -1
  90. package/dist/content/security/ever-rec/en.json +3 -3
  91. package/dist/content/security/ever-teams/en.html +1 -1
  92. package/dist/content/security/ever-teams/en.json +3 -3
  93. package/dist/content/security/ever-works/en.html +1 -1
  94. package/dist/content/security/ever-works/en.json +3 -3
  95. package/dist/content/security/gauzy/en.html +1 -1
  96. package/dist/content/security/gauzy/en.json +3 -3
  97. package/dist/content/security/githands/en.html +1 -1
  98. package/dist/content/security/githands/en.json +3 -3
  99. package/dist/content/security/hust/en.html +1 -1
  100. package/dist/content/security/hust/en.json +3 -3
  101. package/dist/content/subprocessors/ever-corporate/en.html +1 -7
  102. package/dist/content/subprocessors/ever-corporate/en.json +3 -3
  103. package/dist/content/subprocessors/ever-demand/en.html +1 -1
  104. package/dist/content/subprocessors/ever-demand/en.json +3 -3
  105. package/dist/content/subprocessors/ever-rec/en.html +1 -7
  106. package/dist/content/subprocessors/ever-rec/en.json +3 -3
  107. package/dist/content/subprocessors/ever-teams/en.html +1 -1
  108. package/dist/content/subprocessors/ever-teams/en.json +3 -3
  109. package/dist/content/subprocessors/ever-tech/en.html +1 -7
  110. package/dist/content/subprocessors/ever-tech/en.json +3 -3
  111. package/dist/content/subprocessors/ever-works/en.html +1 -1
  112. package/dist/content/subprocessors/ever-works/en.json +3 -3
  113. package/dist/content/subprocessors/everiq/en.html +1 -1
  114. package/dist/content/subprocessors/everiq/en.json +3 -3
  115. package/dist/content/subprocessors/gauzy/en.html +1 -1
  116. package/dist/content/subprocessors/gauzy/en.json +3 -3
  117. package/dist/content/subprocessors/githands/en.html +1 -1
  118. package/dist/content/subprocessors/githands/en.json +3 -3
  119. package/dist/content/subprocessors/hust/en.html +1 -1
  120. package/dist/content/subprocessors/hust/en.json +3 -3
  121. package/dist/content/subprocessors/traduora/en.html +1 -1
  122. package/dist/content/subprocessors/traduora/en.json +3 -3
  123. package/dist/content/tos/ever-corporate/en.html +3 -3
  124. package/dist/content/tos/ever-corporate/en.json +3 -3
  125. package/dist/content/tos/ever-demand/en.html +3 -3
  126. package/dist/content/tos/ever-demand/en.json +3 -3
  127. package/dist/content/tos/ever-rec/en.html +3 -3
  128. package/dist/content/tos/ever-rec/en.json +3 -3
  129. package/dist/content/tos/ever-teams/en.html +3 -3
  130. package/dist/content/tos/ever-teams/en.json +3 -3
  131. package/dist/content/tos/ever-tech/en.html +3 -3
  132. package/dist/content/tos/ever-tech/en.json +3 -3
  133. package/dist/content/tos/ever-works/en.html +3 -3
  134. package/dist/content/tos/ever-works/en.json +3 -3
  135. package/dist/content/tos/everiq/en.html +3 -3
  136. package/dist/content/tos/everiq/en.json +3 -3
  137. package/dist/content/tos/gauzy/en.html +3 -3
  138. package/dist/content/tos/gauzy/en.json +3 -3
  139. package/dist/content/tos/githands/en.html +3 -3
  140. package/dist/content/tos/githands/en.json +3 -3
  141. package/dist/content/tos/hust/en.html +3 -3
  142. package/dist/content/tos/hust/en.json +3 -3
  143. package/dist/content/tos/traduora/en.html +3 -3
  144. package/dist/content/tos/traduora/en.json +3 -3
  145. package/dist/index.json +144 -144
  146. package/package.json +50 -50
@@ -6,9 +6,9 @@
6
6
  "entity": "Ever Technologies LTD",
7
7
  "entityId": "ever-technologies-bg",
8
8
  "locale": "en",
9
- "version": "1.0.0",
9
+ "version": "1.0.1",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "c284c50c83288a8ad1f09a9386d4b0d9515ed705dc564b94ea00c8e752e1c819",
11
+ "sha256": "51ea68a29e5061f8d1f224ba7bd0bc1f2480e14805acdfdeb85660a634ac1a37",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/cookies/010-scope",
@@ -189,5 +189,5 @@
189
189
  }
190
190
  ],
191
191
  "path": "content/cookies/traduora/en.html",
192
- "markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[traduora.co](https://traduora.co) and in Ever Traduora — 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://traduora.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://traduora.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## Ever Traduora: what runs on our two websites\n\nThis annex covers the two properties we operate under this name: the website at\n[traduora.co](https://traduora.co) and the documentation at https://docs.traduora.co. **There is\nnothing else to cover.** Ever Traduora is software you run on your own server — there is no hosted\nservice, no sign-in and no application of ours holding anything of yours — so the parts of this policy\nwritten for a signed-in Service describe a surface that does not exist for this product.\n\n**The software we publish writes nothing to anybody's device on our behalf and reports nothing to us.**\nIt carries no analytics, no telemetry, no licence check and no update ping. What your own instance stores\nin your users' browsers to keep them signed in is yours to describe, on your own domain.\n\nOne absence is worth naming before the tables. **We run no analytics of our own on these sites.** There is\nno first-party, self-hosted measurement tool here, and therefore nothing that could rely on the\naudience-measurement exemption. Every measurement technology below belongs to another company, and every\none of them waits for your consent.\n\n### 1. The website at [traduora.co](https://traduora.co)\n\n| Technology | Provider | Category | What it is for | Consent |\n|---|---|---|---|---|\n| Edge, routing and security | Cloudflare | Strictly necessary | Terminating the connection, absorbing attacks and filtering hostile traffic before a request reaches us | Not required |\n| Consent record | Us | Strictly necessary | Remembering what you chose, so we honour it and stop asking | Not required |\n| Flag icons in the language menu | jsDelivr | Strictly necessary to render the page as designed | The flag images beside each language are fetched from a public content delivery network. Nothing is stored — the request itself is the disclosure | Not required, and it happens before you have chosen |\n| Language choice | Us | Functional | Keeping the site in the language you picked, on the next page and the next visit | Required |\n| Light or dark theme | Us | Functional | Remembering which one you chose | Required |\n| Google Analytics, loaded from googletagmanager.com | Google | Analytics | Counting visits, pages and referrers | Required |\n| Product analytics | PostHog | Analytics | Which pages are read and which are abandoned | Required |\n| Error diagnostics | Sentry | Analytics | Capturing an error, with a stack trace, when something on the page fails | Required |\n| **Session replay** | Sentry | Analytics | A masked reconstruction of your visit — set out in full below, because it deserves more than a table row | Required |\n| Browser performance monitoring | New Relic | Analytics | Page load and rendering timings, reported to that provider's European Union endpoint | Required |\n| Real user monitoring | Pingdom | Analytics | How long pages actually took to load for real visitors | Required |\n\nTwo honest notes on that table.\n\n- **The Google Analytics identifier in our pages is a legacy Universal Analytics property.** Whether or not\n anything is still measured behind it, loading the tag tells Google you were here, so it is declared and\n consent-gated like any other analytics tool rather than treated as dormant.\n- **New Relic's agent is configured with its own cookies switched off**, so it stores nothing on your\n device. The beacon it sends is still a disclosure to that provider, which is why it sits in the analytics\n category with the rest.\n\nOur Sub-processor List gives the full legal name, the location and the exact data set for each of these\nproviders.\n\n### 2. The documentation at https://docs.traduora.co\n\n| Technology | Provider | Category | What it is for | Consent |\n|---|---|---|---|---|\n| Edge, routing and security | Cloudflare | Strictly necessary | As above | Not required |\n| Typefaces | Google Fonts | Strictly necessary to render the page as designed | Two typefaces are fetched from Google when the page opens. Nothing is stored — the request itself is the disclosure | Not required, and it happens before you have chosen |\n| Theme and interface state | Us | Functional | Remembering dark or light mode and which sections you left collapsed | Required |\n| Documentation search | Us | Strictly necessary | Searching the documentation against an index served from our own domain. No search company is involved and nothing about your search leaves our infrastructure | Not required |\n\n**No analytics of any kind runs on the documentation.** No Google Analytics, no product analytics, no\nsession replay, no performance monitoring. The two sites genuinely differ on this point. It would be\ntidier to describe them as one, and it would not be true.\n\n### What is actually written to your device\n\nCookies are not the whole story, and a notice that lists only cookies under-describes what is happening.\nThe rules that require your consent apply to storing or reading anything on your device, whatever\nmechanism does it. So, precisely:\n\n- **Cookies set by us** — one holding a language code and nothing else, written when you use the language\n switcher on [traduora.co](https://traduora.co); and the record of your consent choice.\n- **Cookies set by others** — Cloudflare's own security cookies, lasting from the session up to a year\n depending on which one; Google Analytics' client identifier, up to two years; and PostHog's visitor\n identifier, up to a year.\n- **Browser local storage** — your light or dark theme choice on both sites, and the sections you have\n collapsed in the documentation. These stay until you clear your browser's storage. PostHog also keeps\n its visitor identifier here as well as in a cookie.\n- **Browser session storage** — the identifier that ties a session replay together. It is cleared when you\n close the tab.\n- **Nothing at all** — New Relic's agent, the Pingdom measurement, the flag icons and the documentation\n typefaces. Each is a request that leaves your browser rather than something left behind in it.\n\n### Two requests that leave your browser before you have chosen anything\n\nWe would rather name these than let you find them.\n\n**The language menu on [traduora.co](https://traduora.co) loads its flag images from jsDelivr, a public\ncontent delivery network, and the documentation loads its two typefaces from Google.** Nothing is stored\non your device by either, but **the request discloses your IP address, your browser and the page you are\non to that network** — and because both are needed for the page to render as designed, they happen whether\nor not you accept anything.\n\nThere is no way to fetch a file from somebody else's network and hide the request for it. The real fix is\nto serve both files ourselves, which is what the website already does for its own typefaces, and we intend\nto do the same for these two. Until then, the accurate statement is the one above rather than a claim that\nnothing loads before consent.\n\n### Session replay, in full\n\n**Our error diagnostics provider records session replays on [traduora.co](https://traduora.co).** A\nsession replay is a reconstruction of your visit — the structure of the page, what moved, what you\nclicked, what you typed into, and in what order — played back afterwards like a recording.\n\n- It is captured for **roughly one visit in ten**, chosen at random, and for **every visit in which an\n error occurs**.\n- **All text is masked and all media is blocked** in the capture. What is reconstructed is the shape of the\n page and your interaction with it, not the words on it.\n- It runs on the website only. **There is no session replay on the documentation.**\n- **It is in the analytics category and it is gated like everything else in that category.** Refuse\n analytics and no replay is captured at all.\n\nWe give it its own section because recording a session is a different proposition from counting page\nviews, and you are entitled to decide about it on its own terms rather than find it folded into a general\nline about error tracking.\n\n### What does not run on either site\n\n- **No advertising, no advertising pixel and no cross-site tracking.** Nothing here is used to target\n advertising anywhere, and no advertising network receives anything from these pages.\n- **No visitor identification.** We make no attempt to work out which organisation a visitor belongs to.\n- **No tag manager container.** Google's tag is delivered from googletagmanager.com, which is that\n company's delivery host — but we operate no container through which further tags could be added without\n changing this document.\n- **No bot-protection script, because there is no form.** There is no sign-up, no newsletter, no contact\n form and no checkout on either site, so no reCAPTCHA or equivalent loads and nothing about your mouse\n movement or typing is sent anywhere for that purpose.\n- **Nothing reaches our content management system from your browser.** Our own server reads it when a page\n is built; your browser never contacts it.\n\n### If you run your own copy\n\n**This policy describes our two websites, not your instance.** Ever Traduora ships with no analytics, no\ntracking technology and no consent mechanism of its own, so there is nothing of ours to switch off in a\ndeployment you run — and equally, nothing of ours to ask your users about. If you add a measurement tool\nto your own deployment, telling your users about it and asking them where the law requires it is yours to\ndo. Our banner is not your consent mechanism.\n\nIf you find something running on either of our sites that is not in the tables above, that is a defect and\nwe want to know. Write to privacy@ever.co.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://traduora.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://traduora.co/cookies](https://traduora.co/cookies). The effective date shown with this policy tells you which\nversion applies today.\n\n## How to reach us\n\nQuestions about this policy, about anything in the table above, or about a choice you have made — write to\nprivacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent\nrecord, for the current sub-processor list, or to be excluded from our own analytics, and we will do it\nwithout asking why.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\nIf you think we have handled your data badly, tell us first — we would rather fix it. **You can also\ncomplain to a data protection supervisory authority at any time.** Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.0 of the Cookie Policy for\n[traduora.co](https://traduora.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://traduora.co/cookies](https://traduora.co/cookies)."
192
+ "markdown": "## What this policy covers\n\nThis Cookie Policy explains the cookies and similar technologies we use on\n[traduora.co](https://traduora.co) and in Ever Traduora — 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://traduora.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://traduora.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## Ever Traduora: what runs on our two websites\n\nThis annex covers the two properties we operate under this name: the website at\n[traduora.co](https://traduora.co) and the documentation at https://docs.traduora.co. **There is\nnothing else to cover.** Ever Traduora is software you run on your own server — there is no hosted\nservice, no sign-in and no application of ours holding anything of yours — so the parts of this policy\nwritten for a signed-in Service describe a surface that does not exist for this product.\n\n**The software we publish writes nothing to anybody's device on our behalf and reports nothing to us.**\nIt carries no analytics, no telemetry, no licence check and no update ping. What your own instance stores\nin your users' browsers to keep them signed in is yours to describe, on your own domain.\n\nOne absence is worth naming before the tables. **We run no analytics of our own on these sites.** There is\nno first-party, self-hosted measurement tool here, and therefore nothing that could rely on the\naudience-measurement exemption. Every measurement technology below belongs to another company, and every\none of them waits for your consent.\n\n### 1. The website at [traduora.co](https://traduora.co)\n\n| Technology | Provider | Category | What it is for | Consent |\n|---|---|---|---|---|\n| Edge, routing and security | Cloudflare | Strictly necessary | Terminating the connection, absorbing attacks and filtering hostile traffic before a request reaches us | Not required |\n| Consent record | Us | Strictly necessary | Remembering what you chose, so we honour it and stop asking | Not required |\n| Flag icons in the language menu | jsDelivr | Strictly necessary to render the page as designed | The flag images beside each language are fetched from a public content delivery network. Nothing is stored — the request itself is the disclosure | Not required, and it happens before you have chosen |\n| Language choice | Us | Functional | Keeping the site in the language you picked, on the next page and the next visit | Required |\n| Light or dark theme | Us | Functional | Remembering which one you chose | Required |\n| Google Analytics, loaded from googletagmanager.com | Google | Analytics | Counting visits, pages and referrers | Required |\n| Product analytics | PostHog | Analytics | Which pages are read and which are abandoned | Required |\n| Error diagnostics | Sentry | Analytics | Capturing an error, with a stack trace, when something on the page fails | Required |\n| **Session replay** | Sentry | Analytics | A masked reconstruction of your visit — set out in full below, because it deserves more than a table row | Required |\n| Browser performance monitoring | New Relic | Analytics | Page load and rendering timings, reported to that provider's European Union endpoint | Required |\n| Real user monitoring | Pingdom | Analytics | How long pages actually took to load for real visitors | Required |\n\nTwo honest notes on that table.\n\n- **The Google Analytics identifier in our pages is a legacy Universal Analytics property.** Whether or not\n anything is still measured behind it, loading the tag tells Google you were here, so it is declared and\n consent-gated like any other analytics tool rather than treated as dormant.\n- **New Relic's agent is configured with its own cookies switched off**, so it stores nothing on your\n device. The beacon it sends is still a disclosure to that provider, which is why it sits in the analytics\n category with the rest.\n\nOur Sub-processor List gives the full legal name, the location and the exact data set for each of these\nproviders.\n\n### 2. The documentation at https://docs.traduora.co\n\n| Technology | Provider | Category | What it is for | Consent |\n|---|---|---|---|---|\n| Edge, routing and security | Cloudflare | Strictly necessary | As above | Not required |\n| Typefaces | Google Fonts | Strictly necessary to render the page as designed | Two typefaces are fetched from Google when the page opens. Nothing is stored — the request itself is the disclosure | Not required, and it happens before you have chosen |\n| Theme and interface state | Us | Functional | Remembering dark or light mode and which sections you left collapsed | Required |\n| Documentation search | Us | Strictly necessary | Searching the documentation against an index served from our own domain. No search company is involved and nothing about your search leaves our infrastructure | Not required |\n\n**No analytics of any kind runs on the documentation.** No Google Analytics, no product analytics, no\nsession replay, no performance monitoring. The two sites genuinely differ on this point. It would be\ntidier to describe them as one, and it would not be true.\n\n### What is actually written to your device\n\nCookies are not the whole story, and a notice that lists only cookies under-describes what is happening.\nThe rules that require your consent apply to storing or reading anything on your device, whatever\nmechanism does it. So, precisely:\n\n- **Cookies set by us** — one holding a language code and nothing else, written when you use the language\n switcher on [traduora.co](https://traduora.co); and the record of your consent choice.\n- **Cookies set by others** — Cloudflare's own security cookies, lasting from the session up to a year\n depending on which one; Google Analytics' client identifier, up to two years; and PostHog's visitor\n identifier, up to a year.\n- **Browser local storage** — your light or dark theme choice on both sites, and the sections you have\n collapsed in the documentation. These stay until you clear your browser's storage. PostHog also keeps\n its visitor identifier here as well as in a cookie.\n- **Browser session storage** — the identifier that ties a session replay together. It is cleared when you\n close the tab.\n- **Nothing at all** — New Relic's agent, the Pingdom measurement, the flag icons and the documentation\n typefaces. Each is a request that leaves your browser rather than something left behind in it.\n\n### Two requests that leave your browser before you have chosen anything\n\nWe would rather name these than let you find them.\n\n**The language menu on [traduora.co](https://traduora.co) loads its flag images from jsDelivr, a public\ncontent delivery network, and the documentation loads its two typefaces from Google.** Nothing is stored\non your device by either, but **the request discloses your IP address, your browser and the page you are\non to that network** — and because both are needed for the page to render as designed, they happen whether\nor not you accept anything.\n\nThere is no way to fetch a file from somebody else's network and hide the request for it. The real fix is\nto serve both files ourselves, which is what the website already does for its own typefaces, and we intend\nto do the same for these two. Until then, the accurate statement is the one above rather than a claim that\nnothing loads before consent.\n\n### Session replay, in full\n\n**Our error diagnostics provider records session replays on [traduora.co](https://traduora.co).** A\nsession replay is a reconstruction of your visit — the structure of the page, what moved, what you\nclicked, what you typed into, and in what order — played back afterwards like a recording.\n\n- It is captured for **roughly one visit in ten**, chosen at random, and for **every visit in which an\n error occurs**.\n- **All text is masked and all media is blocked** in the capture. What is reconstructed is the shape of the\n page and your interaction with it, not the words on it.\n- It runs on the website only. **There is no session replay on the documentation.**\n- **It is in the analytics category and it is gated like everything else in that category.** Refuse\n analytics and no replay is captured at all.\n\nWe give it its own section because recording a session is a different proposition from counting page\nviews, and you are entitled to decide about it on its own terms rather than find it folded into a general\nline about error tracking.\n\n### What does not run on either site\n\n- **No advertising, no advertising pixel and no cross-site tracking.** Nothing here is used to target\n advertising anywhere, and no advertising network receives anything from these pages.\n- **No visitor identification.** We make no attempt to work out which organisation a visitor belongs to.\n- **No tag manager container.** Google's tag is delivered from googletagmanager.com, which is that\n company's delivery host — but we operate no container through which further tags could be added without\n changing this document.\n- **No bot-protection script, because there is no form.** There is no sign-up, no newsletter, no contact\n form and no checkout on either site, so no reCAPTCHA or equivalent loads and nothing about your mouse\n movement or typing is sent anywhere for that purpose.\n- **Nothing reaches our content management system from your browser.** Our own server reads it when a page\n is built; your browser never contacts it.\n\n### If you run your own copy\n\n**This policy describes our two websites, not your instance.** Ever Traduora ships with no analytics, no\ntracking technology and no consent mechanism of its own, so there is nothing of ours to switch off in a\ndeployment you run — and equally, nothing of ours to ask your users about. If you add a measurement tool\nto your own deployment, telling your users about it and asking them where the law requires it is yours to\ndo. Our banner is not your consent mechanism.\n\nIf you find something running on either of our sites that is not in the tables above, that is a defect and\nwe want to know. Write to privacy@ever.co.\n\n## Third-party cookies and the providers behind them\n\nSome of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is\nthere — but the provider decides what its own technology collects, and for that collection it is usually\nacting in its own right and under its own privacy notice rather than ours. Where that is the case, the table\nbelow links to their notice.\n\nThese are the kinds of provider involved, and what each kind does.\n\n### Analytics providers\n\nMeasure how the Service is used: page views, feature use, funnels, errors and performance. Most set a\npersistent identifier of their own so a returning visitor is recognised, and some can record a **session\nreplay** — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do\nthat, the table says so explicitly.\n\n**Consent required.** They do not load until you agree.\n\n### Tag management\n\nA tag manager is a container we load once, through which other tags can then be delivered without shipping\nnew code. That flexibility is exactly what makes it worth describing carefully: **a container is a delivery\nmechanism, so what it delivers matters more than the container itself.**\n\nEvery tag we deliver through a container is declared in the table below, in its own category. The container\nis consent-gated as a whole, and **we do not use it to deliver anything from a category you have refused.**\n\n**Consent required.**\n\n### Marketing and visitor identification\n\nCampaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —\nand business-audience identification, which resolves a visitor's IP address to the organisation that holds\nit so we can see which companies are interested in the product. It gives us a company, not your name. Most\npeople still do not expect it, which is why it is named here as well as in the table.\n\n**Consent required.**\n\n### Video, maps, fonts and other embedded content\n\nWhere a page embeds something served from another provider's network — a video player, a map, a code\nsandbox, a font, a script from a public content delivery network — your browser fetches it directly from\nthat provider.\n\n**That fetch discloses your IP address, your browser and the page you were on to the provider, whether or\nnot anything is stored on your device.** There is no way to embed a resource and hide the request for it.\n\nWe handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party\nentirely; and where an embed stores or reads anything on your device, we treat it as **consent required**\nand it does not load until you agree. Embeds that store nothing but are still fetched from a third party are\nlisted in the table so you can see the disclosure even where no cookie is involved.\n\n### Security and delivery\n\nThe network in front of our sites — the proxy and content delivery layer that terminates the connection,\nabsorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on\npayment. These see connection metadata and may set their own security cookies.\n\n**Strictly necessary**, and therefore not consent-gated. Our reasoning for putting bot protection in that\ncategory, including what it sends to its provider, is set out in the categories section above.\n\n#### Measurement injected by that layer, which our banner cannot control\n\nThere is one thing here we would rather state plainly than have you discover in a network trace. **Our\ncontent delivery provider injects its own lightweight measurement script at the edge — into the response,\nafter it leaves our servers.** It is not in our code, our consent system never sees it, and **switching a\ncategory off in our preference centre does not stop it**, because by the time the page reaches you the\nscript is already part of it.\n\nWhat it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent\nidentifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to\nanything else we hold.\n\nWhat it is not: covered by the exemption we claim for our own analytics. That argument rests on the data\nstaying on our own infrastructure, and this is a third party receiving it. **We are not going to stretch\nthe same reasoning over both.**\n\nIf you would rather it did not run, a content blocker or a network-level block stops it, and we do not\nattempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the\ncurrent provider and exactly what it collects.\n\n### Where these providers are, and where to find the full list\n\nSome of these providers are established outside the European Economic Area, and using them involves an\ninternational transfer of personal data. **The transfers section of our\n[Privacy Policy](https://traduora.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://traduora.co/cookies](https://traduora.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.1 of the Cookie Policy for\n[traduora.co](https://traduora.co), in force from 2026-08-02. Earlier versions, with the dates\nthey applied, are at [https://traduora.co/cookies](https://traduora.co/cookies)."
193
193
  }
@@ -1,6 +1,6 @@
1
1
  <h1 id="data-processing-addendum" tabindex="-1">Data Processing Addendum</h1>
2
2
  <p><strong>Ever Demand</strong> — <a href="https://everdemand.co">everdemand.co</a></p>
3
- <p>Version 1.0.0 · In force from 2026-08-02</p>
3
+ <p>Version 1.0.1 · In force from 2026-08-02</p>
4
4
  <p>This Data Processing Addendum (&quot;<strong>Addendum</strong>&quot;) governs our processing of personal data <strong>on your behalf</strong>
5
5
  when you use Ever Demand. It is agreed between you and <strong>Ever Technologies LTD</strong>, a company
6
6
  registered in Bulgaria under company number 204599535, with its registered office
@@ -1799,6 +1799,6 @@ are established. <strong>Our own authority is the Commission for Personal Data P
1799
1799
  <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. A data subject can
1800
1800
  complain to the authority in their own country as well, and neither of us can require them to come through
1801
1801
  us first.</p>
1802
- <p>This document is version 1.0.0 of the Data Processing Addendum for
1802
+ <p>This document is version 1.0.1 of the Data Processing Addendum for
1803
1803
  <a href="https://everdemand.co">everdemand.co</a>, in force from 2026-08-02. Earlier versions, with the
1804
1804
  dates they applied, are at <a href="https://everdemand.co/dpa">https://everdemand.co/dpa</a>.</p>