@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,1350 @@
1
+ <h1 id="terms-of-service" tabindex="-1">Terms of Service</h1>
2
+ <p><strong>Ever Async</strong> — <a href="https://async.ever.co">async.ever.co</a></p>
3
+ <p>Version 1.0.2 · In force from 2026-08-02</p>
4
+ <p>These Terms of Service (&quot;<strong>Terms</strong>&quot;) govern your access to and use of the Ever Async hosted service and the
5
+ websites, applications and application programming interfaces we make available at <a href="https://async.ever.co">async.ever.co</a>
6
+ (together, the &quot;<strong>Service</strong>&quot;).</p>
7
+ <p>The Service is provided by <strong>Ever Technologies LTD</strong>, a company registered in Bulgaria under
8
+ company number 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria (&quot;<strong>we</strong>&quot;,
9
+ &quot;<strong>us</strong>&quot;, &quot;<strong>our</strong>&quot;).</p>
10
+ <p>By creating an account, by accessing the Service, or by clicking to accept these Terms, you agree to be
11
+ bound by them. If you are agreeing on behalf of a company or other organisation, you confirm that you have
12
+ authority to bind that organisation, and &quot;<strong>you</strong>&quot; means that organisation.</p>
13
+ <p><strong>If you do not agree to these Terms, you must not use the Service.</strong></p>
14
+ <p>These Terms incorporate by reference our <a href="https://async.ever.co/privacy">Privacy Policy</a>, our
15
+ <a href="https://async.ever.co/cookies">Cookie Policy</a>, our Acceptable Use Policy and our Refund Policy. Where you
16
+ process personal data of your own users or personnel through the Service, our Data Processing Addendum
17
+ also applies.</p>
18
+ <h2 id="definitions" tabindex="-1">Definitions</h2>
19
+ <p>These are the words we use throughout these Terms with a particular meaning. Everywhere else, words carry
20
+ their ordinary meaning.</p>
21
+ <ul>
22
+ <li><strong>Acceptable Use Policy</strong> (or <strong>AUP</strong>) — the rules on what may and may not be done with the Service. It is
23
+ published with these Terms and forms part of them. Where the AUP changes, the version in force when you
24
+ use the Service is the one that applies.</li>
25
+ <li><strong>Account</strong> — the credentialed identity through which you or an End User signs in to the Service.</li>
26
+ <li><strong>Beta Features</strong> — any part of the Service we describe as beta, preview, early access, experimental,
27
+ pilot or similar, or make available for evaluation ahead of general release. They carry a weaker regime
28
+ than the rest of the Service; the warranties and limitation of liability sections say how.</li>
29
+ <li><strong>Confidential Information</strong> — information one of us discloses to the other that is marked confidential,
30
+ or that a reasonable person receiving it would understand to be confidential, including non-public
31
+ technical, security, commercial and pricing information. <strong>Customer Data is always your Confidential
32
+ Information.</strong></li>
33
+ <li><strong>Customer</strong> (also <strong>you</strong> and <strong>your</strong>) — the person or organisation that has accepted these Terms and
34
+ holds the Subscription. Where an individual accepts on behalf of an organisation, the Customer is that
35
+ organisation and not the individual.</li>
36
+ <li><strong>Customer Data</strong> — everything you or your End Users submit to, store in, generate through or import into
37
+ the Service: files, records, messages, configuration, and anything an integration you connect brings in.
38
+ It does not include our own service logs, security telemetry or the aggregated statistics described in
39
+ the Customer Data section.</li>
40
+ <li><strong>Data Processing Addendum</strong> (or <strong>DPA</strong>) — the terms on which we process Personal Data on your behalf.
41
+ It applies automatically wherever you use the Service to handle personal data about other people, forms
42
+ part of these Terms, and needs no separate signature.</li>
43
+ <li><strong>Documentation</strong> — the user guides, help articles, API references and technical descriptions we publish
44
+ for the Service, as they stand when you use it. Marketing pages, roadmaps, benchmarks and statements made
45
+ in sales conversations are not Documentation.</li>
46
+ <li><strong>End User</strong> — an individual you permit to use the Service under your Subscription: an employee,
47
+ contractor, colleague, client or other person you invite into your Workspace.</li>
48
+ <li><strong>Fees</strong> — the amounts payable for the Service under your plan or Order, before taxes. Taxes are added
49
+ where they apply.</li>
50
+ <li><strong>Order</strong> — the plan selection, checkout, order form or written quotation under which you subscribe,
51
+ including the seats, usage limits, term and price it records.</li>
52
+ <li><strong>Personal Data</strong> — information relating to an identified or identifiable living person, as defined in
53
+ the General Data Protection Regulation (Regulation (EU) 2016/679). Where another data protection law
54
+ governs a particular processing operation, that law's equivalent definition applies to it.</li>
55
+ <li><strong>Service</strong> — as defined at the start of these Terms. Throughout, it means <strong>the hosted service we
56
+ operate</strong>, and never any separately licensed source code you may obtain and run yourself.</li>
57
+ <li><strong>Sub-processor</strong> — a third party we engage to process Personal Data on your behalf so that we can
58
+ deliver the Service. Our current sub-processors are published in our sub-processor list, and the DPA sets
59
+ out how we notify you of changes and how you may object.</li>
60
+ <li><strong>Subscription</strong> — your right to use the Service for a stated term, at a stated plan level, within a
61
+ stated number of seats or usage allowance.</li>
62
+ <li><strong>Workspace</strong> — the separate space in which your Customer Data is held and your End Users work. Depending
63
+ on the product it may be presented as a workspace, an organisation, a team or a tenant. These Terms use
64
+ <em>Workspace</em> for all of them.</li>
65
+ </ul>
66
+ <h3 id="how-to-read-these-terms" tabindex="-1">How to read these Terms</h3>
67
+ <ul>
68
+ <li>Headings exist for navigation. They do not limit or extend what a section says.</li>
69
+ <li>&quot;Including&quot;, &quot;such as&quot; and &quot;for example&quot; introduce examples. They never narrow the words in front of them.</li>
70
+ <li>The singular includes the plural, and the other way round.</li>
71
+ <li>A reference to our Privacy Policy, Cookie Policy, Acceptable Use Policy, Refund Policy or DPA means the
72
+ version in force when you use the Service. How and when we change them is dealt with in the section on
73
+ changes to these Terms.</li>
74
+ <li>A reference to a law includes that law as amended, extended or replaced.</li>
75
+ <li>&quot;In writing&quot; includes email. Where a notice may be given inside the Service, the notices section says so.</li>
76
+ <li>If an Order, a product annex or the DPA says something different from these core terms, the precedence
77
+ rules in the general section decide which one wins.</li>
78
+ </ul>
79
+ <h2 id="who-you-contract-with" tabindex="-1">Who you contract with</h2>
80
+ <p>Your contract for the Service is with <strong>Ever Technologies LTD</strong>, and with no one else.</p>
81
+ <ul>
82
+ <li>Registered in Bulgaria under company number 204599535</li>
83
+ <li>Registered office: Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria</li>
84
+ <li>Legal notices and contract queries: legal@ever.co</li>
85
+ </ul>
86
+ <p>Ever Technologies operates the Service, invoices you for it, holds your Subscription, and is the party
87
+ responsible to you under these Terms. <strong>When these Terms say &quot;we&quot;, &quot;us&quot; or &quot;our&quot;, they mean
88
+ Ever Technologies LTD.</strong> If you need to bring a claim about the Service, it is the company you bring it
89
+ against, on the governing law and in the venue set out later in these Terms.</p>
90
+ <h3 id="the-company-that-owns-the-software-is-not-your-counterparty" tabindex="-1">The company that owns the software is not your counterparty</h3>
91
+ <p>The intellectual property in the Service is owned by a separate company, which is identified in the
92
+ intellectual property section below and which licenses that property to Ever Technologies LTD. <strong>You do not
93
+ contract with it.</strong> It is not a party to these Terms, it owes you nothing under them, it makes you no
94
+ promise about the Service, and it does not handle the data you put into the Service. Everything you are
95
+ owed in connection with the Service, you are owed by Ever Technologies LTD.</p>
96
+ <h3 id="separately-licensed-source-code-is-not-part-of-this-contract" tabindex="-1">Separately licensed source code is not part of this contract</h3>
97
+ <p>Some of the software behind the Service is published under an open-source licence. <strong>That code reaches you
98
+ under its own licence, from its own publisher, on its own terms — not under this contract.</strong> These Terms
99
+ neither grant you rights in that code nor take any away. The section on open-source software below explains
100
+ exactly where the line falls and what follows from it if you run your own copy.</p>
101
+ <h3 id="these-terms-cover-this-product" tabindex="-1">These Terms cover this product</h3>
102
+ <p>These Terms govern <a href="https://async.ever.co">async.ever.co</a> and the Ever Async hosted service. Other websites,
103
+ products and services — including ones that share part of our branding, and ones operated by other
104
+ companies — have their own terms, their own operator and their own privacy notice. Read the terms published
105
+ on the site you are actually using.</p>
106
+ <h2 id="who-may-use-the-service" tabindex="-1">Who may use the Service</h2>
107
+ <h3 id="age" tabindex="-1">Age</h3>
108
+ <p><strong>You must be at least 16 years old to hold an Account.</strong></p>
109
+ <p>We know that Bulgaria sets the age at which a child can consent to an information-society service
110
+ at 14, which is lower. We require 16 regardless. The Service is a tool for work, it is not designed for or
111
+ directed at children, and we do not knowingly provide it to anyone under 16.</p>
112
+ <p>If we learn that an Account is held by someone under 16, we will close it and delete the associated personal
113
+ data as described in our <a href="https://async.ever.co/privacy">Privacy Policy</a>. If you believe a child under 16 has an
114
+ Account, tell us at privacy@ever.co.</p>
115
+ <h3 id="capacity" tabindex="-1">Capacity</h3>
116
+ <p>You must have the legal capacity to enter into a binding contract in the place where you live or where your
117
+ organisation is established. If you do not, you must not accept these Terms.</p>
118
+ <h3 id="authority-to-bind-an-organisation" tabindex="-1">Authority to bind an organisation</h3>
119
+ <p>If you accept these Terms, or sign up, in the name of a company, partnership, public body or any other
120
+ organisation, you confirm that:</p>
121
+ <ul>
122
+ <li>you are authorised to bind that organisation to these Terms;</li>
123
+ <li>the organisation becomes the Customer, and &quot;you&quot; in these Terms means the organisation; and</li>
124
+ <li>you have the authority to place Orders, incur Fees and appoint administrators on its behalf.</li>
125
+ </ul>
126
+ <p><strong>If it turns out you did not have that authority, you accept these Terms in your own name and are
127
+ personally responsible for everything in them, including payment.</strong> We may ask for evidence of your
128
+ authority at any time, and we may suspend an Account while we check.</p>
129
+ <h3 id="if-we-have-closed-your-account-before" tabindex="-1">If we have closed your Account before</h3>
130
+ <p>You must not use the Service if we have previously terminated an Account held by you, or by an organisation
131
+ you control, for breach of these Terms or the Acceptable Use Policy — unless we have agreed in writing that
132
+ you may come back.</p>
133
+ <p><strong>Opening a new Account to get around a closure is itself a breach</strong>, and we may close the new Account
134
+ without notice and without refund.</p>
135
+ <h3 id="sanctions-and-restricted-jurisdictions" tabindex="-1">Sanctions and restricted jurisdictions</h3>
136
+ <p>You confirm, each time you use the Service, that you are not:</p>
137
+ <ul>
138
+ <li>located in, ordinarily resident in, or organised under the laws of a country or territory subject to
139
+ comprehensive economic sanctions or a trade embargo imposed by the European Union, the United Nations,
140
+ the United Kingdom or the United States;</li>
141
+ <li>named on, or owned or controlled by anyone named on, a sanctions or restricted-party list maintained by
142
+ any of those authorities; or</li>
143
+ <li>acting for, or on behalf of, anyone in either of those categories.</li>
144
+ </ul>
145
+ <p><strong>Tell us immediately if that stops being true.</strong> We may suspend or terminate access without notice where we
146
+ reasonably believe continuing to provide the Service would breach sanctions or export control law. The
147
+ compliance section below sets out the wider obligations that go with this.</p>
148
+ <h2 id="accounts-and-workspace-administration" tabindex="-1">Accounts and workspace administration</h2>
149
+ <h3 id="your-account" tabindex="-1">Your Account</h3>
150
+ <p>Give us accurate registration details and keep them current. An Account belongs to one named individual —
151
+ do not share credentials, and do not let someone else use your Account. If a colleague needs access, add
152
+ them as an End User.</p>
153
+ <p>Do not create Accounts by automated means, and do not register an Account using someone else's identity or
154
+ an email address you are not entitled to use.</p>
155
+ <h3 id="account-security-is-yours-to-keep" tabindex="-1">Account security is yours to keep</h3>
156
+ <p><strong>You are responsible for everything done through your Account and through the Accounts of your End Users</strong>,
157
+ whether or not you authorised it, unless the cause was our own failure to keep the Service secure.</p>
158
+ <p>That means you need to:</p>
159
+ <ul>
160
+ <li>choose strong, unique credentials and keep them confidential;</li>
161
+ <li>turn on multi-factor authentication where the Service offers it;</li>
162
+ <li>revoke access, API keys and tokens when a person leaves or a device is lost; and</li>
163
+ <li>keep the devices and email accounts used to reach the Service secure, because whoever controls the email
164
+ address controls password recovery.</li>
165
+ </ul>
166
+ <p><strong>Tell us at abuse@ever.co as soon as you suspect an Account has been compromised or credentials have
167
+ leaked.</strong> We may reset credentials, revoke tokens or suspend an Account to contain a security problem, and
168
+ we will tell you when we do.</p>
169
+ <h3 id="the-workspace-administrator-controls-the-workspace" tabindex="-1">The workspace administrator controls the Workspace</h3>
170
+ <p>Every Workspace has one or more administrators, appointed by you. An administrator acts for you, and we act
171
+ on an administrator's instructions without checking them against anyone else.</p>
172
+ <p><strong>An administrator can, among other things:</strong></p>
173
+ <ul>
174
+ <li>access, search, export and permanently delete anything in the Workspace — including content, messages and
175
+ files created by End Users;</li>
176
+ <li>add, suspend and remove End Users, and reset or take over their Accounts;</li>
177
+ <li>change Workspace settings, including retention periods and which features are enabled;</li>
178
+ <li>turn features on or off for particular people, including any features the product provides for recording
179
+ or measuring how End Users work; and</li>
180
+ <li>see usage and audit information about what End Users do in the Workspace.</li>
181
+ </ul>
182
+ <p><strong>If you are an End User rather than the Customer, this is the sentence that matters to you: the
183
+ organisation that runs your Workspace can see what you put into it, can export it, can delete it, and can
184
+ remove your access at any time.</strong> We cannot restore what an administrator deletes, and we cannot give you
185
+ access an administrator has withdrawn.</p>
186
+ <h3 id="an-organisation-may-take-administrative-control-of-an-account" tabindex="-1">An organisation may take administrative control of an Account</h3>
187
+ <p>This one surprises people, so we would rather you read it here than discover it later.</p>
188
+ <p><strong>If you registered an Account with an email address on a domain controlled by an organisation — typically
189
+ your employer — or you join a Workspace that organisation runs, that organisation may claim administrative
190
+ control of your Account.</strong></p>
191
+ <p>If it does, and it can show us that it controls the domain or the Workspace, then:</p>
192
+ <ul>
193
+ <li>it becomes the Customer for that Account and these Terms apply between us and it;</li>
194
+ <li>it can apply its own policies to the Account, change its settings, and access the Customer Data associated
195
+ with it;</li>
196
+ <li>it can transfer, suspend or delete the Account; and</li>
197
+ <li><strong>it can do all of that after you created the Account, and without needing your agreement.</strong></li>
198
+ </ul>
199
+ <p>We will act on a claim we have verified. We are not in a position to referee a disagreement between you and
200
+ your employer about it, and we will not: that dispute is between the two of you, and you should raise it
201
+ with the organisation.</p>
202
+ <p><strong>If you want an Account that stays yours, register it with a personal email address and keep personal
203
+ material out of a Workspace someone else administers.</strong></p>
204
+ <h3 id="acting-on-administrator-instructions" tabindex="-1">Acting on administrator instructions</h3>
205
+ <p>We may rely on an instruction that appears to come from an administrator or from someone with access to an
206
+ administrator's Account. We are not obliged to investigate whether an administrator was authorised
207
+ internally to give it, and we are not responsible for the consequences of an instruction you gave us
208
+ through a person you appointed. Keep your list of administrators accurate, and remove people promptly when
209
+ their role changes.</p>
210
+ <h2 id="your-right-to-use-the-service" tabindex="-1">Your right to use the Service</h2>
211
+ <h3 id="what-we-grant-you" tabindex="-1">What we grant you</h3>
212
+ <p>For as long as your Subscription is in force and you are keeping to these Terms, we grant you a <strong>limited,
213
+ non-exclusive, non-transferable, non-sublicensable and revocable right</strong> to access and use the Service, and
214
+ the Documentation, for your own internal business purposes.</p>
215
+ <p>That right is bounded by what you have actually ordered — your plan, your seats, your usage allowance and
216
+ any other limit recorded in your Order — and by the term of your Subscription. It extends to your End Users,
217
+ who may use the Service on your behalf and under your responsibility.</p>
218
+ <p><strong>What you are paying for is access to the Service we operate. You are not buying the software, and you are
219
+ not acquiring a copy of it.</strong> Any right we have not expressly granted here is reserved.</p>
220
+ <h3 id="what-you-must-not-do" tabindex="-1">What you must not do</h3>
221
+ <p>You must not, and must not permit anyone else to:</p>
222
+ <ul>
223
+ <li>resell, rent, lease, sublicense, syndicate or otherwise make the Service available to a third party, or
224
+ run it as a service bureau, a managed service or a hosting offering for anyone other than your own
225
+ organisation and its End Users;</li>
226
+ <li>reverse engineer, decompile or disassemble the Service, or try to derive its source code, structure or
227
+ underlying ideas — <strong>except to the extent the law expressly gives you that right despite a contractual
228
+ restriction</strong>, and in that case only after you have asked us in writing for the information you need and
229
+ given us a reasonable chance to supply it;</li>
230
+ <li>work around, disable or exceed any technical control, seat count, rate limit, storage limit or usage
231
+ quota, or disguise the volume, origin or nature of your use in order to do so;</li>
232
+ <li>extract data from the Service by scraping, crawling or automated means other than the interfaces we
233
+ document for that purpose;</li>
234
+ <li>publish a benchmark, load test or comparative performance study of the Service without our prior written
235
+ consent — we will not withhold consent unreasonably where you tell us your methodology first and let us
236
+ comment on it, and nothing here stops you describing your own experience of using the Service;</li>
237
+ <li>remove, obscure or alter any copyright, trade mark or other proprietary notice in the Service or the
238
+ Documentation, or present the Service as your own;</li>
239
+ <li>probe, scan or test the security of the Service other than through our responsible disclosure process; or</li>
240
+ <li>use the Service, or anything you learn from it, to build or improve a product or service that competes
241
+ with it.</li>
242
+ </ul>
243
+ <p>The Acceptable Use Policy adds rules about content and conduct. These restrictions and the AUP both apply.</p>
244
+ <h3 id="this-does-not-cut-down-any-open-source-licence" tabindex="-1">This does not cut down any open-source licence</h3>
245
+ <p>Nothing in this section restricts a right that an open-source licence gives you in code published under it.
246
+ <strong>If you obtain the source code under an open-source licence, that licence governs what you may do with the
247
+ code, and this section governs only what you may do with the hosted Service.</strong> The open-source section
248
+ explains the split in full.</p>
249
+ <h3 id="suspension-and-withdrawal" tabindex="-1">Suspension and withdrawal</h3>
250
+ <p>We may suspend or withdraw the rights granted here in the circumstances set out in the section on term,
251
+ suspension and termination — most obviously a serious or continuing breach of these Terms or the AUP, or
252
+ non-payment.</p>
253
+ <h2 id="what-you-are-responsible-for" tabindex="-1">What you are responsible for</h2>
254
+ <p>We operate the Service. Almost everything about <em>how you use it</em> sits with you, and the list below is the
255
+ honest version of that split rather than a formality.</p>
256
+ <h3 id="lawful-use-and-your-own-compliance" tabindex="-1">Lawful use, and your own compliance</h3>
257
+ <p>Use the Service lawfully. <strong>You are responsible for working out which laws apply to you and for meeting
258
+ them</strong> — we do not know your sector, your jurisdictions, your regulator or your internal policies, and we do
259
+ not advise you on any of them.</p>
260
+ <p>That includes, where they apply to you: data protection and privacy law, employment and workplace law,
261
+ electronic marketing rules, consumer law, financial, health and other sector regulation, records-retention
262
+ duties, export controls and sanctions, and the terms of any third-party platform whose data you bring into
263
+ or push out of the Service.</p>
264
+ <h3 id="the-data-you-put-in" tabindex="-1">The data you put in</h3>
265
+ <p>You are responsible for the accuracy, quality, legality and integrity of your Customer Data, and for
266
+ deciding whether it should be in the Service at all.</p>
267
+ <p>Before you put personal data into the Service, <strong>it is your job — not ours — to give whatever notices and
268
+ obtain whatever consents or other lawful basis your own law requires</strong>, from the people the data is about.
269
+ That applies to your personnel, your customers, your candidates, your contacts, and anyone whose data
270
+ arrives through an integration you connect.</p>
271
+ <h3 id="features-that-record-or-measure-how-people-work" tabindex="-1">Features that record or measure how people work</h3>
272
+ <p>Where the Service includes features that record, capture or measure the activity of your personnel, <strong>you
273
+ decide whether to switch them on, on whom, and how</strong>. That decision is yours and so are the obligations that
274
+ follow from it.</p>
275
+ <p>Depending on where your people are, those obligations can include identifying a lawful basis for the
276
+ monitoring, telling each affected person clearly and in advance what is captured, completing a data
277
+ protection impact assessment, consulting a works council or employee representatives, and observing limits
278
+ on what may be captured and when. <strong>The rules differ sharply from country to country, and we make no claim
279
+ that any particular configuration is lawful anywhere.</strong> We supply the controls; you decide how to use them.</p>
280
+ <p>Your product annex and the DPA set out the capture types, the controls available to you and the express
281
+ representations you give us about all of this.</p>
282
+ <h3 id="your-end-users" tabindex="-1">Your End Users</h3>
283
+ <p>You are responsible for your End Users. <strong>Their acts and omissions in the Service count as yours.</strong> Make
284
+ sure they know what these Terms and the Acceptable Use Policy require of them, and that they follow both.</p>
285
+ <h3 id="your-backups-and-your-records" tabindex="-1">Your backups and your records</h3>
286
+ <p><strong>Keep your own copies of anything you cannot afford to lose.</strong> We run backups for our own operational
287
+ continuity, and they are not a substitute for your records. Export your data regularly using the tools the
288
+ Service provides, and do not rely on the Service as your only copy of anything — including anything you are
289
+ required by law to retain.</p>
290
+ <h3 id="equipment-connectivity-and-third-party-accounts" tabindex="-1">Equipment, connectivity and third-party accounts</h3>
291
+ <p>You provide the devices, browsers, operating systems, networks and internet connectivity needed to reach the
292
+ Service, and you keep them reasonably secure and up to date. You also provide and pay for any third-party
293
+ account or credential that an integration or a bring-your-own-key feature needs. We are not responsible for
294
+ problems caused by your own equipment, network or third-party accounts.</p>
295
+ <h3 id="acceptable-use-policy" tabindex="-1">Acceptable Use Policy</h3>
296
+ <p><strong>Our Acceptable Use Policy forms part of these Terms and applies every time the Service is used under your
297
+ Subscription.</strong> Breaching it is a breach of these Terms. We update the AUP from time to time — abuse changes
298
+ faster than contracts do — and the version in force when you use the Service is the one that applies. Where
299
+ a change to the AUP materially reduces what you are permitted to do, we will give you notice in the way the
300
+ changes section describes.</p>
301
+ <h2 id="customer-data" tabindex="-1">Customer Data</h2>
302
+ <h3 id="it-is-yours" tabindex="-1">It is yours</h3>
303
+ <p><strong>You own your Customer Data.</strong> Nothing in these Terms transfers ownership of it to us, and we claim no
304
+ rights in it beyond the limited operational licence described below. Putting data into the Service does not
305
+ change who owns it, and taking a Subscription does not make us a joint owner of anything you create with it.</p>
306
+ <h3 id="the-licence-you-give-us-and-its-limits" tabindex="-1">The licence you give us, and its limits</h3>
307
+ <p>You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, display and
308
+ process your Customer Data <strong>solely to the extent necessary to provide, secure, maintain and support the
309
+ Service for you</strong>, and to comply with our legal obligations.</p>
310
+ <p>That licence extends to the sub-processors we engage to help us deliver the Service, acting on our behalf
311
+ and under contract. It goes no further than the sentence above. The licence ends when the Customer Data is
312
+ deleted, except for copies held in routine backups for the period described in our
313
+ <a href="https://async.ever.co/privacy">Privacy Policy</a>, and except where the law requires us to keep something for
314
+ longer.</p>
315
+ <p><strong>We do not use your Customer Data to train machine-learning models for our own purposes or for the benefit
316
+ of other customers, unless you have expressly opted in.</strong> The AI features section says more about how this
317
+ works where a model is involved.</p>
318
+ <h3 id="aggregated-and-de-identified-statistics" tabindex="-1">Aggregated and de-identified statistics</h3>
319
+ <p>We generate statistics about how the Service is used — volumes, performance, feature adoption, error rates
320
+ — and we use them to run, secure, support and improve it, and to report on our business.</p>
321
+ <p><strong>Those statistics are always aggregated and de-identified.</strong> They do not identify you, your End Users or
322
+ any other individual, we do not publish or share them in a form from which you could be identified, and they
323
+ never contain your Customer Data itself.</p>
324
+ <h3 id="what-you-promise-us-about-the-data-you-provide" tabindex="-1">What you promise us about the data you provide</h3>
325
+ <p>You warrant, each time Customer Data is submitted under your Subscription, that:</p>
326
+ <ul>
327
+ <li>you have all rights, licences, permissions and lawful bases needed to provide it to us and to have us
328
+ process it as these Terms describe;</li>
329
+ <li>doing so does not breach any law, any third party's rights, or any obligation of confidence you owe;</li>
330
+ <li>where the data is personal data, you have given the notices and satisfied the lawful-basis requirements
331
+ your own law imposes, before the data reached us; and</li>
332
+ <li>the data does not breach our Acceptable Use Policy.</li>
333
+ </ul>
334
+ <p>You will indemnify us against claims arising from a breach of those promises, as set out in the
335
+ indemnification section.</p>
336
+ <h3 id="we-can-remove-content" tabindex="-1">We can remove content</h3>
337
+ <p><strong>We may remove, disable access to, or refuse to transmit Customer Data that breaches the Acceptable Use
338
+ Policy or the law, infringes someone's rights, or that we are legally required to remove.</strong></p>
339
+ <ul>
340
+ <li>Where it is practicable and lawful to do so, we will tell you first. Where it is not — because the matter
341
+ is urgent, because a court or authority has ordered it, or because notice would prejudice an investigation
342
+ — we will tell you as soon as we reasonably can afterwards.</li>
343
+ <li>We do not monitor Customer Data, and we are under no general obligation to look for unlawful content. That
344
+ we did not act on something does not mean we approved of it.</li>
345
+ <li>Removing content is an operational step to protect the Service and other people. It is not a judgement on
346
+ the merits of whatever complaint prompted it, and it does not make us responsible for content we left in
347
+ place.</li>
348
+ </ul>
349
+ <p>Where the Service publishes content to third parties, the notice-and-action procedure in these Terms sets
350
+ out how illegal content and infringement are reported and handled.</p>
351
+ <h3 id="keeping-your-own-copy" tabindex="-1">Keeping your own copy</h3>
352
+ <p>Export what matters to you, regularly. <strong>We are not your archive</strong>, and the warranties section is explicit
353
+ that you should not treat our backups as a substitute for your own records.</p>
354
+ <h3 id="personal-data" tabindex="-1">Personal data</h3>
355
+ <p>Where Customer Data includes personal data, the privacy and data protection section below and the DPA govern
356
+ who is responsible for what.</p>
357
+ <h2 id="privacy-and-data-protection" tabindex="-1">Privacy and data protection</h2>
358
+ <p>Three documents sit alongside these Terms and you should read them:</p>
359
+ <ul>
360
+ <li>our <a href="https://async.ever.co/privacy">Privacy Policy</a> — what we do with personal data in our own right, and the
361
+ rights you have over it;</li>
362
+ <li>our <a href="https://async.ever.co/cookies">Cookie Policy</a> — cookies and similar technologies on our websites and in the
363
+ Service; and</li>
364
+ <li>our <strong>Data Processing Addendum</strong> — how we handle personal data that you put into the Service about other
365
+ people. It forms part of these Terms and applies automatically. You do not need to sign it separately, and
366
+ you can obtain the current version from legal@ever.co.</li>
367
+ </ul>
368
+ <h3 id="who-is-responsible-for-what" tabindex="-1">Who is responsible for what</h3>
369
+ <p>Two different relationships run in parallel, and it matters which one you are looking at.</p>
370
+ <p><strong>We are the controller</strong> for the personal data we handle in our own relationship with you: your account and
371
+ administrator details, billing and tax records, support correspondence, security and audit logs, and people
372
+ who visit our websites or contact us. We decide why and how that data is processed, and our Privacy Policy
373
+ explains it.</p>
374
+ <p><strong>You are the controller and we are your processor</strong> for the personal data that you and your End Users put
375
+ into the Service about other people — your records and content, and, where the Service offers such features,
376
+ any data it captures about how your own personnel work. <strong>You decide why that data is processed and how; we
377
+ process it on your documented instructions and for no purpose of our own.</strong> The DPA sets out the detail:
378
+ instructions, confidentiality, security measures, sub-processors and how we notify you of changes, breach
379
+ notification, assistance with requests from individuals, assistance with impact assessments, audits,
380
+ international transfers, and deletion or return at the end.</p>
381
+ <p>We do not decide whether your processing is lawful, and we are not in a position to. <strong>That assessment, and
382
+ the notices, lawful bases and consultations that go with it, are yours</strong> — see the section on what you are
383
+ responsible for.</p>
384
+ <h3 id="contacting-us-about-data-protection" tabindex="-1">Contacting us about data protection</h3>
385
+ <p>Write to privacy@ever.co with any data protection question, or to exercise a right you have over
386
+ personal data we hold as controller. Our Privacy Policy explains how to make a request, how long we take,
387
+ and your right to complain to a supervisory authority. Ours is the
388
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
389
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may also complain to
390
+ the supervisory authority where you live or work.</p>
391
+ <p>If you are one of our customer's End Users and your question is about data held in their Workspace, that
392
+ request goes to them: they are the controller for it, not us.</p>
393
+ <h2 id="third-party-services-and-integrations" tabindex="-1">Third-party services and integrations</h2>
394
+ <p>The Service can connect to software you already use. Depending on the product, that includes identity and
395
+ single sign-on providers, payment processors, AI and model providers, project and issue trackers, time
396
+ tracking and activity sources, source-code and repository platforms, messaging and email delivery, calendars
397
+ and file storage, and analytics tools. Our sub-processor list names the specific vendors we engage; this
398
+ section is about the ones <strong>you</strong> choose to connect.</p>
399
+ <h3 id="connecting-one-is-your-instruction-to-us" tabindex="-1">Connecting one is your instruction to us</h3>
400
+ <p><strong>When you connect a third-party service, you are instructing us to exchange data with it, and you authorise
401
+ every exchange that integration needs in order to work</strong> — in both directions, for as long as the connection
402
+ is live.</p>
403
+ <p>Before you connect something, check what it will send and receive. The Service tells you the scope an
404
+ integration asks for, and you decide whether to grant it. You are responsible for holding a valid account
405
+ with the provider, for the credentials, API keys and tokens you supply, for the permissions you grant, and
406
+ for revoking them when they are no longer needed — including when a person leaves your organisation.</p>
407
+ <h3 id="their-terms-govern-them-not-ours" tabindex="-1">Their terms govern them, not ours</h3>
408
+ <p>A third-party service is supplied by that provider under <strong>its own terms and its own privacy notice</strong>, in a
409
+ contract between you and it. We are not a party to it, and these Terms do not change it.</p>
410
+ <p>That provider is not acting for us. It acts for you, on your instructions, under your agreement with it.
411
+ <strong>It is not our sub-processor, and we are not its</strong> — so it does not appear on our sub-processor list, and
412
+ what it does with the data you send it is a matter between the two of you. Where we engage a provider
413
+ ourselves to deliver the Service, the position is the opposite: it is our sub-processor and it is on that
414
+ list.</p>
415
+ <h3 id="what-we-are-not-responsible-for" tabindex="-1">What we are not responsible for</h3>
416
+ <p><strong>We are not responsible for third-party services, and we do not endorse them.</strong> We give no warranty about
417
+ any of them and we accept no liability for them, including for:</p>
418
+ <ul>
419
+ <li>whether they are available, accurate, secure, lawful or fit for what you want;</li>
420
+ <li>what they do with data you send them, how long they keep it and where;</li>
421
+ <li>what they charge you, and how they change what they charge;</li>
422
+ <li>any loss you suffer through using one; or</li>
423
+ <li>anything published on a third-party website that the Service links to.</li>
424
+ </ul>
425
+ <p><strong>If a third-party service changes, restricts, degrades, prices differently or shuts down — or if it changes
426
+ its API so an integration stops working — that is not a breach of these Terms by us.</strong> It does not entitle
427
+ you to a refund or a credit, and it does not release you from your Subscription. We will tell you when we
428
+ learn that an integration is affected, and we will restore it where we reasonably can.</p>
429
+ <p>We may also have to suspend or remove an integration at short notice — if the provider requires it, if it
430
+ stops being safe or lawful, or if it threatens the security or stability of the Service. We will give you as
431
+ much warning as the circumstances allow.</p>
432
+ <h3 id="extensions-plugins-and-marketplace-items" tabindex="-1">Extensions, plugins and marketplace items</h3>
433
+ <p>Plugins, extensions and add-ons published by anyone other than us are third-party services for the purposes
434
+ of this section, even where the Service helps you install them. We do not review or vet them unless we
435
+ expressly say that we have.</p>
436
+ <h2 id="ai-features" tabindex="-1">AI features</h2>
437
+ <p>Parts of the Service use machine-learning models to generate text, summarise, translate, classify, extract,
438
+ rank, score or suggest. We call what comes back <strong>Output</strong>, and what you send in <strong>Input</strong>. This section
439
+ applies whenever you use one of those features.</p>
440
+ <h3 id="output-can-be-wrong-and-you-must-check-it" tabindex="-1">Output can be wrong, and you must check it</h3>
441
+ <p><strong>AI Output can be inaccurate, incomplete, out of date, biased or entirely made up — and it can be wrong in
442
+ ways that read as confident and plausible.</strong> Treat it as a draft produced by something that does not know
443
+ what it is saying, not as a finding.</p>
444
+ <ul>
445
+ <li><strong>It is not professional advice.</strong> Nothing the Service generates is legal, financial, tax, accounting,
446
+ medical, employment or safety advice, and it is no substitute for a qualified person. Do not use it as
447
+ one.</li>
448
+ <li><strong>Do not use Output as the sole basis for a decision that has a legal or similarly significant effect on
449
+ a person</strong> — hiring, discipline, dismissal, pay, promotion, credit, eligibility or access to a service. A
450
+ competent human being with authority to decide must review the Output and take the decision. Where the
451
+ Service produces a score, a rating or a verdict about a person, that is a signal for a person to consider,
452
+ not an outcome.</li>
453
+ <li><strong>You are responsible for what you do with Output</strong>, for checking it before you act on it or publish it,
454
+ and for the consequences either way.</li>
455
+ <li>Output is not guaranteed to be unique. The same or similar Input can produce similar Output for someone
456
+ else, and we do not grant you exclusivity in it. Check that Output does not infringe anyone's rights
457
+ before you use it commercially.</li>
458
+ </ul>
459
+ <p><strong>We do not warrant that Output is accurate, complete, current, original, fit for your purpose or free of
460
+ third-party rights.</strong> The warranties and limitation of liability sections apply to AI features in full.</p>
461
+ <h3 id="what-you-must-not-put-in" tabindex="-1">What you must not put in</h3>
462
+ <p>Do not send as Input:</p>
463
+ <ul>
464
+ <li>data you do not have the rights or permissions to provide, or whose disclosure would breach a duty of
465
+ confidence, a licence, a court order or your own regulatory obligations;</li>
466
+ <li>personal data for which you have no lawful basis, or which you have not told the relevant people you would
467
+ process this way; or</li>
468
+ <li>special-category or otherwise highly sensitive data, unless you have satisfied yourself that you may and
469
+ have configured the Service accordingly.</li>
470
+ </ul>
471
+ <p>The Acceptable Use Policy adds restrictions on what AI features may be used for. Both apply.</p>
472
+ <h3 id="which-model-provider-is-involved-and-who-contracts-with-it" tabindex="-1">Which model provider is involved, and who contracts with it</h3>
473
+ <p><strong>Where we operate an AI feature using a third-party model provider, we engage that provider as our
474
+ sub-processor.</strong> It appears in our sub-processor list with its location and the transfer mechanism we rely
475
+ on, and it is bound by the DPA terms on sub-processing.</p>
476
+ <p><strong>Some products instead let you supply your own API key, or your own model endpoint, for an AI provider you
477
+ choose. When you do that, you are the one contracting with that provider, not us.</strong> That has real
478
+ consequences, so we would rather state them than let you assume otherwise:</p>
479
+ <ul>
480
+ <li>their terms and their privacy notice govern what happens to your Input and Output;</li>
481
+ <li>your data goes to them under <strong>your</strong> agreement with them, not ours;</li>
482
+ <li>they are <strong>not</strong> our sub-processor and they are not on our sub-processor list;</li>
483
+ <li>we have no control over what they do with your data, whether they retain it, whether they train on it, or
484
+ where in the world they process it; and</li>
485
+ <li>the key is yours to protect, to rotate and to revoke.</li>
486
+ </ul>
487
+ <p>Read that provider's terms before you connect it. The third-party services section applies to it as well.</p>
488
+ <h3 id="training" tabindex="-1">Training</h3>
489
+ <p><strong>We do not use your Input, your Output or your Customer Data to train machine-learning models for our own
490
+ purposes or for the benefit of other customers, unless you have expressly opted in.</strong> Where we engage a
491
+ model provider ourselves, our contract with it prohibits it from training on your content. Where you bring
492
+ your own provider, that is between you and them — see above.</p>
493
+ <h3 id="availability" tabindex="-1">Availability</h3>
494
+ <p>AI features may be offered as Beta Features, may change or be withdrawn, and may carry usage limits. Model
495
+ providers impose their own acceptable-use restrictions and can change or discontinue a model at short
496
+ notice, and we may have to pass those changes through to you. The section on modification of the Service
497
+ covers how we handle that.</p>
498
+ <h2 id="ever-async-a-bot-in-a-channel-other-people-are-talking-in" tabindex="-1">Ever Async: a bot in a channel other people are talking in</h2>
499
+ <p>the Ever Async hosted service is not an application your colleagues choose to open. It is a bot that one person
500
+ installs into a chat workspace, after which it observes what everyone in a connected conversation writes,
501
+ posts a public card into the thread, and sends the author a private message suggesting they rewrite what
502
+ they said. <strong>Almost everyone affected by it never signs in, never sees these Terms and never agreed to
503
+ anything.</strong> This section is about the consequences of that, and it governs over the general sections above
504
+ wherever the two differ.</p>
505
+ <h3 id="installing-it-is-a-decision-you-make-for-other-people" tabindex="-1">Installing it is a decision you make for other people</h3>
506
+ <p><strong>Whoever connects a workspace, a channel or a guild is the Customer, and the whole of these Terms binds
507
+ them.</strong> That is one administrator making a decision on behalf of everybody who posts in that conversation.</p>
508
+ <ul>
509
+ <li><strong>Everything anyone does in a connected conversation is treated as your act, not theirs and not ours.</strong>
510
+ You decide which conversations are connected, what the charter says, what the policy thresholds are and
511
+ who is allowed to change them.</li>
512
+ <li><strong>The people in those conversations are not our customers.</strong> We contract with you, we take instructions
513
+ from you, and we deal with you. They have no relationship with us, we give them no promises, and a
514
+ complaint about the bot goes to you first.</li>
515
+ <li><strong>Telling them is your job.</strong> Under your employment arrangements, your internal policies and data
516
+ protection law, whatever you owe the people in a connected conversation you owe them directly. <strong>We
517
+ will not announce the bot's presence for you, and its visible posts are not a notice.</strong> The privacy
518
+ annex sets out what we hold and for how long, so you have something accurate to give them.</li>
519
+ <li>If someone in a connected conversation writes to us instead, <strong>we will normally point them to you and
520
+ tell you that we have done so</strong>, unless the law requires otherwise.</li>
521
+ </ul>
522
+ <p>There are no seats and no per-user accounting in Ever Async. That does not reduce this obligation; it
523
+ removes the moment at which most products would have made you count the people involved.</p>
524
+ <h3 id="nothing-is-charged-for-ever-async" tabindex="-1">Nothing is charged for Ever Async</h3>
525
+ <p>There is no plan, no price, no checkout, no payment method that can be entered and no payment processor
526
+ anywhere in the product. <strong>We therefore publish no Refund Policy for it</strong>, because there is nothing to
527
+ refund and inventing a process would be worse than saying so.</p>
528
+ <p><strong>We may introduce a paid tier.</strong> If we do, the fee, billing and refund sections that this document
529
+ currently omits arrive with it, on the notice period in the section on changes to these Terms — before a
530
+ charge, never after one.</p>
531
+ <h3 id="this-is-an-early-product-and-we-are-not-going-to-dress-it-up" tabindex="-1">This is an early product and we are not going to dress it up</h3>
532
+ <p>Our own documentation calls Ever Async an MVP and the marketing site labels it <strong>Early MVP</strong>. The section
533
+ on free, trial and pre-release offerings above applies to it in full: <strong>no warranty, no service level, no
534
+ support commitment, no indemnity, and we may change or withdraw it at any time.</strong> The liability cap in
535
+ that section is the cap that applies to you.</p>
536
+ <p>Do not make Ever Async load-bearing for anything you cannot afford to have stop.</p>
537
+ <h3 id="the-source-code-a-licence-exists-the-source-does-not-yet" tabindex="-1">The source code: a licence exists, the source does not yet</h3>
538
+ <p>The product is licensed under the Apache License 2.0 and we intend to publish it. <strong>Today the repository
539
+ is private, so there is no published source for that licence to reach and no open-source grant to carve
540
+ out.</strong> That is why the general open-source section is deliberately absent from these Terms rather than
541
+ printed as if it applied.</p>
542
+ <p>Two consequences while that is true:</p>
543
+ <ul>
544
+ <li><strong>Nothing in these Terms grants you the source, and nothing entitles you to it.</strong> If you have obtained
545
+ it, you obtained it from us under whatever arrangement covered that.</li>
546
+ <li><strong>The self-hosting rules below still bind anyone who runs a deployment</strong>, because some people already
547
+ do. When the repository goes public, the open-source section returns and the split it describes —
548
+ licence governs the code, these Terms govern the hosted Service — applies from that moment.</li>
549
+ </ul>
550
+ <h3 id="the-writable-api-and-the-thing-a-self-hoster-gets-wrong" tabindex="-1">The writable API, and the thing a self-hoster gets wrong</h3>
551
+ <p><strong><code>/api/v1</code> accepts writes, and in the shipped configuration authentication is off.</strong> The default auth
552
+ mode is <code>local_trusted</code>, which means no credential is required and every caller is treated as the board
553
+ principal. Three of those routes change behaviour for an entire workspace:</p>
554
+ <ul>
555
+ <li><strong><code>PUT</code> policies</strong> — thresholds, quiet hours, which conversations are in scope;</li>
556
+ <li><strong><code>PUT</code> charter</strong> — the text the product quotes back to people and uses to justify a nudge; and</li>
557
+ <li><strong><code>POST</code> digest/send</strong> — which <strong>sends real messages to real people</strong>, immediately.</li>
558
+ </ul>
559
+ <p>Our own deployments set <code>mode = &quot;authenticated&quot;</code>. <strong>If you run your own and expose a hostname without
560
+ reading the security documentation, one request from anyone who finds it can rewrite your charter or
561
+ message your team.</strong> That is a configuration you chose, it is outside anything we operate, and the
562
+ consequences are yours. We state it here as plainly as we can rather than leave it to be discovered.</p>
563
+ <h3 id="connectors-act-with-credentials-you-supply-inside-systems-we-do-not-control" tabindex="-1">Connectors act with credentials you supply, inside systems we do not control</h3>
564
+ <p>Configuring a connector is your instruction to us, and it authorises us to reach the third-party system it
565
+ names using the credential you gave us, for as long as that credential is live:</p>
566
+ <ul>
567
+ <li><strong>GitHub</strong> — read pull requests and issues. <strong>A token that can read a private repository gives the
568
+ connector the same reach.</strong> Mint the narrowest token that does the job.</li>
569
+ <li><strong>Jira</strong> — read issues from your own Atlassian site with your own account email and API token.</li>
570
+ <li><strong>Ever Gauzy</strong> — read tasks and resolve a chat identity to an employee record, which is dealt with
571
+ separately below.</li>
572
+ </ul>
573
+ <p><strong>You warrant that you are entitled to grant that access</strong>, that the credential is yours to give, and that
574
+ using it this way is permitted where you are. What a connector reads is pulled back into a chat
575
+ conversation and shown to whoever is in it — <strong>so connecting a system is also a decision to surface its
576
+ contents to that audience.</strong> Check who is in the channel before you connect anything.</p>
577
+ <h3 id="the-gauzy-user-map-links-a-chat-identity-to-an-employee-record" tabindex="-1">The Gauzy user map links a chat identity to an employee record</h3>
578
+ <p>The Ever Gauzy connector takes a static map from a chat user id to an Ever Gauzy employee identifier. That
579
+ map is what makes &quot;my last task&quot; resolvable, and <strong>an administrator configures it without the employee
580
+ being involved</strong>.</p>
581
+ <p>By configuring it you confirm that you are entitled to make that linkage and to tell the people it covers
582
+ about it. <strong>Ever Gauzy is a separate service with its own terms and its own privacy notice</strong>, and once a
583
+ request crosses into it, those govern what happens there.</p>
584
+ <h3 id="artificial-intelligence-here-is-off-by-default-and-the-charter-travels-with-every-call" tabindex="-1">Artificial intelligence here is off by default, and the charter travels with every call</h3>
585
+ <p>The general AI section above applies. Three things specific to this product sit underneath it:</p>
586
+ <ul>
587
+ <li><strong>No model is called until you configure one.</strong> With no <code>[llm]</code> provider configured, classification runs
588
+ on plain heuristics and nothing leaves for a model at all.</li>
589
+ <li><strong>Sensitivity decides the rest.</strong> At the conservative setting the model is never consulted even when a
590
+ provider is configured. At balanced or high, the ambiguous middle of the classifier's range — and only
591
+ that middle — is sent to your chosen provider.</li>
592
+ <li><strong>Your charter is sent with every one of those calls.</strong> A charter that names customers, staff or
593
+ matters sends those names to a model provider each time the classifier runs. Write it accordingly.</li>
594
+ </ul>
595
+ <p>Where you configure your own provider key or your own OpenAI-compatible endpoint, <strong>that provider is
596
+ yours, not ours</strong>: your content goes to it under your agreement with it, we have no control over what it
597
+ retains, and it is not on our sub-processor list.</p>
598
+ <h3 id="what-the-bot-will-and-will-not-do-to-a-person" tabindex="-1">What the bot will and will not do to a person</h3>
599
+ <ul>
600
+ <li><strong>The public card is public.</strong> It carries a resolved link and a live status into the thread, where
601
+ everyone in the conversation sees it.</li>
602
+ <li><strong>The nudge is private.</strong> It goes to the author alone, after a grace window, and it quotes your own
603
+ charter rather than a rule of ours.</li>
604
+ <li><strong>Nothing is blocked, deleted or escalated.</strong> Ever Async suggests; it does not moderate, and it does not
605
+ report anyone to anyone.</li>
606
+ <li><strong>The output is unverified.</strong> A classification can be wrong, a resolved link can be the wrong link, and
607
+ a suggested rewrite can be worse than the original. Everything the general AI section says about that
608
+ applies here in full.</li>
609
+ </ul>
610
+ <p><strong>What you must not do with it is in our <a href="https://async.ever.co/aup">Acceptable Use Policy</a></strong> — in particular,
611
+ turning a nudge tool into a monitoring tool.</p>
612
+ <h3 id="rate-limits-and-protecting-the-shared-service" tabindex="-1">Rate limits and protecting the shared service</h3>
613
+ <p>Webhook ingress, connector fan-out and model calls all draw on infrastructure shared with other customers.
614
+ <strong>We may rate-limit, pause or disconnect a workspace, a conversation or an account where it threatens the
615
+ stability, security or capacity of that infrastructure</strong>, without that being a failure of the Service.
616
+ Where we can tell you first we will; where we cannot, we will tell you straight afterwards and why.</p>
617
+ <h2 id="support-and-service-levels" tabindex="-1">Support and service levels</h2>
618
+ <h3 id="the-support-you-get-depends-on-your-plan" tabindex="-1">The support you get depends on your plan</h3>
619
+ <p>We provide support for the Service as described for the plan you are on — in the plan description, in your
620
+ order, or on the support pages we publish for the Service. That description is where you will find the
621
+ channels open to you, the hours we staff them, and the kinds of problem we will help with. This section
622
+ sets the boundaries around it.</p>
623
+ <p>Support covers the Service as we operate it. It does not cover:</p>
624
+ <ul>
625
+ <li>a copy of the software that you run yourself, on your own infrastructure or someone else's;</li>
626
+ <li>third-party products, integrations, networks or devices you connect to the Service;</li>
627
+ <li>code, templates, automations or configuration built by you or by anyone other than us;</li>
628
+ <li>problems caused by use of the Service outside these Terms or outside our documentation;</li>
629
+ <li>training, migration, implementation and bespoke development, which we are happy to quote for separately.</li>
630
+ </ul>
631
+ <h3 id="there-is-no-sla-unless-we-have-signed-one-with-you" tabindex="-1">There is no SLA unless we have signed one with you</h3>
632
+ <p><strong>We make no commitment to any level of availability, uptime, response time or resolution time.</strong> If you
633
+ need one, we can agree a separate written service level agreement that sets its own targets, its own
634
+ method of measurement and its own service credits. <strong>Only a document of that kind creates an availability
635
+ commitment.</strong> A plan description, a status page, a proposal, a slide or an email from us does not, however
636
+ it is phrased.</p>
637
+ <h3 id="what-we-publish-about-performance-is-information-not-a-promise" tabindex="-1">What we publish about performance is information, not a promise</h3>
638
+ <p>Status pages, historical availability figures, incident histories, product roadmaps, expected release
639
+ dates, benchmark results and target support response times all describe how the Service has behaved or how
640
+ we currently expect it to behave.</p>
641
+ <p><strong>They are not commitments. They can change. Do not buy the Service, or build on it, on the assumption
642
+ that any of them will hold.</strong> If something matters to your decision, decide on what the Service does today
643
+ rather than on what a roadmap says it will do later.</p>
644
+ <h3 id="maintenance" tabindex="-1">Maintenance</h3>
645
+ <p>We maintain the Service, and maintenance sometimes means it is unavailable or degraded for a period.</p>
646
+ <ul>
647
+ <li><strong>Planned maintenance.</strong> We aim to schedule it outside the busiest hours for the Service and to give you
648
+ advance notice through whatever channel we normally use to reach you — a status page, an email, or a
649
+ notice inside the product.</li>
650
+ <li><strong>Emergency maintenance.</strong> Where we need to act immediately to protect the security, integrity or
651
+ stability of the Service, or to meet a legal obligation, <strong>we will do it without advance notice</strong>. We
652
+ will tell you what happened as soon as we reasonably can afterwards.</li>
653
+ </ul>
654
+ <p>Time spent in planned or emergency maintenance is not a failure to provide the Service and does not create
655
+ a right to a refund or a credit, unless a service level agreement we have signed says otherwise.</p>
656
+ <h3 id="free-and-pre-release-use-carries-no-support-commitment" tabindex="-1">Free and pre-release use carries no support commitment</h3>
657
+ <p>If you use the Service on a free plan, on a trial, or in beta, preview or early access, <strong>we owe you no
658
+ support at all</strong>. We often help anyway, and we would much rather hear about a problem than not — but do
659
+ not plan around a reply. The wider terms for those offerings are in the section on free, trial and
660
+ pre-release offerings below.</p>
661
+ <h3 id="when-you-ask-us-for-help" tabindex="-1">When you ask us for help</h3>
662
+ <p>To resolve a support request we may need to look at your account, and sometimes at content inside your
663
+ workspace. We do that only so far as it is needed to deal with what you asked us about, and in line with
664
+ our Privacy Policy and, where one applies to you, our Data Processing Addendum.</p>
665
+ <p>Anything you send us with a request — logs, screenshots, exports, sample records — we use for the same
666
+ limited purpose. <strong>Please take out anything you do not need us to see before you send it.</strong></p>
667
+ <h2 id="free-trial-and-pre-release-offerings" tabindex="-1">Free, trial and pre-release offerings</h2>
668
+ <h3 id="what-this-section-covers" tabindex="-1">What this section covers</h3>
669
+ <p>This section applies whenever you use the Service without paying for it, or use part of it before it is
670
+ finished. That includes:</p>
671
+ <ul>
672
+ <li>free plans and free tiers;</li>
673
+ <li>trials, evaluations and proofs of concept;</li>
674
+ <li>anything we label beta, preview, early access, experimental, labs or similar — whether that is a single
675
+ feature inside a paid plan or a whole product.</li>
676
+ </ul>
677
+ <p>Where this section conflicts with another part of these Terms, <strong>this section wins for that offering</strong>.</p>
678
+ <h3 id="what-you-are-getting-and-what-you-are-not" tabindex="-1">What you are getting, and what you are not</h3>
679
+ <p>We make these offerings available because they are useful to both of us. They come with almost nothing
680
+ attached, and we would rather say so here than have you find out later.</p>
681
+ <ul>
682
+ <li><strong>No warranty of any kind</strong>, including the limited warranty we give elsewhere in these Terms. A
683
+ pre-release feature may be incomplete, unstable, undocumented, or behave differently from one build to
684
+ the next.</li>
685
+ <li><strong>No service level and no support commitment.</strong> See the support section above.</li>
686
+ <li><strong>No indemnity from us.</strong> Where these Terms give you an indemnity for paid use of the Service, it does
687
+ not apply to your use of a free, trial or pre-release offering.</li>
688
+ <li><strong>We may change or withdraw them at any time, without notice and without liability to you</strong> — including
689
+ changing how a feature works, limiting it, moving it behind a paid plan, or stopping it altogether.</li>
690
+ <li><strong>Nothing here entitles you to access.</strong> We decide who gets a trial or a pre-release offering, and we
691
+ may end that access for any account at any time.</li>
692
+ </ul>
693
+ <h3 id="your-data-on-a-free-trial-or-pre-release-offering" tabindex="-1">Your data on a free, trial or pre-release offering</h3>
694
+ <p><strong>Do not put anything into one of these offerings that you cannot afford to lose.</strong></p>
695
+ <p>If a trial or evaluation ends without you moving to a paid plan, or we withdraw a free or pre-release
696
+ offering, <strong>we may delete the account, the workspace and everything in it</strong>. We will give you a chance to
697
+ export your data where we reasonably can, but the responsibility for exporting in time is yours. Data
698
+ created in a preview may also be reset between builds, and may not carry across when the feature becomes
699
+ generally available.</p>
700
+ <p>Our backups exist for our own operational continuity. They are not your archive, and you should not treat
701
+ them as one.</p>
702
+ <h3 id="our-liability-for-these-offerings" tabindex="-1">Our liability for these offerings</h3>
703
+ <p><strong>Where you use the Service on a free, trial, evaluation, beta or preview basis, our total liability to
704
+ you is capped at one hundred euros (EUR 100)</strong>, as set out in the limitation of liability section, and the
705
+ exclusions in that section apply in full. You pay us nothing, there are no fees to measure a cap against,
706
+ and we make these offerings available on that basis.</p>
707
+ <p>The carve-outs in that section still stand. Nothing here limits our liability for death or personal injury
708
+ caused by our negligence, for fraud, for gross negligence or wilful misconduct, or for anything that
709
+ cannot lawfully be limited — and if you are a consumer, your statutory rights are unaffected.</p>
710
+ <h3 id="unreleased-features-are-confidential" tabindex="-1">Unreleased features are confidential</h3>
711
+ <p>What you learn through a beta, preview or early-access offering, where it is not already public, is our
712
+ Confidential Information under the confidentiality section below. That includes the fact that the feature
713
+ exists, how it works, its documentation, how it performs, and any defect you find in it.</p>
714
+ <p>In particular, unless we have given you written permission:</p>
715
+ <ul>
716
+ <li>do not publish benchmarks, screenshots, recordings, reviews or descriptions of an unreleased feature;</li>
717
+ <li>do not share your access with anyone outside your own organisation.</li>
718
+ </ul>
719
+ <p>This stops applying to a particular feature once we make it generally available, or once we otherwise make
720
+ the information public ourselves.</p>
721
+ <h3 id="telling-us-what-you-think" tabindex="-1">Telling us what you think</h3>
722
+ <p>Pre-release access is worth more to us when you tell us how it went. If you do, the feedback section below
723
+ governs what we may do with what you send.</p>
724
+ <h2 id="confidentiality" tabindex="-1">Confidentiality</h2>
725
+ <p><strong>This section works both ways.</strong> It binds us exactly as it binds you.</p>
726
+ <h3 id="what-counts-as-confidential" tabindex="-1">What counts as confidential</h3>
727
+ <p>&quot;<strong>Confidential Information</strong>&quot; means information that one of us (the &quot;<strong>disclosing party</strong>&quot;) makes
728
+ available to the other (the &quot;<strong>receiving party</strong>&quot;) in connection with the Service, in any form, which is
729
+ either marked or described as confidential, or which a reasonable person would understand to be
730
+ confidential from its nature or from the circumstances in which it was disclosed.</p>
731
+ <ul>
732
+ <li><strong>Ours</strong> includes the non-public parts of the Service, our source code, security information,
733
+ architecture and infrastructure detail, unreleased features, non-public pricing, and our product plans.</li>
734
+ <li><strong>Yours</strong> includes the content and data you put into the Service, and your non-public business,
735
+ technical, financial and commercial information.</li>
736
+ </ul>
737
+ <p>The terms of any order between us are confidential to both of us.</p>
738
+ <p>Where Confidential Information is also personal data, how it is processed is governed by our Privacy
739
+ Policy and, where it applies to you, our Data Processing Addendum. Where those and this section both bite,
740
+ <strong>the stricter obligation applies</strong>.</p>
741
+ <h3 id="what-does-not-count" tabindex="-1">What does not count</h3>
742
+ <p>This section does not apply to information that:</p>
743
+ <ul>
744
+ <li>was public when it was disclosed, or later becomes public other than through a breach of this section;</li>
745
+ <li>the receiving party already had, free of any duty of confidence, before it was disclosed;</li>
746
+ <li>the receiving party develops independently, without using or referring to the disclosing party's
747
+ Confidential Information; or</li>
748
+ <li>a third party lawfully provides to the receiving party without a duty of confidence.</li>
749
+ </ul>
750
+ <p>The party relying on one of these has to be able to show that it applies.</p>
751
+ <h3 id="how-each-of-us-must-treat-it" tabindex="-1">How each of us must treat it</h3>
752
+ <p>Each of us will use the other's Confidential Information only to provide or receive the Service and to
753
+ perform these Terms, and will not disclose it except as this section permits.</p>
754
+ <p>Each of us will protect it with at least the care we use for our own confidential information of similar
755
+ importance — and never with less than reasonable care.</p>
756
+ <h3 id="who-it-may-be-shared-with" tabindex="-1">Who it may be shared with</h3>
757
+ <p>Each of us may disclose the other's Confidential Information to our employees, officers, contractors,
758
+ group companies and professional advisers who genuinely need it for that purpose and who are bound by
759
+ confidentiality duties at least as protective as these. We may also disclose it to our sub-processors so
760
+ far as needed to provide the Service, on the same footing.</p>
761
+ <p><strong>Each of us stays responsible for what those people do with it</strong>, as if we had done it ourselves.</p>
762
+ <h3 id="when-the-law-requires-disclosure" tabindex="-1">When the law requires disclosure</h3>
763
+ <p>If a law, a court, a regulator or a stock exchange requires disclosure, the receiving party may disclose —
764
+ but only what is actually required, and, where it is lawful and practical to do so, only after giving the
765
+ disclosing party advance notice and a reasonable opportunity to object or to seek protective treatment.
766
+ The receiving party will give reasonable cooperation with any such attempt, at the disclosing party's
767
+ cost.</p>
768
+ <h3 id="how-long-it-lasts" tabindex="-1">How long it lasts</h3>
769
+ <p>These obligations begin when the information is disclosed and continue for <strong>three (3) years</strong> after these
770
+ Terms come to an end.</p>
771
+ <p><strong>Anything that qualifies as a trade secret stays protected for as long as it remains a trade secret under
772
+ the applicable law</strong>, whether or not the three years have run.</p>
773
+ <h3 id="returning-or-destroying-it" tabindex="-1">Returning or destroying it</h3>
774
+ <p>When these Terms end — or earlier, if the disclosing party asks in writing — the receiving party will
775
+ return or destroy the Confidential Information it holds, and confirm in writing that it has done so if
776
+ asked. There are two exceptions:</p>
777
+ <ul>
778
+ <li>copies held in routine backups or archives that are not readily accessible in the ordinary course of
779
+ business; and</li>
780
+ <li>copies a party must keep to meet a legal or regulatory obligation.</li>
781
+ </ul>
782
+ <p>Anything kept under either exception stays subject to this section for as long as it is kept. Your own
783
+ content inside the Service is dealt with by the termination section — export and then deletion — rather
784
+ than by this one.</p>
785
+ <h3 id="no-licence-and-what-happens-on-a-breach" tabindex="-1">No licence, and what happens on a breach</h3>
786
+ <p>Nothing in this section transfers ownership of, or grants any licence in, Confidential Information.</p>
787
+ <p>Damages may not be an adequate remedy for a breach of this section, so either of us may seek an injunction
788
+ or other equitable relief without having to prove financial loss and without providing security, in
789
+ addition to any other remedy available.</p>
790
+ <h2 id="intellectual-property" tabindex="-1">Intellectual property</h2>
791
+ <h3 id="ours" tabindex="-1">Ours</h3>
792
+ <p>All intellectual property rights in the Service — including the software, its design, its user interface,
793
+ its documentation, and the Ever names, logos and other brand features — are owned by
794
+ <strong>Ever Co. LTD</strong>, a company registered in Israel under company number
795
+ 515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, or by its licensors.</p>
796
+ <p>Ever Technologies LTD operates the Service under licence from Ever Co. LTD. Your agreement for the
797
+ Service is with Ever Technologies LTD, and Ever Technologies LTD is solely responsible to you for the
798
+ Service under these Terms.</p>
799
+ <p>These Terms grant you a limited, non-exclusive, non-transferable, revocable right to use the Service while
800
+ your subscription is in force and you comply with these Terms. <strong>They transfer no ownership.</strong> Any right
801
+ not expressly granted is reserved. Separately licensed open-source components are governed by their own
802
+ licences, as described above.</p>
803
+ <p>You must not remove, obscure or alter any proprietary notice in the Service, and you must not use our
804
+ brand features except as permitted by these Terms or by our written permission.</p>
805
+ <h3 id="yours" tabindex="-1">Yours</h3>
806
+ <p>You retain all rights in the content and data you submit to the Service. You grant us a worldwide,
807
+ non-exclusive, royalty-free licence to host, store, copy, transmit, display and process that content
808
+ <strong>solely to the extent necessary to provide, secure, maintain and support the Service for you</strong>, and to
809
+ comply with our legal obligations. That licence ends when the content is deleted, except for copies
810
+ retained in routine backups for the period described in our Privacy Policy, and except where we are
811
+ required by law to retain it.</p>
812
+ <p>We will not use your content to train machine-learning models for our own purposes or for the benefit of
813
+ other customers, except where you have expressly opted in.</p>
814
+ <h2 id="feedback" tabindex="-1">Feedback</h2>
815
+ <p>If you send us ideas, suggestions, feature requests, bug reports or any other comment about the Service,
816
+ we may use them however we like — including building them into the Service and offering the result to
817
+ everyone else — with no obligation to you and no payment. <strong>You grant us a perpetual, irrevocable,
818
+ worldwide, royalty-free licence to use, copy, modify and exploit that feedback for any purpose</strong>, and you
819
+ confirm you are free to give it to us without breaching anyone else's rights. Please do send it: we would
820
+ rather hear it than not. But we cannot take feedback in confidence, so if an idea is one you want to keep,
821
+ keep it — this section does not touch any other confidentiality obligation between us.</p>
822
+ <h2 id="publicity-and-customer-references" tabindex="-1">Publicity and customer references</h2>
823
+ <p>We may say that you are a customer. That means we may use your name, trading name and logo — as they are
824
+ ordinarily presented — on our websites, in customer lists, in presentations and in sales and marketing
825
+ material, for the purpose of identifying you as a customer of the Service. Where you have published brand
826
+ guidelines, or given them to us, we will follow them.</p>
827
+ <p><strong>If you would rather we did not, write to legal@ever.co and we will stop.</strong> You do not need to give a
828
+ reason, and we will take you out of the material we control within a reasonable period. We will not recall
829
+ material that has already been printed or distributed, but we will not produce any more of it.</p>
830
+ <p>Anything beyond that plain identification needs your prior written consent, which is yours to give or
831
+ withhold as you see fit. That includes a case study, a quotation attributed to you or to one of your
832
+ people, a press release, a joint announcement, a logo in paid advertising, and any statement about what
833
+ you use the Service for or what results you got from it.</p>
834
+ <p>You may say that you use the Service and refer to it by name for that purpose. Beyond what this section
835
+ allows, neither of us gets any right in the other's trade marks, logos or brand features, and each of us
836
+ keeps ownership of our own.</p>
837
+ <h2 id="term-suspension-and-termination" tabindex="-1">Term, suspension and termination</h2>
838
+ <h3 id="how-long-this-agreement-lasts" tabindex="-1">How long this agreement lasts</h3>
839
+ <p>These Terms start when you first accept them or first use the Service, whichever happens sooner, and they
840
+ continue for as long as you hold an account or a subscription with us.</p>
841
+ <p>Where you pay for the Service, the term of your subscription is the period you have paid for, and it
842
+ renews as described in the refunds and cancellation section above. Where you use the Service free of
843
+ charge, on a trial, or in beta or preview, the term runs until you or we close the account.</p>
844
+ <h3 id="you-can-end-it" tabindex="-1">You can end it</h3>
845
+ <p>You may cancel at any time from your account settings, or by writing to legal@ever.co. Cancellation
846
+ takes effect at the end of the period you have already paid for, and your access continues until then.
847
+ You do not need a reason and there is no exit fee.</p>
848
+ <p>You may also terminate immediately if we are in material breach of these Terms and have not fixed it
849
+ within thirty (30) days of your written notice describing the breach.</p>
850
+ <h3 id="we-can-end-it-for-breach" tabindex="-1">We can end it for breach</h3>
851
+ <p>We may terminate these Terms and your account if you are in material breach and have not fixed it within
852
+ thirty (30) days of our written notice. We may terminate immediately, without a cure period, where the
853
+ breach cannot sensibly be cured — for example a serious breach of our Acceptable Use Policy, an attack on
854
+ the Service, or use of the Service to commit a crime.</p>
855
+ <p><strong>We will not terminate a paid subscription part-way through its term for our own convenience.</strong> If we
856
+ stop offering the Service or a material paid feature, the modification and discontinuation section below
857
+ governs what happens, including the refund you get.</p>
858
+ <p>We may close a free, trial, beta or preview account at any time on reasonable notice, and immediately
859
+ where the account is being abused.</p>
860
+ <h3 id="suspension" tabindex="-1">Suspension</h3>
861
+ <p>We may suspend your access, or the access of a particular user, immediately where:</p>
862
+ <ul>
863
+ <li>you breach the Acceptable Use Policy, or the Service is being used to harm someone else;</li>
864
+ <li>there is a security risk to the Service, to your data or to another customer's data;</li>
865
+ <li>an invoice is overdue and remains unpaid after we have asked you to pay it and given you a further
866
+ fourteen (14) days; or</li>
867
+ <li>the law, a court, a regulator or a sanctions or trade-control obligation requires us to.</li>
868
+ </ul>
869
+ <p>We will tell you before we suspend where that is practicable, and as soon as possible afterwards where it
870
+ is not. We will suspend no more than we need to — a single user, a single feature or a single workspace
871
+ rather than your whole account, where that resolves the problem. We will restore access once the cause is
872
+ resolved.</p>
873
+ <p><strong>Suspension does not stop your fees running.</strong> A suspended period is still part of your paid term and is
874
+ not refunded, unless the suspension turned out to be our mistake.</p>
875
+ <h3 id="what-happens-when-it-ends" tabindex="-1">What happens when it ends</h3>
876
+ <p>When these Terms end, for any reason:</p>
877
+ <ul>
878
+ <li>your right to use the Service ends, along with every licence we granted you under these Terms, and
879
+ accounts, workspaces and API credentials stop working;</li>
880
+ <li>fees that were already due stay payable, and fees for a period already served are not refunded;</li>
881
+ <li><strong>you get no refund except where our Refund Policy or another section of these Terms expressly gives
882
+ you one</strong>; and</li>
883
+ <li>you can export your data for a limited period, on the terms in the next section.</li>
884
+ </ul>
885
+ <p>The licence you granted us to host and process your content ends at the same time, apart from the copies
886
+ described in the intellectual property and data export sections.</p>
887
+ <h3 id="what-survives" tabindex="-1">What survives</h3>
888
+ <p>These sections continue to apply after termination, for as long as they are relevant: definitions and
889
+ interpretation; fees already accrued; intellectual property; confidentiality; data export after
890
+ termination; warranties and disclaimer; limitation of liability; indemnification; compliance, export
891
+ controls and sanctions; governing law and venue; notices; and this general section. Any other provision
892
+ that by its nature is meant to outlast the agreement also survives.</p>
893
+ <h2 id="getting-your-data-out-after-termination" tabindex="-1">Getting your data out after termination</h2>
894
+ <p><strong>You have thirty (30) days from the day your subscription or account ends to export your data.</strong> We keep
895
+ your content available for that window and then delete it. This section says exactly what that means, so
896
+ you can plan around real dates rather than a promise to be reasonable.</p>
897
+ <h3 id="the-window" tabindex="-1">The window</h3>
898
+ <p>The 30 days run from the effective date of termination or expiry — the day your access to the Service
899
+ ends, not the day you gave notice. During the window the account is limited: you can sign in and export,
900
+ but you cannot use the Service normally, and the account will not accept new data.</p>
901
+ <p><strong>Do not rely on the window. Export before you cancel.</strong> It is the only period in which we guarantee your
902
+ data is still there, and thirty days is not long if the person who held the admin account has left.</p>
903
+ <h3 id="how-to-export" tabindex="-1">How to export</h3>
904
+ <p>Three routes, and you may use any of them:</p>
905
+ <ul>
906
+ <li><strong>From the product.</strong> Where the product provides a self-service export, it is in your account or
907
+ workspace settings. This is the fastest route and it works throughout the window.</li>
908
+ <li><strong>Through our API.</strong> Your existing credentials keep working for export purposes for the whole window.
909
+ The endpoints are in the product documentation.</li>
910
+ <li><strong>By asking us.</strong> Write to legal@ever.co from the account's registered address. We will acknowledge
911
+ within five (5) business days and deliver the export within thirty (30) days of your request. <strong>A
912
+ request made inside the window is honoured even if the export itself is delivered after the window has
913
+ closed</strong> — so a request on day 29 is a valid request.</li>
914
+ </ul>
915
+ <p>Exports contain your account records and your workspace content in a structured, commonly used,
916
+ machine-readable format (CSV or JSON), together with any files you uploaded in the format we hold them.
917
+ They do not contain our internal system and security logs, data derived by us that is not your content,
918
+ or anything belonging to another customer.</p>
919
+ <h3 id="after-the-window" tabindex="-1">After the window</h3>
920
+ <p>Once the 30 days close, we delete your content from our live systems on our normal schedule, which
921
+ completes within a further thirty (30) days. That deletion is permanent and we cannot reverse it.</p>
922
+ <p><strong>Backups are different, and we will not pretend otherwise.</strong> We take backups for operational continuity
923
+ and they are rotated on their own cycle. We do not surgically remove one customer's records from a backup
924
+ set that already exists — doing so would compromise the integrity of the backup. Your data therefore
925
+ persists in backups until those backups age out and are overwritten in the ordinary rotation. While they
926
+ exist, backups are encrypted, access-controlled, and restored only as a whole in a disaster-recovery
927
+ event. The backup retention period for the Service is stated in our
928
+ <a href="https://async.ever.co/privacy">Privacy Policy</a>.</p>
929
+ <h3 id="what-we-keep-and-why" tabindex="-1">What we keep, and why</h3>
930
+ <p>We retain, beyond the periods above, only what we have to:</p>
931
+ <ul>
932
+ <li>billing, invoicing and tax records, for the period the law requires us to keep them;</li>
933
+ <li>records needed to establish, exercise or defend a legal claim, for as long as that claim is live or
934
+ could still be brought;</li>
935
+ <li>security and audit logs, for the periods set out in our <a href="https://async.ever.co/privacy">Privacy Policy</a>; and</li>
936
+ <li>anything a law, court order or regulator requires us to preserve.</li>
937
+ </ul>
938
+ <p>We do not keep your content for any other purpose, and we do not use retained copies to provide the
939
+ Service to anyone else.</p>
940
+ <h3 id="where-we-terminated-for-non-payment-or-abuse" tabindex="-1">Where we terminated for non-payment or abuse</h3>
941
+ <p>If we terminated or suspended your account for unpaid fees or for a breach of the Acceptable Use Policy,
942
+ we may withhold the export until the breach is remedied or the outstanding amount is paid. We will tell
943
+ you what is required and we will not use this as a way to keep your data.</p>
944
+ <p><strong>This never affects anyone's rights under data-protection law.</strong> An individual's right to obtain a copy
945
+ of their own personal data does not depend on your account being in good standing. Those requests go to
946
+ privacy@ever.co and we honour them regardless of the state of the account.</p>
947
+ <h3 id="where-we-act-as-your-processor" tabindex="-1">Where we act as your processor</h3>
948
+ <p>For personal data that you control and we merely process on your behalf — including employee monitoring
949
+ data, where the customer is the controller and we are the processor — deletion and return are governed by
950
+ our Data Processing Addendum and by your documented instructions. Where the Addendum and this section
951
+ differ on that data, the Addendum applies.</p>
952
+ <h2 id="warranties-and-disclaimer" tabindex="-1">Warranties and disclaimer</h2>
953
+ <p>We warrant only that we will provide the Service with reasonable skill and care, and that we will not
954
+ knowingly introduce malicious code into it.</p>
955
+ <p><strong>Beyond that limited warranty, and to the fullest extent permitted by law, the Service is provided &quot;as
956
+ is&quot; and &quot;as available&quot;, without warranty of any kind.</strong> We expressly disclaim all other warranties,
957
+ conditions, representations and terms, whether express, implied or statutory, including any implied
958
+ warranty of merchantability, satisfactory quality, fitness for a particular purpose, title or
959
+ non-infringement, and any warranty arising from a course of dealing or usage of trade.</p>
960
+ <p>In particular, and without limiting the above, <strong>we do not warrant that</strong>:</p>
961
+ <ul>
962
+ <li>the Service will be uninterrupted, timely, secure or error-free;</li>
963
+ <li>defects will be corrected, or corrected within any particular period;</li>
964
+ <li>the Service will meet your requirements or expectations, or produce any particular result;</li>
965
+ <li>data or output produced by the Service will be accurate, complete or reliable;</li>
966
+ <li>the Service will operate with any third-party product, service or integration you choose to use with it;
967
+ or</li>
968
+ <li>the Service will be available in, or lawful to use in, any particular jurisdiction.</li>
969
+ </ul>
970
+ <p><strong>No service level commitment applies</strong> unless we have separately agreed one with you in a written service
971
+ level agreement that expressly refers to these Terms. Uptime figures, roadmap statements, benchmarks and
972
+ support response times published on our websites or given in sales discussions are informational and do
973
+ not create any commitment.</p>
974
+ <p><strong>Free, trial, evaluation, beta, preview and early-access features carry no warranty at all.</strong> They are
975
+ provided for your evaluation, may be changed or withdrawn at any time without notice, may not be
976
+ supported, and may not perform as documented. Do not use them for anything you cannot afford to lose.</p>
977
+ <p><strong>You are responsible for your own backups.</strong> We maintain backups for our own operational continuity, and
978
+ you should not treat them as a substitute for retaining your own copies of your data.</p>
979
+ <p>Nothing in this section limits any warranty or right that cannot lawfully be excluded. <strong>If you are a
980
+ consumer, your statutory rights are unaffected</strong> by this section.</p>
981
+ <h2 id="indemnification" tabindex="-1">Indemnification</h2>
982
+ <p>This section runs both ways. We cover you if someone claims our software infringes their rights; you cover
983
+ us if the claim comes out of your data or your use of the Service.</p>
984
+ <h3 id="what-we-cover" tabindex="-1">What we cover</h3>
985
+ <p>We will defend you against a third-party claim that the Service, <strong>as we supply it</strong>, infringes that
986
+ party's patent, copyright, trade mark, database right or trade secret, and we will pay the damages finally
987
+ awarded against you on that claim, or the settlement amount we agree.</p>
988
+ <p>That is conditional on you:</p>
989
+ <ul>
990
+ <li>telling us in writing promptly once you know about the claim — late notice only reduces our obligation
991
+ to the extent the delay actually harmed our ability to defend;</li>
992
+ <li>letting us take sole control of the defence and of any settlement; and</li>
993
+ <li>giving us reasonable co-operation, information and authority to run the defence, at our expense.</li>
994
+ </ul>
995
+ <p>We will not settle on terms that admit fault on your part, impose a payment on you that we do not cover,
996
+ or require you to do something other than stop using the infringing part, unless you agree.</p>
997
+ <h3 id="what-we-do-not-cover" tabindex="-1">What we do not cover</h3>
998
+ <p>We owe you nothing under this section where the claim arises from:</p>
999
+ <ul>
1000
+ <li>any change to the Service made by anyone other than us;</li>
1001
+ <li>combining the Service with hardware, software, data, models or services we did not supply, where the
1002
+ claim would not have arisen without the combination;</li>
1003
+ <li>your Customer Data, or your instructions, designs or specifications;</li>
1004
+ <li>use of the Service in breach of these Terms, the Acceptable Use Policy or the documentation;</li>
1005
+ <li>your continued use of an allegedly infringing version after we have provided a non-infringing
1006
+ replacement and asked you to switch;</li>
1007
+ <li>a free, trial, evaluation, beta, preview or early-access offering, which carries no indemnity from us at
1008
+ all; or</li>
1009
+ <li>separately licensed open-source components, which come with their own licences and their own
1010
+ disclaimers.</li>
1011
+ </ul>
1012
+ <h3 id="what-we-will-do-about-it" tabindex="-1">What we will do about it</h3>
1013
+ <p>If the Service is held to infringe, or we think it might be, we may at our own cost and at our option:</p>
1014
+ <ul>
1015
+ <li>obtain the right for you to keep using it;</li>
1016
+ <li>modify or replace it so that it no longer infringes, without materially reducing what it does; or</li>
1017
+ <li>if neither of those is available on commercially reasonable terms, terminate the affected part of the
1018
+ Service and refund the unused portion of any fees you have prepaid for it.</li>
1019
+ </ul>
1020
+ <p><strong>Those remedies, together with the defence and payment above, are the whole of our liability, and your
1021
+ only remedy, for any claim that the Service infringes someone's intellectual property.</strong></p>
1022
+ <h3 id="what-you-cover" tabindex="-1">What you cover</h3>
1023
+ <p>You will defend us, and pay the damages finally awarded or agreed in settlement, against any third-party
1024
+ claim arising from:</p>
1025
+ <ul>
1026
+ <li>your Customer Data — including a claim that it infringes intellectual property, breaches privacy or
1027
+ publicity rights, is unlawful, or was collected or used without a proper basis;</li>
1028
+ <li>your use of the Service in breach of these Terms, the Acceptable Use Policy or applicable law; and</li>
1029
+ <li>your breach of the representations and warranties you give us in our Data Processing Addendum,
1030
+ including those about lawful basis, notices to the people whose data you process, impact assessments,
1031
+ and consultation with employee representatives or works councils.</li>
1032
+ </ul>
1033
+ <p>The same conditions apply in reverse: we will notify you promptly, let you control the defence, and
1034
+ co-operate at your expense. We will not settle without your agreement on the terms described above.</p>
1035
+ <p>Your obligations under this section are not subject to the cap in the limitation of liability section.
1036
+ Ours are, except where the law does not permit that.</p>
1037
+ <h3 id="if-you-are-a-consumer" tabindex="-1">If you are a consumer</h3>
1038
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
1039
+ or profession, the indemnity you would otherwise give us in this section does not apply to you.</strong> Our
1040
+ indemnity to you is unaffected, and so are your statutory rights.</p>
1041
+ <h2 id="limitation-of-liability" tabindex="-1">Limitation of liability</h2>
1042
+ <p><strong>Please read this section carefully. It limits what we can be held liable for.</strong></p>
1043
+ <h3 id="damages-we-exclude-entirely" tabindex="-1">Damages we exclude entirely</h3>
1044
+ <p>To the fullest extent permitted by law, we will not be liable for any indirect, consequential, incidental,
1045
+ special, exemplary or punitive damages, and we will not be liable — whether the claim is framed as direct
1046
+ or indirect — for:</p>
1047
+ <ul>
1048
+ <li>loss of profits, revenue, business, contracts, anticipated savings or opportunity;</li>
1049
+ <li>loss of goodwill or reputational harm;</li>
1050
+ <li>loss, corruption or inaccuracy of data, or the cost of recovering or reconstructing it;</li>
1051
+ <li>business interruption, or the cost of substitute goods or services;</li>
1052
+ <li>any liability you incur to your own customers, clients, personnel or other third parties.</li>
1053
+ </ul>
1054
+ <p>This applies however the liability arises — contract, tort (including negligence), breach of statutory
1055
+ duty, restitution or otherwise — and whether or not we were advised that such loss was possible.</p>
1056
+ <h3 id="cap-on-everything-else" tabindex="-1">Cap on everything else</h3>
1057
+ <p>Our total aggregate liability arising out of or in connection with these Terms and the Service, for all
1058
+ claims taken together, is limited to <strong>the total fees you actually paid us for the Service in the twelve
1059
+ (12) months immediately before the event giving rise to the claim</strong>.</p>
1060
+ <p><strong>Where you use the Service on a free, trial, evaluation, beta or preview basis, our total aggregate
1061
+ liability is limited to one hundred euros (EUR 100).</strong> No fees paid means no fees to measure a cap
1062
+ against, and we make free access available on that footing.</p>
1063
+ <h3 id="what-this-section-does-not-limit" tabindex="-1">What this section does not limit</h3>
1064
+ <p>Nothing in these Terms excludes or limits our liability for:</p>
1065
+ <ul>
1066
+ <li>death or personal injury caused by our negligence;</li>
1067
+ <li>fraud or fraudulent misrepresentation;</li>
1068
+ <li>gross negligence or wilful misconduct; or</li>
1069
+ <li>any other liability that cannot lawfully be excluded or limited.</li>
1070
+ </ul>
1071
+ <h3 id="if-you-are-a-consumer-1" tabindex="-1">If you are a consumer</h3>
1072
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
1073
+ or profession, this section applies to you only so far as the law permits.</strong> Your mandatory statutory
1074
+ rights, and any remedy the law gives you that cannot be excluded or limited by agreement, are unaffected.
1075
+ Where a limitation in this section would be unfair or unenforceable against you as a consumer, it does not
1076
+ apply to you, and the remainder of this section continues in force.</p>
1077
+ <h3 id="allocation-of-risk" tabindex="-1">Allocation of risk</h3>
1078
+ <p>You acknowledge that the fees for the Service reflect this allocation of risk, that these limits are a
1079
+ fundamental basis of the bargain between us, and that they apply even if a limited remedy is found to have
1080
+ failed of its essential purpose.</p>
1081
+ <h2 id="compliance-export-controls-and-sanctions" tabindex="-1">Compliance, export controls and sanctions</h2>
1082
+ <p>Each of us will comply with the laws that apply to it in performing under these Terms. You are
1083
+ responsible for the lawfulness of what you do with the Service, including in any country where your users
1084
+ are located.</p>
1085
+ <h3 id="sanctions-and-restricted-parties" tabindex="-1">Sanctions and restricted parties</h3>
1086
+ <p>You confirm, each time you use the Service, that:</p>
1087
+ <ul>
1088
+ <li>you are not named on, and are not owned or controlled by or acting for anyone named on, a sanctions or
1089
+ restricted-party list maintained by the European Union, the United Nations, the United Kingdom or the
1090
+ United States;</li>
1091
+ <li>you are not established, located or ordinarily resident in a country or territory subject to
1092
+ comprehensive sanctions or embargo; and</li>
1093
+ <li>you will not give access to the Service to anyone who falls into either category.</li>
1094
+ </ul>
1095
+ <p>Tell us promptly if any of that stops being true.</p>
1096
+ <h3 id="export-and-trade-controls" tabindex="-1">Export and trade controls</h3>
1097
+ <p>You will not export, re-export, transfer or make the Service or its output available in breach of export
1098
+ control, sanctions or trade law. You will not use the Service in connection with the development or
1099
+ production of weapons, or for any other end use that those laws restrict.</p>
1100
+ <p><strong>Where a sanctions or trade-control obligation requires it, we will suspend or terminate your access
1101
+ immediately and without liability to you.</strong> We will tell you what has happened as far as the law allows
1102
+ us to.</p>
1103
+ <h3 id="bribery-and-corruption" tabindex="-1">Bribery and corruption</h3>
1104
+ <p>Neither of us will offer, give, request or accept a bribe, kickback or other improper payment or
1105
+ advantage in connection with these Terms, and each of us will comply with the anti-bribery and
1106
+ anti-corruption laws that apply to it.</p>
1107
+ <h2 id="changing-and-discontinuing-the-service" tabindex="-1">Changing and discontinuing the Service</h2>
1108
+ <p>The Service is software we develop continuously. We add features, improve them, replace them and
1109
+ occasionally remove them. Most of those changes make the Service better and we make them without notice.
1110
+ Some do not, and this section says what we owe you when they do not.</p>
1111
+ <h3 id="material-adverse-changes-to-a-paid-feature" tabindex="-1">Material adverse changes to a paid feature</h3>
1112
+ <p>Where we intend to make a change that materially reduces a feature you pay for, we will give you at least
1113
+ thirty (30) days' notice before it takes effect, by email to your account address or by a notice inside
1114
+ the product.</p>
1115
+ <p>We may act faster than that where we have to — to close a security vulnerability, to comply with the law
1116
+ or a regulator, or because a third party we depend on has withdrawn something at short notice. In those
1117
+ cases we will give as much notice as the circumstances allow, and explain why.</p>
1118
+ <h3 id="if-we-discontinue-a-material-paid-feature-mid-term" tabindex="-1">If we discontinue a material paid feature mid-term</h3>
1119
+ <p><strong>If we withdraw a material feature you have prepaid for, or the Service itself, before the end of your
1120
+ paid term, we will refund the unused portion of what you prepaid for the affected part, calculated
1121
+ pro rata from the date the feature stops working.</strong></p>
1122
+ <p>That refund is deliberate. Reserving the right to change what we sell is only fair if we hand back the
1123
+ money for what we no longer deliver. It is also bounded: <strong>the pro-rata refund is your only remedy for a
1124
+ discontinuation, and we are not liable for any other loss you suffer because a feature went away.</strong> If
1125
+ you would rather not continue at all, you may terminate the affected subscription when the notice period
1126
+ expires.</p>
1127
+ <h3 id="free-trial-beta-and-preview" tabindex="-1">Free, trial, beta and preview</h3>
1128
+ <p>Anything provided free of charge, on trial, or as a beta, preview or early-access feature may be changed
1129
+ or withdrawn at any time, without notice and without compensation. There are no fees to refund, and this
1130
+ is part of what you accept in exchange for using it without paying.</p>
1131
+ <h3 id="apis-and-integrations" tabindex="-1">APIs and integrations</h3>
1132
+ <p>Where we deprecate an API endpoint, a data format or an integration that you build against, we will give
1133
+ reasonable notice and, where it is practicable, keep the previous version working for a transition
1134
+ period. Deprecation notices are published in the product documentation.</p>
1135
+ <h3 id="roadmaps-are-not-promises" tabindex="-1">Roadmaps are not promises</h3>
1136
+ <p>Nothing we say about future features — on our websites, in a roadmap, in a support conversation or in a
1137
+ sales discussion — is a commitment to build anything or to keep anything. Buy the Service for what it
1138
+ does today.</p>
1139
+ <h2 id="changes-to-these-terms" tabindex="-1">Changes to these Terms</h2>
1140
+ <p>We will change these Terms from time to time — because the Service changes, because the law changes, or
1141
+ because something here turned out to be unclear. Every version carries a version number and an effective
1142
+ date, printed at the top of the document. This one is version 1.0.2, in force from
1143
+ 2026-08-02.</p>
1144
+ <h3 id="changes-that-take-effect-immediately" tabindex="-1">Changes that take effect immediately</h3>
1145
+ <p>Corrections, clarifications, formatting, new contact details, and terms covering a new feature you are
1146
+ not using take effect when we publish them. So does any change we are required to make with immediate
1147
+ effect by law, a court or a regulator.</p>
1148
+ <h3 id="material-changes-thirty-days-notice" tabindex="-1">Material changes: thirty days' notice</h3>
1149
+ <p><strong>For any change that materially affects your rights or obligations, we will give you at least thirty
1150
+ (30) days' notice before the new version takes effect.</strong> That includes changes to fees and billing, to
1151
+ the limitation of liability, to the indemnities, to governing law and venue, and to how we may suspend or
1152
+ terminate your account.</p>
1153
+ <p>We give that notice by email to the address on your account, by a notice inside the product, or both. If
1154
+ you do not have an account with us, we give it by publishing the new version with its effective date
1155
+ before it applies.</p>
1156
+ <h3 id="your-choice" tabindex="-1">Your choice</h3>
1157
+ <p><strong>If you keep using the Service on or after the effective date, you accept the new version.</strong> If you do
1158
+ not want it, terminate before that date — from your account settings or by writing to legal@ever.co.
1159
+ If you terminate because you object to a material change, <strong>we will refund the unused portion of any
1160
+ period you have already paid for</strong>, calculated pro rata from the date your access ends.</p>
1161
+ <p>Where a change is significant enough that continued use is not a fair way to establish agreement, we will
1162
+ ask you to accept the new version explicitly the next time you sign in, and you will not be able to
1163
+ continue until you do.</p>
1164
+ <p>A change never applies retrospectively to a dispute that had already arisen before it took effect.</p>
1165
+ <h3 id="every-version-stays-available" tabindex="-1">Every version stays available</h3>
1166
+ <p>We keep an archive of every version we have published, with its effective date, linked from each
1167
+ document. You can always see which text was in force on a given date, and read the version you actually
1168
+ agreed to: <a href="https://async.ever.co/tos">https://async.ever.co/tos</a>.</p>
1169
+ <p>When you accept these Terms we record which version you accepted, when, and a fingerprint of the exact
1170
+ text — so that neither of us has to rely on memory about what was on the page that day.</p>
1171
+ <h3 id="if-you-are-a-consumer-2" tabindex="-1">If you are a consumer</h3>
1172
+ <p>If you are a consumer, nothing in this section obliges you to accept a change. You may reject it and stop
1173
+ using the Service, with the refund described above, and your statutory rights are unaffected.</p>
1174
+ <h2 id="force-majeure" tabindex="-1">Force majeure</h2>
1175
+ <p>Neither of us is liable for failing to perform, or for being late in performing, where the cause is
1176
+ outside our reasonable control.</p>
1177
+ <p>That includes natural disaster, fire, flood, extreme weather, epidemic, war, terrorism, civil unrest,
1178
+ industrial action other than by our own workforce, an act or order of a government or regulator, failure
1179
+ of electricity, cooling or telecommunications supply, failure or degradation of the public internet or of
1180
+ a transit, peering or DNS provider, a large-scale cyber attack including denial of service, and the
1181
+ failure, interruption or withdrawal of a third-party provider we depend on.</p>
1182
+ <p>The affected party must tell the other without undue delay, take reasonable steps to limit the effect,
1183
+ and resume performance as soon as it reasonably can.</p>
1184
+ <p><strong>Your obligation to pay is not excused.</strong> Fees for a period already served remain payable.</p>
1185
+ <p>If the event continues for more than thirty (30) consecutive days, either of us may terminate the
1186
+ affected subscription on written notice, and we will refund the unused portion of any period you have
1187
+ prepaid for it.</p>
1188
+ <h2 id="assignment-and-change-of-control" tabindex="-1">Assignment and change of control</h2>
1189
+ <h3 id="you" tabindex="-1">You</h3>
1190
+ <p>You may not assign, transfer, novate, charge or otherwise deal with these Terms, or any of your rights or
1191
+ obligations under them, without our prior written consent. <strong>We will not withhold or delay that consent
1192
+ unreasonably.</strong></p>
1193
+ <p>You may, on written notice to us and without our consent, transfer these Terms to a successor of the
1194
+ whole of your business, or of the part of it that uses the Service, following a merger, an acquisition or
1195
+ a sale of substantially all of your assets — provided the successor agrees in writing to be bound by
1196
+ these Terms and no fees are outstanding.</p>
1197
+ <h3 id="us" tabindex="-1">Us</h3>
1198
+ <p>We may assign or transfer these Terms, in whole or in part:</p>
1199
+ <ul>
1200
+ <li>to an affiliate; or</li>
1201
+ <li>in connection with a merger, acquisition, corporate reorganisation or a sale of all or substantially
1202
+ all of our assets or of the business line that provides the Service.</li>
1203
+ </ul>
1204
+ <p>We do not need your consent to do that, but we will tell you, and the transferee takes on our obligations
1205
+ to you under these Terms in full. If you are a consumer and a transfer by us would leave you worse off,
1206
+ you may terminate and we will refund the unused portion of any period you have prepaid.</p>
1207
+ <h3 id="both-of-us" tabindex="-1">Both of us</h3>
1208
+ <p>Any purported assignment in breach of this section is void. An assignment does not release either of us
1209
+ from an obligation that had already accrued before it took effect. Subject to all of the above, these
1210
+ Terms bind and benefit each party's permitted successors and assigns.</p>
1211
+ <p>Sub-contracting part of the Service to a supplier is not an assignment. We remain responsible to you for
1212
+ the Service, and our use of sub-processors for personal data is governed by our Data Processing Addendum
1213
+ and our published sub-processor list.</p>
1214
+ <h2 id="governing-law-and-where-disputes-are-heard" tabindex="-1">Governing law and where disputes are heard</h2>
1215
+ <p>These Terms, and any dispute or claim arising out of or in connection with them or with the Service —
1216
+ including a non-contractual one — are governed by the laws of the Republic of Bulgaria, without regard to its
1217
+ conflict-of-law rules.</p>
1218
+ <p>The exclusive forum for any such dispute or claim is the competent courts of Sofia, Bulgaria, and both of us submit to that
1219
+ jurisdiction.</p>
1220
+ <p>The United Nations Convention on Contracts for the International Sale of Goods does not apply to these
1221
+ Terms.</p>
1222
+ <p>Either of us may still apply to any court of competent jurisdiction for urgent interim or injunctive
1223
+ relief — for example to stop an infringement of intellectual property or a misuse of confidential
1224
+ information — without that being a breach of this section.</p>
1225
+ <p><strong>There is no arbitration clause and no class-action waiver in these Terms.</strong> We have not asked you to
1226
+ give up the right to go to court, or to bring a claim together with other people.</p>
1227
+ <h3 id="if-you-are-a-consumer-3" tabindex="-1">If you are a consumer</h3>
1228
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business,
1229
+ craft or profession, this section does not take anything away from you.</strong></p>
1230
+ <ul>
1231
+ <li>You keep the protection of the mandatory rules of the law of the country where you habitually live.
1232
+ Where those rules give you more than the laws of the Republic of Bulgaria does, they win.</li>
1233
+ <li>You may bring proceedings against us either in the competent courts of Sofia, Bulgaria or in the courts of the country where
1234
+ you live.</li>
1235
+ <li>We will bring proceedings against you only in the courts of the country where you live.</li>
1236
+ </ul>
1237
+ <h3 id="complaints-and-out-of-court-routes" tabindex="-1">Complaints, and out-of-court routes</h3>
1238
+ <p>Please tell us first. Write to legal@ever.co with what went wrong and what you would like us to do.
1239
+ Most disputes end there, and it costs you nothing to try.</p>
1240
+ <p>We are not currently committed to using any particular alternative dispute resolution body, and we are
1241
+ not obliged to use one. If you ask us to resolve a dispute through an ADR or mediation body, we will
1242
+ consider the request in good faith and tell you whether we agree.</p>
1243
+ <p>If you are a consumer, you can also approach the consumer protection authority or the recognised consumer
1244
+ ADR body in your own country. <strong>The European Commission's online dispute resolution platform closed on
1245
+ 20 July 2025, so there is no longer an EU-wide online form for this</strong> — the route now runs through your
1246
+ national body.</p>
1247
+ <p>For a complaint about how we handle personal data, write to privacy@ever.co. You may also complain to
1248
+ our lead supervisory authority, the Commission for Personal Data Protection (Комисия за защита на личните данни)
1249
+ (CPDP) —
1250
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a> — or to the data
1251
+ protection authority in the country where you live or work. Doing so does not affect any other remedy you
1252
+ have.</p>
1253
+ <h2 id="notices" tabindex="-1">Notices</h2>
1254
+ <h3 id="how-we-contact-you" tabindex="-1">How we contact you</h3>
1255
+ <p>We give you notice in one of three ways:</p>
1256
+ <ul>
1257
+ <li><strong>by email</strong>, to the address registered on your account;</li>
1258
+ <li><strong>inside the product</strong>, as a banner, a message or a prompt you have to acknowledge; or</li>
1259
+ <li><strong>by publishing it</strong>, where the notice applies to everyone — for example a new version of these Terms
1260
+ or of a policy — with its effective date shown on the page.</li>
1261
+ </ul>
1262
+ <p><strong>Keep the email address on your account current, and make sure someone reads it.</strong> A notice sent to the
1263
+ address you gave us counts as given, even if the person who set up the account has left. If your billing
1264
+ and technical contacts are different people, tell us, and we will use the right one.</p>
1265
+ <h3 id="how-you-contact-us" tabindex="-1">How you contact us</h3>
1266
+ <p>For anything to do with these Terms, write to legal@ever.co.</p>
1267
+ <p>A <strong>formal legal notice</strong> — terminating for breach, notifying a breach, making a claim, or invoking the
1268
+ indemnification section — must be in writing and sent to legal@ever.co. If you want the notice to be
1269
+ beyond argument, send a copy by post as well, to <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.</p>
1270
+ <p>A support ticket, a chat message, a social media post or a comment inside the product is not a formal
1271
+ legal notice, and neither is an email to an individual employee's personal work address.</p>
1272
+ <p>Privacy and data-protection matters go to privacy@ever.co; abuse and security reports go to
1273
+ abuse@ever.co. Those addresses are monitored, and using them gets you a faster answer than the legal
1274
+ address will.</p>
1275
+ <h3 id="when-a-notice-counts-as-received" tabindex="-1">When a notice counts as received</h3>
1276
+ <ul>
1277
+ <li><strong>Email</strong> — on the day it is sent, if that is a business day where the recipient is and it was sent
1278
+ before 17:00 local time; otherwise on the next business day. This does not apply if the sender receives
1279
+ a bounce or other non-delivery report.</li>
1280
+ <li><strong>Inside the product</strong> — when it is first displayed to you.</li>
1281
+ <li><strong>Published</strong> — on the effective date stated on the page, or on the date of publication if none is
1282
+ stated.</li>
1283
+ <li><strong>Post</strong> — on delivery, where a signature or delivery confirmation is obtained; otherwise on the fifth
1284
+ business day after posting.</li>
1285
+ </ul>
1286
+ <p>Notices must be in English.</p>
1287
+ <h2 id="general" tabindex="-1">General</h2>
1288
+ <h3 id="entire-agreement" tabindex="-1">Entire agreement</h3>
1289
+ <p>These Terms, together with the documents they incorporate, are the whole agreement between us about the
1290
+ Service, and they replace anything said or written before. Neither of us has relied on any statement,
1291
+ promise or representation that is not written down here. Nothing in this paragraph limits liability for
1292
+ fraud or fraudulent misrepresentation, and if you are a consumer it does not affect your statutory
1293
+ rights.</p>
1294
+ <h3 id="which-document-wins" tabindex="-1">Which document wins</h3>
1295
+ <p>With several documents in play, conflicts happen. Where two of them genuinely contradict each other, the
1296
+ higher one on this list applies:</p>
1297
+ <ol>
1298
+ <li>an order form or other agreement that we have both signed and that expressly varies these Terms;</li>
1299
+ <li>our Data Processing Addendum, on any question about the processing of personal data;</li>
1300
+ <li>the annex for the product you are using, which is specific to that product and may add to or change
1301
+ these Terms for it;</li>
1302
+ <li>these Terms; and</li>
1303
+ <li>our Acceptable Use Policy, Refund Policy, <a href="https://async.ever.co/privacy">Privacy Policy</a>,
1304
+ <a href="https://async.ever.co/cookies">Cookie Policy</a> and any other policy incorporated by reference.</li>
1305
+ </ol>
1306
+ <p>A document is only &quot;in conflict&quot; if both cannot be true at once. A term that adds something is not a
1307
+ conflict.</p>
1308
+ <h3 id="severability" tabindex="-1">Severability</h3>
1309
+ <p>If any provision of these Terms is held to be invalid or unenforceable, it is treated as modified to the
1310
+ smallest extent needed to make it valid, and if that is not possible it is severed. Everything else
1311
+ continues in force.</p>
1312
+ <h3 id="no-waiver" tabindex="-1">No waiver</h3>
1313
+ <p>If either of us delays or fails to enforce a right, that is not a waiver of it. A waiver only counts if
1314
+ it is in writing, and it applies only to the occasion it was given for. Exercising a right once or in
1315
+ part does not prevent exercising it again or in full.</p>
1316
+ <h3 id="nobody-else-can-enforce-these-terms" tabindex="-1">Nobody else can enforce these Terms</h3>
1317
+ <p>These Terms are between you and us. <strong>No one else has any right to enforce any part of them</strong>, and we do
1318
+ not need anyone else's consent to vary or terminate them.</p>
1319
+ <h3 id="we-are-independent-of-each-other" tabindex="-1">We are independent of each other</h3>
1320
+ <p>We are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency,
1321
+ franchise or employment relationship between us, and neither of us may bind the other or hold itself out
1322
+ as able to.</p>
1323
+ <h3 id="how-to-read-these-terms-1" tabindex="-1">How to read these Terms</h3>
1324
+ <p>Headings are there to help you find things and do not affect meaning. &quot;Including&quot; and &quot;for example&quot; never
1325
+ limit what comes before them. The singular includes the plural and the other way round. A reference to
1326
+ writing includes email.</p>
1327
+ <h3 id="acceptance-signature-and-records" tabindex="-1">Acceptance, signature and records</h3>
1328
+ <p>You may accept these Terms by clicking to accept, by signing electronically, or by using the Service —
1329
+ each is as valid as a signature on paper, and you agree not to challenge validity on the ground that
1330
+ acceptance was electronic. These Terms may be signed in counterparts, and an electronic or scanned copy
1331
+ counts as an original.</p>
1332
+ <p>We keep a record of your acceptance, including the version, the date and a fingerprint of the exact text
1333
+ you accepted.</p>
1334
+ <h3 id="language" tabindex="-1">Language</h3>
1335
+ <p><strong>The English version of these Terms is the authoritative one.</strong> We may publish translations to help you
1336
+ read them, but a translation is a convenience only, and where it differs from the English text the
1337
+ English text applies.</p>
1338
+ <h2 id="how-to-reach-us" tabindex="-1">How to reach us</h2>
1339
+ <p>Write to a person, not a form. These addresses are monitored and we answer them.</p>
1340
+ <ul>
1341
+ <li><strong>Contracts, these Terms, formal legal notices</strong> — legal@ever.co</li>
1342
+ <li><strong>Privacy, data protection, and requests about your personal data</strong> — privacy@ever.co</li>
1343
+ <li><strong>Abuse, security reports, and anything harmful you find on the Service</strong> — abuse@ever.co</li>
1344
+ </ul>
1345
+ <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
1346
+ number 204599535.</p>
1347
+ <p>We correspond in English.</p>
1348
+ <p>This document is version 1.0.2 of the Terms of Service for
1349
+ <a href="https://async.ever.co">async.ever.co</a>, in force from 2026-08-02. Earlier versions, with the
1350
+ dates they applied, are at <a href="https://async.ever.co/tos">https://async.ever.co/tos</a>.</p>