@ever-co/legal 0.1.2 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (82) hide show
  1. package/dist/content/aup/ever-async/en.html +778 -0
  2. package/dist/content/aup/ever-async/en.json +343 -0
  3. package/dist/content/aup/hust/en.html +9 -0
  4. package/dist/content/aup/hust/en.json +2 -2
  5. package/dist/content/cookies/ever-async/en.html +457 -0
  6. package/dist/content/cookies/ever-async/en.json +185 -0
  7. package/dist/content/cookies/ever-demand/en.html +5 -2
  8. package/dist/content/cookies/ever-demand/en.json +2 -2
  9. package/dist/content/cookies/ever-rec/en.html +5 -2
  10. package/dist/content/cookies/ever-rec/en.json +2 -2
  11. package/dist/content/cookies/ever-teams/en.html +5 -2
  12. package/dist/content/cookies/ever-teams/en.json +2 -2
  13. package/dist/content/cookies/ever-works/en.html +5 -2
  14. package/dist/content/cookies/ever-works/en.json +2 -2
  15. package/dist/content/cookies/gauzy/en.html +5 -2
  16. package/dist/content/cookies/gauzy/en.json +2 -2
  17. package/dist/content/cookies/githands/en.html +5 -2
  18. package/dist/content/cookies/githands/en.json +2 -2
  19. package/dist/content/cookies/hust/en.html +5 -2
  20. package/dist/content/cookies/hust/en.json +2 -2
  21. package/dist/content/dpa/ever-async/en.html +1848 -0
  22. package/dist/content/dpa/ever-async/en.json +640 -0
  23. package/dist/content/privacy/ever-async/en.html +1350 -0
  24. package/dist/content/privacy/ever-async/en.json +364 -0
  25. package/dist/content/privacy/ever-corporate/en.html +86 -3
  26. package/dist/content/privacy/ever-corporate/en.json +2 -2
  27. package/dist/content/privacy/ever-demand/en.html +99 -2
  28. package/dist/content/privacy/ever-demand/en.json +2 -2
  29. package/dist/content/privacy/ever-rec/en.html +110 -3
  30. package/dist/content/privacy/ever-rec/en.json +2 -2
  31. package/dist/content/privacy/ever-teams/en.html +97 -1
  32. package/dist/content/privacy/ever-teams/en.json +2 -2
  33. package/dist/content/privacy/ever-tech/en.html +86 -3
  34. package/dist/content/privacy/ever-tech/en.json +2 -2
  35. package/dist/content/privacy/ever-works/en.html +74 -5
  36. package/dist/content/privacy/ever-works/en.json +2 -2
  37. package/dist/content/privacy/everiq/en.html +107 -0
  38. package/dist/content/privacy/everiq/en.json +2 -2
  39. package/dist/content/privacy/gauzy/en.html +88 -3
  40. package/dist/content/privacy/gauzy/en.json +2 -2
  41. package/dist/content/privacy/githands/en.html +83 -2
  42. package/dist/content/privacy/githands/en.json +2 -2
  43. package/dist/content/privacy/hust/en.html +186 -37
  44. package/dist/content/privacy/hust/en.json +3 -3
  45. package/dist/content/privacy/traduora/en.html +93 -0
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-rec/en.html +595 -0
  48. package/dist/content/refund/ever-rec/en.json +336 -0
  49. package/dist/content/security/ever-async/en.html +853 -0
  50. package/dist/content/security/ever-async/en.json +417 -0
  51. package/dist/content/subprocessors/ever-async/en.html +852 -0
  52. package/dist/content/subprocessors/ever-async/en.json +166 -0
  53. package/dist/content/subprocessors/ever-corporate/en.html +403 -9
  54. package/dist/content/subprocessors/ever-corporate/en.json +6 -2
  55. package/dist/content/subprocessors/ever-demand/en.html +443 -13
  56. package/dist/content/subprocessors/ever-demand/en.json +6 -2
  57. package/dist/content/subprocessors/ever-rec/en.html +493 -10
  58. package/dist/content/subprocessors/ever-rec/en.json +6 -2
  59. package/dist/content/subprocessors/ever-teams/en.html +435 -8
  60. package/dist/content/subprocessors/ever-teams/en.json +6 -2
  61. package/dist/content/subprocessors/ever-tech/en.html +443 -9
  62. package/dist/content/subprocessors/ever-tech/en.json +6 -2
  63. package/dist/content/subprocessors/ever-works/en.html +354 -13
  64. package/dist/content/subprocessors/ever-works/en.json +6 -2
  65. package/dist/content/subprocessors/everiq/en.html +484 -3
  66. package/dist/content/subprocessors/everiq/en.json +6 -2
  67. package/dist/content/subprocessors/gauzy/en.html +353 -20
  68. package/dist/content/subprocessors/gauzy/en.json +6 -2
  69. package/dist/content/subprocessors/githands/en.html +451 -13
  70. package/dist/content/subprocessors/githands/en.json +6 -2
  71. package/dist/content/subprocessors/hust/en.html +502 -12
  72. package/dist/content/subprocessors/hust/en.json +14 -2
  73. package/dist/content/subprocessors/traduora/en.html +461 -4
  74. package/dist/content/subprocessors/traduora/en.json +6 -2
  75. package/dist/content/tos/ever-async/en.html +1350 -0
  76. package/dist/content/tos/ever-async/en.json +687 -0
  77. package/dist/content/tos/ever-rec/en.html +40 -11
  78. package/dist/content/tos/ever-rec/en.json +5 -5
  79. package/dist/content/tos/hust/en.html +32 -8
  80. package/dist/content/tos/hust/en.json +10 -2
  81. package/dist/index.json +5338 -2148
  82. package/package.json +1 -1
