@ever-co/legal 0.3.0 → 0.4.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.
- package/dist/content/refund/githands/en.html +32 -36
- package/dist/content/refund/githands/en.json +13 -9
- package/dist/content/refund/hust/en.html +16 -3
- package/dist/content/refund/hust/en.json +21 -4
- package/dist/content/subprocessors/githands/en.html +3 -3
- package/dist/content/subprocessors/githands/en.json +4 -4
- package/dist/content/tos/ever-rec/en.html +14 -10
- package/dist/content/tos/ever-rec/en.json +4 -4
- package/dist/content/tos/githands/en.html +59 -23
- package/dist/content/tos/githands/en.json +6 -6
- package/dist/content/tos/hust/en.html +22 -11
- package/dist/content/tos/hust/en.json +5 -5
- package/dist/index.json +47 -26
- package/package.json +1 -1
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0
|
|
10
|
-
"effectiveDate": "2026-
|
|
11
|
-
"sha256": "
|
|
9
|
+
"version": "1.1.0",
|
|
10
|
+
"effectiveDate": "2026-10-05",
|
|
11
|
+
"sha256": "678f205fdef99134d27e7d077be40da26d3d68f580c23b482e96d2a033570327",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/refund/010-scope",
|
|
@@ -23,6 +23,7 @@
|
|
|
23
23
|
"core/refund/100-chargebacks",
|
|
24
24
|
"core/refund/110-eu-consumer-withdrawal-right",
|
|
25
25
|
"core/refund/120-failed-payments",
|
|
26
|
+
"@annex/refund",
|
|
26
27
|
"core/refund/900-contact"
|
|
27
28
|
],
|
|
28
29
|
"headings": [
|
|
@@ -318,6 +319,22 @@
|
|
|
318
319
|
"level": 3,
|
|
319
320
|
"text": "Disputing rather than not paying"
|
|
320
321
|
},
|
|
322
|
+
{
|
|
323
|
+
"level": 2,
|
|
324
|
+
"text": "Annex: Ever Hust"
|
|
325
|
+
},
|
|
326
|
+
{
|
|
327
|
+
"level": 3,
|
|
328
|
+
"text": "A self-hosted plan is covered, even though you run the software yourself"
|
|
329
|
+
},
|
|
330
|
+
{
|
|
331
|
+
"level": 3,
|
|
332
|
+
"text": "The free trial is for Cloud plans only"
|
|
333
|
+
},
|
|
334
|
+
{
|
|
335
|
+
"level": 3,
|
|
336
|
+
"text": "The free tier"
|
|
337
|
+
},
|
|
321
338
|
{
|
|
322
339
|
"level": 2,
|
|
323
340
|
"text": "How to reach us"
|
|
@@ -332,5 +349,5 @@
|
|
|
332
349
|
}
|
|
333
350
|
],
|
|
334
351
|
"path": "content/refund/hust/en.html",
|
|
335
|
-
"markdown": "# Refund Policy\n\n**Ever Hust** — [hust.so](https://hust.so)\n\nVersion 1.0.2 · In force from 2026-08-02\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 the Ever Hust hosted service — 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://hust.so/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://hust.so/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 Hust 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://hust.so/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://hust.so/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://hust.so/tos). What we do with personal data, and how to ask us\nto erase it, is in our [Privacy Policy](https://hust.so/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 the Ever Hust hosted service 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 the Ever Hust hosted service**. 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 the Ever Hust hosted service. 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://hust.so/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://hust.so/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://hust.so/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://hust.so/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 the Ever Hust hosted service.\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://hust.so/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://hust.so/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://hust.so/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://hust.so/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## 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://hust.so/privacy).\n\n### About this document\n\nThis is version 1.0.2 of the Refund Policy for [hust.so](https://hust.so), in force\nfrom 2026-08-02. Earlier versions, with the dates they applied, are at\n[https://hust.so/refund](https://hust.so/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."
|
|
352
|
+
"markdown": "# Refund Policy\n\n**Ever Hust** — [hust.so](https://hust.so)\n\nVersion 1.1.0 · In force from 2026-10-05\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 the Ever Hust hosted service — 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://hust.so/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://hust.so/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 Hust 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://hust.so/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://hust.so/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://hust.so/tos). What we do with personal data, and how to ask us\nto erase it, is in our [Privacy Policy](https://hust.so/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 the Ever Hust hosted service 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 the Ever Hust hosted service**. 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 the Ever Hust hosted service. 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://hust.so/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://hust.so/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://hust.so/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://hust.so/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 the Ever Hust hosted service.\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://hust.so/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://hust.so/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://hust.so/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://hust.so/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 Hust\n\n### A self-hosted plan is covered, even though you run the software yourself\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 self-hosted plan is different: it is a commercial licence\nyou paid us for, and this policy covers that payment in full** — including the 30-day money-back guarantee\non a first purchase and, if you are a consumer, the statutory withdrawal right.\n\n### The free trial is for Cloud plans only\n\nA paid Cloud plan begins with the free trial described in the section on free plans and trials above. **A\nself-hosted subscription has no trial: it is charged when you buy it**, and if that is your first payment\nto us, the 30-day money-back guarantee runs from that day.\n\n### The free tier\n\nthe Ever Hust hosted service has a free tier that stays free. You pay nothing for it, so there is nothing to\nrefund, and nothing in this policy starts charging you for 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://hust.so/privacy).\n\n### About this document\n\nThis is version 1.1.0 of the Refund Policy for [hust.so](https://hust.so), in force\nfrom 2026-10-05. Earlier versions, with the dates they applied, are at\n[https://hust.so/refund](https://hust.so/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."
|
|
336
353
|
}
|
|
@@ -340,7 +340,7 @@ site, their notice applies.</li>
|
|
|
340
340
|
</tr>
|
|
341
341
|
<tr>
|
|
342
342
|
<td>Stripe, Inc.</td>
|
|
343
|
-
<td>Payments and subscription billing
|
|
343
|
+
<td>Payments and subscription billing for paid plans, engaged when you buy one. The free plan never reaches it, and we never receive your full card number.</td>
|
|
344
344
|
<td>United States</td>
|
|
345
345
|
<td>Standard Contractual Clauses (EU 2021/914)</td>
|
|
346
346
|
<td>billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history</td>
|
|
@@ -897,7 +897,7 @@ and mark the letter for the attention of the privacy team. We correspond in Engl
|
|
|
897
897
|
Commission for Personal Data Protection (Комисия за защита на личните данни), the CPDP, at
|
|
898
898
|
<a href="https://www.cpdp.bg/">https://www.cpdp.bg/</a>. You may instead complain
|
|
899
899
|
to the authority for the country where you live or work.</p>
|
|
900
|
-
<p>This document is version 1.0
|
|
901
|
-
<a href="https://githands.com">githands.com</a>, in force from 2026-
|
|
900
|
+
<p>This document is version 1.1.0 of the sub-processor list for
|
|
901
|
+
<a href="https://githands.com">githands.com</a>, in force from 2026-10-05. It lists the providers engaged
|
|
902
902
|
as at that date. Earlier versions, with the dates they applied, are at
|
|
903
903
|
<a href="https://githands.com/subprocessors">https://githands.com/subprocessors</a>.</p>
|
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0
|
|
10
|
-
"effectiveDate": "2026-
|
|
11
|
-
"sha256": "
|
|
9
|
+
"version": "1.1.0",
|
|
10
|
+
"effectiveDate": "2026-10-05",
|
|
11
|
+
"sha256": "68b126b4c9c1a76291033485edca95524a04c918a7842055994fbb573a4ad614",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/subprocessors/010-purpose",
|
|
@@ -154,5 +154,5 @@
|
|
|
154
154
|
}
|
|
155
155
|
],
|
|
156
156
|
"path": "content/subprocessors/githands/en.html",
|
|
157
|
-
"markdown": "## Why this page exists\n\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://githands.com/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [githands.com](https://githands.com), for GitHands\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://githands.com/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where a provider contracts through a European establishment but processes\n elsewhere, this column says both, because the two are different facts and only naming the first would\n flatter us.\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\n tier the transfer is not ours at all — you choose the provider and hold the contract.\n The general rules behind this column are in the international transfers section of our\n [Privacy Policy](https://githands.com/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### Why this list is deliberately longer than it needs to be\n\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\npurpose already described here, it appears in the tables below — even if no data has reached it this\nmonth, and even where we currently run the equivalent ourselves.\n\nWe do this on purpose, and you should read the tables with it in mind:\n\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\n tells you when it is engaged.\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\n covered by a disclosure you have already seen rather than by a fresh surprise.\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\n ordinary operational change, which is what makes it dependable.\n\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\nand to the notice period below — not something the width of a table quietly absorbs.\n\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\nmay be, ask us at privacy@ever.co and we will tell you.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://githands.com/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: GitHands\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | Standard Contractual Clauses (EU 2021/914) | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | To be confirmed — we do not yet evidence a mechanism | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | None needed — established in the EEA | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. d/b/a Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | None — we run this ourselves in the EU | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | Not published by the provider | To be confirmed — we do not yet evidence a mechanism | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n| Cloudflare, Inc. (R2 object storage) | Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network. | United States | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold |\n| Google Ireland Limited (Google Workspace) | Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs. | Ireland (contracting) / United States and global (Google LLC) | Standard Contractual Clauses (EU 2021/914) | all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments |\n| Cloudflare, Inc. (Turnstile) | Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie |\n| Clerk, Inc. | Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name. | United States | Standard Contractual Clauses (EU 2021/914) | name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain. | United States | To be confirmed — we do not yet evidence a mechanism | search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata |\n| Prospect One sp. z o.o. (jsDelivr) | Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating. | Poland (operator); delivery worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified | Second permitted origin for the Lottie animation runtime on the ever-works login and register pages. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\n| Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting. | Handles subscription billing and invoicing for the hosted Gauzy service. | United States / Netherlands | To be confirmed — we do not yet evidence a mechanism | billing identity and address, plan, invoice and payment history |\n| Shopify International Limited | Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records. | Ireland (contracting) / Canada and United States (Shopify group) | Standard Contractual Clauses (EU 2021/914) | customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States | Standard Contractual Clauses (EU 2021/914) | contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | Standard Contractual Clauses (EU 2021/914) | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | Standard Contractual Clauses (EU 2021/914) | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing. **Not engaged today** — the hosted Service is free, no payment method is collected and nothing is charged. Stripe becomes a sub-processor only if and when paid plans are switched on, and we will give notice before that happens. | United States | Standard Contractual Clauses (EU 2021/914) | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio Inc. (SendGrid) | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign, LLC (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Google Ireland Limited (Sign in with Google) | Authenticates a user who chooses 'sign in with Google', returning their email, name and picture, and in ever-rec also exports recordings to the user's own Google Drive when they connect it. | Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | email address, name and profile picture, Google account identifier, OAuth access and refresh tokens, Google Drive file metadata and content the user chooses to export, where the Drive scope is granted (ever-rec) |\n| Zapier, Inc. | Forwards workspace records into whatever third-party apps a customer wires into a Zap, so the onward destinations are the customer's choice and outside our contract. | United States | Standard Contractual Clauses (EU 2021/914) | records pushed through a Zap (tasks, timesheets, contacts), OAuth tokens and authorization codes, arbitrary event payloads forwarded to whatever apps the customer wires up |\n| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| Google Ireland Limited (Google Analytics 4 and Google Tag Manager) | Measures marketing-site and, on some properties, in-application usage through the GA4 tag loaded via Tag Manager, keyed to a persistent client-id cookie. | Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address (anonymize_ip is set on some sites, not all), _ga / _gid / _gat cookies (GA client identifier), page URLs, referrer and UTM parameters, device, browser and approximate location, conversion events, tied to a user id on gauzy.co |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Receives OpenTelemetry traces from the API where Honeycomb is selected as the OTEL provider, including request URLs and database statements that routinely carry identifiers. | United States | Standard Contractual Clauses (EU 2021/914) | trace and span data including request URLs, route parameters and DB statements, service and host identifiers, anything a span attribute carries, which can include user and tenant ids |\n| SigNoz Inc. (Delaware, USA) for SigNoz Cloud; SigNoz itself is Apache-2.0 and self-hostable. | Receives OpenTelemetry traces, metrics and logs from the API wherever the OTLP endpoint is configured, including route parameters and SQL text. | United States | To be confirmed — we do not yet evidence a mechanism | distributed traces including HTTP routes, query strings and SQL statements, service and host metadata, metrics and logs, anything attached as a span attribute |\n| Better Stack, s.r.o. | Receives shipped application logs where a log token is configured, including the ChatGPT connector service in ever-teams and the cloc platform's observability pipeline. | Czech Republic | None needed — established in the EEA | application log lines, which may embed user ids, request paths and IP addresses, uptime probe results |\n| OpenAI, L.L.C. | Generates completions and transcribes audio for in-application AI features, using either a platform-held key (cloc) or a key the customer supplies (gauzy, ever-works, ever-teams, hust). | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, including workspace records, job posts, candidate and employee profile text, issue and task text and chat messages, audio submitted for transcription, model responses, OAuth device-auth identity for the Codex CLI plugin |\n| Anthropic, PBC | Generates completions for in-application AI features - the default model in hust, a plugin or bring-your-own-key option in gauzy and ever-works. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, which can include workspace data the user pastes or references, model responses |\n| Google Ireland Limited (Gemini API) | Generates completions for the in-application AI assistant where a customer connects a Gemini key, through the AI Studio endpoint rather than Vertex AI. | Ireland (contracting entity); processing in United States (AI Studio) / Ireland (Vertex AI) | Standard Contractual Clauses (EU 2021/914) | prompt content, which can carry workspace, HR and candidate data, model responses |\n| Mistral AI SAS | Generates completions where the Mistral plugin is enabled for a Work. | France | None needed — established in the EEA | prompt text, completions |\n| X.AI LLC | Generates completions where a customer selects Grok and supplies a key. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Groq, Inc. | Serves completions where a user supplies a Groq key and selects it as the provider. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Together Computer, Inc. (trading as Together AI) | Serves completions where a user selects Together as the provider and supplies a key, called from our own Next.js server route. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, including chat message text, model responses |\n| Vercel Inc. | Routes AI prompts from the Gauzy assistant to whichever downstream model provider the customer's selected model resolves to. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, model responses, request routing and usage metadata |\n| Intuition Machines, Inc. (hCaptcha) | Scores signup and login attempts wherever the CAPTCHA provider is set to hCaptcha. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and browser/device fingerprint signals, mouse, touch and timing interaction signals, challenge solution and token |\n| Meta Platforms Ireland Limited (Facebook Login) | Authenticates a user who chooses to sign in with Facebook, returning their email, name and profile picture. | Ireland (contracting entity); processing in Ireland (contracting for EEA users) / United States (Meta Platforms, Inc.) | Standard Contractual Clauses (EU 2021/914) | email address and name, Facebook user identifier, profile picture URL, OAuth tokens |\n| X Corp. (Twitter) | Authenticates a user who chooses to sign in with X, where that provider is enabled for the deployment. | United States | To be confirmed — we do not yet evidence a mechanism | handle and public profile, X user identifier, OAuth tokens |\n| Microsoft Corporation (Microsoft Entra ID) | Authenticates a user or administrator who chooses a Microsoft work or personal account, reading profile details from Microsoft Graph, where FEATURE_MICROSOFT_LOGIN is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | email address and display name, Microsoft tenant identifier and user object id, OAuth access and refresh tokens, directory profile fields returned by Graph within the granted scope |\n| Okta, Inc. (Auth0) | Authenticates an organisation's people where that organisation chooses to route sign-in through its own hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | email address and profile, OAuth/OIDC tokens, login IP address, device and user agent, authentication and MFA event logs |\n| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Atlassian Pty Ltd (Jira, Trello) | Syncs tasks, issues and attachments with a Jira or Trello site the customer connects using its own account. | Australia (Atlassian Pty Ltd) / Netherlands (Atlassian B.V.) / United States (Atlassian, Inc.) | Standard Contractual Clauses (EU 2021/914) | issue, project, card and board records, reporter and assignee identity, attachments, screenshots and recordings pushed to an issue, API key and OAuth tokens |\n| Activepieces Inc. | Runs automation flows that read and receive whatever workspace records a customer wires in, on Activepieces' US cloud unless repointed at a self-hosted instance. | United States / Canada | Standard Contractual Clauses (EU 2021/914) | records pushed through a flow, which can be any workspace data, API keys, webhook payloads |\n| Celonis SE (Make.com) | Runs automation scenarios that read and receive whatever workspace records the customer wires in, from EU infrastructure. | Germany / Czech Republic | None needed — established in the EEA | records pushed through a scenario, webhook payloads, OAuth tokens |\n| Noti-Fire Apps Ltd. (Novu) | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | Israel | Adequacy decision — Israel | a hashed subscriber identifier, computed server-side under NOVU_SECRET_KEY, notification content, email address where Novu is used as a delivery channel |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | Estonia | None needed — established in the EEA | page views and referrer, coarse device and country, derived and not stored as an IP address |\n| Chatwoot Inc. | Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context. | United States | Standard Contractual Clauses (EU 2021/914) | visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Algolia SAS | Answers the search box on the documentation sites, receiving each reader's query and IP where Algolia credentials are configured. | France (EEA) or United States, depending on the contracting entity and the index region | To be confirmed — we do not yet evidence a mechanism | search queries typed by the reader, IP address, user agent, indexed page content |\n| Google Ireland Limited (Google Maps Platform) | Renders maps and completes typed addresses for contacts, clients and organisations where the Maps and Places features are enabled with an API key. | Ireland (contracting entity); processing in Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address, typed address fragments and place queries, latitude and longitude of contacts, clients and organisations, session tokens for autocomplete billing |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record where the Work Owner connects it, so the Work Owner contracts with it directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing address and tax location, payment identifiers and purchase history, card data entered on Lemon Squeezy's own hosted checkout and never reaching us |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors, connected and contracted by the Work Owner. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing and tax location, payment identifiers and subscription history, card data entered on Polar's own hosted checkout and never reaching us |\n| SolidGate | A further card payment option for a Work site's own visitors, where the Work Owner enables it and contracts with the payment institution directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Cyprus (EEA) | None needed — established in the EEA | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run GitHands on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | Not our transfer — you choose the provider | recipient email addresses and names, message content, delivery and engagement events |\n| The Rocket Science Group LLC d/b/a Mailchimp | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | Not our transfer — you choose the provider | prompts and completions, including any personal data your installation puts in them |\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | Not our transfer — you choose the provider | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | Not our transfer — you choose the provider | all application data in your installation |\n| The Rocket Science Group LLC d/b/a Mailchimp | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | Not our transfer — you choose the provider | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | Not our transfer — you choose the provider | stored agent conversation memory, which can contain customer and developer details |\n| none in a self-hosted deployment - the reader (or we) runs the runtime. Ollama Inc. (US) publishes the software and would become a processor only if a hosted Ollama service were adopted. | Runs open-weight models inside the deployment itself, so prompts reach no third party at all. | n/a (self-hosted); United States for Ollama Inc. | Not our transfer — you choose the provider | chat and prompt text, which never leaves the deployment |\n| Red Hat, Inc. (Keycloak) | Authenticates users through a Keycloak realm that the organisation running the deployment operates itself. | United States (Red Hat, Inc.) / wherever the reader runs the realm | Not our transfer — you choose the provider | email address and profile, OIDC tokens |\n| Mixpanel, Inc. | Records in-app screens and named events - 'Order Delivered' from the courier application, 'Order Failed' from the merchant tablet and similar - against a device identifier, where the operator configures a Mixpanel token and publishes a build containing it. | United States | Not our transfer — you choose the provider | device identifier, screens viewed and in-app events, IP address, user identifier once the person has signed in, the Mixpanel project token, which is compiled into the distributed binary |\n| Intercom, Inc. | Runs the in-application support conversation in the shopping, merchant and courier mobile applications through cordova-plugin-intercom / @ionic-native/intercom, where the operator supplies Intercom credentials. | United States (Intercom, Inc.) / Ireland (Intercom R&D Unlimited Company) | Not our transfer — you choose the provider | user identifier and email address, full support conversation content, device and application context, the operator's Intercom app id and API key |\n\n### Data about developers who are not our users\n\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\nabove process that data on our instructions in the same way as any other — but two points follow that a\nplain table does not convey.\n\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\n may be done with it afterwards.\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\n acts on our instructions under a written contract.\n\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://githands.com/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://githands.com/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for GitHands, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://githands.com/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://githands.com/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://githands.com/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond 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 sub-processor list for\n[githands.com](https://githands.com), in force from 2026-08-02. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://githands.com/subprocessors](https://githands.com/subprocessors)."
|
|
157
|
+
"markdown": "## Why this page exists\n\nWhen you use GitHands Cloud to process personal data, we act as your processor and you are the\ncontroller. Article 28 GDPR says we may not bring in another processor without your authorisation, and that\nyou must be told in advance when we intend to add or replace one so that you have a real chance to object.\n\n**This page is that disclosure.** It names every provider we engage to process personal data for the hosted\nService, says what each one does, where it does it, and what categories of data reach it. Our Data\nProcessing Addendum refers to this page, and your general authorisation to the providers listed here is\ngiven through it.\n\nIt is also written for people who are not our customers — someone whose employer uses the Service, or\nwhose data ends up here for some other reason — because \"who else can see this\" is a fair question and the\nanswer should not be available only to the person paying the invoice.\n\n### What counts as a sub-processor\n\nA **sub-processor** is a third party we engage that processes personal data **on our behalf and on our\ninstructions**, under a written contract meeting Article 28 GDPR. A provider that keeps the servers running,\ndelivers your email, catches our errors or answers your support chat is a sub-processor.\n\nThree things are not sub-processors, and lumping them in would make this page less accurate rather than\nmore complete:\n\n- **A provider that never touches personal data.** A design tool or an accounting package we use internally\n is not in the path of your data.\n- **A company that decides its own purposes.** A payment processor acting on its own regulated obligations\n — fraud prevention, anti-money-laundering, card-scheme rules — is a controller in its own right for that\n part, not our processor. Those recipients are described in the\n [Privacy Policy](https://githands.com/privacy) instead.\n- **Something we run ourselves.** Our databases, object storage, secrets manager and container platform are\n ours. There is no third party to disclose. The infrastructure section below explains what we operate and\n what genuinely sits in front of it.\n\n### What this page covers\n\nThe **hosted Service we operate** at [githands.com](https://githands.com), for GitHands\nspecifically. Other products in our range have their own list on their own domain, and the providers differ\nbetween them — do not read this one as covering a product it does not name.\n\n**It does not cover a deployment you run yourself.** If you install our open-source software on your own\ninfrastructure, you choose your own providers with your own credentials and contracts. The third tier below\nexists to make that distinction visible rather than to blur it.\n\nThis page is versioned and dated. The version in force, and the date it took effect, are at the end.\n\n## How to read this list\n\nThe three tables that follow mean genuinely different things, and reading them as one flat list will give\nyou the wrong answer.\n\nHere is why the split exists. Our products are open-source at their core and built to be connected to other\nthings, so **more than 160 distinct third-party providers appear somewhere in our source code across our\nwhole range of products.** The overwhelming majority of them are never engaged by us for anything. Some are\noptional integrations that do nothing until somebody switches them on. Many are reachable only in a\ndeployment that somebody else runs, with their own account and their own credentials.\n\nPublishing all of them as \"our sub-processors\" would be inaccurate, and inaccurate in the worst direction:\nit would tell you your data reaches companies it never touches, while burying the handful that it actually\ndoes. **A list that is technically exhaustive and practically misleading is not a disclosure.** So there are\nthree tiers.\n\n### Tier 1 — always engaged\n\n**If you use the hosted Service, these providers are in the path.** There is no setting that removes them,\nbecause they are part of how the Service is delivered to everyone.\n\nThis is the real Article 28 sub-processor list. It is the tier to use when you are completing a data\nprotection impact assessment, mapping your transfers, or deciding whether you can use the Service at all.\nIt is short, and it is short because we run our own infrastructure rather than renting someone else's.\n\n### Tier 2 — engaged only if you turn something on\n\n**A provider in this tier is engaged only when a specific feature, connector or integration is enabled.**\nEnable nothing and it is never involved, and no data of yours ever reaches it.\n\nWho does the enabling depends on the feature:\n\n- **You or your workspace administrator**, by switching on a feature or connecting an account in the\n product's settings — a payment provider, an analytics tool, a chat widget, a calendar or repository\n connector.\n- **An individual user**, by making a personal choice — signing in with a social account, for example, or\n connecting their own third-party tool.\n\nThe table names the feature or setting that activates each provider, so you can check your own\nconfiguration against it rather than take our word for the current state. If you want to know precisely\nwhich of these are live for your workspace today, ask us at privacy@ever.co and we will tell you.\n\n**Enabling one of these is a decision to send your data somewhere else**, and it is yours to make. The\nprovider's own terms and privacy notice then apply to what it does, alongside our contract with it.\n\n### Tier 3 — self-hosted deployments only\n\nSeveral of our products are published as open source and can be run on your own infrastructure. When you do\nthat, **you** choose the database, the object storage, the email relay, the AI provider and everything else,\nusing your own accounts and your own credentials.\n\nThe providers in this tier are listed **only so that you can see what the software can be pointed at**.\nThey are not our sub-processors, and they never become ours by appearing here.\n\n**In a deployment you run: we process nothing, we have no access to it, we are not your processor for it,\nand nothing on this page or in our Data Processing Addendum describes it.** You choose those providers, you\ncontract with them, you hold the credentials, and the obligations to your own users are yours alone. The\nopen-source section of our [Terms of Service](https://githands.com/tos) sets out the same split.\n\nIf you run a deployment yourself and need to publish a sub-processor list of your own, this tier is a\nuseful starting inventory. It is not your list — only you know which of these you actually configured.\n\n### What the columns mean\n\n- **Sub-processor** — the contracting legal entity, not the brand on the website. Where a provider has a\n separate European establishment that contracts with us, that is the one named.\n- **Purpose** — what it does for the Service, specifically enough to be checked. Not \"business operations\".\n- **Location** — where the processing takes place, or the provider's place of establishment where\n processing is distributed. Where a provider contracts through a European establishment but processes\n elsewhere, this column says both, because the two are different facts and only naming the first would\n flatter us.\n- **Transfer mechanism** — for a provider outside the European Economic Area, the Chapter V instrument we\n actually rely on for that specific provider: an adequacy decision, the Standard Contractual Clauses, or\n nothing yet. **Where it reads \"To be confirmed\", we have not yet evidenced an instrument for that\n provider, and we would rather say so here than print one we cannot produce.** That is a live piece of\n work, not a formula. Providers established inside the EEA need no mechanism and say so. For the third\n tier the transfer is not ours at all — you choose the provider and hold the contract.\n The general rules behind this column are in the international transfers section of our\n [Privacy Policy](https://githands.com/privacy), and we will give you a copy of the safeguards for a named\n provider on request.\n- **Personal data** — the categories that reach that provider. Categories, not a promise about volume: a\n provider that receives email addresses receives them for the people who trigger the feature, not for\n everyone.\n\n### Why this list is deliberately longer than it needs to be\n\n**We list providers we may engage, not only the ones engaged today.** Where we have configured a\nprovider, kept one available behind a feature flag, used one recently, or expect to use one for a\npurpose already described here, it appears in the tables below — even if no data has reached it this\nmonth, and even where we currently run the equivalent ourselves.\n\nWe do this on purpose, and you should read the tables with it in mind:\n\n- **A provider appearing here is not proof that your data has reached it.** It means the provider is\n within the scope of what we have told you we may do, at the tier shown. The tier is the part that\n tells you when it is engaged.\n- **Where we self-host something today** — our analytics, our job runner, our databases, our object\n storage — we say so, and we also name the hosted service we would move to, so that a later change is\n covered by a disclosure you have already seen rather than by a fresh surprise.\n- **The alternative is worse.** A list that names only today's exact set has to be re-issued, and\n re-consented, every time an engineer changes a setting. A list drawn slightly wide stays true through\n ordinary operational change, which is what makes it dependable.\n\n**What we will not do is use this as cover.** Breadth here does not license a purpose we have not\ndescribed, a category of data we have not listed, or a transfer without a mechanism. If we start\nsending a new *kind* of personal data, or sending it for a new *reason*, that is a change to this page\nand to the notice period below — not something the width of a table quietly absorbs.\n\nIf you need to know precisely which providers are live for your workspace today, rather than which ones\nmay be, ask us at privacy@ever.co and we will tell you.\n\n### What is deliberately not in the tables\n\n- **Infrastructure we operate ourselves.** Our databases, object storage, cache, secrets manager and\n container platform are not sub-processors, because there is no third party involved. The next section\n describes what we run and what really does sit in front of it.\n- **Recipients that are not processors** — payment providers acting under their own regulatory\n obligations, professional advisers, public authorities, and an acquirer in a corporate transaction. Those\n are covered in the [Privacy Policy](https://githands.com/privacy).\n- **Sites you choose to visit** by following a link out of the Service. Once you are on someone else's\n site, their notice applies.\n\n## Annex: GitHands\n\n### Tier 1 — always engaged\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy, TLS termination and the tunnel that is the only public route into our infrastructure. Every request to any GitHands hostname passes through it. | United States, with edge termination worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, connection and TLS metadata, full request URLs and headers, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Three distinct roles. It hosts our source code, our container images and our build pipeline. It is the identity provider when a customer signs in with GitHub. And its public API is the primary source from which the developer database is built — profiles, stargazer and forker lists, contributor and participant lists, public commit metadata and public event streams. | United States | Standard Contractual Clauses (EU 2021/914) | the queries we make against its public API, the OAuth grant and access token a customer gives us, our own account and organisation identity |\n| Resend, Inc. | Delivery of outbound email — account and invitation mail, and the campaign messages a customer sends through the Service's default sending path — together with the delivery, open, click, bounce, complaint and reply events that come back. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, personalised subject line and message body, delivery, open, click, bounce and unsubscribe events, recipient IP address and user agent captured by open and click tracking, the content of a reply |\n| OpenRouter, Inc. | Routing of every AI request the Service makes to the model provider selected for it. This is the only AI provider configured in the hosted Service. OpenRouter forwards the prompt on to the upstream model provider it routes to, and that provider receives the same content. | United States, and onward to the selected model provider | To be confirmed — we do not yet evidence a mechanism | developer names, usernames, email addresses, biographies and repository lists embedded in prompts, drafted outreach messages and the inbound replies being classified, customer chat messages with the in-product assistant |\n| Langfuse GmbH | Observability for AI requests — the full prompt and the full completion for each call are recorded as a trace so we can debug quality and cost. That means the same personal data that goes to the model provider is also stored here, in readable form. | Germany | None needed — established in the EEA | complete prompts and completions, developer names, email addresses and repository data contained in them, session and user identifiers attached to a trace |\n| Functional Software, Inc. d/b/a Sentry | Application error monitoring and performance tracing. Browser reports are sent to a path on our own domain and forwarded on, so that an extension blocking third-party requests does not silently hide our errors from us. Server-side logging is enabled, so console output can travel with a report. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, user identifier and email address attached as error context, URL and route, stack traces and breadcrumbs, console output, which can carry fragments of whatever request failed |\n| PostHog, Inc. | Product analytics — which pages and features are used, where people abandon a flow, and what fails. Captured both in the browser and on our servers. Consent-gated in the browser. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and the approximate location derived from it, device and browser characteristics, pageviews and in-product events, distinct identifier and referrer |\n| Jitsu Labs, Inc. | A second product-analytics event pipeline. Events are collected through an endpoint on the githands.com domain rather than a vendor hostname, which is worth saying plainly: an endpoint on our own domain that forwards to somebody else should never be a surprise. Consent-gated. | United States | Standard Contractual Clauses (EU 2021/914) | IP address and user agent, in-product events and their properties, user identifier |\n| Trigger.dev Ltd. | The managed runtime that executes background work — extraction runs, enrichment, scoring, sequence steps and scheduled jobs. Job payloads and run logs are held there, and the runtime holds the credentials it needs to reach our database. | United Kingdom | None — we run this ourselves in the EU | job payloads, which contain developer profiles and campaign content, run logs and error output, database connection credentials, and therefore indirect reach into application data |\n| ui-avatars.com | Generated placeholder avatars, used where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | Not published by the provider | To be confirmed — we do not yet evidence a mechanism | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n| Cloudflare, Inc. (R2 object storage) | Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network. | United States | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold |\n| Google Ireland Limited (Google Workspace) | Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs. | Ireland (contracting) / United States and global (Google LLC) | Standard Contractual Clauses (EU 2021/914) | all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments |\n| Cloudflare, Inc. (Turnstile) | Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie |\n| Clerk, Inc. | Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name. | United States | Standard Contractual Clauses (EU 2021/914) | name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain. | United States | To be confirmed — we do not yet evidence a mechanism | search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata |\n| Prospect One sp. z o.o. (jsDelivr) | Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating. | Poland (operator); delivery worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified | Second permitted origin for the Lottie animation runtime on the ever-works login and register pages. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\n| Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting. | Handles subscription billing and invoicing for the hosted Gauzy service. | United States / Netherlands | To be confirmed — we do not yet evidence a mechanism | billing identity and address, plan, invoice and payment history |\n| Shopify International Limited | Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records. | Ireland (contracting) / Canada and United States (Shopify group) | Standard Contractual Clauses (EU 2021/914) | customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront |\n\n### Tier 2 — engaged only when a feature, integration or consent brings them in\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Google LLC | Sign in with Google. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name, profile picture URL, Google account identifier |\n| LinkedIn Ireland Unlimited Company | Sign in with LinkedIn, and the delivery of LinkedIn-hosted profile images where a signed-in user has one. Engaged only where an individual chooses that sign-in method. | United States | Standard Contractual Clauses (EU 2021/914) | email address, name and profile fields, profile picture URL, LinkedIn member identifier |\n| HubSpot, Inc. | Two-way contact synchronisation, engaged only when a customer connects its own HubSpot account. Data moves in both directions once connected. | United States | Standard Contractual Clauses (EU 2021/914) | contact and company records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Two-way contact synchronisation, engaged only when a customer connects its own Salesforce organisation. | United States | Standard Contractual Clauses (EU 2021/914) | contact and account records the customer chooses to sync, names, email addresses, employers and job titles in those records, the OAuth credential for the connection |\n| Slack Technologies, LLC (a Salesforce, Inc. company) | Workspace notifications and in-Slack actions, engaged only when a customer installs the Slack application into its own workspace. | United States | Standard Contractual Clauses (EU 2021/914) | workspace, channel and user identifiers, the notification content we send |\n| Stripe, Inc. | Payments and subscription billing for paid plans, engaged when you buy one. The free plan never reaches it, and we never receive your full card number. | United States | Standard Contractual Clauses (EU 2021/914) | billing name and address, country and tax identification number, payment method token and card last four digits, invoice and subscription history |\n| Twilio Inc. (SendGrid) | An alternative outbound sending provider. The Service can be configured to send through it instead of the default. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery and engagement events |\n| Sinch Mailgun | An alternative outbound sending provider. Not configured in the hosted Service. | United States, with an optional European region | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Amazon Web Services, Inc. | Amazon SES as an alternative outbound sending provider, with Amazon SNS carrying bounce and complaint notifications back. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, bounce and complaint events |\n| ActiveCampaign, LLC (Postmark) | An alternative outbound sending provider. Not configured in the hosted Service. | United States | Standard Contractual Clauses (EU 2021/914) | recipient email address and name, message content, delivery events |\n| Google Ireland Limited (Sign in with Google) | Authenticates a user who chooses 'sign in with Google', returning their email, name and picture, and in ever-rec also exports recordings to the user's own Google Drive when they connect it. | Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | email address, name and profile picture, Google account identifier, OAuth access and refresh tokens, Google Drive file metadata and content the user chooses to export, where the Drive scope is granted (ever-rec) |\n| Zapier, Inc. | Forwards workspace records into whatever third-party apps a customer wires into a Zap, so the onward destinations are the customer's choice and outside our contract. | United States | Standard Contractual Clauses (EU 2021/914) | records pushed through a Zap (tasks, timesheets, contacts), OAuth tokens and authorization codes, arbitrary event payloads forwarded to whatever apps the customer wires up |\n| Google Ireland Limited (Google Fonts) | Delivers typefaces to the visitor's browser at page load on the properties that hot-link them, disclosing the visitor's IP to Google before any consent choice. | Ireland (contracting entity); processing in Ireland (contracting) / United States (operating) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| Vercel Inc. | Hosts the cloc platform; routes AI prompts to downstream model providers for gauzy through the AI Gateway; and remains the deployment target of surviving workflows and DNS delegations for several frontends that have since moved to our own cluster. | United States | Standard Contractual Clauses (EU 2021/914) | for cloc: full application traffic and runtime data (the platform actually runs there), IP address and user agent of visitors where a site is served from Vercel, page-view and Web Vitals events, for gauzy: prompt content and model responses routed through the AI Gateway, plus routing and usage metadata, deployment metadata |\n| DigitalOcean, LLC | Serves desktop installer downloads from the gauzy.co download page, holds media in Spaces where a deployment selects it as the file provider, still carries legacy container images and gated deploy workflows, and for cloc provisions servers on a customer's behalf. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files, screenshots and captured media held in Spaces, IP address and user agent of anyone downloading an asset or a desktop installer, container images and build metadata (no personal data), for cloc: server handles, sizes and lifecycle state of infrastructure provisioned on a customer's behalf |\n| Uptime Robot Service Provider Ltd - UNVERIFIED. The commonly cited registration is Cyprus (Nicosia); confirm from the current Terms or Imprint before publishing any location claim. | Hosts the public status page at status.<our-domain>, so anyone who opens it hands their IP and user agent to the vendor. | Cyprus (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address and user agent of every visitor to a status page, cookies set by the status page, monitored endpoint URLs and response metadata |\n| Wasabi Technologies, Inc. | Holds avatars, task attachments and time-tracker screenshots wherever the platform's or a tenant's file provider is set to Wasabi. | United States | Standard Contractual Clauses (EU 2021/914) | uploaded files and document attachments, avatars, employee time-tracker screenshots and captured monitoring media |\n| Cloudinary Ltd. | Stores and transforms images and video where a deployment's or the platform's media provider is set to Cloudinary, and serves them to viewers directly from its own CDN. | Israel | Adequacy decision — Israel | uploaded images and video, screenshots and captured media, IP address and user agent of every viewer fetching an asset |\n| UNKNOWN - operated by an individual developer; no identifiable legal entity, no privacy policy, no DPA counterparty | Supplies fallback avatar and logo placeholder images whose URLs are written into persisted user, organization and team records and then fetched directly by the visitor's browser. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Twilio Inc. (Programmable Messaging) | Sends SMS where a tenant configures Twilio as its SMS gateway using its own account SID and token. | United States | Standard Contractual Clauses (EU 2021/914) | recipient telephone number, message body, which can contain a capture link or workspace content, delivery and status metadata |\n| Google Ireland Limited (Google Analytics 4 and Google Tag Manager) | Measures marketing-site and, on some properties, in-application usage through the GA4 tag loaded via Tag Manager, keyed to a persistent client-id cookie. | Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address (anonymize_ip is set on some sites, not all), _ga / _gid / _gat cookies (GA client identifier), page URLs, referrer and UTM parameters, device, browser and approximate location, conversion events, tied to a user id on gauzy.co |\n| Hound Technology, Inc. (d/b/a Honeycomb.io) | Receives OpenTelemetry traces from the API where Honeycomb is selected as the OTEL provider, including request URLs and database statements that routinely carry identifiers. | United States | Standard Contractual Clauses (EU 2021/914) | trace and span data including request URLs, route parameters and DB statements, service and host identifiers, anything a span attribute carries, which can include user and tenant ids |\n| SigNoz Inc. (Delaware, USA) for SigNoz Cloud; SigNoz itself is Apache-2.0 and self-hostable. | Receives OpenTelemetry traces, metrics and logs from the API wherever the OTLP endpoint is configured, including route parameters and SQL text. | United States | To be confirmed — we do not yet evidence a mechanism | distributed traces including HTTP routes, query strings and SQL statements, service and host metadata, metrics and logs, anything attached as a span attribute |\n| Better Stack, s.r.o. | Receives shipped application logs where a log token is configured, including the ChatGPT connector service in ever-teams and the cloc platform's observability pipeline. | Czech Republic | None needed — established in the EEA | application log lines, which may embed user ids, request paths and IP addresses, uptime probe results |\n| OpenAI, L.L.C. | Generates completions and transcribes audio for in-application AI features, using either a platform-held key (cloc) or a key the customer supplies (gauzy, ever-works, ever-teams, hust). | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, including workspace records, job posts, candidate and employee profile text, issue and task text and chat messages, audio submitted for transcription, model responses, OAuth device-auth identity for the Codex CLI plugin |\n| Anthropic, PBC | Generates completions for in-application AI features - the default model in hust, a plugin or bring-your-own-key option in gauzy and ever-works. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, which can include workspace data the user pastes or references, model responses |\n| Google Ireland Limited (Gemini API) | Generates completions for the in-application AI assistant where a customer connects a Gemini key, through the AI Studio endpoint rather than Vertex AI. | Ireland (contracting entity); processing in United States (AI Studio) / Ireland (Vertex AI) | Standard Contractual Clauses (EU 2021/914) | prompt content, which can carry workspace, HR and candidate data, model responses |\n| Mistral AI SAS | Generates completions where the Mistral plugin is enabled for a Work. | France | None needed — established in the EEA | prompt text, completions |\n| X.AI LLC | Generates completions where a customer selects Grok and supplies a key. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Groq, Inc. | Serves completions where a user supplies a Groq key and selects it as the provider. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, model responses |\n| Together Computer, Inc. (trading as Together AI) | Serves completions where a user selects Together as the provider and supplies a key, called from our own Next.js server route. | United States | To be confirmed — we do not yet evidence a mechanism | prompt content, including chat message text, model responses |\n| Vercel Inc. | Routes AI prompts from the Gauzy assistant to whichever downstream model provider the customer's selected model resolves to. | United States | Standard Contractual Clauses (EU 2021/914) | prompt content, model responses, request routing and usage metadata |\n| Intuition Machines, Inc. (hCaptcha) | Scores signup and login attempts wherever the CAPTCHA provider is set to hCaptcha. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and browser/device fingerprint signals, mouse, touch and timing interaction signals, challenge solution and token |\n| Meta Platforms Ireland Limited (Facebook Login) | Authenticates a user who chooses to sign in with Facebook, returning their email, name and profile picture. | Ireland (contracting entity); processing in Ireland (contracting for EEA users) / United States (Meta Platforms, Inc.) | Standard Contractual Clauses (EU 2021/914) | email address and name, Facebook user identifier, profile picture URL, OAuth tokens |\n| X Corp. (Twitter) | Authenticates a user who chooses to sign in with X, where that provider is enabled for the deployment. | United States | To be confirmed — we do not yet evidence a mechanism | handle and public profile, X user identifier, OAuth tokens |\n| Microsoft Corporation (Microsoft Entra ID) | Authenticates a user or administrator who chooses a Microsoft work or personal account, reading profile details from Microsoft Graph, where FEATURE_MICROSOFT_LOGIN is enabled. | United States | Standard Contractual Clauses (EU 2021/914) | email address and display name, Microsoft tenant identifier and user object id, OAuth access and refresh tokens, directory profile fields returned by Graph within the granted scope |\n| Okta, Inc. (Auth0) | Authenticates an organisation's people where that organisation chooses to route sign-in through its own hosted Auth0 tenant. | United States | Standard Contractual Clauses (EU 2021/914) | email address and profile, OAuth/OIDC tokens, login IP address, device and user agent, authentication and MFA event logs |\n| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Takes payments for a commerce deployment, where the merchant running that deployment contracts with PayPal directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Luxembourg (EEA users) / United States (PayPal, Inc.) | None needed — established in the EEA | payer identity and email address, transaction amount and order reference, payment status and history |\n| Atlassian Pty Ltd (Jira, Trello) | Syncs tasks, issues and attachments with a Jira or Trello site the customer connects using its own account. | Australia (Atlassian Pty Ltd) / Netherlands (Atlassian B.V.) / United States (Atlassian, Inc.) | Standard Contractual Clauses (EU 2021/914) | issue, project, card and board records, reporter and assignee identity, attachments, screenshots and recordings pushed to an issue, API key and OAuth tokens |\n| Activepieces Inc. | Runs automation flows that read and receive whatever workspace records a customer wires in, on Activepieces' US cloud unless repointed at a self-hosted instance. | United States / Canada | Standard Contractual Clauses (EU 2021/914) | records pushed through a flow, which can be any workspace data, API keys, webhook payloads |\n| Celonis SE (Make.com) | Runs automation scenarios that read and receive whatever workspace records the customer wires in, from EU infrastructure. | Germany / Czech Republic | None needed — established in the EEA | records pushed through a scenario, webhook payloads, OAuth tokens |\n| Noti-Fire Apps Ltd. (Novu) | The in-application notification inbox and a delivery channel for notifications, where it is configured against Novu's hosted service rather than an instance you run. | Israel | Adequacy decision — Israel | a hashed subscriber identifier, computed server-side under NOVU_SECRET_KEY, notification content, email address where Novu is used as a delivery channel |\n| Plausible Insights OÜ | Cookieless site analytics on a Work site, where the Work Owner enables it. | Estonia | None needed — established in the EEA | page views and referrer, coarse device and country, derived and not stored as an IP address |\n| Chatwoot Inc. | Runs the support chat widget that visitors and signed-in users type into, receiving the whole conversation plus the page context. | United States | Standard Contractual Clauses (EU 2021/914) | visitor or user name and email when supplied, full chat message content, IP address, page URL and browser details |\n| iubenda s.r.l. | Delivers hosted legal documents to visitors who open the /legal route in the Gauzy application, which still fetches the policy from iubenda in the visitor's browser. | Italy | None needed — established in the EEA | IP address, user agent, consent preferences and the timestamp of the choice |\n| Algolia SAS | Answers the search box on the documentation sites, receiving each reader's query and IP where Algolia credentials are configured. | France (EEA) or United States, depending on the contracting entity and the index region | To be confirmed — we do not yet evidence a mechanism | search queries typed by the reader, IP address, user agent, indexed page content |\n| Google Ireland Limited (Google Maps Platform) | Renders maps and completes typed addresses for contacts, clients and organisations where the Maps and Places features are enabled with an API key. | Ireland (contracting entity); processing in Ireland (contracting) / United States (processing) | Standard Contractual Clauses (EU 2021/914) | IP address, typed address fragments and place queries, latitude and longitude of contacts, clients and organisations, session tokens for autocomplete billing |\n| Lemon Squeezy, LLC | Takes payments from a Work site's own visitors as merchant of record where the Work Owner connects it, so the Work Owner contracts with it directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing address and tax location, payment identifiers and purchase history, card data entered on Lemon Squeezy's own hosted checkout and never reaching us |\n| Polar Software Inc. | An alternative payment and subscription provider for a Work site's own visitors, connected and contracted by the Work Owner. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | United States (Delaware) | Not our transfer — you choose the provider | name and email address, billing and tax location, payment identifiers and subscription history, card data entered on Polar's own hosted checkout and never reaching us |\n| SolidGate | A further card payment option for a Work site's own visitors, where the Work Owner enables it and contracts with the payment institution directly. Acts as an independent controller for fraud prevention, anti-money-laundering and card-scheme compliance, on its own legal obligations rather than our instructions. | Cyprus (EEA) | None needed — established in the EEA | cardholder name, email address, billing address, payment identifiers |\n\n### Tier 3 — self-hosted deployments only\n\nIf you run GitHands on your own infrastructure, you choose these providers and hold the\ncredentials. **We are not a processor for anything in a deployment you run**: we do not receive that data,\nwe cannot reach it, and we have no relationship with the providers you configure.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation has no sending path of ours to fall back on — we removed the shared sending address deliberately. You bring your own sending account and your own verified sending domain. The software supports Resend, Twilio SendGrid, Sinch Mailgun, Amazon SES, Postmark and a plain SMTP relay. | Wherever the provider you choose processes | Not our transfer — you choose the provider | recipient email addresses and names, message content, delivery and engagement events |\n| The Rocket Science Group LLC d/b/a Mailchimp | Every AI feature in a self-hosted installation runs against a key you supply, to a provider you pick. Nothing routes through us and we see none of it. | Wherever the provider you choose processes | Not our transfer — you choose the provider | prompts and completions, including any personal data your installation puts in them |\n| The Rocket Science Group LLC d/b/a Mailchimp | A self-hosted installation reads the source platforms under your own credentials and in your own name. The rate limits, the platform's acceptable use rules and the consequences of breaching them attach to your account, not ours. | The platform's own infrastructure | Not our transfer — you choose the provider | the queries your installation makes, your own account identity and access token |\n| The database, object storage and job runtime you choose | You select and operate the PostgreSQL database, the object storage and the background-job runtime. Trigger.dev can be pointed at its hosted service or at an instance you run yourself. | Wherever you deploy them | Not our transfer — you choose the provider | all application data in your installation |\n| The Rocket Science Group LLC d/b/a Mailchimp | Sentry, PostHog and Jitsu wiring ships in the software but is inert until you supply your own project keys. Supply them and the data goes to your projects, under your account. | Wherever the provider you choose processes | Not our transfer — you choose the provider | error reports, console output, product analytics events and the identifiers attached to them |\n| Mem0 AI, Inc. | Long-term memory for the command-line client and the MCP server. Disabled in the hosted Service and available only to a self-hoster who switches it on with a key of their own. | United States | Not our transfer — you choose the provider | stored agent conversation memory, which can contain customer and developer details |\n| none in a self-hosted deployment - the reader (or we) runs the runtime. Ollama Inc. (US) publishes the software and would become a processor only if a hosted Ollama service were adopted. | Runs open-weight models inside the deployment itself, so prompts reach no third party at all. | n/a (self-hosted); United States for Ollama Inc. | Not our transfer — you choose the provider | chat and prompt text, which never leaves the deployment |\n| Red Hat, Inc. (Keycloak) | Authenticates users through a Keycloak realm that the organisation running the deployment operates itself. | United States (Red Hat, Inc.) / wherever the reader runs the realm | Not our transfer — you choose the provider | email address and profile, OIDC tokens |\n| Mixpanel, Inc. | Records in-app screens and named events - 'Order Delivered' from the courier application, 'Order Failed' from the merchant tablet and similar - against a device identifier, where the operator configures a Mixpanel token and publishes a build containing it. | United States | Not our transfer — you choose the provider | device identifier, screens viewed and in-app events, IP address, user identifier once the person has signed in, the Mixpanel project token, which is compiled into the distributed binary |\n| Intercom, Inc. | Runs the in-application support conversation in the shopping, merchant and courier mobile applications through cordova-plugin-intercom / @ionic-native/intercom, where the operator supplies Intercom credentials. | United States (Intercom, Inc.) / Ireland (Intercom R&D Unlimited Company) | Not our transfer — you choose the provider | user identifier and email address, full support conversation content, device and application context, the operator's Intercom app id and API key |\n\n### Data about developers who are not our users\n\nMost of the personal data in GitHands is about people who never signed up. The sub-processors\nabove process that data on our instructions in the same way as any other — but two points follow that a\nplain table does not convey.\n\n- **The source platforms are not our sub-processors.** GitHub, GitLab and similar platforms are where the\n data comes from, not parties we send it to. Their terms govern what may be collected from them and what\n may be done with it afterwards.\n- **We do not sell this data, and no provider above receives it for their own purposes.** Every one of them\n acts on our instructions under a written contract.\n\nIf you are a developer whose data is here and you want it removed, you do not need to work out which\nprovider holds what. Use the objection route in the privacy annex and it is handled across all of them.\n\n## Hosting and infrastructure\n\nThe tables above are short for a reason, and the reason is worth stating plainly: **we run our own\ninfrastructure.** The Service is not a tenancy in a public cloud account. It runs on physical servers we\nown, in facilities we control, **inside the European Union**, on a virtualisation and container platform we\noperate ourselves.\n\nThe database, the object storage that holds your files, the cache and queue layers, the secrets manager and\nthe deployment system are all components we run. **None of them is a third party, so none of them appears\nas a sub-processor** — there is nobody else to disclose. What we do with them is described on our\n[Security page](https://githands.com/security).\n\n### Where processing actually happens\n\n- **Your data at rest, and the applications that process it, sit on our own hardware in the European\n Union.** That is the primary location for accounts, content, files and the databases behind them.\n- **Requests reach us through a global content delivery and security network.** Traffic is terminated at\n the edge location nearest to whoever is making the request, which can be anywhere in the world, before\n being carried to our infrastructure in Europe. That provider is in the always-engaged tier above, and the\n transfer mechanism for it is described in our [Privacy Policy](https://githands.com/privacy).\n- **Off-site backup copies are held with an external object storage provider**, encrypted by us before they\n leave our network. That provider holds ciphertext and no key, and cannot read what it stores.\n- **Our source code, build pipeline and container images are hosted with a third-party provider.** That is\n how the Service is built and deployed rather than where your data lives day to day, but it is a genuine\n third party and it is disclosed as one.\n\n### Where a product does something different\n\nA small number of products use a third-party managed database, managed storage or hosted platform for a\nspecific function instead of our own infrastructure. **Where that is the case for GitHands, the\nprovider appears in the always-engaged tier above and the product annex says which data goes there.**\n\nWe are explicit about this because \"self-hosted\" is exactly the sort of claim that gets made once and then\nstops being true for one product in the range. If your data for a given feature sits with someone else, the\ntable says so.\n\n### The regions you should design around\n\nIf you are completing a transfer mapping or a data protection impact assessment, the honest summary is:\n**primary processing in the European Union on infrastructure we operate; edge termination worldwide; a\nsmall number of named providers established outside the European Economic Area, each with its own transfer\nmechanism.** Every one of those providers is in the tables above, and the mechanism for each is in the\ninternational transfers section of the [Privacy Policy](https://githands.com/privacy).\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and which\nmodules apply — write to privacy@ever.co and we will send them.\n\n## When this list changes\n\n### The notice period\n\n**We give at least 30 days' notice before a new or replacement sub-processor starts processing personal\ndata for the hosted Service.** The 30 days run from the date the notice is published or sent, whichever\ncomes first, and they exist so that your objection right is a real one rather than a formality you learn\nabout afterwards.\n\n### How you find out\n\n- **This page changes first.** It carries the date it took effect and a dated record of what changed, so\n the page itself is the notice.\n- **By email, if you ask for it.** Write to privacy@ever.co and we will add your address to the\n notification list. We then email you before each change, at the same time the page is updated. **We\n recommend a role address rather than an individual's** — a notice sent to someone who has left your\n organisation has been sent and not received.\n- **In the product**, for changes that affect a feature you are using, through a notice to workspace\n administrators.\n\n### What the notice tells you\n\nThe provider's legal name, what it will do, where it is established, the categories of personal data it\nwill receive, the transfer mechanism if it is outside the European Economic Area, the date it takes effect,\nand whether it is a new provider or replaces one already on the list. If it replaces one, we say which.\n\n### Urgent replacements\n\nSometimes we have to move faster than 30 days — a provider suffers a security incident, terminates its\nservice, loses the legal basis it relied on, or fails in a way that makes staying with it worse than\nleaving.\n\n**Where that happens we may engage the replacement sooner, and we will notify you as quickly as we can with\nthe reason we could not wait.** Your right to object is not affected: it simply runs from the notice\ninstead of before the change. We do not use this route as a convenience, and a notice sent under it says\nplainly why the normal period was not followed.\n\n### Changes that do not need notice\n\nRemoving a provider does not need a notice period — it reduces the number of people handling your data. A\nprovider changing its own name, or the group entity that contracts with us changing without a change in\nwhere or how the processing happens, is recorded here as an administrative update rather than announced as\na new engagement. **A provider moving its processing to a different country is not administrative, and gets\nthe full notice.**\n\n### The record\n\nWe keep the change history for this page so that you can reconstruct who was engaged during a given period.\nThat matters if you are updating your own records of processing, refreshing an impact assessment, or\nanswering a question about a period in the past. Ask privacy@ever.co if you need the state of the list\nas it stood on a particular date.\n\n## Objecting to a sub-processor\n\n### Who can object\n\nThe customer — the organisation or person who contracts with us and acts as controller for the data in the\nworkspace. If you are an individual whose data we hold, this is not your route: your rights are in the\n[Privacy Policy](https://githands.com/privacy), and if your data sits in an employer's workspace, your employer\nis the controller and the request goes to them.\n\n### How to object\n\nWrite to **privacy@ever.co** within **30 days** of the notice, and tell us:\n\n- which provider you are objecting to;\n- **your reasons, on data protection grounds** — a transfer you cannot justify, a conflict with a\n commitment you have given your own users, a regulator's position that applies to you, a documented\n security concern;\n- which of your workspaces or environments the objection covers.\n\n**The reasons matter.** This is a right to object on data protection grounds, not a veto over our choice of\nsuppliers, and an objection with no stated ground gives us nothing to work with. Tell us what the problem\nis and we can usually solve it.\n\n### What we do next\n\nWe acknowledge your objection within five business days and **respond substantively within 30 days.** In\nbetween we look for a way to make the objection unnecessary:\n\n- **A different provider** for your workspace, where one exists that does the job.\n- **A different configuration** — narrowing what is sent, changing a region, or turning off the feature\n that needs the provider at all, if you can live without it.\n- **Excluding your workspace** from the provider, where that is technically possible.\n- **Additional safeguards or contractual terms** where your concern is about a specific risk rather than\n the provider as a whole.\n\nWhere it is technically possible to hold off, **we will not start using the provider you have objected to\nfor your data while the objection is open.** Where it is not possible — because the provider is part of how\nthe Service is delivered to everyone — we will tell you that plainly and quickly, rather than letting the\nclock run out on you.\n\n### If we cannot resolve it\n\nIf we cannot offer you a solution you can accept, **you may terminate the affected subscription by written\nnotice, without penalty, and we will refund the fees you have prepaid for the period after termination.**\nThat is the remedy: neither of us owes the other damages for a good-faith disagreement about a supplier.\n\nGive us notice within 30 days of our final response, and we will keep your data available for export for\nthe usual 30-day window described in the [Terms of Service](https://githands.com/tos) so that leaving does not\ncost you the data.\n\nIf you are on a free tier there is nothing to refund, and the same route is simply to stop using the\nService and export your data.\n\n### Objecting to a provider already on the list\n\nYou do not have to wait for a change. **You can raise a concern about a provider already listed at any\ntime**, using the same address and the same process, without the 30-day deadline. The realistic outcome\ndiffers by tier: a tier 2 provider can usually be switched off for you; a tier 1 provider generally cannot,\nbecause it is part of how the Service works — and if the answer is going to be no, you will get it as a\nstraight no with the reason.\n\n## How to reach us about this list\n\n- **Questions about a provider, a request for the safeguards behind a transfer, or a request to join the\n change notification list** — privacy@ever.co.\n- **An objection to a sub-processor** — privacy@ever.co, as set out above.\n- **The Data Processing Addendum, a due diligence request, or a security questionnaire** —\n legal@ever.co.\n\nWe are **Ever Technologies LTD**, registered in Bulgaria under company number\n204599535, with its registered office at Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria. We are the controller for our\nown processing and your processor for the data in your workspace. By post, write to the registered office\nand mark the letter for the attention of the privacy team. We correspond 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.1.0 of the sub-processor list for\n[githands.com](https://githands.com), in force from 2026-10-05. It lists the providers engaged\nas at that date. Earlier versions, with the dates they applied, are at\n[https://githands.com/subprocessors](https://githands.com/subprocessors)."
|
|
158
158
|
}
|