@ever-co/legal 0.6.0 → 0.7.1

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 (98) hide show
  1. package/dist/content/aup/ever-async/en.json +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +2 -2
  3. package/dist/content/aup/ever-demand/en.json +2 -2
  4. package/dist/content/aup/ever-rec/en.json +2 -2
  5. package/dist/content/aup/ever-teams/en.json +2 -2
  6. package/dist/content/aup/ever-works/en.json +2 -2
  7. package/dist/content/aup/everiq/en.json +2 -2
  8. package/dist/content/aup/gauzy/en.json +2 -2
  9. package/dist/content/aup/githands/en.json +2 -2
  10. package/dist/content/aup/hust/en.json +2 -2
  11. package/dist/content/aup/traduora/en.json +2 -2
  12. package/dist/content/cookies/ever-async/en.json +2 -2
  13. package/dist/content/cookies/ever-corporate/en.json +2 -2
  14. package/dist/content/cookies/ever-demand/en.json +2 -2
  15. package/dist/content/cookies/ever-rec/en.json +2 -2
  16. package/dist/content/cookies/ever-teams/en.json +2 -2
  17. package/dist/content/cookies/ever-tech/en.json +2 -2
  18. package/dist/content/cookies/ever-works/en.json +2 -2
  19. package/dist/content/cookies/everiq/en.json +2 -2
  20. package/dist/content/cookies/gauzy/en.json +2 -2
  21. package/dist/content/cookies/githands/en.json +2 -2
  22. package/dist/content/cookies/hust/en.json +2 -2
  23. package/dist/content/cookies/traduora/en.json +2 -2
  24. package/dist/content/dpa/ever-async/en.json +2 -2
  25. package/dist/content/dpa/ever-demand/en.json +2 -2
  26. package/dist/content/dpa/ever-rec/en.json +2 -2
  27. package/dist/content/dpa/ever-teams/en.json +2 -2
  28. package/dist/content/dpa/ever-tech-services/en.json +2 -2
  29. package/dist/content/dpa/ever-works/en.json +2 -2
  30. package/dist/content/dpa/gauzy/en.json +2 -2
  31. package/dist/content/dpa/githands/en.json +2 -2
  32. package/dist/content/dpa/hust/en.json +2 -2
  33. package/dist/content/dpia/gauzy/en.json +2 -2
  34. package/dist/content/privacy/ever-async/en.json +2 -2
  35. package/dist/content/privacy/ever-corporate/en.json +2 -2
  36. package/dist/content/privacy/ever-demand/en.json +2 -2
  37. package/dist/content/privacy/ever-rec/en.json +2 -2
  38. package/dist/content/privacy/ever-teams/en.json +2 -2
  39. package/dist/content/privacy/ever-tech/en.html +90 -24
  40. package/dist/content/privacy/ever-tech/en.json +4 -4
  41. package/dist/content/privacy/ever-works/en.json +2 -2
  42. package/dist/content/privacy/everiq/en.json +2 -2
  43. package/dist/content/privacy/gauzy/en.json +2 -2
  44. package/dist/content/privacy/githands/en.json +2 -2
  45. package/dist/content/privacy/hust/en.json +2 -2
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-corporate/en.json +2 -2
  48. package/dist/content/refund/ever-demand/en.json +2 -2
  49. package/dist/content/refund/ever-rec/en.json +2 -2
  50. package/dist/content/refund/ever-teams/en.json +2 -2
  51. package/dist/content/refund/ever-tech-services/en.json +2 -2
  52. package/dist/content/refund/ever-works/en.json +2 -2
  53. package/dist/content/refund/gauzy/en.json +2 -2
  54. package/dist/content/refund/githands/en.json +2 -2
  55. package/dist/content/refund/hust/en.json +2 -2
  56. package/dist/content/refund/traduora/en.json +2 -2
  57. package/dist/content/security/ever-async/en.json +2 -2
  58. package/dist/content/security/ever-corporate/en.json +2 -2
  59. package/dist/content/security/ever-demand/en.json +2 -2
  60. package/dist/content/security/ever-rec/en.json +2 -2
  61. package/dist/content/security/ever-teams/en.json +2 -2
  62. package/dist/content/security/ever-tech/en.html +21 -2
  63. package/dist/content/security/ever-tech/en.json +9 -4
  64. package/dist/content/security/ever-works/en.json +2 -2
  65. package/dist/content/security/gauzy/en.json +2 -2
  66. package/dist/content/security/githands/en.json +2 -2
  67. package/dist/content/security/hust/en.json +2 -2
  68. package/dist/content/security/traduora/en.json +2 -2
  69. package/dist/content/subprocessors/ever-async/en.json +2 -2
  70. package/dist/content/subprocessors/ever-corporate/en.json +2 -2
  71. package/dist/content/subprocessors/ever-demand/en.json +2 -2
  72. package/dist/content/subprocessors/ever-rec/en.json +2 -2
  73. package/dist/content/subprocessors/ever-teams/en.json +2 -2
  74. package/dist/content/subprocessors/ever-tech/en.html +27 -12
  75. package/dist/content/subprocessors/ever-tech/en.json +4 -4
  76. package/dist/content/subprocessors/ever-tech-services/en.json +2 -2
  77. package/dist/content/subprocessors/ever-works/en.json +2 -2
  78. package/dist/content/subprocessors/everiq/en.json +2 -2
  79. package/dist/content/subprocessors/gauzy/en.json +2 -2
  80. package/dist/content/subprocessors/githands/en.json +2 -2
  81. package/dist/content/subprocessors/hust/en.json +2 -2
  82. package/dist/content/subprocessors/traduora/en.json +2 -2
  83. package/dist/content/tos/ever-async/en.json +2 -2
  84. package/dist/content/tos/ever-corporate/en.json +2 -2
  85. package/dist/content/tos/ever-demand/en.json +2 -2
  86. package/dist/content/tos/ever-rec/en.json +2 -2
  87. package/dist/content/tos/ever-teams/en.json +2 -2
  88. package/dist/content/tos/ever-tech/en.html +25 -10
  89. package/dist/content/tos/ever-tech/en.json +4 -4
  90. package/dist/content/tos/ever-tech-services/en.json +2 -2
  91. package/dist/content/tos/ever-works/en.json +2 -2
  92. package/dist/content/tos/everiq/en.json +2 -2
  93. package/dist/content/tos/gauzy/en.json +2 -2
  94. package/dist/content/tos/githands/en.json +2 -2
  95. package/dist/content/tos/hust/en.json +2 -2
  96. package/dist/content/tos/traduora/en.json +2 -2
  97. package/dist/index.json +105 -100
  98. package/package.json +52 -52
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.0",
10
10
  "effectiveDate": "2026-10-04",
11
- "sha256": "c809a1180a0e3ac6b49ad317725aeb1b053d8e865d71ecb3d698893804b05111",
11
+ "sha256": "323c5132313de15b3f59ba6dcb6b565e4100a1c44544756b496b18d0b8de4191",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/refund/010-scope",
@@ -353,5 +353,5 @@
353
353
  }
354
354
  ],
355
355
  "path": "content/refund/traduora/en.html",
