Sub-processors
The other companies that handle DreamSheets customer data when we run the service, what they do, and where they do it. Last updated 24 September 2026.
What this page is
When a production uses DreamSheets, the production company is the controller of its crew and schedule data and we are its processor. Some of the work of running the service is done by other companies on our instructions. Those companies are our sub-processors, and each has a contract with us that covers the same protections we give your data. This page lists all of them — there are two.
We do not use analytics, advertising or tracking tools on the service, and no other third party receives customer data from us.
Who we use
| Sub-processor | What they do for us | Where | Their data processing terms | Used since |
|---|---|---|---|---|
| Supabase | The managed PostgreSQL database that holds production data, and Supabase Auth, which handles account sign-in and passwords | United Kingdom (AWS London, eu-west-2) | Data Processing Addendum | August 2026 |
| Hostinger | The UK server the application runs on, and the email service that sends invitations, password resets and other account email | United Kingdom | Data Processing Addendum | July 2026 |
What each of them holds, and for how long, is set out in our privacy notice. Both sub-processors process customer data only inside the United Kingdom. If that ever changes, we'll update this page and put the transfer safeguards in the notice before anything moves.
Other providers
TLS certificates for the website are issued by Let's Encrypt. That service sees our domain names only, never any personal data, so it is not a sub-processor.
Changes to this list
We'll tell customers by email at least 30 days before a new sub-processor starts processing customer data, and update this page at the same time. A customer can object to a new sub-processor in that period; if we can't resolve the objection, the customer can end the agreement without penalty.