@ever-co/legal 0.1.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.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +667 -0
  2. package/dist/content/aup/ever-corporate/en.json +302 -0
  3. package/dist/content/aup/ever-demand/en.html +802 -0
  4. package/dist/content/aup/ever-demand/en.json +339 -0
  5. package/dist/content/aup/ever-rec/en.html +667 -0
  6. package/dist/content/aup/ever-rec/en.json +302 -0
  7. package/dist/content/aup/ever-teams/en.html +667 -0
  8. package/dist/content/aup/ever-teams/en.json +302 -0
  9. package/dist/content/aup/ever-works/en.html +667 -0
  10. package/dist/content/aup/ever-works/en.json +302 -0
  11. package/dist/content/aup/everiq/en.html +726 -0
  12. package/dist/content/aup/everiq/en.json +319 -0
  13. package/dist/content/aup/gauzy/en.html +715 -0
  14. package/dist/content/aup/gauzy/en.json +327 -0
  15. package/dist/content/aup/githands/en.html +864 -0
  16. package/dist/content/aup/githands/en.json +363 -0
  17. package/dist/content/aup/hust/en.html +781 -0
  18. package/dist/content/aup/hust/en.json +347 -0
  19. package/dist/content/aup/traduora/en.html +667 -0
  20. package/dist/content/aup/traduora/en.json +302 -0
  21. package/dist/content/cookies/ever-corporate/en.html +493 -0
  22. package/dist/content/cookies/ever-corporate/en.json +193 -0
  23. package/dist/content/cookies/ever-demand/en.html +633 -0
  24. package/dist/content/cookies/ever-demand/en.json +226 -0
  25. package/dist/content/cookies/ever-rec/en.html +564 -0
  26. package/dist/content/cookies/ever-rec/en.json +206 -0
  27. package/dist/content/cookies/ever-teams/en.html +549 -0
  28. package/dist/content/cookies/ever-teams/en.json +222 -0
  29. package/dist/content/cookies/ever-tech/en.html +469 -0
  30. package/dist/content/cookies/ever-tech/en.json +177 -0
  31. package/dist/content/cookies/ever-works/en.html +618 -0
  32. package/dist/content/cookies/ever-works/en.json +202 -0
  33. package/dist/content/cookies/everiq/en.html +437 -0
  34. package/dist/content/cookies/everiq/en.json +185 -0
  35. package/dist/content/cookies/gauzy/en.html +490 -0
  36. package/dist/content/cookies/gauzy/en.json +206 -0
  37. package/dist/content/cookies/githands/en.html +618 -0
  38. package/dist/content/cookies/githands/en.json +210 -0
  39. package/dist/content/cookies/hust/en.html +622 -0
  40. package/dist/content/cookies/hust/en.json +210 -0
  41. package/dist/content/cookies/traduora/en.html +580 -0
  42. package/dist/content/cookies/traduora/en.json +193 -0
  43. package/dist/content/dpa/ever-demand/en.html +1804 -0
  44. package/dist/content/dpa/ever-demand/en.json +628 -0
  45. package/dist/content/dpa/ever-rec/en.html +1963 -0
  46. package/dist/content/dpa/ever-rec/en.json +652 -0
  47. package/dist/content/dpa/ever-teams/en.html +1918 -0
  48. package/dist/content/dpa/ever-teams/en.json +648 -0
  49. package/dist/content/dpa/ever-works/en.html +1801 -0
  50. package/dist/content/dpa/ever-works/en.json +624 -0
  51. package/dist/content/dpa/gauzy/en.html +1836 -0
  52. package/dist/content/dpa/gauzy/en.json +632 -0
  53. package/dist/content/dpa/githands/en.html +1808 -0
  54. package/dist/content/dpa/githands/en.json +624 -0
  55. package/dist/content/dpa/hust/en.html +1804 -0
  56. package/dist/content/dpa/hust/en.json +632 -0
  57. package/dist/content/privacy/ever-corporate/en.html +1184 -0
  58. package/dist/content/privacy/ever-corporate/en.json +352 -0
  59. package/dist/content/privacy/ever-demand/en.html +1234 -0
  60. package/dist/content/privacy/ever-demand/en.json +364 -0
  61. package/dist/content/privacy/ever-rec/en.html +1250 -0
  62. package/dist/content/privacy/ever-rec/en.json +360 -0
  63. package/dist/content/privacy/ever-teams/en.html +1238 -0
  64. package/dist/content/privacy/ever-teams/en.json +368 -0
  65. package/dist/content/privacy/ever-tech/en.html +1127 -0
  66. package/dist/content/privacy/ever-tech/en.json +352 -0
  67. package/dist/content/privacy/ever-works/en.html +1284 -0
  68. package/dist/content/privacy/ever-works/en.json +364 -0
  69. package/dist/content/privacy/everiq/en.html +1172 -0
  70. package/dist/content/privacy/everiq/en.json +328 -0
  71. package/dist/content/privacy/gauzy/en.html +1281 -0
  72. package/dist/content/privacy/gauzy/en.json +356 -0
  73. package/dist/content/privacy/githands/en.html +1393 -0
  74. package/dist/content/privacy/githands/en.json +380 -0
  75. package/dist/content/privacy/hust/en.html +1359 -0
  76. package/dist/content/privacy/hust/en.json +368 -0
  77. package/dist/content/privacy/traduora/en.html +1146 -0
  78. package/dist/content/privacy/traduora/en.json +336 -0
  79. package/dist/content/refund/ever-works/en.html +595 -0
  80. package/dist/content/refund/ever-works/en.json +336 -0
  81. package/dist/content/refund/gauzy/en.html +595 -0
  82. package/dist/content/refund/gauzy/en.json +336 -0
  83. package/dist/content/refund/githands/en.html +647 -0
  84. package/dist/content/refund/githands/en.json +361 -0
  85. package/dist/content/refund/hust/en.html +595 -0
  86. package/dist/content/refund/hust/en.json +336 -0
  87. package/dist/content/security/ever-demand/en.html +900 -0
  88. package/dist/content/security/ever-demand/en.json +425 -0
  89. package/dist/content/security/ever-rec/en.html +768 -0
  90. package/dist/content/security/ever-rec/en.json +380 -0
  91. package/dist/content/security/ever-teams/en.html +768 -0
  92. package/dist/content/security/ever-teams/en.json +380 -0
  93. package/dist/content/security/ever-works/en.html +768 -0
  94. package/dist/content/security/ever-works/en.json +380 -0
  95. package/dist/content/security/gauzy/en.html +768 -0
  96. package/dist/content/security/gauzy/en.json +380 -0
  97. package/dist/content/security/githands/en.html +876 -0
  98. package/dist/content/security/githands/en.json +421 -0
  99. package/dist/content/security/hust/en.html +768 -0
  100. package/dist/content/security/hust/en.json +380 -0
  101. package/dist/content/subprocessors/ever-corporate/en.html +382 -0
  102. package/dist/content/subprocessors/ever-corporate/en.json +158 -0
  103. package/dist/content/subprocessors/ever-demand/en.html +452 -0
  104. package/dist/content/subprocessors/ever-demand/en.json +154 -0
  105. package/dist/content/subprocessors/ever-rec/en.html +439 -0
  106. package/dist/content/subprocessors/ever-rec/en.json +154 -0
  107. package/dist/content/subprocessors/ever-teams/en.html +477 -0
  108. package/dist/content/subprocessors/ever-teams/en.json +154 -0
  109. package/dist/content/subprocessors/ever-tech/en.html +335 -0
  110. package/dist/content/subprocessors/ever-tech/en.json +141 -0
  111. package/dist/content/subprocessors/ever-works/en.html +551 -0
  112. package/dist/content/subprocessors/ever-works/en.json +154 -0
  113. package/dist/content/subprocessors/everiq/en.html +296 -0
  114. package/dist/content/subprocessors/everiq/en.json +149 -0
  115. package/dist/content/subprocessors/gauzy/en.html +603 -0
  116. package/dist/content/subprocessors/gauzy/en.json +154 -0
  117. package/dist/content/subprocessors/githands/en.html +465 -0
  118. package/dist/content/subprocessors/githands/en.json +154 -0
  119. package/dist/content/subprocessors/hust/en.html +482 -0
  120. package/dist/content/subprocessors/hust/en.json +154 -0
  121. package/dist/content/subprocessors/traduora/en.html +362 -0
  122. package/dist/content/subprocessors/traduora/en.json +154 -0
  123. package/dist/content/tos/ever-corporate/en.html +973 -0
  124. package/dist/content/tos/ever-corporate/en.json +517 -0
  125. package/dist/content/tos/ever-demand/en.html +1598 -0
  126. package/dist/content/tos/ever-demand/en.json +783 -0
  127. package/dist/content/tos/ever-rec/en.html +1524 -0
  128. package/dist/content/tos/ever-rec/en.json +771 -0
  129. package/dist/content/tos/ever-teams/en.html +1551 -0
  130. package/dist/content/tos/ever-teams/en.json +779 -0
  131. package/dist/content/tos/ever-tech/en.html +762 -0
  132. package/dist/content/tos/ever-tech/en.json +421 -0
  133. package/dist/content/tos/ever-works/en.html +1552 -0
  134. package/dist/content/tos/ever-works/en.json +787 -0
  135. package/dist/content/tos/everiq/en.html +781 -0
  136. package/dist/content/tos/everiq/en.json +429 -0
  137. package/dist/content/tos/gauzy/en.html +1440 -0
  138. package/dist/content/tos/gauzy/en.json +755 -0
  139. package/dist/content/tos/githands/en.html +1542 -0
  140. package/dist/content/tos/githands/en.json +779 -0
  141. package/dist/content/tos/hust/en.html +1566 -0
  142. package/dist/content/tos/hust/en.json +787 -0
  143. package/dist/content/tos/traduora/en.html +1238 -0
  144. package/dist/content/tos/traduora/en.json +646 -0
  145. package/dist/index.json +26991 -0
  146. package/package.json +52 -0
