Companies that receive Boosthis data
Notice before a new company begins receiving data: 14 days. Before another company starts receiving account data or telemetry, it is named here 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 instead of watching. Double opt-in email change notices are available without an account at boosthis.com/trust. An additional Atom feed is available at https://www.boosthis.com/subprocessors.xml.
To object to a new company within the notice period, write to support@boosthis.com. We may not be able to keep serving you without it, and we will say so rather than let you find out.
The list
This is every outside company Boosthis engages. Three destinations are deliberately absent because you chose them rather than us — an alert webhook you configure, a chat workspace you connect, and an AI assistant you connect — and those are described in the Terms.
Moyasar
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
On whose instructions: Moyasar is not only our processor, and no term could make it one. It is a payment institution licensed and supervised by the Saudi Central Bank, and the card data a buyer enters through Moyasar's embedded form on Boosthis-hosted checkout is sent directly from the browser to Moyasar and handled under its own regulatory and card-scheme obligations — anti-money-laundering checks, fraud screening, chargeback handling and record keeping it must perform whatever we instruct. What it does for us on our instruction is narrow and named beside it: take the charge we ask for, and tell us whether it succeeded. Recording it as instruction-only would be a term neither side could keep. Its published terms.
Its own sub-processors: Moyasar publishes no sub-processor list. Its privacy notice describes disclosures to banks, card schemes, regulators and service providers in general terms, without naming them, so there is no list to read and no list to watch. This is a real gap in what we can tell a customer, not a finding about the provider: for a licensed payment institution it is the ordinary published posture in this market. None published. Because there is no list, a change to it is not something we could be told about or detect; what we can see is a change to the privacy notice itself, which is the source recorded above.
Onward transfer: Its privacy notice states that personal data is collected and processed within the Kingdom of Saudi Arabia in compliance with the Saudi PDPL. Nothing on this path is recorded as crossing a border, which is why this recipient carries no transfer basis above. Nothing we hand this recipient may leave the Kingdom without the recipient list and the transfer register saying so first. That is checkable rather than promised: the register's own guard fails when a recipient's processing location moves outside the Kingdom and no transfer basis is recorded beside it, and the published residency sentences are generated from this record rather than typed.
Acts as: an independent controller, acting under its own legal duties · Bound by: nothing on our record yet
How they were accepted: It acts as an independent controller under its own legal duties as a payment institution, and receives only account holders' payment details, which the processing agreement does not cover; no processor terms are claimed for it. Terms read: 2026-09-29.
Transfer mechanism: None needed: the record shows it processes what it receives within the Kingdom.
Resend
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
In-Kingdom alternative: none found.
On whose instructions: Resend publishes a Data Processing Addendum that applies to its customers by its terms rather than by signature, under which it acts as processor for the customer data it handles and processes it on the customer's documented instructions. Our instruction is the whole of what the recipient list says reaches it: deliver this one message to this one address, and hand the support mail Google Workspace passes on to it to the support inbox. There is no marketing path, no list upload and no second use to instruct it out of. Its published terms.
Its own sub-processors: Resend publishes a named sub-processor list at its own address, which is the strongest of the practices recorded here: the companies are named, not described by category, so a change is visible rather than inferable. Read on the date below; the list at that reading was entirely United States companies, which is also what the residency evidence above rests on. The list is published and dated by the provider. It is the provider's own page, not a commitment made to us, so what we rely on is our weekly re-reading of its list rather than a promise of notice. Its published list.
Onward transfer: Its addendum engages sub-processors under terms it undertakes to keep no less protective than its own, and its published list is where a change to them shows up. What it holds — account data, email metadata and logs — stays in the United States whichever sending region is used, so an onward move is a move between United States companies rather than into a new country. A sub-processor this recipient adds is an onward transfer of one address and one message, and it reaches a customer the same way our own list does: named on the published recipient page before it begins, on the notice period stated there. That is not left to somebody noticing — `subProcessorWatch.ts` re-reads the page above on a weekly clock, compares it with the digest recorded here, and puts a change on the operator's own alert surface until a human has read it and moved this entry.
Acts as: our processor · Bound by: Data Processing Addendum The terms.
How they were accepted: The addendum is incorporated into Resend's terms of service and binds on entering them, which our account did; it was accepted with those terms rather than countersigned. Terms read: 2026-10-04.
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
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
In-Kingdom alternative: one exists, but not on the path we use.
On whose instructions: Boosthis holds no agreement with Anthropic yet, and saying otherwise would be the cross-referencing this entry exists to remove. The call leaves us to Replit's AI gateway on Replit's own account and credential, and Replit passes it on — so the company we instruct is Replit, under the terms recorded on its entry below, and Anthropic is its sub-processor rather than ours. Anthropic publishes Commercial Terms and a sub-processor list of its own, and they are the right documents for the relationship; they are simply not a relationship we are a party to until Boosthis opens an Anthropic account of its own. What binds this path for a Boosthis customer is therefore Replit's instruction-only term, and what limits it in practice is the screening described in the safeguards above: the PII guard refuses the whole call before it is sent, and screens the answer again. Its published terms.
Its own sub-processors: Anthropic publishes a named sub-processor list at its own address, which forwards to its trust centre. That page is built by script in the reader's browser, so what this server reads there is the page's frame and not the list: the weekly watch can tell that the page still answers at that address and whether its frame changed, never that the list itself is unchanged. A person reads the list. Whatever the provider commits to on that page is a commitment to its own customers. We are not one yet, so no notice from it would reach us; a change here reaches us through the recipient we do contract with. Its published list.
Onward transfer: Every onward step on this path is already an onward step: what reaches Anthropic got there because Replit passed it on. Anthropic's published position is that it stores what it receives in the United States and may route a call to select countries in the United States, Europe, Asia and Australia; the Kingdom is not among them, which is why this entry certainly leaves the Kingdom and why which country actually processes a call is recorded above as unconfirmed rather than assumed. This is the one path where our recourse is at one remove, and it is written down rather than glossed: a change of model provider behind the gateway is Replit's to make, and what we hold is the right to be told through Replit's own sub-processor list and the option to stop using the gateway. The published claim that what the API receives is not used to train models is recorded against its source and its reading date, so it cannot quietly become folklore. Moving to an Anthropic account of our own, the step that ends the remove, is a key change rather than a release.
Acts as: a processor reached on another recipient's account, not engaged by us directly · Bound by: nothing on our record yet
How they were accepted: Reached on Replit's account, so what binds it is Replit's own agreement with it, which we are not a party to; that reaches us only through Replit's addendum. Terms read: 2026-11-17.
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
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
In-Kingdom alternative: none found.
On whose instructions: Replit publishes a Data Processing Addendum, forming part of the Commercial Agreement that its terms of service apply to Replit's own Pro and Enterprise plans, under which it processes customer content as a processor on the customer's documented instructions. Whether it binds Replit for us therefore turns on the plan, which the binding record below has not yet shown. This is the widest instruction of the five and the one worth stating precisely: our instruction to this recipient is to run the service — compute, the managed database, object storage and the gateway in front of the model — and everything the privacy policy describes as stored is inside it, because the service cannot run otherwise. Its published terms.
Its own sub-processors: Replit publishes a named sub-processor list at its own address. It is the most load-bearing of the five, because two of the other companies on our own list are reached through this one: the model provider behind the AI gateway, and the object storage behind the backups. A change to this page is therefore the change most likely to move something a Boosthis customer would care about. The list is published and dated by the provider, and its addendum is where any commitment about changing it lives. Because two of our recipients sit behind this one, our weekly re-reading of its list is the signal we actually act on. Its published list.
Onward transfer: Its addendum engages sub-processors under terms no less protective than its own and identifies them on the page above. Its geography documentation says a published app's compute, database and object storage are colocated in the geography chosen, which is what keeps an onward move from silently becoming a move to a new country: the geography is ours to choose, and it is North America today. Because this recipient's own list is where two of our recipients appear, a change to it is treated as a change to ours: the watch compares the page weekly against the digest recorded here, raises it on the operator alert surface, and it stays raised until a human has read the page and moved this entry. If a change means another company starts receiving customer data, it is named on the published recipient page before it begins, on the notice period stated there.
Acts as: our processor · Bound by: nothing on our record yet The terms.
How they were accepted: Replit's Data Processing Addendum forms part of its Commercial Agreement, which its terms of service apply to Replit's own Pro and Enterprise plans. Which plan this account is on cannot be read from inside the workspace, so the record does not yet show that the addendum binds Replit for us. Terms read: 2026-10-04.
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
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
In-Kingdom alternative: one exists, but not on the path we use.
On whose instructions: Boosthis holds no Google Cloud account and no agreement with Google. The backups are written through the host's App Storage, which is a facility of the hosting recipient above and reaches the bucket on the host's own credentials — so Google Cloud is that recipient's sub-processor, and our instruction runs through it. Google publishes processor terms for its own customers; we are not one, and recording their protections as ours would be borrowing somebody else's contract. Its published terms.
Its own sub-processors: Google publishes a named third-party sub-processor list at its own address. It covers a whole cloud platform, most of it unrelated to a private storage bucket, so a change on that page is weak evidence about this path specifically: the weekly re-reading treats one as a prompt to go and read, not as a finding that something about our backups has moved. Google commits to notice through that page for its own customers. We are not one, so the commitment is not made to us; what reaches us is the page itself, re-read weekly. Its published list.
Onward transfer: What reaches this recipient is a copy of the operational database in a private bucket, colocated by the host with the app's publishing geography — North America today. Google runs a Dammam region inside the Kingdom, so the provider has an in-Kingdom location that this path does not reach; that is recorded as an alternative above rather than as a safeguard here, because it is not one until the path changes. An onward move here is the hosting recipient's to make, and the same term applies as on its own entry: if it means another company starts holding a copy of the database, that company is named on the published recipient page before it begins, on the notice period stated there. The weekly watch reads this page and the hosting recipient's page both, because a change to our backups could show up on either.
Acts as: a processor reached on another recipient's account, not engaged by us directly · Bound by: nothing on our record yet
How they were accepted: Reached on Replit's account, so what binds it is Replit's own agreement with it, which we are not a party to; that reaches us only through Replit's addendum. Terms read: 2026-10-04.
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
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
In-Kingdom alternative: none found.
On whose instructions: Expo's terms of service make it a processor of personal data in what its customers submit, acting in the context of its services, and incorporate the EU standard contractual clauses for that processing. Our instruction is what this list says reaches it: deliver this one notification to the phone this one address belongs to. The same terms make it an independent controller for that data in aggregated or de-identified form, used to improve its own products, and that is recorded here rather than left out. Its published terms.
Its own sub-processors: Expo publishes a named sub-processor list at its own address, dated by Expo. It names Apple for sending push notifications, which this list names separately, and Google for the same purpose, which Boosthis never reaches because no Android build is released; the rest is Expo's own infrastructure and business tooling. Expo's terms choose the general written authorisation option of the standard contractual clauses, with one week's prior notice of a change to its sub-processors. What we rely on is our weekly re-reading of its list. Its published list.
Onward transfer: Expo hands each notification to Apple's notification service, which delivers it to the phone. Its terms cover an onward transfer with the standard contractual clauses, and its published list is where a change to the companies it uses shows up. A sub-processor Expo adds is an onward transfer of a push address and a notification, and it reaches a customer the same way our own list does: named on the published recipient page before it begins, on the notice period stated there. `subProcessorWatch.ts` re-reads the page above on a weekly clock and puts a change on the operator's own alert surface until a human has read it and moved this entry.
Acts as: our processor · Bound by: Terms of Service, section 3.2 (GDPR) The terms.
How they were accepted: The processor terms are part of Expo's terms of service and bind on entering them, which our Expo account did; they were accepted with those terms rather than countersigned. Expo publishes no separate processing agreement. Terms read: 2026-10-07.
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
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
In-Kingdom alternative: none found.
On whose instructions: The key Expo presents to Apple when it hands over a notification belongs to Boosthis's own Apple developer account, so the relationship with Apple's notification service is ours, under the Apple Developer Program License Agreement. What that agreement says about how Apple handles a notification has not been read for this record, so nothing here claims Apple acts only on our instructions. Its published terms.
Its own sub-processors: Apple publishes no sub-processor list for its push notification service, so there is no list to watch. None is committed to: with no published list, a change to the companies Apple uses would never be announced to us.
Onward transfer: Apple publishes nothing about passing a notification on: it is delivered to the phone its address belongs to, or discarded when it expires. If what reaches Apple ever starts reaching another company, that company is named on the published recipient page before it begins, on the notice period stated there.
Acts as: not established · Bound by: nothing on our record yet
How they were accepted: Our Apple developer account accepted the Apple Developer Program License Agreement, which governs the notification service. Whether it contains terms that bind Apple for what reaches it has not been read for this record. Terms read: 2026-10-07.
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
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
In-Kingdom alternative: none found.
On whose instructions: Google's Cloud Data Processing Addendum is part of the Workspace terms and makes Google the customer's processor for the mail it holds: the customer instructs it to process that data only to provide, secure and monitor the service, and as the customer's own use of the service specifies. Our instruction is what this entry says reaches it: receive mail for the domain, pass support mail on to Resend, and keep the owner's mailbox until the owner deletes from it. Its published terms.
Its own sub-processors: Google publishes a named list of the third-party sub-processors Workspace uses, at its own address. It covers every Workspace service, not only mail, so a change on that page is a prompt to go and read rather than a finding that something about our mail has moved. Google's addendum commits to telling the customer at least 30 days before a new sub-processor starts, at the notification address the account's administrator sets, and lets the customer object by ending the agreement within 90 days. Whether that address is set has not been checked, so we also rely on our weekly re-reading of its list. Its published list.
Onward transfer: The addendum lets Google process customer data in any country where it or its sub-processors have facilities, unless a data region is set, and binds each sub-processor by written contract to use the data only for the work given to it, with Google remaining liable for it. So an onward move can be to another country without anything on our side changing. If what reaches Google starts reaching another company because of anything we set up — a forwarding rule, another group member, a connected app — that company is named on the published recipient page before it begins, on the notice period stated there. Google's own list is re-read on the weekly clock like the others.
Acts as: our processor · Bound by: Cloud Data Processing Addendum The terms.
How they were accepted: The addendum is incorporated into the Workspace terms of service and binds on entering them, which the domain's Workspace account did; it was accepted with those terms rather than countersigned. Terms read: 2026-10-10.
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
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
On whose instructions: sccc's subscription agreement says it accesses or uses what a customer runs on or uploads to its services only as far as needed to maintain or provide them, or as the law requires, and that the customer keeps every right in it. Asked for a processing agreement, its support team answered in writing that cloud customers act as the data controllers for what they host, and pointed to its published privacy policy. Our instruction to it is the one we give the current host: run the service, its database and its backups. Its published terms.
Its own sub-processors: sccc publishes no sub-processor list. Its subscription agreement says that anything offered outside the Kingdom comes from an Alibaba Cloud entity or another party under their own terms, and names none of the companies sccc itself relies on inside the Kingdom, so there is no list to read and none to watch. None published. With no list, a change to the companies sccc relies on would not be announced to us; what we can see is a change to its published agreement and privacy policy.
Onward transfer: Its subscription agreement keeps all data its offerings hold within the Kingdom of Saudi Arabia, subject to limited exceptions under applicable law, and lets it disclose content where the law, legal process or a lawful request from a government body requires it. Its privacy policy says personal data may be transferred abroad only in certain circumstances, under the Saudi Personal Data Protection Law. Nothing we hand this recipient may leave the Kingdom without the recipient list and the transfer register saying so first. That is checkable rather than promised: the register's own guard fails when a recipient's processing location moves outside the Kingdom and no transfer basis is recorded beside it, and the published residency sentences are generated from this record rather than typed.
Acts as: our processor · Bound by: Subscription Agreement The terms.
How they were accepted: sccc's published subscription agreement binds on opening an account, which Boosthis did; it was accepted with the account rather than countersigned. sccc offers no separate processing agreement: asked for one, its support team pointed to its published privacy policy. On 16 November 2026 the owner of Boosthis accepted sccc's published agreement and privacy policy as the terms for what it will hold. Terms read: 2026-11-16.
Transfer mechanism: None needed: its agreement keeps what its offerings hold within the Kingdom.