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