Security Policy for Anonimator

Effective date: 22 October 2026

This policy explains how to report security vulnerabilities in Anonimator and how we handle them. Anonimator is developed by Antonio Castellon (Castellon.CH), “we” or “us”.

Anonimator is a local pseudonymisation layer for using external AI services with documents that contain personal data. It replaces identifiers with tokens before text leaves your premises and keeps the key needed to restore them (the vault) encrypted and under your control. The result is pseudonymised, not anonymous: it is still personal data. Anonimator is in pre-release and available as a demo on request.

1. How to report a vulnerability

Email [email protected] with the subject [SECURITY] anonimator.
Do not open public issues, pull requests or discussions about the vulnerability.
If you can, include: affected version or commit, a description, steps to reproduce, the impact you expect, and whether anyone else knows about it.
Do not send real personal data (documents, names, vault contents). Use synthetic data.
Encryption: we do not publish a PGP key yet. If you need an encrypted channel, ask for one in a first message without details.

Languages: Spanish, English, German or French.

2. Target response times

These are targets, not contractual guarantees. Business days are Swiss business days.

Step	Target
Acknowledgement	3 business days
Initial triage (confirmation, CVSS severity, scope)	10 business days
Fix or mitigation, critical/high severity	30 days from confirmation
Fix, medium/low severity	90 days from confirmation
Coordinated public disclosure	when the fix is released, or after 90 days unless we agree another date

We keep you informed and, if you wish, credit you in the security advisory.

Actively exploited vulnerabilities and severe incidents affecting the security of the product are notified to ENISA / the national CSIRT through the CRA single reporting platform (early warning within 24 hours, notification within 72 hours, final report) when that obligation applies.

3. Supported versions

We use Semantic Versioning. While Anonimator is in 0.x (before the first client), only the latest 0.x minor version receives security fixes. From 1.0, each major version receives security updates for 5 years from its release.

Version	Security support
0.x (latest minor)	Yes
Earlier 0.x	No: update to the latest
1.0 and later	5 years per major version from its release

4. Scope

In scope:

Anonimator software: detection, pseudonymisation, vault, leak check before sending, identity resolution and the evidence pack.
The pinned models and dependencies (hashes) we ship, and our signed release artefacts.
In particular: personal data leaking in outgoing text, re-identification without the vault, linking tokens across queries, personal values in logs or reports, and failures to stop on error (fail closed).

Out of scope:

Already published vulnerabilities in third-party dependencies with no specific impact on Anonimator (report them to the upstream project; tell us if they affect how we use them).
Client deployments and their infrastructure, non-default configurations that turn protections off, and external language models.
Social engineering, physical attacks and volume-based denial of service.
Detection errors without security impact (handled as normal bugs; real leaks are in scope).
This website.

5. Rewards

There is no bug bounty programme. We are grateful for good-faith reports.

6. Safe harbour

We will not take legal action against good-faith research that follows this policy, does not access third-party data, does not degrade services, and gives us reasonable time before disclosure.

7. Changes to this policy

We will update this policy when our process changes and revise the effective date above. A machine-readable contact is published at https://www.castellon.ch/.well-known/security.txt (RFC 9116).

8. Contact

Castellon.CH, Antonio Castellon
Email: [email protected]
Website: https://www.castellon.ch
Address: Zaunweg 5, 2502 Biel/Bienne, Switzerland