Meeting data stays under your control.

Who is responsible?

Data controller: the Compacio operator identified in the service's legal notice. The operator must publish a legal name, business address and a privacy contact before commercial launch.

What is processed?

• Microphone or system audio during a meeting session.
• Speaker labels, transcript text, translations and locally generated meeting insights.
• Meeting settings stored in the browser only, such as language and speaker count.

Why and where?

The Windows engine processes audio, speech recognition and speaker separation on the user's computer. Local only does not upload audio or call a remote model. If the organiser explicitly chooses API mode, only transcript text after obvious local redaction is sent directly from the device to the selected provider; Compacio does not proxy or store the key or transcript. The provider's retention and transfer policy applies. The mobile PWA sends microphone frames only to the paired private Windows engine during the active session. If that engine is unavailable, the app can offer a separately labelled browser speech fallback so a meeting does not become a dead screen. Browser recognition may process audio outside the device; reconnect the local engine or stop the meeting when zero egress is required.

Participant notice

The meeting organiser must inform every participant before capture begins and choose the lawful basis appropriate to the context. A single organiser checkbox does not replace participant information or any consent required by local law. Participants can ask the organiser to stop capture and can request access, correction, deletion or restriction through the organiser.

Retention and exports

Compacio keeps active data in the local engine process. Completed meeting records can be saved to the device's browser storage and managed at History & account; audio is never saved there. You can delete an individual meeting or all local account data. Exported files are under your control; delete them when no longer needed. The app does not silently create a cloud backup.

Optional cloud features

Optional remote translation is separately labelled and requires a separate acknowledgement. OpenRouter is offered only as a 60-second text-translation trial using the user's own key. Provider policies differ; select a zero-data-retention or in-region policy where available, and use Local only for zero egress.

Hosted history uses Google OAuth with a short-lived PKCE exchange and an HTTP-only session; it stores only the user-owned meeting records in D1. Local Windows, macOS and PWA use never require an account, and anonymous Local mode never uploads transcript content.

Your rights

Depending on the lawful basis, you may have rights of access, rectification, erasure, restriction, objection and portability. Contact the operator shown in the legal notice. You may also complain to the relevant data protection authority, such as the CNIL in France.