Security and privacy

How the service handles your text, what we commit to and where protection stops.

Download whitepapers

Our commitment

Security and privacy are what Anonymizator is for, so we hold the service to them first. We aim for the highest safety and privacy standards, and we only claim what we can show.

  • The service keeps no text and no results, and it never receives Current IDs or your ID files.
  • The product has no analytics, tracking or advertising.
  • This page and the whitepapers say where protection stops.
  • You can report a security issue to privacy@prosecco37.com.

When you press Protect

In the hosted service, Protect sends text to Anonymizator encrypted with Hybrid Public Key Encryption (HPKE, RFC 9180), and it is decrypted there to find IDs. The service returns only where the IDs are. It keeps no text and no results. To detect repeated requests, it keeps a random technical value from each encrypted request for about a minute. The service runs in the EU.

Custom installations on your company's own servers can work differently.

The companies and systems that carry a request can still see your login details, the timing and approximate size of requests, and your IP address.

What stays in your browser

Placeholders, Current IDs and Reveal stay in your browser. In the web app, Current IDs clears when you reload or close the page. In the extension, it clears when you close the browser.

An ID file is a file on your computer, and it holds the original details. We never receive it. You decide where it's kept and who sees it.

GDPR and compliance

We're committed to helping you meet your data protection duties. Anonymizator supports data minimisation (GDPR Article 5), data protection by design (Article 25) and security of processing (Article 32), which names pseudonymization as a measure.

You remain the controller, and you still need a lawful basis and permission to share. Using Anonymizator doesn't by itself make a process GDPR compliant. A data processing agreement is available on request.

We don't hold ISO 27001 or ISO 42001 certification today. The whitepapers relate the product to frameworks such as these and NIS2 as a guide only, and no accreditation body has audited that.

What protection doesn't do

By default this is reversible pseudonymization, and the text is not anonymous. Job titles, dates, places, rare events and writing style can still identify people. Recognition is not complete, so read the whole result before you share it.

Need the details for an internal assessment? Tell us what you need to understand.

Contact us

The whitepapers

For a full assessment, we've written two documents.

Security whitepaper

For security engineers and technical due diligence: architecture, encryption, how detection works and the threat model.

Compliance whitepaper

For data protection officers, auditors and legal counsel: pseudonymization and anonymization, how the product relates to GDPR articles and what stays your responsibility.

Download whitepapers

Download the whitepapers

Tell us where to send the Security and Compliance whitepapers.

Optional. You can unsubscribe at any time using the link in our marketing emails or by contacting privacy@prosecco37.com. Your choice won't affect getting the whitepapers.