PAT security posture.

Authentication boundaries

Production authentication is provider-backed. Local review credentials are restricted to local machines and cannot be used against public production auth.

Sensitive operations

Billing and account-sensitive operations are protected by page-level guards, rate-limit checks, and elevated confirmation where supported by the current build. Session payloads are kept to the fields needed for routing and authorization.

Release and build proof

We verify that every release matches its source before it serves, and the full technical proof, branch, commit, build identity, and build checks, is published on the release page at /release.

Billing data boundary

Card entry is delegated to the payment provider when billing is configured. PAT stores provider identifiers and reconciliation status; it does not store raw card numbers.

Subprocessors

PAT relies on a small set of infrastructure and service providers to operate. We inherit each provider's own infrastructure controls; PAT does not claim its own external certification.

• Vercel: application hosting and edge/serverless compute.
• Neon: managed PostgreSQL database (pooled, with connection management).
• Stripe: payment processing and provider-hosted checkout when billing is configured.
• Anthropic: large-language-model provider powering optional AI-assisted features (no customer data is used to train third-party models).

Data practices and methodology

Data is transmitted over encrypted connections. Retention is configured per data class with a soft-delete window before hard purge, and tested tenant export and deletion paths exist for contractual data-subject requests. How PAT computes its scores and benchmarks, including the integrity walls that keep demo data and vendor self-report out of peer aggregates, is published on the versioned methodology page at /methodology.

Entity

PAT is operated by Patalign LLC, registered office 202 N Cedar Ave Ste 1, Owatonna, MN 55060. Security questions go to cam@patalignhq.com.