Every company that touches your data - and exactly what each one does
We list every sub-processor by name, the data they handle, the region they operate in, and a direct link to their data-processing or privacy terms. Material changes are notified at least 30 days in advance.
This register lists service providers, including conditional integrations and AI providers. A listing does not mean every provider receives every merchant’s data. Stripe also acts as an independent controller for some processing under its own terms. This register is maintained in accordance with our obligations under the Data Processing Agreement.
Listed providers 13 total
Vercel
Hosting- When used
- Hosting; Web Analytics and Speed Insights only with consent
- Purpose
- Frontend hosting, content delivery, Web Analytics (with consent) and Speed Insights
- Data
- HTTP request metadata, IP addresses, authenticated session cookies, form submissions, web usage and performance measurements
Render
Hosting- When used
- Application and database hosting
- Purpose
- Application hosting and PostgreSQL database
- Data
- All application data (encrypted at rest and in transit)
Cloudflare
Storage- When used
- Storage and bot protection where used
- Purpose
- Object storage (R2, including voucher assets and private handover/records exports) and bot protection (Turnstile)
- Data
- Uploaded files; private export packages and temporary archive snapshots; user interaction signals for bot detection. Package retention and signed-link expiry are separate.
Stripe
Payments- When used
- Subscription billing or connected voucher payments
- Purpose
- Payment processing and subscription billing
- Data
- Payment card details, billing address, transaction history
Resend
Email- When used
- When transactional messages are sent
- Purpose
- Transactional email delivery
- Data
- Recipient name, email address, email content
Twilio
Identity- When used
- When phone verification or enabled SMS delivery is used
- Purpose
- Phone verification (SMS OTP) and Phone Sales payment-link SMS delivery
- Data
- Phone number, verification codes, payment-link SMS delivery metadata
Sentry
Errors- When used
- Necessary errors; performance only with consent; session replay disabled
- Purpose
- Error monitoring and application performance
- Data
- Limited error traces and technical metadata; performance measurements with consent; no session replay. EU storage; other processing locations follow provider terms
PostHog
Analytics- When used
- Analytics only with consent; session recording disabled
- Purpose
- Product analytics (with consent)
- Data
- Usage events, session data, device metadata
Google Cloud
AI- When used
- Conditional AI tooling; merchant generation excluded from launch
- Purpose
- Configured AI image generation (Imagen) and prompt refinement (Gemini); merchant generation is not a launch feature
- Data
- Design prompts, generated images
OpenAI
AI- When used
- Conditional fallback; not active by default
- Purpose
- Configured AI image generation fallback (gpt-image-1); not active by default and not a merchant launch feature
- Data
- Design prompts, generated images
Xero
Accounting- When used
- Only when connected by the merchant
- Purpose
- Accounting integration (when enabled by merchant)
- Data
- Voucher financial data, journal entry amounts and dates
Freshdesk
Support/Ticketing- When used
- When an authenticated merchant submits a support ticket
- Purpose
- In-app support ticket creation for authenticated merchants
- Data
- Merchant name, email, tenant ID, ticket content
QuickBooks Online
Accounting- When used
- Only when connected by the merchant
- Purpose
- Accounting integration (when enabled by merchant)
- Data
- Voucher financial data, journal entry amounts and dates
Regions summarise the recorded service setup; they are not exclusive data-residency guarantees or a choice of hosting region. Provider terms may describe additional processing locations.
Quick summary by region
| Feature | Sub-processors | What they hold |
|---|---|---|
| AU / NZ | Xero | Voucher financial data, journal entries (when integration enabled) |
| Singapore | Render | Application hosting and PostgreSQL database |
| United States | Stripe, Resend, PostHog, QuickBooks, Twilio, Google Cloud, Freshdesk, OpenAI (fallback only) | Payments, transactional email, analytics, OTP, support tickets, AI prompts |
| European Union storage | Sentry | Limited error data; consented performance data. Other processing locations follow provider terms. |
| Global edge | Cloudflare, Vercel | Frontend hosting and request handling (Vercel); R2 object storage, bot protection signals, partner-export archives (Cloudflare) |
Swipe sideways for the full comparison
How we manage changes
Adding a sub-processor
We assess the applicable agreement, actual account coverage, processing locations and safeguards before appointing a provider for merchant data. The links identify each provider's published data-processing or privacy terms. Some providers incorporate their DPA into online terms; others require separate acceptance. A listing does not itself certify a particular jurisdiction or processing purpose.
Removing or replacing a sub-processor
We give affected merchants at least 30 days in advance for planned additions or replacements, including the provider's role and locations. We keep this register current when a provider is removed.
Objecting to a change
Reasonable data-protection objections that cannot be resolved allow exit from the affected service without penalty, a refund of unused prepaid subscription fees for that service and an orderly handover. Questions can be sent to privacy@vouchergrid.com.
Document review and change history
- Version date
- Changes in this revision
- First-launch provider register; Sentry EU storage verified and optional telemetry distinguished from necessary errors.
Earlier development drafts are not customer acceptance records. Contact privacy@vouchergrid.com for a copy of the version associated with your account.