Sub-processors

    Last updated: July 5, 2026

    The third parties Refactyl uses to deliver its code-migration service. This list supplements the Data Processing Agreement. Customers with an active DPA are notified of additions or replacements at least 14 days in advance.

    Self-hosted (BYO-cloud) Enterprise customers run Refactyl entirely in their own cloud: compute, database, Redis, and object storage all live inside their environment, and none of the infrastructure sub-processors below apply.

    Core infrastructure

    All primary infrastructure runs on Amazon Web Services (US regions). Source code is encrypted in transit and at rest and deleted on handoff.

    Sub-processorPurposeData processedLocation
    Amazon Web Services: ComputeRuns the API and migration workerAll customer data in transit; migration sandboxes are ephemeral and isolatedUnited States
    Amazon Web Services: RDS (PostgreSQL)Accounts, migration metadata, logsUser PII, job metadata (no retained source code, purged on handoff)United States
    Amazon Web Services: ElastiCache (Redis)Job queue, sessions, rate limitingJob payloads, session tokens (no source code)United States
    Amazon Web Services: S3Temporary migration artifact storageSource code + output, encrypted (AES-256-GCM); deleted on handoffUnited States

    Processing, payments & communications

    Sub-processorPurposeData processedLocation
    OpenAI, L.L.C.LLM inference for AI-assisted transformationBatches of source-code files as prompt context (API inputs not used for training)United States
    Paddle (Market Ltd / Inc.)Payments & Merchant of Record; invoicingBilling name, email, payment method (no source code; no card data stored by Refactyl)UK / EEA / US
    ResendTransactional & lifecycle emailRecipient email, name, message content (no source code)United States
    PostHog, Inc.Product analyticsPseudonymous user ID, event names, browser metadata (no source code)United States
    Google LLC (Analytics)Web analyticsCookie-based visitor analytics (no source code, no logged-in PII)United States
    Cloudflare, Inc.Turnstile CAPTCHA (homepage demo) & CDNIP address, browser fingerprint (no source code)Global (US)

    Enterprise and self-hosted deployments can route LLM inference to Azure OpenAI, an on-premises model, or any OpenAI-compatible endpoint (via OPENAI_BASE_URL), eliminating the cross-border transfer of source code to OpenAI. Refactyl does not currently use a third-party error-tracking or APM sub-processor.

    Authentication providers

    Used only when a user chooses them. Refactyl receives profile data from these providers at the user's direction; they are not sent customer source code.

    Sub-processorPurposeData processedLocation
    Google LLC (OAuth)Optional “Sign in with Google”Name, email, avatar received at the user’s directionUnited States
    GitHub, Inc. (OAuth)Optional “Sign in with GitHub”; repo access to clone repos the user migratesName, email, avatar; repo contents only for repos the user explicitly migratesUnited States

    Need the paperwork?

    A signed DPA (with the sub-processor annex and transfer mechanisms) is available for Enterprise and Big Migration customers.

    Read the DPA summary, see our security overview, or request a signed copy.