Privacy Policy

Last updated: 19/08/2026

Note on future features. Some sections below describe features that are planned but not yet active (a registered account area, analytics, and advertising). These are written in the future tense and clearly marked. They will become effective only when the corresponding feature is launched, at which point this policy will be updated.

1. What this service does

This service is a tool for anonymizing medical imaging files (DICOM) and other images. It helps remove identifying information from files before you share them. Understanding how the anonymization works is important for understanding how your data is handled, so we explain it in plain terms below.

2. How your data is processed — the two levels of anonymization

Anonymization with this tool works at two levels. The completeness of anonymization depends partly on the system and partly on you.

Level 1 — Automatic tag anonymization (in your browser)

For DICOM files, identifying information contained in the file's metadata (tags) — such as patient name, patient ID, and dates — is removed automatically, inside your web browser, before any data is sent to our server. This step requires no action from you.

Level 2 — Visual redaction of the image (your responsibility)

Identifying information is sometimes burned into the image itself (for example, a patient's name displayed on an ultrasound frame). This information is part of the pixels, not the metadata, and cannot be removed automatically with certainty.

The tool proposes redaction areas to help you, and requires you to open and review every image before anonymization can proceed. However, the redaction proposals are suggestions: you remain responsible for confirming that all sensitive areas are correctly covered before sharing the files.

A file is fully anonymized only after both levels are complete: the metadata is removed, and you confirm that the visible image contains no identifying information.

3. What is sent to our server, and what is not

Original files never leave your device unmodified. For DICOM files, the metadata is anonymized in your browser before any transmission.
To rebuild the final file, the anonymized header and the image pixels with the redactions you applied are sent to our server for processing.
The reconstructed file is returned to you for download.

Temporary files

Files processed on our server are stored temporarily only for the duration of processing and are automatically deleted shortly afterwards. We do not keep a copy of your images.

Non-DICOM images (JPEG, PNG, and similar) — important

Non-DICOM images do not contain DICOM tags, so the automatic metadata anonymization (Level 1) does not apply to them. For these images, only the visual redactions you apply are used, and the system does not automatically remove other embedded metadata (such as EXIF data, which may include date, camera model, or location). You are responsible for ensuring such images contain no identifying information.

4. What we do and do not store

What we do NOT store

Your medical images and their content. Files are processed and then automatically deleted shortly after. We do not keep a copy, so there is nothing to export or delete on request — they no longer exist after processing.

What we DO store

Device redaction data. To help propose redactions for similar images, we store technical information about the imaging device (manufacturer, model, modality, image type, resolution) together with the coordinates of redaction areas. This contains no patient data and no part of the image.
Usage-limit data. To enforce usage limits on the free service, we use a cookie stored in your browser and we record your IP address on our server, together with the time of each completed anonymization. This lets us count usage per browser and per IP address. IP records used for this purpose are automatically deleted after the limit window elapses.
Server logs. Our web server keeps technical logs (including IP addresses) for security and troubleshooting. These logs are automatically deleted after 3 days.

We use your IP address for security, abuse prevention, and to enforce the usage limits of the free service. This is a limited, legitimate use; we do not use it to build profiles about you.

5. Cookies and similar technologies

This service uses cookies. When required by law, we ask for your consent before setting non-essential cookies (see the cookie banner shown on your first visit). You can change your choice at any time via the "Cookie preferences" link.

Strictly necessary. Security / anti-abuse (Google reCAPTCHA), the usage-limit cookie, and the cookie that stores your consent choice. These are always active.
Analytics (planned). Google Analytics, to understand how the service is used. Will be loaded only with your consent, once activated.
Advertising (planned). Google AdSense, to show and measure ads. Will be loaded only with your consent, once activated.

6. Third parties we rely on

Aruba S.p.A. — hosting provider (servers located in Italy / EU).
Google (reCAPTCHA; Analytics and AdSense once activated) — anti-abuse, and, in future, analytics and advertising. Google may process data outside the EU; [CONFIRM SAFEGUARDS].

7. Registered account area (planned — not yet active)

The following describes a future free registered-account area that is not yet available. It is included here so it can be reviewed in advance. It will take effect only when the feature is launched.

When we launch the registered area, creating an account will involve processing:

Email address — for login, account identification, and password recovery.
Password — stored only in protected form (hashed, never in clear text).
Security question and answer — used for account recovery. The answer is stored only in protected form, never in clear text.
Usage counts — to apply the limits associated with the account.

Password recovery will be available via email and the security question. The registered area will not change how images are handled: anonymization will remain transient, and images will still never be stored.

8. Legal basis for processing (GDPR)

Performance of the service you request (Art. 6(1)(b)).
Legitimate interest (Art. 6(1)(f)) — security, abuse prevention, enforcement of usage limits, service improvement.
Consent (Art. 6(1)(a)) — non-essential cookies, analytics, advertising (once activated).

9. Your rights

Under the GDPR, you have the right to access, correct, or delete your personal data; to restrict or object to processing; to data portability; and to withdraw consent at any time. You may also lodge a complaint with your national data protection authority (in Italy, the Garante per la protezione dei dati personali).

Regarding your images: these are not retained after processing, so there is nothing for us to access, export, or delete on request.
Regarding your usage data and (in future) account data: where this constitutes personal data, these rights apply and we will act on valid requests.

To exercise any of these rights, contact us at dicomhelper@gmail.com.

10. Changes to this policy

We may update this policy from time to time. The date at the top indicates when it was last revised. Material changes will be communicated through the service.