Draft. A lawyer has not read this page yet, so it isn't in force. Highlighted passages are gaps for counsel to fill.
Subprocessors
These companies run parts of the service for us and may process personal data while they do.
| Company | What it does | Data it handles | Region |
|---|---|---|---|
| Cloudflare | Serves this site and proxies API traffic | IP addresses and request metadata | To be confirmed |
| RunPod | Runs the GPU workers that process your files | Your files, while each job runs. Temporary copies are deleted when the job ends | To be confirmed |
| Railway | Hosts the API gateway | Account and usage metadata in transit. Files never pass through it | To be confirmed |
| Supabase | Hosts the database and sign-in, and stores uploaded and output files | Account, usage and ledger records, your GitHub identity, and your files, until they are deleted. Deletion starts at 7 days and normally finishes within a further day. | To be confirmed |
| Stripe | Takes payment and handles tax through Managed Payments, where Link is the seller shown | Billing details, card details, and payment records | To be confirmed |
| GitHub | Identifies you at sign-in, if you choose GitHub | Your GitHub identity | To be confirmed |
For the owner: fill in regions and contracting entities once projects exist, and add the destination of operational alerts if it receives personal data.
For counsel: how customers are told about a new subprocessor, and whether the providers Supabase itself stores files with need naming here.