356
- "markdown": "# Refund Policy\r\n\r\n**Ever Traduora** — [traduora.co](https://traduora.co)\r\n\r\nVersion 1.0.0 · In force from 2026-10-04\r\n\r\nThis policy explains what happens to your money. When we refund it, when we do not, how a cancellation\r\naffects a term you have already paid for, and what statutory rights you have that no policy of ours can\r\ntouch.\r\n\r\nIt is published by **Ever Technologies LTD**, a company registered in Bulgaria under company\r\nnumber 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria (\"**we**\", \"**us**\",\r\n\"**our**\"). Ever Technologies LTD is the party you contract with and the party that takes your payment.\r\n\r\n## What this policy covers\r\n\r\nThis policy applies to the fees you pay us for Ever Traduora — subscriptions, one-off purchases,\r\nseats, add-ons and usage charges billed through your account with us.\r\n\r\nIt forms part of our [Terms of Service](https://traduora.co/tos) and should be read with them. The Terms set\r\nout the contract; this policy is the detail on refunds, cancellation and billing disputes. Where the two\r\ndescribe the same thing, they are meant to say the same thing — if you ever find that they do not, write to\r\nlegal@ever.co and we will fix the document rather than argue about it.\r\n\r\n### What it does not cover\r\n\r\n- **Free plans.** If you pay us nothing, there is nothing to refund. What you get on a free, trial or\r\n pre-release plan is described in our [Terms of Service](https://traduora.co/tos), and it comes with a much\r\n weaker set of promises.\r\n- **Software you run yourself.** Parts of what powers the Service are published as open source. If you run\r\n your own copy, you paid us nothing for it and this policy has nothing to say about it. Your rights in the\r\n code come from its open-source licence.\r\n- **Purchases you made from someone else.** If you bought access through a reseller, a partner, a cloud\r\n marketplace or an app store, your money went to them, not to us. **Their refund terms apply and they are\r\n the ones who can refund you.** We will help you work out who to ask.\r\n- **What your own customers pay you.** If you use the Service to run something of your own, the money your\r\n users pay you is between you and them. This policy is not your refund policy.\r\n\r\n### Two kinds of customer, and the difference matters\r\n\r\nSome of what follows depends on which one you are.\r\n\r\n- **You are a consumer** if you are an individual buying for purposes wholly or mainly outside your trade,\r\n business, craft or profession. Consumers in the EU, the EEA and the UK have a statutory right to withdraw\r\n that sits on top of everything else in this policy and cannot be signed away. It has its own section\r\n below, and **it is the part of this document to read first**.\r\n- **You are a business customer** if you are buying for your organisation or for your own trade or\r\n profession — including as a sole trader in most cases. The statutory withdrawal right does not apply to\r\n you. Our voluntary guarantee still does.\r\n\r\nNothing in this policy reduces a right the law gives you and does not let you give up. Where a clause here\r\nwould conflict with such a right, the right wins and the rest of this policy carries on as written.\n\n## Subscriptions and renewal\r\n\r\n### How a subscription is charged\r\n\r\nSubscriptions are paid in advance. When you subscribe, you buy a term — a month, a year, or whatever\r\nlength your plan says — and we charge for the whole of it up front. Usage and overage charges are billed\r\nafter the period in which you run them up.\r\n\r\nThat single fact explains most of this policy. **You have already paid for the term you are in, and a\r\nrefund of it is the exception rather than the rule.**\r\n\r\n### Renewal is automatic\r\n\r\nAt the end of each term your subscription renews for another term of the same length, at the price then in\r\neffect for your plan, and we charge the payment method on file. This carries on until you cancel.\r\n\r\nWe give you reasonable advance notice before a price increase reaches you, and a new price never applies\r\npart-way through a term you have already paid for. If you do not want to pay it, cancel before the renewal\r\ndate.\r\n\r\n### Renewals are not refundable\r\n\r\n**A renewal charge is not covered by our 30-day money-back guarantee.** The guarantee is for a first\r\npurchase — see the section on it below.\r\n\r\nIf a renewal has taken you by surprise, tell us at legal@ever.co and say what happened. We cannot\r\npromise a refund and we will not pretend otherwise, but we would rather hear about a renewal you did not\r\nwant than read about it in a chargeback.\r\n\r\nTo avoid an unwanted renewal, cancel before the renewal date. Cancelling on the day the charge lands is too\r\nlate for that term.\r\n\r\n### One-off and perpetual purchases\r\n\r\nSome plans are a single purchase rather than a subscription — a one-time licence, a perpetual licence, or a\r\nbundle of credits or usage bought in advance.\r\n\r\n- There is no renewal to cancel and no recurring charge to stop.\r\n- **Our 30-day money-back guarantee applies to a one-off purchase in the same way it applies to a first\r\n subscription payment**, provided it is your first purchase.\r\n- Credits, allowances and usage bought in advance are not refunded once they have been used, and unused\r\n ones expire on whatever schedule your plan states.\r\n\r\nWhere Ever Traduora sells a plan of this kind, the product-specific section later in this policy says\r\nwhat it is and what happens at the end of its life.\r\n\r\n### Committed terms and signed orders\r\n\r\nIf you signed an order form or agreement with us for a fixed committed term, that document governs. A\r\ncommitted term is exactly that: **the fees for it are payable in full whether or not you use the Service**,\r\nand you cannot shorten it by cancelling part-way through. Where the order and this policy disagree, the\r\norder wins for that customer.\n\n## Free plans and trials\r\n\r\n### While you are on a free plan or a trial, there is nothing to refund\r\n\r\nWe have not charged you, so there is nothing to give back. If you decide the Service is not for you during\r\na trial, simply stop using it or cancel — you owe us nothing and you do not need a reason.\r\n\r\nThe same is true of free tiers, evaluations, proofs of concept and anything we have labelled beta, preview\r\nor early access. What those offerings do and do not come with is set out in our\r\n[Terms of Service](https://traduora.co/tos), and it is a deliberately thin set of promises.\r\n\r\n### What happens when a trial ends\r\n\r\nIf your trial is one that converts to a paid plan, we say so when you start it, we tell you the price and\r\nthe date, and we charge the payment method you gave us on that date unless you have cancelled first.\r\n\r\n- **Cancel before the trial ends and you are not charged.** Cancelling on the day the charge lands is too\r\n late.\r\n- **If the trial converts and that charge is your first payment to us, our 30-day money-back guarantee\r\n applies to it in full.** A trial does not use the guarantee up.\r\n- If your trial does not convert automatically, it simply expires and access stops.\r\n\r\n### Card checks are not charges\r\n\r\nSome plans ask for a payment card at the start of a trial. Where they do, your bank or card issuer may\r\nplace a small temporary authorisation on the card to check it is valid. **That is not a payment, we do not\r\nreceive it, and there is nothing for us to refund** — it drops off by itself, usually within a few days,\r\non your issuer's timetable rather than ours.\r\n\r\nIf an authorisation of that kind is still showing after a week, contact your card issuer. If you would like\r\nus to confirm what we did and did not charge, write to legal@ever.co and we will.\r\n\r\n### Your data when a trial or free plan ends\r\n\r\n**Do not put anything into a free or trial plan that you cannot afford to lose.**\r\n\r\nWhen a trial ends without converting, or a free plan is closed or withdrawn, the account and everything in\r\nit may be deleted. We will give you a reasonable chance to export your data where we can, but exporting in\r\ntime is your responsibility, and our backups are for our own operational continuity — they are not your\r\narchive. Our [Terms of Service](https://traduora.co/tos) set out what happens to your data when access ends.\r\n\r\n### Consumers keep their statutory rights on a paid conversion\r\n\r\nIf you are a consumer and a trial converts into a paid contract, the statutory 14-day withdrawal right\r\ndescribed below applies to that contract in the ordinary way. **A free period beforehand does not shorten\r\nit and does not use it up.**\n\n## Cancelling\r\n\r\n### How to cancel\r\n\r\nCancel from your account settings, or write to legal@ever.co from the email address on the account. We\r\ndo not put cancellation behind a phone call, a retention conversation or a notice period.\r\n\r\nIf you cancel by email, we treat the cancellation as made on the day we receive it, not the day we get\r\nround to processing it. Ask us for confirmation and we will send it.\r\n\r\n### What cancelling does\r\n\r\n**Cancelling stops the next renewal. It does not refund the term you are in.**\r\n\r\n- Your access continues until the end of the period you have already paid for, and then stops.\r\n- We do not pro-rate an unused part of a term on cancellation, except where our 30-day guarantee applies or\r\n where the law requires it.\r\n- Cancelling in month seven of an annual term does not produce five months back. The plan runs to the end\r\n of the year you paid for.\r\n- Usage you have already run up in the current period is still payable, even after you cancel.\r\n\r\nIf you would rather keep the remaining time than lose it, do not cancel immediately — cancellation only has\r\nto reach us before the renewal date to stop the next charge.\r\n\r\n### Cancelling is not deleting\r\n\r\nCancelling ends the subscription. It does not by itself delete your account, your workspace or your data,\r\nand it is not a request to erase your personal data. Those are separate things, and you can ask for them\r\nseparately.\r\n\r\nWhat happens to your data after a subscription ends, including the window in which you can still export it,\r\nis set out in our [Terms of Service](https://traduora.co/tos). What we do with personal data, and how to ask us\r\nto erase it, is in our [Privacy Policy](https://traduora.co/privacy).\r\n\r\n### Downgrading is not cancelling\r\n\r\nMoving to a cheaper plan is a plan change, not a cancellation, and it follows the rules in the section on\r\nupgrades and downgrades below. In particular, **a downgrade does not refund the difference for the term you\r\nare in.**\r\n\r\n### If we end it rather than you\r\n\r\n- **If we terminate or suspend your access because you broke the Terms or our Acceptable Use Policy, or\r\n because you did not pay, we do not refund the remainder of the term.** Fees for a suspended period are\r\n not refunded either.\r\n- **If we terminate without cause, or we withdraw Ever Traduora altogether, we refund the unused\r\n part of what you have already paid, pro rata** — counted from the day access ends to the end of the term\r\n you paid for. That refund is the remedy for the withdrawal itself; the limits on our liability in the\r\n Terms still apply to everything else.\r\n\r\nIf you are a consumer, your statutory rights on termination are unaffected by any of this.\n\n## Our 30-day money-back guarantee\r\n\r\n### The promise, in one paragraph\r\n\r\n**If you are not satisfied, you can ask for your first payment back within thirty (30) days of making it,\r\nand we will refund it in full.** No lengthy justification, no restocking fee, no deduction for the days you\r\nused. Write to legal@ever.co within the 30 days, from the email address on the account, and tell us\r\nwhich payment you mean.\r\n\r\nThis is something we offer voluntarily. It is not a statutory right, and it does not replace one — if you\r\nare a consumer, the 14-day withdrawal right described below exists as well, and you may rely on whichever\r\nis better for you.\r\n\r\n### It applies to a first purchase, and only to a first purchase\r\n\r\nWe want to be blunt about the limit rather than let you discover it at the wrong moment.\r\n\r\n- The guarantee covers **your first payment to us for Ever Traduora**. That may be a first\r\n subscription charge, a first one-off purchase, or the first charge after a trial converts.\r\n- **It applies once per customer.** Not once per plan, not once per workspace, and not once per year.\r\n- **Renewals are not covered.** Neither is any later purchase, upgrade, add-on, seat or usage charge.\r\n- Closing an account and opening a new one does not produce a fresh guarantee. Nor does moving between our\r\n products under the same billing relationship.\r\n\r\nThe 30 days run from the date of the payment itself, not from the day you signed up, the day you first\r\nlogged in, or the day you noticed the charge.\r\n\r\n### Annual plans\r\n\r\nAn annual plan is not treated differently, and the window is not longer because the term is.\r\n\r\n- If the annual fee was your first payment, you have the same 30 days to ask for it back, and we refund it\r\n in full.\r\n- Inside those 30 days you may instead ask us to keep your access running and refund the unused part of the\r\n year pro rata. Tell us which you would prefer and we will do that one.\r\n- **Outside those 30 days there is no pro-rata refund of the unused part of an annual term.** The plan runs\r\n to the end of the year you paid for and then stops.\r\n\r\n### What we do with the request\r\n\r\nWe do not ask you to prove dissatisfaction. We will usually ask one question — what went wrong — because it\r\nis the most useful thing anyone tells us, and you are free not to answer it.\r\n\r\nOnce we agree the refund we start it promptly, pay it to the method you used, and confirm it in writing.\r\nThe mechanics are in the section on how refunds are paid.\r\n\r\n### Refunds outside the guarantee\r\n\r\nSometimes the right thing to do sits outside a written rule: a duplicate charge, a plan nobody ever\r\nactivated, an outage that made the thing unusable for a stretch. **We may make a refund or a credit in\r\nthose situations at our discretion.**\r\n\r\nDoing so once does not create an entitlement, does not extend the guarantee, and does not oblige us to do\r\nit again in a case that looks similar to you. If you think you are in one of those situations, write to\r\nlegal@ever.co and put it to us plainly — that works better than a dispute with your bank.\n\n## What we do not refund\r\n\r\nSome charges are outside every refund route in this policy. They are listed here in one place so you can\r\nsee them before you buy rather than after.\r\n\r\n### Usage, overages and anything already consumed\r\n\r\n- **Usage and overage charges** for a period you have already used — API calls, storage, seats occupied,\r\n messages, minutes, jobs, exports, computation, or whatever the meter on your plan counts.\r\n- **Credits, allowances and prepaid units that have been spent.** Unused ones expire on the schedule your\r\n plan states and are not converted to cash.\r\n- Anything else you have already had the benefit of. Once we have supplied it, it is supplied.\r\n\r\n### Add-ons, extras and partial periods\r\n\r\n- **Optional features, add-ons and modules** you switched on, for the term in which you switched them on.\r\n- **Additional seats** for the period they were active. Removing a seat takes effect at your next renewal\r\n and does not produce a refund.\r\n- **Part-periods.** We bill by term. Cancelling part-way through one does not produce a refund of the\r\n remainder, except under the 30-day guarantee or where the law requires it.\r\n\r\n### Set-up and professional services\r\n\r\n- **Set-up, onboarding, configuration, migration, data import, training and consultancy fees**, once the\r\n work has been done. Where work is partly done, we refund only the part not yet performed.\r\n- **Custom development, bespoke integrations and anything built to your specification.** These are made for\r\n you and cannot be resold, so they are non-refundable once started, in proportion to the work completed.\r\n- Time booked and then not used, where we held the time for you and you gave us no reasonable notice.\r\n\r\n### Third-party and marketplace charges\r\n\r\n- **Anything you bought from someone else** — a reseller, partner, cloud marketplace, app store or payment\r\n intermediary. Your money went to them. Their refund terms apply and only they can refund you.\r\n- **Pass-through purchases we made on your behalf**, such as domain names, certificates, telephone numbers,\r\n paid third-party APIs or model provider usage, once we have paid for them ourselves.\r\n- Charges made to you by a third-party service you connected to Ever Traduora. We do not control\r\n what a connected service bills you.\r\n\r\n### Periods you could not use because of something you did\r\n\r\n- **Any period during which your access was suspended** for non-payment, for breach of our\r\n [Terms of Service](https://traduora.co/tos), or for breach of our Acceptable Use Policy. The subscription\r\n keeps running and the fees keep accruing during a suspension.\r\n- Time lost because you locked yourself out, misconfigured the Service, deleted your own data, or lost\r\n control of your own credentials.\r\n\r\n### Bank charges and currency movement\r\n\r\nFees your bank, card issuer or payment provider charges you — cross-border fees, conversion fees, transfer\r\ncharges — are yours. **We refund what we received, not what it cost you to send it**, and we do not\r\ncompensate for a movement in the exchange rate between the payment and the refund.\r\n\r\n### What this list does not do\r\n\r\nThis list does not remove your statutory rights, and it does not sit above them.\r\n\r\n**If you are a consumer exercising the 14-day withdrawal right described below, that right governs and this\r\nlist does not cut it down.** Nor does anything here limit our liability where the law does not permit it —\r\nour [Terms of Service](https://traduora.co/tos) set out exactly which liabilities we do not limit.\n\n## Upgrades, downgrades and seats\r\n\r\nPlan changes are billing events, not refund events. This section says which direction money moves in each\r\ncase, so nothing about it comes as a surprise.\r\n\r\n### Upgrading during a term\r\n\r\nWhen you move to a more expensive plan part-way through a term, the change takes effect immediately and we\r\ncharge you for the rest of that term at the new rate, less the unused part of what you already paid for the\r\nold plan. In other words you pay the difference for the time remaining, not the full price twice.\r\n\r\n- Your renewal date does not move unless we say so at the time.\r\n- **An upgrade is not a first purchase.** It does not restart the 30-day money-back guarantee, and the\r\n guarantee does not apply to the upgrade charge.\r\n- If an upgrade unlocks usage that is metered, the meter starts at the new plan's rates from the moment the\r\n upgrade takes effect.\r\n\r\n### Downgrading\r\n\r\nA downgrade takes effect at your next renewal, not immediately, and it is not a refund.\r\n\r\n- **You are not refunded the difference for the term you are already in.** You keep the higher plan until\r\n the term ends, then continue on the cheaper one.\r\n- We will tell you what you lose. If your account is over the new plan's limits — seats, storage, projects,\r\n workspaces, retention, whichever your plan meters — those limits apply once the downgrade takes effect,\r\n and features above them stop being available.\r\n- **Data above a lower plan's limits may become inaccessible, and may eventually be deleted.** Export\r\n anything you need before the downgrade date. We will give you notice of what is affected where we\r\n reasonably can, but the decision to downgrade is yours and so is the timing.\r\n\r\nIf a downgrade would cost you something you did not expect, cancel the downgrade before the renewal date\r\nrather than after it.\r\n\r\n### Seats\r\n\r\nWhere your plan charges per seat, per user or per licence:\r\n\r\n- **Adding a seat is charged from the day you add it for the rest of the current term**, at the rate then\r\n published for your plan.\r\n- **Removing a seat does not reduce the current term's fee and does not create a refund.** It takes effect\r\n at your next renewal.\r\n- Where seat count is derived automatically from your own directory or identity provider, **an\r\n administrator on your side adding a member is itself an instruction to buy a seat**, and it changes your\r\n bill without any further step from us. Decide who in your organisation is allowed to do that.\r\n\r\n### Moving between products or plan families\r\n\r\nMoving from one of our products to another, or between plan families that are billed differently, is\r\ntreated as a new purchase of the new plan and a cancellation of the old one — with the ordinary rule that\r\nthe old term is not refunded. It does not create a fresh 30-day guarantee.\r\n\r\nIf a migration of that kind is something we asked you to do, tell us at legal@ever.co before you do it.\r\nWe will not leave you paying twice for a change we initiated.\n\n## How we pay a refund\r\n\r\n### Back the way it came\r\n\r\nWe refund to the payment method that made the original payment — the same card, the same account, the same\r\nprovider. That is how card and bank rules work, and it is also the safest route for both of us.\r\n\r\nIf that method no longer exists — a closed account, an expired card that cannot accept a reversal, a\r\nprovider we no longer work with — tell us and we will agree an alternative in writing. We may ask you to\r\nconfirm the new details from the email address on the account before we send money to a destination that\r\ndid not send it to us.\r\n\r\n**We do not refund to a different person, a different company or a third-party account**, and we do not pay\r\nrefunds in cash, cryptocurrency or gift cards.\r\n\r\n### Timing\r\n\r\n- We start a refund within **five (5) business days** of agreeing it, and usually the same day.\r\n- After that it moves at your bank's or card issuer's pace. **Five to ten business days** is typical; some\r\n issuers take a full statement cycle to show a card refund.\r\n- **Where you are a consumer exercising the statutory 14-day withdrawal right, we pay within 14 days** of\r\n being told, as the law requires — see that section below.\r\n\r\nIf a refund we have confirmed has not reached you within fifteen (15) business days, write to\r\nlegal@ever.co with the confirmation and we will trace it with our payment provider.\r\n\r\n### Amount and currency\r\n\r\n- **We refund in the currency we charged**, at the amount we charged. We do not convert a refund into\r\n another currency on request.\r\n- **We never refund more than we actually received.** If the exchange rate has moved since your payment,\r\n the amount reaching your account may be worth more or less than it was — that is between you and your\r\n bank, and we do not top it up or claw it back.\r\n- Fees charged to you by your own bank, card issuer or intermediary — conversion, cross-border, transfer —\r\n are not part of what we received and are not reimbursed.\r\n- A partial refund is stated as a figure and an explanation on the credit note, so you can check the\r\n arithmetic.\r\n\r\n### Credit instead of cash\r\n\r\nWhere you would rather have account credit than money back, we can usually do that, and it is normally\r\nfaster. **We will only do it if you ask for it.** We do not substitute credit for a refund you are entitled\r\nto, and credit is never offered as a way of avoiding the statutory withdrawal right.\r\n\r\nCredit applied to your account is used against future charges, is not transferable, and is not later\r\nconvertible into cash.\r\n\r\n### Paperwork\r\n\r\nEvery refund produces a credit note against the original invoice, issued electronically to the billing\r\ncontact on the account. Keep it — it is what your own accountant and, where relevant, your tax authority\r\nwill want to see.\n\n## Tax on refunds\r\n\r\nOur fees are quoted exclusive of VAT, sales tax and similar charges, which are added on top where they\r\napply. A refund follows the same logic in reverse.\r\n\r\n### What comes back\r\n\r\n- **Where we charged you tax, we refund the tax with the fee**, in proportion to the amount refunded. A\r\n half refund returns half the tax.\r\n- **Where we charged you no tax, none comes back.** If you are a business customer in another EU member\r\n state and the reverse charge applied, we never held VAT on that sale, so a refund is of the net fee\r\n alone.\r\n- We issue a credit note for every refund, showing the net amount, the tax and the rate applied. That\r\n document, not this policy, is what your accounting needs.\r\n\r\n### Tax you accounted for yourself\r\n\r\n**If you self-assessed VAT under the reverse charge, or paid tax directly to your own authority, we cannot\r\ngive it back to you — we never had it.** Adjust it through your own VAT return or the equivalent filing in\r\nyour country, using our credit note as the supporting document. If your adviser needs anything further from\r\nus, ask at legal@ever.co.\r\n\r\nThe same is true of any amount you withheld or deducted at source, and of import, customs or similar\r\ncharges levied by a country we did not bill from.\r\n\r\n### If your tax position changed after the invoice\r\n\r\nTax is calculated on the facts as they stood when we invoiced — your billing country, your status, and the\r\ntax identification number you gave us at the time.\r\n\r\n- If you gave us no valid VAT identification number and we therefore charged VAT, **supplying the number\r\n later does not turn that charge into a refund.** It applies to invoices from the point we have it.\r\n- If you told us something that was wrong or out of date and we were assessed for tax as a result, that\r\n cost is yours, as our [Terms of Service](https://traduora.co/tos) set out.\r\n- Tell us promptly when your registration, place of establishment or tax status changes. It is far easier\r\n to bill correctly than to unpick it afterwards.\r\n\r\n### Rate changes\r\n\r\nWhere a tax rate changes between the payment and the refund, we refund the tax at the rate we actually\r\ncharged you — not at today's rate. That is what the credit note has to match.\r\n\r\n### Bank charges are not tax\r\n\r\nConversion fees, cross-border fees and transfer charges from your own bank are not tax, are not part of\r\nwhat we received, and are not refunded. They are covered in the section on how refunds are paid.\n\n## Chargebacks and payment disputes\r\n\r\n### Talk to us first\r\n\r\nIf a charge looks wrong — a duplicate, an amount you did not expect, a renewal you meant to cancel, a\r\npayment you do not recognise — **write to legal@ever.co before you contact your bank.** Tell us the\r\naccount, the date, the amount and what you think went wrong.\r\n\r\nWe can usually resolve it in a day or two. A chargeback takes weeks, is decided by people who have never\r\nseen your account, and often ends with a worse outcome for you than a direct refund would have. Contacting\r\nus costs you nothing and does not affect your right to go to your bank afterwards if we cannot sort it out.\r\n\r\n### What happens if a chargeback is raised\r\n\r\nIf you raise a chargeback, reversal or payment dispute with your bank, card issuer or payment provider\r\nwithout contacting us first:\r\n\r\n- **we may suspend your access to the Service while the dispute is open**, because the money for the period\r\n in question has been taken back and the account is, for the moment, unpaid;\r\n- we will respond to the dispute and **supply our evidence to the payment provider** — the invoice and\r\n credit notes, the record of your acceptance of our terms, the plan and dates in question, our\r\n correspondence with you, and the account and usage records relevant to the charge;\r\n- the subscription itself carries on. **A chargeback is not a cancellation.** Fees keep accruing, and if\r\n you want the subscription to stop you still have to cancel it in the ordinary way.\r\n\r\nIf the dispute is resolved in our favour, the amount stays due. Where the law allows, we may also recover\r\nthe fee our payment provider charges us for handling the dispute, and we may require a different payment\r\nmethod — or decline to continue serving the account — where chargebacks are repeated.\r\n\r\nIf the dispute is resolved in your favour, that is the end of it. We do not re-charge a reversed payment.\r\n\r\n### Fraud and unauthorised use\r\n\r\n**If you think someone used your card or your account without permission, tell your bank straight away, and\r\ntell us at legal@ever.co at the same time.** That is exactly what a chargeback is for, and none of the\r\nabove is aimed at you.\r\n\r\nWe will help: we can confirm what was charged, when, from where, and against which account, and we will\r\nclose off the access that produced it.\r\n\r\n### What this section does not do\r\n\r\n**Nothing here takes away your right to dispute a payment with your bank or card issuer.** That right comes\r\nfrom your agreement with them and from the law, not from us, and we cannot and do not ask you to give it\r\nup. We are asking you to try us first — not requiring it as a condition of anything.\r\n\r\nIf you are a consumer, your statutory withdrawal right and your statutory remedies are unaffected by this\r\nsection.\n\n## If you are a consumer in the EU or the UK: your 14-day right to withdraw\r\n\r\n**This is the most important section of this policy, and it is the one part of it we could not change even\r\nif we wanted to.**\r\n\r\nIf you are a consumer buying from us at a distance — online, by email, over the phone — the law gives you\r\n**fourteen (14) days to change your mind and get your money back, without giving any reason**. That right\r\ncomes from EU consumer law and, in the United Kingdom, from the equivalent domestic rules. It exists\r\nseparately from, and in addition to, our own 30-day money-back guarantee.\r\n\r\n**Nothing in this policy, in our [Terms of Service](https://traduora.co/tos), or in anything you clicked on the\r\nway to paying us, takes that right away.** A term that tried to would simply have no effect.\r\n\r\n### Who has it\r\n\r\nYou have it if you are an individual buying for purposes wholly or mainly outside your trade, business,\r\ncraft or profession.\r\n\r\n- **Business customers do not have it.** If you are buying for your organisation, or for your own trade or\r\n profession, this section does not apply to you — the rest of this policy does. That includes companies,\r\n partnerships, and in most cases sole traders buying for their business.\r\n- A few countries extend some consumer protections to sole traders and very small businesses. If the law\r\n where you live does that, it applies whatever this section says.\r\n- If your purchase serves both personal and business purposes, what matters is which purpose predominates.\r\n- If you are not sure which you are, ask us at legal@ever.co before you buy, not after.\r\n\r\n### How long you have\r\n\r\nThe 14 days run **from the day after the contract is made** — for us, the day after your order is accepted\r\nand your subscription or purchase is confirmed. You need only send your notice before the 14 days are up;\r\nit does not matter when it reaches us or when we process it.\r\n\r\n**If we never told you about this right, you get much longer.** In that case the period extends by up to\r\ntwelve (12) months. If we tell you late, but within those twelve months, you get 14 days from the day we\r\ntell you. We would rather tell you here, now, and start the clock properly.\r\n\r\n### How to exercise it\r\n\r\nAny clear statement that you are withdrawing is enough. There is no form to fill in, no reason to give, and\r\nno fee.\r\n\r\n- Email **legal@ever.co** and say that you are withdrawing.\r\n- Or write to us at **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\r\n\r\nSay who you are, which account or invoice you mean, and the date you bought. **Keep a copy of what you\r\nsent** — the burden of showing that you withdrew in time is on you, and a sent email does that neatly.\r\n\r\nWe will acknowledge your notice without delay once we receive it.\r\n\r\n### A model form, if you would rather use one\r\n\r\nYou do not have to use a form. If you prefer one, copy the following, fill it in, and send it to\r\nlegal@ever.co. We will also send you a copy on request.\r\n\r\n> **Notice of withdrawal**\r\n>\r\n> To Ever Technologies LTD, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — legal@ever.co\r\n>\r\n> I give notice that I withdraw from my contract for the supply of Ever Traduora.\r\n>\r\n> Ordered on: *the date of your order*\r\n> Name: *your name*\r\n> Address: *your address*\r\n> Account or email address the order was placed under: *your account*\r\n> Invoice or order reference, if you have one: *the reference*\r\n> Date of this notice: *today's date*\r\n\r\n### What we pay back, and when\r\n\r\nIf you withdraw in time, **we refund everything you paid us under the contract — within fourteen (14) days\r\nof receiving your notice.** We use the same means of payment you used, and we do not charge you a fee for\r\nthe refund.\r\n\r\nWe do not make you wait for a \"processing period\", we do not offer credit instead, and we do not deduct\r\nanything except in the one situation described next.\r\n\r\n### If you asked us to start straight away\r\n\r\nThis is the part that most people meet at checkout without noticing, so here it is in plain words.\r\n\r\nOrdinarily we would have to wait 14 days before giving you access. Almost nobody wants that. So the law\r\nlets you ask us to start supplying the Service immediately, during the withdrawal period — and when you\r\nask, two things follow, which we must tell you and you must acknowledge:\r\n\r\n- **If you withdraw after we have started but before the contract is fully performed, you still get your\r\n money back — minus a proportionate amount for what you actually received.** That amount is worked out\r\n against the total price of the contract and the share of it we had supplied by the moment you told us you\r\n were withdrawing. On a monthly plan used for four days, that is roughly four days' worth.\r\n- **If the Service has been fully performed within the 14 days, and you asked us to begin and acknowledged\r\n this consequence, the right to withdraw is gone.** The same applies where what you bought is digital\r\n content supplied other than on a physical medium and its supply has begun with your express prior consent\r\n and that acknowledgement.\r\n\r\nWe ask for both the request and the acknowledgement at the point of purchase, separately and in plain\r\nwords. **We do not pre-tick them, and we do not bury them in a longer agreement.** If you would rather not\r\ngive them, say so — you can wait out the 14 days instead, and we will start your access afterwards.\r\n\r\n**If we did not obtain your express request and your acknowledgement, or we did not give you the\r\ninformation the law requires, you pay nothing at all for what was supplied during the withdrawal period.**\r\nThat is the law's answer, not our concession, and we will apply it without argument.\r\n\r\n### How this fits with our 30-day guarantee\r\n\r\nThey are two different things and you do not have to choose blind.\r\n\r\n- The **statutory right** is 14 days, applies to consumers only, cannot be excluded, and can carry a\r\n proportionate charge for what you used if you asked us to start early.\r\n- The **30-day guarantee** is our own promise, applies to consumers and businesses alike, is limited to a\r\n first purchase, and refunds it in full with no deduction for the days you used.\r\n\r\n**Use whichever leaves you better off.** Tell us which you are relying on, or just tell us what you want\r\nand we will apply the one that gives you more.\r\n\r\n### Complaints, and what to do if we cannot agree\r\n\r\nWrite to legal@ever.co first. Set out what you bought, what went wrong and what you would like us to\r\ndo. We will give you a substantive answer, in writing, and we would much rather resolve it directly.\r\n\r\nIf that does not settle it:\r\n\r\n- **We are not currently committed to, and do not participate in, any alternative dispute resolution (ADR)\r\n body.** We say so because the law requires us to tell you either way. If you ask us to take a dispute to\r\n a particular approved ADR body, we will consider the request in good faith, case by case.\r\n- You can approach the **national consumer protection authority in the country where you live**, and the\r\n approved ADR bodies on the list that authority maintains. Those bodies are free or low-cost for\r\n consumers, and using one does not stop you going to court later.\r\n- Ever Technologies LTD is established in Bulgaria, and you may also raise a complaint with the\r\n consumer protection authority there.\r\n- **The European Commission's online dispute resolution (ODR) platform closed on 20 July 2025 and no longer\r\n exists.** We mention it only because older policies still link to it. Use a national body instead.\r\n\r\n**Your right to bring proceedings in the courts of the country where you live is unaffected**, as are any\r\nother mandatory protections the law of your own country gives you as a consumer. Our\r\n[Terms of Service](https://traduora.co/tos) set out the governing law and venue for everyone else.\n\n## Failed and late payments\r\n\r\n### When a charge does not go through\r\n\r\nPayments fail for ordinary reasons — an expired card, a new card number, a bank's fraud check on a\r\nrecurring charge, a limit reached, a card blocked for travel, a strong-authentication step nobody\r\ncompleted.\r\n\r\nWhen one fails:\r\n\r\n- **we email the billing contact on the account**, and keep emailing while the balance is outstanding;\r\n- **we retry the charge** over the following days, on a schedule set with our payment provider. A retry is\r\n not a second charge — if one succeeds, the others stop;\r\n- your access carries on for the time being. We do not cut you off at the first decline.\r\n\r\nFixing it is usually one step: update the payment method in your account settings and we will take the\r\noutstanding amount. If you cannot, write to legal@ever.co and we will find another way.\r\n\r\n### A failed payment does not pause or cancel anything\r\n\r\nThis is the part that catches people out, so we will say it directly.\r\n\r\n**A failed payment is not a cancellation.** The subscription keeps running, the term keeps running, and the\r\nfees keep accruing. If you meant to cancel, cancel — do not simply let a card expire and assume that ends\r\nit. Cancelling takes a minute and is described above.\r\n\r\nEqually, a failed renewal charge does not mean you have been let out of the renewal. The amount stays owed\r\nuntil it is paid or the subscription is properly cancelled.\r\n\r\n### Suspension\r\n\r\nIf an undisputed amount stays unpaid, **we may suspend your access — but only after written notice and at\r\nleast fourteen (14) days to put it right.** We will tell you what is owed, how to pay it and when the\r\ndeadline falls.\r\n\r\nWhile suspended:\r\n\r\n- the subscription continues and fees continue to accrue;\r\n- **a suspended period is not refunded and is not credited**, even after you pay;\r\n- your data stays where it is. Suspension is not deletion.\r\n\r\nOnce the balance is cleared we restore access promptly, normally the same business day.\r\n\r\n### Interest, costs and continued non-payment\r\n\r\nWhere an amount is overdue we may charge interest from the due date and recover the reasonable costs of\r\ncollecting it, on the basis set out in our [Terms of Service](https://traduora.co/tos). **If you are a\r\nconsumer, we will charge interest and costs only to the extent the law permits**, and the statutory regime\r\nfor late payment between businesses does not apply to you.\r\n\r\nContinued non-payment is a material breach, and we may terminate on that basis. Our\r\n[Terms of Service](https://traduora.co/tos) set out what happens to your data when a subscription ends,\r\nincluding the window for exporting it. **Do not leave an export until after a termination for non-payment.**\r\n\r\n### Disputing rather than not paying\r\n\r\nIf you think an invoice is wrong, say so — do not simply let the payment fail. Write to legal@ever.co\r\nwith the invoice, what you dispute and why, within the period our\r\n[Terms of Service](https://traduora.co/tos) allow for it.\r\n\r\n**Pay the part you are not disputing, on time.** A disputed line does not make the rest of the invoice\r\nlate, and raising a genuine dispute in good faith stops the clock on suspension for the amount in question\r\nwhile we work through it.\r\n\r\nIf your first move is a chargeback rather than an email, the section above on chargebacks applies.\n\n## Annex: Ever Traduora\r\n\r\n### What this policy covers for Ever Traduora\r\n\r\nThere is no hosted Ever Traduora, so there is no hosted subscription to refund. **What we sell is a\r\ncommercial licence for a copy you run yourself**, bought through the checkout at\r\n[https://ever.co/pricing](https://ever.co/pricing), and that is what this policy is about.\r\n\r\nThe section above on what this policy does not cover leaves out software you run yourself, because a copy\r\nof the open-source code costs you nothing. **A commercial licence is different: you paid us for it, and\r\nthis policy covers that payment in full** — including the 30-day money-back guarantee on a first purchase\r\nand, if you are a consumer, the statutory withdrawal right. Where the sections above speak of access to the\r\nService, for Ever Traduora read the licence you bought.\r\n\r\n### Perpetual licences\r\n\r\nThe section above on one-off and perpetual purchases promises that this part of the policy will say what a\r\nperpetual licence is and what happens at the end of its life. For Ever Traduora:\r\n\r\n- **A perpetual licence is charged once.** It does not renew, it is not a subscription, and there is no\r\n recurring charge to cancel.\r\n- **It does not expire.** There is no end of its life to describe.\r\n- Everything this policy says about a one-off purchase applies to it, including the 30-day money-back\r\n guarantee where it is your first purchase.\r\n\r\n### Subscriptions have no free trial\r\n\r\nA self-hosted subscription is charged when you buy it. There is no trial in front of it, so if that is\r\nyour first payment to us, the 30-day money-back guarantee runs from that day.\r\n\r\n### Cancelling\r\n\r\nThere is no account for Ever Traduora, so there are no account settings to cancel from. Write to\r\nlegal@ever.co from the address you bought with, and we will action it.\n\n## How to reach us\r\n\r\nAnything about a charge, a refund, a cancellation or an invoice — write to **legal@ever.co**. That\r\naddress is monitored and we answer it.\r\n\r\nTo get you an answer on the first reply rather than the third, include:\r\n\r\n- the account or workspace, and the email address it is registered to;\r\n- the invoice number, or the date and amount of the payment;\r\n- what you would like — a refund, a cancellation, a correction, or simply an explanation;\r\n- if you are relying on the 30-day guarantee or on the statutory withdrawal right, which one.\r\n\r\nWe acknowledge refund and withdrawal requests without undue delay. **Where you are a consumer exercising\r\nthe statutory 14-day withdrawal right, we pay within 14 days of your notice**, as that section requires.\r\n\r\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\r\nnumber 204599535. We correspond in English.\r\n\r\n### If you are not happy with our answer\r\n\r\nTell us, and say so plainly — we would rather fix it than have it escalate. If we still cannot agree and\r\nyou are a consumer, the complaints and ADR routes in the withdrawal-right section above are open to you,\r\nincluding the national consumer protection authority in the country where you live. **Your right to go to\r\ncourt is unaffected.**\r\n\r\nComplaints about how we handle personal data go somewhere different: privacy@ever.co, and the routes in\r\nour [Privacy Policy](https://traduora.co/privacy).\r\n\r\n### About this document\r\n\r\nThis is version 1.0.0 of the Refund Policy for [traduora.co](https://traduora.co), in force\r\nfrom 2026-10-04. Earlier versions, with the dates they applied, are at\r\n[https://traduora.co/refund](https://traduora.co/refund).\r\n\r\nWe may change this policy. **A change never applies retrospectively to a payment you have already made**,\r\nand it never reduces a statutory right. Where a change matters to a term you are already in, we will tell\r\nyou before it takes effect."
356
+ "markdown": "# Refund Policy\n\n**Ever Traduora** — [traduora.co](https://traduora.co)\n\nVersion 1.0.0 · In force from 2026-10-04\n\nThis policy explains what happens to your money. When we refund it, when we do not, how a cancellation\naffects a term you have already paid for, and what statutory rights you have that no policy of ours can\ntouch.\n\nIt is published by **Ever Technologies LTD**, a company registered in Bulgaria under company\nnumber 204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria (\"**we**\", \"**us**\",\n\"**our**\"). Ever Technologies LTD is the party you contract with and the party that takes your payment.\n\n## What this policy covers\n\nThis policy applies to the fees you pay us for Ever Traduora — subscriptions, one-off purchases,\nseats, add-ons and usage charges billed through your account with us.\n\nIt forms part of our [Terms of Service](https://traduora.co/tos) and should be read with them. The Terms set\nout the contract; this policy is the detail on refunds, cancellation and billing disputes. Where the two\ndescribe the same thing, they are meant to say the same thing — if you ever find that they do not, write to\nlegal@ever.co and we will fix the document rather than argue about it.\n\n### What it does not cover\n\n- **Free plans.** If you pay us nothing, there is nothing to refund. What you get on a free, trial or\n pre-release plan is described in our [Terms of Service](https://traduora.co/tos), and it comes with a much\n weaker set of promises.\n- **Software you run yourself.** Parts of what powers the Service are published as open source. If you run\n your own copy, you paid us nothing for it and this policy has nothing to say about it. Your rights in the\n code come from its open-source licence.\n- **Purchases you made from someone else.** If you bought access through a reseller, a partner, a cloud\n marketplace or an app store, your money went to them, not to us. **Their refund terms apply and they are\n the ones who can refund you.** We will help you work out who to ask.\n- **What your own customers pay you.** If you use the Service to run something of your own, the money your\n users pay you is between you and them. This policy is not your refund policy.\n\n### Two kinds of customer, and the difference matters\n\nSome of what follows depends on which one you are.\n\n- **You are a consumer** if you are an individual buying for purposes wholly or mainly outside your trade,\n business, craft or profession. Consumers in the EU, the EEA and the UK have a statutory right to withdraw\n that sits on top of everything else in this policy and cannot be signed away. It has its own section\n below, and **it is the part of this document to read first**.\n- **You are a business customer** if you are buying for your organisation or for your own trade or\n profession — including as a sole trader in most cases. The statutory withdrawal right does not apply to\n you. Our voluntary guarantee still does.\n\nNothing in this policy reduces a right the law gives you and does not let you give up. Where a clause here\nwould conflict with such a right, the right wins and the rest of this policy carries on as written.\n\n## Subscriptions and renewal\n\n### How a subscription is charged\n\nSubscriptions are paid in advance. When you subscribe, you buy a term — a month, a year, or whatever\nlength your plan says — and we charge for the whole of it up front. Usage and overage charges are billed\nafter the period in which you run them up.\n\nThat single fact explains most of this policy. **You have already paid for the term you are in, and a\nrefund of it is the exception rather than the rule.**\n\n### Renewal is automatic\n\nAt the end of each term your subscription renews for another term of the same length, at the price then in\neffect for your plan, and we charge the payment method on file. This carries on until you cancel.\n\nWe give you reasonable advance notice before a price increase reaches you, and a new price never applies\npart-way through a term you have already paid for. If you do not want to pay it, cancel before the renewal\ndate.\n\n### Renewals are not refundable\n\n**A renewal charge is not covered by our 30-day money-back guarantee.** The guarantee is for a first\npurchase — see the section on it below.\n\nIf a renewal has taken you by surprise, tell us at legal@ever.co and say what happened. We cannot\npromise a refund and we will not pretend otherwise, but we would rather hear about a renewal you did not\nwant than read about it in a chargeback.\n\nTo avoid an unwanted renewal, cancel before the renewal date. Cancelling on the day the charge lands is too\nlate for that term.\n\n### One-off and perpetual purchases\n\nSome plans are a single purchase rather than a subscription — a one-time licence, a perpetual licence, or a\nbundle of credits or usage bought in advance.\n\n- There is no renewal to cancel and no recurring charge to stop.\n- **Our 30-day money-back guarantee applies to a one-off purchase in the same way it applies to a first\n subscription payment**, provided it is your first purchase.\n- Credits, allowances and usage bought in advance are not refunded once they have been used, and unused\n ones expire on whatever schedule your plan states.\n\nWhere Ever Traduora sells a plan of this kind, the product-specific section later in this policy says\nwhat it is and what happens at the end of its life.\n\n### Committed terms and signed orders\n\nIf you signed an order form or agreement with us for a fixed committed term, that document governs. A\ncommitted term is exactly that: **the fees for it are payable in full whether or not you use the Service**,\nand you cannot shorten it by cancelling part-way through. Where the order and this policy disagree, the\norder wins for that customer.\n\n## Free plans and trials\n\n### While you are on a free plan or a trial, there is nothing to refund\n\nWe have not charged you, so there is nothing to give back. If you decide the Service is not for you during\na trial, simply stop using it or cancel — you owe us nothing and you do not need a reason.\n\nThe same is true of free tiers, evaluations, proofs of concept and anything we have labelled beta, preview\nor early access. What those offerings do and do not come with is set out in our\n[Terms of Service](https://traduora.co/tos), and it is a deliberately thin set of promises.\n\n### What happens when a trial ends\n\nIf your trial is one that converts to a paid plan, we say so when you start it, we tell you the price and\nthe date, and we charge the payment method you gave us on that date unless you have cancelled first.\n\n- **Cancel before the trial ends and you are not charged.** Cancelling on the day the charge lands is too\n late.\n- **If the trial converts and that charge is your first payment to us, our 30-day money-back guarantee\n applies to it in full.** A trial does not use the guarantee up.\n- If your trial does not convert automatically, it simply expires and access stops.\n\n### Card checks are not charges\n\nSome plans ask for a payment card at the start of a trial. Where they do, your bank or card issuer may\nplace a small temporary authorisation on the card to check it is valid. **That is not a payment, we do not\nreceive it, and there is nothing for us to refund** — it drops off by itself, usually within a few days,\non your issuer's timetable rather than ours.\n\nIf an authorisation of that kind is still showing after a week, contact your card issuer. If you would like\nus to confirm what we did and did not charge, write to legal@ever.co and we will.\n\n### Your data when a trial or free plan ends\n\n**Do not put anything into a free or trial plan that you cannot afford to lose.**\n\nWhen a trial ends without converting, or a free plan is closed or withdrawn, the account and everything in\nit may be deleted. We will give you a reasonable chance to export your data where we can, but exporting in\ntime is your responsibility, and our backups are for our own operational continuity — they are not your\narchive. Our [Terms of Service](https://traduora.co/tos) set out what happens to your data when access ends.\n\n### Consumers keep their statutory rights on a paid conversion\n\nIf you are a consumer and a trial converts into a paid contract, the statutory 14-day withdrawal right\ndescribed below applies to that contract in the ordinary way. **A free period beforehand does not shorten\nit and does not use it up.**\n\n## Cancelling\n\n### How to cancel\n\nCancel from your account settings, or write to legal@ever.co from the email address on the account. We\ndo not put cancellation behind a phone call, a retention conversation or a notice period.\n\nIf you cancel by email, we treat the cancellation as made on the day we receive it, not the day we get\nround to processing it. Ask us for confirmation and we will send it.\n\n### What cancelling does\n\n**Cancelling stops the next renewal. It does not refund the term you are in.**\n\n- Your access continues until the end of the period you have already paid for, and then stops.\n- We do not pro-rate an unused part of a term on cancellation, except where our 30-day guarantee applies or\n where the law requires it.\n- Cancelling in month seven of an annual term does not produce five months back. The plan runs to the end\n of the year you paid for.\n- Usage you have already run up in the current period is still payable, even after you cancel.\n\nIf you would rather keep the remaining time than lose it, do not cancel immediately — cancellation only has\nto reach us before the renewal date to stop the next charge.\n\n### Cancelling is not deleting\n\nCancelling ends the subscription. It does not by itself delete your account, your workspace or your data,\nand it is not a request to erase your personal data. Those are separate things, and you can ask for them\nseparately.\n\nWhat happens to your data after a subscription ends, including the window in which you can still export it,\nis set out in our [Terms of Service](https://traduora.co/tos). What we do with personal data, and how to ask us\nto erase it, is in our [Privacy Policy](https://traduora.co/privacy).\n\n### Downgrading is not cancelling\n\nMoving to a cheaper plan is a plan change, not a cancellation, and it follows the rules in the section on\nupgrades and downgrades below. In particular, **a downgrade does not refund the difference for the term you\nare in.**\n\n### If we end it rather than you\n\n- **If we terminate or suspend your access because you broke the Terms or our Acceptable Use Policy, or\n because you did not pay, we do not refund the remainder of the term.** Fees for a suspended period are\n not refunded either.\n- **If we terminate without cause, or we withdraw Ever Traduora altogether, we refund the unused\n part of what you have already paid, pro rata** — counted from the day access ends to the end of the term\n you paid for. That refund is the remedy for the withdrawal itself; the limits on our liability in the\n Terms still apply to everything else.\n\nIf you are a consumer, your statutory rights on termination are unaffected by any of this.\n\n## Our 30-day money-back guarantee\n\n### The promise, in one paragraph\n\n**If you are not satisfied, you can ask for your first payment back within thirty (30) days of making it,\nand we will refund it in full.** No lengthy justification, no restocking fee, no deduction for the days you\nused. Write to legal@ever.co within the 30 days, from the email address on the account, and tell us\nwhich payment you mean.\n\nThis is something we offer voluntarily. It is not a statutory right, and it does not replace one — if you\nare a consumer, the 14-day withdrawal right described below exists as well, and you may rely on whichever\nis better for you.\n\n### It applies to a first purchase, and only to a first purchase\n\nWe want to be blunt about the limit rather than let you discover it at the wrong moment.\n\n- The guarantee covers **your first payment to us for Ever Traduora**. That may be a first\n subscription charge, a first one-off purchase, or the first charge after a trial converts.\n- **It applies once per customer.** Not once per plan, not once per workspace, and not once per year.\n- **Renewals are not covered.** Neither is any later purchase, upgrade, add-on, seat or usage charge.\n- Closing an account and opening a new one does not produce a fresh guarantee. Nor does moving between our\n products under the same billing relationship.\n\nThe 30 days run from the date of the payment itself, not from the day you signed up, the day you first\nlogged in, or the day you noticed the charge.\n\n### Annual plans\n\nAn annual plan is not treated differently, and the window is not longer because the term is.\n\n- If the annual fee was your first payment, you have the same 30 days to ask for it back, and we refund it\n in full.\n- Inside those 30 days you may instead ask us to keep your access running and refund the unused part of the\n year pro rata. Tell us which you would prefer and we will do that one.\n- **Outside those 30 days there is no pro-rata refund of the unused part of an annual term.** The plan runs\n to the end of the year you paid for and then stops.\n\n### What we do with the request\n\nWe do not ask you to prove dissatisfaction. We will usually ask one question — what went wrong — because it\nis the most useful thing anyone tells us, and you are free not to answer it.\n\nOnce we agree the refund we start it promptly, pay it to the method you used, and confirm it in writing.\nThe mechanics are in the section on how refunds are paid.\n\n### Refunds outside the guarantee\n\nSometimes the right thing to do sits outside a written rule: a duplicate charge, a plan nobody ever\nactivated, an outage that made the thing unusable for a stretch. **We may make a refund or a credit in\nthose situations at our discretion.**\n\nDoing so once does not create an entitlement, does not extend the guarantee, and does not oblige us to do\nit again in a case that looks similar to you. If you think you are in one of those situations, write to\nlegal@ever.co and put it to us plainly — that works better than a dispute with your bank.\n\n## What we do not refund\n\nSome charges are outside every refund route in this policy. They are listed here in one place so you can\nsee them before you buy rather than after.\n\n### Usage, overages and anything already consumed\n\n- **Usage and overage charges** for a period you have already used — API calls, storage, seats occupied,\n messages, minutes, jobs, exports, computation, or whatever the meter on your plan counts.\n- **Credits, allowances and prepaid units that have been spent.** Unused ones expire on the schedule your\n plan states and are not converted to cash.\n- Anything else you have already had the benefit of. Once we have supplied it, it is supplied.\n\n### Add-ons, extras and partial periods\n\n- **Optional features, add-ons and modules** you switched on, for the term in which you switched them on.\n- **Additional seats** for the period they were active. Removing a seat takes effect at your next renewal\n and does not produce a refund.\n- **Part-periods.** We bill by term. Cancelling part-way through one does not produce a refund of the\n remainder, except under the 30-day guarantee or where the law requires it.\n\n### Set-up and professional services\n\n- **Set-up, onboarding, configuration, migration, data import, training and consultancy fees**, once the\n work has been done. Where work is partly done, we refund only the part not yet performed.\n- **Custom development, bespoke integrations and anything built to your specification.** These are made for\n you and cannot be resold, so they are non-refundable once started, in proportion to the work completed.\n- Time booked and then not used, where we held the time for you and you gave us no reasonable notice.\n\n### Third-party and marketplace charges\n\n- **Anything you bought from someone else** — a reseller, partner, cloud marketplace, app store or payment\n intermediary. Your money went to them. Their refund terms apply and only they can refund you.\n- **Pass-through purchases we made on your behalf**, such as domain names, certificates, telephone numbers,\n paid third-party APIs or model provider usage, once we have paid for them ourselves.\n- Charges made to you by a third-party service you connected to Ever Traduora. We do not control\n what a connected service bills you.\n\n### Periods you could not use because of something you did\n\n- **Any period during which your access was suspended** for non-payment, for breach of our\n [Terms of Service](https://traduora.co/tos), or for breach of our Acceptable Use Policy. The subscription\n keeps running and the fees keep accruing during a suspension.\n- Time lost because you locked yourself out, misconfigured the Service, deleted your own data, or lost\n control of your own credentials.\n\n### Bank charges and currency movement\n\nFees your bank, card issuer or payment provider charges you — cross-border fees, conversion fees, transfer\ncharges — are yours. **We refund what we received, not what it cost you to send it**, and we do not\ncompensate for a movement in the exchange rate between the payment and the refund.\n\n### What this list does not do\n\nThis list does not remove your statutory rights, and it does not sit above them.\n\n**If you are a consumer exercising the 14-day withdrawal right described below, that right governs and this\nlist does not cut it down.** Nor does anything here limit our liability where the law does not permit it —\nour [Terms of Service](https://traduora.co/tos) set out exactly which liabilities we do not limit.\n\n## Upgrades, downgrades and seats\n\nPlan changes are billing events, not refund events. This section says which direction money moves in each\ncase, so nothing about it comes as a surprise.\n\n### Upgrading during a term\n\nWhen you move to a more expensive plan part-way through a term, the change takes effect immediately and we\ncharge you for the rest of that term at the new rate, less the unused part of what you already paid for the\nold plan. In other words you pay the difference for the time remaining, not the full price twice.\n\n- Your renewal date does not move unless we say so at the time.\n- **An upgrade is not a first purchase.** It does not restart the 30-day money-back guarantee, and the\n guarantee does not apply to the upgrade charge.\n- If an upgrade unlocks usage that is metered, the meter starts at the new plan's rates from the moment the\n upgrade takes effect.\n\n### Downgrading\n\nA downgrade takes effect at your next renewal, not immediately, and it is not a refund.\n\n- **You are not refunded the difference for the term you are already in.** You keep the higher plan until\n the term ends, then continue on the cheaper one.\n- We will tell you what you lose. If your account is over the new plan's limits — seats, storage, projects,\n workspaces, retention, whichever your plan meters — those limits apply once the downgrade takes effect,\n and features above them stop being available.\n- **Data above a lower plan's limits may become inaccessible, and may eventually be deleted.** Export\n anything you need before the downgrade date. We will give you notice of what is affected where we\n reasonably can, but the decision to downgrade is yours and so is the timing.\n\nIf a downgrade would cost you something you did not expect, cancel the downgrade before the renewal date\nrather than after it.\n\n### Seats\n\nWhere your plan charges per seat, per user or per licence:\n\n- **Adding a seat is charged from the day you add it for the rest of the current term**, at the rate then\n published for your plan.\n- **Removing a seat does not reduce the current term's fee and does not create a refund.** It takes effect\n at your next renewal.\n- Where seat count is derived automatically from your own directory or identity provider, **an\n administrator on your side adding a member is itself an instruction to buy a seat**, and it changes your\n bill without any further step from us. Decide who in your organisation is allowed to do that.\n\n### Moving between products or plan families\n\nMoving from one of our products to another, or between plan families that are billed differently, is\ntreated as a new purchase of the new plan and a cancellation of the old one — with the ordinary rule that\nthe old term is not refunded. It does not create a fresh 30-day guarantee.\n\nIf a migration of that kind is something we asked you to do, tell us at legal@ever.co before you do it.\nWe will not leave you paying twice for a change we initiated.\n\n## How we pay a refund\n\n### Back the way it came\n\nWe refund to the payment method that made the original payment — the same card, the same account, the same\nprovider. That is how card and bank rules work, and it is also the safest route for both of us.\n\nIf that method no longer exists — a closed account, an expired card that cannot accept a reversal, a\nprovider we no longer work with — tell us and we will agree an alternative in writing. We may ask you to\nconfirm the new details from the email address on the account before we send money to a destination that\ndid not send it to us.\n\n**We do not refund to a different person, a different company or a third-party account**, and we do not pay\nrefunds in cash, cryptocurrency or gift cards.\n\n### Timing\n\n- We start a refund within **five (5) business days** of agreeing it, and usually the same day.\n- After that it moves at your bank's or card issuer's pace. **Five to ten business days** is typical; some\n issuers take a full statement cycle to show a card refund.\n- **Where you are a consumer exercising the statutory 14-day withdrawal right, we pay within 14 days** of\n being told, as the law requires — see that section below.\n\nIf a refund we have confirmed has not reached you within fifteen (15) business days, write to\nlegal@ever.co with the confirmation and we will trace it with our payment provider.\n\n### Amount and currency\n\n- **We refund in the currency we charged**, at the amount we charged. We do not convert a refund into\n another currency on request.\n- **We never refund more than we actually received.** If the exchange rate has moved since your payment,\n the amount reaching your account may be worth more or less than it was — that is between you and your\n bank, and we do not top it up or claw it back.\n- Fees charged to you by your own bank, card issuer or intermediary — conversion, cross-border, transfer —\n are not part of what we received and are not reimbursed.\n- A partial refund is stated as a figure and an explanation on the credit note, so you can check the\n arithmetic.\n\n### Credit instead of cash\n\nWhere you would rather have account credit than money back, we can usually do that, and it is normally\nfaster. **We will only do it if you ask for it.** We do not substitute credit for a refund you are entitled\nto, and credit is never offered as a way of avoiding the statutory withdrawal right.\n\nCredit applied to your account is used against future charges, is not transferable, and is not later\nconvertible into cash.\n\n### Paperwork\n\nEvery refund produces a credit note against the original invoice, issued electronically to the billing\ncontact on the account. Keep it — it is what your own accountant and, where relevant, your tax authority\nwill want to see.\n\n## Tax on refunds\n\nOur fees are quoted exclusive of VAT, sales tax and similar charges, which are added on top where they\napply. A refund follows the same logic in reverse.\n\n### What comes back\n\n- **Where we charged you tax, we refund the tax with the fee**, in proportion to the amount refunded. A\n half refund returns half the tax.\n- **Where we charged you no tax, none comes back.** If you are a business customer in another EU member\n state and the reverse charge applied, we never held VAT on that sale, so a refund is of the net fee\n alone.\n- We issue a credit note for every refund, showing the net amount, the tax and the rate applied. That\n document, not this policy, is what your accounting needs.\n\n### Tax you accounted for yourself\n\n**If you self-assessed VAT under the reverse charge, or paid tax directly to your own authority, we cannot\ngive it back to you — we never had it.** Adjust it through your own VAT return or the equivalent filing in\nyour country, using our credit note as the supporting document. If your adviser needs anything further from\nus, ask at legal@ever.co.\n\nThe same is true of any amount you withheld or deducted at source, and of import, customs or similar\ncharges levied by a country we did not bill from.\n\n### If your tax position changed after the invoice\n\nTax is calculated on the facts as they stood when we invoiced — your billing country, your status, and the\ntax identification number you gave us at the time.\n\n- If you gave us no valid VAT identification number and we therefore charged VAT, **supplying the number\n later does not turn that charge into a refund.** It applies to invoices from the point we have it.\n- If you told us something that was wrong or out of date and we were assessed for tax as a result, that\n cost is yours, as our [Terms of Service](https://traduora.co/tos) set out.\n- Tell us promptly when your registration, place of establishment or tax status changes. It is far easier\n to bill correctly than to unpick it afterwards.\n\n### Rate changes\n\nWhere a tax rate changes between the payment and the refund, we refund the tax at the rate we actually\ncharged you — not at today's rate. That is what the credit note has to match.\n\n### Bank charges are not tax\n\nConversion fees, cross-border fees and transfer charges from your own bank are not tax, are not part of\nwhat we received, and are not refunded. They are covered in the section on how refunds are paid.\n\n## Chargebacks and payment disputes\n\n### Talk to us first\n\nIf a charge looks wrong — a duplicate, an amount you did not expect, a renewal you meant to cancel, a\npayment you do not recognise — **write to legal@ever.co before you contact your bank.** Tell us the\naccount, the date, the amount and what you think went wrong.\n\nWe can usually resolve it in a day or two. A chargeback takes weeks, is decided by people who have never\nseen your account, and often ends with a worse outcome for you than a direct refund would have. Contacting\nus costs you nothing and does not affect your right to go to your bank afterwards if we cannot sort it out.\n\n### What happens if a chargeback is raised\n\nIf you raise a chargeback, reversal or payment dispute with your bank, card issuer or payment provider\nwithout contacting us first:\n\n- **we may suspend your access to the Service while the dispute is open**, because the money for the period\n in question has been taken back and the account is, for the moment, unpaid;\n- we will respond to the dispute and **supply our evidence to the payment provider** — the invoice and\n credit notes, the record of your acceptance of our terms, the plan and dates in question, our\n correspondence with you, and the account and usage records relevant to the charge;\n- the subscription itself carries on. **A chargeback is not a cancellation.** Fees keep accruing, and if\n you want the subscription to stop you still have to cancel it in the ordinary way.\n\nIf the dispute is resolved in our favour, the amount stays due. Where the law allows, we may also recover\nthe fee our payment provider charges us for handling the dispute, and we may require a different payment\nmethod — or decline to continue serving the account — where chargebacks are repeated.\n\nIf the dispute is resolved in your favour, that is the end of it. We do not re-charge a reversed payment.\n\n### Fraud and unauthorised use\n\n**If you think someone used your card or your account without permission, tell your bank straight away, and\ntell us at legal@ever.co at the same time.** That is exactly what a chargeback is for, and none of the\nabove is aimed at you.\n\nWe will help: we can confirm what was charged, when, from where, and against which account, and we will\nclose off the access that produced it.\n\n### What this section does not do\n\n**Nothing here takes away your right to dispute a payment with your bank or card issuer.** That right comes\nfrom your agreement with them and from the law, not from us, and we cannot and do not ask you to give it\nup. We are asking you to try us first — not requiring it as a condition of anything.\n\nIf you are a consumer, your statutory withdrawal right and your statutory remedies are unaffected by this\nsection.\n\n## If you are a consumer in the EU or the UK: your 14-day right to withdraw\n\n**This is the most important section of this policy, and it is the one part of it we could not change even\nif we wanted to.**\n\nIf you are a consumer buying from us at a distance — online, by email, over the phone — the law gives you\n**fourteen (14) days to change your mind and get your money back, without giving any reason**. That right\ncomes from EU consumer law and, in the United Kingdom, from the equivalent domestic rules. It exists\nseparately from, and in addition to, our own 30-day money-back guarantee.\n\n**Nothing in this policy, in our [Terms of Service](https://traduora.co/tos), or in anything you clicked on the\nway to paying us, takes that right away.** A term that tried to would simply have no effect.\n\n### Who has it\n\nYou have it if you are an individual buying for purposes wholly or mainly outside your trade, business,\ncraft or profession.\n\n- **Business customers do not have it.** If you are buying for your organisation, or for your own trade or\n profession, this section does not apply to you — the rest of this policy does. That includes companies,\n partnerships, and in most cases sole traders buying for their business.\n- A few countries extend some consumer protections to sole traders and very small businesses. If the law\n where you live does that, it applies whatever this section says.\n- If your purchase serves both personal and business purposes, what matters is which purpose predominates.\n- If you are not sure which you are, ask us at legal@ever.co before you buy, not after.\n\n### How long you have\n\nThe 14 days run **from the day after the contract is made** — for us, the day after your order is accepted\nand your subscription or purchase is confirmed. You need only send your notice before the 14 days are up;\nit does not matter when it reaches us or when we process it.\n\n**If we never told you about this right, you get much longer.** In that case the period extends by up to\ntwelve (12) months. If we tell you late, but within those twelve months, you get 14 days from the day we\ntell you. We would rather tell you here, now, and start the clock properly.\n\n### How to exercise it\n\nAny clear statement that you are withdrawing is enough. There is no form to fill in, no reason to give, and\nno fee.\n\n- Email **legal@ever.co** and say that you are withdrawing.\n- Or write to us at **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\nSay who you are, which account or invoice you mean, and the date you bought. **Keep a copy of what you\nsent** — the burden of showing that you withdrew in time is on you, and a sent email does that neatly.\n\nWe will acknowledge your notice without delay once we receive it.\n\n### A model form, if you would rather use one\n\nYou do not have to use a form. If you prefer one, copy the following, fill it in, and send it to\nlegal@ever.co. We will also send you a copy on request.\n\n> **Notice of withdrawal**\n>\n> To Ever Technologies LTD, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — legal@ever.co\n>\n> I give notice that I withdraw from my contract for the supply of Ever Traduora.\n>\n> Ordered on: *the date of your order*\n> Name: *your name*\n> Address: *your address*\n> Account or email address the order was placed under: *your account*\n> Invoice or order reference, if you have one: *the reference*\n> Date of this notice: *today's date*\n\n### What we pay back, and when\n\nIf you withdraw in time, **we refund everything you paid us under the contract — within fourteen (14) days\nof receiving your notice.** We use the same means of payment you used, and we do not charge you a fee for\nthe refund.\n\nWe do not make you wait for a \"processing period\", we do not offer credit instead, and we do not deduct\nanything except in the one situation described next.\n\n### If you asked us to start straight away\n\nThis is the part that most people meet at checkout without noticing, so here it is in plain words.\n\nOrdinarily we would have to wait 14 days before giving you access. Almost nobody wants that. So the law\nlets you ask us to start supplying the Service immediately, during the withdrawal period — and when you\nask, two things follow, which we must tell you and you must acknowledge:\n\n- **If you withdraw after we have started but before the contract is fully performed, you still get your\n money back — minus a proportionate amount for what you actually received.** That amount is worked out\n against the total price of the contract and the share of it we had supplied by the moment you told us you\n were withdrawing. On a monthly plan used for four days, that is roughly four days' worth.\n- **If the Service has been fully performed within the 14 days, and you asked us to begin and acknowledged\n this consequence, the right to withdraw is gone.** The same applies where what you bought is digital\n content supplied other than on a physical medium and its supply has begun with your express prior consent\n and that acknowledgement.\n\nWe ask for both the request and the acknowledgement at the point of purchase, separately and in plain\nwords. **We do not pre-tick them, and we do not bury them in a longer agreement.** If you would rather not\ngive them, say so — you can wait out the 14 days instead, and we will start your access afterwards.\n\n**If we did not obtain your express request and your acknowledgement, or we did not give you the\ninformation the law requires, you pay nothing at all for what was supplied during the withdrawal period.**\nThat is the law's answer, not our concession, and we will apply it without argument.\n\n### How this fits with our 30-day guarantee\n\nThey are two different things and you do not have to choose blind.\n\n- The **statutory right** is 14 days, applies to consumers only, cannot be excluded, and can carry a\n proportionate charge for what you used if you asked us to start early.\n- The **30-day guarantee** is our own promise, applies to consumers and businesses alike, is limited to a\n first purchase, and refunds it in full with no deduction for the days you used.\n\n**Use whichever leaves you better off.** Tell us which you are relying on, or just tell us what you want\nand we will apply the one that gives you more.\n\n### Complaints, and what to do if we cannot agree\n\nWrite to legal@ever.co first. Set out what you bought, what went wrong and what you would like us to\ndo. We will give you a substantive answer, in writing, and we would much rather resolve it directly.\n\nIf that does not settle it:\n\n- **We are not currently committed to, and do not participate in, any alternative dispute resolution (ADR)\n body.** We say so because the law requires us to tell you either way. If you ask us to take a dispute to\n a particular approved ADR body, we will consider the request in good faith, case by case.\n- You can approach the **national consumer protection authority in the country where you live**, and the\n approved ADR bodies on the list that authority maintains. Those bodies are free or low-cost for\n consumers, and using one does not stop you going to court later.\n- Ever Technologies LTD is established in Bulgaria, and you may also raise a complaint with the\n consumer protection authority there.\n- **The European Commission's online dispute resolution (ODR) platform closed on 20 July 2025 and no longer\n exists.** We mention it only because older policies still link to it. Use a national body instead.\n\n**Your right to bring proceedings in the courts of the country where you live is unaffected**, as are any\nother mandatory protections the law of your own country gives you as a consumer. Our\n[Terms of Service](https://traduora.co/tos) set out the governing law and venue for everyone else.\n\n## Failed and late payments\n\n### When a charge does not go through\n\nPayments fail for ordinary reasons — an expired card, a new card number, a bank's fraud check on a\nrecurring charge, a limit reached, a card blocked for travel, a strong-authentication step nobody\ncompleted.\n\nWhen one fails:\n\n- **we email the billing contact on the account**, and keep emailing while the balance is outstanding;\n- **we retry the charge** over the following days, on a schedule set with our payment provider. A retry is\n not a second charge — if one succeeds, the others stop;\n- your access carries on for the time being. We do not cut you off at the first decline.\n\nFixing it is usually one step: update the payment method in your account settings and we will take the\noutstanding amount. If you cannot, write to legal@ever.co and we will find another way.\n\n### A failed payment does not pause or cancel anything\n\nThis is the part that catches people out, so we will say it directly.\n\n**A failed payment is not a cancellation.** The subscription keeps running, the term keeps running, and the\nfees keep accruing. If you meant to cancel, cancel — do not simply let a card expire and assume that ends\nit. Cancelling takes a minute and is described above.\n\nEqually, a failed renewal charge does not mean you have been let out of the renewal. The amount stays owed\nuntil it is paid or the subscription is properly cancelled.\n\n### Suspension\n\nIf an undisputed amount stays unpaid, **we may suspend your access — but only after written notice and at\nleast fourteen (14) days to put it right.** We will tell you what is owed, how to pay it and when the\ndeadline falls.\n\nWhile suspended:\n\n- the subscription continues and fees continue to accrue;\n- **a suspended period is not refunded and is not credited**, even after you pay;\n- your data stays where it is. Suspension is not deletion.\n\nOnce the balance is cleared we restore access promptly, normally the same business day.\n\n### Interest, costs and continued non-payment\n\nWhere an amount is overdue we may charge interest from the due date and recover the reasonable costs of\ncollecting it, on the basis set out in our [Terms of Service](https://traduora.co/tos). **If you are a\nconsumer, we will charge interest and costs only to the extent the law permits**, and the statutory regime\nfor late payment between businesses does not apply to you.\n\nContinued non-payment is a material breach, and we may terminate on that basis. Our\n[Terms of Service](https://traduora.co/tos) set out what happens to your data when a subscription ends,\nincluding the window for exporting it. **Do not leave an export until after a termination for non-payment.**\n\n### Disputing rather than not paying\n\nIf you think an invoice is wrong, say so — do not simply let the payment fail. Write to legal@ever.co\nwith the invoice, what you dispute and why, within the period our\n[Terms of Service](https://traduora.co/tos) allow for it.\n\n**Pay the part you are not disputing, on time.** A disputed line does not make the rest of the invoice\nlate, and raising a genuine dispute in good faith stops the clock on suspension for the amount in question\nwhile we work through it.\n\nIf your first move is a chargeback rather than an email, the section above on chargebacks applies.\n\n## Annex: Ever Traduora\n\n### What this policy covers for Ever Traduora\n\nThere is no hosted Ever Traduora, so there is no hosted subscription to refund. **What we sell is a\ncommercial licence for a copy you run yourself**, bought through the checkout at\n[https://ever.co/pricing](https://ever.co/pricing), and that is what this policy is about.\n\nThe section above on what this policy does not cover leaves out software you run yourself, because a copy\nof the open-source code costs you nothing. **A commercial licence is different: you paid us for it, and\nthis policy covers that payment in full** — including the 30-day money-back guarantee on a first purchase\nand, if you are a consumer, the statutory withdrawal right. Where the sections above speak of access to the\nService, for Ever Traduora read the licence you bought.\n\n### Perpetual licences\n\nThe section above on one-off and perpetual purchases promises that this part of the policy will say what a\nperpetual licence is and what happens at the end of its life. For Ever Traduora:\n\n- **A perpetual licence is charged once.** It does not renew, it is not a subscription, and there is no\n recurring charge to cancel.\n- **It does not expire.** There is no end of its life to describe.\n- Everything this policy says about a one-off purchase applies to it, including the 30-day money-back\n guarantee where it is your first purchase.\n\n### Subscriptions have no free trial\n\nA self-hosted subscription is charged when you buy it. There is no trial in front of it, so if that is\nyour first payment to us, the 30-day money-back guarantee runs from that day.\n\n### Cancelling\n\nThere is no account for Ever Traduora, so there are no account settings to cancel from. Write to\nlegal@ever.co from the address you bought with, and we will action it.\n\n## How to reach us\n\nAnything about a charge, a refund, a cancellation or an invoice — write to **legal@ever.co**. That\naddress is monitored and we answer it.\n\nTo get you an answer on the first reply rather than the third, include:\n\n- the account or workspace, and the email address it is registered to;\n- the invoice number, or the date and amount of the payment;\n- what you would like — a refund, a cancellation, a correction, or simply an explanation;\n- if you are relying on the 30-day guarantee or on the statutory withdrawal right, which one.\n\nWe acknowledge refund and withdrawal requests without undue delay. **Where you are a consumer exercising\nthe statutory 14-day withdrawal right, we pay within 14 days of your notice**, as that section requires.\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company\nnumber 204599535. We correspond in English.\n\n### If you are not happy with our answer\n\nTell us, and say so plainly — we would rather fix it than have it escalate. If we still cannot agree and\nyou are a consumer, the complaints and ADR routes in the withdrawal-right section above are open to you,\nincluding the national consumer protection authority in the country where you live. **Your right to go to\ncourt is unaffected.**\n\nComplaints about how we handle personal data go somewhere different: privacy@ever.co, and the routes in\nour [Privacy Policy](https://traduora.co/privacy).\n\n### About this document\n\nThis is version 1.0.0 of the Refund Policy for [traduora.co](https://traduora.co), in force\nfrom 2026-10-04. Earlier versions, with the dates they applied, are at\n[https://traduora.co/refund](https://traduora.co/refund).\n\nWe may change this policy. **A change never applies retrospectively to a payment you have already made**,\nand it never reduces a statutory right. Where a change matters to a term you are already in, we will tell\nyou before it takes effect."
357
357
  }
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.2",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "edda187d22d41f50486cd63f38469f1cdcac5885fe87e8e9293609ae92dee37e",
11
+ "sha256": "51308e23e18456ce860b2a292c4773c5c2d7db8dbaea9df85fc9d8c93746d1f8",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/security/010-overview",
@@ -413,5 +413,5 @@
413
413
  }
