Boosthis — Data Processing Agreement
You do not sign this. It is published, and accepting the Boosthis Terms accepts it — the same way Sentry, PostHog and other tools in this category do it. There is no countersigned copy to chase and no signature round-trip before you can buy.
The companies that receive data are not listed in this document. They are at https://www.boosthis.com/subprocessors, on 14 days' notice before a new company starts receiving data, so a change of provider does not require amending an agreement you have already accepted.
1. Who this is between, and what it covers
This agreement is between you — the account holder, referred to here as the customer — and Veqtara Tech Company, the company that operates Boosthis (commercial registration 7054832287, Rabwa District, Al Noaim Street, Riyadh, Saudi Arabia).
It governs personal data that Boosthis processes on your behalf when you install a Boosthis kit in your own application: the measurements the kit takes, the identifiers it carries, and anything about your application's end users that reaches us as a result. For that data you are the controller and we are the processor, and this agreement is the written record of that — with the one use of our own that clause 12 sets out.
It does NOT cover your own account with us — your name, your email address, your billing details, and what you do while signed in. For that data we are the controller in our own right, and what we do with it is set out in the privacy half of the Terms rather than here.
This agreement is incorporated into the Boosthis Terms of Service by reference. Accepting the Terms accepts this, and there is no separate signature: it is published at https://www.boosthis.com/processing and changes there, visibly, rather than in a document neither side can find later.
2. Subject matter, duration, nature and purpose
Subject matter: performance and reliability measurement of your application. Nature and purpose: taking, storing, aggregating and reporting those measurements back to you, and deriving from them the findings, comparisons and written advice the product exists to produce.
Categories of data subject: the end users of your application, and the developers on your own team who install and operate the kit.
Categories of personal data: technical and behavioural measurements — timings, screen and route labels, error and crash signatures, device and runtime characteristics, and an installation identifier that is generated by the kit rather than taken from a person. Boosthis does not ask for and has no field for a name, an email address, a postal address or a payment detail belonging to one of your end users. What may be sent at all is a closed vocabulary that the kit cannot add to and the server drops terms it does not recognise.
Duration: for as long as your account is open and the kit is installed, and then for the periods in clause 8.
3. We act on your instructions
We process the data described above only on your documented instructions, and for no purpose of our own beyond operating and securing the service you are paying for and the one use clause 12 authorises and describes. Your instructions are: this agreement, the Terms, the settings you choose in your dashboard, and what the kit you installed is configured to send.
If we believe an instruction of yours requires us to break a law that applies to us, we will tell you rather than quietly comply or quietly refuse.
If a law that applies to us requires us to process the data in some other way, we will tell you before doing so unless that same law forbids telling you.
We do not sell the data, we do not rent or trade it, and we do not use it for anybody's advertising. We do not use your end users' measurements to train a general-purpose AI model. What clause 12 lets us learn across projects leaves your project only as a rule or a count of projects — never one of your end users' records.
4. Confidentiality
Everybody who can reach the data is bound to keep it confidential, and that obligation outlives their involvement. Boosthis is operated by a small team; access is limited to the people who need it to run the service, and privileged actions taken inside the product's own administrative pages are recorded in an audit trail.
5. Security
We keep appropriate technical and organisational measures in place. Concretely, and in the words of what the code actually does: data travels over TLS and the site is served with a strict transport policy; the database and its daily backups are encrypted at rest by the companies that hold them, Replit and Google Cloud, and the backups carry that encryption rather than one of our own; credentials are stored as one-way hashes, and the values we must be able to use again are encrypted by us with AES-256-GCM, under keys kept apart from the database; what a kit may send is a closed vocabulary rather than free text, and the one free-text field a developer can send is screened for identifiers before it leaves; outbound requests are pinned to a checked address; the database is backed up daily and a full restore is rehearsed weekly against real backups; and the public surfaces are checked from outside our own network.
6. Sub-processors
You give a general authorisation for us to engage the sub-processors published at https://www.boosthis.com/subprocessors, and that page — not this agreement — is the list. It is separate on purpose, so a company can be added or replaced without amending a contract you have already accepted.
Before another company starts receiving your data it is named on that page at least 14 days beforehand, unless a change has to be made sooner to keep the service running or secure, in which case it is named as soon as it takes effect. You can subscribe to double opt-in email change notices at https://www.boosthis.com/trust without an account, or follow the additional feed at https://www.boosthis.com/subprocessors.xml.
If you object to a new sub-processor within the notice period, tell us at support@boosthis.com. We may not be able to keep serving you without it — in which case your remedy is to stop using the service and close your account, and we will say so plainly rather than leave you to discover it.
Each sub-processor that acts as our processor must be bound by written data-protection terms that give your data at least the same protection as this agreement, including on security, confidentiality, help with requests and incidents, deletion, and audit. Where a company acts under its own legal duties instead — a licensed payment institution, for example — it is an independent controller, and the list says so in those words rather than claiming a term nobody can keep.
What the record shows today: Resend is bound by its Data Processing Addendum. Expo is bound by its Terms of Service, section 3.2 (GDPR). sccc is bound by its Subscription Agreement. Moyasar acts as an independent controller under its own legal duties, so no processor terms are claimed for it. Anthropic, Replit, Google Cloud, Apple and Google Workspace are not yet shown to be bound, and each is named on that page as an action we owe rather than claimed. The page states, for each company, the terms that bind it, how they were accepted, its transfer mechanism and the date the terms were read.
We remain responsible to you for what a sub-processor does with what we give it.
7. Where it is processed, and onward transfers
Where the service runs: the Boosthis servers and the database behind them run in the United States.
Whether your data crosses a border: some of it does. Moyasar and sccc hold what reaches them in the Kingdom of Saudi Arabia; Resend, Replit, Google Cloud and Expo hold what reaches them in the United States; what reaches Anthropic, Apple and Google Workspace leaves the Kingdom of Saudi Arabia too, but which country processes it is not confirmed.
Resend, Anthropic, Replit, Google Cloud, Expo, Apple and Google Workspace process what reaches them outside the Kingdom of Saudi Arabia. The transfer mechanism recorded for each one, and whether an in-Kingdom alternative exists, is published on https://www.boosthis.com/subprocessors.
If the GDPR applies to your processing of this data, the standard contractual clauses adopted by the European Commission in Decision (EU) 2021/914 are incorporated into this agreement by reference, for the transfer from you to us: Module Two where you are a controller, Module Three where you are yourself a processor, with you as the data exporter and us as the data importer. Clause 7 of those clauses (the docking clause) applies. Under their Clause 9, option 2 applies, with the notice period of clause 6 above. The optional wording in their Clause 11 is not used. Their Clause 13 points to the supervisory authority competent for you. Under their Clause 17, option 1 applies and they are governed by the law of Ireland, and under their Clause 18 disputes arising from them go to the courts of Ireland. Their annexes are printed at the end of this page, generated from the facts this page and the recipient list already publish.
If the UK GDPR applies, the International Data Transfer Addendum to those clauses, issued by the Information Commissioner under section 119A of the Data Protection Act 2018, is incorporated in the same way. Its Table 1 is completed by Annex I, its Table 2 by the paragraph above, and its Table 3 by the annexes; under its Table 4, neither party may end it as its Section 19 would allow. It is governed by the law of England and Wales, and disputes arising from it go to the courts of England and Wales.
If those clauses or that addendum conflict with anything else in this agreement or the Terms, they prevail.
Where we pass your data to a sub-processor outside the Kingdom of Saudi Arabia and no other transfer mechanism covers it, we rely on the standard contractual clauses that sub-processor offers in its own terms. What each company relies on — or that nothing yet does — is published against it on https://www.boosthis.com/subprocessors.
Onward transfer — a sub-processor handing the data to somebody further down its own chain — is covered by the position recorded against each company on https://www.boosthis.com/subprocessors, together with what that company's own published practice is. Those published lists are re-read on a weekly clock and compared with what was recorded, so a change in somebody else's chain is something we find out about rather than something we assume away. Two of the companies on our list are reached on another company's account, and that is the only place such a change shows up at all.
8. Deletion and return at the end
You can take a machine-readable copy of everything we hold for your account at any time, from your dashboard, without asking anyone. Take it before you close the account: after deletion we cannot produce one.
When you close your account it is frozen for 24 hours — a window in which you can change your mind — and then the data is deleted or de-identified in place. Where a payment or tax record must be kept by law, it is kept for that reason and nothing else.
An unpaid account is frozen rather than purged: we do not delete somebody's data as a debt-collection measure. Where a purge does run on a countdown, that countdown is 60 days and it is shown to you while it is running.
Backups are a separate clock. A routine backup is kept for 30 days and then rotated out, so deleted data can persist in a backup for up to that long after it has gone from the live database. We do not restore a backup to recover data you asked us to delete.
Independently of any of that, an installation on a server can have its measurements erased immediately from inside your own application, by the kit, without an email to anybody. A website's or phone app's installation is shared by every visitor's browser or every phone running the app, so one copy's erase request clears that device and stops it sending but erases nothing pooled: one person switching Boosthis off must not remove everybody's measurements. You erase the whole of such an installation by revoking the project key it reports under, which deletes the data of every installation under that key at the end of the countdown above, or by closing your account. See https://www.boosthis.com/your-data.
9. Help with requests and incidents
If one of your end users comes to us directly, we will not answer for you. We will tell them that their request belongs with you — the company whose application they used — and tell you that it reached us. What we will do without you is the self-serve erasure described at https://www.boosthis.com/your-data, which needs no decision from either of us because it is proved by control of the installation rather than by anything we hold. On a website or in a phone app that erasure clears the person's own device and stops it sending, and erases nothing pooled; erasing the installation itself stays with you.
If one of your end users' requests reaches you and you need our help to answer it, we will help: we can tell you what is stored for a given installation, produce it, correct it, or erase it. There is no charge for this.
If we become aware of a personal-data breach affecting data we process for you, we will tell you without undue delay, and in any case within 48 hours of becoming aware of it, so that you still have time to meet a 72-hour duty of your own. The first notice carries what we know at the time, and we keep telling you as we learn more. We will not wait until we have a complete picture to make the first contact.
We will give you the information you reasonably need for your own impact assessments and for any consultation with a supervisory authority, to the extent it is about what we do.
How to reach us for any of this: support@boosthis.com. We answer within 30 days.
10. Audit
Information comes first. You can ask us for the information needed to show that this agreement is being kept, and we will provide it. Most of it is already published: who receives what, where it is processed, how long it lives, and what the product does and does not collect are all on the public pages and are generated from the records the code itself is held to.
If that information does not settle the question, you may audit our compliance with this agreement, including by inspection, yourself or through an independent auditor bound to confidentiality, on at least 30 days' written notice to support@boosthis.com. An audit may take place at most once in any twelve months, unless there has been a personal-data breach affecting your data or a supervisory authority requires one. It is at your cost, it is arranged so that it does not disrupt the service or expose other customers' data, and what you or your auditor learn about other customers or about our security is kept confidential.
We hold no third-party audit report to offer in place of an audit, and this agreement does not pretend otherwise.
11. Governing law, and how this changes
This agreement is governed by the law of the Kingdom of Saudi Arabia, and disputes go the same way as under the Terms: Saudi Center for Commercial Arbitration (SCCA), seated in Riyadh, Kingdom of Saudi Arabia. The standard contractual clauses and the UK addendum incorporated in clause 7 are the exception: they are governed by the law, and go to the courts, that they themselves name.
Changes to this agreement are published here with the date they came into force, and every earlier revision stays listed below so you can see what changed and when. Each new revision is announced to everyone subscribed to change notices at https://www.boosthis.com/trust, in the change notice of the recipient list it is published with. A change that reduces your protection is announced at least 14 days before it comes into force; one that adds to it, or describes more precisely what we already do, comes into force when it is published. The recipient list has its own address and its own notice period, and otherwise moves independently of this document.
12. What we learn across projects
You authorise one use of the data this agreement covers for a purpose of our own: learning, across every project that uses Boosthis, which performance and reliability problems recur and what fixes them, so that the rule book every customer is served gets better. Nothing else in this agreement allows a purpose of our own, and this clause does not stretch to any other.
What feeds it is a closed list of code-derived signals, and nothing outside it: from a crash report, its one-way signature, its error name and kind, its redacted top frame and a bucketed count; from a finding the kit's own detectors report, its one-way signature and kind, with severity and count buckets; from a report that a pattern matched no rule, the runtime, a coarse category, severity and timing buckets, a one-way signature and how often it occurred; from a performance snapshot, the readings in the closed reading catalogue, to find the same work repeated and readings that keep getting worse; and from a promise judged broken, only its subject kind and its measure, from two lists this server defines, never its wording or its subject's name.
If you connect your own AI assistant, it can also send a drafted rule and the text of the pattern it saw. That is the one free-text value a kit can carry and it is not one of the signals above: it is screened for identifiers, addresses and secrets before it is kept, refused whole if the screen trips, and nothing drafted from it is served until a person has approved it.
Crash reports and findings are kept per installation, and pattern reports per project key — under the installation identifier the kit generates, or a one-way hash of your project key, never a person's name or address. That makes them pseudonymised, not anonymous, and we treat them as personal data for as long as that remains true. When your account closes, crash reports, findings and fix outcomes are re-keyed to a random token that cannot be traced back to the installation and the optional detailed crash fields are deleted; pattern reports keep the hash of the project key, with the link to the installation removed.
What leaves the learning is fleet-level: a rule in the rule book, with its fix, and counts of how many separate projects reported the problem behind it. It counts projects, never people. A rule is drafted only from a problem that separate customers reported, and nothing one project sent is shown to another customer.
For this one use we decide the purpose and the means, so we act as a controller in our own right rather than as your processor, and we answer for it ourselves — to you, to your end users and to any supervisory authority. The rule book also counts, with no text, questions about a project that no rule could answer; that is your own account activity, covered by the privacy half of the Terms rather than here.
If you object to this use, write to support@boosthis.com. There is no setting today that leaves one project out of the learning while the kit keeps measuring it, and we will not pretend there is: your choices are to remove the kit, which stops anything new reaching the learning, and to close your account, which de-identifies what it already holds as described above. If you object because of a duty of your own, tell us what it is and we will tell you plainly whether we can meet it.
13. Nobody in Europe
Boosthis is operated only from the Kingdom of Saudi Arabia, by Veqtara Tech Company, and has appointed no representative in the European Union or the United Kingdom. There is no European address to write to and no European entity behind this service: the contact for everything in this agreement is support@boosthis.com, answered from Riyadh. If you are in the EU or the UK and this matters to your purchase, say so before you buy rather than after — the decision, its reasoning and the condition that would change it are recorded at docs/decisions/eu-uk-representative.md in the Boosthis repository.
14. Revisions
- 2026-11-17 — Clause 5 now says how stored data is protected at rest: the database and its daily backups are encrypted at rest by the companies that hold them, Replit and Google Cloud, and the backups carry that encryption rather than one of our own; credentials are stored as one-way hashes, and the values we must be able to use again are encrypted by us with AES-256-GCM, under keys kept apart from the database. It replaces a shorter sentence about credentials. These measures were already in place, so nothing about your protection was reduced, and this revision came into force when it was published. Announced with the recipient list's change notice of the same date.
- 2026-10-13 — Two sentences in clause 5 that described what this agreement does not offer were removed. Neither was an obligation of ours or a right of yours, so nothing about your protection changed, and this revision came into force when it was published. Where your data is processed is still stated in clause 7. Announced with the recipient list's change notice of the same date.
- 2026-10-08 — Erasing a website's or phone app's installation. Every visitor's browser on a website, and every phone running an app, is a copy of one installation, so one copy's erase request now clears that device and stops it sending but erases nothing pooled; the customer erases the whole installation by revoking the project key it reports under, or by closing the account. An installation on a server is still erased at once from inside the application. Announced with the recipient list's change notice of the same date.
- 2026-10-04 — Brought to the legal minimum for a processor. Sub-processors acting for us must be bound by written terms giving at least the same protection, and the recipient list now shows what binds each one or names it as an action we owe. Audits, including inspections, are allowed after information, on notice, at most once a year unless a breach or a regulator requires more. Customers under the GDPR or the UK GDPR get the EU standard contractual clauses and the UK Addendum, with annexes generated from what this site publishes. The first breach notice has an outer limit. And a new clause authorises, and describes, the learning across projects that builds the rule book. Announced with the recipient list's change notice of the same date.
- 2026-09-29 — First published. Incorporated into the Terms by reference, with the recipient list moved to an address of its own so it can change without amending this agreement.
Annexes to the standard contractual clauses
These complete the clauses clause 7 incorporates, for customers under the GDPR or the UK GDPR. They are generated from the facts this page and the recipient list publish, so they cannot say something different from either.
Annex I.A — The parties
Data exporter: you, the customer, as the holder of the Boosthis account; contact: the address on that account. Role: controller (Module Two), or processor where you act for somebody else (Module Three). Activities relevant to the transfer: using the hosted service clause 2 describes. Signature and date: given by accepting the Terms, on the date recorded against your account.
Data importer: Veqtara Tech Company, operating Boosthis (commercial registration 7054832287, Rabwa District, Al Noaim Street, Riyadh, Saudi Arabia); contact: support@boosthis.com. Role: processor. Activities relevant to the transfer: those clause 2 describes. Signature and date: given by publishing this agreement, on the date this revision came into force.
Annex I.B — Description of the transfer
Categories of data subjects: the end users of your application, and the developers on your own team who install and operate the kit.
Categories of personal data: technical and behavioural measurements — timings, screen and route labels, error and crash signatures, device and runtime characteristics, and an installation identifier that is generated by the kit rather than taken from a person.
Sensitive data: none. The kit has no field for it, and the server drops terms it does not recognise.
Frequency: continuous, for as long as the kit is installed and sending.
Nature and purpose of the processing: taking, storing, aggregating and reporting those measurements back to you, and deriving from them the findings, comparisons and written advice the product exists to produce; and the learning clause 12 describes.
Retention: for the periods in clause 8.
Transfers to sub-processors: to the companies in Annex III, for the purpose and the data stated against each.
Annex I.C — Competent supervisory authority
The supervisory authority competent for you, as the data exporter, under Clause 13; for the UK addendum, the Information Commissioner.
Annex II — Technical and organisational measures
The measures clause 5 states: data travels over TLS and the site is served with a strict transport policy; the database and its daily backups are encrypted at rest by the companies that hold them, Replit and Google Cloud, and the backups carry that encryption rather than one of our own; credentials are stored as one-way hashes, and the values we must be able to use again are encrypted by us with AES-256-GCM, under keys kept apart from the database; what a kit may send is a closed vocabulary rather than free text, and the one free-text field a developer can send is screened for identifiers before it leaves; outbound requests are pinned to a checked address; the database is backed up daily and a full restore is rehearsed weekly against real backups; and the public surfaces are checked from outside our own network.
Annex III — Sub-processors
- Moyasar — an independent controller, acting under its own legal duties. What it does: payments — embedded payment form and subscription charges. What reaches it: card details sent directly from the browser through Moyasar's form embedded in Boosthis-hosted checkout (never to Boosthis's servers), the amount and currency of each charge, the billing name and email on the payment, the reusable payment token that makes a renewal work, and with each charge the account's id, its short reference and Boosthis's own reference for the charge; a renewal also names the plan it renews. Processed in: Kingdom of Saudi Arabia. Bound by: nothing on our record yet. Transfer mechanism: None needed: the record shows it processes what it receives within the Kingdom.
- Resend — our processor. What it does: email delivery — the account emails listed under Account data — and receiving support mail, which Google Workspace passes on to it for the support inbox. What reaches it: your email address, the subject, and the body of the message; and for mail written to Boosthis that Google Workspace passes on for the support inbox, the sender's address and name, the subject, the body and any attachments. Processed in: United States. Bound by: Data Processing Addendum. Transfer mechanism: The EU standard contractual clauses, Modules One to Three, and the UK addendum are part of its addendum; it also relies on the EU-US Data Privacy Framework and its UK extension.
- Anthropic — a processor reached on another recipient's account, not engaged by us directly. What it does: helps Boosthis write and improve its own rule book — drafting rules, writing each fix's version for each programming language, finding gaps and grouping related problems, and answering the owner's own questions on the admin page. Two companies sit in this path today: the call leaves Boosthis to an AI gateway operated by Replit, on Replit's own account and credential, and Replit passes it to Anthropic, whose Claude model generates the answer. Replit is also the hosting recipient listed separately; on this path it is the intermediary, and what it can see is the call itself. What reaches it: the text of our own rule book, which is ours rather than a customer's — rule titles, the conditions that decide when a rule applies and the detector patterns behind them, plus the prescriptive fix text on the drafting and review calls that cannot work without it — and anonymous totals pooled across projects, as labels and numbers, never one project's data on its own; and, when the owner asks a question on the admin page, a summary of the service in labels, counts and dates — how many projects, accounts and keys there are, and the kinds of open alerts and recent crashes — with each project shown only as a numbered stand-in, never by name. It receives no account details, no app's own readings, no code, and nothing a customer or their AI tools wrote: no question to the Ask Boosthis assistant, which is switched off for customers and refused on the server; no project's name; and no rule wording a customer's AI proposed until a person at Boosthis has approved it into the rule book. Anthropic's published terms for its API say what it receives is not used to train its models. Processed in: United States. Bound by: nothing on our record yet. Transfer mechanism: Not yet settled: it would be covered through Replit's addendum, which is not yet shown to bind. Action we owe: Settled by the Replit action, or by opening Boosthis's own Anthropic account and accepting its Commercial Terms and data processing terms, dated: until one of those is shown, nothing on our record binds this company for us either.
- Replit — our processor. What it does: hosting and the managed PostgreSQL database, and the AI gateway in front of Anthropic. What reaches it: everything this document describes as stored: account data, telemetry, and the operational database as a whole. Processed in: United States. Bound by: nothing on our record yet. Transfer mechanism: Not yet settled. Its addendum includes the EU standard contractual clauses, Modules Two and Three, and provides for the UK addendum — once it is shown to bind. Action we owe: Confirm from the Replit account's billing page that it is on one of Replit's own Pro or Enterprise plans, so that Replit's Commercial Agreement and the addendum it incorporates apply, or obtain the addendum some other way; then record the evidence here.
- Google Cloud — a processor reached on another recipient's account, not engaged by us directly. What it does: backup storage — the routine encrypted database backups described under Retention. What reaches it: a copy of the operational database, in a private bucket. Processed in: United States. Bound by: nothing on our record yet. Transfer mechanism: Not yet settled: it would be covered through Replit's addendum, which is not yet shown to bind. Action we owe: Settled by the Replit action: until Replit's addendum is shown to bind Replit for us, nothing on our record binds this company for us either.
- Expo — our processor. What it does: phone notifications — passing each serious-problem notification from Boosthis to Apple's notification service, for an iPhone whose owner turned notifications on in the Boosthis phone app. What reaches it: the push address of each iPhone that turned notifications on, and each notification: the kind of problem, such as "New crash in production", and an opaque reference, never a project name or anything about the problem itself; when notifications are turned on, the phone app asks Expo for that push address, handing it the phone's Apple notification address, an installation identifier and the app's identifiers, and Expo sees the network address that request comes from. Processed in: United States. Bound by: Terms of Service, section 3.2 (GDPR). Transfer mechanism: The EU standard contractual clauses, Module Two for its processing on our behalf and Module One for its own, are part of its terms; it also self-certifies to the EU-US Data Privacy Framework and its UK and Swiss extensions.
- Apple — not established. What it does: phone notifications — Apple's push notification service, which delivers each notification to the iPhone it is addressed to; Boosthis reaches it only through Expo. What reaches it: the Apple notification address of each iPhone that turned notifications on, which Apple issued to that phone itself, and each notification as Expo hands it over: the kind of problem and an opaque reference. Processed in: United States. Bound by: nothing on our record yet. Transfer mechanism: Not yet settled. Action we owe: Read what the Apple Developer Program License Agreement says about the Apple Push Notification service and the data it carries, and record whether it binds Apple to use a notification only to deliver it.
- Google Workspace — our processor. What it does: receiving email — the mail service for the boosthis.com domain, which receives every message sent to an address there, including the support address, and passes support mail on to Resend for the support inbox. What reaches it: each message sent to a boosthis.com address: the sender's address and name, the subject, the body and any attachments; a copy of each support message stays in the owner's mailbox there with no deletion schedule, and a reply written from that mailbox rather than from the app is sent through it too. Processed in: United States. Bound by: Cloud Data Processing Addendum. Transfer mechanism: The EU and UK standard contractual clauses, which the addendum applies to transfers of European data. It names nothing for a transfer out of the Kingdom. Action we owe: Confirm in the Workspace Admin Console which edition the account is on, that the Cloud Data Processing Addendum applies to it, whether a data region is set, and which notification address Google's notices go to.
- sccc — our processor. What it does: the next host — the servers, the database and the backups of the Boosthis service once it moves to sccc; until that day they stay with Replit and Google Cloud, above. What reaches it: from the day the service moves, everything Replit and Google Cloud hold for it today: account data, telemetry, the operational database as a whole and its backups; nothing before that day. Processed in: Kingdom of Saudi Arabia. Bound by: Subscription Agreement. Transfer mechanism: None needed: its agreement keeps what its offerings hold within the Kingdom.