stapel-gdpr
GDPR compliance: staged async data export (Art. 15/20) with status polling and download; subject-scoped erasure (Art. 17) — account, workspace, meeting, recording, document, file — each proven by one receipt per data owner that claims the subject type, with a purge SLA, timeout sweep and a subprocessor ledger behind
fully_erased_by; account closure keeps its cancellable 30-day grace and produces an ErasureRequest at grace end; DSAR intake (Art. 12) with automated acknowledgement and both statutory clocks; data-owner liveness probing; inactivity closure, retention cleanup, LegalHold and ReRegistrationHash; orchestrated through an in-process GDPRProvider registry (stapel_core.gdpr.gdpr_registry) plus comm confirmation (gdpr.section.erased) for remote owners.
Part of the Stapel framework — composable Django apps that deploy as a monolith or as microservices without changing module code.
Install
pip install stapel-gdpr
At a glance
| Fact | Value |
|---|---|
| Version | 0.5.3 |
| Python | >=3.11 (3.11, 3.12, 3.13, 3.14) |
| HTTP operations | 15 |
| Config axes | 3 |
| Usage surface | 18 |
| Extension points | 4 |
| Error codes | 57 |
| Fleet dependencies | stapel-core |
Documentation
OpenAPI · capabilities.json · llms.txt (for agents)
Quick start
# settings.py
INSTALLED_APPS = [
...
'stapel_gdpr',
]
MIDDLEWARE = [
...
# After authentication: refuses every request of an account being erased,
# whatever a still-valid token claims.
'stapel_gdpr.guards.AccountClosureGuardMiddleware',
]
STAPEL_GDPR = {
# Every store holding personal data. Erasure is only ever reported
# complete when each of these returned a deletion receipt, so an owner
# missing here is a store that quietly keeps the data. `manage.py check`
# fails while this is empty.
'DATA_OWNERS': ['auth', 'profiles', {'name': 'cdn', 'kind': 'remote'}],
'DATA_OWNERS_VERSION': '2026-08-13.1',
# How the user's sessions are revoked at closure. Auto-detected when
# stapel-auth is installed; without any seam, closure is refused rather
# than performed with live tokens left behind.
'SESSION_REVOKER': 'stapel_auth.sessions.services.SessionService.revoke_all',
}
Run manage.py check after wiring: a missing or stale data-owner inventory,
hash rows written outside store_hashes, and every open escape hatch are
reported there rather than discovered in an audit.
Bus events
Emits
| user.deleted | schema | All user PII permanently deleted after grace period. Every package storing user |
| user.deletion_cancelled | schema | Account closure cancelled during the grace period; every reversible reaction to user.deletion_initiated must be lifted. |
| user.deletion_initiated | schema | Account closure started. 30-day grace period begins; account is deactivated. |
| user.export_ready | schema | Data export archive is ready for download. |
| user.sessions_revoked | schema | Closure revoked every session and access JTI of the user. |
License
MIT — see LICENSE.
This page is assembled by stapel-readme from docs/readme.md plus the contract artifacts in docs/. Edit the prose in docs/readme.md; the badges, facts and links above and below it are generated — do not hand-edit README.md.
1 maintainer
Release files for stapel-gdpr 0.5.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| stapel_gdpr-0.5.3.tar.gz | 154.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stapel_gdpr-0.5.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 292.6 kB
Release files / stapel_gdpr-0.5.3.tar.gz
| Download URL | stapel_gdpr-0.5.3.tar.gz |
|---|---|
| Size | 154.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9025f538df2b331dc47099b57aa740dd49d05740aa2598a1448d1abbdadfc827
|
|
BLAKE2b-256 checksum How to use checksums |
f4883a0acb10ae1b03b8e420f6819a9b707776a61f7601009333a3fcb1ad093e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency logRelease files / stapel_gdpr-0.5.3-py3-none-any.whl
| Download URL | stapel_gdpr-0.5.3-py3-none-any.whl |
|---|---|
| Size | 137.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4daa05e4539cfdf48364ed8b805b771310e3928bc3fb1aed9c144968c2b18e1
|
|
BLAKE2b-256 checksum How to use checksums |
90fad4cc6f2dea1acb42807a323b5c9294e98fcb3516fe8d44f3ff5ee99a4042
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.
Transparency log
