Sub-processors
Last updated: 16 October 2026
These are the third parties that process personal data on behalf of InvoiceFlow. Each is bound by a data-processing agreement or equivalent terms. We update this list before adding a new sub-processor that handles customer data.
Current list
| Provider | What for | Data involved | Location | Terms |
|---|---|---|---|---|
| Google Cloud Platform | Application hosting (Cloud Run), secrets, logs | All service data in transit; request logs (IP, user agent) | India (Mumbai, asia-south1) | View |
| Neon | Primary PostgreSQL database | All account, client, invoice and payment records | India (AWS Mumbai, ap-south-1) | View |
| Upstash | Redis queue for background jobs | Transient job identifiers | India (AWS Mumbai, ap-south-1) | View |
| Cloudflare (R2) | Storage for Compliance Vault documents | Files you upload (e.g. FIRC, contracts, tax documents) | Cloudflare global network (automatic region) | View |
| Clerk | Sign-in, sessions and identity | Name, email, profile image, sign-in metadata | United States | View |
| Razorpay | Subscription and add-on payments | Name, email, payment status; card/UPI details are entered with Razorpay and never reach us | India | View |
| Resend | Sending invoice, reminder and account emails | Recipient name/email and email content | United States | View |
| OpenAI | AI invoice drafting, contracts, receipts and collections drafts (only when you use them) | The text or image you submit and minimal invoice context | United States | View |
| ExchangeRate-API | Foreign-exchange rates | None (currency codes only) | Global | View |
Changes and objections
We give customers at least 30 days' notice by email before a new sub-processor starts processing customer data. If you object on reasonable data-protection grounds, contact us within that period and we will work with you on an alternative, and you may delete your account if we cannot agree.