Privacy

Data controller

Controller: to follow. To exercise your rights, write to ciao@enrosa.live.

Enrosa is the controller for accounts, sign-in, payments, invoicing and security of the service; for the contents of rooms (audio, captions, AI-generated minutes, speaker names, listener count) it acts as processor on behalf of the organizer, who is the controller.

Data we collect

Organizer account: email and, if provided, name (including the one received from Google, if the account has none yet).

Payment data: handled by Stripe; Enrosa never stores card numbers.

Room metadata: event name, languages, schedule, glossary.

Captions generated during the event, kept for at most 24 hours after the last session ends, unless the organizer requests an export. During those 24 hours the organizer can read the transcript again on the page of the ended event.

Enrosa never records or stores audio and never creates voiceprints of any kind. The transcription provider (Soniox) processes audio in real time without storing it.

Voice separation (when on in a room): the transcription provider tells speakers apart with anonymous ids ("Voice 1", "Voice 2") valid only for the current session. The organizer assigns the names from the console: the voice-to-name mapping is deleted when the event ends, while the name stays attached to the caption lines for as long as they are kept (at most 24 hours), appears in transcripts exported by the organizer and may appear in the event minutes for as long as they are kept (30 days). No voice is recognized from one event to the next.

Speakers: the voice picked up by the organizer's microphone is sent in real time to the transcription provider and turned into text; the spoken content and any name assigned by the organizer appear in the captions and in the minutes. Source of the data: the event organizer.

Event minutes: at the end of every event an artificial intelligence model writes, from the captions, minutes with a summary, topics, decisions, action items, open questions and short quotes; speakers appear with the name assigned by the organizer or as "Voice N". The minutes are visible only to the organizer, who can download them as a PDF or have them translated into other languages. They can be regenerated only while the captions exist; if there is too little speech, no minutes are written.

Listener pages require no account: a random identifier is stored in the browser's localStorage to avoid duplicate counts.

Sign-in with an email code: when a browser that has never logged in with that email asks for a code, the login page runs the Cloudflare Turnstile anti-abuse check, which processes the IP address and technical browser data to tell people from automated programs. To limit repeated requests we keep a hash of the IP address with the code request and delete it within two days. Signing in with Google or with a passkey does not use Turnstile.

Security notices: when a passkey is added to or removed from an account, we send an email to the account's address.

Sign-in with Google (optional)

If the organizer chooses "Continue with Google", Google (Google Ireland Limited and Google LLC) verifies their identity and sends Enrosa the verified email address, the name and a stable identifier of the Google account. If an Enrosa account with the same email already exists, the Google sign-in is linked to that account: at once for a Gmail address or a Google Workspace address of its own domain, otherwise only after a sign-in with the email code.

Enrosa stores the identifier and the email to recognize later sign-ins, together with the dates of linking and last use; it does not store the profile picture and gets no access to Gmail, contacts, Drive or any other data of the Google account. Sign-in with Google is optional: the email code always remains available.

During sign-in Google processes the IP address and technical browser data as an independent controller, under its own privacy policy: https://policies.google.com/privacy. Legal basis for Enrosa: performance of the contract (Art. 6(1)(b) GDPR). For transfers to the United States, Standard Contractual Clauses (SCCs) and, where the provider is certified, the EU-U.S. Data Privacy Framework (DPF) apply.

Passkeys

The organizer can turn on a passkey to sign in with Face ID, Touch ID, Windows Hello, a fingerprint or the device PIN. Biometric matching happens only on the device: biometric data never leave the device and Enrosa processes no biometric data.

For each passkey Enrosa stores only the public key, the credential identifier, the signature counter, the supported transports, the device type and whether the passkey is synced, an editable device label, and the dates of creation and last use. Each passkey can be removed from the Account page and is deleted together with the account.

Purposes and legal basis

Account, sign-in (email code, Google, passkey), rooms, captions and minutes: performance of the contract (Art. 6(1)(b) GDPR). For the spoken content in captions and minutes Enrosa acts as processor on behalf of the organizer, who informs speakers and participants.

Invoices and tax obligations: legal obligation (Art. 6(1)(c) GDPR).

Anti-abuse check at login (Turnstile), IP address hash, security notices by email, abuse reports and technical logs: legitimate interest in the security of the service (Art. 6(1)(f) GDPR).

Providers and transfers

We rely on third-party providers for hosting, transcription, translation, writing and laying out the minutes, payments, email and e-invoicing: the full list is on the Sub-processors page.

Some providers are based in the United States (Soniox, OpenRouter, Cloudflare, Stripe, Microsoft Azure) and involve a transfer of data to a non-EU country; others are based in the EU (Inceptron in Sweden and Finland, NextBit in Spain, A-Cube in Italy). For transfers to the United States we use Standard Contractual Clauses (SCCs) and, where the provider is certified, the EU-U.S. Data Privacy Framework (DPF). Rooms and the database are stored in EU jurisdiction; the minutes PDF is generated on demand in Cloudflare's network, which may be outside the EU, and is not stored.

Retention

Captions and transcript: at most 24 hours after the event's last session ends, unless exported; at once, together with the minutes, if the organizer deletes the event.

AI-generated minutes: 30 days after the event's last session ends, then deleted automatically by the daily cleanup, so within the following 24 hours; at once if the organizer deletes the event.

Rooms and their metadata: deleted 30 days after the last session ends; unactivated drafts after 90 days of inactivity. These deletions run with the daily automatic cleanup, so within 24 hours after the deadline.

Passkeys: until removed from the Account page or until the account is deleted. Google link and other account data: until the account is deleted.

Invoices and billing data: 10 years (Art. 2220 of the Italian Civil Code).

Your rights

Access, rectification, erasure, restriction (Art. 18), portability and objection, under the GDPR. You can also lodge a complaint with the competent data protection authority.

We do not make decisions based solely on automated processing within the meaning of Art. 22.

Further information

Providing your email is necessary to use the organizer console; listeners do not have to provide any data.

No data protection officer (DPO) has been appointed.

The console is reserved for adults; the listener pages do not collect identifying data.