---
title: "theAuth compliance: SOC 2 mapping and GDPR reference"
description: "Reports, not certifications: a SOC 2 criteria mapping and a GDPR data handling reference for theauth-go. No audit or certificate is claimed or published."
canonical: https://theauth.dev/open/compliance/
lastmod: 2026-10-31
---

Compliance

# Reports, not certifications

theauth-go publishes a mapping of library behavior to SOC 2 criteria and a GDPR engineering reference for operators. No third-party audit is published, and nothing here says any deployment is compliant or certified.

[SOC 2 mapping](https://docs.theauth.dev/go/security/compliance-soc2) [GDPR reference](https://docs.theauth.dev/go/security/compliance-gdpr)

## Sources and review date

**Source**Last reviewed 2026-10-06

SOC 2

## A mapping, not an attestation

The document maps library behavior to the AICPA Trust Services Criteria. The maintainers wrote it. No auditor has reviewed it.

- CoverageCommon criteria CC1 to CC9, plus availability, confidentiality, processing integrity and privacy.
- Per criterionWhat the criterion asks for, how theauth-go helps, and what the operator must implement.
- Often not addressableSome criteria, such as board oversight and hiring, cannot be satisfied by a library. The document says so.
- Closing sectionA list of what theauth-go does not provide.

- RolesThe operator is the data controller. theauth-go is a library with no data processing infrastructure of its own, and its authors are not a sub-processor.
- Data inventoryThe personal data the built-in storage adapters hold by default, such as email, name, session IP and user agent, and credential hashes.
- Rights and retentionHow to satisfy data subject rights, retention considerations, data residency and cross-border transfers.
- Defaults and checklistPrivacy-by-design defaults, and a checklist for the operator.

GDPR

## An engineering reference

It is not legal advice and not a statement that any deployment is GDPR compliant.

## What we do not claim

- **No certifications.** theauth-go is not SOC 2 certified or audited. There is no ISO certificate.
- **No third-party audit is published.** Nothing on this site presents an auditor's report.
- **No deployment-level claims.** An examination covers an operator's whole system. These documents cover one library's contribution.

- [Security practices](https://theauth.dev/security/)
- [GDPR docs](https://docs.theauth.dev/gdpr)
- [Compliance docs](https://docs.theauth.dev/compliance)

## Related pages

- [Roadmap](https://theauth.dev/open/roadmap/)
- [Stability](https://theauth.dev/open/stability/)
- [Threat model](https://theauth.dev/open/threat-model/)
- [Governance](https://theauth.dev/open/governance/)
- [Releases](https://theauth.dev/open/releases/)
- [Open hub](https://theauth.dev/open/)
- [Security and disclosure](https://theauth.dev/security/)
