Current subprocessors
| Provider | Purpose | Region | Data category | Status |
|---|---|---|---|---|
| Supabase | Managed Postgres database, authentication, file storage, realtime | United States | Workspace data, account data, item photos | Active |
| Cloudflare | Edge compute, content delivery, DDoS protection | Global edge | Application traffic metadata | Active |
| Payment provider | Subscription billing, invoicing, tax handling | United States and European Union | Billing contact, payment method token | Planned |
| Email provider | Transactional notifications, weekly briefs, password resets | United States | Workspace user email, notification content | Planned |
| Analytics provider | First-party product analytics and performance monitoring | United States or European Union | Pseudonymous usage events, performance timings | Planned |
Status reflects what is wired up today. Items marked Planned are scoped vendors that ReturnGuard expects to onboard and will activate after a security review and contract signing.
How we evaluate a new subprocessor
- Security review of the vendor's controls and incident history.
- Contractual data protection terms and, where relevant, transfer clauses.
- Scoping the minimum data the vendor needs to perform its function.
- Notification to workspace owners before activation when personal data is involved.
Notifications and objections
Workspace owners can subscribe to subprocessor change notifications by emailing support@returnguard.net. If a Customer reasonably objects to a new subprocessor on data protection grounds, the parties will discuss in good faith; if no resolution is found, the Customer may terminate the affected subscription as described in the Terms of Service.
These pages describe how ReturnGuard operates today. They are written in plain language for our customers and are not legal advice. For contractual questions, contact support@returnguard.net.