AuthorityRailExecution Authority Infrastructure
Trust

Subprocessors, certifications, regional residency, and customer-side controls

A current, accurate posture statement for procurement-grade evaluation. Where the answer is “not yet,” the page says “not yet.” Mapping is done; audits are on the roadmap.

Companion documents: /security · /security/disclosure · /legal/privacy · /legal/dpa · /legal/subprocessors

Subprocessors

AuthorityRail engages a small, accountable set of subprocessors. The canonical list with links to each subprocessor’s security and privacy pages is at /legal/subprocessors. New subprocessors get at least thirty (30) days’ advance notice before processing Customer Personal Data. Customers may object on reasonable data-protection grounds within fifteen (15) days; mechanism is in Section 6 of the DPA.

SubprocessorFunctionRegion
Supabasedatabase hosting, authentication backend, RLS tenant isolation, CAR persistenceus-east-1
AnthropicLLM inference for policy evaluation, intent scoring, decision explanationUnited States
Stripepayment processing and billingUS / global delivery
Vapivoice agent infrastructure backing the Voice Execution Gateway (VEX-1)United States
Railwayapplication compute hosting (gate, voice gateway, ARES gateway, supporting services)us-east-1 (on AWS)
Cloudflareedge / CDN / DNS / DDoS / static-site hostingglobal anycast

Compliance and certification posture

Every entry below states the truth at the date of this page. We will not state “audit in progress” until an audit is actually in progress. We will not state “SOC 2 compliant” without a SOC 2 report.

SOC 2

Type II audit planned for post-launch (Q3 2026 target). No SOC 2 audit is currently in progress. There is no Type I report. There is no Type II report. We have implemented the controls we expect a Type II audit to assess (see /security) but have not yet been audited against them. When we engage an audit firm, this page will name the firm and the engagement scope.

HIPAA

The platform is not currently HIPAA-eligible. AuthorityRail does not represent itself as a HIPAA-compliant Covered Service today.

Business Associate Agreement: [FOUNDER_TO_FILL — confirm with counsel either “A BAA may be available for the Enterprise tier on a per-deployment basis after a sectoral compliance review. Contact hello@authorityrail.com to initiate.” OR “Not available at this time. We will publish a BAA template when the platform supports a HIPAA-eligible deployment shape.”]

GDPR / UK GDPR / FADP

The DPA at /legal/dpa incorporates the EU Standard Contractual Clauses (Module 2 + Module 3 with Clause 9 Option 2 general written subprocessor authorization), the UK Addendum (UK ICO IDTA v.A1.0), and the FADP modifications. Personal Data Breach notification within 72 hours of confirmation per DPA Section 8.

CCPA / CPRA

AuthorityRail acts as a service provider under CCPA / CPRA. We do not “sell” or “share” Personal Information through cookies and do not use cross-context behavioral advertising. Full service-provider commitments in DPA Section 12.

EU AI Act

Article 14 human-oversight artifact: Human Decision Records under DRI-v1 (Tier 2 Published 2026-04-30). Mapping at standards/DRI-v1/SPEC.md §7. AuthorityRail does not certify EU AI Act compliance on customers’ behalf — the platform produces the cryptographically signed evidence that customers’ compliance counsel uses to demonstrate Article 14 conformance.

Other

  • ISO 27001 — not pursued at this time.
  • PCI DSS — not in scope. Card numbers are processed by Stripe; AuthorityRail does not store cardholder data.
  • FedRAMP / IL-x — not pursued at this time. Federal deployments are not a launch market.
  • State / sectoral certifications — none in progress.

Regional data residency

  • At launch: all Customer Data is hosted in the United States, AWS region us-east-1, via Supabase + Railway.
  • Cloudflare delivers the marketing site and standards site over a global anycast network. No Customer Data flows through Cloudflare beyond the request path; application origins terminate at Railway / Supabase in us-east-1.
  • Multi-region (e.g., eu-west-1 for EU data residency) is on the AuthorityRail public roadmap and is tracked under the master plan’s regional-expansion items. It is not available at the date of this page.

Customer-side trust controls

Controls a Customer can exercise itself today, without filing a support ticket.

Self-serve audit log

The customer dashboard exposes the CAR Verification Console at /audit/cars, the Federation Manifests view at /audit/manifests, and the Regulatory Citations view at /audit/citations — read-only and scoped to your own org_id. Every CAR is independently verifiable via the public verification endpoint.

docs/CAR_VERIFICATION.md, https://authorityrail.com/v1/verify/:car_id

Tenant isolation

Postgres row-level security gates every tenant-scoped read against auth.org_id() from the Customer JWT. Cross-tenant test assertions live in the gate test suite. The dual-identity model (Customer SDK + RLS vs. operator dashboard + Okta + service-role) is documented at docs/AUTH_IDENTITY_MODEL.md.

supabase/migrations/20260505000100_rls_helper_fn.sql · services/gate/__tests__/rls-isolation.test.ts

Decision-time controls

Operators can issue a Global Halt or Scoped Containment that takes effect on the next decision; set per-agent and per-action authority bands; and tenant-configure policy rules with full audit (the Enterprise Decision Policy Engine, EDPE). Idempotent retry: same caller-supplied request_id within 24h replays the original CAR.

services/gate/src/routes/kill-switch.ts · docs/REPLAY_FRESHNESS.md

Data subject rights and export

Customer-administered Personal Data is editable in the dashboard. Other rights (access, correction, deletion, portability, restriction) are handled per the Privacy Policy and the DPA. On termination, AuthorityRail provides Customer Data export in a machine-readable format on written request within 30 days.

/legal/privacy · /legal/dpa

Contact

  • Trust / compliance / DPA: hello@authorityrail.com.
  • Security incident or vulnerability report: security@authorityrail.com — see /security/disclosure.
  • Subprocessor change notifications: subscribe by emailing hello@authorityrail.com with subject “Subprocessor change notifications.”

External: federation manifests · public CAR verification