@ever-co/legal 0.5.0 → 0.6.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 (103) hide show
  1. package/dist/content/aup/ever-async/en.json +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +2 -2
  3. package/dist/content/aup/ever-demand/en.json +2 -2
  4. package/dist/content/aup/ever-rec/en.json +2 -2
  5. package/dist/content/aup/ever-teams/en.json +2 -2
  6. package/dist/content/aup/ever-works/en.json +2 -2
  7. package/dist/content/aup/everiq/en.json +2 -2
  8. package/dist/content/aup/gauzy/en.json +2 -2
  9. package/dist/content/aup/githands/en.json +2 -2
  10. package/dist/content/aup/hust/en.json +2 -2
  11. package/dist/content/aup/traduora/en.json +2 -2
  12. package/dist/content/cookies/ever-async/en.json +2 -2
  13. package/dist/content/cookies/ever-corporate/en.json +2 -2
  14. package/dist/content/cookies/ever-demand/en.json +2 -2
  15. package/dist/content/cookies/ever-rec/en.json +2 -2
  16. package/dist/content/cookies/ever-teams/en.json +2 -2
  17. package/dist/content/cookies/ever-tech/en.html +11 -3
  18. package/dist/content/cookies/ever-tech/en.json +4 -4
  19. package/dist/content/cookies/ever-works/en.json +2 -2
  20. package/dist/content/cookies/everiq/en.json +2 -2
  21. package/dist/content/cookies/gauzy/en.json +2 -2
  22. package/dist/content/cookies/githands/en.json +2 -2
  23. package/dist/content/cookies/hust/en.json +2 -2
  24. package/dist/content/cookies/traduora/en.json +2 -2
  25. package/dist/content/dpa/ever-async/en.json +2 -2
  26. package/dist/content/dpa/ever-demand/en.json +2 -2
  27. package/dist/content/dpa/ever-rec/en.json +2 -2
  28. package/dist/content/dpa/ever-teams/en.json +2 -2
  29. package/dist/content/dpa/ever-tech-services/en.html +1847 -0
  30. package/dist/content/dpa/ever-tech-services/en.json +624 -0
  31. package/dist/content/dpa/ever-works/en.json +2 -2
  32. package/dist/content/dpa/gauzy/en.html +5 -10
  33. package/dist/content/dpa/gauzy/en.json +3 -3
  34. package/dist/content/dpa/githands/en.json +2 -2
  35. package/dist/content/dpa/hust/en.json +2 -2
  36. package/dist/content/dpia/gauzy/en.json +2 -2
  37. package/dist/content/privacy/ever-async/en.json +2 -2
  38. package/dist/content/privacy/ever-corporate/en.json +2 -2
  39. package/dist/content/privacy/ever-demand/en.json +2 -2
  40. package/dist/content/privacy/ever-rec/en.json +2 -2
  41. package/dist/content/privacy/ever-teams/en.json +2 -2
  42. package/dist/content/privacy/ever-tech/en.html +55 -12
  43. package/dist/content/privacy/ever-tech/en.json +12 -4
  44. package/dist/content/privacy/ever-works/en.json +2 -2
  45. package/dist/content/privacy/everiq/en.json +2 -2
  46. package/dist/content/privacy/gauzy/en.json +2 -2
  47. package/dist/content/privacy/githands/en.json +2 -2
  48. package/dist/content/privacy/hust/en.json +2 -2
  49. package/dist/content/privacy/traduora/en.json +2 -2
  50. package/dist/content/refund/ever-corporate/en.json +2 -2
  51. package/dist/content/refund/ever-demand/en.json +2 -2
  52. package/dist/content/refund/ever-rec/en.json +2 -2
  53. package/dist/content/refund/ever-teams/en.json +2 -2
  54. package/dist/content/refund/ever-tech-services/en.html +270 -0
  55. package/dist/content/refund/ever-tech-services/en.json +178 -0
  56. package/dist/content/refund/ever-works/en.json +2 -2
  57. package/dist/content/refund/gauzy/en.json +2 -2
  58. package/dist/content/refund/githands/en.json +2 -2
  59. package/dist/content/refund/hust/en.json +2 -2
  60. package/dist/content/refund/traduora/en.json +2 -2
  61. package/dist/content/security/ever-async/en.json +2 -2
  62. package/dist/content/security/ever-corporate/en.json +2 -2
  63. package/dist/content/security/ever-demand/en.json +2 -2
  64. package/dist/content/security/ever-rec/en.json +2 -2
  65. package/dist/content/security/ever-teams/en.json +2 -2
  66. package/dist/content/security/ever-tech/en.json +2 -2
  67. package/dist/content/security/ever-works/en.json +2 -2
  68. package/dist/content/security/gauzy/en.json +2 -2
  69. package/dist/content/security/githands/en.json +2 -2
  70. package/dist/content/security/hust/en.json +2 -2
  71. package/dist/content/security/traduora/en.json +2 -2
  72. package/dist/content/subprocessors/ever-async/en.json +2 -2
  73. package/dist/content/subprocessors/ever-corporate/en.json +2 -2
  74. package/dist/content/subprocessors/ever-demand/en.json +2 -2
  75. package/dist/content/subprocessors/ever-rec/en.json +2 -2
  76. package/dist/content/subprocessors/ever-teams/en.json +2 -2
  77. package/dist/content/subprocessors/ever-tech/en.html +16 -2
  78. package/dist/content/subprocessors/ever-tech/en.json +4 -4
  79. package/dist/content/subprocessors/ever-tech-services/en.html +357 -0
  80. package/dist/content/subprocessors/ever-tech-services/en.json +158 -0
  81. package/dist/content/subprocessors/ever-works/en.json +2 -2
  82. package/dist/content/subprocessors/everiq/en.json +2 -2
  83. package/dist/content/subprocessors/gauzy/en.json +2 -2
  84. package/dist/content/subprocessors/githands/en.json +2 -2
  85. package/dist/content/subprocessors/hust/en.json +2 -2
  86. package/dist/content/subprocessors/traduora/en.json +2 -2
  87. package/dist/content/tos/ever-async/en.json +2 -2
  88. package/dist/content/tos/ever-corporate/en.json +2 -2
  89. package/dist/content/tos/ever-demand/en.json +2 -2
  90. package/dist/content/tos/ever-rec/en.json +2 -2
  91. package/dist/content/tos/ever-teams/en.json +2 -2
  92. package/dist/content/tos/ever-tech/en.html +46 -11
  93. package/dist/content/tos/ever-tech/en.json +12 -4
  94. package/dist/content/tos/ever-tech-services/en.html +937 -0
  95. package/dist/content/tos/ever-tech-services/en.json +473 -0
  96. package/dist/content/tos/ever-works/en.json +2 -2
  97. package/dist/content/tos/everiq/en.json +2 -2
  98. package/dist/content/tos/gauzy/en.json +2 -2
  99. package/dist/content/tos/githands/en.json +2 -2
  100. package/dist/content/tos/hust/en.json +2 -2
  101. package/dist/content/tos/traduora/en.json +2 -2
  102. package/dist/index.json +1788 -343
  103. package/package.json +52 -52
