Privacy Policy

No Data Storage

We do not store or log your text. When you use OpenRedaction (whether via the playground, API, or library), your data is processed in memory and discarded immediately after processing.

• No persistent databases
• No logs of your input text
• No retention of processed data
• All processing happens in memory

Hosted AI Assist

When AI assist is enabled, your text is sent to our hosted AI proxy for entity detection. Here's what happens:

• Text is sent to our hosted AI proxy
• The proxy forwards it to our model provider strictly for entity detection
• We do not log or store your text
• Everything is processed in memory and discarded
• No persistent storage of any kind

AI assist is optional. Regex-only mode works completely offline and requires no external services.

Self-Hosted Option

For complete privacy and control, you can self-host OpenRedaction on your own infrastructure:

• Your data never leaves your environment
• You control all processing and logging
• You can configure your own AI endpoint if needed
• Complete control over data handling

OpenRedaction is fully open source, so you can audit the code and deploy it on your own servers.

Data Minimization Principles

Our approach aligns with GDPR and UK-GDPR data minimization principles:

• Storage limitation: We don't store your data
• Data minimization: We only process what you send, and only for the purpose of redaction
• Purpose limitation: Data is used solely for PII detection and redaction
• Transparency: All code is open source and auditable

User Data Discarded After Processing

All user data is discarded immediately after processing:

• Input text is processed and then discarded
• No intermediate storage
• No caching of results
• No analytics or tracking of your content

Third-Party Services

OpenRedaction uses the following third-party services:

• AI Detection Service: When AI assist is enabled, your text is sent to our hosted proxy, which forwards it to our AI detection service strictly for entity detection. The service processes your text but does not store it. We do not share your data with the service for training or other purposes.
• Stripe: For Pro tier subscriptions, we use Stripe to process payments. Stripe collects and processes payment information (credit card details, billing address) according to their privacy policy. We do not store full credit card numbers on our servers.
• Email Service: We use an email service provider to send API keys and service notifications. Email addresses are used solely for service-related communications and are not shared with third parties for marketing purposes.

All third-party services are used in compliance with applicable privacy laws and data protection regulations.

Metadata Logging

For rate limiting, abuse prevention, and service improvement, we may log minimal metadata:

• IP addresses (for free tier rate limiting)
• API key identifiers (for Pro tier usage tracking)
• Request timestamps
• Response status codes
• Usage counts (for quota management)

We do not log: your input text, detected entities, or any content of your requests. All metadata is retained only as long as necessary for rate limiting and abuse prevention purposes.

GDPR & UK-GDPR Compliance

Our data handling practices align with GDPR and UK-GDPR principles:

• Data Minimization: We only process data necessary for the service (PII detection and redaction)
• Storage Limitation: We do not store your text — processing is stateless
• Purpose Limitation: Data is used solely for PII detection and redaction
• Transparency: All code is open source and auditable
• Right to Erasure: Since we don't store your text, there's nothing to delete. For metadata, contact us to request deletion.

For complete control over your data, you can self-host the open-source library, which requires no external services and processes everything locally.

Contact

If you have questions about this privacy policy, please contact us through our support channels or contact page.

Last updated: January 2025