Sub-processors
InvoHub engages the following sub-processors to deliver our service. Each sub-processor is contractually bound to data processing standards equivalent to ours, and is assessed for security, compliance, and EU data residency posture.
Current sub-processors
| Sub-processor | Purpose | Location | Data accessed | Safeguards |
|---|---|---|---|---|
| Anthropic | AI invoice extraction (Claude) | US | Invoice content (PDFs, text) | Zero data retention configured; no model training |
| AWS | Object storage (S3) for invoice files | EU (Frankfurt) | Encrypted invoice files | AES-256, EU-only buckets, SCC 2021 |
| Neon | Managed PostgreSQL database | EU (Frankfurt) | Account, tenant, invoice metadata | Row-level security, encrypted at rest |
| Gmail OAuth + Pub/Sub for mailbox watching | EU (multi-region) | Gmail metadata + message IDs | OAuth scopes minimized to gmail.readonly | |
| Microsoft | Outlook OAuth for mailbox access | EU | Outlook metadata + message IDs | Microsoft Graph scopes minimized |
| Replit | Application hosting | EU | Application runtime | EU-region deployment, SCC 2021 |
Notification of changes
We notify customers at least 30 days before adding or replacing a sub-processor. Notification is sent to the email address associated with the account.
Object to a sub-processor
If you object to a new sub-processor, contact hello@invohub.eu before the 30-day notice period ends. We will work with you in good faith; if no resolution is reached, you may terminate the affected service.