What we keep.

Last updated 30 August 2026.

Two separate things are worth separating: the app, which collects nothing, and this website, which collects an email address if you type one in to download the app, and your message if you write to us.

The app

Briska has no account system, no analytics, no crash reporting and no update check. It does not send your voice, your text or your notes anywhere, because there is nowhere for them to go: no server exists to receive them.

Its only network requests are model downloads. Most of those happen the first time you run it; two are deferred until you switch on the feature that needs them, because voice commands and meeting speaker labels each pull their own model when you enable them. Nothing else ever goes out, and once a model is on disk that feature works with the network off.

Everything it produces stays in a folder on your Mac that you can open, inspect and delete, and nothing you dictate is used to train any model. What that buys you, and what we won't claim, is on the home page.

The one exception, stated plainly

When you confirm an action (a reminder, a calendar event, an email draft) Briska hands that text to Apple's own apps. Those apps then sync it wherever you have told them to, which for most people means iCloud. Briska isn't doing the sending and can't see where it goes, but the text does leave your Mac at that point, and you should know that before you confirm one.

Nothing else works this way. It only ever happens to something you explicitly approved on a confirmation card, never to a transcript, a recording or a note. The app says the same thing in Settings → Privacy, and every action it proposes is written to a local log you can read.

This website

If you download Briska

We store:

• The email address you typed.
• The date you submitted it, and which form on the site you used.

That's the whole record: three fields. We never ask for your name, your company or anything else, no confirmation email is sent when you sign up (there is nothing to confirm into, because the address just sits in the list), and the list lives in a database on a server we run ourselves rather than in a third-party marketing platform.

We will use it for exactly one thing: telling you about a change to Briska big enough that you would want to hear it from us — a new version, or a major feature. That is rare, and it is the only thing the address is ever used for. Giving us the address is what starts the download; it does not create an account, and there is no account to create. Every email we ever send will have a one-click unsubscribe, which deletes you from the list. If you'd rather not wait for an email to do that, ask and we'll remove you.

If you write to us

We store the message you wrote, the topic you picked, your email address, the date, and which form on the site you used. The address is required so that a reply has somewhere to go. It is used for that and nothing else, and it is never added to the download list or any other. It goes into the same database on the same server, is never joined to anything else, and is deleted on request the same way.

If you just read the site

There is no analytics script, no cookie banner and no cookie, because there is nothing setting one. The site loads no third-party resources at all, no fonts, no scripts, no images from anywhere but this domain, so simply reading a page tells nobody but us that you did.

Our web server keeps ordinary access logs (the requested URL, timestamp, and the requesting address) for a short window, for the boring reason that a server with no logs can't be debugged or defended. They aren't joined to anything else and aren't used to build a profile.

The download host keeps less than that: its log records what was requested and how much of it arrived, with no address and no user agent, so there is no version of “who downloaded Briska” for it to hold.

Anti-abuse is the one exception worth naming: the signup endpoint rate-limits by IP address, held in memory only, so a single machine can't submit thousands of addresses. Nothing is written to disk for that, and it is gone when the server restarts.

Third parties

Model downloads come from Hugging Face, which sees a request for a public file from your IP address, the same as any download. When the launch email is eventually sent it will go through an email delivery provider, because mail doesn't reliably arrive any other way, and it means your address passes through them for that send; this page will name the provider before that happens.

Otherwise there are none. No CDN in front of the site, no CAPTCHA, no embedded video, no ad network.

Your data

Ask us and we will tell you exactly what the subscriber or the contact table holds for your address, or delete it. Since the record is an email address, a date and, for a message, the topic and the text you wrote, both requests are quick.

Changes

If this page changes in a way that affects what we collect, the date at the top changes with it and everyone on the list is told before it takes effect.