Privacy Policy

Last updated 29 August 2026

The short version: FRIGG listens only while a session is running, sends only what it needs to answer, and stores as little as it can. This page says exactly what that means.

The microphone

It opens when you press Start and closes when you press Stop. Silence is dropped before it reaches any model: transcription only runs on detected speech. FRIGG never records in the background, and it never listens because the app is merely open.

Your screen

When you ask FRIGG something, it takes one screenshot at that moment and sends it with your question, so the answer can be about the error you are actually looking at rather than a description of it. That happens per question, never in the background, and no copy is kept on either end.

It is on by default and it is a real thing to send, so there is a switch: Settings › What FRIGG sees. Turn it off and FRIGG answers from what was said instead, with nothing from your screen leaving the Mac. macOS also gates this independently — without Screen Recording permission there is no picture to send, and FRIGG answers without one.

Separately, the Detectable switch hides the FRIGG window itself from screen sharing and recording. It is off by default, so FRIGG does not appear in your calls unless you turn it on.

What leaves your Mac

• Every plan. Audio goes from your Mac to OpenAI using a short-lived credential we issue; prompts and the relevant transcript pass through our API to OpenAI. We do not store transcripts, prompts, or answers. OpenAI processes them under its own API terms and, at the time of writing, does not train on API data.
• Your pet. The words you type to describe it go to OpenAI to be drawn, and we keep those words so the drawing can be made again on another Mac. The picture itself is written to your Mac and nowhere else.

What we store, for every account

• Your email address, so you can sign in.
• Your subscription status, plan, and renewal date, mirrored from Stripe. Empty until you pay.
• Three counters per month: seconds of speech, sessions started, and number of answers, so the free allowance and the plan limit can be enforced.
• The description you typed for each pet, and when you made it.

That is the whole list. No transcripts, no audio, no screenshots, no tracking pixels, no advertising, and nothing sold or shared with anyone.

Three counts

FRIGG counts three things so we can tell whether anyone uses it twice: the app opened, a session started, an assist ran. Each count carries a random id that FRIGG generates on your Mac, plus the app and macOS version. That id is not derived from your machine, is not linked to your email or subscription, and is not shared with anyone. No analytics SDK is involved, so no IP address or device profile reaches a third party. It is the whole of our usage measurement.

The same switch also covers crash reports. When FRIGG hits an error it did not expect, it sends the error message, the stack trace, the app and macOS version, and that same random id, capped at twenty per launch so a crash loop cannot become a flood. A stack trace is machine text about our own code, but it can carry a file path from your Mac, so it is worth knowing it goes.

Turn it off in Settings, under Usage counts, and FRIGG sends nothing — neither counts nor crashes.

Reading your editor log, if you let it

A session where you built for hours with an agent and said almost nothing out loud produces a recap written from a nearly empty transcript — the one case where the recap matters most. So FRIGG can offer to read Claude Code's own log for the hours the session covered, and write the notes from what you built rather than only what you said.

It asks first, and does nothing until you say yes; the answer is remembered on your Mac and you can change it in Settings. Only the session's own window is read, never the rest of the log. Your own messages go in full, each tool call becomes a one-line trace, and the agent's prose is clipped. Tool results — file contents, shell output — are dropped entirely. What survives that goes to the model with the notes request, on the same terms as the transcript, and is not stored.

Where your session notes live

Session notes and history are written to a file on your own Mac, under ~/.frigg/. If you point FRIGG at your own Supabase project, they go there instead. Either way they are yours; deleting a session in the app deletes it.

Payments

Stripe handles checkout and stores your card. We receive a customer id and the subscription status, never card details. Stripe's own privacy policy covers what it collects.

Your choices

Email hyeonminsong7@gmail.com to get a copy of what we hold about you, correct it, or delete it. Deleting your account removes your row and cancels the subscription. California residents have these rights under the CCPA; we honour them for everyone, and we do not sell personal information.

Children

FRIGG is for developers at work and is not directed at anyone under 13.