Sub-processors
Last updated: August 24, 2026
These providers process data for Repro It to operate the website and managed Cloud. Each provider receives only the data needed for its role. Repro It will give account holders at least 30 days of notice before it adds or replaces a sub-processor, as described in the DPA.
| Provider | Role | Data |
|---|---|---|
| Fly.io | Managed Cloud hosting, network termination, and isolated replay compute | Service traffic, account and workflow data in transit, and one authorized Repro during bounded managed execution |
| Neon | Managed PostgreSQL database | Account, organization, project, service, workflow, authorization, quota, and audit metadata |
| Cloudflare | Public website delivery, page performance analytics, and encrypted object storage | Public website requests, page performance metrics, page-load identifiers, referrer URLs, and encrypted verified Repro objects |
| WorkOS | Hosted authentication, Magic Auth, social login, and Enterprise SSO | Email, identity, organization, session, authentication, and security data |
| Google Fonts | Public website font delivery | Public website font requests and related network data |
Source access
Repro It uses standard Git for source access. A developer operation uses the Git credential helper or SSH agent in the developer's environment. Repro It does not require a Cloud-side GitHub, GitLab, or Bitbucket integration.
Questions or objections
Email agho@reproit.com. The objection process is in the DPA.