Security & privacy

Where the recording goes.

This page is written to be forwarded. If a client's legal or IT team has asked what you are using to record their meetings, send them here — it answers the questions they will ask, in the order they ask them, without marketing language.

01Data residency

Swiss hosted, EU at the furthest.

The application, the database and the audio files run on Infomaniak infrastructure in Switzerland. Notizli is operated from Switzerland by a Swiss sole trader, and is subject to the revised Federal Act on Data Protection (revFADP) as well as the GDPR for EU-resident participants.

Audio is written to a private bucket that is not publicly addressable. It is reachable only through short-lived signed links issued to the account that made the recording, and it is deleted automatically within 24 hours of the meeting.

Transcripts, minutes and commitments are retained until you delete them, in a database with row-level security enforced per user — one account physically cannot read another account's records, regardless of what the application code does.

02Sub-processors

The complete list. Anything not named here does not receive meeting content.

ProcessorPurposeLocation
InfomaniakHosting — application, database, recordingsSwitzerland
Infomaniak AIMinutes and commitment extractionSwitzerland
Deepgram (EU host)Speech to text, speaker separationEuropean Union
Google DriveOptional — only if you connect it, only your own DriveYour organisation's tenancy
Microsoft OneDriveOptional — instead of Google Drive, only Notizli's own folderYour organisation's tenancy

Meeting content is never used to train any model, by Notizli or by any provider listed above.

04The AI connection

Read-mostly, per user, revocable.

Two ways to give an assistant your history, and both are scoped to one person.

Drive context files. Notizli writes a document per project into your own Google Drive or OneDrive. It lives in your organisation's tenancy, under your organisation's policy, and any assistant with access to your Drive can read it. Notizli only ever writes to the folder it created.

The connector. A standard OAuth 2.1 flow — no shared key, no service account. Each person signs in and approves it themselves, and the token belongs to that individual. It can read that user's meetings and write their own commitments and notes. It cannot delete a meeting, reach another user's data, retrieve recording audio, or send anything outbound. Revoked the moment the user disconnects it.

The deeper technical brief for a connector review is on the connector page.

05Your data, and theirs

Export anything, any time

Transcripts, minutes and commitments leave in a readable format. Your history is not a lock-in mechanism.

Delete anything, any time

Deleting a meeting removes its transcript, minutes, commitments and audio, and moves its Drive or OneDrive copy to the bin. Deleting your account, from Settings, removes everything.

Participant requests

If a meeting participant asks you to delete a recording of them, you can do it yourself immediately — you do not need to contact support.

If Notizli shuts down

You get notice and an export window. A one-person product should be explicit about this rather than leave you to wonder.

Questions a security reviewer needs answered that aren't here — hello@notizli.ch. A real person answers, usually the same day.