Privacy tooling only works if you can trust it with your most sensitive data. TruePrivacy is built so that data is protected in transit, isolated per organization, and — for endpoint discovery — never leaves your devices at all.
Security and trust overview

Encryption in transit

All communication with the TruePrivacy platform — dashboard, REST API, consent banner, and public endpoints — happens over HTTPS/TLS. API access is authenticated with scoped bearer tokens that you can rotate at any time from the dashboard.

Tenant isolation

Every record in TruePrivacy — scans, cookies, consent logs, DSRs, assessments, findings — is scoped to your organization. API tokens and dashboard sessions can only ever read or write data belonging to your own tenant.

Safe website scanning

The website scanner only crawls public, internet-facing pages of the site you point it at:
  • Scans stay on the same site — the crawler never follows links off your domain.
  • Requests to private, internal, or reserved network addresses are refused, so a scan can never be used to probe infrastructure behind your firewall.
  • Page and scan time limits keep crawls short and predictable.

Signed offline licenses

Device agent offline licenses (TP-OFFLINE-...) are cryptographically signed by TruePrivacy. The agent verifies each license before accepting it, so licenses cannot be forged and their terms (organization, plan, expiry, device count) cannot be tampered with. Expiry is enforced live on the device — see Installation & Licensing.

Local-only device processing

The Device Agent performs all PII detection on the endpoint itself:
  • File contents are scanned locally; raw data is never uploaded.
  • Findings show masked samples only (for example •••• 1234), never full values.
  • Archive scanning enforces strict size and member limits so a malicious archive cannot exhaust the machine.
Even when an agent is enrolled with the platform, only finding metadata (file path, entity type, count, masked sample) is reported — never the underlying file contents.
Consent receipts are recorded with a timestamp, the policy version shown, and the choices made, giving you an audit-ready trail for regulators. The public cookie declaration and banner configuration are served read-only from cache-friendly endpoints.

Responsible disclosure

Found a vulnerability? Email [email protected] — we respond quickly and appreciate coordinated disclosure.