Privacy Policy

Last updated: October 2026.

Who processes the data

This website and the linked prototype are a personal demonstration project. For any data-related request you can get in touch via www.simonescaffidi.it.

Controller: Simone Scaffidi Domianello — Piazza Merendino 6, 98071 Capo d'Orlando (ME), Italia — P.IVA IT03507360836 — C.F. SCFSMN83R25G377C — info@simonescaffidi.it — PEC: simone.scaffididomianello@widipec.it

Data collected by the presentation website

This website does not use third-party analytics or tracking tools. Only the cookie preferences you choose are saved (see Cookie Policy), locally in your browser.

Data collected by the prototype (/app)

To use the messaging prototype you create a profile with an email, a username and a password. The following is stored on the server (PostgreSQL database): email (encrypted), username, password hash, public ID, hidden-chat combination, added contacts, your public encryption key, active sessions and the messages sent.

Messages: the content is end-to-end encrypted in the browser before sending; the server keeps only ciphertext and cannot read it. Metadata (sender, time, reactions, expiry of timed messages) remains unencrypted.

Biometric unlock: if you enable it, only the passkey's public key (WebAuthn) is stored on the server. Biometric data never leaves your device.

Important: this is a demonstration prototype and the service doesn't meet the standards of a production product. Email and username are encrypted at rest in the database (AES-256-GCM); the email is used only for verification and password recovery. Passwords are not stored in clear (only a salted scrypt hash) and failed sign-in attempts are limited per IP address and per username. Don't enter real sensitive information: use test data.

Encryption keys: private keys never leave your device and are stored encrypted with your password (PBKDF2 + AES-GCM), as is the local cache of messages already read. The server holds only your public key and a batch of one-time public keys, which it deletes on each delivery.

Purpose of processing

The data is used solely to make the demo work (authentication, messaging, contacts). It is not shared with third parties and not used for advertising profiling.

Retention

Data is kept in a persistent database until you delete the profile; during updates or demo resets it may still be deleted without notice.

Your rights

You can request deletion of the data entered in the prototype at any time by writing via the contact details above.

Securmy features: vault, P2P transfers and calls

Vault files, notes, passwords and backups stay on your device, encrypted with a key that never leaves it: we do not receive them and cannot read or recover them.

Sync (paid plan only): the server stores files, notes and passwords already encrypted on your device, without the key to open them, until you or your account delete them. For payments we use Stripe: we neither see nor store your card details.

For P2P transfers and calls, the content travels directly between devices, encrypted. The server only handles connection information (SDP and ICE candidates), kept in memory for at most one hour and then deleted; the other participant and a public STUN server can see your IP address.

If you enable two-step verification we store the TOTP secret, encrypted at rest; view-once messages are deleted from the server a few seconds after being opened.