ProtectedAI ("we", "us", "our") operates the ProtectedAI Chrome extension and associated services at protectedai.io. Our product anonymizes sensitive information before it is submitted to AI platforms such as ChatGPT, Claude, and Gemini.
This Privacy Policy explains what personal data we collect, how we use it, and what rights you have in relation to it. By using our service, you agree to the practices described in this policy.
When you create an account, we collect:
bcrypt hash. We never store your password in plain text and cannot recover or reverse it.admin or member).Each time you use the anonymization service, we record:
Your organization's administrator configures an audit logging level that determines what data is captured when you use the anonymization service. The default level is Metadata only (Level 1).
| Level | Name | What is captured | Available on |
|---|---|---|---|
| 0 | Off | Nothing — no audit record is created | All plans |
| 1 | Metadata only | Entity types detected, entity count, platform, page domain, severity, risk score. No text is stored. | Team and above |
| 2 | Redacted context | Everything in Level 1, plus the anonymized text and entity map (entity type and replacement label only — no original values). Encrypted content fingerprint (SHA-256 hash). | Pro and above |
| 3 | Full content | Everything in Level 2, plus the original text you submitted and full entity map (entity type, original value, and replacement). Encrypted content fingerprint. | Enterprise only |
At Levels 2 and 3, sensitive fields are encrypted at rest using per-tenant keys (AES-256-GCM). Retention periods are determined by your plan: 90 days (Team), 180 days (Pro), or 365 days (Enterprise). After expiry, audit records and associated payload files are automatically deleted.
For Business accounts, the extension reports which supported AI platforms team members visit and when. This data powers the Shadow AI dashboard, giving administrators visibility into which AI tools the team uses.
We collect technical data about the browser extension to ensure it is up to date and functioning correctly:
This data is updated after each anonymization request (throttled to at most once per minute) and is used for security monitoring and extension update notifications.
When an audit log entry is created (Levels 1–3), we derive and store the following from your IP address:
At Levels 2 and 3, the raw IP address is additionally stored in encrypted form and automatically purged after one-third of the retention period (Level 2) or the full retention period (Level 3). The raw IP is never exposed through our API — only the derived metadata listed above is accessible.
The ProtectedAI extension stores the following data locally in your browser's extension storage (chrome.storage.local):
This data is stored only on your device and never transmitted to third parties. Session data (credentials, caches, and timestamps) is cleared when you log out. The onboarding flag persists across sessions to avoid showing the tutorial again. All extension data is removed if you uninstall the extension.
We explicitly do not collect or store:
We use the data we collect for the following purposes:
| Data | Purpose |
|---|---|
| Email address | Account identification; sending service notifications |
| Name | Personalizing your account and communications |
| Password hash | Authenticating your login |
| Company name & role | Managing team access and permissions |
| Language preference | Delivering anonymization labels in your preferred language |
| Last login | Account security monitoring |
| Usage metering | Billing, consumption tracking, and plan enforcement |
| Audit logs (Levels 1–3) | Compliance auditing, security monitoring, and incident investigation as configured by your admin |
| Platform visit activity | Shadow AI monitoring — giving admins visibility into which AI tools the team uses |
| Extension status | Security monitoring and ensuring the extension is up to date |
| IP-derived geolocation | Security monitoring, anomaly detection, and access pattern analysis |
| Custom recognizer patterns | Applying admin-configured detection rules to all team members' text during anonymization |
| Notification log | Ensuring each lifecycle notification is sent only once |
| Error logs | Debugging and maintaining service reliability |
We do not sell, rent, or trade your personal data. We do not use your data for advertising or profiling.
We process your personal data on the following legal bases:
| Legal Basis | Data Categories |
|---|---|
| Contractual necessity (GDPR Art. 6(1)(b) / Ley 1581 Art. 5) | Account data (email, name, password hash), anonymization processing, usage metering, billing |
| Legitimate interest (GDPR Art. 6(1)(f)) | Platform visit tracking (Shadow AI), extension status monitoring, IP-derived security telemetry, error logging |
| Admin authorization with employee notification obligation (GDPR Art. 6(1)(f), subject to balancing test) | Audit logging at Levels 2–3 (anonymized or original text). The admin who enables these levels is responsible for informing affected team members (see Terms of Service). |
We share your data with third parties only when strictly necessary to operate the service.
We use Stripe for payment processing. When you subscribe to a paid plan, your payment information (card details, billing address) is handled directly by Stripe and never touches our servers. We store only Stripe reference identifiers (customer ID, subscription ID) to manage your billing relationship. Stripe's privacy policy governs their handling of your payment data.
We use Resend as our transactional email provider. When we send you a service notification (account verification, team invitation, trial expiration), your email address is transmitted to Resend for delivery. Resend does not receive any text content processed through our service.
Our backend runs on Amazon Web Services (AWS), which processes your requests in transit but does not retain any user content. AWS operates under its own privacy and security policies. Our database is hosted on AWS RDS and is not exposed to the public internet.
The ProtectedAI extension runs within the Google Chrome browser, subject to Google's own privacy policies. Extension data is stored in chrome.storage.local, isolated to the ProtectedAI extension.
We do not share your data with AI platforms. Our service exists precisely to prevent your sensitive information from reaching those platforms.
bcrypt. We cannot recover your password.| Data Type | Retention Period |
|---|---|
| Text submitted for anonymization (default) | Not retained — discarded immediately after processing at Levels 0 and 1 |
| Text in audit logs (Levels 2–3) | 90 days (Team), 180 days (Pro), or 365 days (Enterprise), then automatically deleted |
| Audit log metadata (Level 1+) | Same as above — retained per plan, then automatically deleted |
| Payload files (Levels 2–3) | Same as audit logs — automatically deleted after the plan retention period |
| Raw IP address (Levels 2–3) | Encrypted; purged after 1/3 of retention period (Level 2) or full retention period (Level 3) |
| Platform visit activity | Retained per plan retention period, then automatically deleted |
| Usage metering records | Retained for the life of the account |
| Extension status | Retained while the account is active |
| Active account data | Retained while your account is active |
| Expired or cancelled account data | Retained until you request deletion (see below) |
| Refresh tokens | Automatically purged 7 days after expiry or revocation |
| Server error logs | 30 days; no user content included |
| Service notification log | Life of the account |
You may delete your account at any time through your account settings or by contacting support@protectedai.io. When you request deletion:
Depending on your jurisdiction, you may have the following rights:
To exercise any of these rights, contact us at support@protectedai.io. We will respond within 30 days (or sooner if required by applicable law).
ProtectedAI acts in different data processing capacities depending on the context:
Enterprise customers who require a Data Processing Agreement (DPA) may contact us at support@protectedai.io.
For users located in Colombia, the processing of personal data described in this policy is governed by Ley 1581 de 2012 (Ley de Protección de Datos Personales) and Decreto 1377 de 2013.
The rights described in Section 9 are consistent with the rights recognized to data subjects (titulares) under Colombian law. For individual account data, ProtectedAI acts as the Responsable del Tratamiento (data controller). For data processed on behalf of Business accounts, your organization is the Responsable del Tratamiento and ProtectedAI acts as Encargado del Tratamiento (data processor).
For data protection inquiries: support@protectedai.io.
If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, the General Data Protection Regulation (GDPR) applies to our processing of your personal data, regardless of where ProtectedAI is incorporated.
In addition to the rights listed in Section 9, you have the right to lodge a complaint with your local supervisory authority. The legal bases for our processing are described in Section 5. Your data may be processed in AWS regions outside your jurisdiction; we rely on the service provider's standard contractual arrangements to safeguard international transfers.
For GDPR-related inquiries: support@protectedai.io.
ProtectedAI is not directed at individuals under the age of 18. We do not knowingly collect personal data from minors. If you believe a minor has provided us with personal data, contact us at support@protectedai.io and we will delete that data promptly.
In the event of a security breach that compromises personal data, ProtectedAI will notify affected users within the timeframes required by applicable law and take all necessary corrective measures. Notifications will be sent to the email address associated with the affected account.
We may update this Privacy Policy from time to time. We will revise the "Last updated" date and notify you by email at least 30 days before material changes take effect. Continued use of the service after that period constitutes acceptance.