Really Really Me Second-channel identity verification for chats, calls, and more

Privacy Policy

Last updated: 2 June 2026

Who we are

Really Really Me is operated by Marco Matarazzo, acting as the data controller. You can reach us at marco@esagonorosso.com for any matter related to this privacy policy or to exercise your rights.

What information we process

When you use Really Really Me, the following personal data is processed:

We do not collect, store, or log: IP addresses, user-agent strings, geolocation, device identifiers, or any other identifier. We do not use analytics services, advertising networks, or third-party tracking.

Why we process this data (legal basis)

We rely on legitimate interest (Article 6(1)(f) GDPR): both the host and the invitees have a clear interest in confirming, through a separate channel, the identity of the person they are communicating with. We process the minimum personal data necessary to deliver that service, nothing more.

How long we keep data

Where data is stored

All data is stored on a single server located in the European Union (Paris, France), operated by Scaleway SAS. We do not transfer personal data outside the EU/EEA.

Who can access your data

Only the host of the verification room (identified by an HttpOnly cookie in their browser) can see the verifications submitted to that room, and only for as long as the room is active. We do not share data with any third party. We do not sell, rent, or otherwise transfer personal data to anyone.

Your rights under GDPR

You have the right to:

To exercise any of these rights, email marco@esagonorosso.com. We will respond within 30 days. Please be aware that, because all data is automatically deleted within 1 hour, by the time most requests are processed there is typically nothing left to access or delete.

Security

The service is served exclusively over HTTPS with a valid TLS certificate. Cookies are marked HttpOnly and SameSite=Lax; over HTTPS they are also marked Secure. The database is on the same machine as the application, not exposed to the public network.

Changes to this policy

We may update this policy as the service evolves. The "last updated" date at the top of this page reflects the most recent revision.