Backify
Service providers and subprocessors
Pre-release provider register, version 2026-10-28. Contracting entities, activated services, processing countries and transfer safeguards must be verified in each production processing schedule.
Providers depend on the features and connections enabled. A customer’s own direct provider contract and an independent controller relationship are different from a Backify subprocessor relationship.
| Provider | Purpose | Scope to confirm |
|---|---|---|
| Microsoft Azure | Hosting, database, key management, storage, diagnostics and selected AI services | Deployed resource regions, control-plane records, support access and contractual entity |
| Resend | Transactional email when configured | Verified sending domains, message retention, processing locations and provider agreement |
| GitHub | Connected source repositories, builds and deployment workflows | Customer connection, repository permissions, account relationship and relevant processing terms |
| Stripe | Hosted checkout, invoicing, tax IDs and payment management | Applicable controller/processor roles and Stripe’s service-specific terms |
| Customer-selected AI and integration providers | Requested model inference and integrations | Exact provider, data categories, retention, region and transfer terms before activation |
Data location
A selected application region applies to its deployed resources. Account, billing, audit, support and control-plane records can have different boundaries. Customer Azure hosting does not move Backify’s control plane into the customer’s subscription. No specific control-plane location or EEA-only processing claim is published until the deployed inventory and contracts are verified.
Changes and evidence
The approved processing schedule must list authorized providers and advance notice arrangements. Request current provider evidence and transfer safeguards through support before submitting data subject to residency restrictions.