Help and account

Privacy: what stays and what is sent

What Jevie keeps stays on your Mac; what it counts is numbers and fixed words, never what you typed or said, sent only after your yes.

FreeMac

Choose an example to copy it, then try it in Jevie.

Use itHow it worksLimitsWhere it's kept

Use it

• onboarding's question about usage countsIts switch starts off, so only turning it on is a yes; no means nothing is even queued
• open the record page (http://127.0.0.1:63798/)What Jevie sends lists every count before it goes
• what do you rememberforget that …What Jevie keeps about you, and removing it (memory)
• screen memory settingsWhat is captured from the screen, and which apps never are
• agent accesswhat can my agents accessdoes claude have full disk accessWhat agents and programs in your sessions can reach on this Mac: Full Disk Access, Screen & System Audio Recording, Microphone, Camera, Accessibility, Notifications; Grant on a missing one shows macOS's question, or opens its exact list in System Settings with Jevie's icon to drag in. Also on the session wall: ⇧⌘P → Agent Access…, and Wall Settings… → Agent Access…
• drop a file on a terminal on the session wallIts path is typed at the cursor; when it is somewhere agents cannot open (Downloads, Desktop, Documents, another app's data, Mail) a line over the terminal says so, with Grant; a screenshot dragged from its thumbnail is copied to ~/.jevie/drops first, since macOS deletes that file in moments
• the phone app's menu without a Mac → Delete my Jevie Cloud accountThe cloud forgets the phone's token and usage; a paid plan is cancelled first

How it works

What you keep stays on your Mac, in ~/.jevie. Usage counts are numbers and fixed words only, and nothing is sent until you say yes. A model sees a sentence only when one is needed to answer it.

• Kept on your Mac: notes, memory and profile, screen memory, clipboard history, routines, snippets, rooms and the record of every request. Dictation is heard on the Mac; nothing you say is sent to be transcribed.
• Usage counts: every count has a fixed shape of names, closed sets of words and numbers, with no field for free text, so nothing you typed, no title, path or address can pass. Counts wait in a file you can read and are sent once a day for finished days only; counts Jevie Cloud cannot keep stay in the file. Counted: each sentence and task; a day used, once per place (mac, windows, phone); the first sentence and first finished task, once ever; a connector's sign-in by its well-known name (else other). Once a day a Mac counts what it has: whether search by meaning and its model are ready, how many helpers are missing, whether Parakeet and Jev's voice are installed, and yes or no per macOS permission (Accessibility, Screen Recording, microphone, calendar). A crash is one count naming only the part that fell over (app, daemon, worker, listener); no stack, message or file name.
• Sent to a model: when Jevie needs one (deciding, answering, planning), the sentence and the context it needs go to the provider, through Jevie Cloud or directly with your own keys. A file or your screen goes only when you ask about it; what Jevie remembers about you goes when it helps. The launcher, files, clipboard, routines and dictation send nothing. Accessibility lets Jevie read and press in your apps; only what a sentence needs leaves the Mac.
• Who gets it: Jevie Cloud runs on Cloudflare and stores no text of your requests, only your account token, your plan and this month's usage numbers. A request that needs a model may go to Anthropic, Inception Labs (Mercury), OpenRouter, Typesafe or Google (Gemini), and web search and page reading use TinyFish and treg; they handle it under their own terms.
• Keystrokes: Jevie never logs them. Its event tap reads a key's code only to tell ⌘ held alone or tapped twice from a shortcut, and writes nothing down.
• Kept on your phone: the phone's contacts, once you allow them, are read by the Jevie app to find who call anyutka means; they stay on the phone, except the names you are likeliest to say (no numbers or addresses), which go to your own paired Mac while you talk so its listener hears them right (kept in ~/.jevie/phone-terms.json, never Jevie Cloud or a model), and a call or text to someone found in them is decided there, without asking your Mac (phone actions).
• Google suggestions as you type (off until you say turn on google suggestions): the words typed in the Mac's palette go to Google's suggestion address, with no cookies, to draw its completion after the caret. Never an address, an email, a path, four digits in a row, a command, a trigger line or a reply to a session.
• Coding agents (Claude Code, Codex) talk to their own providers under your login; Jevie only follows their sessions on the Mac.
• What agents can reach: macOS decides what a program may open by asking the process it holds responsible for it, and every program in Jevie's sessions answers to Jevie.app (the app or its daemon starts the session holder, which starts the program), even sessions started before Jevie last restarted. So what Jevie is granted in Privacy & Security, its sessions are, and the agent access card reads it in Jevie itself, without a prompt. The doctor lists each missing one too.
• The public policy is https://jevie.ai/privacy

Limits

• An answer from the web or a model needs the sentence to leave the Mac.
• Screen memory keeps what its settings allow until you delete it.
• Agent access is read by the Mac app (at launch and whenever Jevie comes forward); without the app, agent access shows its last reading. Whether Desktop, Documents and Downloads were allowed one by one is TCC's own answer, asked through a private call; when macOS has none, a drop says macOS will ask rather than guess.
• Granting Full Disk Access takes System Settings: macOS has no question for it.

Where it's kept

The counts waiting to go: ~/.jevie/telemetry-queue.jsonl. Everything else: ~/.jevie.

In Jevie, help privacy answers from this page as you type.

Related

Updated 6 November 2026 · Something wrong or missing? Tell us