@@ -0,0 +1,633 @@
1
+ <h2 id="what-this-policy-covers" tabindex="-1">What this policy covers</h2>
2
+ <p>This Cookie Policy explains the cookies and similar technologies we use on
3
+ <a href="https://everdemand.co">everdemand.co</a> and in Ever Demand — the public website, the documentation,
4
+ the signed-in application, and any desktop or mobile application we publish for it. The product-specific
5
+ section below lists what is actually in use on each of those surfaces.</p>
6
+ <p>It sits alongside our <a href="https://everdemand.co/privacy">Privacy Policy</a>. The two documents answer different
7
+ questions, and it is worth knowing which one you are reading:</p>
8
+ <ul>
9
+ <li><strong>This policy is about your device.</strong> What we store on it, what we read back from it, why, and how you
10
+ control that.</li>
11
+ <li><strong>The <a href="https://everdemand.co/privacy">Privacy Policy</a> is about the information itself.</strong> What we do with personal
12
+ data once we hold it, the lawful basis for each purpose, who receives it, how long we keep it, and the
13
+ rights you can exercise over it.</li>
14
+ </ul>
15
+ <p>Where something described here involves personal data, the Privacy Policy governs that processing.
16
+ <strong>Nothing in this policy narrows the rights that document gives you.</strong></p>
17
+ <h3 id="what-this-policy-does-not-cover" tabindex="-1">What this policy does not cover</h3>
18
+ <p><strong>Other people's sites and services.</strong> Our pages link to third-party sites, and our Service connects to
19
+ third-party tools when you ask it to. Once you are on someone else's site, their cookie notice applies, not
20
+ ours. We have no control over what they store on your device.</p>
21
+ <p><strong>Your own workspace, your own site, your own people.</strong> Where you use the Service as a customer to run
22
+ something of your own — a workspace for your organisation, or a site we provision for you — the pages you
23
+ publish and the people you invite are yours. <strong>This policy is not your cookie notice to your own visitors or
24
+ personnel, and our banner is not your consent mechanism.</strong> Providing those is your responsibility, on your
25
+ own domain, under your own control.</p>
26
+ <p><strong>A copy you run yourself.</strong> Where the software behind the Service is published as open source and you run
27
+ your own deployment, this policy describes the service <em>we</em> operate — not yours. You choose what your
28
+ deployment loads and what it stores on your users' devices, and only you can describe it to them.</p>
29
+ <h2 id="cookies-and-the-other-technologies-that-behave-like-them" tabindex="-1">Cookies and the other technologies that behave like them</h2>
30
+ <p>A <strong>cookie</strong> is a small text file that a website asks your browser to keep and hands back to a server on
31
+ later requests. It is the oldest way of doing this, and the best known — but it is only one of several, and
32
+ the rules that matter here do not turn on which one is used.</p>
33
+ <p><strong>The law we work to attaches to storing information on your device or reading information back from it,
34
+ whatever the mechanism.</strong> So wherever this policy says &quot;cookies&quot;, read it as covering all of the following.</p>
35
+ <h3 id="the-technologies" tabindex="-1">The technologies</h3>
36
+ <ul>
37
+ <li><strong>Cookies</strong> — as above. Set by the site you are visiting, or by another provider whose code runs on the
38
+ page.</li>
39
+ <li><strong>Local storage and session storage</strong> — key-value storage inside your browser. Larger than a cookie, not
40
+ sent automatically with every request, and it can hold exactly the same kind of identifier.</li>
41
+ <li><strong>IndexedDB and the browser cache</strong> — structured storage and cached files. Ordinarily used to make pages
42
+ load faster and to let parts of the Service work offline, but capable of holding an identifier too.</li>
43
+ <li><strong>Pixels, beacons and tags</strong> — a tiny image or a short script whose only job is to load. The act of
44
+ loading it tells the provider that a page was opened, or an email read, along with your IP address and
45
+ browser details. A pixel often stores nothing at all and still reports on you.</li>
46
+ <li><strong>Tracking parameters in links</strong> — identifiers added to a URL so that a click can be attributed to the
47
+ campaign or message that produced it.</li>
48
+ <li><strong>SDK identifiers in desktop and mobile applications</strong> — an installed application has no cookie jar. It
49
+ stores identifiers in its own application storage instead, and may use identifiers the operating system
50
+ provides: an advertising identifier, an installation identifier, or a push notification token.</li>
51
+ <li><strong>Device and network characteristics</strong> — your IP address, screen size, language, time zone, fonts and
52
+ browser version. Individually unremarkable; combined, they can form a <strong>fingerprint</strong> that recognises a
53
+ device without storing anything on it.</li>
54
+ </ul>
55
+ <h3 id="first-party-and-third-party" tabindex="-1">First-party and third-party</h3>
56
+ <p><strong>First-party</strong> means we set it, on our own domain, and it goes to our servers.</p>
57
+ <p><strong>Third-party</strong> means it belongs to another company whose code we have chosen to run on the page — an
58
+ analytics provider, an embedded video player, a bot-protection service. Their technology reports to them,
59
+ not to us, and they decide what it does. Note the awkward part plainly: <strong>a third-party resource embedded in
60
+ our page discloses your IP address, your browser and the page you were on to that provider, even when it
61
+ stores nothing on your device at all.</strong> Loading it is the disclosure.</p>
62
+ <p>Some third-party technologies are deliberately set up to look first-party — served from a subdomain of ours,
63
+ or routed through our own servers. Where we do that, we say so in the table below rather than letting the
64
+ appearance stand.</p>
65
+ <h3 id="session-and-persistent" tabindex="-1">Session and persistent</h3>
66
+ <p><strong>Session</strong> items are discarded when you close the browser or the application. They are typically what keeps
67
+ you signed in and moving through a single visit.</p>
68
+ <p><strong>Persistent</strong> items survive until they expire or you delete them, which is what lets us recognise a
69
+ returning visitor, remember your preferences, or remember that you refused something. Each entry in the
70
+ table below states how long it lasts.</p>
71
+ <h2 id="why-we-use-them" tabindex="-1">Why we use them</h2>
72
+ <p>There are six reasons, and each one maps to one of the categories in the next section. We have written the
73
+ category next to each so you can see immediately which ones you control.</p>
74
+ <ul>
75
+ <li><strong>To sign you in and keep you signed in.</strong> Your session has to be attached to the right account, the right
76
+ workspace and the right organisation as you move between pages, and it has to be protected against being
77
+ replayed or forged by someone else. → <em>strictly necessary</em></li>
78
+ <li><strong>To keep the Service secure.</strong> Telling a person apart from an abusive script, protecting forms against
79
+ automated submission, enforcing rate limits, and detecting fraudulent sign-ups and payments.
80
+ → <em>strictly necessary</em></li>
81
+ <li><strong>To make the Service work at all.</strong> Routing your request to a healthy server, keeping you on the same one
82
+ where a feature requires it, balancing load, and serving the right version of the application.
83
+ → <em>strictly necessary</em></li>
84
+ <li><strong>To remember what you decided about cookies.</strong> Your choice has to be stored somewhere, or we would have
85
+ to ask you on every page. → <em>strictly necessary</em></li>
86
+ <li><strong>To remember your preferences.</strong> Language, time zone, theme, layout, a panel you collapsed, a message you
87
+ dismissed, and whether you want the support widget open. → <em>functional</em></li>
88
+ <li><strong>To understand how the Service is used.</strong> Which pages and features people actually use, which paths fail,
89
+ and where things are slow — so that we improve the right things rather than the ones we happen to notice.
90
+ → <em>analytics</em></li>
91
+ <li><strong>To measure our marketing.</strong> Whether a campaign reached anyone, which content leads to sign-ups, and
92
+ which organisations show interest in the product. → <em>marketing</em></li>
93
+ </ul>
94
+ <p>Two things follow from that list, and we would rather state them than leave them implied.</p>
95
+ <p><strong>Only the first four are needed for the Service to function.</strong> Everything in the last three groups is
96
+ optional. If you refuse all of it, every feature you are entitled to still works, at the same price.</p>
97
+ <p><strong>Where we can achieve a purpose without storing anything on your device, we do.</strong> That is the whole reason
98
+ our own analytics is built the way it is — see the section on analytics without consent below.</p>
99
+ <h2 id="the-four-categories-we-use" tabindex="-1">The four categories we use</h2>
100
+ <p>Every entry in the table below belongs to exactly one of these four categories. The banner and the
101
+ preference centre use the same four names, so what you agree to and what this policy describes are the same
102
+ thing.</p>
103
+ <h3 id="1-strictly-necessary-no-consent-because-the-service-cannot-run-without-them" tabindex="-1">1. Strictly necessary — no consent, because the Service cannot run without them</h3>
104
+ <p>These are the ones we set because you asked for a service that cannot be delivered otherwise. They are not
105
+ optional, they are not used for analytics or marketing, and there is no switch for them in the preference
106
+ centre. If you block them at the browser level, parts of the Service will stop working.</p>
107
+ <ul>
108
+ <li><strong>Session and authentication</strong> — signing you in, keeping you signed in, refreshing your session, and
109
+ binding it to the correct account, workspace and organisation.</li>
110
+ <li><strong>Security</strong> — protection against cross-site request forgery, detection of abusive automated traffic, rate
111
+ limiting, and fraud prevention on sign-up and payment.</li>
112
+ <li><strong>Load balancing and routing</strong> — sending your request to a healthy server and keeping you there where a
113
+ feature needs it.</li>
114
+ <li><strong>Your consent choice</strong> — storing what you decided, so that we can honour it and stop asking.</li>
115
+ </ul>
116
+ <p>Error and crash diagnostics are <strong>not</strong> in this category by default. Where we use a diagnostics tool that
117
+ records more than a technical error — a reconstruction of what was on your screen, for example — it is
118
+ listed under analytics and it waits for your consent.</p>
119
+ <h4 id="recaptcha-is-in-this-category-and-here-is-our-reasoning" tabindex="-1">reCAPTCHA is in this category, and here is our reasoning</h4>
120
+ <p>We use Google reCAPTCHA — and on some surfaces an alternative provider, named in the table below — to stop
121
+ automated abuse of forms such as sign-up, password reset and contact. <strong>We treat it as strictly necessary,
122
+ which means it loads without asking you first.</strong></p>
123
+ <p>The reason is that it protects the specific form you are trying to use. You cannot meaningfully ask for the
124
+ form and refuse the protection on it: without it, those endpoints are abused within hours, which is a
125
+ security failure that harms you as much as us.</p>
126
+ <p>What that means in practice, stated plainly:</p>
127
+ <ul>
128
+ <li>It collects device and behaviour signals from your browser — mouse and touch movement, timing, browser and
129
+ device characteristics, and your IP address — and <strong>sends them to Google, which acts as its own controller
130
+ for that data under its own privacy notice.</strong></li>
131
+ <li>We load it only on pages carrying a protected form. It is not present across the whole site.</li>
132
+ <li>Where an equivalent provider is available on a surface, we prefer the one that collects less.</li>
133
+ </ul>
134
+ <p><strong>Not every data protection authority accepts that a bot-protection service belongs in the strictly
135
+ necessary category.</strong> We think it does, for the reason above, and we would rather publish the reasoning and
136
+ let you judge it than bury the tool in a list. If you would prefer not to submit a form protected this way,
137
+ write to privacy@ever.co and we will take it from you another way.</p>
138
+ <h3 id="2-functional-and-preferences-consent-required" tabindex="-1">2. Functional and preferences — consent required</h3>
139
+ <p>These remember choices you have made so that the Service behaves the way you left it: language, time zone,
140
+ theme, layout, dismissed messages, and support or chat widgets where we offer them.</p>
141
+ <p><strong>Refusing this category costs you convenience, not access.</strong> Everything still works; it simply forgets your
142
+ preferences between visits and you set them again.</p>
143
+ <h3 id="3-analytics-consent-required" tabindex="-1">3. Analytics — consent required</h3>
144
+ <p>These tell us how the Service is used: which pages and features are used, which paths people abandon, what
145
+ is slow, and what fails. Depending on the surface this may include a provider's own persistent identifier
146
+ and, where the table says so, a masked reconstruction of a session.</p>
147
+ <p>Third-party analytics tools are <strong>off until you turn them on</strong>, and nothing in this category loads before you
148
+ choose.</p>
149
+ <p>There is one deliberate exception, and it is the subject of the next section: <strong>our own analytics, running on
150
+ our own servers, is designed to operate without a consent requirement</strong> — cookieless, with no persistent
151
+ identifier and aggregate reporting only. The next section sets out exactly what that involves and the
152
+ conditions it depends on.</p>
153
+ <h3 id="4-marketing-consent-required" tabindex="-1">4. Marketing — consent required</h3>
154
+ <p>These measure whether our marketing works and help us understand who is interested in the product:
155
+ attribution of a sign-up to the campaign that produced it, and business-audience identification tools.</p>
156
+ <p>One of these deserves a plain sentence rather than a euphemism. <strong>Visitor identification tools resolve a
157
+ visitor's IP address to the organisation it belongs to, so that we can see which companies have looked at
158
+ the product.</strong> They do not tell us your name, but most people do not expect a website to work out their
159
+ employer, so we would rather say it here than let you find it in a table. It is off unless you consent.</p>
160
+ <h3 id="no-cookie-walls-ever" tabindex="-1">No cookie walls, ever</h3>
161
+ <p><strong>We do not use cookie walls, and we never make access conditional on consenting to non-essential cookies.</strong></p>
162
+ <p>You can refuse everything except the strictly necessary category and the whole of the Service remains
163
+ available to you — the same features, the same content, the same price. We do not offer a &quot;consent or pay&quot;
164
+ alternative. We do not degrade the experience, hide content, or nag you on every page because you said no.
165
+ Refusing is a decision we record and respect, not a negotiating position.</p>
166
+ <h2 id="our-own-analytics-and-why-it-runs-without-asking-you" tabindex="-1">Our own analytics, and why it runs without asking you</h2>
167
+ <p>We want to know whether the Service works — which pages load, which fail, whether a change made things
168
+ better or worse. That is a legitimate thing for us to want, and it is also the reason most websites hand
169
+ their visitors to a third-party analytics company. <strong>We built ours the other way round: we run our own
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. The
172
+ table below names the software and where it runs.</p>
173
+ <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
+ <ul>
175
+ <li><strong>It sets no cookies.</strong> Nothing is written to your device — no cookie, no local storage entry, nothing.</li>
176
+ <li><strong>It creates no persistent identifier.</strong> There is no visitor ID that follows you from one day to the next.</li>
177
+ <li><strong>It does not track you across sites or across devices.</strong> It measures our own site only. It has no
178
+ presence anywhere else, so there is nothing to join up.</li>
179
+ <li><strong>It counts visits using a hash that is salted and rotated daily.</strong> A one-way value is derived from your
180
+ IP address and browser details together with a secret salt, purely to tell one visit apart from another
181
+ within a single day. <strong>We change the salt every day, which breaks the link between today's value and
182
+ tomorrow's by design.</strong> The inputs are not stored.</li>
183
+ <li><strong>It reports only in aggregate</strong> — page counts, referrers, countries, browsers. No profile of you, no
184
+ individual visitor record to open, nothing to hand to a marketing tool.</li>
185
+ <li><strong>It keeps data for a bounded period,</strong> stated in the table below, after which the underlying records go
186
+ and only aggregate statistics remain.</li>
187
+ <li><strong>It is never used for advertising,</strong> and the data is not sold, shared for anyone else's purposes, or
188
+ combined with data from another source.</li>
189
+ </ul>
190
+ <h3 id="why-this-can-run-without-consent-and-the-condition-attached" tabindex="-1">Why this can run without consent, and the condition attached</h3>
191
+ <p>Under the ePrivacy rules, storing information on your device or reading it back generally requires your
192
+ prior consent, with a narrow exemption for what is strictly necessary. European regulators — the French CNIL
193
+ most explicitly — have also published criteria under which a first-party audience-measurement tool can be
194
+ treated as exempt: it must serve only the operator's own site, produce only aggregate statistics, avoid
195
+ cross-site and cross-device tracking, avoid a persistent identifier, and keep data for a limited period.</p>
196
+ <p><strong>Our configuration is built to meet those criteria. That is the whole basis on which it runs without
197
+ asking you — and it is conditional on every one of the measures listed above.</strong></p>
198
+ <p>We are not claiming a general permission. If we ever changed any of it — a persistent identifier, a fixed
199
+ salt, measurement across more than one of our own sites, a third-party vendor, reporting at the level of an
200
+ individual visitor — <strong>the exemption would no longer apply, and we would move this tool into the analytics
201
+ category and ask for your consent before making the change.</strong> The category is a configuration setting in our
202
+ consent system, not a paragraph in this document, precisely so that it can be changed the moment the facts
203
+ change.</p>
204
+ <p>One further distinction worth being precise about. The exemption above is about <strong>storage on your device</strong>.
205
+ Where the resulting data is still personal data, the separate question of a lawful basis under data
206
+ protection law arises, and ours is our legitimate interest in understanding whether our own service works —
207
+ assessed against the fact that the measurement is aggregate, short-lived and cannot be traced back to you.
208
+ <strong>You can object to that processing</strong>, and the paragraph below is how.</p>
209
+ <h3 id="you-can-switch-it-off-anyway" tabindex="-1">You can switch it off anyway</h3>
210
+ <p>You do not have to accept our reasoning to escape the measurement.</p>
211
+ <ul>
212
+ <li>Open <strong>Cookie preferences</strong> from the footer of any page. Our own analytics appears there with a switch,
213
+ even though it runs without consent, and turning it off stops it.</li>
214
+ <li>Blocking it at the browser or network level also works, and we do not try to detect or defeat that.</li>
215
+ <li>Or write to privacy@ever.co and ask us to exclude you.</li>
216
+ </ul>
217
+ <p><strong>We do not ask for a reason and we do not require an account.</strong></p>
218
+ <h3 id="separately-and-only-with-your-consent-we-also-use-third-party-tools" tabindex="-1">Separately, and only with your consent, we also use third-party tools</h3>
219
+ <p>Alongside our own analytics we use third-party analytics and marketing products. Those are a genuinely
220
+ different proposition: another company receives the data, they typically use a persistent identifier of
221
+ their own, and some are capable of following a visitor across other sites entirely.</p>
222
+ <p><strong>Nothing in that group runs until you consent to it</strong>, and none of it is covered by the exemption described
223
+ above. Each tool is named in the table below, with what it does, who operates it, and how long anything it
224
+ stores lasts.</p>
225
+ <h2 id="annex-ever-demand-what-runs-on-each-surface" tabindex="-1">Annex: Ever Demand — what runs on each surface</h2>
226
+ <h3 id="where-this-policy-applies-and-where-it-does-not" tabindex="-1">Where this policy applies, and where it does not</h3>
227
+ <p>We operate three things under this name, and this policy covers all three and nothing else:</p>
228
+ <ul>
229
+ <li>the website at <a href="https://everdemand.co">everdemand.co</a>;</li>
230
+ <li>the documentation site at <a href="https://docs.everdemand.co">docs.everdemand.co</a>; and</li>
231
+ <li>the content management system behind the website, which only our own editors sign in to.</li>
232
+ </ul>
233
+ <p><strong>There is no hosted Ever Demand platform.</strong> No shopping site, merchant console, administration console
234
+ or courier application is operated by us at any address, so there is no application surface here for this
235
+ policy to describe.</p>
236
+ <p><strong>A deployment somebody else runs is not covered.</strong> The shopping site a business built on this software sets
237
+ its own cookies, on its own domain, under its own notice. The section near the end says what the software
238
+ stores in a browser and on a device, so that an operator can write that notice from facts rather than
239
+ guesswork — but it is that operator's notice to write, and ours does not do the job for them.</p>
240
+ <h3 id="1-the-website-at-everdemandco" tabindex="-1">1. The website at <a href="https://everdemand.co">everdemand.co</a></h3>
241
+ <table>
242
+ <thead>
243
+ <tr>
244
+ <th>Technology</th>
245
+ <th>Provider</th>
246
+ <th>Category</th>
247
+ <th>Consent</th>
248
+ <th>What it is for</th>
249
+ </tr>
250
+ </thead>
251
+ <tbody>
252
+ <tr>
253
+ <td>Edge, routing and bot-filtering cookies</td>
254
+ <td>Cloudflare</td>
255
+ <td>Strictly necessary</td>
256
+ <td>Not required</td>
257
+ <td>Getting your request to the site, absorbing attack traffic, telling a person apart from a hostile script</td>
258
+ </tr>
259
+ <tr>
260
+ <td>Consent record</td>
261
+ <td>iubenda</td>
262
+ <td>Strictly necessary</td>
263
+ <td>Not required</td>
264
+ <td>Storing what you chose, so we can honour it and stop asking</td>
265
+ </tr>
266
+ <tr>
267
+ <td>reCAPTCHA</td>
268
+ <td>Google</td>
269
+ <td>Strictly necessary</td>
270
+ <td>Not required</td>
271
+ <td>Stopping automated abuse of the contact, pricing-notification and newsletter forms. Read the next section — on the current build it loads on every page, not only on the ones carrying a form</td>
272
+ </tr>
273
+ <tr>
274
+ <td>Google Analytics 4, delivered through a tag container</td>
275
+ <td>Google</td>
276
+ <td>Analytics</td>
277
+ <td>Required</td>
278
+ <td>Which pages and campaigns bring people to the site, and where people give up</td>
279
+ </tr>
280
+ <tr>
281
+ <td>Product analytics</td>
282
+ <td>PostHog</td>
283
+ <td>Analytics</td>
284
+ <td>Required</td>
285
+ <td>Page views and events, on the environments where a key is configured</td>
286
+ </tr>
287
+ <tr>
288
+ <td>Business visitor identification</td>
289
+ <td>Leadfeeder</td>
290
+ <td>Marketing</td>
291
+ <td>Required</td>
292
+ <td>Resolving your IP address to the organisation it belongs to, so that we can see which companies have looked at the product</td>
293
+ </tr>
294
+ </tbody>
295
+ </table>
296
+ <p><strong>The last three rows say &quot;required&quot; because that is what this site is meant to do.</strong> The next section is
297
+ about the fact that today it does not.</p>
298
+ <h3 id="the-defect-on-this-site-named-rather-than-left-for-you-to-find" tabindex="-1">The defect on this site, named rather than left for you to find</h3>
299
+ <p><strong>On the build of <a href="https://everdemand.co">everdemand.co</a> running as this policy is published, the consent
300
+ banner does not gate the analytics and marketing tools.</strong> The tag container and the visitor-identification
301
+ script are loaded as ordinary page scripts sitting alongside the banner rather than behind it. Nothing
302
+ listens for your decision, and nothing is held back by it, so they run when the page loads whatever you
303
+ choose.</p>
304
+ <p><strong>Two smaller things follow from the same mistake.</strong> reCAPTCHA loads on every page of this site rather than
305
+ only on the pages carrying a protected form, which is narrower than the commitment made in the section above.
306
+ And the consent record is stored, so your choice is captured accurately — it simply is not acted on.</p>
307
+ <p>We are not going to write this up as policy and hope you do not check. <strong>The table above is what this site is
308
+ supposed to do, and what it will do once those scripts are moved behind the consent decision</strong>, which is how
309
+ our other sites already work. Until that ships:</p>
310
+ <ul>
311
+ <li><strong>Blocking these tools in your browser or at the network level works</strong>, and we do not try to detect or
312
+ defeat it.</li>
313
+ <li>Writing to privacy@ever.co and asking to be excluded also works. We do not ask for a reason and we do
314
+ not require an account.</li>
315
+ <li>If you have already loaded the site and want what was collected removed, the same address is the route, and
316
+ you do not have to explain yourself.</li>
317
+ </ul>
318
+ <h3 id="things-on-this-site-that-are-not-cookies-but-are-still-disclosures" tabindex="-1">Things on this site that are not cookies but are still disclosures</h3>
319
+ <p>None of these stores anything on your device. Each of them still sends something about you to somebody else,
320
+ so naming them is the point.</p>
321
+ <ul>
322
+ <li><strong>Error monitoring.</strong> When a page fails, a report goes to Sentry carrying your IP address, your browser, the
323
+ page you were on and the context around the failure. It runs on all three surfaces and it is not waiting for
324
+ a consent choice, because it is not measuring you — it exists so that a fault is visible to us with enough
325
+ detail to fix it. <strong>We do not run session replay or screen reconstruction on any of these surfaces.</strong> If you
326
+ would rather not be in those reports, privacy@ever.co will exclude you.</li>
327
+ <li><strong>Sending us a form.</strong> Using the contact form or the pricing-notification form sends what you wrote through
328
+ Postmark, which delivers the email to us.</li>
329
+ <li><strong>Subscribing.</strong> Joining the newsletter sends your address to Mailchimp, which holds the list.</li>
330
+ <li><strong>Opening the chat.</strong> The support chat widget is Chatwoot, and it starts a conversation record — your
331
+ message, your page, your IP address — when you open it, not before.</li>
332
+ </ul>
333
+ <h3 id="2-the-documentation-site" tabindex="-1">2. The documentation site</h3>
334
+ <table>
335
+ <thead>
336
+ <tr>
337
+ <th>Technology</th>
338
+ <th>Provider</th>
339
+ <th>Category</th>
340
+ <th>Consent</th>
341
+ <th>What it is for</th>
342
+ </tr>
343
+ </thead>
344
+ <tbody>
345
+ <tr>
346
+ <td>Edge and security cookies</td>
347
+ <td>Cloudflare</td>
348
+ <td>Strictly necessary</td>
349
+ <td>Not required</td>
350
+ <td>Routing and filtering, as above</td>
351
+ </tr>
352
+ <tr>
353
+ <td>Theme and navigation preferences, held in your browser's local storage</td>
354
+ <td>Us</td>
355
+ <td>Functional</td>
356
+ <td>Required</td>
357
+ <td>Remembering dark mode and which sections you collapsed</td>
358
+ </tr>
359
+ <tr>
360
+ <td>Documentation search</td>
361
+ <td>Algolia</td>
362
+ <td>Functional</td>
363
+ <td>Required</td>
364
+ <td>Searching the documentation, where the search keys are configured for that site. <strong>Where they are not, search runs entirely in your browser and sends nothing to anyone</strong></td>
365
+ </tr>
366
+ </tbody>
367
+ </table>
368
+ <p>There is no analytics and no marketing tool on the documentation site.</p>
369
+ <h3 id="3-the-content-management-system" tabindex="-1">3. The content management system</h3>
370
+ <p>This is a staff surface. A visitor to the public website never reaches it, and nothing about you as a reader
371
+ is processed there.</p>
372
+ <table>
373
+ <thead>
374
+ <tr>
375
+ <th>Technology</th>
376
+ <th>Provider</th>
377
+ <th>Category</th>
378
+ <th>Consent</th>
379
+ <th>What it is for</th>
380
+ </tr>
381
+ </thead>
382
+ <tbody>
383
+ <tr>
384
+ <td>Session and sign-in cookies</td>
385
+ <td>Us</td>
386
+ <td>Strictly necessary</td>
387
+ <td>Not required</td>
388
+ <td>Signing an editor in and keeping them signed in</td>
389
+ </tr>
390
+ <tr>
391
+ <td>Cross-site request forgery token</td>
392
+ <td>Us</td>
393
+ <td>Strictly necessary</td>
394
+ <td>Not required</td>
395
+ <td>Stopping another site submitting a request as a signed-in editor</td>
396
+ </tr>
397
+ <tr>
398
+ <td>Edge and security cookies</td>
399
+ <td>Cloudflare</td>
400
+ <td>Strictly necessary</td>
401
+ <td>Not required</td>
402
+ <td>Routing and filtering, as above</td>
403
+ </tr>
404
+ </tbody>
405
+ </table>
406
+ <p>No analytics, no marketing tools, no third-party measurement of any kind.</p>
407
+ <h3 id="our-own-analytics-does-not-run-here" tabindex="-1">Our own analytics does not run here</h3>
408
+ <p>The section above describes audience measurement we run on our own servers, cookieless and without a
409
+ persistent identifier, and explains why it does not need to ask you. <strong>None of it is deployed on these three
410
+ surfaces.</strong> The only audience measurement on this product's website is Google's, and it belongs in the
411
+ analytics category where consent is required. The exemption described earlier is not doing any work here, and
412
+ we would rather say so than let you assume the gentler arrangement applies.</p>
413
+ <h3 id="the-mobile-applications-need-a-different-section-because-cookies-are-the-wrong-word" tabindex="-1">The mobile applications need a different section, because cookies are the wrong word</h3>
414
+ <p>The shopping, merchant and courier applications are not browsers. What they hold is device identifiers rather
415
+ than cookies, and the operator who publishes a build decides all of it:</p>
416
+ <ul>
417
+ <li><strong>A device record</strong> — a device identifier, the platform, the language and a push channel identifier — is
418
+ created so that the platform can send an order or an invite to the right handset.</li>
419
+ <li><strong>Sign-in state is held on the device</strong>, in application storage rather than in a cookie. The website leg of
420
+ social sign-in uses a server-side session cookie.</li>
421
+ <li><strong>Google Analytics, Mixpanel and Intercom are compiled into all three applications</strong>, including the courier
422
+ application, and the courier build additionally carries a plugin that reads a unique device identifier. Each
423
+ of these is inert until the operator supplies a key and ships a build containing it.</li>
424
+ </ul>
425
+ <p><strong>Analytics inside a worker's application is a harder problem than analytics in a shopper's application, and
426
+ it should not be treated as the same decision.</strong> A shopper can uninstall. A courier who was given the
427
+ application to do a job cannot, and an in-app tracking prompt put in front of someone whose employer issued
428
+ the device is not a free choice. An operator switching those keys on for the courier build is measuring a
429
+ worker, and the acceptable use annex to this product says what that requires.</p>
430
+ <p>App-store privacy labels and the operating system's own tracking prompt belong to whoever publishes the
431
+ build. <strong>That is the operator, not us.</strong></p>
432
+ <h3 id="if-you-run-the-software-yourself" tabindex="-1">If you run the software yourself</h3>
433
+ <p>The platform stores a signed access token and interface state in the browser or the application, and sets a
434
+ server-side session cookie on the social sign-in legs. Beyond that, <strong>every tracker in a deployment is one the
435
+ operator added</strong>: the maps key, the analytics keys, any tag you drop into the shopping site, and anything your
436
+ own marketing team wants.</p>
437
+ <p>Your cookie notice, your banner and your consent record are yours. The legal pages bundled inside the software
438
+ are not a consent mechanism and were never one, and ours governs our three surfaces rather than your shop.</p>
439
+ <h3 id="selling-sharing-and-global-privacy-control" tabindex="-1">Selling, sharing, and Global Privacy Control</h3>
440
+ <p><strong>We do not sell personal data, and we do not share it for cross-context behavioural advertising.</strong> There is
441
+ no sale here to opt out of, and no advertising network receives anything from these surfaces.</p>
442
+ <p>Our banner is configured to recognise a Global Privacy Control signal as a refusal of the analytics and
443
+ marketing categories. <strong>Given the defect described above, browser-level or network-level blocking is currently
444
+ the route that certainly works</strong>, and we would rather tell you that than have you rely on a signal that is
445
+ being recorded correctly and acted on late.</p>
446
+ <h2 id="third-party-cookies-and-the-providers-behind-them" tabindex="-1">Third-party cookies and the providers behind them</h2>
447
+ <p>Some of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is
448
+ there — but the provider decides what its own technology collects, and for that collection it is usually
449
+ acting in its own right and under its own privacy notice rather than ours. Where that is the case, the table
450
+ below links to their notice.</p>
451
+ <p>These are the kinds of provider involved, and what each kind does.</p>
452
+ <h3 id="analytics-providers" tabindex="-1">Analytics providers</h3>
453
+ <p>Measure how the Service is used: page views, feature use, funnels, errors and performance. Most set a
454
+ persistent identifier of their own so a returning visitor is recognised, and some can record a <strong>session
455
+ replay</strong> — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do
456
+ that, the table says so explicitly.</p>
457
+ <p><strong>Consent required.</strong> They do not load until you agree.</p>
458
+ <h3 id="tag-management" tabindex="-1">Tag management</h3>
459
+ <p>A tag manager is a container we load once, through which other tags can then be delivered without shipping
460
+ new code. That flexibility is exactly what makes it worth describing carefully: <strong>a container is a delivery
461
+ mechanism, so what it delivers matters more than the container itself.</strong></p>
462
+ <p>Every tag we deliver through a container is declared in the table below, in its own category. The container
463
+ is consent-gated as a whole, and <strong>we do not use it to deliver anything from a category you have refused.</strong></p>
464
+ <p><strong>Consent required.</strong></p>
465
+ <h3 id="marketing-and-visitor-identification" tabindex="-1">Marketing and visitor identification</h3>
466
+ <p>Campaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —
467
+ and business-audience identification, which resolves a visitor's IP address to the organisation that holds
468
+ it so we can see which companies are interested in the product. It gives us a company, not your name. Most
469
+ people still do not expect it, which is why it is named here as well as in the table.</p>
470
+ <p><strong>Consent required.</strong></p>
471
+ <h3 id="video-maps-fonts-and-other-embedded-content" tabindex="-1">Video, maps, fonts and other embedded content</h3>
472
+ <p>Where a page embeds something served from another provider's network — a video player, a map, a code
473
+ sandbox, a font, a script from a public content delivery network — your browser fetches it directly from
474
+ that provider.</p>
475
+ <p><strong>That fetch discloses your IP address, your browser and the page you were on to the provider, whether or
476
+ not anything is stored on your device.</strong> There is no way to embed a resource and hide the request for it.</p>
477
+ <p>We handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party
478
+ entirely; and where an embed stores or reads anything on your device, we treat it as <strong>consent required</strong>
479
+ and it does not load until you agree. Embeds that store nothing but are still fetched from a third party are
480
+ listed in the table so you can see the disclosure even where no cookie is involved.</p>
481
+ <h3 id="security-and-delivery" tabindex="-1">Security and delivery</h3>
482
+ <p>The network in front of our sites — the proxy and content delivery layer that terminates the connection,
483
+ absorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on
484
+ payment. These see connection metadata and may set their own security cookies.</p>
485
+ <p><strong>Strictly necessary</strong>, and therefore not consent-gated. Our reasoning for putting bot protection in that
486
+ category, including what it sends to its provider, is set out in the categories section above.</p>
487
+ <h3 id="where-these-providers-are-and-where-to-find-the-full-list" tabindex="-1">Where these providers are, and where to find the full list</h3>
488
+ <p>Some of these providers are established outside the European Economic Area, and using them involves an
489
+ international transfer of personal data. <strong>The transfers section of our
490
+ <a href="https://everdemand.co/privacy">Privacy Policy</a> sets out the destinations and the safeguards we rely on for each</strong>,
491
+ and you can ask us for a copy of those safeguards.</p>
492
+ <p>Two lists keep this current, and between them they are the authoritative answer:</p>
493
+ <ul>
494
+ <li><strong>The table in the product-specific section below</strong> names every cookie and similar technology in use on
495
+ this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,
496
+ how long it lasts, and a link to the provider's own notice.</li>
497
+ <li><strong>Our Sub-processor List</strong> covers the wider set of providers that process personal data for us, including
498
+ the many that never touch your device at all. You can obtain the current version at any time from
499
+ privacy@ever.co, and it names the sub-processor, what it does, and where it processes.</li>
500
+ </ul>
501
+ <p>We update both when a provider is added, removed or changed. If you find something on our pages that is not
502
+ in either list, tell us at privacy@ever.co — that is a defect and we will fix it.</p>
503
+ <h2 id="consent-and-how-to-withdraw-it" tabindex="-1">Consent, and how to withdraw it</h2>
504
+ <h3 id="how-the-banner-works" tabindex="-1">How the banner works</h3>
505
+ <p>On your first visit we show a consent banner, and <strong>nothing in the functional, analytics or marketing
506
+ categories is written to or read from your device until you have made a choice.</strong> The strictly necessary
507
+ items load, because the page cannot be delivered otherwise. Everything else waits.</p>
508
+ <p>The first layer of the banner — the one you see without clicking anything further — carries both a
509
+ <strong>Reject all</strong> and an <strong>Accept all</strong> control, presented with equal prominence. <strong>Refusing everything takes
510
+ one click, exactly like accepting everything.</strong> Alongside them is a route into per-category choice, so you
511
+ can accept analytics and refuse marketing, or any other combination.</p>
512
+ <p>Three things that some banners do and ours does not:</p>
513
+ <ul>
514
+ <li><strong>No pre-ticked boxes.</strong> Every category except strictly necessary starts switched off.</li>
515
+ <li><strong>Closing the banner is not consent.</strong> Neither is dismissing it, scrolling past it, or carrying on
516
+ browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.</li>
517
+ <li><strong>No dark patterns.</strong> We do not make the reject control smaller, greyer, slower or harder to find than the
518
+ accept control, and we do not hide it a layer down.</li>
519
+ </ul>
520
+ <h3 id="changing-your-mind" tabindex="-1">Changing your mind</h3>
521
+ <p><strong>Withdrawing consent is as easy as giving it, and you can do it at any time.</strong></p>
522
+ <p>There is a persistent <strong>Cookie preferences</strong> link in the footer of every page, and an equivalent entry
523
+ inside the application's settings. It opens the same per-category controls you saw in the banner, showing
524
+ what you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we
525
+ remove what was stored.</p>
526
+ <p>Two honest limits on that:</p>
527
+ <ul>
528
+ <li><strong>Withdrawal works forwards, not backwards.</strong> It does not make lawful past processing unlawful, and it
529
+ does not reach into data a third-party provider already received. If you want that deleted too, ask us at
530
+ privacy@ever.co and we will tell you who holds it and how to ask them.</li>
531
+ <li><strong>Your choice is stored on the device and browser you made it on.</strong> A different browser, a different
532
+ device or a private window will ask again, because there is nothing there to read. Clearing your browser
533
+ storage deletes the record of your refusal as well, which is why the banner reappears afterwards.</li>
534
+ </ul>
535
+ <h3 id="the-record-we-keep" tabindex="-1">The record we keep</h3>
536
+ <p>When you make a choice we record what you chose, when you chose it, which categories it covered, and which
537
+ version of this policy was in force at the time. That record exists for two reasons: so that we honour your
538
+ choice, and so that we can show what you were asked and what you answered.</p>
539
+ <p>You can ask us for a copy of your own consent record at privacy@ever.co.</p>
540
+ <h3 id="how-long-a-choice-lasts-before-we-ask-again" tabindex="-1">How long a choice lasts before we ask again</h3>
541
+ <p>We store a consent choice for <strong>six months</strong>. After that the banner appears again so you can confirm or
542
+ change it. We will also ask again sooner if we add a purpose or a category your earlier choice did not
543
+ cover, or if this policy changes in a way that materially affects what you agreed to.</p>
544
+ <p><strong>This is our own practice, not a legal requirement.</strong> There is no EU-wide statutory interval for asking
545
+ again — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to
546
+ apply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same
547
+ six months, and blocking storage at the browser level stops the question permanently.</p>
548
+ <h2 id="controls-in-your-browser-and-on-your-device" tabindex="-1">Controls in your browser and on your device</h2>
549
+ <p>Our banner is not the only way to control this, and it is not the strongest one. Your browser and your
550
+ operating system can enforce a choice on every site at once, including ours.</p>
551
+ <h3 id="in-a-browser" tabindex="-1">In a browser</h3>
552
+ <p>Every major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under
553
+ privacy or site settings:</p>
554
+ <ul>
555
+ <li><strong>Delete cookies and site data</strong>, for one site or all of them.</li>
556
+ <li><strong>Block cookies</strong>, either all of them or only those set by third parties.</li>
557
+ <li><strong>Clear storage on exit</strong>, so nothing survives the session.</li>
558
+ <li><strong>Private or incognito windows</strong>, which discard everything when the window closes.</li>
559
+ <li><strong>Per-site permissions</strong>, so you can allow storage on the sites you use and block it everywhere else.</li>
560
+ </ul>
561
+ <p>Your browser's own help pages describe exactly where these live in your version — we deliberately do not
562
+ reproduce click-by-click instructions here, because they go stale faster than this document does.</p>
563
+ <p>Content blockers and privacy extensions work on our sites too. <strong>Using one is a legitimate choice</strong>, and we
564
+ build the Service so that it keeps working when the optional things are blocked.</p>
565
+ <h3 id="in-our-desktop-and-mobile-applications" tabindex="-1">In our desktop and mobile applications</h3>
566
+ <p>An installed application has no browser settings to change, so the controls are at the operating-system
567
+ level instead:</p>
568
+ <ul>
569
+ <li>Reset or limit the <strong>advertising identifier</strong> your device provides.</li>
570
+ <li>Answer <strong>no</strong> to the app-tracking permission prompt on iOS, which stops access to that identifier
571
+ entirely.</li>
572
+ <li>Withdraw <strong>notification permission</strong>, which stops the push token being useful.</li>
573
+ <li>Clear the application's stored data, or uninstall it, which removes everything it kept locally.</li>
574
+ </ul>
575
+ <p>The <strong>Cookie preferences</strong> controls described above are also available inside the application, and they
576
+ govern the same categories there as on the website.</p>
577
+ <h3 id="what-breaks-if-you-block-the-strictly-necessary-ones" tabindex="-1">What breaks if you block the strictly necessary ones</h3>
578
+ <p>Blocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to
579
+ expect:</p>
580
+ <ul>
581
+ <li><strong>You will not be able to sign in, or stay signed in.</strong> Authentication needs somewhere to keep the
582
+ session.</li>
583
+ <li><strong>Forms may fail their security check</strong> and refuse to submit.</li>
584
+ <li><strong>Some features will behave inconsistently</strong>, because requests can no longer be kept on the same server.</li>
585
+ <li><strong>We cannot remember that you refused.</strong> The record of your choice is itself stored on your device, so
586
+ blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and
587
+ it comes from the mechanism rather than from us being difficult.</li>
588
+ </ul>
589
+ <h3 id="do-not-track" tabindex="-1">Do Not Track</h3>
590
+ <p>Browsers once offered a <strong>Do Not Track</strong> header, and some still do. <strong>We do not treat it, on its own, as a
591
+ refusal</strong> — and we would rather explain why than quietly ignore it.</p>
592
+ <p>No consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether
593
+ it expressed a considered decision or a default someone else had set, browsers behaved differently, and
594
+ several have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.</p>
595
+ <p>Use the banner or the preference centre instead. A choice made there is unambiguous, and we record it.</p>
596
+ <h3 id="global-privacy-control" tabindex="-1">Global Privacy Control</h3>
597
+ <p><strong>Global Privacy Control (GPC)</strong> is the later, better-specified signal, and unlike Do Not Track it is
598
+ defined to express an actual opt-out rather than a preference.</p>
599
+ <p><strong>Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing
600
+ categories</strong> on that browser, and we act on it without waiting for you to interact with a banner.</p>
601
+ <p>Two points of detail:</p>
602
+ <ul>
603
+ <li>It applies to the browser or device sending it. Another browser sends its own signal, or none.</li>
604
+ <li><strong>An explicit choice you make later in our preference centre takes precedence</strong>, in either direction. If
605
+ you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as
606
+ such. If you would rather that never happened, leave the categories switched off.</li>
607
+ </ul>
608
+ <h2 id="changes-to-this-policy" tabindex="-1">Changes to this policy</h2>
609
+ <p>We update this policy when what we do changes — a provider added or removed, a technology retired, a
610
+ category reassigned. Every update gets its own version number and effective date, recorded at the end of
611
+ this document.</p>
612
+ <p><strong>Where a change materially affects what you agreed to</strong> — a new purpose, a new category, or a tool moving
613
+ out of the strictly necessary or exempt group — <strong>we ask for your consent again rather than relying on the
614
+ choice you made against the old text.</strong> Corrections, clarifications and provider renames are published with
615
+ a new version and no fresh request.</p>
616
+ <p>Earlier versions stay available, with the dates each was in force, at
617
+ <a href="https://everdemand.co/cookies">https://everdemand.co/cookies</a>. The effective date shown with this policy tells you which
618
+ version applies today.</p>
619
+ <h2 id="how-to-reach-us" tabindex="-1">How to reach us</h2>
620
+ <p>Questions about this policy, about anything in the table above, or about a choice you have made — write to
621
+ privacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent
622
+ record, for the current sub-processor list, or to be excluded from our own analytics, and we will do it
623
+ without asking why.</p>
624
+ <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
625
+ number 204599535. We correspond in English.</p>
626
+ <p>If you think we have handled your data badly, tell us first — we would rather fix it. <strong>You can also
627
+ complain to a data protection supervisory authority at any time.</strong> Ours is the
628
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
629
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
630
+ to the authority for the country where you live or work.</p>
631
+ <p>This document is version 1.0.0 of the Cookie Policy for
632
+ <a href="https://everdemand.co">everdemand.co</a>, in force from 2026-08-02. Earlier versions, with the dates
633
+ they applied, are at <a href="https://everdemand.co/cookies">https://everdemand.co/cookies</a>.</p>