These terms describe how PairRail processes Customer Content when you use Atlas. They supplement the Terms of Use and the Privacy Policy. They are not a substitute for an Enterprise order form.
1. Roles
You (the seller organization) are the controller of Customer Content you submit: catalogs, prices, evidence, workspace members, agent credentials metadata, and integration tokens. PairRail is the processor of that Customer Content. We process it only to provide Atlas, as you instruct through the product, or as required by law.
Account and billing data needed to run your PairRail subscription is processed as described in Privacy. Card numbers are handled by our payment partner, not stored by PairRail.
2. What we process
- Workspace and catalog state (offers, versions, publication, policy).
- Extraction inputs and model output when you run AI extraction or Deep verification. Anthropic (Claude, through the Anthropic API) and Gemini on Google Cloud Vertex AI run these. Groq and Cloudflare Workers AI also run extraction when needed (see Subprocessors).
- Protocol projections you choose to publish (MCP, UCP, ACP, A2A, UAP, and related feeds).
- Quotes, access requests, deal-desk items, and audit events.
- Optional connector tokens and the API payloads those connectors send or receive.
- Operational telemetry and feedback as described in Privacy.
3. Instructions we will not take
We do not sell Customer Content. We do not use your price books to train a general public model. Extraction calls a configured provider for your workspace only. Published protocol endpoints expose what you publish. That is your instruction, not a PairRail listing.
4. Subprocessors
We use the providers on the Subprocessors page. Optional connectors you enable send data to your Stripe, Chargebee, HubSpot, merchant, or webhook endpoint.
5. Location and transfers
Default processing is in the United States on Google Cloud (us-central1), with Cloudflare at the edge, and other providers as listed.
If you access Atlas from another country, Customer Content may be transferred to those locations.
A different residency is an Enterprise contract term, not a self-serve toggle.
6. Security
We apply the administrative and technical measures described on the Security page. That page is a posture summary, not a SOC 2 report or a warranty.
7. Retention and deletion
- Sandbox: about 14 days of activity history.
- Pro: audit trail and catalog versions for 90 days, unless you still need them to run the live catalog.
- Enterprise: retention can be extended under contract.
To offboard, the owner downloads the workspace export and then deletes the workspace in Workspace → Settings, confirming with the workspace name and a code sent to their email. Published protocol surfaces and agent access stop at once. After 14 days we delete Customer Content and the owner’s account, keeping only quote amounts and dates without personal data, and billing records we must keep. The owner can cancel during those 14 days, and we email the owner and teammates when deletion is scheduled. You can also email support@pairrail.com from an owner seat.
Recent saved versions of the Service’s state are kept for up to 30 days, so a recent mistake by anyone, including us, can be undone. Deleted data leaves those versions as they expire. Within that window we restore a deleted workspace only when its owner asks. Security logs may remain for a limited period.
8. Assistance
We will help with reasonable requests that you need to answer your own data-subject or customer inquiries, to the extent the information sits in Atlas and you cannot pull it from the workspace yourself.
9. Executable Enterprise DPA
If you need a signed DPA (including SCCs or a UK addendum) on an order form, email support@pairrail.com.