@ever-co/legal 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (146) hide show
  1. package/dist/content/aup/ever-corporate/en.html +667 -0
  2. package/dist/content/aup/ever-corporate/en.json +302 -0
  3. package/dist/content/aup/ever-demand/en.html +802 -0
  4. package/dist/content/aup/ever-demand/en.json +339 -0
  5. package/dist/content/aup/ever-rec/en.html +667 -0
  6. package/dist/content/aup/ever-rec/en.json +302 -0
  7. package/dist/content/aup/ever-teams/en.html +667 -0
  8. package/dist/content/aup/ever-teams/en.json +302 -0
  9. package/dist/content/aup/ever-works/en.html +667 -0
  10. package/dist/content/aup/ever-works/en.json +302 -0
  11. package/dist/content/aup/everiq/en.html +726 -0
  12. package/dist/content/aup/everiq/en.json +319 -0
  13. package/dist/content/aup/gauzy/en.html +715 -0
  14. package/dist/content/aup/gauzy/en.json +327 -0
  15. package/dist/content/aup/githands/en.html +864 -0
  16. package/dist/content/aup/githands/en.json +363 -0
  17. package/dist/content/aup/hust/en.html +781 -0
  18. package/dist/content/aup/hust/en.json +347 -0
  19. package/dist/content/aup/traduora/en.html +667 -0
  20. package/dist/content/aup/traduora/en.json +302 -0
  21. package/dist/content/cookies/ever-corporate/en.html +493 -0
  22. package/dist/content/cookies/ever-corporate/en.json +193 -0
  23. package/dist/content/cookies/ever-demand/en.html +633 -0
  24. package/dist/content/cookies/ever-demand/en.json +226 -0
  25. package/dist/content/cookies/ever-rec/en.html +564 -0
  26. package/dist/content/cookies/ever-rec/en.json +206 -0
  27. package/dist/content/cookies/ever-teams/en.html +549 -0
  28. package/dist/content/cookies/ever-teams/en.json +222 -0
  29. package/dist/content/cookies/ever-tech/en.html +469 -0
  30. package/dist/content/cookies/ever-tech/en.json +177 -0
  31. package/dist/content/cookies/ever-works/en.html +618 -0
  32. package/dist/content/cookies/ever-works/en.json +202 -0
  33. package/dist/content/cookies/everiq/en.html +437 -0
  34. package/dist/content/cookies/everiq/en.json +185 -0
  35. package/dist/content/cookies/gauzy/en.html +490 -0
  36. package/dist/content/cookies/gauzy/en.json +206 -0
  37. package/dist/content/cookies/githands/en.html +618 -0
  38. package/dist/content/cookies/githands/en.json +210 -0
  39. package/dist/content/cookies/hust/en.html +622 -0
  40. package/dist/content/cookies/hust/en.json +210 -0
  41. package/dist/content/cookies/traduora/en.html +580 -0
  42. package/dist/content/cookies/traduora/en.json +193 -0
  43. package/dist/content/dpa/ever-demand/en.html +1804 -0
  44. package/dist/content/dpa/ever-demand/en.json +628 -0
  45. package/dist/content/dpa/ever-rec/en.html +1963 -0
  46. package/dist/content/dpa/ever-rec/en.json +652 -0
  47. package/dist/content/dpa/ever-teams/en.html +1918 -0
  48. package/dist/content/dpa/ever-teams/en.json +648 -0
  49. package/dist/content/dpa/ever-works/en.html +1801 -0
  50. package/dist/content/dpa/ever-works/en.json +624 -0
  51. package/dist/content/dpa/gauzy/en.html +1836 -0
  52. package/dist/content/dpa/gauzy/en.json +632 -0
  53. package/dist/content/dpa/githands/en.html +1808 -0
  54. package/dist/content/dpa/githands/en.json +624 -0
  55. package/dist/content/dpa/hust/en.html +1804 -0
  56. package/dist/content/dpa/hust/en.json +632 -0
  57. package/dist/content/privacy/ever-corporate/en.html +1184 -0
  58. package/dist/content/privacy/ever-corporate/en.json +352 -0
  59. package/dist/content/privacy/ever-demand/en.html +1234 -0
  60. package/dist/content/privacy/ever-demand/en.json +364 -0
  61. package/dist/content/privacy/ever-rec/en.html +1250 -0
  62. package/dist/content/privacy/ever-rec/en.json +360 -0
  63. package/dist/content/privacy/ever-teams/en.html +1238 -0
  64. package/dist/content/privacy/ever-teams/en.json +368 -0
  65. package/dist/content/privacy/ever-tech/en.html +1127 -0
  66. package/dist/content/privacy/ever-tech/en.json +352 -0
  67. package/dist/content/privacy/ever-works/en.html +1284 -0
  68. package/dist/content/privacy/ever-works/en.json +364 -0
  69. package/dist/content/privacy/everiq/en.html +1172 -0
  70. package/dist/content/privacy/everiq/en.json +328 -0
  71. package/dist/content/privacy/gauzy/en.html +1281 -0
  72. package/dist/content/privacy/gauzy/en.json +356 -0
  73. package/dist/content/privacy/githands/en.html +1393 -0
  74. package/dist/content/privacy/githands/en.json +380 -0
  75. package/dist/content/privacy/hust/en.html +1359 -0
  76. package/dist/content/privacy/hust/en.json +368 -0
  77. package/dist/content/privacy/traduora/en.html +1146 -0
  78. package/dist/content/privacy/traduora/en.json +336 -0
  79. package/dist/content/refund/ever-works/en.html +595 -0
  80. package/dist/content/refund/ever-works/en.json +336 -0
  81. package/dist/content/refund/gauzy/en.html +595 -0
  82. package/dist/content/refund/gauzy/en.json +336 -0
  83. package/dist/content/refund/githands/en.html +647 -0
  84. package/dist/content/refund/githands/en.json +361 -0
  85. package/dist/content/refund/hust/en.html +595 -0
  86. package/dist/content/refund/hust/en.json +336 -0
  87. package/dist/content/security/ever-demand/en.html +900 -0
  88. package/dist/content/security/ever-demand/en.json +425 -0
  89. package/dist/content/security/ever-rec/en.html +768 -0
  90. package/dist/content/security/ever-rec/en.json +380 -0
  91. package/dist/content/security/ever-teams/en.html +768 -0
  92. package/dist/content/security/ever-teams/en.json +380 -0
  93. package/dist/content/security/ever-works/en.html +768 -0
  94. package/dist/content/security/ever-works/en.json +380 -0
  95. package/dist/content/security/gauzy/en.html +768 -0
  96. package/dist/content/security/gauzy/en.json +380 -0
  97. package/dist/content/security/githands/en.html +876 -0
  98. package/dist/content/security/githands/en.json +421 -0
  99. package/dist/content/security/hust/en.html +768 -0
  100. package/dist/content/security/hust/en.json +380 -0
  101. package/dist/content/subprocessors/ever-corporate/en.html +382 -0
  102. package/dist/content/subprocessors/ever-corporate/en.json +158 -0
  103. package/dist/content/subprocessors/ever-demand/en.html +452 -0
  104. package/dist/content/subprocessors/ever-demand/en.json +154 -0
  105. package/dist/content/subprocessors/ever-rec/en.html +439 -0
  106. package/dist/content/subprocessors/ever-rec/en.json +154 -0
  107. package/dist/content/subprocessors/ever-teams/en.html +477 -0
  108. package/dist/content/subprocessors/ever-teams/en.json +154 -0
  109. package/dist/content/subprocessors/ever-tech/en.html +335 -0
  110. package/dist/content/subprocessors/ever-tech/en.json +141 -0
  111. package/dist/content/subprocessors/ever-works/en.html +551 -0
  112. package/dist/content/subprocessors/ever-works/en.json +154 -0
  113. package/dist/content/subprocessors/everiq/en.html +296 -0
  114. package/dist/content/subprocessors/everiq/en.json +149 -0
  115. package/dist/content/subprocessors/gauzy/en.html +603 -0
  116. package/dist/content/subprocessors/gauzy/en.json +154 -0
  117. package/dist/content/subprocessors/githands/en.html +465 -0
  118. package/dist/content/subprocessors/githands/en.json +154 -0
  119. package/dist/content/subprocessors/hust/en.html +482 -0
  120. package/dist/content/subprocessors/hust/en.json +154 -0
  121. package/dist/content/subprocessors/traduora/en.html +362 -0
  122. package/dist/content/subprocessors/traduora/en.json +154 -0
  123. package/dist/content/tos/ever-corporate/en.html +973 -0
  124. package/dist/content/tos/ever-corporate/en.json +517 -0
  125. package/dist/content/tos/ever-demand/en.html +1598 -0
  126. package/dist/content/tos/ever-demand/en.json +783 -0
  127. package/dist/content/tos/ever-rec/en.html +1524 -0
  128. package/dist/content/tos/ever-rec/en.json +771 -0
  129. package/dist/content/tos/ever-teams/en.html +1551 -0
  130. package/dist/content/tos/ever-teams/en.json +779 -0
  131. package/dist/content/tos/ever-tech/en.html +762 -0
  132. package/dist/content/tos/ever-tech/en.json +421 -0
  133. package/dist/content/tos/ever-works/en.html +1552 -0
  134. package/dist/content/tos/ever-works/en.json +787 -0
  135. package/dist/content/tos/everiq/en.html +781 -0
  136. package/dist/content/tos/everiq/en.json +429 -0
  137. package/dist/content/tos/gauzy/en.html +1440 -0
  138. package/dist/content/tos/gauzy/en.json +755 -0
  139. package/dist/content/tos/githands/en.html +1542 -0
  140. package/dist/content/tos/githands/en.json +779 -0
  141. package/dist/content/tos/hust/en.html +1566 -0
  142. package/dist/content/tos/hust/en.json +787 -0
  143. package/dist/content/tos/traduora/en.html +1238 -0
  144. package/dist/content/tos/traduora/en.json +646 -0
  145. package/dist/index.json +26991 -0
  146. package/package.json +52 -0
