Skip to content
echoValuesecrets
LanguageItalianoEnglish

Privacy policy

Last updated: October 14, 2026

What data we process, how long we keep it and how to exercise your rights.

Controller and purposes

The controller is Example Operator S.r.l. Contact: [email protected]. We process data to provide the service and prevent abuse, based on legitimate interest (Article 6(1)(f) GDPR). No account is required. We do not use data for marketing, profiling or automated decision-making.

Data we process

  • Encrypted content, token hashes, a hash of the verification key, whether a password is set, and creation and expiry dates.
  • The status and time of a read, cancellation or expiry, available through the control link.
  • Your IP address in cleartext in counters that limit creations, reads and cancellations.
  • A cookie that remembers your language choice for one year. A CDN or reverse proxy in front may set other technical cookies, depending on the features enabled on that deployment.

Protecting the secret

The browser encrypts the text before sending it. The key stays in the link, after #, and never reaches the server. The password stays in the browser. The server authorizes reading only after verifying that the browser holds the correct key and, if set, the password. Anyone with the complete link can open the secret, with the password if set.

This is not end-to-end encryption verified by an independent review. A compromised device or a malicious change to the page code can expose the content.

Retention

  • Secrets: deleted on reading or cancellation. At expiry, within 30 days of creation, they become inaccessible and are removed by periodic cleanup.
  • Secret status: kept until the original expiry or seven days after closure, whichever is later; then removed by periodic cleanup.
  • IP counters: removed by cleanup after the configured period, at least as long as the longest counting window (one hour with default settings).

Deletion does not immediately remove copies from database logs (WAL) or backups. For technical logs and backups under our control, the planned policy is a maximum of 7 days; enforcement on the infrastructure remains to be verified. Data retained independently by providers follows their own policies.

Logs and providers

The application does not log content, passwords, tokens or request bodies. A proxy and hosting provider may log IP addresses, times, requested paths and browsers; paths may include tokens, but never the key after #. The servers are hosted with the provider named in the service documentation, in a country the European Commission recognises as providing adequate data protection. The hosting provider and any CDN in front process IP addresses and request metadata to deliver their respective services. These providers may process the technical data needed for their respective services. Any further transfers outside the European Economic Area require GDPR safeguards; contact [email protected] for details.

Cloudflare Turnstile may be introduced to prevent abuse, but it is not yet integrated into the application. When enabled, it processes IP addresses and technical browser signals to distinguish people from bots. Cloudflare also uses these signals to improve Turnstile as an independent controller: Turnstile privacy notice. A cf_clearance cookie depends on enabling the pre-clearance feature.

Rights and contact

Where the GDPR provides for it, you can request access, rectification, erasure, restriction and portability, or object to processing. Write to [email protected] without including the content, password or complete link. We cannot decrypt or recover secrets. You can complain to the Italian data protection authority or the competent authority in your country.

This policy covers secrets. For the echoValue site: https://example.com/privacy. For this service: terms of use. The date above shows the last revision; changes affecting your rights will be communicated before taking effect.

  • How it works
  • Privacy policy
  • Source code
  • Terms of use