@@ -0,0 +1,937 @@
1
+ <h1 id="terms-of-service" tabindex="-1">Terms of Service</h1>
2
+ <p><strong>Ever Tech Engineering Services</strong> — <a href="https://ever.tech">ever.tech</a></p>
3
+ <p>Version 1.0.0 · In force from 2026-10-25</p>
4
+ <p>These Terms of Service (&quot;<strong>Terms</strong>&quot;) govern your access to and use of Ever Tech's engineering services and the
5
+ websites, applications and application programming interfaces we make available at <a href="https://ever.tech">ever.tech</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.tech/privacy">Privacy Policy</a>, our
15
+ <a href="https://ever.tech/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.tech">ever.tech</a> and Ever Tech's engineering services. 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.tech/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="customer-data" tabindex="-1">Customer Data</h2>
197
+ <h3 id="it-is-yours" tabindex="-1">It is yours</h3>
198
+ <p><strong>You own your Customer Data.</strong> Nothing in these Terms transfers ownership of it to us, and we claim no
199
+ rights in it beyond the limited operational licence described below. Putting data into the Service does not
200
+ change who owns it, and taking a Subscription does not make us a joint owner of anything you create with it.</p>
201
+ <h3 id="the-licence-you-give-us-and-its-limits" tabindex="-1">The licence you give us, and its limits</h3>
202
+ <p>You grant us a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, display and
203
+ process your Customer Data <strong>solely to the extent necessary to provide, secure, maintain and support the
204
+ Service for you</strong>, and to comply with our legal obligations.</p>
205
+ <p>That licence extends to the sub-processors we engage to help us deliver the Service, acting on our behalf
206
+ and under contract. It goes no further than the sentence above. The licence ends when the Customer Data is
207
+ deleted, except for copies held in routine backups for the period described in our
208
+ <a href="https://ever.tech/privacy">Privacy Policy</a>, and except where the law requires us to keep something for
209
+ longer.</p>
210
+ <p><strong>We do not use your Customer Data to train machine-learning models for our own purposes or for the benefit
211
+ of other customers, unless you have expressly opted in.</strong> The AI features section says more about how this
212
+ works where a model is involved.</p>
213
+ <h3 id="aggregated-and-de-identified-statistics" tabindex="-1">Aggregated and de-identified statistics</h3>
214
+ <p>We generate statistics about how the Service is used — volumes, performance, feature adoption, error rates
215
+ — and we use them to run, secure, support and improve it, and to report on our business.</p>
216
+ <p><strong>Those statistics are always aggregated and de-identified.</strong> They do not identify you, your End Users or
217
+ any other individual, we do not publish or share them in a form from which you could be identified, and they
218
+ never contain your Customer Data itself.</p>
219
+ <h3 id="what-you-promise-us-about-the-data-you-provide" tabindex="-1">What you promise us about the data you provide</h3>
220
+ <p>You warrant, each time Customer Data is submitted under your Subscription, that:</p>
221
+ <ul>
222
+ <li>you have all rights, licences, permissions and lawful bases needed to provide it to us and to have us
223
+ process it as these Terms describe;</li>
224
+ <li>doing so does not breach any law, any third party's rights, or any obligation of confidence you owe;</li>
225
+ <li>where the data is personal data, you have given the notices and satisfied the lawful-basis requirements
226
+ your own law imposes, before the data reached us; and</li>
227
+ <li>the data does not breach our Acceptable Use Policy.</li>
228
+ </ul>
229
+ <p>You will indemnify us against claims arising from a breach of those promises, as set out in the
230
+ indemnification section.</p>
231
+ <h3 id="we-can-remove-content" tabindex="-1">We can remove content</h3>
232
+ <p><strong>We may remove, disable access to, or refuse to transmit Customer Data that breaches the Acceptable Use
233
+ Policy or the law, infringes someone's rights, or that we are legally required to remove.</strong></p>
234
+ <ul>
235
+ <li>Where it is practicable and lawful to do so, we will tell you first. Where it is not — because the matter
236
+ is urgent, because a court or authority has ordered it, or because notice would prejudice an investigation
237
+ — we will tell you as soon as we reasonably can afterwards.</li>
238
+ <li>We do not monitor Customer Data, and we are under no general obligation to look for unlawful content. That
239
+ we did not act on something does not mean we approved of it.</li>
240
+ <li>Removing content is an operational step to protect the Service and other people. It is not a judgement on
241
+ the merits of whatever complaint prompted it, and it does not make us responsible for content we left in
242
+ place.</li>
243
+ </ul>
244
+ <p>Where the Service publishes content to third parties, the notice-and-action procedure in these Terms sets
245
+ out how illegal content and infringement are reported and handled.</p>
246
+ <h3 id="keeping-your-own-copy" tabindex="-1">Keeping your own copy</h3>
247
+ <p>Export what matters to you, regularly. <strong>We are not your archive</strong>, and the warranties section is explicit
248
+ that you should not treat our backups as a substitute for your own records.</p>
249
+ <h3 id="personal-data" tabindex="-1">Personal data</h3>
250
+ <p>Where Customer Data includes personal data, the privacy and data protection section below and the DPA govern
251
+ who is responsible for what.</p>
252
+ <h2 id="privacy-and-data-protection" tabindex="-1">Privacy and data protection</h2>
253
+ <p>Three documents sit alongside these Terms and you should read them:</p>
254
+ <ul>
255
+ <li>our <a href="https://ever.tech/privacy">Privacy Policy</a> — what we do with personal data in our own right, and the
256
+ rights you have over it;</li>
257
+ <li>our <a href="https://ever.tech/cookies">Cookie Policy</a> — cookies and similar technologies on our websites and in the
258
+ Service; and</li>
259
+ <li>our <strong>Data Processing Addendum</strong> — how we handle personal data that you put into the Service about other
260
+ people. It forms part of these Terms and applies automatically. You do not need to sign it separately, and
261
+ you can obtain the current version from legal@ever.co.</li>
262
+ </ul>
263
+ <h3 id="who-is-responsible-for-what" tabindex="-1">Who is responsible for what</h3>
264
+ <p>Two different relationships run in parallel, and it matters which one you are looking at.</p>
265
+ <p><strong>We are the controller</strong> for the personal data we handle in our own relationship with you: your account and
266
+ administrator details, billing and tax records, support correspondence, security and audit logs, and people
267
+ who visit our websites or contact us. We decide why and how that data is processed, and our Privacy Policy
268
+ explains it.</p>
269
+ <p><strong>You are the controller and we are your processor</strong> for the personal data that you and your End Users put
270
+ into the Service about other people — your records and content, and, where the Service offers such features,
271
+ any data it captures about how your own personnel work. <strong>You decide why that data is processed and how; we
272
+ process it on your documented instructions and for no purpose of our own.</strong> The DPA sets out the detail:
273
+ instructions, confidentiality, security measures, sub-processors and how we notify you of changes, breach
274
+ notification, assistance with requests from individuals, assistance with impact assessments, audits,
275
+ international transfers, and deletion or return at the end.</p>
276
+ <p>We do not decide whether your processing is lawful, and we are not in a position to. <strong>That assessment, and
277
+ the notices, lawful bases and consultations that go with it, are yours</strong> — see the section on what you are
278
+ responsible for.</p>
279
+ <h3 id="contacting-us-about-data-protection" tabindex="-1">Contacting us about data protection</h3>
280
+ <p>Write to privacy@ever.co with any data protection question, or to exercise a right you have over
281
+ personal data we hold as controller. Our Privacy Policy explains how to make a request, how long we take,
282
+ and your right to complain to a supervisory authority. Ours is the
283
+ Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
284
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may also complain to
285
+ the supervisory authority where you live or work.</p>
286
+ <p>If you are one of our customer's End Users and your question is about data held in their Workspace, that
287
+ request goes to them: they are the controller for it, not us.</p>
288
+ <h2 id="annex-ever-tech-engineering-services" tabindex="-1">Annex: Ever Tech Engineering Services</h2>
289
+ <p>This annex is specific to Ever Tech's engineering services. It sits on top of the sections above and, <strong>where it is
290
+ more specific, it governs.</strong> In these Terms, &quot;the Service&quot; means the engineering services we perform for you
291
+ under an order form.</p>
292
+ <p><strong>How the general sections read for services.</strong> The general sections of these Terms were written for our
293
+ hosted products. For Ever Tech's engineering services, read <strong>&quot;Subscription&quot;</strong> and <strong>&quot;Order&quot;</strong> as <em>a signed order form
294
+ (statement of work)</em>, <strong>&quot;Fees&quot;</strong> as <em>the fees in that order form</em>, <strong>&quot;Account&quot;</strong> and <strong>&quot;Workspace&quot;</strong> as <em>your
295
+ access to an engagement on the platform described below</em>, and <strong>&quot;End User&quot;</strong> as <em>a person you authorise to work
296
+ with us on an engagement</em>. Statements about free, trial, beta or preview offerings do not apply: nothing under
297
+ these Terms is free.</p>
298
+ <h3 id="what-these-terms-cover-and-what-they-do-not" tabindex="-1">What these Terms cover — and what they do not</h3>
299
+ <p>These Terms cover the work <strong>Ever Technologies LTD contracts and bills itself</strong>:</p>
300
+ <ol>
301
+ <li><strong>Human engineering</strong> by our engineers, under an order form or statement of work you sign with us.</li>
302
+ <li><strong>Direct engagements of AI agents and teams</strong> that we bill you for ourselves, run on the operations platform
303
+ described below.</li>
304
+ <li><strong>Agent hours for an existing Upwork client</strong>, billed as milestones under your existing Upwork contract and
305
+ run as a direct engagement. Upwork's own terms govern that contract; these Terms govern our work under it to
306
+ the extent Upwork's terms allow.</li>
307
+ </ol>
308
+ <p>They do <strong>not</strong> cover:</p>
309
+ <ul>
310
+ <li><strong>Hours, trials or team time you buy on the Cloc Now marketplace</strong>, a marketplace operated by a separate
311
+ company. Those purchases are governed by the marketplace's terms and by the operations terms you accept on
312
+ the platform before anything runs; we perform the work as the agency named on the profile.</li>
313
+ <li><strong>Human work you contract with us on Upwork</strong>, which Upwork's terms govern. We offer our Data Processing
314
+ Addendum for client data we touch.</li>
315
+ <li><strong>The trial requested through the form on ever.tech</strong>, which is governed by the trial terms on that site.</li>
316
+ </ul>
317
+ <p><strong>Business clients only.</strong> We contract with businesses, never with consumers. The order form names the
318
+ business, its address and — in the European Union — its VAT number, and the person signing confirms that they
319
+ may bind it.</p>
320
+ <h3 id="definitions-used-in-this-annex" tabindex="-1">Definitions used in this annex</h3>
321
+ <ul>
322
+ <li><strong>Agent</strong> — a pre-built AI agent we offer under a name and a tier, for example &quot;Virtual Senior Engineer&quot;.</li>
323
+ <li><strong>Operated Agent</strong> — an Agent supervised by a named <strong>Operator</strong>, one of our engineers certified for it.</li>
324
+ <li><strong>Automated Agent</strong> — an Agent we run without an Operator, labelled &quot;Automated&quot; wherever it is offered.</li>
325
+ <li><strong>Instance</strong> — one running copy of an Agent dedicated to you, on a machine used for no other client.</li>
326
+ <li><strong>Team</strong> — a named group of Agents and engineers sold as one unit.</li>
327
+ <li><strong>Working Hour</strong> — time during which an Instance (or, for a Team, at least one member) executes a task for
328
+ you, as measured by the platform.</li>
329
+ <li><strong>Output</strong> — everything an Instance, a Team or an engineer delivers to you: code, commits, pull requests,
330
+ documents, messages, tickets and reports.</li>
331
+ <li><strong>Agent Materials</strong> — everything used to run an Agent: its repository, configuration, prompts, skills,
332
+ runbooks, tools, evaluation suites and know-how.</li>
333
+ <li><strong>The platform</strong> — Cloc M, an operations platform for operated agents <strong>operated by a separate company that
334
+ is not part of our group</strong>, on which our Agents run.</li>
335
+ </ul>
336
+ <h3 id="the-platform-our-agents-run-on" tabindex="-1">The platform our Agents run on</h3>
337
+ <p>Our Agents run on the platform, which provisions them on dedicated machines, connects them to the tools you
338
+ choose, enforces the approvals and gate mode you set, measures Working Hours and keeps the work diary.</p>
339
+ <ul>
340
+ <li><strong>We use the platform as our sub-processor</strong> for your content, under a written agreement with its operator
341
+ that mirrors our Data Processing Addendum. It is on our sub-processor list.</li>
342
+ <li><strong>The first time you sign in to the platform you accept its short operations terms</strong> for direct engagements:
343
+ its acceptable-use and agent tasking rules, its AI disclosure, no-training and retention policies, the gate
344
+ modes and their waivers, and its security terms. <strong>You owe the platform's operator nothing under them</strong>, and
345
+ it is not a party to your contract with us for the work.</li>
346
+ <li><strong>There is no money inside the platform for a direct engagement.</strong> We invoice you under these Terms.</li>
347
+ </ul>
348
+ <h3 id="the-operator-guarantee-operated-agents" tabindex="-1">The operator guarantee (Operated Agents)</h3>
349
+ <p>Every Instance of an Operated Agent has a named Operator. <strong>Nothing your Instance produces is sent to a person
350
+ outside our team, posted in your tools as a deliverable, or merged into your repositories without either an
351
+ Operator's review or an approval policy you and we have agreed in writing on the platform.</strong> Instant
352
+ acknowledgements (&quot;On it, I'll report back here&quot;) are sent without review and say that they come from an AI
353
+ agent. Every approval and refusal is recorded in your audit trail.</p>
354
+ <h3 id="automated-agents" tabindex="-1">Automated Agents</h3>
355
+ <p>An Automated Agent has no Operator and acts without human review of each step. <strong>We are responsible for it as
356
+ for our own staff.</strong> What happens to its irreversible actions depends on the gate mode you choose.</p>
357
+ <h3 id="gate-modes-and-waivers" tabindex="-1">Gate modes and waivers</h3>
358
+ <p>For each engagement you choose a gate mode on the platform, and you may change it later:</p>
359
+ <ol>
360
+ <li><strong>Buyer approves</strong> (the default) — every irreversible action of an Automated Agent waits for <strong>your</strong>
361
+ approval.</li>
362
+ <li><strong>Provider decides</strong> — we mark the kinds of action we trust our Agents to take without your approval; the
363
+ rest wait for you.</li>
364
+ <li><strong>No gate</strong> — Automated Agents act fully autonomously, except that production deploys and merges still follow
365
+ the next section.</li>
366
+ </ol>
367
+ <p><strong>If you choose Provider decides, you waive all claims for damages against us arising from the actions we
368
+ marked as trusted and that ran without your approval in that mode. If you choose No gate, you accept that the
369
+ Agent and we bear no responsibility for any action taken without approval in that mode, and you waive all
370
+ claims against us arising from those actions.</strong> You accept each waiver separately, in its own box, for that
371
+ engagement; the platform records the version, the person and the time, and its own terms carry the matching
372
+ waiver towards the platform's operator. <strong>Neither waiver covers intent or gross negligence, or any liability
373
+ that cannot be excluded or limited by law.</strong> Operated Agents keep the operator guarantee in every mode.</p>
374
+ <h3 id="what-agents-do-not-do" tabindex="-1">What Agents do not do</h3>
375
+ <p>Unless the order form says otherwise:</p>
376
+ <ul>
377
+ <li><strong>Deploys:</strong> an Agent deploys to an environment of yours only after you have enabled &quot;agent may deploy to
378
+ <em>environment</em>&quot; for the engagement <strong>and approved that deploy</strong> on the platform (an Operator reviews it first
379
+ for an Operated Agent) — or, only for an Automated Agent in the No gate mode, under a separate standing deploy
380
+ consent you gave for that environment. Deploy permissions are <strong>off by default</strong>; credentials are scoped and
381
+ short-lived; every deploy is recorded.</li>
382
+ <li><strong>Merges:</strong> an Agent merges a pull request into your repositories only with your approval, in every mode.</li>
383
+ <li>Agents receive no standing credentials to production systems, payment instruments or personal accounts, spend
384
+ none of your money without a recorded approval, and contact no one outside the channels you connected.</li>
385
+ </ul>
386
+ <h3 id="your-responsibilities" tabindex="-1">Your responsibilities</h3>
387
+ <p>You give access only to what the work needs; name a decision-maker who answers questions and approves deploys
388
+ and merges; review and merge pull requests in your own repositories; keep secrets out of tickets and chat; and
389
+ remain responsible for decisions you take on the basis of Output.</p>
390
+ <h3 id="hours-and-start-dates" tabindex="-1">Hours and start dates</h3>
391
+ <ul>
392
+ <li><strong>Only Working Hours count.</strong> Waiting, pauses, provisioning, upgrades and recovery from an incident we caused
393
+ are not counted. Hours are rounded to the nearest 6 minutes per
394
+ Instance per day. A Team is counted per member or as a team, as the order form says.</li>
395
+ <li><strong>Human hours</strong> are recorded on the platform or in our time tracker. You may dispute an entry within
396
+ 7 days; after that it is final.</li>
397
+ <li><strong>Routine Operator review is included</strong> in an Agent's hourly rate; additional human work is billed only after
398
+ you agree to it.</li>
399
+ <li>An Operated Agent or a Team starts at the <strong>next free slot of its Operator</strong>, given in the order form; an
400
+ Automated Agent starts when you activate it.</li>
401
+ </ul>
402
+ <h3 id="service-levels" tabindex="-1">Service levels</h3>
403
+ <p>Unless the order form sets stricter ones, the platform's published service levels by agent tier apply. <strong>No
404
+ service credits apply.</strong> The correction remedy below remains.</p>
405
+ <h3 id="fees-invoices-and-payment" tabindex="-1">Fees, invoices and payment</h3>
406
+ <ul>
407
+ <li><strong>Fees and rates are in the order form</strong>, per engineer, per Agent tier or per Team. Upwork engagements are
408
+ priced and paid on Upwork.</li>
409
+ <li><strong>We invoice in advance (prepayment) or in arrears, as the order form says. Invoices are payable within
410
+ 7 days</strong> unless the order form says otherwise.</li>
411
+ <li><strong>VAT.</strong> A Bulgarian business client pays Bulgarian VAT at the standard rate. An EU business client with a
412
+ valid VAT number, checked in VIES, is invoiced without Bulgarian VAT under the <strong>reverse charge</strong>. A client
413
+ outside the EU is invoiced outside the scope of Bulgarian VAT. Each invoice carries the wording and legal basis
414
+ the law requires.</li>
415
+ <li><strong>Invoices and credit notes are issued from our accounting system</strong> under Bulgarian invoicing rules, with the
416
+ payment reference on them.</li>
417
+ <li>Refunds follow the Refund Policy for Ever Tech's engineering services.</li>
418
+ </ul>
419
+ <h3 id="intellectual-property" tabindex="-1">Intellectual property</h3>
420
+ <ul>
421
+ <li><strong>Your Output is yours.</strong> On payment of the hours in which it was produced, <strong>we assign to you all rights we
422
+ hold in the Output.</strong> Our engineers and Operators assign their rights in their work to us so that we can.
423
+ Output is committed to your repositories and tools from the start.</li>
424
+ <li><strong>Agent Materials stay ours.</strong> Our Agents' repositories, prompts, skills, evaluations and know-how are owned by
425
+ Ever Co. LTD and used by us under licence, even when an improvement was prompted by your work. We never
426
+ put your confidential information or your code into Agent Materials.</li>
427
+ <li><strong>Pre-existing material.</strong> Output may include our general know-how, small reusable snippets and open-source
428
+ components under their own licences. We grant you a perpetual, worldwide, royalty-free licence to any of our
429
+ pre-existing material that ends up in Output, so that you can use it as part of the Output. <strong>A new dependency
430
+ is added only after an approval that shows its licence.</strong></li>
431
+ <li><strong>What we cannot promise.</strong> Some AI-generated material may not be protected by copyright in some countries. We
432
+ assign the rights that exist and do not warrant that every part of the Output is protectable.</li>
433
+ <li><strong>Your content</strong> stays yours; we use it only to perform the Service, and <strong>neither we, the platform nor any
434
+ model provider uses it to train AI models.</strong></li>
435
+ </ul>
436
+ <h3 id="warranties-and-the-correction-remedy" tabindex="-1">Warranties and the correction remedy</h3>
437
+ <p>We perform the Service with reasonable skill and care, through certified Operators and qualified engineers.
438
+ <strong>AI Output can be wrong</strong>, and we do not warrant that Output is free of errors or fit for a purpose you have not
439
+ told us about. <strong>If approved Output does not meet the acceptance criteria of its task, tell us within
440
+ 14 days and we will correct it without charging the hours spent on the
441
+ correction.</strong> That is your main remedy for defective Output; worked hours are not refunded.</p>
442
+ <h3 id="term-ending-an-engagement-and-offboarding" tabindex="-1">Term, ending an engagement and offboarding</h3>
443
+ <ul>
444
+ <li>An order form runs for the term it states, or until either of us ends it on the notice it states. Either of us
445
+ may end it at once for a material breach that is not remedied within 14 days of written notice.</li>
446
+ <li><strong>Offboarding:</strong> at the end of an agent engagement your workspace and client memory are exported, encrypted,
447
+ and the export is verified <strong>before</strong> the machine is destroyed. The export is kept for the retention period you
448
+ chose (7–180 days, default
449
+ 30), then deleted, and the deletion is confirmed to you.</li>
450
+ <li>Fees for hours already worked remain payable. Unused prepaid hours are dealt with under the Refund Policy.</li>
451
+ </ul>
452
+ <h3 id="changes-to-the-platform-and-the-agents" tabindex="-1">Changes to the platform and the Agents</h3>
453
+ <p>We may change the models, model providers and runtimes behind an Agent. We will not reduce an Agent's tier, the
454
+ operator guarantee, data residency or the no-training terms without 30 days' notice, and a new model provider
455
+ follows the sub-processor notice and objection procedure.</p>
456
+ <h3 id="non-solicitation" tabindex="-1">Non-solicitation</h3>
457
+ <p>For 12 months after an engagement ends, <strong>neither of us will solicit for
458
+ employment or engagement the other's people who worked on it.</strong> General job advertisements are not
459
+ solicitation.</p>
460
+ <h3 id="the-order-form-statement-of-work" tabindex="-1">The order form (statement of work)</h3>
461
+ <p>Every engagement under these Terms has an order form, signed by both of us, that states:</p>
462
+ <ul>
463
+ <li><strong>the client</strong> — legal name, address, VAT number, signatory and their authority;</li>
464
+ <li><strong>the contracting entity</strong> — Ever Technologies LTD;</li>
465
+ <li><strong>the channel</strong> — direct, or Upwork (with the Upwork contract reference);</li>
466
+ <li><strong>the team</strong> — named engineers with their rates; Agents with tier, rate, operated or automated, and number of
467
+ Instances; Teams with their billing mode; the lead Operator;</li>
468
+ <li><strong>payment</strong> — prepayment or invoicing, and the payment terms;</li>
469
+ <li><strong>the hour cap per week</strong>;</li>
470
+ <li><strong>the gate mode and the deploy environments enabled</strong>;</li>
471
+ <li><strong>the retention period</strong> (7–180 days);</li>
472
+ <li><strong>the region</strong> — the European Union (Germany or Finland by default) unless stated otherwise;</li>
473
+ <li><strong>model-provider exclusions</strong>, and any <strong>special-category data agreement</strong>;</li>
474
+ <li><strong>the start date</strong> (the next free Operator slot for Operated Agents and Teams);</li>
475
+ <li><strong>the documents incorporated</strong>, with their versions — these Terms, the Data Processing Addendum, the Refund
476
+ Policy, and the platform's operations terms for direct engagements; and</li>
477
+ <li><strong>signatures</strong>.</li>
478
+ </ul>
479
+ <h3 id="order-of-precedence" tabindex="-1">Order of precedence</h3>
480
+ <p>If documents conflict: (1) the signed order form; (2) this annex; (3) the Data Processing Addendum; (4) the rest
481
+ of these Terms. For Upwork engagements, Upwork's terms prevail on the matters they govern.</p>
482
+ <h2 id="confidentiality" tabindex="-1">Confidentiality</h2>
483
+ <p><strong>This section works both ways.</strong> It binds us exactly as it binds you.</p>
484
+ <h3 id="what-counts-as-confidential" tabindex="-1">What counts as confidential</h3>
485
+ <p>&quot;<strong>Confidential Information</strong>&quot; means information that one of us (the &quot;<strong>disclosing party</strong>&quot;) makes
486
+ available to the other (the &quot;<strong>receiving party</strong>&quot;) in connection with the Service, in any form, which is
487
+ either marked or described as confidential, or which a reasonable person would understand to be
488
+ confidential from its nature or from the circumstances in which it was disclosed.</p>
489
+ <ul>
490
+ <li><strong>Ours</strong> includes the non-public parts of the Service, our source code, security information,
491
+ architecture and infrastructure detail, unreleased features, non-public pricing, and our product plans.</li>
492
+ <li><strong>Yours</strong> includes the content and data you put into the Service, and your non-public business,
493
+ technical, financial and commercial information.</li>
494
+ </ul>
495
+ <p>The terms of any order between us are confidential to both of us.</p>
496
+ <p>Where Confidential Information is also personal data, how it is processed is governed by our Privacy
497
+ Policy and, where it applies to you, our Data Processing Addendum. Where those and this section both bite,
498
+ <strong>the stricter obligation applies</strong>.</p>
499
+ <h3 id="what-does-not-count" tabindex="-1">What does not count</h3>
500
+ <p>This section does not apply to information that:</p>
501
+ <ul>
502
+ <li>was public when it was disclosed, or later becomes public other than through a breach of this section;</li>
503
+ <li>the receiving party already had, free of any duty of confidence, before it was disclosed;</li>
504
+ <li>the receiving party develops independently, without using or referring to the disclosing party's
505
+ Confidential Information; or</li>
506
+ <li>a third party lawfully provides to the receiving party without a duty of confidence.</li>
507
+ </ul>
508
+ <p>The party relying on one of these has to be able to show that it applies.</p>
509
+ <h3 id="how-each-of-us-must-treat-it" tabindex="-1">How each of us must treat it</h3>
510
+ <p>Each of us will use the other's Confidential Information only to provide or receive the Service and to
511
+ perform these Terms, and will not disclose it except as this section permits.</p>
512
+ <p>Each of us will protect it with at least the care we use for our own confidential information of similar
513
+ importance — and never with less than reasonable care.</p>
514
+ <h3 id="who-it-may-be-shared-with" tabindex="-1">Who it may be shared with</h3>
515
+ <p>Each of us may disclose the other's Confidential Information to our employees, officers, contractors,
516
+ group companies and professional advisers who genuinely need it for that purpose and who are bound by
517
+ confidentiality duties at least as protective as these. We may also disclose it to our sub-processors so
518
+ far as needed to provide the Service, on the same footing.</p>
519
+ <p><strong>Each of us stays responsible for what those people do with it</strong>, as if we had done it ourselves.</p>
520
+ <h3 id="when-the-law-requires-disclosure" tabindex="-1">When the law requires disclosure</h3>
521
+ <p>If a law, a court, a regulator or a stock exchange requires disclosure, the receiving party may disclose —
522
+ but only what is actually required, and, where it is lawful and practical to do so, only after giving the
523
+ disclosing party advance notice and a reasonable opportunity to object or to seek protective treatment.
524
+ The receiving party will give reasonable cooperation with any such attempt, at the disclosing party's
525
+ cost.</p>
526
+ <h3 id="how-long-it-lasts" tabindex="-1">How long it lasts</h3>
527
+ <p>These obligations begin when the information is disclosed and continue for <strong>three (3) years</strong> after these
528
+ Terms come to an end.</p>
529
+ <p><strong>Anything that qualifies as a trade secret stays protected for as long as it remains a trade secret under
530
+ the applicable law</strong>, whether or not the three years have run.</p>
531
+ <h3 id="returning-or-destroying-it" tabindex="-1">Returning or destroying it</h3>
532
+ <p>When these Terms end — or earlier, if the disclosing party asks in writing — the receiving party will
533
+ return or destroy the Confidential Information it holds, and confirm in writing that it has done so if
534
+ asked. There are two exceptions:</p>
535
+ <ul>
536
+ <li>copies held in routine backups or archives that are not readily accessible in the ordinary course of
537
+ business; and</li>
538
+ <li>copies a party must keep to meet a legal or regulatory obligation.</li>
539
+ </ul>
540
+ <p>Anything kept under either exception stays subject to this section for as long as it is kept. Your own
541
+ content inside the Service is dealt with by the termination section — export and then deletion — rather
542
+ than by this one.</p>
543
+ <h3 id="no-licence-and-what-happens-on-a-breach" tabindex="-1">No licence, and what happens on a breach</h3>
544
+ <p>Nothing in this section transfers ownership of, or grants any licence in, Confidential Information.</p>
545
+ <p>Damages may not be an adequate remedy for a breach of this section, so either of us may seek an injunction
546
+ or other equitable relief without having to prove financial loss and without providing security, in
547
+ addition to any other remedy available.</p>
548
+ <h2 id="feedback" tabindex="-1">Feedback</h2>
549
+ <p>If you send us ideas, suggestions, feature requests, bug reports or any other comment about the Service,
550
+ we may use them however we like — including building them into the Service and offering the result to
551
+ everyone else — with no obligation to you and no payment. <strong>You grant us a perpetual, irrevocable,
552
+ worldwide, royalty-free licence to use, copy, modify and exploit that feedback for any purpose</strong>, and you
553
+ confirm you are free to give it to us without breaching anyone else's rights. Please do send it: we would
554
+ rather hear it than not. But we cannot take feedback in confidence, so if an idea is one you want to keep,
555
+ keep it — this section does not touch any other confidentiality obligation between us.</p>
556
+ <h2 id="publicity-and-customer-references" tabindex="-1">Publicity and customer references</h2>
557
+ <p>We may say that you are a customer. That means we may use your name, trading name and logo — as they are
558
+ ordinarily presented — on our websites, in customer lists, in presentations and in sales and marketing
559
+ material, for the purpose of identifying you as a customer of the Service. Where you have published brand
560
+ guidelines, or given them to us, we will follow them.</p>
561
+ <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
562
+ reason, and we will take you out of the material we control within a reasonable period. We will not recall
563
+ material that has already been printed or distributed, but we will not produce any more of it.</p>
564
+ <p>Anything beyond that plain identification needs your prior written consent, which is yours to give or
565
+ withhold as you see fit. That includes a case study, a quotation attributed to you or to one of your
566
+ people, a press release, a joint announcement, a logo in paid advertising, and any statement about what
567
+ you use the Service for or what results you got from it.</p>
568
+ <p>You may say that you use the Service and refer to it by name for that purpose. Beyond what this section
569
+ allows, neither of us gets any right in the other's trade marks, logos or brand features, and each of us
570
+ keeps ownership of our own.</p>
571
+ <h2 id="warranties-and-disclaimer" tabindex="-1">Warranties and disclaimer</h2>
572
+ <p>We warrant only that we will provide the Service with reasonable skill and care, and that we will not
573
+ knowingly introduce malicious code into it.</p>
574
+ <p><strong>Beyond that limited warranty, and to the fullest extent permitted by law, the Service is provided &quot;as
575
+ is&quot; and &quot;as available&quot;, without warranty of any kind.</strong> We expressly disclaim all other warranties,
576
+ conditions, representations and terms, whether express, implied or statutory, including any implied
577
+ warranty of merchantability, satisfactory quality, fitness for a particular purpose, title or
578
+ non-infringement, and any warranty arising from a course of dealing or usage of trade.</p>
579
+ <p>In particular, and without limiting the above, <strong>we do not warrant that</strong>:</p>
580
+ <ul>
581
+ <li>the Service will be uninterrupted, timely, secure or error-free;</li>
582
+ <li>defects will be corrected, or corrected within any particular period;</li>
583
+ <li>the Service will meet your requirements or expectations, or produce any particular result;</li>
584
+ <li>data or output produced by the Service will be accurate, complete or reliable;</li>
585
+ <li>the Service will operate with any third-party product, service or integration you choose to use with it;
586
+ or</li>
587
+ <li>the Service will be available in, or lawful to use in, any particular jurisdiction.</li>
588
+ </ul>
589
+ <p><strong>No service level commitment applies</strong> unless we have separately agreed one with you in a written service
590
+ level agreement that expressly refers to these Terms. Uptime figures, roadmap statements, benchmarks and
591
+ support response times published on our websites or given in sales discussions are informational and do
592
+ not create any commitment.</p>
593
+ <p><strong>Free, trial, evaluation, beta, preview and early-access features carry no warranty at all.</strong> They are
594
+ provided for your evaluation, may be changed or withdrawn at any time without notice, may not be
595
+ supported, and may not perform as documented. Do not use them for anything you cannot afford to lose.</p>
596
+ <p><strong>You are responsible for your own backups.</strong> We maintain backups for our own operational continuity, and
597
+ you should not treat them as a substitute for retaining your own copies of your data.</p>
598
+ <p>Nothing in this section limits any warranty or right that cannot lawfully be excluded. <strong>If you are a
599
+ consumer, your statutory rights are unaffected</strong> by this section.</p>
600
+ <h2 id="indemnification" tabindex="-1">Indemnification</h2>
601
+ <p>This section runs both ways. We cover you if someone claims our software infringes their rights; you cover
602
+ us if the claim comes out of your data or your use of the Service.</p>
603
+ <h3 id="what-we-cover" tabindex="-1">What we cover</h3>
604
+ <p>We will defend you against a third-party claim that the Service, <strong>as we supply it</strong>, infringes that
605
+ party's patent, copyright, trade mark, database right or trade secret, and we will pay the damages finally
606
+ awarded against you on that claim, or the settlement amount we agree.</p>
607
+ <p>That is conditional on you:</p>
608
+ <ul>
609
+ <li>telling us in writing promptly once you know about the claim — late notice only reduces our obligation
610
+ to the extent the delay actually harmed our ability to defend;</li>
611
+ <li>letting us take sole control of the defence and of any settlement; and</li>
612
+ <li>giving us reasonable co-operation, information and authority to run the defence, at our expense.</li>
613
+ </ul>
614
+ <p>We will not settle on terms that admit fault on your part, impose a payment on you that we do not cover,
615
+ or require you to do something other than stop using the infringing part, unless you agree.</p>
616
+ <h3 id="what-we-do-not-cover" tabindex="-1">What we do not cover</h3>
617
+ <p>We owe you nothing under this section where the claim arises from:</p>
618
+ <ul>
619
+ <li>any change to the Service made by anyone other than us;</li>
620
+ <li>combining the Service with hardware, software, data, models or services we did not supply, where the
621
+ claim would not have arisen without the combination;</li>
622
+ <li>your Customer Data, or your instructions, designs or specifications;</li>
623
+ <li>use of the Service in breach of these Terms, the Acceptable Use Policy or the documentation;</li>
624
+ <li>your continued use of an allegedly infringing version after we have provided a non-infringing
625
+ replacement and asked you to switch;</li>
626
+ <li>a free, trial, evaluation, beta, preview or early-access offering, which carries no indemnity from us at
627
+ all; or</li>
628
+ <li>separately licensed open-source components, which come with their own licences and their own
629
+ disclaimers.</li>
630
+ </ul>
631
+ <h3 id="what-we-will-do-about-it" tabindex="-1">What we will do about it</h3>
632
+ <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>
633
+ <ul>
634
+ <li>obtain the right for you to keep using it;</li>
635
+ <li>modify or replace it so that it no longer infringes, without materially reducing what it does; or</li>
636
+ <li>if neither of those is available on commercially reasonable terms, terminate the affected part of the
637
+ Service and refund the unused portion of any fees you have prepaid for it.</li>
638
+ </ul>
639
+ <p><strong>Those remedies, together with the defence and payment above, are the whole of our liability, and your
640
+ only remedy, for any claim that the Service infringes someone's intellectual property.</strong></p>
641
+ <h3 id="what-you-cover" tabindex="-1">What you cover</h3>
642
+ <p>You will defend us, and pay the damages finally awarded or agreed in settlement, against any third-party
643
+ claim arising from:</p>
644
+ <ul>
645
+ <li>your Customer Data — including a claim that it infringes intellectual property, breaches privacy or
646
+ publicity rights, is unlawful, or was collected or used without a proper basis;</li>
647
+ <li>your use of the Service in breach of these Terms, the Acceptable Use Policy or applicable law; and</li>
648
+ <li>your breach of the representations and warranties you give us in our Data Processing Addendum,
649
+ including those about lawful basis, notices to the people whose data you process, impact assessments,
650
+ and consultation with employee representatives or works councils.</li>
651
+ </ul>
652
+ <p>The same conditions apply in reverse: we will notify you promptly, let you control the defence, and
653
+ co-operate at your expense. We will not settle without your agreement on the terms described above.</p>
654
+ <p>Your obligations under this section are not subject to the cap in the limitation of liability section.
655
+ Ours are, except where the law does not permit that.</p>
656
+ <h3 id="if-you-are-a-consumer" tabindex="-1">If you are a consumer</h3>
657
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
658
+ or profession, the indemnity you would otherwise give us in this section does not apply to you.</strong> Our
659
+ indemnity to you is unaffected, and so are your statutory rights.</p>
660
+ <h2 id="limitation-of-liability" tabindex="-1">Limitation of liability</h2>
661
+ <p><strong>Please read this section carefully. It limits what we can be held liable for.</strong></p>
662
+ <h3 id="damages-we-exclude-entirely" tabindex="-1">Damages we exclude entirely</h3>
663
+ <p>To the fullest extent permitted by law, we will not be liable for any indirect, consequential, incidental,
664
+ special, exemplary or punitive damages, and we will not be liable — whether the claim is framed as direct
665
+ or indirect — for:</p>
666
+ <ul>
667
+ <li>loss of profits, revenue, business, contracts, anticipated savings or opportunity;</li>
668
+ <li>loss of goodwill or reputational harm;</li>
669
+ <li>loss, corruption or inaccuracy of data, or the cost of recovering or reconstructing it;</li>
670
+ <li>business interruption, or the cost of substitute goods or services;</li>
671
+ <li>any liability you incur to your own customers, clients, personnel or other third parties.</li>
672
+ </ul>
673
+ <p>This applies however the liability arises — contract, tort (including negligence), breach of statutory
674
+ duty, restitution or otherwise — and whether or not we were advised that such loss was possible.</p>
675
+ <h3 id="cap-on-everything-else" tabindex="-1">Cap on everything else</h3>
676
+ <p>Our total aggregate liability arising out of or in connection with these Terms and the Service, for all
677
+ claims taken together, is limited to <strong>the total fees you actually paid us for the Service in the twelve
678
+ (12) months immediately before the event giving rise to the claim</strong>.</p>
679
+ <p><strong>Where you use the Service on a free, trial, evaluation, beta or preview basis, our total aggregate
680
+ liability is limited to one hundred euros (EUR 100).</strong> No fees paid means no fees to measure a cap
681
+ against, and we make free access available on that footing.</p>
682
+ <h3 id="what-this-section-does-not-limit" tabindex="-1">What this section does not limit</h3>
683
+ <p>Nothing in these Terms excludes or limits our liability for:</p>
684
+ <ul>
685
+ <li>death or personal injury caused by our negligence;</li>
686
+ <li>fraud or fraudulent misrepresentation;</li>
687
+ <li>gross negligence or wilful misconduct; or</li>
688
+ <li>any other liability that cannot lawfully be excluded or limited.</li>
689
+ </ul>
690
+ <h3 id="if-you-are-a-consumer-1" tabindex="-1">If you are a consumer</h3>
691
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business, craft
692
+ or profession, this section applies to you only so far as the law permits.</strong> Your mandatory statutory
693
+ rights, and any remedy the law gives you that cannot be excluded or limited by agreement, are unaffected.
694
+ Where a limitation in this section would be unfair or unenforceable against you as a consumer, it does not
695
+ apply to you, and the remainder of this section continues in force.</p>
696
+ <h3 id="allocation-of-risk" tabindex="-1">Allocation of risk</h3>
697
+ <p>You acknowledge that the fees for the Service reflect this allocation of risk, that these limits are a
698
+ fundamental basis of the bargain between us, and that they apply even if a limited remedy is found to have
699
+ failed of its essential purpose.</p>
700
+ <h2 id="compliance-export-controls-and-sanctions" tabindex="-1">Compliance, export controls and sanctions</h2>
701
+ <p>Each of us will comply with the laws that apply to it in performing under these Terms. You are
702
+ responsible for the lawfulness of what you do with the Service, including in any country where your users
703
+ are located.</p>
704
+ <h3 id="sanctions-and-restricted-parties" tabindex="-1">Sanctions and restricted parties</h3>
705
+ <p>You confirm, each time you use the Service, that:</p>
706
+ <ul>
707
+ <li>you are not named on, and are not owned or controlled by or acting for anyone named on, a sanctions or
708
+ restricted-party list maintained by the European Union, the United Nations, the United Kingdom or the
709
+ United States;</li>
710
+ <li>you are not established, located or ordinarily resident in a country or territory subject to
711
+ comprehensive sanctions or embargo; and</li>
712
+ <li>you will not give access to the Service to anyone who falls into either category.</li>
713
+ </ul>
714
+ <p>Tell us promptly if any of that stops being true.</p>
715
+ <h3 id="export-and-trade-controls" tabindex="-1">Export and trade controls</h3>
716
+ <p>You will not export, re-export, transfer or make the Service or its output available in breach of export
717
+ control, sanctions or trade law. You will not use the Service in connection with the development or
718
+ production of weapons, or for any other end use that those laws restrict.</p>
719
+ <p><strong>Where a sanctions or trade-control obligation requires it, we will suspend or terminate your access
720
+ immediately and without liability to you.</strong> We will tell you what has happened as far as the law allows
721
+ us to.</p>
722
+ <h3 id="bribery-and-corruption" tabindex="-1">Bribery and corruption</h3>
723
+ <p>Neither of us will offer, give, request or accept a bribe, kickback or other improper payment or
724
+ advantage in connection with these Terms, and each of us will comply with the anti-bribery and
725
+ anti-corruption laws that apply to it.</p>
726
+ <h2 id="changes-to-these-terms" tabindex="-1">Changes to these Terms</h2>
727
+ <p>We will change these Terms from time to time — because the Service changes, because the law changes, or
728
+ because something here turned out to be unclear. Every version carries a version number and an effective
729
+ date, printed at the top of the document. This one is version 1.0.0, in force from
730
+ 2026-10-25.</p>
731
+ <h3 id="changes-that-take-effect-immediately" tabindex="-1">Changes that take effect immediately</h3>
732
+ <p>Corrections, clarifications, formatting, new contact details, and terms covering a new feature you are
733
+ not using take effect when we publish them. So does any change we are required to make with immediate
734
+ effect by law, a court or a regulator.</p>
735
+ <h3 id="material-changes-thirty-days-notice" tabindex="-1">Material changes: thirty days' notice</h3>
736
+ <p><strong>For any change that materially affects your rights or obligations, we will give you at least thirty
737
+ (30) days' notice before the new version takes effect.</strong> That includes changes to fees and billing, to
738
+ the limitation of liability, to the indemnities, to governing law and venue, and to how we may suspend or
739
+ terminate your account.</p>
740
+ <p>We give that notice by email to the address on your account, by a notice inside the product, or both. If
741
+ you do not have an account with us, we give it by publishing the new version with its effective date
742
+ before it applies.</p>
743
+ <h3 id="your-choice" tabindex="-1">Your choice</h3>
744
+ <p><strong>If you keep using the Service on or after the effective date, you accept the new version.</strong> If you do
745
+ not want it, terminate before that date — from your account settings or by writing to legal@ever.co.
746
+ If you terminate because you object to a material change, <strong>we will refund the unused portion of any
747
+ period you have already paid for</strong>, calculated pro rata from the date your access ends.</p>
748
+ <p>Where a change is significant enough that continued use is not a fair way to establish agreement, we will
749
+ ask you to accept the new version explicitly the next time you sign in, and you will not be able to
750
+ continue until you do.</p>
751
+ <p>A change never applies retrospectively to a dispute that had already arisen before it took effect.</p>
752
+ <h3 id="every-version-stays-available" tabindex="-1">Every version stays available</h3>
753
+ <p>We keep an archive of every version we have published, with its effective date, linked from each
754
+ document. You can always see which text was in force on a given date, and read the version you actually
755
+ agreed to: <a href="https://ever.tech/tos">https://ever.tech/tos</a>.</p>
756
+ <p>When you accept these Terms we record which version you accepted, when, and a fingerprint of the exact
757
+ text — so that neither of us has to rely on memory about what was on the page that day.</p>
758
+ <h3 id="if-you-are-a-consumer-2" tabindex="-1">If you are a consumer</h3>
759
+ <p>If you are a consumer, nothing in this section obliges you to accept a change. You may reject it and stop
760
+ using the Service, with the refund described above, and your statutory rights are unaffected.</p>
761
+ <h2 id="force-majeure" tabindex="-1">Force majeure</h2>
762
+ <p>Neither of us is liable for failing to perform, or for being late in performing, where the cause is
763
+ outside our reasonable control.</p>
764
+ <p>That includes natural disaster, fire, flood, extreme weather, epidemic, war, terrorism, civil unrest,
765
+ industrial action other than by our own workforce, an act or order of a government or regulator, failure
766
+ of electricity, cooling or telecommunications supply, failure or degradation of the public internet or of
767
+ a transit, peering or DNS provider, a large-scale cyber attack including denial of service, and the
768
+ failure, interruption or withdrawal of a third-party provider we depend on.</p>
769
+ <p>The affected party must tell the other without undue delay, take reasonable steps to limit the effect,
770
+ and resume performance as soon as it reasonably can.</p>
771
+ <p><strong>Your obligation to pay is not excused.</strong> Fees for a period already served remain payable.</p>
772
+ <p>If the event continues for more than thirty (30) consecutive days, either of us may terminate the
773
+ affected subscription on written notice, and we will refund the unused portion of any period you have
774
+ prepaid for it.</p>
775
+ <h2 id="assignment-and-change-of-control" tabindex="-1">Assignment and change of control</h2>
776
+ <h3 id="you" tabindex="-1">You</h3>
777
+ <p>You may not assign, transfer, novate, charge or otherwise deal with these Terms, or any of your rights or
778
+ obligations under them, without our prior written consent. <strong>We will not withhold or delay that consent
779
+ unreasonably.</strong></p>
780
+ <p>You may, on written notice to us and without our consent, transfer these Terms to a successor of the
781
+ whole of your business, or of the part of it that uses the Service, following a merger, an acquisition or
782
+ a sale of substantially all of your assets — provided the successor agrees in writing to be bound by
783
+ these Terms and no fees are outstanding.</p>
784
+ <h3 id="us" tabindex="-1">Us</h3>
785
+ <p>We may assign or transfer these Terms, in whole or in part:</p>
786
+ <ul>
787
+ <li>to an affiliate; or</li>
788
+ <li>in connection with a merger, acquisition, corporate reorganisation or a sale of all or substantially
789
+ all of our assets or of the business line that provides the Service.</li>
790
+ </ul>
791
+ <p>We do not need your consent to do that, but we will tell you, and the transferee takes on our obligations
792
+ to you under these Terms in full. If you are a consumer and a transfer by us would leave you worse off,
793
+ you may terminate and we will refund the unused portion of any period you have prepaid.</p>
794
+ <h3 id="both-of-us" tabindex="-1">Both of us</h3>
795
+ <p>Any purported assignment in breach of this section is void. An assignment does not release either of us
796
+ from an obligation that had already accrued before it took effect. Subject to all of the above, these
797
+ Terms bind and benefit each party's permitted successors and assigns.</p>
798
+ <p>Sub-contracting part of the Service to a supplier is not an assignment. We remain responsible to you for
799
+ the Service, and our use of sub-processors for personal data is governed by our Data Processing Addendum
800
+ and our published sub-processor list.</p>
801
+ <h2 id="governing-law-and-where-disputes-are-heard" tabindex="-1">Governing law and where disputes are heard</h2>
802
+ <p>These Terms, and any dispute or claim arising out of or in connection with them or with the Service —
803
+ including a non-contractual one — are governed by the laws of the Republic of Bulgaria, without regard to its
804
+ conflict-of-law rules.</p>
805
+ <p>The exclusive forum for any such dispute or claim is the competent courts of Sofia, Bulgaria, and both of us submit to that
806
+ jurisdiction.</p>
807
+ <p>The United Nations Convention on Contracts for the International Sale of Goods does not apply to these
808
+ Terms.</p>
809
+ <p>Either of us may still apply to any court of competent jurisdiction for urgent interim or injunctive
810
+ relief — for example to stop an infringement of intellectual property or a misuse of confidential
811
+ information — without that being a breach of this section.</p>
812
+ <p><strong>There is no arbitration clause and no class-action waiver in these Terms.</strong> We have not asked you to
813
+ give up the right to go to court, or to bring a claim together with other people.</p>
814
+ <h3 id="if-you-are-a-consumer-3" tabindex="-1">If you are a consumer</h3>
815
+ <p><strong>If you are dealing with us as a consumer rather than for purposes related to your trade, business,
816
+ craft or profession, this section does not take anything away from you.</strong></p>
817
+ <ul>
818
+ <li>You keep the protection of the mandatory rules of the law of the country where you habitually live.
819
+ Where those rules give you more than the laws of the Republic of Bulgaria does, they win.</li>
820
+ <li>You may bring proceedings against us either in the competent courts of Sofia, Bulgaria or in the courts of the country where
821
+ you live.</li>
822
+ <li>We will bring proceedings against you only in the courts of the country where you live.</li>
823
+ </ul>
824
+ <h3 id="complaints-and-out-of-court-routes" tabindex="-1">Complaints, and out-of-court routes</h3>
825
+ <p>Please tell us first. Write to legal@ever.co with what went wrong and what you would like us to do.
826
+ Most disputes end there, and it costs you nothing to try.</p>
827
+ <p>We are not currently committed to using any particular alternative dispute resolution body, and we are
828
+ not obliged to use one. If you ask us to resolve a dispute through an ADR or mediation body, we will
829
+ consider the request in good faith and tell you whether we agree.</p>
830
+ <p>If you are a consumer, you can also approach the consumer protection authority or the recognised consumer
831
+ ADR body in your own country. <strong>The European Commission's online dispute resolution platform closed on
832
+ 20 July 2025, so there is no longer an EU-wide online form for this</strong> — the route now runs through your
833
+ national body.</p>
834
+ <p>For a complaint about how we handle personal data, write to privacy@ever.co. You may also complain to
835
+ our lead supervisory authority, the Commission for Personal Data Protection (Комисия за защита на личните данни)
836
+ (CPDP) —
837
+ <a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a> — or to the data
838
+ protection authority in the country where you live or work. Doing so does not affect any other remedy you
839
+ have.</p>
840
+ <h2 id="notices" tabindex="-1">Notices</h2>
841
+ <h3 id="how-we-contact-you" tabindex="-1">How we contact you</h3>
842
+ <p>We give you notice in one of three ways:</p>
843
+ <ul>
844
+ <li><strong>by email</strong>, to the address registered on your account;</li>
845
+ <li><strong>inside the product</strong>, as a banner, a message or a prompt you have to acknowledge; or</li>
846
+ <li><strong>by publishing it</strong>, where the notice applies to everyone — for example a new version of these Terms
847
+ or of a policy — with its effective date shown on the page.</li>
848
+ </ul>
849
+ <p><strong>Keep the email address on your account current, and make sure someone reads it.</strong> A notice sent to the
850
+ address you gave us counts as given, even if the person who set up the account has left. If your billing
851
+ and technical contacts are different people, tell us, and we will use the right one.</p>
852
+ <h3 id="how-you-contact-us" tabindex="-1">How you contact us</h3>
853
+ <p>For anything to do with these Terms, write to legal@ever.co.</p>
854
+ <p>A <strong>formal legal notice</strong> — terminating for breach, notifying a breach, making a claim, or invoking the
855
+ indemnification section — must be in writing and sent to legal@ever.co. If you want the notice to be
856
+ 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>
857
+ <p>A support ticket, a chat message, a social media post or a comment inside the product is not a formal
858
+ legal notice, and neither is an email to an individual employee's personal work address.</p>
859
+ <p>Privacy and data-protection matters go to privacy@ever.co; abuse and security reports go to
860
+ abuse@ever.co. Those addresses are monitored, and using them gets you a faster answer than the legal
861
+ address will.</p>
862
+ <h3 id="when-a-notice-counts-as-received" tabindex="-1">When a notice counts as received</h3>
863
+ <ul>
864
+ <li><strong>Email</strong> — on the day it is sent, if that is a business day where the recipient is and it was sent
865
+ before 17:00 local time; otherwise on the next business day. This does not apply if the sender receives
866
+ a bounce or other non-delivery report.</li>
867
+ <li><strong>Inside the product</strong> — when it is first displayed to you.</li>
868
+ <li><strong>Published</strong> — on the effective date stated on the page, or on the date of publication if none is
869
+ stated.</li>
870
+ <li><strong>Post</strong> — on delivery, where a signature or delivery confirmation is obtained; otherwise on the fifth
871
+ business day after posting.</li>
872
+ </ul>
873
+ <p>Notices must be in English.</p>
874
+ <h2 id="general" tabindex="-1">General</h2>
875
+ <h3 id="entire-agreement" tabindex="-1">Entire agreement</h3>
876
+ <p>These Terms, together with the documents they incorporate, are the whole agreement between us about the
877
+ Service, and they replace anything said or written before. Neither of us has relied on any statement,
878
+ promise or representation that is not written down here. Nothing in this paragraph limits liability for
879
+ fraud or fraudulent misrepresentation, and if you are a consumer it does not affect your statutory
880
+ rights.</p>
881
+ <h3 id="which-document-wins" tabindex="-1">Which document wins</h3>
882
+ <p>With several documents in play, conflicts happen. Where two of them genuinely contradict each other, the
883
+ higher one on this list applies:</p>
884
+ <ol>
885
+ <li>an order form or other agreement that we have both signed and that expressly varies these Terms;</li>
886
+ <li>our Data Processing Addendum, on any question about the processing of personal data;</li>
887
+ <li>the annex for the product you are using, which is specific to that product and may add to or change
888
+ these Terms for it;</li>
889
+ <li>these Terms; and</li>
890
+ <li>our Acceptable Use Policy, Refund Policy, <a href="https://ever.tech/privacy">Privacy Policy</a>,
891
+ <a href="https://ever.tech/cookies">Cookie Policy</a> and any other policy incorporated by reference.</li>
892
+ </ol>
893
+ <p>A document is only &quot;in conflict&quot; if both cannot be true at once. A term that adds something is not a
894
+ conflict.</p>
895
+ <h3 id="severability" tabindex="-1">Severability</h3>
896
+ <p>If any provision of these Terms is held to be invalid or unenforceable, it is treated as modified to the
897
+ smallest extent needed to make it valid, and if that is not possible it is severed. Everything else
898
+ continues in force.</p>
899
+ <h3 id="no-waiver" tabindex="-1">No waiver</h3>
900
+ <p>If either of us delays or fails to enforce a right, that is not a waiver of it. A waiver only counts if
901
+ it is in writing, and it applies only to the occasion it was given for. Exercising a right once or in
902
+ part does not prevent exercising it again or in full.</p>
903
+ <h3 id="nobody-else-can-enforce-these-terms" tabindex="-1">Nobody else can enforce these Terms</h3>
904
+ <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
905
+ not need anyone else's consent to vary or terminate them.</p>
906
+ <h3 id="we-are-independent-of-each-other" tabindex="-1">We are independent of each other</h3>
907
+ <p>We are independent contractors. Nothing in these Terms creates a partnership, joint venture, agency,
908
+ franchise or employment relationship between us, and neither of us may bind the other or hold itself out
909
+ as able to.</p>
910
+ <h3 id="how-to-read-these-terms-1" tabindex="-1">How to read these Terms</h3>
911
+ <p>Headings are there to help you find things and do not affect meaning. &quot;Including&quot; and &quot;for example&quot; never
912
+ limit what comes before them. The singular includes the plural and the other way round. A reference to
913
+ writing includes email.</p>
914
+ <h3 id="acceptance-signature-and-records" tabindex="-1">Acceptance, signature and records</h3>
915
+ <p>You may accept these Terms by clicking to accept, by signing electronically, or by using the Service —
916
+ each is as valid as a signature on paper, and you agree not to challenge validity on the ground that
917
+ acceptance was electronic. These Terms may be signed in counterparts, and an electronic or scanned copy
918
+ counts as an original.</p>
919
+ <p>We keep a record of your acceptance, including the version, the date and a fingerprint of the exact text
920
+ you accepted.</p>
921
+ <h3 id="language" tabindex="-1">Language</h3>
922
+ <p><strong>The English version of these Terms is the authoritative one.</strong> We may publish translations to help you
923
+ read them, but a translation is a convenience only, and where it differs from the English text the
924
+ English text applies.</p>
925
+ <h2 id="how-to-reach-us" tabindex="-1">How to reach us</h2>
926
+ <p>Write to a person, not a form. These addresses are monitored and we answer them.</p>
927
+ <ul>
928
+ <li><strong>Contracts, these Terms, formal legal notices</strong> — legal@ever.co</li>
929
+ <li><strong>Privacy, data protection, and requests about your personal data</strong> — privacy@ever.co</li>
930
+ <li><strong>Abuse, security reports, and anything harmful you find on the Service</strong> — abuse@ever.co</li>
931
+ </ul>
932
+ <p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company
933
+ number 204599535.</p>
934
+ <p>We correspond in English.</p>
935
+ <p>This document is version 1.0.0 of the Terms of Service for
936
+ <a href="https://ever.tech">ever.tech</a>, in force from 2026-10-25. Earlier versions, with the
937
+ dates they applied, are at <a href="https://ever.tech/tos">https://ever.tech/tos</a>.</p>