Security and privacy
The sensitive part of a meeting — the recording, the transcript, and the summary — lives on your computer.
Where your meetings live
Recordings, imported media, transcripts, and summary documents are written to a local folder you choose. Brifta keeps no copy of your finished meeting files.
What AI processing sends
Starting processing uploads the meeting audio for transcription, then sends transcript text and meeting context for summarization. Rewrite and translation send the summary you already have. Nothing leaves your PC until you start one of those actions.
How long anything is kept
Uploaded audio is temporary and is deleted once its job finishes, with a storage lifecycle rule as a backstop. Generated result text is removed after your app has retrieved it.
Your account
Signing in uses a one-time code sent to your email address, so there is no password to leak. The account holds your plan, processing balance, and billing records — not your meeting content.
In transit
Traffic between the app, this website, and the Brifta service uses HTTPS.
Your device is the perimeter
Because meeting files are ordinary files, anyone with access to your Windows account, your backups, or a sync tool pointed at that folder can read them. Protect them the way you protect other sensitive documents.
Recording responsibly
Brifta asks you to confirm that participants are aware of and accept the recording, and offers a notice you can read aloud or paste into the meeting chat. Complying with recording, consent, privacy, and workplace rules is your responsibility; Brifta does not give legal advice.
Reporting a problem
If you think you have found a security issue, email us with enough detail to reproduce it. Please give us a chance to fix it before posting it publicly.