Privacy and security

This page explains plainly where your data goes when you use the Jennefer apps, and which protections apply. The full legal text is in our Privacy Policy.

How it is built#

Agent runs are planned and driven by Jennefer's hosted runtime. The runtime never touches your disk, shell or model directly. It reaches them only through the app on your computer: model requests, file actions and commands are sent to the app, which checks them and carries them out.

• The app accepts requests only during a run you started, and only inside your open project folder or folders you approved.
• The app keeps its own record of your approvals, so the server cannot approve anything by itself. See Approvals and safety.
• Model requests go from the app to the Engine on your computer, which passes them to your model.
• Closing the app stops a run. Nothing keeps running on the server.

One exception: a build you start from your phone runs on the server, works in your cloud sandbox, and calls an endpoint kept in your account. It never touches your computer, and it runs until it ends or you stop it.

What stays on your computer#

• Your project files. Jennefer's servers do not keep copies.
• Local models and everything the Engine runs: packs, MCP servers and their config.
• Your endpoint's API key and your sign-in, kept in Windows Credential Manager. Apps never see the endpoint key; the Engine adds it. The key leaves this computer only if you keep that endpoint in your account (see below).
• What Studio makes: images, videos, designs, 3D models and brands.
• Workshop apps and their saved data.
• IDE conversations, saved per project folder, and run state in .jennefer/dag_state.json in your project.
• Requests from your connected apps, which go only to the model on this computer.

What passes through servers#

Because the runtime plans and drives agents, the content it needs passes through Jennefer's servers in transit: your prompts, the file contents and command output that agents read, and the results they return. We do not claim that your code never leaves your computer.

• Your prompts go to the model you chose: a local model on your computer, or the provider behind your endpoint, under that provider's terms.
• Answers you give to a secret question become part of the conversation, so avoid pasting keys you cannot rotate.
• Jennefer Mobile messages to your home model pass through Jennefer's servers to your computer and are not stored there.
• If you keep an endpoint in your account, Jennefer's servers call that endpoint themselves, with the stored key, for your Mobile chats with it and for builds from your phone. Messages and answers pass through and are not stored.
• PDFs you attach in Mobile are read in server memory to get their text and are not kept.
• Builds from your phone keep your request, the agent's steps and its summary in server memory for up to 24 hours, for your last 10 builds, so the phone can show them.
• Studio checks in with Jennefer before each image or video to count your daily use. Your prompts and images are not sent.

What is stored with your account#

• Your account, plan, team and settings such as connected-app registrations.
• Your library's cloud copies, only if you turn on cloud backup.
• Files in cloud sandboxes, until you delete the sandbox or it is cleaned up. Sandboxes run on our hosting provider, E2B. Preview links are public while a sandbox runs.
• Team shared keys, encrypted. Members allowed to use them can see them. See Teams.
• Endpoints you keep in your account, only if you turn on Use from your phone without this computer in Hub > Models > Your endpoint: the address, model, context window, effort and API key. The key is sent once and stored encrypted, and only Jennefer's servers decrypt it, for a request you start. Your plan and the address approval are checked on every use. Turn the switch off or remove the model to delete the copy. See Your endpoint.
• Agent runs that Mobile shows, for 24 hours, in memory.

Analytics#

• The Hub asks once, during first-run setup, whether you want to share anonymous usage data. It is off unless you choose Share usage data, and you can change it in Hub > Settings > Privacy. The choice applies to every Jennefer app on this computer.
• When it is on, the Engine on your computer sends a fixed list of events to Mixpanel, such as an app opening, an app being installed or updated, or a model download finishing. Each event carries the app and Engine versions, the operating system and processor type, a random device ID and, after sign-in, a pseudonymous account ID. Never your email address.
• The apps never send your code, prompts, model responses, file names or paths, terminal output, error messages or URLs.
• What is sent in Hub > Settings > Privacy shows the events exactly as they leave this computer. Turning sharing off deletes the events not sent yet.
• For now, the IDE asks separately. Its choice is in IDE Settings > Privacy, and it sends its events to PostHog, with the same limits.
• Jennefer Mobile sends no usage analytics.

The website and the portal use PostHog analytics only with your consent where the law requires it. The full list of providers is in the Privacy Policy.

Sign-in and two-factor#

• Sign-in happens on a hosted page in your browser, with Google, Microsoft or email.
• Accounts are never merged automatically by email. You prove ownership by signing in with the existing method first.
• With two-factor on, purchases, plan changes, creating a cloud sandbox and sign-in method changes ask for a fresh 6-digit code.

Signed installers#

Jennefer Setup and every app installer are code-signed. Setup and the Hub check the signature of each download before they install it. Download Jennefer only from your account at portal.jennefer.dev.

Payments#

Payments are handled by Stripe in the portal. Jennefer does not receive your full card number.

The .jennefer folder#

Almost everything Jennefer keeps on your computer is in the .jennefer folder of your user profile. The table in Engine lists what is where. Add .jennefer to your project's .gitignore if you do not want run state in version control.

FAQ#