414
414
  ],
415
415
  "path": "content/security/ever-async/en.html",
416
- "markdown": "## Security overview\r\n\r\nThis page describes how we protect the Ever Async hosted service and the data you keep in it. It is written to be\r\nchecked rather than admired: every measure below is something we actually run, and where we do not do\r\nsomething that a page like this usually claims, **we say so instead of leaving a gap you have to guess at**.\r\n\r\nThe short version:\r\n\r\n- We run the Service on **hardware we own and operate ourselves**, not as a tenant in someone else's cloud.\r\n The database, the object storage and the secrets store are ours. That is why the list of providers with\r\n access to your data is short.\r\n- Traffic is encrypted in transit, storage is encrypted at rest, and off-site backup copies are encrypted\r\n **before they leave our network**, so the provider holding them holds ciphertext.\r\n- Production changes go through version control and review. Hand edits on live systems are the exception,\r\n not the routine.\r\n- **We hold no security certification, and we do not claim one.** The next section says exactly what we do\r\n instead.\r\n\r\n### What this page covers\r\n\r\nIt covers the hosted Service we operate at [async.ever.co](https://async.ever.co) — the application, its\r\ninterfaces, and the infrastructure underneath them.\r\n\r\nIt does **not** cover two things that are easy to confuse with it:\r\n\r\n- **A copy of the software you run yourself.** Where our software is published as open source and you deploy\r\n it on your own infrastructure, you are the operator. You choose its hosting, its storage and every other\r\n component, we have no access to it, and nothing on this page describes it.\r\n- **Your own systems and your own configuration.** Which of your people have access, how you configure the\r\n product, what you connect it to and how you secure the devices your team uses are yours. The shared\r\n responsibility section near the end of this page sets out that split in detail, because most real\r\n incidents happen on one side of that line rather than in the middle of it.\r\n\r\n### What this page is, legally\r\n\r\nThis is a factual description of the measures in place at the version and date shown at the end. It is\r\n**not a warranty, and it does not create a service level commitment.** Our contractual security obligations\r\nare in our Data Processing Addendum and in the [Terms of Service](https://async.ever.co/tos), and those are the\r\ndocuments that bind us.\r\n\r\nWe change these measures as the systems and the threats change. **We will not make a change that materially\r\nreduces the protection described here**, and when the description changes we republish this page with a new\r\nversion and date.\r\n\r\n### One thing we will not tell you\r\n\r\n**No system is perfectly secure, and a vendor who tells you otherwise is selling something.** Everything\r\nbelow reduces risk; none of it eliminates it. What we can commit to is that we take these measures\r\nseriously, that we test the ones that can be tested, and that when something goes wrong we tell you rather\r\nthan manage the news.\n\n## Certifications — what we hold, and what we do not\r\n\r\n**We do not hold a SOC 2 report of any type. We are not certified to ISO/IEC 27001. We hold no other\r\nsecurity certification or attestation, and we do not claim one.**\r\n\r\nWe are stating that first, in plain words, because a security page that leaves the question open is doing\r\nso on purpose. If a proposal, a sales conversation, a questionnaire response, a directory listing or a\r\nthird-party summary has told you that we are SOC 2 or ISO 27001 certified, **it is wrong** — please send it\r\nto legal@ever.co so we can get it corrected at the source.\r\n\r\n### What we do instead\r\n\r\nWe use two published control sets as a working checklist rather than as a badge:\r\n\r\n- **The control areas of ISO/IEC 27001 Annex A** — access control, cryptography, operations security,\r\n supplier relationships, incident management, continuity — as the structure for reviewing our own\r\n practices. This page is organised broadly along those lines.\r\n- **Article 32 GDPR**, which is not optional for us and is the standard our customers can actually hold us\r\n to: technical and organisational measures appropriate to the risk, kept under review as the risk changes.\r\n\r\n**No external auditor has examined either.** These are self-assessments, and you should read them as such.\r\nAn unaudited framework alignment and a certification are different things, and we will not blur the two by\r\nwriting \"aligned with\" in a way that reads like \"certified to\".\r\n\r\n### What you can have instead of a certificate\r\n\r\nA certificate is a proxy for evidence. Where we cannot give you the proxy, we will give you the evidence:\r\n\r\n- **This page**, which is specific enough to be checked against what we actually do.\r\n- **The security measures schedule in our Data Processing Addendum**, which is contractual rather than\r\n descriptive — if a measure matters to you, that is where to pin it down.\r\n- **A completed security questionnaire.** Send yours to legal@ever.co. We answer them, we answer them\r\n honestly, and where the honest answer is \"no\" you will get \"no\" rather than a paragraph that avoids the\r\n question.\r\n- **Evidence on request** for specific points — a description of the architecture, the outcome of our most\r\n recent restore test, the current sub-processor list, the transfer mechanism for a named provider.\r\n- **A right to audit**, on the terms set out in the Data Processing Addendum.\r\n\r\n### If that changes\r\n\r\nIf we obtain a certification or an independent report, this page will say which one, who issued it, what\r\nits scope covers and what it excludes — because the scope is the part that matters and the part most often\r\nleft out. Until that day, the sentence at the top of this section is the whole answer.\n\n## Encryption\r\n\r\n### In transit\r\n\r\nAll traffic between you and the Service travels over TLS. HTTPS is enforced and plain HTTP requests are\r\nredirected rather than served, so a request that arrives unencrypted never reaches the application with its\r\ncontents intact. We keep the accepted protocol versions and cipher suites current and retire weak ones as\r\nthe ecosystem does.\r\n\r\nTraffic between our own sites, and between our infrastructure and the edge network in front of it, runs\r\nover encrypted connections. Traffic to the providers we engage runs over TLS to their published endpoints.\r\n\r\n### At rest\r\n\r\n- **Storage holding customer content, databases and backups is encrypted at rest.** That protects against\r\n the loss, theft or improper disposal of physical media — it does not protect against a compromise of a\r\n running system that already has the data decrypted, and we would rather you knew which threat it answers.\r\n- **Off-site backup copies are encrypted before they leave our network**, with keys we hold and manage\r\n ourselves. The provider storing those copies holds ciphertext and nothing else: it cannot read them, and\r\n neither can anyone who obtains them from it.\r\n\r\n### At the application layer\r\n\r\nSome values are too sensitive to rely on storage-level encryption alone, so they are encrypted again inside\r\nthe application before they are written:\r\n\r\n- **Credentials, access tokens and API keys** — including tokens you grant us for a third-party integration.\r\n- **Secrets used to operate the Service** — held in a secrets manager we run ourselves, injected into\r\n workloads at runtime, and **never committed to source control**.\r\n\r\n**Passwords are never stored in a form we can read.** They are put through a modern one-way hashing\r\nfunction with a per-password salt. We cannot recover your password, tell you what it is, or send it back to\r\nyou — a reset is the only route, and any service that offers you the alternative is storing it wrongly.\r\n\r\nWhere a specific product stores a particular credential differently from the description above, its annex\r\nto this page says so and says why. **We would rather publish an awkward exception than a tidy sentence that\r\nis not true everywhere.**\r\n\r\n### Keys\r\n\r\nEncryption keys are held in our self-hosted secrets manager, separately from the data they protect, and are\r\naccessible only to the systems and people that need them. Keys are rotated when a person with access leaves,\r\nwhen we have reason to think a key has been exposed, and on a periodic schedule. **The keys for off-site\r\nbackups are held independently of the infrastructure they protect**, so that losing a site does not also\r\nlose the ability to decrypt its backups.\n\n## Access control\r\n\r\n### Your access to your own data\r\n\r\nAccess inside your workspace is yours to configure. The Service gives you named user accounts, roles and\r\npermissions, workspace administrators who can invite and remove people, and session controls. Where a\r\nproduct supports single sign-on, multi-factor authentication or IP restrictions, its annex says so and its\r\ndocumentation says how to switch them on.\r\n\r\n**Turning those controls on, and reviewing who still needs access, is your job — see the shared\r\nresponsibility section.** The most common way an account is compromised is not a flaw in our systems; it is\r\na shared password, a former employee who was never removed, or an integration token that outlived its\r\npurpose.\r\n\r\n### Our access to production systems\r\n\r\n- **Named individual accounts, never shared logins.** Every action in production is attributable to a\r\n person.\r\n- **Multi-factor authentication** on the systems and administrative accounts that support it.\r\n- **Least privilege.** Access is scoped to the narrowest role that lets the work happen, and elevated\r\n access is granted for a purpose rather than held permanently by default.\r\n- **Changes go through Git.** The configuration of the live environment is held in version control and\r\n applied automatically, so a change is reviewable, attributable and reversible. Direct hands-on changes to\r\n a running system are an exception for incidents and hands-on maintenance, not the daily routine — and the\r\n automation reverts undeclared edits rather than leaving them in place.\r\n- **Removal on departure or role change.** Access is revoked when someone leaves or no longer needs it, and\r\n credentials they held are rotated. Access is reviewed periodically as well, because revocation lists rot.\r\n\r\n### Access to your content\r\n\r\nWe access the content in your workspace only where it is necessary to operate, secure or support the\r\nService — for example to investigate a fault you have reported, or to respond to a security incident. **We\r\ndo not browse customer content, and we do not use it to build products, train models or produce insights\r\nfor anyone else.**\r\n\r\nSupport access is granted for the task in hand and logged. Where a product offers a mechanism for you to\r\ngrant or revoke support access yourself, its annex describes it.\r\n\r\n### Being honest about the limits\r\n\r\n**We are a small team, and several of us hold administrative access because operating this infrastructure\r\nrequires it.** A large organisation would separate the person who approves a change from the person who\r\nmakes it; at our size that separation is partial, and we are not going to describe it as complete. What we\r\ndo instead is make every change visible: production state comes from version control, actions are\r\nattributable to named accounts, and administrative events are logged and monitored.\n\n## Infrastructure and hosting\r\n\r\n### We run our own infrastructure\r\n\r\nThe Service does not run in a rented public cloud account. It runs on **physical servers we own, in\r\nfacilities we control, inside the European Union**, on a virtualisation and container platform we operate\r\nourselves. The database, the object storage, the message and cache layers, the secrets store and the\r\ndeployment system are all components we run — not managed services bought from a third party.\r\n\r\nThat is an unusual answer in this market, and it has a direct consequence you can verify: **the list of\r\nproviders with access to your data is short.** Most of what would otherwise be a sub-processor is simply a\r\nservice we operate.\r\n\r\nIn outline, and deliberately without the detail that would help someone attack it:\r\n\r\n- **Hardware and virtualisation we own**, clustered so that losing a machine does not lose a service.\r\n- **A container orchestration platform** running the applications, with the control plane replicated across\r\n multiple machines.\r\n- **PostgreSQL**, run by an operator that handles replication, failover and continuous archiving of the\r\n write-ahead log.\r\n- **S3-compatible object storage** we host, for files and media, with data replicated across nodes.\r\n- **A secrets manager we host**, from which credentials are injected into workloads at runtime.\r\n- **Declarative configuration held in Git** and applied automatically, so the live environment matches a\r\n reviewed commit rather than an accumulation of manual changes.\r\n\r\nA content delivery and security network sits in front of all of it, and our source code, build pipeline and\r\ncontainer registry are hosted with a third-party provider. Those are genuine third parties even though the\r\ninfrastructure behind them is ours, and they are named on our\r\n[sub-processor page](https://async.ever.co/subprocessors).\r\n\r\n### Redundancy and failure domains\r\n\r\nServices that can run on more than one machine run on more than one machine. Databases are replicated,\r\nobject storage is replicated across nodes, and the systems that hold backups run on **a physically separate\r\ncluster from the systems they protect** — so a failure that takes out the live environment does not take\r\nits backups with it.\r\n\r\n**This is not the same as multi-region redundancy, and we will not describe it as such.** We can lose\r\nmachines without losing data or availability. A whole-site failure means recovering from off-site copies,\r\nwhich is a matter of hours rather than seconds. The continuity section is specific about what that means.\r\n\r\n### Separation between customers\r\n\r\nIsolation between customers is **logical, not physical**, unless you have separately contracted for a\r\ndedicated deployment. Depending on the product that means a separate database per customer, a separate\r\nnamespace and deployment per customer site, or tenant scoping enforced in the application and the data\r\nmodel. **Your product's annex states which model applies to you** — it is a question worth asking of any\r\nvendor, and worth a straight answer.\r\n\r\n### Separation between environments\r\n\r\nDevelopment, staging and production are separate environments with separate credentials and separate data\r\nstores. Production credentials are not available in development or staging, and **we do not copy production\r\ndata into a development environment**. Test data is synthetic or anonymised.\r\n\r\n### Third-party managed services, where they are used\r\n\r\nA small number of products use a third-party managed database, managed storage or hosted platform for a\r\nspecific function rather than our own. Where that is the case it is named in that product's annex and it\r\nappears in the always-engaged tier of the sub-processor list. **We do not describe the estate as fully\r\nself-hosted where a product's data actually sits somewhere else.**\n\n## Network security\r\n\r\n### At the edge\r\n\r\nEvery request to the Service passes through a content delivery and security network before it reaches us.\r\nThat layer terminates TLS, absorbs volumetric denial-of-service traffic, applies a web application firewall\r\nand filters automated abuse. It also means the address of our origin infrastructure is not the address your\r\nbrowser connects to.\r\n\r\n### The origin is not exposed\r\n\r\n**Our application servers do not publish inbound ports to the public internet.** Traffic reaches them\r\nthrough outbound-initiated tunnels established from inside our network to the edge, so there is no\r\npublic listener to scan, and no direct path from the internet to an origin host.\r\n\r\n### Inside the network\r\n\r\n- Databases, object storage, the secrets manager and internal services sit on **segmented private networks\r\n and are not reachable from the internet**. They accept connections only from the workloads that need them.\r\n- **Administrative interfaces are not published publicly.** Reaching them requires being on the internal\r\n network, through a controlled route with authenticated access.\r\n- Outbound connectivity from workloads is limited to what the workload actually needs, so a compromised\r\n component has fewer places to send data and fewer places to fetch a second stage from.\r\n\r\n### Abuse and automation\r\n\r\nSign-up, sign-in, password reset and contact endpoints are protected against automated abuse by rate\r\nlimiting and by a bot-detection challenge. **That challenge is strictly necessary to keep the Service\r\nworking and available** — it protects accounts from credential-stuffing and forms from bulk abuse — which\r\nis why it runs without a consent prompt, as explained in our [Cookie Policy](https://async.ever.co/cookies). It\r\nis not used for analytics, profiling or advertising.\r\n\r\n### What we monitor for\r\n\r\nUnusual authentication patterns, unexpected administrative activity, sudden changes in traffic shape and\r\nfailures of the components above raise alerts that a person sees. The logging and monitoring section\r\ndescribes what is recorded and for how long.\n\n## Application security\r\n\r\n### How a change reaches production\r\n\r\nEvery change to the Service starts as a change to source code in version control and follows the same\r\nroute:\r\n\r\n1. **A pull request**, reviewed by someone other than its author on the branches that matter.\r\n2. **Automated checks** — build, tests, static analysis and dependency scanning — which must pass.\r\n3. **Promotion through environments.** Changes move development to staging to production, in that order.\r\n Production is deployed from the release branch and from nothing else.\r\n4. **A container image built by the pipeline** from a reviewed commit, identified by its digest, deployed\r\n by the same automation that holds the environment's configuration in Git.\r\n\r\n**Nobody edits production by hand as a way of shipping a change.** The deployment system reconciles the\r\nlive environment against the version-controlled definition, so an undeclared edit is reverted rather than\r\nquietly kept.\r\n\r\n### Automated checks on every change\r\n\r\n- **Dependency scanning**, with alerts for known vulnerabilities in the packages we use, and updates\r\n applied on a defined schedule with a faster path for serious issues.\r\n- **Static analysis** of our source code, run on each change, flagging the classes of defect it can find\r\n before the code ships.\r\n- **Secret scanning** across our repositories, with pushes blocked where a credential is detected. Where a\r\n credential has been exposed, we treat rotating it at the provider as the fix — deleting it from the code\r\n is not the fix.\r\n- **Automated tests**, which have to pass before a change can be merged or released.\r\n\r\nDependencies are installed through an internal package cache we run, which gives us a consistent, auditable\r\nview of what actually went into a build.\r\n\r\n### In the application itself\r\n\r\n- Database access goes through parameterised queries and a mapping layer rather than assembled strings.\r\n- Output is encoded for its context, and state-changing requests are protected against cross-site request\r\n forgery.\r\n- Authentication, session handling and password storage use established libraries rather than anything we\r\n invented; passwords are hashed as described in the encryption section.\r\n- Authorisation is enforced on the server for every request. A hidden control in the interface is not an\r\n access control.\r\n- Input is validated at the boundary, and uploads are constrained by type and size.\r\n- Browser-facing responses carry security headers, including a content security policy on the surfaces\r\n where one can be applied without breaking the product.\r\n\r\n### The honest limit\r\n\r\n**Automated tooling finds categories of defect, not all defects.** Review catches more, and neither catches\r\neverything. That is why the sections on logging, incident response and responsible disclosure exist: they\r\nare what we rely on for the bugs that get through, and something always gets through.\n\n## Testing\r\n\r\n### What we test, and how often\r\n\r\n- **Automated test suites** run on every change, in the pipeline, before anything can be merged or\r\n released.\r\n- **Static analysis and dependency scanning** run on every change as well, as described in the previous\r\n section.\r\n- **Restore tests.** We restore backups into a scratch environment and check the result against the source\r\n rather than assuming a backup that completed is a backup that works. This is the test most often skipped\r\n in the industry and the one most often needed.\r\n- **Manual review** of changes that touch authentication, authorisation, payment flows, data export or the\r\n handling of credentials — the areas where an automated check is least likely to notice that the logic is\r\n wrong.\r\n- **Configuration review** of the version-controlled definition of the live environment, which is where a\r\n surprising share of real exposure lives.\r\n\r\n### Penetration testing — what we do not have\r\n\r\n**We have not commissioned an independent penetration test of the hosted Service, and we do not claim one.\r\nThere is no test report for us to send you, and any summary suggesting otherwise is not ours.**\r\n\r\nWe would rather write that sentence than the usual formulation about \"regular security assessments\" that\r\nturns out on inspection to mean an automated scanner. When we do commission a test, this page will say who\r\nperformed it, when, what was in scope and what was excluded.\r\n\r\n### Testing the Service yourself\r\n\r\n**You may not run security testing against the Service without our written agreement** — automated\r\nscanning, load testing, fuzzing and exploitation attempts included. From our side an unannounced scan is\r\nindistinguishable from an attack, and it will be handled as one.\r\n\r\nIf you want to test, we will usually say yes. Write to legal@ever.co and we will agree the scope, the\r\nwindow, the accounts you use and how findings are reported. The conditions are the obvious ones: your own\r\ntest data only, no other customer's data touched, nothing that degrades the Service for anyone else, and\r\nfindings to us before they go anywhere else.\r\n\r\nIf you have already found something without meaning to, do not test further — go straight to the\r\nresponsible disclosure section, which is written for exactly that situation and offers you protection for\r\nit.\n\n## Logging and monitoring\r\n\r\n### What we record\r\n\r\n- **Authentication events** — sign-in, sign-out, failed attempts, password and multi-factor changes.\r\n- **Administrative and security-relevant events** — permission changes, invitations and removals, token\r\n creation and revocation, changes to workspace settings, access to production systems.\r\n- **Application programming interface access** — the request, its source, its outcome and its timing.\r\n- **Infrastructure and platform events** — deployments, configuration changes, node and service state.\r\n- **Application errors and diagnostics** — enough to work out what broke.\r\n\r\n### What we try not to record\r\n\r\nWe do not deliberately log passwords, session tokens, API keys or payment card numbers, and where such a\r\nvalue would otherwise appear in a log or an error report it is redacted. **We will not claim this is\r\nperfect** — a value can end up in a stack trace nobody predicted. When we find one, we treat it as an\r\nexposure: the credential is rotated and the log entry removed.\r\n\r\nWhere a product sends error reports to a third-party error-tracking service, that service is named in the\r\nproduct's annex and on the [sub-processor page](https://async.ever.co/subprocessors), because an error report can\r\ncarry an identifier for the person who hit the error.\r\n\r\n### How long we keep it\r\n\r\n| Log type | Retention |\r\n|---|---|\r\n| Security, access and audit logs | **12 months** |\r\n| Application and error logs, crash reports, diagnostics | **90 days** |\r\n\r\nThese are the same periods published in the retention table of our\r\n[Privacy Policy](https://async.ever.co/privacy), and if the two ever disagree the Privacy Policy governs.\r\n\r\nAccess to logs is restricted to the people whose job needs it, and log access is itself an administrative\r\nevent that gets recorded.\r\n\r\n### Monitoring and alerting\r\n\r\nMetrics from the platform, the databases, the storage layer and the applications feed a monitoring system\r\nthat raises alerts when something is wrong — a service failing, a certificate close to expiry, a backup\r\nthat did not complete, a disk filling, an unusual pattern of authentication failures. **Alerts go to people,\r\nnot to a dashboard nobody opens.**\r\n\r\nWe also run an **independent external check** that watches the Service and the monitoring system itself\r\nfrom outside our network, and raises an alarm if either goes quiet. Monitoring that cannot survive the\r\nfailure it is meant to detect is decoration, and a failed backup that alerts nobody is the standard way a\r\nrecovery turns out to be impossible.\n\n## Incident response\r\n\r\n### How we handle an incident\r\n\r\n1. **Detect and record.** An alert, a customer report or a disclosure from a researcher opens an incident,\r\n with one named person responsible for running it.\r\n2. **Assess and classify.** What happened, what is affected, whether personal data is involved, whose data,\r\n and how bad it could get. Severity drives everything that follows.\r\n3. **Contain.** Cut the access, revoke the credential, isolate the component, block the route — stopping it\r\n comes before understanding it.\r\n4. **Eradicate and recover.** Remove the cause, restore service, restore data from backup where that is\r\n what is needed, and verify the result rather than assuming it.\r\n5. **Notify.** Under the timescales below.\r\n6. **Review afterwards.** A written review of what happened, why, what we changed, and what would have\r\n caught it sooner.\r\n\r\n### Telling you about it\r\n\r\n**Where we are the controller** — for the data described in our [Privacy Policy](https://async.ever.co/privacy) as\r\nours — and there is a personal data breach that is likely to result in a risk to people:\r\n\r\n- We notify the CPDP **within 72 hours of becoming aware of it**, as\r\n Article 33 GDPR requires, and where we cannot give complete information in that window we give what we\r\n have and follow up.\r\n- We notify the affected people **without undue delay** where the breach is likely to result in a high risk\r\n to them.\r\n\r\n**Where we are your processor** — everything inside your workspace, including data your organisation\r\ncollects about its own personnel — you are the controller and the notification duty to the authority is\r\nyours, so ours is to you:\r\n\r\n- We notify you **without undue delay after we become aware, and in any event within 72 hours.**\r\n- We give you what Article 33(3) requires you to have: the nature of the breach, the categories and\r\n approximate number of people and records involved, the likely consequences, the measures we have taken or\r\n propose, and a contact point who can answer follow-up questions.\r\n- We assist you with your own notifications and with any questions from your supervisory authority. Our\r\n Data Processing Addendum sets that out contractually.\r\n\r\nWe notify you at the administrative contact addresses on your account. **Keeping those current is worth\r\nfive minutes of your time**, because a notification that reaches a mailbox nobody reads has been made and\r\nnot received.\r\n\r\n### What we will not do\r\n\r\n- **We will not sit on a breach** to work out how it looks, or wait until we have a complete picture before\r\n telling you something is wrong.\r\n- **We will not require you to sign anything** — a non-disclosure agreement, a waiver, an amended contract —\r\n as a condition of being told.\r\n- **We will not describe an incident as something else.** If data was accessed, the notice says data was\r\n accessed.\r\n\r\n### Reporting an incident to us\r\n\r\nIf you think an account has been compromised, credentials have leaked, or you have seen something in the\r\nService you should not be able to see, tell us immediately at abuse@ever.co. If personal data is\r\ninvolved, copy privacy@ever.co. Both addresses are monitored and reach the people who operate the\r\nService.\r\n\r\nIf you have found a vulnerability rather than an incident in progress, the responsible disclosure section\r\nbelow is the route, and it offers you protection that this section does not.\n\n## Continuity and backups\r\n\r\n### Three tiers, and why there are three\r\n\r\nBackups fail in three different ways — the copy is too old, the copy is on the machine that died, or the\r\ncopy is in the building that burned. So there are three tiers, each answering a different failure:\r\n\r\n- **Tier 1 — a fast local copy.** Recent database backups are staged on storage separate from the live\r\n database, on a different machine. This is the tier that answers \"somebody dropped the wrong table twenty\r\n minutes ago\" and it restores quickly because the data never left the site.\r\n- **Tier 2 — a durable on-site copy.** Everything is copied into a **private, backup-only object store that\r\n runs on a physically separate cluster from the systems it protects**, with its own credentials, reachable\r\n only from inside our network and never from the internet. Losing the cluster that runs the Service does\r\n not lose the cluster that holds its backups.\r\n- **Tier 3 — an off-site copy with a third party.** A further copy goes to object storage operated by an\r\n external provider, in a different place entirely, **encrypted before it leaves our network**. The\r\n provider stores ciphertext and holds no key. This is the tier that answers the loss of the whole site.\r\n\r\nDeliberately, **the credentials that run the Service are not the credentials that can delete its backups.**\r\n\r\n### What is backed up\r\n\r\n- **Databases** — continuous archiving of the write-ahead log for point-in-time recovery, plus periodic\r\n full backups and separate logical dumps. Two mechanisms, because they fail differently.\r\n- **Object storage** — the files and media held for you, mirrored to the backup tiers.\r\n- **Cluster and platform state**, including the configuration needed to rebuild the control plane.\r\n- **The secrets store**, snapshotted on a short cycle.\r\n- **The version-controlled configuration** that defines the environment, which is what makes a rebuild\r\n possible rather than merely theoretical.\r\n\r\n**Not backed up, on purpose:** caches and queues, which are disposable by design and reconstructed on\r\nrestart, and build artefacts that the pipeline can regenerate. Backing those up would add cost and\r\nrestore time for nothing.\r\n\r\n### Recovery objectives\r\n\r\nThese are the objectives we design and test against. **They are internal targets, not contractual\r\ncommitments** — no service level applies unless we have separately agreed one with you in writing, as the\r\n[Terms of Service](https://async.ever.co/tos) says.\r\n\r\n| Scenario | Recovery point — how much data is at risk | Recovery time — how long it takes |\r\n|---|---|---|\r\n| Loss of a machine or a service | None. Replicated components carry on | Minutes, usually without anyone noticing |\r\n| Database corruption or an unwanted change | Minutes — continuous archiving supports point-in-time recovery | Hours, depending on the size of the database |\r\n| Loss of the storage holding files | Last completed replication cycle | Hours |\r\n| **Loss of the whole site** | Last completed off-site cycle | **Hours to days.** This is the honest number |\r\n\r\n**We are candid about the last row.** We are resilient to losing machines; we are not a multi-region\r\nservice that fails over silently, and we will not describe ourselves as one.\r\n\r\n### We test restores\r\n\r\nA backup nobody has restored is a guess. We restore into a scratch environment and verify the result\r\nagainst the source — record counts, integrity checks, and whether the restored system actually starts —\r\nrather than trusting a job that reported success. Restore drills are documented, and the outcome of the\r\nmost recent one is available to customers on request at legal@ever.co.\r\n\r\nMonitoring alerts on a backup that is late, failing or stale, because **a backup system that fails silently\r\nis functionally the same as no backup system**, and is discovered at the worst possible moment.\r\n\r\n### How long backups are kept, and what deletion means\r\n\r\nEach backup ages out on its own rolling cycle, within the period given in the retention table of our\r\n[Privacy Policy](https://async.ever.co/privacy). Backups are not individually edited to remove one record — that\r\nwould defeat what a backup is for — so a deleted record persists in backup copies until that cycle\r\ncompletes. During that window the data is not used for anything, and **we do not restore a backup in order\r\nto bring back data somebody asked us to delete.** A backup is restored to recover a system, not to\r\nresurrect a record.\r\n\r\n### Your own copies\r\n\r\nWe maintain backups for our operational continuity and for the recovery obligations we owe you. **They are\r\nnot a substitute for your own copies**, and the Service provides export so that you can keep some. If your\r\nbusiness could not tolerate the loss of the data you keep with us, export it on a schedule that reflects\r\nthat.\n\n## Retention, deletion and export\r\n\r\n### Getting your data out\r\n\r\nYou can export your data while your account is open — through the product's own export function where it\r\nhas one, through the application programming interface, or by asking us. Exports are in structured,\r\nmachine-readable formats — commonly CSV and JSON, with files delivered in their original format. Your\r\nproduct's annex says which export routes exist for it.\r\n\r\nIf you need an export we do not offer as a self-service function, write to legal@ever.co and we will\r\nproduce it. **We do not charge for a reasonable export, and we do not make leaving harder than joining.**\r\n\r\n### After your agreement ends\r\n\r\nYour data remains available for export for **30 days** after the agreement ends. After that window we\r\ndelete it. The same period, and the reasoning behind it, is in the retention table of our\r\n[Privacy Policy](https://async.ever.co/privacy).\r\n\r\nIf you need longer, ask before the window closes rather than after it.\r\n\r\n### Deletion on request\r\n\r\nWhere you delete something inside the Service, or ask us to delete your workspace:\r\n\r\n- **Live systems are updated straight away.** The data is gone from the running service.\r\n- **Backup copies are not individually edited.** A deleted record persists in backups until each copy ages\r\n out on its rolling cycle, within the period stated in the Privacy Policy. During that window the data is\r\n not used for anything, and we do not restore a backup to bring it back.\r\n- **Copies held by a provider we engage** are deleted on our instruction, under the Article 28 terms in our\r\n contract with them.\r\n\r\nWhere we can keep something useful without keeping anyone identifiable — aggregate usage counts, for\r\nexample — we anonymise rather than delete, and once anonymised it is no longer personal data.\r\n\r\n### Retention you control\r\n\r\nFor data inside your workspace we are your processor, and **you set the retention period, not us**. Where a\r\nproduct lets you configure how long activity data, captured media, logs or archived records are kept, that\r\nsetting is yours and its default is documented in the annex. Choosing a period that is lawful and\r\nproportionate in your jurisdiction is part of your controller responsibility — see the shared\r\nresponsibility section.\r\n\r\nOur own retention periods, for the data where we are the controller, are published in full in the\r\n[Privacy Policy](https://async.ever.co/privacy) as a table with actual numbers rather than the phrase \"as long as\r\nnecessary\".\r\n\r\n### Legal hold\r\n\r\nWhere we are required to preserve data for a legal claim, an investigation or a regulatory request, we keep\r\nit until that ends, including any appeal period, and we do not delete it in the meantime. That obligation\r\noverrides the periods above. It applies to us; it will sometimes apply to you as well.\r\n\r\n### Disposing of hardware\r\n\r\nBecause we own our infrastructure, we also retire our own drives. Storage is encrypted at rest, and a drive\r\nis wiped, cryptographically erased or physically destroyed before it leaves our control. **A retired drive\r\nis never sold, donated or returned intact.**\n\n## Personnel\r\n\r\nWe are a small, long-standing team, and the people who build the Service are the people who operate it.\r\nThat has a security upside — nobody is administering a system they do not understand — and a limit we set\r\nout in the access control section rather than hide.\r\n\r\n**Everyone with access to production systems or customer data:**\r\n\r\n- is bound by **written confidentiality obligations that continue after their engagement ends**, whether\r\n they are an employee or a contractor;\r\n- works on a **need-to-know basis**, with access scoped to their role and granted for a purpose rather than\r\n by default;\r\n- uses **named individual accounts with multi-factor authentication**, never a shared login;\r\n- is briefed on how we expect data to be handled as part of joining, and again when something material\r\n changes;\r\n- **loses that access when they leave or when their role changes**, with the credentials they held rotated\r\n as part of the same step.\r\n\r\nContractors and anyone working on our behalf are engaged on terms at least as strict as those above. We do\r\nnot give a provider or a contractor access to customer data because it is convenient.\r\n\r\n### Devices\r\n\r\nMachines used to access production systems or customer data run full-disk encryption, lock automatically,\r\nare kept patched, and are protected by multi-factor authentication on the accounts they hold. A lost or\r\nstolen device is treated as an incident: access is revoked and credentials are rotated before anything else\r\nis decided.\r\n\r\n### Two things we do not claim\r\n\r\n- **We do not run formal background screening as a standard step**, and we are not going to describe an\r\n informal hiring process as vetting. Where your own contract or regulatory position requires screening for\r\n named individuals working on your account, tell us at legal@ever.co and we will arrange it.\r\n- **We do not run a certified annual security awareness training programme.** Security expectations are\r\n part of onboarding and part of how we review changes, but that is a practice, not a curriculum, and the\r\n two should not be confused on a page like this.\n\n## Providers and vendor management\r\n\r\n### The first question is whether we need one at all\r\n\r\nWe run our own infrastructure, and that is a security decision as much as a cost one: **a provider we do\r\nnot engage is a provider that cannot be breached on our behalf.** Before we take on a new one we ask\r\nwhether the function can be served by something we already operate. Often it can, and the answer is no\r\nprovider.\r\n\r\n### Before we engage one\r\n\r\n- **What data would it see**, and can we send it less — or none — and still get the benefit?\r\n- **What is its security posture**: its own certifications and reports, its published architecture, its\r\n breach history, how it handles vulnerability reports.\r\n- **Where does it process**, which establishment contracts with us, and which transfer mechanism applies if\r\n processing happens outside the European Economic Area.\r\n- **Will it sign a data processing agreement** meeting Article 28 GDPR, including the Standard Contractual\r\n Clauses where they are needed? If it will not, we do not engage it for anything involving personal data.\r\n- **How do we get out** — can we export what it holds, and can we replace it without rebuilding the\r\n product around its absence?\r\n\r\n### What the contract has to contain\r\n\r\nProcessing only on our documented instructions; confidentiality binding its personnel; security measures at\r\nleast as strict as our own; controls on its own sub-processors; assistance with data subject requests and\r\nwith security, breach notification and impact assessments; notification of a breach without undue delay;\r\ndeletion or return of the data when the engagement ends; and our right to the information needed to\r\ndemonstrate compliance.\r\n\r\n**A provider may not use your data for its own purposes.** Not to improve its own products, not to train\r\nmodels, not to build advertising profiles.\r\n\r\n### While it is engaged\r\n\r\nWe review the providers we use periodically, watch for security incidents and for changes in the legal\r\nbasis for transfers to them, and remove one when the feature it served is gone. A provider that is no\r\nlonger used does not stay on the list as decoration, and a provider that has been quietly replaced is a\r\nchange we announce.\r\n\r\n### How this appears to you\r\n\r\nEvery provider that processes personal data for the hosted Service is published on our\r\n[sub-processor page](https://async.ever.co/subprocessors), in three tiers: those always engaged, those engaged\r\nonly when you enable a specific feature, and those that appear only in a deployment you run yourself. That\r\npage also gives the advance notice period before we add or replace one, and the procedure for objecting.\n\n## Annex: Ever Async — what we actually run, and the default that will catch you\r\n\r\nEverything above describes the controls we operate across our range. This annex says which of them are\r\ntrue for Ever Async today, and it does not round anything up. **This is an early product**, our own\r\ndocumentation calls it an MVP, and the honest description of an MVP's security posture is shorter and less\r\nflattering than the general page.\r\n\r\n### The single most important fact: the API is writable and ships unauthenticated\r\n\r\n**`/api/v1` accepts writes, and the shipped default `auth.mode` is `local_trusted` — no credential, every\r\ncaller treated as the board principal.** Three of those routes change behaviour for an entire workspace:\r\n\r\n- **`PUT` policies** — thresholds, quiet hours and which conversations are in scope;\r\n- **`PUT` charter** — the text the product quotes back to people; and\r\n- **`POST` digest/send** — which **sends real messages to real people**, immediately.\r\n\r\n**Our own deployments set `mode = \"authenticated\"`.** That is a setting, not a property of the software.\r\nAnyone running their own copy who exposes a hostname without changing it is one request away from having\r\nthe product rewrite their charter or message their team, and no amount of network luck makes that safe.\r\nThe security documentation says this; this annex says it again because it is the finding a reader most\r\nneeds and the one most easily missed.\r\n\r\n### What is in front of the service\r\n\r\n- **TLS is terminated at our edge provider.** There is no certificate and no TLS listener in our own pods,\r\n and every request to every Ever Async hostname — the site, the dashboard, the API and the webhook\r\n ingress — passes through that edge.\r\n- **Webhook ingress is signature-verified.** Slack requests are checked against the platform signing\r\n secret and Discord interactions against their Ed25519 signature; anything that fails is rejected before\r\n the pipeline sees it.\r\n- **Events are deduplicated** on the platform's own message identifier, so a replayed or redelivered\r\n event does not produce a second nudge.\r\n\r\n### What we run behind it, without the flattering adjectives\r\n\r\n- **One replica.** The application runs as a single instance with a recreate strategy, on a durable\r\n block-storage volume in our own European Union infrastructure. **That is a single point of failure, and\r\n a restart is a short outage.** It is appropriate for an MVP and it is not a high-availability\r\n arrangement; we will not describe it as one.\r\n- **The default store is a file-backed database on that volume.** Larger deployments can be pointed at a\r\n PostgreSQL server; the hosted service is not, today.\r\n- **Backups follow the fleet chain** described in the continuity section above, with the off-site copy\r\n encrypted by us before it leaves our network.\r\n- **There are no credentials in the deployed pods today**, because every plugin block is switched off. The\r\n first workspace connection is also the first time this service holds a secret worth protecting, and the\r\n secret handling described in the general page applies from that point.\r\n\r\n### What holds tenants apart\r\n\r\nEvery primary key in the storage layer leads with a tenant column, and the same binary serves a\r\nsingle-tenant deployment and a multi-tenant one. **That is logical separation, not dedicated\r\ninfrastructure, and we will not describe it as more than it is.** The access-control and application\r\nsecurity sections above set out the controls that hold it up.\r\n\r\n### What we do not have\r\n\r\nStated plainly, because a security page that lists only what exists is a marketing document:\r\n\r\n- **No certification.** No SOC 2, no ISO 27001, no independent audit of this product.\r\n- **No third-party penetration test of Ever Async** has been performed.\r\n- **No error tracking, no crash reporting and no application performance monitoring.** That is good for\r\n privacy and it is a real gap in detection: **we do not get told when this product fails.** We rely on\r\n platform-level monitoring and on people telling us.\r\n- **No automatic retention or expiry.** Event, deduplication, nudge and context metadata persists until\r\n the tenant is deleted, as the privacy annex sets out.\r\n- **No service level.** the Ever Async hosted service is offered on the free, trial and pre-release terms in our\r\n [Terms of Service](https://async.ever.co/tos).\r\n\r\n### What data is actually at risk here, which is less than you would assume\r\n\r\nA useful thing to weigh against the above: **the database holds no chat message text.** Event rows carry\r\nidentifiers and timestamps, not bodies; the one exception is a pending nudge, which holds the original\r\nmessage for its grace window — 150 seconds in every environment we run — and then deletes it. **There is\r\nno email column anywhere in the schema**, and single sign-on identities live in memory for the session\r\nonly.\r\n\r\nSo the worst case for a compromise of the store is metadata about who posted where and when, the\r\nworkspace's charter and policy settings, the connector credentials the customer supplied, and any\r\nchat-identity-to-employee map they configured. **The credentials are the part to worry about**, and\r\nrotating them is the first thing to do in an incident.\r\n\r\n### If you run your own deployment\r\n\r\nThe shared-responsibility section above applies, and for this product it comes down to four things:\r\n\r\n1. **Set `auth.mode` before you expose anything.** Everything else on this list matters less than this.\r\n2. **Do not expose the API to the internet unless you need to.** The chat platform needs the ingress path;\r\n nothing else does.\r\n3. **Mint the narrowest connector tokens that work**, and rotate them. A token that reads a private\r\n repository gives the connector that reach and puts what it returns into a channel.\r\n4. **Decide your own retention.** The software will not age anything out for you.\r\n\r\n### Reporting something\r\n\r\nThe responsible disclosure process above covers Ever Async. If you have found something in it —\r\nincluding in a deployment somebody else runs, where we will pass it on — write to abuse@ever.co. We\r\nwould rather hear it early and awkwardly than late and publicly.\n\n## Responsible disclosure\r\n\r\nIf you have found a security vulnerability in the Service, we want to hear about it, and we would rather\r\nhear about it from you than from someone using it.\r\n\r\n### How to report\r\n\r\nSend it to **abuse@ever.co**. If personal data is exposed, copy privacy@ever.co.\r\n\r\n**We do not operate a separate security mailbox, and we are not going to publish one we do not monitor.**\r\nThat address reaches the people who operate the Service.\r\n\r\nA useful report contains: what the issue is, the exact URL, endpoint or component, the steps to reproduce\r\nit, what an attacker could actually do with it, and anything you need from us to prove it. Screenshots or a\r\nshort recording help. Write in English.\r\n\r\n### What we do with it\r\n\r\n- **We acknowledge your report within three business days.**\r\n- We assess and reproduce it, and tell you what we found — including if we conclude it is not a\r\n vulnerability, and why.\r\n- We keep you updated while we fix it, and tell you when the fix is live.\r\n- We are happy to **credit you publicly** when the fix has shipped, or to leave you out of it. Your choice.\r\n\r\nSerious issues jump the queue. We fix a critical vulnerability as quickly as we can build and verify a fix,\r\nand we will tell you what the timeline looks like rather than leaving you guessing.\r\n\r\n### Our commitment to you\r\n\r\n**If you follow the rules below, we will not pursue legal action against you, we will not report you to\r\nanyone, and we will not ask your employer to.** We will treat your research as authorised access for the\r\npurposes of computer misuse legislation and our own [Terms of Service](https://async.ever.co/tos), and we will\r\ntreat your report as a contribution rather than a threat.\r\n\r\nThis protection covers you personally. It cannot cover you against a third party — if your testing reaches\r\none of our providers' systems, that is between you and them.\r\n\r\n### The rules\r\n\r\n- **Do not access, modify, delete or download anyone else's data.** Use your own test account. If you can\r\n reach another customer's data, that is the finding — stop there and tell us. You do not need to collect\r\n it to prove it.\r\n- **Stop as soon as you have demonstrated the issue.** Do not pivot, escalate further, or establish\r\n persistence.\r\n- **No denial of service**, volumetric testing, load testing or resource exhaustion.\r\n- **No social engineering** of our people, our customers or our providers, and no physical attempts against\r\n our premises or equipment.\r\n- **No spam, no mass account creation, no brute forcing** of live accounts.\r\n- **Give us a reasonable time to fix it before you publish** — 90 days from your report, or the day the fix\r\n ships, whichever comes first. If a fix is taking longer, talk to us; we will not use the clock to bury a\r\n finding.\r\n- **Obey the law**, and do not do anything that would harm the Service or the people who use it.\r\n\r\nReports produced by running an automated scanner against the live Service are not in scope, and running one\r\nis itself a breach of the testing section above.\r\n\r\n### Usually out of scope\r\n\r\nMissing security headers or best-practice settings with no demonstrated impact; self-inflicted\r\ncross-site scripting; missing rate limits without a working attack; outdated version banners without a\r\nworking exploit; results from a vulnerability scanner submitted without validation; social engineering;\r\nand issues in a third-party service rather than ours — report those to the provider that runs it.\r\n\r\nSend it anyway if you are unsure. We would rather triage a duplicate than miss a real one.\r\n\r\n### There is no paid bounty\r\n\r\n**We do not run a paid bug bounty programme and we do not pay for vulnerability reports.** We would rather\r\nsay that plainly at the start than have you invest a weekend on the assumption that we do. What you get is\r\na fast, straight response from the people who can fix it, and public credit if you want it.\r\n\r\n### Security issues in our open-source code\r\n\r\nWhere our software is published as open source, report a security issue in the code to the same address, in\r\nprivate. **Please do not open a public issue or a pull request that describes the vulnerability** — that\r\npublishes a working exploit to everyone running the code, including people who cannot patch quickly.\n\n## Shared responsibility — who secures what\r\n\r\nSecurity of a hosted service is split between the provider and the customer, and **most real incidents\r\nhappen on the customer's side of that line**: a shared password, a departed employee who kept access, an\r\nintegration token that outlived its purpose, a laptop left on a train. That is not a criticism. It is the\r\nreason this section exists and is specific.\r\n\r\n### What we are responsible for\r\n\r\n- The physical hardware, the facilities and the virtualisation platform.\r\n- The container platform, the operating systems and the runtime the application runs on.\r\n- Patching and updating everything in the list above, and the application itself.\r\n- Encryption in transit and at rest, and the management of our keys.\r\n- Network security, the edge, and keeping the origin off the public internet.\r\n- Availability, redundancy, backups of the Service, and restoring it after a failure.\r\n- Isolation between customers.\r\n- The security of our own code, our build pipeline and our deployment process.\r\n- Our own staff: their access, their devices, their confidentiality obligations.\r\n- The providers we engage, and the contracts that bind them.\r\n- Detecting, responding to and notifying you of incidents in our part.\r\n\r\n### What you are responsible for\r\n\r\n**Who gets in, and who stays in.** Your users, their roles and their permissions. Inviting people, removing\r\nthem the day they leave, reviewing periodically who still has access, and not sharing accounts. Choosing\r\nstrong, unique passwords and turning on multi-factor authentication where the product offers it. If your\r\norganisation uses single sign-on, the security of your identity provider is yours.\r\n\r\n**How you configure the product.** Every switch we give you is a decision you are making. Defaults are\r\nchosen to be safe, not to be right for you, and changing one is a deliberate act with consequences you own.\r\n\r\n**Your monitoring configuration.** For products that can capture workforce activity, **you decide which\r\ncapture features are switched on, how often they run, and who can see the result.** We supply the controls;\r\nwhich of them is lawful and proportionate in your organisation, in your jurisdiction, is your call. The\r\nnext block is about that in more detail, because it is the sharpest edge in this document.\r\n\r\n**Your retention settings.** Where the product lets you set how long data is kept, that period is yours.\r\nKeeping data longer than you need it is a risk you are choosing to hold, and it is one of the first things\r\na supervisory authority asks about.\r\n\r\n**Your integrations and your tokens.** Every third-party service you connect, every API key you issue,\r\nevery webhook you point somewhere and every access token you grant to an application or an automated agent.\r\nApproving an integration is you deciding to send your data somewhere else. Scope those grants narrowly,\r\nreview them, and revoke them when a person leaves or a project ends — a token issued by someone who has\r\nleft your organisation still works until you revoke it.\r\n\r\n**Your devices and your endpoints.** The laptops, phones and desktops your people use to reach the Service,\r\nincluding any desktop or mobile application we publish. Full-disk encryption, screen locks, patching,\r\nmalware protection and what happens when a device is lost are yours. We cannot protect an account from a\r\ncompromised machine that is already signed into it.\r\n\r\n**Your data, and what you put in it.** What you choose to upload, whether it belongs in this product at\r\nall, and whether you have the right to process it. Also your own copies — see the backups section.\r\n\r\n**Telling your own people.** Your privacy notice to your staff, customers and site visitors is yours to\r\nwrite. Ours describes what we do; it is not your notice, and our cookie banner is not your consent\r\nmechanism.\r\n\r\n### Where you use the Service to monitor people\r\n\r\nSome of our products capture information about how an organisation's own personnel work — which can include\r\nscreenshots, application and website usage, activity rates derived from keyboard and mouse events, and,\r\nwhere you switch them on, webcam stills, audio or screen recordings.\r\n\r\nFor all of that data, **you are the controller and we are your processor.** You decide why it is collected\r\nand how; we process it on your instructions. That split has consequences you should read carefully:\r\n\r\n- **The lawful basis is yours to establish.** Consent is generally not a valid basis in an employment\r\n relationship because of the imbalance of power between employer and employee, so a signed form is\r\n unlikely to be the answer you need.\r\n- **The notice to the monitored person is yours to give**, in advance, covering each type of capture that\r\n is switched on.\r\n- **The data protection impact assessment is yours to complete** where one is required, which it commonly\r\n is for systematic monitoring of employees. We will help: ask privacy@ever.co for the information you\r\n need about data categories, capture frequencies, retention, storage locations, sub-processors and\r\n transfer mechanisms, and we will provide it.\r\n- **Consultation with a works council, trade union or employee representative body is yours to run** where\r\n local law requires it — which it does in several European countries, before the system is introduced, not\r\n after.\r\n- **Some capture types are restricted or prohibited in some countries.** Continuous screen capture in\r\n particular is treated very differently across Europe.\r\n\r\n**We make no claim that any monitoring feature is lawful for you to use, anywhere.** A feature existing in\r\nthe product is not advice that you may switch it on, and our providing it is not our assessment of your\r\nlegal position. Where you enable one, you confirm to us that you have done the work above — the Data\r\nProcessing Addendum and the [Terms of Service](https://async.ever.co/tos) put that in binding terms, including\r\nwho answers for it if it turns out not to have been done.\r\n\r\n### Where you run the software yourself\r\n\r\nIf you deploy our open-source software on your own infrastructure, **everything above is yours** — the\r\nservers, the database, the storage, the backups, the encryption, the patching, the access control and the\r\nincident response. You are the controller of the data in it. We have no access to it, we are not your\r\nprocessor for it, and no commitment on this page applies to it.\n\n## How to reach us about security\r\n\r\n- **A vulnerability you have found** — abuse@ever.co. Read the responsible disclosure section first; it\r\n tells you what protection you have and what rules go with it.\r\n- **An incident, a compromised account, or something you can see that you should not be able to see** —\r\n abuse@ever.co, immediately. Copy privacy@ever.co if personal data is involved.\r\n- **A security questionnaire, a due diligence request, a request for the Data Processing Addendum, evidence\r\n of a restore test, or permission to test the Service** — legal@ever.co.\r\n- **A question about personal data, a data subject request, or a breach affecting you** —\r\n privacy@ever.co.\r\n\r\nAll of these addresses are monitored by the people who operate the Service. By post: **Ever Technologies LTD**,\r\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number 204599535. We\r\ncorrespond in English.\r\n\r\nYou may also complain to a data protection supervisory authority. Ours is the\r\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\r\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\r\nto the authority for the country where you live or work.\r\n\r\nThis document is version 1.0.2 of the Security Overview for\r\n[async.ever.co](https://async.ever.co), in force from 2026-08-02. It describes the measures in\r\nplace at that date. Earlier versions, with the dates they applied, are at\r\n[https://async.ever.co/security](https://async.ever.co/security)."
416
+ "markdown": "## Security overview\n\nThis page describes how we protect the Ever Async hosted service and the data you keep in it. It is written to be\nchecked rather than admired: every measure below is something we actually run, and where we do not do\nsomething that a page like this usually claims, **we say so instead of leaving a gap you have to guess at**.\n\nThe short version:\n\n- We run the Service on **hardware we own and operate ourselves**, not as a tenant in someone else's cloud.\n The database, the object storage and the secrets store are ours. That is why the list of providers with\n access to your data is short.\n- Traffic is encrypted in transit, storage is encrypted at rest, and off-site backup copies are encrypted\n **before they leave our network**, so the provider holding them holds ciphertext.\n- Production changes go through version control and review. Hand edits on live systems are the exception,\n not the routine.\n- **We hold no security certification, and we do not claim one.** The next section says exactly what we do\n instead.\n\n### What this page covers\n\nIt covers the hosted Service we operate at [async.ever.co](https://async.ever.co) — the application, its\ninterfaces, and the infrastructure underneath them.\n\nIt does **not** cover two things that are easy to confuse with it:\n\n- **A copy of the software you run yourself.** Where our software is published as open source and you deploy\n it on your own infrastructure, you are the operator. You choose its hosting, its storage and every other\n component, we have no access to it, and nothing on this page describes it.\n- **Your own systems and your own configuration.** Which of your people have access, how you configure the\n product, what you connect it to and how you secure the devices your team uses are yours. The shared\n responsibility section near the end of this page sets out that split in detail, because most real\n incidents happen on one side of that line rather than in the middle of it.\n\n### What this page is, legally\n\nThis is a factual description of the measures in place at the version and date shown at the end. It is\n**not a warranty, and it does not create a service level commitment.** Our contractual security obligations\nare in our Data Processing Addendum and in the [Terms of Service](https://async.ever.co/tos), and those are the\ndocuments that bind us.\n\nWe change these measures as the systems and the threats change. **We will not make a change that materially\nreduces the protection described here**, and when the description changes we republish this page with a new\nversion and date.\n\n### One thing we will not tell you\n\n**No system is perfectly secure, and a vendor who tells you otherwise is selling something.** Everything\nbelow reduces risk; none of it eliminates it. What we can commit to is that we take these measures\nseriously, that we test the ones that can be tested, and that when something goes wrong we tell you rather\nthan manage the news.\n\n## Certifications — what we hold, and what we do not\n\n**We do not hold a SOC 2 report of any type. We are not certified to ISO/IEC 27001. We hold no other\nsecurity certification or attestation, and we do not claim one.**\n\nWe are stating that first, in plain words, because a security page that leaves the question open is doing\nso on purpose. If a proposal, a sales conversation, a questionnaire response, a directory listing or a\nthird-party summary has told you that we are SOC 2 or ISO 27001 certified, **it is wrong** — please send it\nto legal@ever.co so we can get it corrected at the source.\n\n### What we do instead\n\nWe use two published control sets as a working checklist rather than as a badge:\n\n- **The control areas of ISO/IEC 27001 Annex A** — access control, cryptography, operations security,\n supplier relationships, incident management, continuity — as the structure for reviewing our own\n practices. This page is organised broadly along those lines.\n- **Article 32 GDPR**, which is not optional for us and is the standard our customers can actually hold us\n to: technical and organisational measures appropriate to the risk, kept under review as the risk changes.\n\n**No external auditor has examined either.** These are self-assessments, and you should read them as such.\nAn unaudited framework alignment and a certification are different things, and we will not blur the two by\nwriting \"aligned with\" in a way that reads like \"certified to\".\n\n### What you can have instead of a certificate\n\nA certificate is a proxy for evidence. Where we cannot give you the proxy, we will give you the evidence:\n\n- **This page**, which is specific enough to be checked against what we actually do.\n- **The security measures schedule in our Data Processing Addendum**, which is contractual rather than\n descriptive — if a measure matters to you, that is where to pin it down.\n- **A completed security questionnaire.** Send yours to legal@ever.co. We answer them, we answer them\n honestly, and where the honest answer is \"no\" you will get \"no\" rather than a paragraph that avoids the\n question.\n- **Evidence on request** for specific points — a description of the architecture, the outcome of our most\n recent restore test, the current sub-processor list, the transfer mechanism for a named provider.\n- **A right to audit**, on the terms set out in the Data Processing Addendum.\n\n### If that changes\n\nIf we obtain a certification or an independent report, this page will say which one, who issued it, what\nits scope covers and what it excludes — because the scope is the part that matters and the part most often\nleft out. Until that day, the sentence at the top of this section is the whole answer.\n\n## Encryption\n\n### In transit\n\nAll traffic between you and the Service travels over TLS. HTTPS is enforced and plain HTTP requests are\nredirected rather than served, so a request that arrives unencrypted never reaches the application with its\ncontents intact. We keep the accepted protocol versions and cipher suites current and retire weak ones as\nthe ecosystem does.\n\nTraffic between our own sites, and between our infrastructure and the edge network in front of it, runs\nover encrypted connections. Traffic to the providers we engage runs over TLS to their published endpoints.\n\n### At rest\n\n- **Storage holding customer content, databases and backups is encrypted at rest.** That protects against\n the loss, theft or improper disposal of physical media — it does not protect against a compromise of a\n running system that already has the data decrypted, and we would rather you knew which threat it answers.\n- **Off-site backup copies are encrypted before they leave our network**, with keys we hold and manage\n ourselves. The provider storing those copies holds ciphertext and nothing else: it cannot read them, and\n neither can anyone who obtains them from it.\n\n### At the application layer\n\nSome values are too sensitive to rely on storage-level encryption alone, so they are encrypted again inside\nthe application before they are written:\n\n- **Credentials, access tokens and API keys** — including tokens you grant us for a third-party integration.\n- **Secrets used to operate the Service** — held in a secrets manager we run ourselves, injected into\n workloads at runtime, and **never committed to source control**.\n\n**Passwords are never stored in a form we can read.** They are put through a modern one-way hashing\nfunction with a per-password salt. We cannot recover your password, tell you what it is, or send it back to\nyou — a reset is the only route, and any service that offers you the alternative is storing it wrongly.\n\nWhere a specific product stores a particular credential differently from the description above, its annex\nto this page says so and says why. **We would rather publish an awkward exception than a tidy sentence that\nis not true everywhere.**\n\n### Keys\n\nEncryption keys are held in our self-hosted secrets manager, separately from the data they protect, and are\naccessible only to the systems and people that need them. Keys are rotated when a person with access leaves,\nwhen we have reason to think a key has been exposed, and on a periodic schedule. **The keys for off-site\nbackups are held independently of the infrastructure they protect**, so that losing a site does not also\nlose the ability to decrypt its backups.\n\n## Access control\n\n### Your access to your own data\n\nAccess inside your workspace is yours to configure. The Service gives you named user accounts, roles and\npermissions, workspace administrators who can invite and remove people, and session controls. Where a\nproduct supports single sign-on, multi-factor authentication or IP restrictions, its annex says so and its\ndocumentation says how to switch them on.\n\n**Turning those controls on, and reviewing who still needs access, is your job — see the shared\nresponsibility section.** The most common way an account is compromised is not a flaw in our systems; it is\na shared password, a former employee who was never removed, or an integration token that outlived its\npurpose.\n\n### Our access to production systems\n\n- **Named individual accounts, never shared logins.** Every action in production is attributable to a\n person.\n- **Multi-factor authentication** on the systems and administrative accounts that support it.\n- **Least privilege.** Access is scoped to the narrowest role that lets the work happen, and elevated\n access is granted for a purpose rather than held permanently by default.\n- **Changes go through Git.** The configuration of the live environment is held in version control and\n applied automatically, so a change is reviewable, attributable and reversible. Direct hands-on changes to\n a running system are an exception for incidents and hands-on maintenance, not the daily routine — and the\n automation reverts undeclared edits rather than leaving them in place.\n- **Removal on departure or role change.** Access is revoked when someone leaves or no longer needs it, and\n credentials they held are rotated. Access is reviewed periodically as well, because revocation lists rot.\n\n### Access to your content\n\nWe access the content in your workspace only where it is necessary to operate, secure or support the\nService — for example to investigate a fault you have reported, or to respond to a security incident. **We\ndo not browse customer content, and we do not use it to build products, train models or produce insights\nfor anyone else.**\n\nSupport access is granted for the task in hand and logged. Where a product offers a mechanism for you to\ngrant or revoke support access yourself, its annex describes it.\n\n### Being honest about the limits\n\n**We are a small team, and several of us hold administrative access because operating this infrastructure\nrequires it.** A large organisation would separate the person who approves a change from the person who\nmakes it; at our size that separation is partial, and we are not going to describe it as complete. What we\ndo instead is make every change visible: production state comes from version control, actions are\nattributable to named accounts, and administrative events are logged and monitored.\n\n## Infrastructure and hosting\n\n### We run our own infrastructure\n\nThe Service does not run in a rented public cloud account. It runs on **physical servers we own, in\nfacilities we control, inside the European Union**, on a virtualisation and container platform we operate\nourselves. The database, the object storage, the message and cache layers, the secrets store and the\ndeployment system are all components we run — not managed services bought from a third party.\n\nThat is an unusual answer in this market, and it has a direct consequence you can verify: **the list of\nproviders with access to your data is short.** Most of what would otherwise be a sub-processor is simply a\nservice we operate.\n\nIn outline, and deliberately without the detail that would help someone attack it:\n\n- **Hardware and virtualisation we own**, clustered so that losing a machine does not lose a service.\n- **A container orchestration platform** running the applications, with the control plane replicated across\n multiple machines.\n- **PostgreSQL**, run by an operator that handles replication, failover and continuous archiving of the\n write-ahead log.\n- **S3-compatible object storage** we host, for files and media, with data replicated across nodes.\n- **A secrets manager we host**, from which credentials are injected into workloads at runtime.\n- **Declarative configuration held in Git** and applied automatically, so the live environment matches a\n reviewed commit rather than an accumulation of manual changes.\n\nA content delivery and security network sits in front of all of it, and our source code, build pipeline and\ncontainer registry are hosted with a third-party provider. Those are genuine third parties even though the\ninfrastructure behind them is ours, and they are named on our\n[sub-processor page](https://async.ever.co/subprocessors).\n\n### Redundancy and failure domains\n\nServices that can run on more than one machine run on more than one machine. Databases are replicated,\nobject storage is replicated across nodes, and the systems that hold backups run on **a physically separate\ncluster from the systems they protect** — so a failure that takes out the live environment does not take\nits backups with it.\n\n**This is not the same as multi-region redundancy, and we will not describe it as such.** We can lose\nmachines without losing data or availability. A whole-site failure means recovering from off-site copies,\nwhich is a matter of hours rather than seconds. The continuity section is specific about what that means.\n\n### Separation between customers\n\nIsolation between customers is **logical, not physical**, unless you have separately contracted for a\ndedicated deployment. Depending on the product that means a separate database per customer, a separate\nnamespace and deployment per customer site, or tenant scoping enforced in the application and the data\nmodel. **Your product's annex states which model applies to you** — it is a question worth asking of any\nvendor, and worth a straight answer.\n\n### Separation between environments\n\nDevelopment, staging and production are separate environments with separate credentials and separate data\nstores. Production credentials are not available in development or staging, and **we do not copy production\ndata into a development environment**. Test data is synthetic or anonymised.\n\n### Third-party managed services, where they are used\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function rather than our own. Where that is the case it is named in that product's annex and it\nappears in the always-engaged tier of the sub-processor list. **We do not describe the estate as fully\nself-hosted where a product's data actually sits somewhere else.**\n\n## Network security\n\n### At the edge\n\nEvery request to the Service passes through a content delivery and security network before it reaches us.\nThat layer terminates TLS, absorbs volumetric denial-of-service traffic, applies a web application firewall\nand filters automated abuse. It also means the address of our origin infrastructure is not the address your\nbrowser connects to.\n\n### The origin is not exposed\n\n**Our application servers do not publish inbound ports to the public internet.** Traffic reaches them\nthrough outbound-initiated tunnels established from inside our network to the edge, so there is no\npublic listener to scan, and no direct path from the internet to an origin host.\n\n### Inside the network\n\n- Databases, object storage, the secrets manager and internal services sit on **segmented private networks\n and are not reachable from the internet**. They accept connections only from the workloads that need them.\n- **Administrative interfaces are not published publicly.** Reaching them requires being on the internal\n network, through a controlled route with authenticated access.\n- Outbound connectivity from workloads is limited to what the workload actually needs, so a compromised\n component has fewer places to send data and fewer places to fetch a second stage from.\n\n### Abuse and automation\n\nSign-up, sign-in, password reset and contact endpoints are protected against automated abuse by rate\nlimiting and by a bot-detection challenge. **That challenge is strictly necessary to keep the Service\nworking and available** — it protects accounts from credential-stuffing and forms from bulk abuse — which\nis why it runs without a consent prompt, as explained in our [Cookie Policy](https://async.ever.co/cookies). It\nis not used for analytics, profiling or advertising.\n\n### What we monitor for\n\nUnusual authentication patterns, unexpected administrative activity, sudden changes in traffic shape and\nfailures of the components above raise alerts that a person sees. The logging and monitoring section\ndescribes what is recorded and for how long.\n\n## Application security\n\n### How a change reaches production\n\nEvery change to the Service starts as a change to source code in version control and follows the same\nroute:\n\n1. **A pull request**, reviewed by someone other than its author on the branches that matter.\n2. **Automated checks** — build, tests, static analysis and dependency scanning — which must pass.\n3. **Promotion through environments.** Changes move development to staging to production, in that order.\n Production is deployed from the release branch and from nothing else.\n4. **A container image built by the pipeline** from a reviewed commit, identified by its digest, deployed\n by the same automation that holds the environment's configuration in Git.\n\n**Nobody edits production by hand as a way of shipping a change.** The deployment system reconciles the\nlive environment against the version-controlled definition, so an undeclared edit is reverted rather than\nquietly kept.\n\n### Automated checks on every change\n\n- **Dependency scanning**, with alerts for known vulnerabilities in the packages we use, and updates\n applied on a defined schedule with a faster path for serious issues.\n- **Static analysis** of our source code, run on each change, flagging the classes of defect it can find\n before the code ships.\n- **Secret scanning** across our repositories, with pushes blocked where a credential is detected. Where a\n credential has been exposed, we treat rotating it at the provider as the fix — deleting it from the code\n is not the fix.\n- **Automated tests**, which have to pass before a change can be merged or released.\n\nDependencies are installed through an internal package cache we run, which gives us a consistent, auditable\nview of what actually went into a build.\n\n### In the application itself\n\n- Database access goes through parameterised queries and a mapping layer rather than assembled strings.\n- Output is encoded for its context, and state-changing requests are protected against cross-site request\n forgery.\n- Authentication, session handling and password storage use established libraries rather than anything we\n invented; passwords are hashed as described in the encryption section.\n- Authorisation is enforced on the server for every request. A hidden control in the interface is not an\n access control.\n- Input is validated at the boundary, and uploads are constrained by type and size.\n- Browser-facing responses carry security headers, including a content security policy on the surfaces\n where one can be applied without breaking the product.\n\n### The honest limit\n\n**Automated tooling finds categories of defect, not all defects.** Review catches more, and neither catches\neverything. That is why the sections on logging, incident response and responsible disclosure exist: they\nare what we rely on for the bugs that get through, and something always gets through.\n\n## Testing\n\n### What we test, and how often\n\n- **Automated test suites** run on every change, in the pipeline, before anything can be merged or\n released.\n- **Static analysis and dependency scanning** run on every change as well, as described in the previous\n section.\n- **Restore tests.** We restore backups into a scratch environment and check the result against the source\n rather than assuming a backup that completed is a backup that works. This is the test most often skipped\n in the industry and the one most often needed.\n- **Manual review** of changes that touch authentication, authorisation, payment flows, data export or the\n handling of credentials — the areas where an automated check is least likely to notice that the logic is\n wrong.\n- **Configuration review** of the version-controlled definition of the live environment, which is where a\n surprising share of real exposure lives.\n\n### Penetration testing — what we do not have\n\n**We have not commissioned an independent penetration test of the hosted Service, and we do not claim one.\nThere is no test report for us to send you, and any summary suggesting otherwise is not ours.**\n\nWe would rather write that sentence than the usual formulation about \"regular security assessments\" that\nturns out on inspection to mean an automated scanner. When we do commission a test, this page will say who\nperformed it, when, what was in scope and what was excluded.\n\n### Testing the Service yourself\n\n**You may not run security testing against the Service without our written agreement** — automated\nscanning, load testing, fuzzing and exploitation attempts included. From our side an unannounced scan is\nindistinguishable from an attack, and it will be handled as one.\n\nIf you want to test, we will usually say yes. Write to legal@ever.co and we will agree the scope, the\nwindow, the accounts you use and how findings are reported. The conditions are the obvious ones: your own\ntest data only, no other customer's data touched, nothing that degrades the Service for anyone else, and\nfindings to us before they go anywhere else.\n\nIf you have already found something without meaning to, do not test further — go straight to the\nresponsible disclosure section, which is written for exactly that situation and offers you protection for\nit.\n\n## Logging and monitoring\n\n### What we record\n\n- **Authentication events** — sign-in, sign-out, failed attempts, password and multi-factor changes.\n- **Administrative and security-relevant events** — permission changes, invitations and removals, token\n creation and revocation, changes to workspace settings, access to production systems.\n- **Application programming interface access** — the request, its source, its outcome and its timing.\n- **Infrastructure and platform events** — deployments, configuration changes, node and service state.\n- **Application errors and diagnostics** — enough to work out what broke.\n\n### What we try not to record\n\nWe do not deliberately log passwords, session tokens, API keys or payment card numbers, and where such a\nvalue would otherwise appear in a log or an error report it is redacted. **We will not claim this is\nperfect** — a value can end up in a stack trace nobody predicted. When we find one, we treat it as an\nexposure: the credential is rotated and the log entry removed.\n\nWhere a product sends error reports to a third-party error-tracking service, that service is named in the\nproduct's annex and on the [sub-processor page](https://async.ever.co/subprocessors), because an error report can\ncarry an identifier for the person who hit the error.\n\n### How long we keep it\n\n| Log type | Retention |\n|---|---|\n| Security, access and audit logs | **12 months** |\n| Application and error logs, crash reports, diagnostics | **90 days** |\n\nThese are the same periods published in the retention table of our\n[Privacy Policy](https://async.ever.co/privacy), and if the two ever disagree the Privacy Policy governs.\n\nAccess to logs is restricted to the people whose job needs it, and log access is itself an administrative\nevent that gets recorded.\n\n### Monitoring and alerting\n\nMetrics from the platform, the databases, the storage layer and the applications feed a monitoring system\nthat raises alerts when something is wrong — a service failing, a certificate close to expiry, a backup\nthat did not complete, a disk filling, an unusual pattern of authentication failures. **Alerts go to people,\nnot to a dashboard nobody opens.**\n\nWe also run an **independent external check** that watches the Service and the monitoring system itself\nfrom outside our network, and raises an alarm if either goes quiet. Monitoring that cannot survive the\nfailure it is meant to detect is decoration, and a failed backup that alerts nobody is the standard way a\nrecovery turns out to be impossible.\n\n## Incident response\n\n### How we handle an incident\n\n1. **Detect and record.** An alert, a customer report or a disclosure from a researcher opens an incident,\n with one named person responsible for running it.\n2. **Assess and classify.** What happened, what is affected, whether personal data is involved, whose data,\n and how bad it could get. Severity drives everything that follows.\n3. **Contain.** Cut the access, revoke the credential, isolate the component, block the route — stopping it\n comes before understanding it.\n4. **Eradicate and recover.** Remove the cause, restore service, restore data from backup where that is\n what is needed, and verify the result rather than assuming it.\n5. **Notify.** Under the timescales below.\n6. **Review afterwards.** A written review of what happened, why, what we changed, and what would have\n caught it sooner.\n\n### Telling you about it\n\n**Where we are the controller** — for the data described in our [Privacy Policy](https://async.ever.co/privacy) as\nours — and there is a personal data breach that is likely to result in a risk to people:\n\n- We notify the CPDP **within 72 hours of becoming aware of it**, as\n Article 33 GDPR requires, and where we cannot give complete information in that window we give what we\n have and follow up.\n- We notify the affected people **without undue delay** where the breach is likely to result in a high risk\n to them.\n\n**Where we are your processor** — everything inside your workspace, including data your organisation\ncollects about its own personnel — you are the controller and the notification duty to the authority is\nyours, so ours is to you:\n\n- We notify you **without undue delay after we become aware, and in any event within 72 hours.**\n- We give you what Article 33(3) requires you to have: the nature of the breach, the categories and\n approximate number of people and records involved, the likely consequences, the measures we have taken or\n propose, and a contact point who can answer follow-up questions.\n- We assist you with your own notifications and with any questions from your supervisory authority. Our\n Data Processing Addendum sets that out contractually.\n\nWe notify you at the administrative contact addresses on your account. **Keeping those current is worth\nfive minutes of your time**, because a notification that reaches a mailbox nobody reads has been made and\nnot received.\n\n### What we will not do\n\n- **We will not sit on a breach** to work out how it looks, or wait until we have a complete picture before\n telling you something is wrong.\n- **We will not require you to sign anything** — a non-disclosure agreement, a waiver, an amended contract —\n as a condition of being told.\n- **We will not describe an incident as something else.** If data was accessed, the notice says data was\n accessed.\n\n### Reporting an incident to us\n\nIf you think an account has been compromised, credentials have leaked, or you have seen something in the\nService you should not be able to see, tell us immediately at abuse@ever.co. If personal data is\ninvolved, copy privacy@ever.co. Both addresses are monitored and reach the people who operate the\nService.\n\nIf you have found a vulnerability rather than an incident in progress, the responsible disclosure section\nbelow is the route, and it offers you protection that this section does not.\n\n## Continuity and backups\n\n### Three tiers, and why there are three\n\nBackups fail in three different ways — the copy is too old, the copy is on the machine that died, or the\ncopy is in the building that burned. So there are three tiers, each answering a different failure:\n\n- **Tier 1 — a fast local copy.** Recent database backups are staged on storage separate from the live\n database, on a different machine. This is the tier that answers \"somebody dropped the wrong table twenty\n minutes ago\" and it restores quickly because the data never left the site.\n- **Tier 2 — a durable on-site copy.** Everything is copied into a **private, backup-only object store that\n runs on a physically separate cluster from the systems it protects**, with its own credentials, reachable\n only from inside our network and never from the internet. Losing the cluster that runs the Service does\n not lose the cluster that holds its backups.\n- **Tier 3 — an off-site copy with a third party.** A further copy goes to object storage operated by an\n external provider, in a different place entirely, **encrypted before it leaves our network**. The\n provider stores ciphertext and holds no key. This is the tier that answers the loss of the whole site.\n\nDeliberately, **the credentials that run the Service are not the credentials that can delete its backups.**\n\n### What is backed up\n\n- **Databases** — continuous archiving of the write-ahead log for point-in-time recovery, plus periodic\n full backups and separate logical dumps. Two mechanisms, because they fail differently.\n- **Object storage** — the files and media held for you, mirrored to the backup tiers.\n- **Cluster and platform state**, including the configuration needed to rebuild the control plane.\n- **The secrets store**, snapshotted on a short cycle.\n- **The version-controlled configuration** that defines the environment, which is what makes a rebuild\n possible rather than merely theoretical.\n\n**Not backed up, on purpose:** caches and queues, which are disposable by design and reconstructed on\nrestart, and build artefacts that the pipeline can regenerate. Backing those up would add cost and\nrestore time for nothing.\n\n### Recovery objectives\n\nThese are the objectives we design and test against. **They are internal targets, not contractual\ncommitments** — no service level applies unless we have separately agreed one with you in writing, as the\n[Terms of Service](https://async.ever.co/tos) says.\n\n| Scenario | Recovery point — how much data is at risk | Recovery time — how long it takes |\n|---|---|---|\n| Loss of a machine or a service | None. Replicated components carry on | Minutes, usually without anyone noticing |\n| Database corruption or an unwanted change | Minutes — continuous archiving supports point-in-time recovery | Hours, depending on the size of the database |\n| Loss of the storage holding files | Last completed replication cycle | Hours |\n| **Loss of the whole site** | Last completed off-site cycle | **Hours to days.** This is the honest number |\n\n**We are candid about the last row.** We are resilient to losing machines; we are not a multi-region\nservice that fails over silently, and we will not describe ourselves as one.\n\n### We test restores\n\nA backup nobody has restored is a guess. We restore into a scratch environment and verify the result\nagainst the source — record counts, integrity checks, and whether the restored system actually starts —\nrather than trusting a job that reported success. Restore drills are documented, and the outcome of the\nmost recent one is available to customers on request at legal@ever.co.\n\nMonitoring alerts on a backup that is late, failing or stale, because **a backup system that fails silently\nis functionally the same as no backup system**, and is discovered at the worst possible moment.\n\n### How long backups are kept, and what deletion means\n\nEach backup ages out on its own rolling cycle, within the period given in the retention table of our\n[Privacy Policy](https://async.ever.co/privacy). Backups are not individually edited to remove one record — that\nwould defeat what a backup is for — so a deleted record persists in backup copies until that cycle\ncompletes. During that window the data is not used for anything, and **we do not restore a backup in order\nto bring back data somebody asked us to delete.** A backup is restored to recover a system, not to\nresurrect a record.\n\n### Your own copies\n\nWe maintain backups for our operational continuity and for the recovery obligations we owe you. **They are\nnot a substitute for your own copies**, and the Service provides export so that you can keep some. If your\nbusiness could not tolerate the loss of the data you keep with us, export it on a schedule that reflects\nthat.\n\n## Retention, deletion and export\n\n### Getting your data out\n\nYou can export your data while your account is open — through the product's own export function where it\nhas one, through the application programming interface, or by asking us. Exports are in structured,\nmachine-readable formats — commonly CSV and JSON, with files delivered in their original format. Your\nproduct's annex says which export routes exist for it.\n\nIf you need an export we do not offer as a self-service function, write to legal@ever.co and we will\nproduce it. **We do not charge for a reasonable export, and we do not make leaving harder than joining.**\n\n### After your agreement ends\n\nYour data remains available for export for **30 days** after the agreement ends. After that window we\ndelete it. The same period, and the reasoning behind it, is in the retention table of our\n[Privacy Policy](https://async.ever.co/privacy).\n\nIf you need longer, ask before the window closes rather than after it.\n\n### Deletion on request\n\nWhere you delete something inside the Service, or ask us to delete your workspace:\n\n- **Live systems are updated straight away.** The data is gone from the running service.\n- **Backup copies are not individually edited.** A deleted record persists in backups until each copy ages\n out on its rolling cycle, within the period stated in the Privacy Policy. During that window the data is\n not used for anything, and we do not restore a backup to bring it back.\n- **Copies held by a provider we engage** are deleted on our instruction, under the Article 28 terms in our\n contract with them.\n\nWhere we can keep something useful without keeping anyone identifiable — aggregate usage counts, for\nexample — we anonymise rather than delete, and once anonymised it is no longer personal data.\n\n### Retention you control\n\nFor data inside your workspace we are your processor, and **you set the retention period, not us**. Where a\nproduct lets you configure how long activity data, captured media, logs or archived records are kept, that\nsetting is yours and its default is documented in the annex. Choosing a period that is lawful and\nproportionate in your jurisdiction is part of your controller responsibility — see the shared\nresponsibility section.\n\nOur own retention periods, for the data where we are the controller, are published in full in the\n[Privacy Policy](https://async.ever.co/privacy) as a table with actual numbers rather than the phrase \"as long as\nnecessary\".\n\n### Legal hold\n\nWhere we are required to preserve data for a legal claim, an investigation or a regulatory request, we keep\nit until that ends, including any appeal period, and we do not delete it in the meantime. That obligation\noverrides the periods above. It applies to us; it will sometimes apply to you as well.\n\n### Disposing of hardware\n\nBecause we own our infrastructure, we also retire our own drives. Storage is encrypted at rest, and a drive\nis wiped, cryptographically erased or physically destroyed before it leaves our control. **A retired drive\nis never sold, donated or returned intact.**\n\n## Personnel\n\nWe are a small, long-standing team, and the people who build the Service are the people who operate it.\nThat has a security upside — nobody is administering a system they do not understand — and a limit we set\nout in the access control section rather than hide.\n\n**Everyone with access to production systems or customer data:**\n\n- is bound by **written confidentiality obligations that continue after their engagement ends**, whether\n they are an employee or a contractor;\n- works on a **need-to-know basis**, with access scoped to their role and granted for a purpose rather than\n by default;\n- uses **named individual accounts with multi-factor authentication**, never a shared login;\n- is briefed on how we expect data to be handled as part of joining, and again when something material\n changes;\n- **loses that access when they leave or when their role changes**, with the credentials they held rotated\n as part of the same step.\n\nContractors and anyone working on our behalf are engaged on terms at least as strict as those above. We do\nnot give a provider or a contractor access to customer data because it is convenient.\n\n### Devices\n\nMachines used to access production systems or customer data run full-disk encryption, lock automatically,\nare kept patched, and are protected by multi-factor authentication on the accounts they hold. A lost or\nstolen device is treated as an incident: access is revoked and credentials are rotated before anything else\nis decided.\n\n### Two things we do not claim\n\n- **We do not run formal background screening as a standard step**, and we are not going to describe an\n informal hiring process as vetting. Where your own contract or regulatory position requires screening for\n named individuals working on your account, tell us at legal@ever.co and we will arrange it.\n- **We do not run a certified annual security awareness training programme.** Security expectations are\n part of onboarding and part of how we review changes, but that is a practice, not a curriculum, and the\n two should not be confused on a page like this.\n\n## Providers and vendor management\n\n### The first question is whether we need one at all\n\nWe run our own infrastructure, and that is a security decision as much as a cost one: **a provider we do\nnot engage is a provider that cannot be breached on our behalf.** Before we take on a new one we ask\nwhether the function can be served by something we already operate. Often it can, and the answer is no\nprovider.\n\n### Before we engage one\n\n- **What data would it see**, and can we send it less — or none — and still get the benefit?\n- **What is its security posture**: its own certifications and reports, its published architecture, its\n breach history, how it handles vulnerability reports.\n- **Where does it process**, which establishment contracts with us, and which transfer mechanism applies if\n processing happens outside the European Economic Area.\n- **Will it sign a data processing agreement** meeting Article 28 GDPR, including the Standard Contractual\n Clauses where they are needed? If it will not, we do not engage it for anything involving personal data.\n- **How do we get out** — can we export what it holds, and can we replace it without rebuilding the\n product around its absence?\n\n### What the contract has to contain\n\nProcessing only on our documented instructions; confidentiality binding its personnel; security measures at\nleast as strict as our own; controls on its own sub-processors; assistance with data subject requests and\nwith security, breach notification and impact assessments; notification of a breach without undue delay;\ndeletion or return of the data when the engagement ends; and our right to the information needed to\ndemonstrate compliance.\n\n**A provider may not use your data for its own purposes.** Not to improve its own products, not to train\nmodels, not to build advertising profiles.\n\n### While it is engaged\n\nWe review the providers we use periodically, watch for security incidents and for changes in the legal\nbasis for transfers to them, and remove one when the feature it served is gone. A provider that is no\nlonger used does not stay on the list as decoration, and a provider that has been quietly replaced is a\nchange we announce.\n\n### How this appears to you\n\nEvery provider that processes personal data for the hosted Service is published on our\n[sub-processor page](https://async.ever.co/subprocessors), in three tiers: those always engaged, those engaged\nonly when you enable a specific feature, and those that appear only in a deployment you run yourself. That\npage also gives the advance notice period before we add or replace one, and the procedure for objecting.\n\n## Annex: Ever Async — what we actually run, and the default that will catch you\n\nEverything above describes the controls we operate across our range. This annex says which of them are\ntrue for Ever Async today, and it does not round anything up. **This is an early product**, our own\ndocumentation calls it an MVP, and the honest description of an MVP's security posture is shorter and less\nflattering than the general page.\n\n### The single most important fact: the API is writable and ships unauthenticated\n\n**`/api/v1` accepts writes, and the shipped default `auth.mode` is `local_trusted` — no credential, every\ncaller treated as the board principal.** Three of those routes change behaviour for an entire workspace:\n\n- **`PUT` policies** — thresholds, quiet hours and which conversations are in scope;\n- **`PUT` charter** — the text the product quotes back to people; and\n- **`POST` digest/send** — which **sends real messages to real people**, immediately.\n\n**Our own deployments set `mode = \"authenticated\"`.** That is a setting, not a property of the software.\nAnyone running their own copy who exposes a hostname without changing it is one request away from having\nthe product rewrite their charter or message their team, and no amount of network luck makes that safe.\nThe security documentation says this; this annex says it again because it is the finding a reader most\nneeds and the one most easily missed.\n\n### What is in front of the service\n\n- **TLS is terminated at our edge provider.** There is no certificate and no TLS listener in our own pods,\n and every request to every Ever Async hostname — the site, the dashboard, the API and the webhook\n ingress — passes through that edge.\n- **Webhook ingress is signature-verified.** Slack requests are checked against the platform signing\n secret and Discord interactions against their Ed25519 signature; anything that fails is rejected before\n the pipeline sees it.\n- **Events are deduplicated** on the platform's own message identifier, so a replayed or redelivered\n event does not produce a second nudge.\n\n### What we run behind it, without the flattering adjectives\n\n- **One replica.** The application runs as a single instance with a recreate strategy, on a durable\n block-storage volume in our own European Union infrastructure. **That is a single point of failure, and\n a restart is a short outage.** It is appropriate for an MVP and it is not a high-availability\n arrangement; we will not describe it as one.\n- **The default store is a file-backed database on that volume.** Larger deployments can be pointed at a\n PostgreSQL server; the hosted service is not, today.\n- **Backups follow the fleet chain** described in the continuity section above, with the off-site copy\n encrypted by us before it leaves our network.\n- **There are no credentials in the deployed pods today**, because every plugin block is switched off. The\n first workspace connection is also the first time this service holds a secret worth protecting, and the\n secret handling described in the general page applies from that point.\n\n### What holds tenants apart\n\nEvery primary key in the storage layer leads with a tenant column, and the same binary serves a\nsingle-tenant deployment and a multi-tenant one. **That is logical separation, not dedicated\ninfrastructure, and we will not describe it as more than it is.** The access-control and application\nsecurity sections above set out the controls that hold it up.\n\n### What we do not have\n\nStated plainly, because a security page that lists only what exists is a marketing document:\n\n- **No certification.** No SOC 2, no ISO 27001, no independent audit of this product.\n- **No third-party penetration test of Ever Async** has been performed.\n- **No error tracking, no crash reporting and no application performance monitoring.** That is good for\n privacy and it is a real gap in detection: **we do not get told when this product fails.** We rely on\n platform-level monitoring and on people telling us.\n- **No automatic retention or expiry.** Event, deduplication, nudge and context metadata persists until\n the tenant is deleted, as the privacy annex sets out.\n- **No service level.** the Ever Async hosted service is offered on the free, trial and pre-release terms in our\n [Terms of Service](https://async.ever.co/tos).\n\n### What data is actually at risk here, which is less than you would assume\n\nA useful thing to weigh against the above: **the database holds no chat message text.** Event rows carry\nidentifiers and timestamps, not bodies; the one exception is a pending nudge, which holds the original\nmessage for its grace window — 150 seconds in every environment we run — and then deletes it. **There is\nno email column anywhere in the schema**, and single sign-on identities live in memory for the session\nonly.\n\nSo the worst case for a compromise of the store is metadata about who posted where and when, the\nworkspace's charter and policy settings, the connector credentials the customer supplied, and any\nchat-identity-to-employee map they configured. **The credentials are the part to worry about**, and\nrotating them is the first thing to do in an incident.\n\n### If you run your own deployment\n\nThe shared-responsibility section above applies, and for this product it comes down to four things:\n\n1. **Set `auth.mode` before you expose anything.** Everything else on this list matters less than this.\n2. **Do not expose the API to the internet unless you need to.** The chat platform needs the ingress path;\n nothing else does.\n3. **Mint the narrowest connector tokens that work**, and rotate them. A token that reads a private\n repository gives the connector that reach and puts what it returns into a channel.\n4. **Decide your own retention.** The software will not age anything out for you.\n\n### Reporting something\n\nThe responsible disclosure process above covers Ever Async. If you have found something in it —\nincluding in a deployment somebody else runs, where we will pass it on — write to abuse@ever.co. We\nwould rather hear it early and awkwardly than late and publicly.\n\n## Responsible disclosure\n\nIf you have found a security vulnerability in the Service, we want to hear about it, and we would rather\nhear about it from you than from someone using it.\n\n### How to report\n\nSend it to **abuse@ever.co**. If personal data is exposed, copy privacy@ever.co.\n\n**We do not operate a separate security mailbox, and we are not going to publish one we do not monitor.**\nThat address reaches the people who operate the Service.\n\nA useful report contains: what the issue is, the exact URL, endpoint or component, the steps to reproduce\nit, what an attacker could actually do with it, and anything you need from us to prove it. Screenshots or a\nshort recording help. Write in English.\n\n### What we do with it\n\n- **We acknowledge your report within three business days.**\n- We assess and reproduce it, and tell you what we found — including if we conclude it is not a\n vulnerability, and why.\n- We keep you updated while we fix it, and tell you when the fix is live.\n- We are happy to **credit you publicly** when the fix has shipped, or to leave you out of it. Your choice.\n\nSerious issues jump the queue. We fix a critical vulnerability as quickly as we can build and verify a fix,\nand we will tell you what the timeline looks like rather than leaving you guessing.\n\n### Our commitment to you\n\n**If you follow the rules below, we will not pursue legal action against you, we will not report you to\nanyone, and we will not ask your employer to.** We will treat your research as authorised access for the\npurposes of computer misuse legislation and our own [Terms of Service](https://async.ever.co/tos), and we will\ntreat your report as a contribution rather than a threat.\n\nThis protection covers you personally. It cannot cover you against a third party — if your testing reaches\none of our providers' systems, that is between you and them.\n\n### The rules\n\n- **Do not access, modify, delete or download anyone else's data.** Use your own test account. If you can\n reach another customer's data, that is the finding — stop there and tell us. You do not need to collect\n it to prove it.\n- **Stop as soon as you have demonstrated the issue.** Do not pivot, escalate further, or establish\n persistence.\n- **No denial of service**, volumetric testing, load testing or resource exhaustion.\n- **No social engineering** of our people, our customers or our providers, and no physical attempts against\n our premises or equipment.\n- **No spam, no mass account creation, no brute forcing** of live accounts.\n- **Give us a reasonable time to fix it before you publish** — 90 days from your report, or the day the fix\n ships, whichever comes first. If a fix is taking longer, talk to us; we will not use the clock to bury a\n finding.\n- **Obey the law**, and do not do anything that would harm the Service or the people who use it.\n\nReports produced by running an automated scanner against the live Service are not in scope, and running one\nis itself a breach of the testing section above.\n\n### Usually out of scope\n\nMissing security headers or best-practice settings with no demonstrated impact; self-inflicted\ncross-site scripting; missing rate limits without a working attack; outdated version banners without a\nworking exploit; results from a vulnerability scanner submitted without validation; social engineering;\nand issues in a third-party service rather than ours — report those to the provider that runs it.\n\nSend it anyway if you are unsure. We would rather triage a duplicate than miss a real one.\n\n### There is no paid bounty\n\n**We do not run a paid bug bounty programme and we do not pay for vulnerability reports.** We would rather\nsay that plainly at the start than have you invest a weekend on the assumption that we do. What you get is\na fast, straight response from the people who can fix it, and public credit if you want it.\n\n### Security issues in our open-source code\n\nWhere our software is published as open source, report a security issue in the code to the same address, in\nprivate. **Please do not open a public issue or a pull request that describes the vulnerability** — that\npublishes a working exploit to everyone running the code, including people who cannot patch quickly.\n\n## Shared responsibility — who secures what\n\nSecurity of a hosted service is split between the provider and the customer, and **most real incidents\nhappen on the customer's side of that line**: a shared password, a departed employee who kept access, an\nintegration token that outlived its purpose, a laptop left on a train. That is not a criticism. It is the\nreason this section exists and is specific.\n\n### What we are responsible for\n\n- The physical hardware, the facilities and the virtualisation platform.\n- The container platform, the operating systems and the runtime the application runs on.\n- Patching and updating everything in the list above, and the application itself.\n- Encryption in transit and at rest, and the management of our keys.\n- Network security, the edge, and keeping the origin off the public internet.\n- Availability, redundancy, backups of the Service, and restoring it after a failure.\n- Isolation between customers.\n- The security of our own code, our build pipeline and our deployment process.\n- Our own staff: their access, their devices, their confidentiality obligations.\n- The providers we engage, and the contracts that bind them.\n- Detecting, responding to and notifying you of incidents in our part.\n\n### What you are responsible for\n\n**Who gets in, and who stays in.** Your users, their roles and their permissions. Inviting people, removing\nthem the day they leave, reviewing periodically who still has access, and not sharing accounts. Choosing\nstrong, unique passwords and turning on multi-factor authentication where the product offers it. If your\norganisation uses single sign-on, the security of your identity provider is yours.\n\n**How you configure the product.** Every switch we give you is a decision you are making. Defaults are\nchosen to be safe, not to be right for you, and changing one is a deliberate act with consequences you own.\n\n**Your monitoring configuration.** For products that can capture workforce activity, **you decide which\ncapture features are switched on, how often they run, and who can see the result.** We supply the controls;\nwhich of them is lawful and proportionate in your organisation, in your jurisdiction, is your call. The\nnext block is about that in more detail, because it is the sharpest edge in this document.\n\n**Your retention settings.** Where the product lets you set how long data is kept, that period is yours.\nKeeping data longer than you need it is a risk you are choosing to hold, and it is one of the first things\na supervisory authority asks about.\n\n**Your integrations and your tokens.** Every third-party service you connect, every API key you issue,\nevery webhook you point somewhere and every access token you grant to an application or an automated agent.\nApproving an integration is you deciding to send your data somewhere else. Scope those grants narrowly,\nreview them, and revoke them when a person leaves or a project ends — a token issued by someone who has\nleft your organisation still works until you revoke it.\n\n**Your devices and your endpoints.** The laptops, phones and desktops your people use to reach the Service,\nincluding any desktop or mobile application we publish. Full-disk encryption, screen locks, patching,\nmalware protection and what happens when a device is lost are yours. We cannot protect an account from a\ncompromised machine that is already signed into it.\n\n**Your data, and what you put in it.** What you choose to upload, whether it belongs in this product at\nall, and whether you have the right to process it. Also your own copies — see the backups section.\n\n**Telling your own people.** Your privacy notice to your staff, customers and site visitors is yours to\nwrite. Ours describes what we do; it is not your notice, and our cookie banner is not your consent\nmechanism.\n\n### Where you use the Service to monitor people\n\nSome of our products capture information about how an organisation's own personnel work — which can include\nscreenshots, application and website usage, activity rates derived from keyboard and mouse events, and,\nwhere you switch them on, webcam stills, audio or screen recordings.\n\nFor all of that data, **you are the controller and we are your processor.** You decide why it is collected\nand how; we process it on your instructions. That split has consequences you should read carefully:\n\n- **The lawful basis is yours to establish.** Consent is generally not a valid basis in an employment\n relationship because of the imbalance of power between employer and employee, so a signed form is\n unlikely to be the answer you need.\n- **The notice to the monitored person is yours to give**, in advance, covering each type of capture that\n is switched on.\n- **The data protection impact assessment is yours to complete** where one is required, which it commonly\n is for systematic monitoring of employees. We will help: ask privacy@ever.co for the information you\n need about data categories, capture frequencies, retention, storage locations, sub-processors and\n transfer mechanisms, and we will provide it.\n- **Consultation with a works council, trade union or employee representative body is yours to run** where\n local law requires it — which it does in several European countries, before the system is introduced, not\n after.\n- **Some capture types are restricted or prohibited in some countries.** Continuous screen capture in\n particular is treated very differently across Europe.\n\n**We make no claim that any monitoring feature is lawful for you to use, anywhere.** A feature existing in\nthe product is not advice that you may switch it on, and our providing it is not our assessment of your\nlegal position. Where you enable one, you confirm to us that you have done the work above — the Data\nProcessing Addendum and the [Terms of Service](https://async.ever.co/tos) put that in binding terms, including\nwho answers for it if it turns out not to have been done.\n\n### Where you run the software yourself\n\nIf you deploy our open-source software on your own infrastructure, **everything above is yours** — the\nservers, the database, the storage, the backups, the encryption, the patching, the access control and the\nincident response. You are the controller of the data in it. We have no access to it, we are not your\nprocessor for it, and no commitment on this page applies to it.\n\n## How to reach us about security\n\n- **A vulnerability you have found** — abuse@ever.co. Read the responsible disclosure section first; it\n tells you what protection you have and what rules go with it.\n- **An incident, a compromised account, or something you can see that you should not be able to see** —\n abuse@ever.co, immediately. Copy privacy@ever.co if personal data is involved.\n- **A security questionnaire, a due diligence request, a request for the Data Processing Addendum, evidence\n of a restore test, or permission to test the Service** — legal@ever.co.\n- **A question about personal data, a data subject request, or a breach affecting you** —\n privacy@ever.co.\n\nAll of these addresses are monitored by the people who operate the Service. By post: **Ever Technologies LTD**,\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number 204599535. We\ncorrespond in English.\n\nYou may also complain to a data protection supervisory authority. Ours is the\nCommission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at\n[https://www.cpdp.bg/](https://www.cpdp.bg/). You may instead complain\nto the authority for the country where you live or work.\n\nThis document is version 1.0.2 of the Security Overview for\n[async.ever.co](https://async.ever.co), in force from 2026-08-02. It describes the measures in\nplace at that date. Earlier versions, with the dates they applied, are at\n[https://async.ever.co/security](https://async.ever.co/security)."
417
417
  }