GDPR Compliance
NoPII supports GDPR right-to-erasure through the token purge feature in the admin console. When a data subject requests deletion, you can delete their tokens and mark the associated audit log entries as purged directly from the console.
How NoPII supports GDPR
- 1Detected PII is tokenized before it reaches the LLM - Providers such as OpenAI and Anthropic receive tokens in place of the personal data NoPII detects in prompt text. See what NoPII covers.
- 2Audit trail without PII - The audit log records entity types and tokens, never plaintext PII.
- 3Right to erasure - The token purge feature in the admin console deletes an individual's tokens, clears them from session caches, and marks their audit entries as purged.
- 4Automatic token expiration - Vault tokens expire automatically based on configurable TTL policies, supporting data minimization. Expired tokens are permanently deleted without manual intervention.
Token purge
You can purge tokens from the admin console. Provide the plaintext PII values belonging to the data subject, and NoPII will search for and delete the matching tokens and mark the associated audit log entries as purged. You can submit up to 1,000 plaintext values per purge request.
What happens during a purge
- 1Search - NoPII searches for existing tokens matching each plaintext value. No new tokens are created.
- 2Delete tokens - Matching tokens are permanently deleted.
- 3Mark audit log entries - Audit log entries referencing the deleted tokens are kept and marked as purged. They hold only the masked value and the token, never the plaintext.
- 4Invalidate caches - Active session caches containing the deleted tokens are invalidated.
Purge by token value
If you have token values rather than the original plaintext (e.g., from audit log entries), the admin console also supports purging directly by token value.
Audit log entries after a purge
Purging does not delete audit log entries. Entries that reference a purged token are kept, and each one is stamped with purged_at and purged_by (the admin who initiated the purge) for compliance audit trails.
An audit entry never stores the plaintext value. For the purged value it holds only a masked form (for example, the first character of a name or the last four digits of a number) and the token. Once the token is deleted from the vault, the token can no longer be resolved back to the original value. The entry also keeps its request metadata, such as entity type, session, provider, model and timestamp.
Active session cleanup
Purged tokens are automatically removed from all active sessions. This prevents deleted PII from being served from the in-memory session cache after a purge.
Automatic token expiration
In addition to on-demand purge, NoPII supports automatic token expiration through configurable TTL (time-to-live) policies. This supports GDPR's data minimization principle by ensuring tokenized PII is not retained longer than necessary.
Lite plan tokens expire after 1 day and Starter tokens after 30 days. Growth and Business can configure retention from 1 day to permanent in the admin console, and Enterprise retention is set in your contract. When a token expires, the underlying PII is permanently deleted from the vault.
TTL-based expiration and manual purge are complementary. Use TTL for automatic lifecycle management and purge for specific data subject erasure requests. See Billing & Pricing for plan-specific TTL details.
Related
- How It Works - Understand how PII is detected and tokenized before it reaches the LLM
- API Reference - Full endpoint documentation