@@ -0,0 +1,973 @@
1
+ <h1 id="terms-of-service" tabindex="-1">Terms of Service</h1>
2
+ <p><strong>Ever</strong> — <a href="https://ever.co">ever.co</a></p>
3
+ <p>Version 1.0.0 · 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 website and the
5
+ websites, applications and application programming interfaces we make available at <a href="https://ever.co">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://ever.co/privacy">Privacy Policy</a>, our
15
+ <a href="https://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://ever.co">ever.co</a> and the Ever website. 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://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="what-you-are-responsible-for" tabindex="-1">What you are responsible for</h2>
149
+ <p>We operate the Service. Almost everything about <em>how you use it</em> sits with you, and the list below is the
150
+ honest version of that split rather than a formality.</p>
151
+ <h3 id="lawful-use-and-your-own-compliance" tabindex="-1">Lawful use, and your own compliance</h3>
152
+ <p>Use the Service lawfully. <strong>You are responsible for working out which laws apply to you and for meeting
153
+ them</strong> — we do not know your sector, your jurisdictions, your regulator or your internal policies, and we do
154
+ not advise you on any of them.</p>
155
+ <p>That includes, where they apply to you: data protection and privacy law, employment and workplace law,
156
+ electronic marketing rules, consumer law, financial, health and other sector regulation, records-retention
157
+ duties, export controls and sanctions, and the terms of any third-party platform whose data you bring into
158
+ or push out of the Service.</p>
159
+ <h3 id="the-data-you-put-in" tabindex="-1">The data you put in</h3>
160
+ <p>You are responsible for the accuracy, quality, legality and integrity of your Customer Data, and for
161
+ deciding whether it should be in the Service at all.</p>
162
+ <p>Before you put personal data into the Service, <strong>it is your job — not ours — to give whatever notices and
163
+ obtain whatever consents or other lawful basis your own law requires</strong>, from the people the data is about.
164
+ That applies to your personnel, your customers, your candidates, your contacts, and anyone whose data
165
+ arrives through an integration you connect.</p>
166
+ <h3 id="features-that-record-or-measure-how-people-work" tabindex="-1">Features that record or measure how people work</h3>
167
+ <p>Where the Service includes features that record, capture or measure the activity of your personnel, <strong>you
168
+ decide whether to switch them on, on whom, and how</strong>. That decision is yours and so are the obligations that
169
+ follow from it.</p>
170
+ <p>Depending on where your people are, those obligations can include identifying a lawful basis for the
171
+ monitoring, telling each affected person clearly and in advance what is captured, completing a data
172
+ protection impact assessment, consulting a works council or employee representatives, and observing limits
173
+ on what may be captured and when. <strong>The rules differ sharply from country to country, and we make no claim
174
+ that any particular configuration is lawful anywhere.</strong> We supply the controls; you decide how to use them.</p>
175
+ <p>Your product annex and the DPA set out the capture types, the controls available to you and the express
176
+ representations you give us about all of this.</p>
177
+ <h3 id="your-end-users" tabindex="-1">Your End Users</h3>
178
+ <p>You are responsible for your End Users. <strong>Their acts and omissions in the Service count as yours.</strong> Make
179
+ sure they know what these Terms and the Acceptable Use Policy require of them, and that they follow both.</p>
180
+ <h3 id="your-backups-and-your-records" tabindex="-1">Your backups and your records</h3>
181
+ <p><strong>Keep your own copies of anything you cannot afford to lose.</strong> We run backups for our own operational
182
+ continuity, and they are not a substitute for your records. Export your data regularly using the tools the
183
+ Service provides, and do not rely on the Service as your only copy of anything — including anything you are
184
+ required by law to retain.</p>
185
+ <h3 id="equipment-connectivity-and-third-party-accounts" tabindex="-1">Equipment, connectivity and third-party accounts</h3>
186
+ <p>You provide the devices, browsers, operating systems, networks and internet connectivity needed to reach the
187
+ Service, and you keep them reasonably secure and up to date. You also provide and pay for any third-party
188
+ account or credential that an integration or a bring-your-own-key feature needs. We are not responsible for
189
+ problems caused by your own equipment, network or third-party accounts.</p>
190
+ <h3 id="acceptable-use-policy" tabindex="-1">Acceptable Use Policy</h3>
191
+ <p><strong>Our Acceptable Use Policy forms part of these Terms and applies every time the Service is used under your
192
+ Subscription.</strong> Breaching it is a breach of these Terms. We update the AUP from time to time — abuse changes
193
+ faster than contracts do — and the version in force when you use the Service is the one that applies. Where
194
+ a change to the AUP materially reduces what you are permitted to do, we will give you notice in the way the
195
+ changes section describes.</p>
196
+ <h2 id="privacy-and-data-protection" tabindex="-1">Privacy and data protection</h2>
197
+ <p>Three documents sit alongside these Terms and you should read them:</p>
198
+ <ul>
199
+ <li>our <a href="https://ever.co/privacy">Privacy Policy</a> — what we do with personal data in our own right, and the
200
+ rights you have over it;</li>
201
+ <li>our <a href="https://ever.co/cookies">Cookie Policy</a> — cookies and similar technologies on our websites and in the
202
+ Service; and</li>
203
+ <li>our <strong>Data Processing Addendum</strong> — how we handle personal data that you put into the Service about other
204
+ people. It forms part of these Terms and applies automatically. You do not need to sign it separately, and
205
+ you can obtain the current version from legal@ever.co.</li>
206
+ </ul>
207
+ <h3 id="who-is-responsible-for-what" tabindex="-1">Who is responsible for what</h3>
208
+ <p>Two different relationships run in parallel, and it matters which one you are looking at.</p>
209
+ <p><strong>We are the controller</strong> for the personal data we handle in our own relationship with you: your account and
210
+ administrator details, billing and tax records, support correspondence, security and audit logs, and people
211
+ who visit our websites or contact us. We decide why and how that data is processed, and our Privacy Policy
212
+ explains it.</p>
213
+ <p><strong>You are the controller and we are your processor</strong> for the personal data that you and your End Users put
214
+ into the Service about other people — your records and content, and, where the Service offers such features,
215
+ any data it captures about how your own personnel work. <strong>You decide why that data is processed and how; we
216
+ process it on your documented instructions and for no purpose of our own.</strong> The DPA sets out the detail:
217
+ instructions, confidentiality, security measures, sub-processors and how we notify you of changes, breach
218
+ notification, assistance with requests from individuals, assistance with impact assessments, audits,
219
+ international transfers, and deletion or return at the end.</p>
220
+ <p>We do not decide whether your processing is lawful, and we are not in a position to. <strong>That assessment, and
221
+ the notices, lawful bases and consultations that go with it, are yours</strong> — see the section on what you are
222
+ responsible for.</p>
223
+ <h3 id="contacting-us-about-data-protection" tabindex="-1">Contacting us about data protection</h3>
224
+ <p>Write to privacy@ever.co with any data protection question, or to exercise a right you have over
225
+ personal data we hold as controller. Our Privacy Policy explains how to make a request, how long we take,
226
+ and your right to complain to a supervisory authority. Ours is the
227
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
228
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may also complain to
229
+ the supervisory authority where you live or work.</p>
230
+ <p>If you are one of our customer's End Users and your question is about data held in their Workspace, that
231
+ request goes to them: they are the controller for it, not us.</p>
232
+ <h2 id="third-party-services-and-integrations" tabindex="-1">Third-party services and integrations</h2>
233
+ <p>The Service can connect to software you already use. Depending on the product, that includes identity and
234
+ single sign-on providers, payment processors, AI and model providers, project and issue trackers, time
235
+ tracking and activity sources, source-code and repository platforms, messaging and email delivery, calendars
236
+ and file storage, and analytics tools. Our sub-processor list names the specific vendors we engage; this
237
+ section is about the ones <strong>you</strong> choose to connect.</p>
238
+ <h3 id="connecting-one-is-your-instruction-to-us" tabindex="-1">Connecting one is your instruction to us</h3>
239
+ <p><strong>When you connect a third-party service, you are instructing us to exchange data with it, and you authorise
240
+ every exchange that integration needs in order to work</strong> — in both directions, for as long as the connection
241
+ is live.</p>
242
+ <p>Before you connect something, check what it will send and receive. The Service tells you the scope an
243
+ integration asks for, and you decide whether to grant it. You are responsible for holding a valid account
244
+ with the provider, for the credentials, API keys and tokens you supply, for the permissions you grant, and
245
+ for revoking them when they are no longer needed — including when a person leaves your organisation.</p>
246
+ <h3 id="their-terms-govern-them-not-ours" tabindex="-1">Their terms govern them, not ours</h3>
247
+ <p>A third-party service is supplied by that provider under <strong>its own terms and its own privacy notice</strong>, in a
248
+ contract between you and it. We are not a party to it, and these Terms do not change it.</p>
249
+ <p>That provider is not acting for us. It acts for you, on your instructions, under your agreement with it.
250
+ <strong>It is not our sub-processor, and we are not its</strong> — so it does not appear on our sub-processor list, and
251
+ what it does with the data you send it is a matter between the two of you. Where we engage a provider
252
+ ourselves to deliver the Service, the position is the opposite: it is our sub-processor and it is on that
253
+ list.</p>
254
+ <h3 id="what-we-are-not-responsible-for" tabindex="-1">What we are not responsible for</h3>
255
+ <p><strong>We are not responsible for third-party services, and we do not endorse them.</strong> We give no warranty about
256
+ any of them and we accept no liability for them, including for:</p>
257
+ <ul>
258
+ <li>whether they are available, accurate, secure, lawful or fit for what you want;</li>
259
+ <li>what they do with data you send them, how long they keep it and where;</li>
260
+ <li>what they charge you, and how they change what they charge;</li>
261
+ <li>any loss you suffer through using one; or</li>
262
+ <li>anything published on a third-party website that the Service links to.</li>
263
+ </ul>
264
+ <p><strong>If a third-party service changes, restricts, degrades, prices differently or shuts down — or if it changes
265
+ its API so an integration stops working — that is not a breach of these Terms by us.</strong> It does not entitle
266
+ you to a refund or a credit, and it does not release you from your Subscription. We will tell you when we
267
+ learn that an integration is affected, and we will restore it where we reasonably can.</p>
268
+ <p>We may also have to suspend or remove an integration at short notice — if the provider requires it, if it
269
+ stops being safe or lawful, or if it threatens the security or stability of the Service. We will give you as
270
+ much warning as the circumstances allow.</p>
271
+ <h3 id="extensions-plugins-and-marketplace-items" tabindex="-1">Extensions, plugins and marketplace items</h3>
272
+ <p>Plugins, extensions and add-ons published by anyone other than us are third-party services for the purposes
273
+ of this section, even where the Service helps you install them. We do not review or vet them unless we
274
+ expressly say that we have.</p>
275
+ <h2 id="annex-ever" tabindex="-1">Annex: Ever</h2>
276
+ <h3 id="what-these-terms-actually-govern" tabindex="-1">What these Terms actually govern</h3>
277
+ <p>the Ever website is a marketing site. These Terms cover reading it, browsing it, and sending us
278
+ something through one of its forms. That is the whole of their scope.</p>
279
+ <p><strong>They do not govern any Ever product.</strong> Each product we publish has its own terms, its own privacy notice
280
+ and its own domain, and the agreement for a product is the one on that product's site rather than this one.
281
+ A page here that describes a product, prices it, compares it or shows a roadmap for it is marketing about
282
+ that product. It is not the contract for it, and it cannot vary the contract for it.</p>
283
+ <p><strong>Nothing published on this site is an offer capable of acceptance.</strong> Package cards, indicative prices,
284
+ comparison pages, roadmap items and expected dates describe what we currently intend, and they change.
285
+ Where a paid engagement grows out of a conversation that started here, it is governed by the agreement,
286
+ order form or statement of work you actually sign with Ever Technologies LTD — that document, not a page on
287
+ this website, sets the price, the scope, the deliverables and the cancellation terms.</p>
288
+ <p><strong>Some of the links here leave our group entirely.</strong> Where a link takes you to a site operated by another
289
+ company, these Terms stop at the link. That company's terms govern what happens on its site, and where
290
+ something is sold there, that company is the seller and we are not.</p>
291
+ <h3 id="free-with-no-account-and-nothing-for-sale" tabindex="-1">Free, with no account and nothing for sale</h3>
292
+ <p>There is no account to create on ever.co, no subscription, no checkout and no payment method to
293
+ enter — there is no payment processor behind this site at all. <strong>Nothing is sold here, so there is nothing
294
+ to refund and this site publishes no refund terms.</strong> Where you buy one of our products, that product's own
295
+ terms govern the purchase and any refund of it.</p>
296
+ <h3 id="open-source-and-what-these-terms-do-not-touch" tabindex="-1">Open source, and what these Terms do not touch</h3>
297
+ <p>The products described on this site are open source under their own licences. <strong>Those licences govern the
298
+ code. These Terms govern this website.</strong> Nothing here grants you any right in the code, and nothing here
299
+ restricts, varies or adds a condition to a right an open-source licence already gives you.</p>
300
+ <p>The website's own code and content are a separate matter. They are not published under an open-source
301
+ licence, and the permission in the next section is the only one you have over them.</p>
302
+ <h3 id="what-you-may-do-with-what-is-on-the-site" tabindex="-1">What you may do with what is on the site</h3>
303
+ <p>You may view, download and print pages for your own personal use or for the internal purposes of your
304
+ organisation, leaving any notice of authorship intact.</p>
305
+ <p>You may not:</p>
306
+ <ul>
307
+ <li>extract the site in bulk, or crawl, scrape or harvest it — including the content management endpoints
308
+ behind the pages, and the job listings;</li>
309
+ <li>mirror or republish it, or frame it inside another site so that it appears to be part of that site;</li>
310
+ <li>use it, or the material published on it, to build a dataset or train a model without our written
311
+ permission; or</li>
312
+ <li>remove, obscure or alter any notice of ownership on it.</li>
313
+ </ul>
314
+ <p>We use technical measures against automated collection, and their presence is not an invitation to test
315
+ them.</p>
316
+ <h3 id="what-you-send-us-through-a-form" tabindex="-1">What you send us through a form</h3>
317
+ <p>The forms on this site — the enquiry and demo request, the job application, the pricing notification and
318
+ the newsletter box — send us whatever you type into them and whatever you attach.</p>
319
+ <p>By sending it, you confirm that:</p>
320
+ <ul>
321
+ <li>you are entitled to send it, and that sending it breaks no obligation you owe anyone else;</li>
322
+ <li>what you tell us about yourself is accurate;</li>
323
+ <li><strong>the file you attach contains no malware, no executable content and nothing built to evade inspection</strong>,
324
+ such as a password-protected archive; and</li>
325
+ <li>where your submission names other people — a referee, a manager, a colleague, a client — you have a
326
+ lawful basis for including them, and you have told them where they would expect to be told.</li>
327
+ </ul>
328
+ <p>We use what you send in order to answer you, to assess an application, and to keep a record of the
329
+ exchange. How long each of those lasts is in the <a href="https://ever.co/privacy">Privacy Policy</a> annex.</p>
330
+ <p><strong>We can refuse a submission.</strong> We may decline, quarantine or delete a submission or an attachment, block
331
+ an address or an IP range, and take a form offline, without notice, where we believe it is being abused.
332
+ We are not liable for doing any of that on a good-faith belief.</p>
333
+ <h3 id="applying-for-a-job-here" tabindex="-1">Applying for a job here</h3>
334
+ <ul>
335
+ <li>An application is not an offer, and it creates no employment or engagement relationship of any kind. We
336
+ are not obliged to reply, to interview you, or to explain a decision.</li>
337
+ <li>Apply for yourself, and truthfully. Do not apply in another person's name, invent credentials or history,
338
+ or use the careers form to probe our systems or to collect information about our people.</li>
339
+ <li><strong>We do not accept unsolicited CVs from recruitment agencies.</strong> A CV sent to us without an agreement
340
+ signed in advance creates no fee entitlement of any kind, whoever it is later hired by, and we delete it.</li>
341
+ </ul>
342
+ <p>What happens to your application, how long we keep it, and how to be kept on file for future roles are set
343
+ out in the <a href="https://ever.co/privacy">Privacy Policy</a> annex.</p>
344
+ <h3 id="the-comparison-pages" tabindex="-1">The comparison pages</h3>
345
+ <p>Some pages here compare our products with products made by other companies. Those comparisons are our own
346
+ view, prepared at a point in time from what was available to us, and other companies change their products
347
+ without telling us.</p>
348
+ <p><strong>Treat everything on this site as general information, and check anything that matters to your decision.</strong>
349
+ Nothing here is advice, and nothing here warrants how any product will behave for you. Where we name
350
+ another company's product or mark, we do it to identify that product; the mark stays theirs.</p>
351
+ <h3 id="thirteen-languages-one-governing-text" tabindex="-1">Thirteen languages, one governing text</h3>
352
+ <p>We publish this site in Arabic, Bulgarian, Chinese, Dutch, English, French, German, Hebrew, Italian,
353
+ Polish, Portuguese, Russian and Spanish. <strong>Where a translation and the English text disagree, the English
354
+ text governs.</strong> The other twelve are provided for convenience. Where the law of your own country gives you
355
+ a right to be dealt with in your own language, that right is unaffected.</p>
356
+ <h2 id="support-and-service-levels" tabindex="-1">Support and service levels</h2>
357
+ <h3 id="the-support-you-get-depends-on-your-plan" tabindex="-1">The support you get depends on your plan</h3>
358
+ <p>We provide support for the Service as described for the plan you are on — in the plan description, in your
359
+ order, or on the support pages we publish for the Service. That description is where you will find the
360
+ channels open to you, the hours we staff them, and the kinds of problem we will help with. This section
361
+ sets the boundaries around it.</p>
362
+ <p>Support covers the Service as we operate it. It does not cover:</p>
363
+ <ul>
364
+ <li>a copy of the software that you run yourself, on your own infrastructure or someone else's;</li>
365
+ <li>third-party products, integrations, networks or devices you connect to the Service;</li>
366
+ <li>code, templates, automations or configuration built by you or by anyone other than us;</li>
367
+ <li>problems caused by use of the Service outside these Terms or outside our documentation;</li>
368
+ <li>training, migration, implementation and bespoke development, which we are happy to quote for separately.</li>
369
+ </ul>
370
+ <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>
371
+ <p><strong>We make no commitment to any level of availability, uptime, response time or resolution time.</strong> If you
372
+ need one, we can agree a separate written service level agreement that sets its own targets, its own
373
+ method of measurement and its own service credits. <strong>Only a document of that kind creates an availability
374
+ commitment.</strong> A plan description, a status page, a proposal, a slide or an email from us does not, however
375
+ it is phrased.</p>
376
+ <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>
377
+ <p>Status pages, historical availability figures, incident histories, product roadmaps, expected release
378
+ dates, benchmark results and target support response times all describe how the Service has behaved or how
379
+ we currently expect it to behave.</p>
380
+ <p><strong>They are not commitments. They can change. Do not buy the Service, or build on it, on the assumption
381
+ that any of them will hold.</strong> If something matters to your decision, decide on what the Service does today
382
+ rather than on what a roadmap says it will do later.</p>
383
+ <h3 id="maintenance" tabindex="-1">Maintenance</h3>
384
+ <p>We maintain the Service, and maintenance sometimes means it is unavailable or degraded for a period.</p>
385
+ <ul>
386
+ <li><strong>Planned maintenance.</strong> We aim to schedule it outside the busiest hours for the Service and to give you
387
+ advance notice through whatever channel we normally use to reach you — a status page, an email, or a
388
+ notice inside the product.</li>
389
+ <li><strong>Emergency maintenance.</strong> Where we need to act immediately to protect the security, integrity or
390
+ stability of the Service, or to meet a legal obligation, <strong>we will do it without advance notice</strong>. We
391
+ will tell you what happened as soon as we reasonably can afterwards.</li>
392
+ </ul>
393
+ <p>Time spent in planned or emergency maintenance is not a failure to provide the Service and does not create
394
+ a right to a refund or a credit, unless a service level agreement we have signed says otherwise.</p>
395
+ <h3 id="free-and-pre-release-use-carries-no-support-commitment" tabindex="-1">Free and pre-release use carries no support commitment</h3>
396
+ <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
397
+ support at all</strong>. We often help anyway, and we would much rather hear about a problem than not — but do
398
+ not plan around a reply. The wider terms for those offerings are in the section on free, trial and
399
+ pre-release offerings below.</p>
400
+ <h3 id="when-you-ask-us-for-help" tabindex="-1">When you ask us for help</h3>
401
+ <p>To resolve a support request we may need to look at your account, and sometimes at content inside your
402
+ workspace. We do that only so far as it is needed to deal with what you asked us about, and in line with
403
+ our Privacy Policy and, where one applies to you, our Data Processing Addendum.</p>
404
+ <p>Anything you send us with a request — logs, screenshots, exports, sample records — we use for the same
405
+ limited purpose. <strong>Please take out anything you do not need us to see before you send it.</strong></p>
406
+ <h2 id="confidentiality" tabindex="-1">Confidentiality</h2>
407
+ <p><strong>This section works both ways.</strong> It binds us exactly as it binds you.</p>
408
+ <h3 id="what-counts-as-confidential" tabindex="-1">What counts as confidential</h3>
409
+ <p>&quot;<strong>Confidential Information</strong>&quot; means information that one of us (the &quot;<strong>disclosing party</strong>&quot;) makes
410
+ available to the other (the &quot;<strong>receiving party</strong>&quot;) in connection with the Service, in any form, which is
411
+ either marked or described as confidential, or which a reasonable person would understand to be
412
+ confidential from its nature or from the circumstances in which it was disclosed.</p>
413
+ <ul>
414
+ <li><strong>Ours</strong> includes the non-public parts of the Service, our source code, security information,
415
+ architecture and infrastructure detail, unreleased features, non-public pricing, and our product plans.</li>
416
+ <li><strong>Yours</strong> includes the content and data you put into the Service, and your non-public business,
417
+ technical, financial and commercial information.</li>
418
+ </ul>
419
+ <p>The terms of any order between us are confidential to both of us.</p>
420
+ <p>Where Confidential Information is also personal data, how it is processed is governed by our Privacy
421
+ Policy and, where it applies to you, our Data Processing Addendum. Where those and this section both bite,
422
+ <strong>the stricter obligation applies</strong>.</p>
423
+ <h3 id="what-does-not-count" tabindex="-1">What does not count</h3>
424
+ <p>This section does not apply to information that:</p>
425
+ <ul>
426
+ <li>was public when it was disclosed, or later becomes public other than through a breach of this section;</li>
427
+ <li>the receiving party already had, free of any duty of confidence, before it was disclosed;</li>
428
+ <li>the receiving party develops independently, without using or referring to the disclosing party's
429
+ Confidential Information; or</li>
430
+ <li>a third party lawfully provides to the receiving party without a duty of confidence.</li>
431
+ </ul>
432
+ <p>The party relying on one of these has to be able to show that it applies.</p>
433
+ <h3 id="how-each-of-us-must-treat-it" tabindex="-1">How each of us must treat it</h3>
434
+ <p>Each of us will use the other's Confidential Information only to provide or receive the Service and to
435
+ perform these Terms, and will not disclose it except as this section permits.</p>
436
+ <p>Each of us will protect it with at least the care we use for our own confidential information of similar
437
+ importance — and never with less than reasonable care.</p>
438
+ <h3 id="who-it-may-be-shared-with" tabindex="-1">Who it may be shared with</h3>
439
+ <p>Each of us may disclose the other's Confidential Information to our employees, officers, contractors,
440
+ group companies and professional advisers who genuinely need it for that purpose and who are bound by
441
+ confidentiality duties at least as protective as these. We may also disclose it to our sub-processors so
442
+ far as needed to provide the Service, on the same footing.</p>
443
+ <p><strong>Each of us stays responsible for what those people do with it</strong>, as if we had done it ourselves.</p>
444
+ <h3 id="when-the-law-requires-disclosure" tabindex="-1">When the law requires disclosure</h3>
445
+ <p>If a law, a court, a regulator or a stock exchange requires disclosure, the receiving party may disclose —
446
+ but only what is actually required, and, where it is lawful and practical to do so, only after giving the
447
+ disclosing party advance notice and a reasonable opportunity to object or to seek protective treatment.
448
+ The receiving party will give reasonable cooperation with any such attempt, at the disclosing party's
449
+ cost.</p>
450
+ <h3 id="how-long-it-lasts" tabindex="-1">How long it lasts</h3>
451
+ <p>These obligations begin when the information is disclosed and continue for <strong>three (3) years</strong> after these
452
+ Terms come to an end.</p>
453
+ <p><strong>Anything that qualifies as a trade secret stays protected for as long as it remains a trade secret under
454
+ the applicable law</strong>, whether or not the three years have run.</p>
455
+ <h3 id="returning-or-destroying-it" tabindex="-1">Returning or destroying it</h3>
456
+ <p>When these Terms end — or earlier, if the disclosing party asks in writing — the receiving party will
457
+ return or destroy the Confidential Information it holds, and confirm in writing that it has done so if
458
+ asked. There are two exceptions:</p>
459
+ <ul>
460
+ <li>copies held in routine backups or archives that are not readily accessible in the ordinary course of
461
+ business; and</li>
462
+ <li>copies a party must keep to meet a legal or regulatory obligation.</li>
463
+ </ul>
464
+ <p>Anything kept under either exception stays subject to this section for as long as it is kept. Your own
465
+ content inside the Service is dealt with by the termination section — export and then deletion — rather
466
+ than by this one.</p>
467
+ <h3 id="no-licence-and-what-happens-on-a-breach" tabindex="-1">No licence, and what happens on a breach</h3>
468
+ <p>Nothing in this section transfers ownership of, or grants any licence in, Confidential Information.</p>
469
+ <p>Damages may not be an adequate remedy for a breach of this section, so either of us may seek an injunction
470
+ or other equitable relief without having to prove financial loss and without providing security, in
471
+ addition to any other remedy available.</p>
472
+ <h2 id="intellectual-property" tabindex="-1">Intellectual property</h2>
473
+ <h3 id="ours" tabindex="-1">Ours</h3>
474
+ <p>All intellectual property rights in the Service — including the software, its design, its user interface,
475
+ its documentation, and the Ever names, logos and other brand features — are owned by
476
+ <strong>Ever Co. LTD</strong>, a company registered in Israel under company number
477
+ 515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, or by its licensors.</p>
478
+ <p>Ever Technologies LTD operates the Service under licence from Ever Co. LTD. Your agreement for the
479
+ Service is with Ever Technologies LTD, and Ever Technologies LTD is solely responsible to you for the
480
+ Service under these Terms.</p>
481
+ <p>These Terms grant you a limited, non-exclusive, non-transferable, revocable right to use the Service while
482
+ your subscription is in force and you comply with these Terms. <strong>They transfer no ownership.</strong> Any right
483
+ not expressly granted is reserved. Separately licensed open-source components are governed by their own
484
+ licences, as described above.</p>
485
+ <p>You must not remove, obscure or alter any proprietary notice in the Service, and you must not use our
486
+ brand features except as permitted by these Terms or by our written permission.</p>
487
+ <h3 id="yours" tabindex="-1">Yours</h3>
488
+ <p>You retain all rights in the content and data you submit to the Service. You grant us a worldwide,
489
+ non-exclusive, royalty-free licence to host, store, copy, transmit, display and process that content
490
+ <strong>solely to the extent necessary to provide, secure, maintain and support the Service for you</strong>, and to
491
+ comply with our legal obligations. That licence ends when the content is deleted, except for copies
492
+ retained in routine backups for the period described in our Privacy Policy, and except where we are
493
+ required by law to retain it.</p>
494
+ <p>We will not use your content to train machine-learning models for our own purposes or for the benefit of
495
+ other customers, except where you have expressly opted in.</p>
496
+ <h2 id="feedback" tabindex="-1">Feedback</h2>
497
+ <p>If you send us ideas, suggestions, feature requests, bug reports or any other comment about the Service,
498
+ we may use them however we like — including building them into the Service and offering the result to
499
+ everyone else — with no obligation to you and no payment. <strong>You grant us a perpetual, irrevocable,
500
+ worldwide, royalty-free licence to use, copy, modify and exploit that feedback for any purpose</strong>, and you
501
+ confirm you are free to give it to us without breaching anyone else's rights. Please do send it: we would
502
+ rather hear it than not. But we cannot take feedback in confidence, so if an idea is one you want to keep,
503
+ keep it — this section does not touch any other confidentiality obligation between us.</p>
504
+ <h2 id="publicity-and-customer-references" tabindex="-1">Publicity and customer references</h2>
505
+ <p>We may say that you are a customer. That means we may use your name, trading name and logo — as they are
506
+ ordinarily presented — on our websites, in customer lists, in presentations and in sales and marketing
507
+ material, for the purpose of identifying you as a customer of the Service. Where you have published brand
508
+ guidelines, or given them to us, we will follow them.</p>
509
+ <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
510
+ reason, and we will take you out of the material we control within a reasonable period. We will not recall
511
+ material that has already been printed or distributed, but we will not produce any more of it.</p>
512
+ <p>Anything beyond that plain identification needs your prior written consent, which is yours to give or
513
+ withhold as you see fit. That includes a case study, a quotation attributed to you or to one of your
514
+ people, a press release, a joint announcement, a logo in paid advertising, and any statement about what
515
+ you use the Service for or what results you got from it.</p>
516
+ <p>You may say that you use the Service and refer to it by name for that purpose. Beyond what this section
517
+ allows, neither of us gets any right in the other's trade marks, logos or brand features, and each of us
518
+ keeps ownership of our own.</p>
519
+ <h2 id="term-suspension-and-termination" tabindex="-1">Term, suspension and termination</h2>
520
+ <h3 id="how-long-this-agreement-lasts" tabindex="-1">How long this agreement lasts</h3>
521
+ <p>These Terms start when you first accept them or first use the Service, whichever happens sooner, and they
522
+ continue for as long as you hold an account or a subscription with us.</p>
523
+ <p>Where you pay for the Service, the term of your subscription is the period you have paid for, and it
524
+ renews as described in the refunds and cancellation section above. Where you use the Service free of
525
+ charge, on a trial, or in beta or preview, the term runs until you or we close the account.</p>
526
+ <h3 id="you-can-end-it" tabindex="-1">You can end it</h3>
527
+ <p>You may cancel at any time from your account settings, or by writing to legal@ever.co. Cancellation
528
+ takes effect at the end of the period you have already paid for, and your access continues until then.
529
+ You do not need a reason and there is no exit fee.</p>
530
+ <p>You may also terminate immediately if we are in material breach of these Terms and have not fixed it
531
+ within thirty (30) days of your written notice describing the breach.</p>
532
+ <h3 id="we-can-end-it-for-breach" tabindex="-1">We can end it for breach</h3>
533
+ <p>We may terminate these Terms and your account if you are in material breach and have not fixed it within
534
+ thirty (30) days of our written notice. We may terminate immediately, without a cure period, where the
535
+ breach cannot sensibly be cured — for example a serious breach of our Acceptable Use Policy, an attack on
536
+ the Service, or use of the Service to commit a crime.</p>
537
+ <p><strong>We will not terminate a paid subscription part-way through its term for our own convenience.</strong> If we
538
+ stop offering the Service or a material paid feature, the modification and discontinuation section below
539
+ governs what happens, including the refund you get.</p>
540
+ <p>We may close a free, trial, beta or preview account at any time on reasonable notice, and immediately
541
+ where the account is being abused.</p>
542
+ <h3 id="suspension" tabindex="-1">Suspension</h3>
543
+ <p>We may suspend your access, or the access of a particular user, immediately where:</p>
544
+ <ul>
545
+ <li>you breach the Acceptable Use Policy, or the Service is being used to harm someone else;</li>
546
+ <li>there is a security risk to the Service, to your data or to another customer's data;</li>
547
+ <li>an invoice is overdue and remains unpaid after we have asked you to pay it and given you a further
548
+ fourteen (14) days; or</li>
549
+ <li>the law, a court, a regulator or a sanctions or trade-control obligation requires us to.</li>
550
+ </ul>
551
+ <p>We will tell you before we suspend where that is practicable, and as soon as possible afterwards where it
552
+ is not. We will suspend no more than we need to — a single user, a single feature or a single workspace
553
+ rather than your whole account, where that resolves the problem. We will restore access once the cause is
554
+ resolved.</p>
555
+ <p><strong>Suspension does not stop your fees running.</strong> A suspended period is still part of your paid term and is
556
+ not refunded, unless the suspension turned out to be our mistake.</p>
557
+ <h3 id="what-happens-when-it-ends" tabindex="-1">What happens when it ends</h3>
558
+ <p>When these Terms end, for any reason:</p>
559
+ <ul>
560
+ <li>your right to use the Service ends, along with every licence we granted you under these Terms, and
561
+ accounts, workspaces and API credentials stop working;</li>
562
+ <li>fees that were already due stay payable, and fees for a period already served are not refunded;</li>
563
+ <li><strong>you get no refund except where our Refund Policy or another section of these Terms expressly gives
564
+ you one</strong>; and</li>
565
+ <li>you can export your data for a limited period, on the terms in the next section.</li>
566
+ </ul>
567
+ <p>The licence you granted us to host and process your content ends at the same time, apart from the copies
568
+ described in the intellectual property and data export sections.</p>
569
+ <h3 id="what-survives" tabindex="-1">What survives</h3>
570
+ <p>These sections continue to apply after termination, for as long as they are relevant: definitions and
571
+ interpretation; fees already accrued; intellectual property; confidentiality; data export after
572
+ termination; warranties and disclaimer; limitation of liability; indemnification; compliance, export
573
+ controls and sanctions; governing law and venue; notices; and this general section. Any other provision
574
+ that by its nature is meant to outlast the agreement also survives.</p>
575
+ <h2 id="warranties-and-disclaimer" tabindex="-1">Warranties and disclaimer</h2>
576
+ <p>We warrant only that we will provide the Service with reasonable skill and care, and that we will not
577
+ knowingly introduce malicious code into it.</p>
578
+ <p><strong>Beyond that limited warranty, and to the fullest extent permitted by law, the Service is provided &quot;as
579
+ is&quot; and &quot;as available&quot;, without warranty of any kind.</strong> We expressly disclaim all other warranties,
580
+ conditions, representations and terms, whether express, implied or statutory, including any implied
581
+ warranty of merchantability, satisfactory quality, fitness for a particular purpose, title or
582
+ non-infringement, and any warranty arising from a course of dealing or usage of trade.</p>
583
+ <p>In particular, and without limiting the above, <strong>we do not warrant that</strong>:</p>
584
+ <ul>
585
+ <li>the Service will be uninterrupted, timely, secure or error-free;</li>
586
+ <li>defects will be corrected, or corrected within any particular period;</li>
587
+ <li>the Service will meet your requirements or expectations, or produce any particular result;</li>
588
+ <li>data or output produced by the Service will be accurate, complete or reliable;</li>
589
+ <li>the Service will operate with any third-party product, service or integration you choose to use with it;
590
+ or</li>
591
+ <li>the Service will be available in, or lawful to use in, any particular jurisdiction.</li>
592
+ </ul>
593
+ <p><strong>No service level commitment applies</strong> unless we have separately agreed one with you in a written service
594
+ level agreement that expressly refers to these Terms. Uptime figures, roadmap statements, benchmarks and
595
+ support response times published on our websites or given in sales discussions are informational and do
596
+ not create any commitment.</p>
597
+ <p><strong>Free, trial, evaluation, beta, preview and early-access features carry no warranty at all.</strong> They are
598
+ provided for your evaluation, may be changed or withdrawn at any time without notice, may not be
599
+ supported, and may not perform as documented. Do not use them for anything you cannot afford to lose.</p>
600
+ <p><strong>You are responsible for your own backups.</strong> We maintain backups for our own operational continuity, and
601
+ you should not treat them as a substitute for retaining your own copies of your data.</p>
602
+ <p>Nothing in this section limits any warranty or right that cannot lawfully be excluded. <strong>If you are a
603
+ consumer, your statutory rights are unaffected</strong> by this section.</p>
604
+ <h2 id="indemnification" tabindex="-1">Indemnification</h2>
605
+ <p>This section runs both ways. We cover you if someone claims our software infringes their rights; you cover
606
+ us if the claim comes out of your data or your use of the Service.</p>
607
+ <h3 id="what-we-cover" tabindex="-1">What we cover</h3>
608
+ <p>We will defend you against a third-party claim that the Service, <strong>as we supply it</strong>, infringes that
609
+ party's patent, copyright, trade mark, database right or trade secret, and we will pay the damages finally
610
+ awarded against you on that claim, or the settlement amount we agree.</p>
611
+ <p>That is conditional on you:</p>
612
+ <ul>
613
+ <li>telling us in writing promptly once you know about the claim — late notice only reduces our obligation
614
+ to the extent the delay actually harmed our ability to defend;</li>
615
+ <li>letting us take sole control of the defence and of any settlement; and</li>
616
+ <li>giving us reasonable co-operation, information and authority to run the defence, at our expense.</li>
617
+ </ul>
618
+ <p>We will not settle on terms that admit fault on your part, impose a payment on you that we do not cover,
619
+ or require you to do something other than stop using the infringing part, unless you agree.</p>
620
+ <h3 id="what-we-do-not-cover" tabindex="-1">What we do not cover</h3>
621
+ <p>We owe you nothing under this section where the claim arises from:</p>
622
+ <ul>
623
+ <li>any change to the Service made by anyone other than us;</li>
624
+ <li>combining the Service with hardware, software, data, models or services we did not supply, where the
625
+ claim would not have arisen without the combination;</li>
626
+ <li>your Customer Data, or your instructions, designs or specifications;</li>
627
+ <li>use of the Service in breach of these Terms, the Acceptable Use Policy or the documentation;</li>
628
+ <li>your continued use of an allegedly infringing version after we have provided a non-infringing
629
+ replacement and asked you to switch;</li>
630
+ <li>a free, trial, evaluation, beta, preview or early-access offering, which carries no indemnity from us at
631
+ all; or</li>
632
+ <li>separately licensed open-source components, which come with their own licences and their own
633
+ disclaimers.</li>
634
+ </ul>
635
+ <h3 id="what-we-will-do-about-it" tabindex="-1">What we will do about it</h3>
636
+ <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>
637
+ <ul>
638
+ <li>obtain the right for you to keep using it;</li>
639
+ <li>modify or replace it so that it no longer infringes, without materially reducing what it does; or</li>
640
+ <li>if neither of those is available on commercially reasonable terms, terminate the affected part of the
641
+ Service and refund the unused portion of any fees you have prepaid for it.</li>
642
+ </ul>
643
+ <p><strong>Those remedies, together with the defence and payment above, are the whole of our liability, and your
644
+ only remedy, for any claim that the Service infringes someone's intellectual property.</strong></p>
645
+ <h3 id="what-you-cover" tabindex="-1">What you cover</h3>
646
+ <p>You will defend us, and pay the damages finally awarded or agreed in settlement, against any third-party
647
+ claim arising from:</p>
648
+ <ul>
649
+ <li>your Customer Data — including a claim that it infringes intellectual property, breaches privacy or
650
+ publicity rights, is unlawful, or was collected or used without a proper basis;</li>
651
+ <li>your use of the Service in breach of these Terms, the Acceptable Use Policy or applicable law; and</li>
652
+ <li>your breach of the representations and warranties you give us in our Data Processing Addendum,
653
+ including those about lawful basis, notices to the people whose data you process, impact assessments,
654
+ and consultation with employee representatives or works councils.</li>
655
+ </ul>
656
+ <p>The same conditions apply in reverse: we will notify you promptly, let you control the defence, and
657
+ co-operate at your expense. We will not settle without your agreement on the terms described above.</p>
658
+ <p>Your obligations under this section are not subject to the cap in the limitation of liability section.
659
+ Ours are, except where the law does not permit that.</p>
660
+ <h3 id="if-you-are-a-consumer" tabindex="-1">If you are a consumer</h3>
661
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
662
+ or profession, the indemnity you would otherwise give us in this section does not apply to you.</strong> Our
663
+ indemnity to you is unaffected, and so are your statutory rights.</p>
664
+ <h2 id="limitation-of-liability" tabindex="-1">Limitation of liability</h2>
665
+ <p><strong>Please read this section carefully. It limits what we can be held liable for.</strong></p>
666
+ <h3 id="damages-we-exclude-entirely" tabindex="-1">Damages we exclude entirely</h3>
667
+ <p>To the fullest extent permitted by law, we will not be liable for any indirect, consequential, incidental,
668
+ special, exemplary or punitive damages, and we will not be liable — whether the claim is framed as direct
669
+ or indirect — for:</p>
670
+ <ul>
671
+ <li>loss of profits, revenue, business, contracts, anticipated savings or opportunity;</li>
672
+ <li>loss of goodwill or reputational harm;</li>
673
+ <li>loss, corruption or inaccuracy of data, or the cost of recovering or reconstructing it;</li>
674
+ <li>business interruption, or the cost of substitute goods or services;</li>
675
+ <li>any liability you incur to your own customers, clients, personnel or other third parties.</li>
676
+ </ul>
677
+ <p>This applies however the liability arises — contract, tort (including negligence), breach of statutory
678
+ duty, restitution or otherwise — and whether or not we were advised that such loss was possible.</p>
679
+ <h3 id="cap-on-everything-else" tabindex="-1">Cap on everything else</h3>
680
+ <p>Our total aggregate liability arising out of or in connection with these Terms and the Service, for all
681
+ claims taken together, is limited to <strong>the total fees you actually paid us for the Service in the twelve
682
+ (12) months immediately before the event giving rise to the claim</strong>.</p>
683
+ <p><strong>Where you use the Service on a free, trial, evaluation, beta or preview basis, our total aggregate
684
+ liability is limited to one hundred euros (EUR 100).</strong> No fees paid means no fees to measure a cap
685
+ against, and we make free access available on that footing.</p>
686
+ <h3 id="what-this-section-does-not-limit" tabindex="-1">What this section does not limit</h3>
687
+ <p>Nothing in these Terms excludes or limits our liability for:</p>
688
+ <ul>
689
+ <li>death or personal injury caused by our negligence;</li>
690
+ <li>fraud or fraudulent misrepresentation;</li>
691
+ <li>gross negligence or wilful misconduct; or</li>
692
+ <li>any other liability that cannot lawfully be excluded or limited.</li>
693
+ </ul>
694
+ <h3 id="if-you-are-a-consumer-1" tabindex="-1">If you are a consumer</h3>
695
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
696
+ or profession, this section applies to you only so far as the law permits.</strong> Your mandatory statutory
697
+ rights, and any remedy the law gives you that cannot be excluded or limited by agreement, are unaffected.
698
+ Where a limitation in this section would be unfair or unenforceable against you as a consumer, it does not
699
+ apply to you, and the remainder of this section continues in force.</p>
700
+ <h3 id="allocation-of-risk" tabindex="-1">Allocation of risk</h3>
701
+ <p>You acknowledge that the fees for the Service reflect this allocation of risk, that these limits are a
702
+ fundamental basis of the bargain between us, and that they apply even if a limited remedy is found to have
703
+ failed of its essential purpose.</p>
704
+ <h2 id="compliance-export-controls-and-sanctions" tabindex="-1">Compliance, export controls and sanctions</h2>
705
+ <p>Each of us will comply with the laws that apply to it in performing under these Terms. You are
706
+ responsible for the lawfulness of what you do with the Service, including in any country where your users
707
+ are located.</p>
708
+ <h3 id="sanctions-and-restricted-parties" tabindex="-1">Sanctions and restricted parties</h3>
709
+ <p>You confirm, each time you use the Service, that:</p>
710
+ <ul>
711
+ <li>you are not named on, and are not owned or controlled by or acting for anyone named on, a sanctions or
712
+ restricted-party list maintained by the European Union, the United Nations, the United Kingdom or the
713
+ United States;</li>
714
+ <li>you are not established, located or ordinarily resident in a country or territory subject to
715
+ comprehensive sanctions or embargo; and</li>
716
+ <li>you will not give access to the Service to anyone who falls into either category.</li>
717
+ </ul>
718
+ <p>Tell us promptly if any of that stops being true.</p>
719
+ <h3 id="export-and-trade-controls" tabindex="-1">Export and trade controls</h3>
720
+ <p>You will not export, re-export, transfer or make the Service or its output available in breach of export
721
+ control, sanctions or trade law. You will not use the Service in connection with the development or
722
+ production of weapons, or for any other end use that those laws restrict.</p>
723
+ <p><strong>Where a sanctions or trade-control obligation requires it, we will suspend or terminate your access
724
+ immediately and without liability to you.</strong> We will tell you what has happened as far as the law allows
725
+ us to.</p>
726
+ <h3 id="bribery-and-corruption" tabindex="-1">Bribery and corruption</h3>
727
+ <p>Neither of us will offer, give, request or accept a bribe, kickback or other improper payment or
728
+ advantage in connection with these Terms, and each of us will comply with the anti-bribery and
729
+ anti-corruption laws that apply to it.</p>
730
+ <h2 id="changing-and-discontinuing-the-service" tabindex="-1">Changing and discontinuing the Service</h2>
731
+ <p>The Service is software we develop continuously. We add features, improve them, replace them and
732
+ occasionally remove them. Most of those changes make the Service better and we make them without notice.
733
+ Some do not, and this section says what we owe you when they do not.</p>
734
+ <h3 id="material-adverse-changes-to-a-paid-feature" tabindex="-1">Material adverse changes to a paid feature</h3>
735
+ <p>Where we intend to make a change that materially reduces a feature you pay for, we will give you at least
736
+ thirty (30) days' notice before it takes effect, by email to your account address or by a notice inside
737
+ the product.</p>
738
+ <p>We may act faster than that where we have to — to close a security vulnerability, to comply with the law
739
+ or a regulator, or because a third party we depend on has withdrawn something at short notice. In those
740
+ cases we will give as much notice as the circumstances allow, and explain why.</p>
741
+ <h3 id="if-we-discontinue-a-material-paid-feature-mid-term" tabindex="-1">If we discontinue a material paid feature mid-term</h3>
742
+ <p><strong>If we withdraw a material feature you have prepaid for, or the Service itself, before the end of your
743
+ paid term, we will refund the unused portion of what you prepaid for the affected part, calculated
744
+ pro rata from the date the feature stops working.</strong></p>
745
+ <p>That refund is deliberate. Reserving the right to change what we sell is only fair if we hand back the
746
+ money for what we no longer deliver. It is also bounded: <strong>the pro-rata refund is your only remedy for a
747
+ discontinuation, and we are not liable for any other loss you suffer because a feature went away.</strong> If
748
+ you would rather not continue at all, you may terminate the affected subscription when the notice period
749
+ expires.</p>
750
+ <h3 id="free-trial-beta-and-preview" tabindex="-1">Free, trial, beta and preview</h3>
751
+ <p>Anything provided free of charge, on trial, or as a beta, preview or early-access feature may be changed
752
+ or withdrawn at any time, without notice and without compensation. There are no fees to refund, and this
753
+ is part of what you accept in exchange for using it without paying.</p>
754
+ <h3 id="apis-and-integrations" tabindex="-1">APIs and integrations</h3>
755
+ <p>Where we deprecate an API endpoint, a data format or an integration that you build against, we will give
756
+ reasonable notice and, where it is practicable, keep the previous version working for a transition
757
+ period. Deprecation notices are published in the product documentation.</p>
758
+ <h3 id="roadmaps-are-not-promises" tabindex="-1">Roadmaps are not promises</h3>
759
+ <p>Nothing we say about future features — on our websites, in a roadmap, in a support conversation or in a
760
+ sales discussion — is a commitment to build anything or to keep anything. Buy the Service for what it
761
+ does today.</p>
762
+ <h2 id="changes-to-these-terms" tabindex="-1">Changes to these Terms</h2>
763
+ <p>We will change these Terms from time to time — because the Service changes, because the law changes, or
764
+ because something here turned out to be unclear. Every version carries a version number and an effective
765
+ date, printed at the top of the document. This one is version 1.0.0, in force from
766
+ 2026-08-02.</p>
767
+ <h3 id="changes-that-take-effect-immediately" tabindex="-1">Changes that take effect immediately</h3>
768
+ <p>Corrections, clarifications, formatting, new contact details, and terms covering a new feature you are
769
+ not using take effect when we publish them. So does any change we are required to make with immediate
770
+ effect by law, a court or a regulator.</p>
771
+ <h3 id="material-changes-thirty-days-notice" tabindex="-1">Material changes: thirty days' notice</h3>
772
+ <p><strong>For any change that materially affects your rights or obligations, we will give you at least thirty
773
+ (30) days' notice before the new version takes effect.</strong> That includes changes to fees and billing, to
774
+ the limitation of liability, to the indemnities, to governing law and venue, and to how we may suspend or
775
+ terminate your account.</p>
776
+ <p>We give that notice by email to the address on your account, by a notice inside the product, or both. If
777
+ you do not have an account with us, we give it by publishing the new version with its effective date
778
+ before it applies.</p>
779
+ <h3 id="your-choice" tabindex="-1">Your choice</h3>
780
+ <p><strong>If you keep using the Service on or after the effective date, you accept the new version.</strong> If you do
781
+ not want it, terminate before that date — from your account settings or by writing to legal@ever.co.
782
+ If you terminate because you object to a material change, <strong>we will refund the unused portion of any
783
+ period you have already paid for</strong>, calculated pro rata from the date your access ends.</p>
784
+ <p>Where a change is significant enough that continued use is not a fair way to establish agreement, we will
785
+ ask you to accept the new version explicitly the next time you sign in, and you will not be able to
786
+ continue until you do.</p>
787
+ <p>A change never applies retrospectively to a dispute that had already arisen before it took effect.</p>
788
+ <h3 id="every-version-stays-available" tabindex="-1">Every version stays available</h3>
789
+ <p>We keep an archive of every version we have published, with its effective date, linked from each
790
+ document. You can always see which text was in force on a given date, and read the version you actually
791
+ agreed to: <a href="https://ever.co/tos">https://ever.co/tos</a>.</p>
792
+ <p>When you accept these Terms we record which version you accepted, when, and a fingerprint of the exact
793
+ text — so that neither of us has to rely on memory about what was on the page that day.</p>
794
+ <h3 id="if-you-are-a-consumer-2" tabindex="-1">If you are a consumer</h3>
795
+ <p>If you are a consumer, nothing in this section obliges you to accept a change. You may reject it and stop
796
+ using the Service, with the refund described above, and your statutory rights are unaffected.</p>
797
+ <h2 id="force-majeure" tabindex="-1">Force majeure</h2>
798
+ <p>Neither of us is liable for failing to perform, or for being late in performing, where the cause is
799
+ outside our reasonable control.</p>
800
+ <p>That includes natural disaster, fire, flood, extreme weather, epidemic, war, terrorism, civil unrest,
801
+ industrial action other than by our own workforce, an act or order of a government or regulator, failure
802
+ of electricity, cooling or telecommunications supply, failure or degradation of the public internet or of
803
+ a transit, peering or DNS provider, a large-scale cyber attack including denial of service, and the
804
+ failure, interruption or withdrawal of a third-party provider we depend on.</p>
805
+ <p>The affected party must tell the other without undue delay, take reasonable steps to limit the effect,
806
+ and resume performance as soon as it reasonably can.</p>
807
+ <p><strong>Your obligation to pay is not excused.</strong> Fees for a period already served remain payable.</p>
808
+ <p>If the event continues for more than thirty (30) consecutive days, either of us may terminate the
809
+ affected subscription on written notice, and we will refund the unused portion of any period you have
810
+ prepaid for it.</p>
811
+ <h2 id="assignment-and-change-of-control" tabindex="-1">Assignment and change of control</h2>
812
+ <h3 id="you" tabindex="-1">You</h3>
813
+ <p>You may not assign, transfer, novate, charge or otherwise deal with these Terms, or any of your rights or
814
+ obligations under them, without our prior written consent. <strong>We will not withhold or delay that consent
815
+ unreasonably.</strong></p>
816
+ <p>You may, on written notice to us and without our consent, transfer these Terms to a successor of the
817
+ whole of your business, or of the part of it that uses the Service, following a merger, an acquisition or
818
+ a sale of substantially all of your assets — provided the successor agrees in writing to be bound by
819
+ these Terms and no fees are outstanding.</p>
820
+ <h3 id="us" tabindex="-1">Us</h3>
821
+ <p>We may assign or transfer these Terms, in whole or in part:</p>
822
+ <ul>
823
+ <li>to an affiliate; or</li>
824
+ <li>in connection with a merger, acquisition, corporate reorganisation or a sale of all or substantially
825
+ all of our assets or of the business line that provides the Service.</li>
826
+ </ul>
827
+ <p>We do not need your consent to do that, but we will tell you, and the transferee takes on our obligations
828
+ to you under these Terms in full. If you are a consumer and a transfer by us would leave you worse off,
829
+ you may terminate and we will refund the unused portion of any period you have prepaid.</p>
830
+ <h3 id="both-of-us" tabindex="-1">Both of us</h3>
831
+ <p>Any purported assignment in breach of this section is void. An assignment does not release either of us
832
+ from an obligation that had already accrued before it took effect. Subject to all of the above, these
833
+ Terms bind and benefit each party's permitted successors and assigns.</p>
834
+ <p>Sub-contracting part of the Service to a supplier is not an assignment. We remain responsible to you for
835
+ the Service, and our use of sub-processors for personal data is governed by our Data Processing Addendum
836
+ and our published sub-processor list.</p>
837
+ <h2 id="governing-law-and-where-disputes-are-heard" tabindex="-1">Governing law and where disputes are heard</h2>
838
+ <p>These Terms, and any dispute or claim arising out of or in connection with them or with the Service —
839
+ including a non-contractual one — are governed by the laws of the Republic of Bulgaria, without regard to its
840
+ conflict-of-law rules.</p>
841
+ <p>The exclusive forum for any such dispute or claim is the competent courts of Sofia, Bulgaria, and both of us submit to that
842
+ jurisdiction.</p>
843
+ <p>The United Nations Convention on Contracts for the International Sale of Goods does not apply to these
844
+ Terms.</p>
845
+ <p>Either of us may still apply to any court of competent jurisdiction for urgent interim or injunctive
846
+ relief — for example to stop an infringement of intellectual property or a misuse of confidential
847
+ information — without that being a breach of this section.</p>
848
+ <p><strong>There is no arbitration clause and no class-action waiver in these Terms.</strong> We have not asked you to
849
+ give up the right to go to court, or to bring a claim together with other people.</p>
850
+ <h3 id="if-you-are-a-consumer-3" tabindex="-1">If you are a consumer</h3>
851
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business,
852
+ craft or profession, this section does not take anything away from you.</strong></p>
853
+ <ul>
854
+ <li>You keep the protection of the mandatory rules of the law of the country where you habitually live.
855
+ Where those rules give you more than the laws of the Republic of Bulgaria does, they win.</li>
856
+ <li>You may bring proceedings against us either in the competent courts of Sofia, Bulgaria or in the courts of the country where
857
+ you live.</li>
858
+ <li>We will bring proceedings against you only in the courts of the country where you live.</li>
859
+ </ul>
860
+ <h3 id="complaints-and-out-of-court-routes" tabindex="-1">Complaints, and out-of-court routes</h3>
861
+ <p>Please tell us first. Write to legal@ever.co with what went wrong and what you would like us to do.
862
+ Most disputes end there, and it costs you nothing to try.</p>
863
+ <p>We are not currently committed to using any particular alternative dispute resolution body, and we are
864
+ not obliged to use one. If you ask us to resolve a dispute through an ADR or mediation body, we will
865
+ consider the request in good faith and tell you whether we agree.</p>
866
+ <p>If you are a consumer, you can also approach the consumer protection authority or the recognised consumer
867
+ ADR body in your own country. <strong>The European Commission's online dispute resolution platform closed on
868
+ 20 July 2025, so there is no longer an EU-wide online form for this</strong> — the route now runs through your
869
+ national body.</p>
870
+ <p>For a complaint about how we handle personal data, write to privacy@ever.co. You may also complain to
871
+ our lead supervisory authority, the Commission for Personal Data Protection (Комисия за защита на личните данни)
872
+ (CPDP) —
873
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a> — or to the data
874
+ protection authority in the country where you live or work. Doing so does not affect any other remedy you
875
+ have.</p>
876
+ <h2 id="notices" tabindex="-1">Notices</h2>
877
+ <h3 id="how-we-contact-you" tabindex="-1">How we contact you</h3>
878
+ <p>We give you notice in one of three ways:</p>
879
+ <ul>
880
+ <li><strong>by email</strong>, to the address registered on your account;</li>
881
+ <li><strong>inside the product</strong>, as a banner, a message or a prompt you have to acknowledge; or</li>
882
+ <li><strong>by publishing it</strong>, where the notice applies to everyone — for example a new version of these Terms
883
+ or of a policy — with its effective date shown on the page.</li>
884
+ </ul>
885
+ <p><strong>Keep the email address on your account current, and make sure someone reads it.</strong> A notice sent to the
886
+ address you gave us counts as given, even if the person who set up the account has left. If your billing
887
+ and technical contacts are different people, tell us, and we will use the right one.</p>
888
+ <h3 id="how-you-contact-us" tabindex="-1">How you contact us</h3>
889
+ <p>For anything to do with these Terms, write to legal@ever.co.</p>
890
+ <p>A <strong>formal legal notice</strong> — terminating for breach, notifying a breach, making a claim, or invoking the
891
+ indemnification section — must be in writing and sent to legal@ever.co. If you want the notice to be
892
+ 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>
893
+ <p>A support ticket, a chat message, a social media post or a comment inside the product is not a formal
894
+ legal notice, and neither is an email to an individual employee's personal work address.</p>
895
+ <p>Privacy and data-protection matters go to privacy@ever.co; abuse and security reports go to
896
+ abuse@ever.co. Those addresses are monitored, and using them gets you a faster answer than the legal
897
+ address will.</p>
898
+ <h3 id="when-a-notice-counts-as-received" tabindex="-1">When a notice counts as received</h3>
899
+ <ul>
900
+ <li><strong>Email</strong> — on the day it is sent, if that is a business day where the recipient is and it was sent
901
+ before 17:00 local time; otherwise on the next business day. This does not apply if the sender receives
902
+ a bounce or other non-delivery report.</li>
903
+ <li><strong>Inside the product</strong> — when it is first displayed to you.</li>
904
+ <li><strong>Published</strong> — on the effective date stated on the page, or on the date of publication if none is
905
+ stated.</li>
906
+ <li><strong>Post</strong> — on delivery, where a signature or delivery confirmation is obtained; otherwise on the fifth
907
+ business day after posting.</li>
908
+ </ul>
909
+ <p>Notices must be in English.</p>
910
+ <h2 id="general" tabindex="-1">General</h2>
911
+ <h3 id="entire-agreement" tabindex="-1">Entire agreement</h3>
912
+ <p>These Terms, together with the documents they incorporate, are the whole agreement between us about the
913
+ Service, and they replace anything said or written before. Neither of us has relied on any statement,
914
+ promise or representation that is not written down here. Nothing in this paragraph limits liability for
915
+ fraud or fraudulent misrepresentation, and if you are a consumer it does not affect your statutory
916
+ rights.</p>
917
+ <h3 id="which-document-wins" tabindex="-1">Which document wins</h3>
918
+ <p>With several documents in play, conflicts happen. Where two of them genuinely contradict each other, the
919
+ higher one on this list applies:</p>
920
+ <ol>
921
+ <li>an order form or other agreement that we have both signed and that expressly varies these Terms;</li>
922
+ <li>our Data Processing Addendum, on any question about the processing of personal data;</li>
923
+ <li>the annex for the product you are using, which is specific to that product and may add to or change
924
+ these Terms for it;</li>
925
+ <li>these Terms; and</li>
926
+ <li>our Acceptable Use Policy, Refund Policy, <a href="https://ever.co/privacy">Privacy Policy</a>,
927
+ <a href="https://ever.co/cookies">Cookie Policy</a> and any other policy incorporated by reference.</li>
928
+ </ol>
929
+ <p>A document is only &quot;in conflict&quot; if both cannot be true at once. A term that adds something is not a
930
+ conflict.</p>
931
+ <h3 id="severability" tabindex="-1">Severability</h3>
932
+ <p>If any provision of these Terms is held to be invalid or unenforceable, it is treated as modified to the
933
+ smallest extent needed to make it valid, and if that is not possible it is severed. Everything else
934
+ continues in force.</p>
935
+ <h3 id="no-waiver" tabindex="-1">No waiver</h3>
936
+ <p>If either of us delays or fails to enforce a right, that is not a waiver of it. A waiver only counts if
937
+ it is in writing, and it applies only to the occasion it was given for. Exercising a right once or in
938
+ part does not prevent exercising it again or in full.</p>
939
+ <h3 id="nobody-else-can-enforce-these-terms" tabindex="-1">Nobody else can enforce these Terms</h3>
940
+ <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
941
+ not need anyone else's consent to vary or terminate them.</p>
942
+ <h3 id="we-are-independent-of-each-other" tabindex="-1">We are independent of each other</h3>
943
+ <p>We are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency,
944
+ franchise or employment relationship between us, and neither of us may bind the other or hold itself out
945
+ as able to.</p>
946
+ <h3 id="how-to-read-these-terms-1" tabindex="-1">How to read these Terms</h3>
947
+ <p>Headings are there to help you find things and do not affect meaning. &quot;Including&quot; and &quot;for example&quot; never
948
+ limit what comes before them. The singular includes the plural and the other way round. A reference to
949
+ writing includes email.</p>
950
+ <h3 id="acceptance-signature-and-records" tabindex="-1">Acceptance, signature and records</h3>
951
+ <p>You may accept these Terms by clicking to accept, by signing electronically, or by using the Service —
952
+ each is as valid as a signature on paper, and you agree not to challenge validity on the ground that
953
+ acceptance was electronic. These Terms may be signed in counterparts, and an electronic or scanned copy
954
+ counts as an original.</p>
955
+ <p>We keep a record of your acceptance, including the version, the date and a fingerprint of the exact text
956
+ you accepted.</p>
957
+ <h3 id="language" tabindex="-1">Language</h3>
958
+ <p><strong>The English version of these Terms is the authoritative one.</strong> We may publish translations to help you
959
+ read them, but a translation is a convenience only, and where it differs from the English text the
960
+ English text applies.</p>
961
+ <h2 id="how-to-reach-us" tabindex="-1">How to reach us</h2>
962
+ <p>Write to a person, not a form. These addresses are monitored and we answer them.</p>
963
+ <ul>
964
+ <li><strong>Contracts, these Terms, formal legal notices</strong> — legal@ever.co</li>
965
+ <li><strong>Privacy, data protection, and requests about your personal data</strong> — privacy@ever.co</li>
966
+ <li><strong>Abuse, security reports, and anything harmful you find on the Service</strong> — abuse@ever.co</li>
967
+ </ul>
968
+ <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
969
+ number 204599535.</p>
970
+ <p>We correspond in English.</p>
971
+ <p>This document is version 1.0.0 of the Terms of Service for
972
+ <a href="https://ever.co">ever.co</a>, in force from 2026-08-02. Earlier versions, with the
973
+ dates they applied, are at <a href="https://ever.co/tos">https://ever.co/tos</a>.</p>