Security

PAUD LTD, Registered in England and Wales, company no. 17241933. Last reviewed June 2026.

pAud is built for operations teams whose data is sensitive by definition. This page summarises how we hold customer operational data and the controls we operate against it. We will share more detail under NDA on request.

Connectors

Integrations into WMS, ERP, TMS, and OMS systems are read-only by default. We pull only the event and master data needed to detect process failures and never write back into source systems without an explicit, scoped agreement.

Encryption

Customer data is encrypted in transit (TLS 1.2 or higher) and at rest. Connection secrets are held in a managed secrets vault and rotated on the cadence required by the underlying provider.

Tenant isolation

Each customer engagement runs against an isolated tenant. Operational data is not used to train shared models. Per-tenant access is limited to the named pAud engineers on the engagement.

Access and audit

Access to production is granted on a need-to-know basis, requires multi-factor authentication and is logged. We will provide audit log extracts on request to customers running active engagements.

Reporting a vulnerability

If you believe you have found a security issue affecting pAud, email fahad@paud.dev with a description and steps to reproduce. We will respond within two working days.