Legal
Subprocessors
The companies that handle personal data on our behalf, what each of them does, and where it is.
Version 1 · draft, not yet in force
A subprocessor is a company we use to run revoo.me that handles personal data on our behalf. Article 28(2) of the GDPR requires us to tell the businesses we work for who they are, and to give notice before the list changes.
This page has its own address because it changes more often than the documents that reference it. The data processing agreement incorporates it by reference, so a change here is announced rather than requiring a new signature.
The current list
| Provider | What it does for us | Where | Transfers outside the EEA |
|---|---|---|---|
| Railway | application hosting, PostgreSQL database, Redis, object storage | United States | standard contractual clauses, Art. 46(2)(c), in Railway's DPA |
| Vercel | frontend hosting and server-side rendering, web analytics, speed insights | United States | standard contractual clauses, Art. 46(2)(c), in Vercel's DPA |
| Stripe | subscription billing, checkout, customer portal, invoices | Ireland, with United States support access | standard contractual clauses, Art. 46(2)(c), in the Stripe DPA |
| Infobip | email and SMS delivery for transactional messages | Croatia | none — inside the EEA |
| Cloudflare | the Turnstile challenge on the booking form and on sign-in | United States | standard contractual clauses, Art. 46(2)(c), in Cloudflare's DPA |
| Google sign-in for members of staff | United States | standard contractual clauses, Art. 46(2)(c), in the Google Cloud DPA |
Infobip is the one provider on this list with no Chapter V question: the messages your clients receive are delivered from inside the European Economic Area.
What each of them actually sees
- Railway holds the database, and therefore everything in it. It is the provider with the broadest technical access and the one our security measures are principally aimed at.
- Vercel serves the pages. It sees the requests that reach them, and — through Web Analytics and Speed Insights — cookieless page-view and performance data.
- Stripe sees the workspace owner's billing details. It never sees client records. Card details never reach us at all.
- Infobip sees the recipient's address and the content of the message being sent to them.
- Cloudflare sees the request that submits a booking form or a sign-in, for the duration of the challenge.
- Google sees only the sign-in itself, and only for members of staff who choose to use it.
None of them is permitted to process the data for its own purposes.
How this list changes
Before a provider is added or replaced we publish the change here and notify workspace owners at least 30 days in advance. A workspace owner may object within that period on reasonable data protection grounds; if the objection cannot be resolved, they may terminate the affected part of the service and be refunded any period paid for and not used.
Removing a provider needs no notice.
Every version of this page carries a number and the date it took effect, and earlier versions stay published at their own addresses, so it can always be shown which list was in force on a given day.
Our details
Our registration details and the mailbox for data protection requests are not published yet. Until they are, this document is a draft.