P-AI-roll
Security

Pay data is sensitive. We built accordingly.

What we store, how we protect it, and what we will and will not do with it.

Architecture

P-AI-roll runs on Cloudflare's global network. Customer data lives in isolated per-tenant storage, encrypted at rest, with TLS 1.3 everywhere in transit. Integrations with trackers, your platform and calendars are read-only: we never write to your systems of record.

Access

  • Google sign-in or SSO for admins and workers; no passwords stored by us.
  • Roles: admin, viewer (read-only) and worker (own portal only).
  • Support mode ("log in as a worker") is time-boxed to eight hours and audited on both ends.
  • Internal access to production is by named engineer, logged, and reviewed monthly.

Audit trail

Every change to hours, pay, time off or settings is an append-only event with the actor, the inputs and the version of the pricing component that ran. Signed-off timesheets are never rewritten; late evidence becomes a flagged adjustment.

Payouts

We create Wise recipients, quotes and transfers and complete the batch. We never hold funds and never store bank credentials; Wise holds the recipient details, we hold a reference.

AI review

The review model sees the claim, the day's block map and the evidence attached. It never sees bank details, and its verdict is advisory. Model calls run through our own gateway with no training on customer data.

Data processing

A data processing addendum is available on request for Core and Scale customers. Workers can request an export or deletion of their own data through their admin.

Compliance

SOC 2 Type I is in progress with a target of Q1 2027. Until the report is issued we share our control set and policies under NDA.

Reporting a vulnerability

Email security@p-ai-roll.com. We acknowledge within two business days and do not pursue researchers acting in good faith.

Controlsat a glance
  • ▸ TLS 1.3 in transit, AES-256 at rest
  • ▸ Per-tenant isolation
  • ▸ Read-only integrations
  • ▸ Append-only audit events
  • ▸ No bank credentials stored
  • ▸ No model training on customer data
  • ▸ SOC 2 Type I in progress