Legal Data
Sub-processors
The four companies that receive personal data on our behalf, each with its legal entity, what it gets, why, and a link to its own data processing agreement.
Four. Named, with what each one receives and the agreement it operates under, because a procurement review that cannot find this page assumes the list is longer than it is.
None of them receives anything from inside your terminals. There is no sub-processor that could, because we never have that data in the first place.
The list
Stripe — payments
Entity: Stripe, LLC (Americas) or Stripe Payments Europe, Limited (elsewhere), depending on where your account sits. Receives: your email address, whatever billing name, address and tax id you enter at checkout, and your card details — which go from your browser to Stripe directly and never pass through our servers. Purpose: taking payment, running the billing portal you cancel from, calculating VAT and sales tax, and telling our licence server when a subscription starts, renews or ends. Where: United States and Ireland. Terms: stripe.com/legal/dpa · stripe.com/privacy
Stripe is also an independent controller for its own fraud prevention. That part is theirs, governed by their policy, and is the reason a payment processor keeps a transaction record even after we have deleted everything on our side.
Resend — licence emails
Entity: Plus Five Five, Inc., trading as Resend, San Francisco, California. Receives: your email address and the message body — which contains your licence key. Purpose: delivering the one email that carries your key, when a trial starts and when a purchase completes. There is no newsletter and no marketing list here; this is transactional only. Where: United States. Terms: resend.com/legal/dpa
Resend’s DPA incorporates Standard Contractual Clauses and states EU–U.S. Data Privacy Framework compliance.
Railway — hosting and database
Entity: Railway Corporation. Receives: everything the licence server stores — the licences, machines, trials and events tables described in the Privacy Policy — plus platform request logs which contain IP addresses and user agents. Purpose: running the licence server and its Postgres database. Where: United States. Terms: railway.com/legal/dpa
Railway is the widest-reaching entry on this page. The database is reached over Railway’s private network rather than the public proxy, and we do not disable certificate verification to make a connection work — the credential travelling over it is the one that can mint licences.
GitHub — release downloads and updates
Entity: GitHub, Inc. (United States) or GitHub B.V. (Netherlands). Receives: your IP address and user agent when Dispatch downloads an installer or checks the release feed. Not your email, not your key, not your fingerprint. Purpose: hosting installers and serving the auto-update feed. Where: United States. Terms: GitHub Privacy Statement
This is a plain HTTP download. It is on the list because your machine talks to GitHub every four hours while Dispatch is running, and a list that omitted that would be incomplete in a way somebody would eventually notice.
This website’s host
TODOthe host serving this site, once it is deployed — setdocs/compliance-checklist.md in src/lib/site.ts
The marketing pages and documentation are static and set no cookies. The account area runs server-side and sets one session cookie — see Cookies.
What is deliberately not on this list
- No analytics provider. There is none.
- No error tracking or crash reporting, in the app or on the site.
- No customer support platform. Support is email, and the mailbox is
TODOthe support address — set
LEGAL.contact.supportinsrc/lib/site.ts. - No CDN in front of the licence server. It is reached directly.
- No advertising or marketing tooling of any kind.
Each of those is a company that would otherwise have to appear here. They are absent because they are not used, not because the list has been trimmed.
Changes to this list
We update this page and change the date at the top whenever a sub-processor is added or removed. If you have a data processing agreement with us, you get the notice period it specifies before a new one starts processing.
For anyone without one: adding a sub-processor is a material change to the Privacy Policy, so it is emailed to the address on your licence before it takes effect.
A DPA for business buyers
TODOwhether a signable DPA exists yet — setdocs/compliance-checklist.md in src/lib/site.ts
If your procurement process needs one, write to
TODOthe privacy address — set LEGAL.contact.privacy in src/lib/site.ts and say so. Telling you
where that stands is more useful than an unsigned template on a page.