Atlas
Trust
Subprocessors
PairRail uses the providers below to operate Atlas. This list is what a vendor questionnaire means by subprocessors for the PairRail-hosted service. Seller connectors you turn on send data to your accounts. Those vendors are listed separately.
Always on
| Provider | What they do for Atlas | Where |
|---|---|---|
| Google Cloud / Firebase | Authentication, Hosting, Cloud Run API and protocol gateway, durable catalog state in Cloud Storage, Vertex AI / Gemini for extraction you request | United States (us-central1) |
| Cloudflare | DNS, CDN, and optional edge telemetry (D1) plus feedback attachments (R2) | Global edge |
| Resend | Transactional email such as sign-in codes and workspace notices | Per Resend’s infrastructure |
When you subscribe to Atlas
| Provider | What they do for Atlas | Where |
|---|---|---|
| Dodo Payments | Checkout and subscription billing for PairRail plans. Card data stays with Dodo. We receive entitlement and subscription metadata. | Per Dodo’s infrastructure |
Identity providers you choose
If you sign in with Google or GitHub, that provider authenticates you under its own terms. PairRail receives the account identifiers described in the Privacy Policy.
Optional seller connectors
These run only when you save credentials in Connect stack. Tokens stay in your workspace. PairRail calls the API you named. The destination account is yours, not a PairRail tenant.
- Stripe or Chargebee for catalog pull into a draft you still publish.
- HubSpot for quote and access-request writeback, using a private app token you paste.
- Your merchant account or signed webhook for settlement when a quote executes on Pro.
Salesforce writeback is on the waitlist and is not a live subprocessor.
Changes
We will update this page when a material provider is added or removed. Enterprise customers who have asked to be notified can email [email protected].
Formal legal entity name will be added when finalized. Related: Data Processing Terms and Security.