@@ -0,0 +1,457 @@
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://async.ever.co">async.ever.co</a> and in the Ever Async hosted service — 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://async.ever.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://async.ever.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="annex-ever-async" tabindex="-1">Annex: Ever Async</h2>
167
+ <h3 id="this-is-the-shortest-list-in-our-range-and-it-is-short-because-there-is-nothing-here" tabindex="-1">This is the shortest list in our range, and it is short because there is nothing here</h3>
168
+ <p>Ever Async has four surfaces — the marketing site, the dashboard, the API and the documentation —
169
+ and between them they set <strong>one cookie</strong>.</p>
170
+ <table>
171
+ <thead>
172
+ <tr>
173
+ <th>Surface</th>
174
+ <th>What is stored</th>
175
+ <th>Provider</th>
176
+ <th>Category</th>
177
+ <th>Consent</th>
178
+ </tr>
179
+ </thead>
180
+ <tbody>
181
+ <tr>
182
+ <td>The dashboard</td>
183
+ <td><code>everasync_session</code>, the cookie that signs you in and keeps you signed in</td>
184
+ <td>First party</td>
185
+ <td>Strictly necessary</td>
186
+ <td>Not required</td>
187
+ </tr>
188
+ <tr>
189
+ <td>The dashboard</td>
190
+ <td>The session token, held in your browser's local storage so the interface can call the API as you</td>
191
+ <td>First party</td>
192
+ <td>Strictly necessary</td>
193
+ <td>Not required</td>
194
+ </tr>
195
+ <tr>
196
+ <td>The dashboard and the sites</td>
197
+ <td><code>theme</code>, the light or dark choice you clicked</td>
198
+ <td>First party</td>
199
+ <td>Preferences</td>
200
+ <td>Written because you asked for it — see below</td>
201
+ </tr>
202
+ <tr>
203
+ <td>The documentation</td>
204
+ <td>Sidebar and theme preferences kept by the documentation software</td>
205
+ <td>First party</td>
206
+ <td>Preferences</td>
207
+ <td>Written because you asked for it</td>
208
+ </tr>
209
+ <tr>
210
+ <td>Every surface</td>
211
+ <td>Short-lived bot-management and routing cookies from our edge network, set where a request is treated as automated</td>
212
+ <td>Cloudflare</td>
213
+ <td>Strictly necessary</td>
214
+ <td>Not required</td>
215
+ </tr>
216
+ <tr>
217
+ <td>Every surface</td>
218
+ <td><strong>Nothing else.</strong> No analytics, no tag manager, no advertising, no session replay, no error reporter, no visitor identification, no social plug-in, no embedded font service, no chat widget and no payment script</td>
219
+ <td>—</td>
220
+ <td>Not present</td>
221
+ <td>—</td>
222
+ </tr>
223
+ </tbody>
224
+ </table>
225
+ <h3 id="there-is-no-consent-banner-and-here-is-why" tabindex="-1">There is no consent banner, and here is why</h3>
226
+ <p><strong>We do not show one on any Ever Async surface, because there is nothing on these pages for a banner
227
+ to gate.</strong> No analytics tool, no marketing tag and no third-party script runs here in any circumstance. A
228
+ banner asking you to accept things that do not exist would be theatre, and it would make our disclosure
229
+ less trustworthy rather than more.</p>
230
+ <p>The one entry above that sits in a consent category deserves a straight answer rather than a category
231
+ label. <strong>The theme value is written at the moment you click the toggle and not before.</strong> It holds one
232
+ word, it is read only by the page you are on, it is never sent anywhere, and clearing site data removes
233
+ it. Never touch the toggle and nothing is written.</p>
234
+ <p><strong>The moment anything in the analytics, marketing or preferences categories is added to any of these
235
+ surfaces, the banner and the preference centre ship in the same change — before the tag, not after it.</strong>
236
+ That is the commitment, and the table above is how you check we kept it.</p>
237
+ <h3 id="we-run-no-analytics-here-at-all" tabindex="-1">We run no analytics here at all</h3>
238
+ <p>Some of our products run our own analytics software on our own servers, configured so that there is
239
+ nothing about you worth asking permission for. <strong>Ever Async does not run that, or anything else.</strong>
240
+ The core section describing that arrangement is deliberately not published for this product, because it
241
+ would not be true here.</p>
242
+ <p>The absence is checkable rather than asserted. There is no measurement identifier, no tag container and no
243
+ analytics host in the service, the dashboard or the marketing site; <strong>the documentation site uses a search
244
+ index built at compile time specifically so that no search request leaves your browser at run time</strong>; and
245
+ the marketing site uses the fonts already on your device — no webfont is fetched from anyone.</p>
246
+ <h3 id="what-the-api-and-the-webhook-ingress-do" tabindex="-1">What the API and the webhook ingress do</h3>
247
+ <p>The API is called by the dashboard and by the chat platform's servers, not by your browser directly, and
248
+ <strong>it sets nothing on your device</strong>. The webhook ingress is contacted by Slack or Discord, never by you.</p>
249
+ <p>Everything that happens to what arrives there is in the <a href="https://async.ever.co/privacy">Privacy Policy</a> — this
250
+ document is only about what is stored on your device, and on the API the answer is nothing.</p>
251
+ <h3 id="your-chat-platforms-own-cookies-are-not-ours" tabindex="-1">Your chat platform's own cookies are not ours</h3>
252
+ <p>If Ever Async is connected to your workspace, you are already using Slack or Discord, and <strong>those products
253
+ set their own cookies under their own notices</strong>. Nothing in this policy governs them, we cannot change
254
+ them, and refusing anything here has no effect on them.</p>
255
+ <h2 id="third-party-cookies-and-the-providers-behind-them" tabindex="-1">Third-party cookies and the providers behind them</h2>
256
+ <p>Some of what runs on our pages belongs to other companies. We chose to include it, so we tell you it is
257
+ there — but the provider decides what its own technology collects, and for that collection it is usually
258
+ acting in its own right and under its own privacy notice rather than ours. Where that is the case, the table
259
+ below links to their notice.</p>
260
+ <p>These are the kinds of provider involved, and what each kind does.</p>
261
+ <h3 id="analytics-providers" tabindex="-1">Analytics providers</h3>
262
+ <p>Measure how the Service is used: page views, feature use, funnels, errors and performance. Most set a
263
+ persistent identifier of their own so a returning visitor is recognised, and some can record a <strong>session
264
+ replay</strong> — a reconstructed, masked playback of what happened on the screen. Where a tool on a surface can do
265
+ that, the table says so explicitly.</p>
266
+ <p><strong>Consent required.</strong> They do not load until you agree.</p>
267
+ <h3 id="tag-management" tabindex="-1">Tag management</h3>
268
+ <p>A tag manager is a container we load once, through which other tags can then be delivered without shipping
269
+ new code. That flexibility is exactly what makes it worth describing carefully: <strong>a container is a delivery
270
+ mechanism, so what it delivers matters more than the container itself.</strong></p>
271
+ <p>Every tag we deliver through a container is declared in the table below, in its own category. The container
272
+ is consent-gated as a whole, and <strong>we do not use it to deliver anything from a category you have refused.</strong></p>
273
+ <p><strong>Consent required.</strong></p>
274
+ <h3 id="marketing-and-visitor-identification" tabindex="-1">Marketing and visitor identification</h3>
275
+ <p>Campaign measurement and attribution — which advertisement, email or article led to a visit or a sign-up —
276
+ and business-audience identification, which resolves a visitor's IP address to the organisation that holds
277
+ it so we can see which companies are interested in the product. It gives us a company, not your name. Most
278
+ people still do not expect it, which is why it is named here as well as in the table.</p>
279
+ <p><strong>Consent required.</strong></p>
280
+ <h3 id="video-maps-fonts-and-other-embedded-content" tabindex="-1">Video, maps, fonts and other embedded content</h3>
281
+ <p>Where a page embeds something served from another provider's network — a video player, a map, a code
282
+ sandbox, a font, a script from a public content delivery network — your browser fetches it directly from
283
+ that provider.</p>
284
+ <p><strong>That fetch discloses your IP address, your browser and the page you were on to the provider, whether or
285
+ not anything is stored on your device.</strong> There is no way to embed a resource and hide the request for it.</p>
286
+ <p>We handle this in two ways: where we can serve the asset ourselves, we do, which removes the third party
287
+ entirely; and where an embed stores or reads anything on your device, we treat it as <strong>consent required</strong>
288
+ and it does not load until you agree. Embeds that store nothing but are still fetched from a third party are
289
+ listed in the table so you can see the disclosure even where no cookie is involved.</p>
290
+ <h3 id="security-and-delivery" tabindex="-1">Security and delivery</h3>
291
+ <p>The network in front of our sites — the proxy and content delivery layer that terminates the connection,
292
+ absorbs attacks and filters hostile traffic — along with bot protection on forms and fraud checks on
293
+ payment. These see connection metadata and may set their own security cookies.</p>
294
+ <p><strong>Strictly necessary</strong>, and therefore not consent-gated. Our reasoning for putting bot protection in that
295
+ category, including what it sends to its provider, is set out in the categories section above.</p>
296
+ <h4 id="measurement-injected-by-that-layer-which-our-banner-cannot-control" tabindex="-1">Measurement injected by that layer, which our banner cannot control</h4>
297
+ <p>There is one thing here we would rather state plainly than have you discover in a network trace. <strong>Our
298
+ content delivery provider injects its own lightweight measurement script at the edge — into the response,
299
+ after it leaves our servers.</strong> It is not in our code, our consent system never sees it, and <strong>switching a
300
+ category off in our preference centre does not stop it</strong>, because by the time the page reaches you the
301
+ script is already part of it.</p>
302
+ <p>What it is: a page-view beacon operated by that provider. It sets no cookie, creates no persistent
303
+ identifier of you, and reports aggregate traffic. It is not used for advertising and it is not joined to
304
+ anything else we hold.</p>
305
+ <p>What it is not: covered by the exemption we claim for our own analytics. That argument rests on the data
306
+ staying on our own infrastructure, and this is a third party receiving it. <strong>We are not going to stretch
307
+ the same reasoning over both.</strong></p>
308
+ <p>If you would rather it did not run, a content blocker or a network-level block stops it, and we do not
309
+ attempt to detect or defeat that. You can also write to privacy@ever.co and we will tell you the
310
+ current provider and exactly what it collects.</p>
311
+ <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>
312
+ <p>Some of these providers are established outside the European Economic Area, and using them involves an
313
+ international transfer of personal data. <strong>The transfers section of our
314
+ <a href="https://async.ever.co/privacy">Privacy Policy</a> sets out the destinations and the safeguards we rely on for each</strong>,
315
+ and you can ask us for a copy of those safeguards.</p>
316
+ <p>Two lists keep this current, and between them they are the authoritative answer:</p>
317
+ <ul>
318
+ <li><strong>The table in the product-specific section below</strong> names every cookie and similar technology in use on
319
+ this product's surfaces — the provider, whether it is first- or third-party, its category, its purpose,
320
+ how long it lasts, and a link to the provider's own notice.</li>
321
+ <li><strong>Our Sub-processor List</strong> covers the wider set of providers that process personal data for us, including
322
+ the many that never touch your device at all. You can obtain the current version at any time from
323
+ privacy@ever.co, and it names the sub-processor, what it does, and where it processes.</li>
324
+ </ul>
325
+ <p>We update both when a provider is added, removed or changed. If you find something on our pages that is not
326
+ in either list, tell us at privacy@ever.co — that is a defect and we will fix it.</p>
327
+ <h2 id="consent-and-how-to-withdraw-it" tabindex="-1">Consent, and how to withdraw it</h2>
328
+ <h3 id="how-the-banner-works" tabindex="-1">How the banner works</h3>
329
+ <p>On your first visit we show a consent banner, and <strong>nothing in the functional, analytics or marketing
330
+ categories is written to or read from your device until you have made a choice.</strong> The strictly necessary
331
+ items load, because the page cannot be delivered otherwise. Everything else waits.</p>
332
+ <p>The first layer of the banner — the one you see without clicking anything further — carries both a
333
+ <strong>Reject all</strong> and an <strong>Accept all</strong> control, presented with equal prominence. <strong>Refusing everything takes
334
+ one click, exactly like accepting everything.</strong> Alongside them is a route into per-category choice, so you
335
+ can accept analytics and refuse marketing, or any other combination.</p>
336
+ <p>Three things that some banners do and ours does not:</p>
337
+ <ul>
338
+ <li><strong>No pre-ticked boxes.</strong> Every category except strictly necessary starts switched off.</li>
339
+ <li><strong>Closing the banner is not consent.</strong> Neither is dismissing it, scrolling past it, or carrying on
340
+ browsing. If you do not make a choice, nothing optional is set — you simply have not decided yet.</li>
341
+ <li><strong>No dark patterns.</strong> We do not make the reject control smaller, greyer, slower or harder to find than the
342
+ accept control, and we do not hide it a layer down.</li>
343
+ </ul>
344
+ <h3 id="changing-your-mind" tabindex="-1">Changing your mind</h3>
345
+ <p><strong>Withdrawing consent is as easy as giving it, and you can do it at any time.</strong></p>
346
+ <p>There is a persistent <strong>Cookie preferences</strong> link in the footer of every page, and an equivalent entry
347
+ inside the application's settings. It opens the same per-category controls you saw in the banner, showing
348
+ what you currently allow. Change a switch and it takes effect immediately: we stop, and where we can, we
349
+ remove what was stored.</p>
350
+ <p>Two honest limits on that:</p>
351
+ <ul>
352
+ <li><strong>Withdrawal works forwards, not backwards.</strong> It does not make lawful past processing unlawful, and it
353
+ does not reach into data a third-party provider already received. If you want that deleted too, ask us at
354
+ privacy@ever.co and we will tell you who holds it and how to ask them.</li>
355
+ <li><strong>Your choice is stored on the device and browser you made it on.</strong> A different browser, a different
356
+ device or a private window will ask again, because there is nothing there to read. Clearing your browser
357
+ storage deletes the record of your refusal as well, which is why the banner reappears afterwards.</li>
358
+ </ul>
359
+ <h3 id="the-record-we-keep" tabindex="-1">The record we keep</h3>
360
+ <p>When you make a choice we record what you chose, when you chose it, which categories it covered, and which
361
+ version of this policy was in force at the time. That record exists for two reasons: so that we honour your
362
+ choice, and so that we can show what you were asked and what you answered.</p>
363
+ <p>You can ask us for a copy of your own consent record at privacy@ever.co.</p>
364
+ <h3 id="how-long-a-choice-lasts-before-we-ask-again" tabindex="-1">How long a choice lasts before we ask again</h3>
365
+ <p>We store a consent choice for <strong>six months</strong>. After that the banner appears again so you can confirm or
366
+ change it. We will also ask again sooner if we add a purpose or a category your earlier choice did not
367
+ cover, or if this policy changes in a way that materially affects what you agreed to.</p>
368
+ <p><strong>This is our own practice, not a legal requirement.</strong> There is no EU-wide statutory interval for asking
369
+ again — six months follows regulator guidance we consider sensible and proportionate, and we have chosen to
370
+ apply it. If you would rather not be asked at all, refusing everything is a decision we keep for the same
371
+ six months, and blocking storage at the browser level stops the question permanently.</p>
372
+ <h2 id="controls-in-your-browser-and-on-your-device" tabindex="-1">Controls in your browser and on your device</h2>
373
+ <p>Our banner is not the only way to control this, and it is not the strongest one. Your browser and your
374
+ operating system can enforce a choice on every site at once, including ours.</p>
375
+ <h3 id="in-a-browser" tabindex="-1">In a browser</h3>
376
+ <p>Every major browser — Chrome, Firefox, Safari, Edge and the rest — offers the same set of controls, under
377
+ privacy or site settings:</p>
378
+ <ul>
379
+ <li><strong>Delete cookies and site data</strong>, for one site or all of them.</li>
380
+ <li><strong>Block cookies</strong>, either all of them or only those set by third parties.</li>
381
+ <li><strong>Clear storage on exit</strong>, so nothing survives the session.</li>
382
+ <li><strong>Private or incognito windows</strong>, which discard everything when the window closes.</li>
383
+ <li><strong>Per-site permissions</strong>, so you can allow storage on the sites you use and block it everywhere else.</li>
384
+ </ul>
385
+ <p>Your browser's own help pages describe exactly where these live in your version — we deliberately do not
386
+ reproduce click-by-click instructions here, because they go stale faster than this document does.</p>
387
+ <p>Content blockers and privacy extensions work on our sites too. <strong>Using one is a legitimate choice</strong>, and we
388
+ build the Service so that it keeps working when the optional things are blocked.</p>
389
+ <h3 id="in-our-desktop-and-mobile-applications" tabindex="-1">In our desktop and mobile applications</h3>
390
+ <p>An installed application has no browser settings to change, so the controls are at the operating-system
391
+ level instead:</p>
392
+ <ul>
393
+ <li>Reset or limit the <strong>advertising identifier</strong> your device provides.</li>
394
+ <li>Answer <strong>no</strong> to the app-tracking permission prompt on iOS, which stops access to that identifier
395
+ entirely.</li>
396
+ <li>Withdraw <strong>notification permission</strong>, which stops the push token being useful.</li>
397
+ <li>Clear the application's stored data, or uninstall it, which removes everything it kept locally.</li>
398
+ </ul>
399
+ <p>The <strong>Cookie preferences</strong> controls described above are also available inside the application, and they
400
+ govern the same categories there as on the website.</p>
401
+ <h3 id="what-breaks-if-you-block-the-strictly-necessary-ones" tabindex="-1">What breaks if you block the strictly necessary ones</h3>
402
+ <p>Blocking the optional categories breaks nothing. Blocking storage entirely does, and you should know what to
403
+ expect:</p>
404
+ <ul>
405
+ <li><strong>You will not be able to sign in, or stay signed in.</strong> Authentication needs somewhere to keep the
406
+ session.</li>
407
+ <li><strong>Forms may fail their security check</strong> and refuse to submit.</li>
408
+ <li><strong>Some features will behave inconsistently</strong>, because requests can no longer be kept on the same server.</li>
409
+ <li><strong>We cannot remember that you refused.</strong> The record of your choice is itself stored on your device, so
410
+ blocking storage means the banner returns on every visit — the one genuinely irritating consequence, and
411
+ it comes from the mechanism rather than from us being difficult.</li>
412
+ </ul>
413
+ <h3 id="do-not-track" tabindex="-1">Do Not Track</h3>
414
+ <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
415
+ refusal</strong> — and we would rather explain why than quietly ignore it.</p>
416
+ <p>No consistent standard was ever agreed for what a site should do on receiving it. It was never clear whether
417
+ it expressed a considered decision or a default someone else had set, browsers behaved differently, and
418
+ several have withdrawn it. A signal we cannot interpret is not a safe basis for deciding what you want.</p>
419
+ <p>Use the banner or the preference centre instead. A choice made there is unambiguous, and we record it.</p>
420
+ <h3 id="global-privacy-control" tabindex="-1">Global Privacy Control</h3>
421
+ <p><strong>Global Privacy Control (GPC)</strong> is the later, better-specified signal, and unlike Do Not Track it is
422
+ defined to express an actual opt-out rather than a preference.</p>
423
+ <p><strong>Where we receive a GPC signal from your browser, we treat it as a refusal of the analytics and marketing
424
+ categories</strong> on that browser, and we act on it without waiting for you to interact with a banner.</p>
425
+ <p>Two points of detail:</p>
426
+ <ul>
427
+ <li>It applies to the browser or device sending it. Another browser sends its own signal, or none.</li>
428
+ <li><strong>An explicit choice you make later in our preference centre takes precedence</strong>, in either direction. If
429
+ you switch a category on there while GPC is enabled, we treat that as your decision, and we record it as
430
+ such. If you would rather that never happened, leave the categories switched off.</li>
431
+ </ul>
432
+ <h2 id="changes-to-this-policy" tabindex="-1">Changes to this policy</h2>
433
+ <p>We update this policy when what we do changes — a provider added or removed, a technology retired, a
434
+ category reassigned. Every update gets its own version number and effective date, recorded at the end of
435
+ this document.</p>
436
+ <p><strong>Where a change materially affects what you agreed to</strong> — a new purpose, a new category, or a tool moving
437
+ out of the strictly necessary or exempt group — <strong>we ask for your consent again rather than relying on the
438
+ choice you made against the old text.</strong> Corrections, clarifications and provider renames are published with
439
+ a new version and no fresh request.</p>
440
+ <p>Earlier versions stay available, with the dates each was in force, at
441
+ <a href="https://async.ever.co/cookies">https://async.ever.co/cookies</a>. The effective date shown with this policy tells you which
442
+ version applies today.</p>
443
+ <h2 id="how-to-reach-us" tabindex="-1">How to reach us</h2>
444
+ <p>Questions about this policy, about anything in the table above, or about a choice you have made — write to
445
+ privacy@ever.co. That address is monitored and we answer it. Ask us for a copy of your own consent
446
+ record, for the current sub-processor list, or to be excluded from our own analytics, and we will do it
447
+ without asking why.</p>
448
+ <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
449
+ number 204599535. We correspond in English.</p>
450
+ <p>If you think we have handled your data badly, tell us first — we would rather fix it. <strong>You can also
451
+ complain to a data protection supervisory authority at any time.</strong> Ours is the
452
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
453
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
454
+ to the authority for the country where you live or work.</p>
455
+ <p>This document is version 1.0.2 of the Cookie Policy for
456
+ <a href="https://async.ever.co">async.ever.co</a>, in force from 2026-08-02. Earlier versions, with the dates
457
+ they applied, are at <a href="https://async.ever.co/cookies">https://async.ever.co/cookies</a>.</p>