Jennefer Privacy Policy

This Privacy Policy explains how Ahmet Enes LLC, a Delaware limited liability company ("Jennefer," "we," "us"), collects, uses, and shares personal information when you visit jennefer.dev and its subdomains (the "Site"), join our early access waitlist, contact us or use our support chat, create a Jennefer account, or use the Jennefer desktop app (the "App"), Jennefer Cloud, and the Jennefer Mobile app for Android.

1. The short version

• The Jennefer desktop app runs on your computer, but its agents are coordinated by Jennefer's servers. While a task runs, your prompts, the files and command output the agent works with, and the model's responses pass through our servers. We do not save them to our databases, and we do not use them to train AI models.
• With a local model, the model itself runs on your device. With your own API key, your key stays on your device and requests go from your device to the provider you chose. The exception is when you choose to keep an endpoint in your Jennefer account so Jennefer Mobile can use it while your computer is off: then we store that key encrypted, and our servers send those requests to your provider.
• The Jennefer apps on your computer send anonymous usage statistics only if you turn them on in Jennefer Hub, and never your code, prompts, or file names. They have no crash-reporting tools.
• Our website and account portal use analytics only with your consent where the law requires it, plus a support chat and a waitlist form.
• We do not sell your personal information and do not use it for targeted advertising.
• If you publish an app from Jennefer Workshop, every Jennefer user can find and open the built app. Its source code goes only to the Jennefer team members who review apps.
• Jennefer Premium, a future edition that runs without our servers, will come with its own privacy notice.

2. Information we collect

Information you give us.

• Waitlist: your name or organization, work email, a description of what you are building, and a record of your consent (the time, the policy version you agreed to, and your IP address). If you apply for Jennefer Premium early access, we also collect optional company, role, team size, operating system, hardware, and model-setup answers, used only to manage early access.
• Messages: when you email us or use support chat, your messages and any contact details you include. In the support chat, an AI assistant provided by BoldDesk answers first, using our public help content, and a person from our team can take over at any time.
• Account: when you sign in, we receive your email address, name, and profile picture from our sign-in provider, plus any other sign-in methods you link to your account.
• Billing: if you buy a plan or credits, our payment processor (Stripe) collects your payment details. We receive and store your billing email, customer ID, plan, and payment status, never your full card number.
• Teams: the names and email addresses of people you invite to your team.
• Custom endpoint access: if you request access to use a custom model endpoint, your name, company, contact email, and intended use.

Information collected automatically on the Site. We use PostHog to understand how visitors use the Site, including the account portal. When analytics is on, PostHog sets a first-party cookie with a random identifier and receives the pages you view, a few interactions such as clicking the waitlist submit button or starting a checkout (never what you type), the website that sent you (its domain only, such as google.com, never the full address) and any campaign tags in the link you followed (such as utm_source), your browser and device type, and an approximate location derived from your IP address. When you are signed in to the portal, we link these events to a pseudonymous account ID that we derive on our servers, never your email address. We do not record your sessions. These analytics requests reach PostHog through our own addresses (jennefer.dev/ingest, and portal.jennefer.dev/ingest for the account portal), which pass them on without storing them. If you are in the EEA, the UK, or Switzerland, PostHog does not load until you accept it in our banner. Elsewhere, you can turn analytics off at any time with the "Analytics" link in the footer. We treat Global Privacy Control and Do Not Track signals as an opt-out.

Information from the App.

• Agent tasks: to run agents, the App connects to our servers, which coordinate each task. Your prompts, the files and command output the agent works with, and the model's responses pass through our servers while the task runs. We process them only to run the task.
• Service requests: the App contacts our servers and our sign-in provider to sign you in, check your plan and credits, and check for updates. These requests include your IP address, the App version, and your account token.
• Third-party components: the code editor and file previews load some components from public content delivery networks (jsDelivr, unpkg, Tailwind CDN, and Google Fonts). Those providers receive your IP address when the components load.
• Usage statistics: off unless you turn them on in Jennefer Hub, during first-run setup or in Settings › Privacy. The choice applies to every Jennefer app on your computer. If you opt in, the Jennefer Engine on your computer sends a fixed list of events to Mixpanel, such as the Hub or an app opening, an app being installed or updated, a model download starting or finishing (with the model's name from the Jennefer model catalog), or first-run setup finishing, with details chosen only from fixed values. Each event carries the app and Engine versions, your operating system and processor type, and a random device identifier created on your computer. After you sign in, events are linked to a pseudonymous account ID, never your email address. We ask Mixpanel not to derive a location from your IP address. The apps never send your code, prompts, model responses, file names or paths, terminal output, error messages, or URLs. You can see exactly what is sent in Hub › Settings › Privacy, and turning statistics off deletes any events not yet sent. For now, the Jennefer IDE asks separately and sends its statistics to PostHog, with the same limits.

Information from Jennefer Mobile.

• Sign-in: the same Jennefer account, through our sign-in provider. Your sign-in tokens are kept in your phone's secure storage.
• Device: when you sign in, the app registers your phone with us: a random device identifier created by the app, the phone's model name (for example "Pixel 9"), the platform, and the dates it was added and last used. We use it to send notifications to the right phone. It is deleted when you sign out on the phone or delete your account.
• Your computer's model ("Home model"): if you turn on phone access in Jennefer Hub and allow a phone, your messages from the phone, including the photos and file text you attach, and the model's replies pass through our servers to the Jennefer Engine on your computer and back, over encrypted connections. If the model you pick on your computer uses your own endpoint, the Engine on your computer sends the request to that provider, as it does for the desktop apps. We do not save messages or replies to our databases. The conversations, photos, and file text are stored only on your phone. Jennefer Hub keeps the list of phones you allowed on your computer.
• PDF attachments: when you attach a PDF in Jennefer Mobile, the phone sends the file to our servers, which read its text in memory and send the text back to the phone. We do not keep the file or its text. Text files are read on the phone.
• Endpoint kept in your account: if you have a paid plan and turn on "Use from your phone without this computer" for one of your endpoint models in Jennefer Hub, the Hub sends that endpoint's address, model name, settings, and API key to our servers once. We store the key encrypted and decrypt it only to make a request you start, after checking your plan and the endpoint's approval. Your chats from the phone with that model, and app builds from the phone, then go from our servers directly to that provider, under its own terms, without your computer. We pass the messages and replies through and do not save them to our databases. We also record when the endpoint was stored, changed, and last used, and we log when you add or remove one, with its address and model, for security.
• App builds from the phone ("Build by chat"): if you have a Cloud plan, you can ask an agent from the phone to build or change an app in one of your existing cloud sandboxes, using an endpoint kept in your account. Your request, the photos and file text you attach, and recent messages from that build chat go through our servers to your endpoint provider, and the agent works with the files in the sandbox, which runs at E2B. While the build runs, and for up to 24 hours after it ends, our servers keep your request, the agent's steps (short lines about what it did, such as the commands it ran and their results), and its summary in memory so the phone can show them, for at most your last 10 builds. They are cleared when our servers restart. Build chats are stored only on your phone.
• Runs and approvals: to show your agent runs on the phone, our servers keep a short list of your runs from the last 24 hours: the start of your request, the folder name (not the full path), the app it ran in, its status and times. While an agent waits for you, the phone shows its question or approval request, including the command or file it is about, and your answer goes to the app on your computer. This list is kept in memory only and is cleared when our servers restart.
• Notifications: if you allow notifications, your phone receives a push token from Google Firebase Cloud Messaging, which we store with your device record. We use it to tell you when an agent needs your approval or a long run finishes. Notifications contain the agent's name and the folder name, never your code or prompts. Google receives the token and the notification text to deliver it. You can turn notifications off in your phone's settings at any time. Signing out on the phone or deleting your account removes the token from our servers.
• Reports: if you report an answer in a Jennefer Mobile chat (long press on the answer, then Report), we receive the text of that answer, the reason you picked, and your account ID, so we can review it. Your other messages are not sent.
• The app has no ads, no analytics, and no crash-reporting tools.

Server error reports. When something fails on our servers, we send an error report to Sentry so we can find and fix the problem. A report contains the type of error and a shortened error message, where in our code it happened, the request method and path, the user agent of your browser or app, and details about our server. Before a report leaves our servers, we remove request bodies, cookies, query strings, IP addresses, account details, email addresses, and keys. The Jennefer apps on your computer do not send error reports.

Cloud features. If you use Jennefer Cloud, the prompts, code, and files you submit are processed on our infrastructure and in cloud sandboxes run by E2B. If you connect your own API key or a custom endpoint (OpenAI-compatible, Anthropic, or Amazon Bedrock), the App sends requests directly to that provider under its own terms, and we do not receive your key, unless you choose to keep that endpoint in your account as described under Jennefer Mobile above.

Workshop gallery.

• Publishing: on Workshop Pro, All Apps Pro, and Team plans you can publish a Workshop app. When you do, the Workshop sends us the built app (the files that run in the app window and the app's manifest), the app's source code, its icon, and the details you enter: the app's name, description, category, the author name you choose to show, the version, and what is new in it. We store them in our file storage at Microsoft Azure. Every Jennefer user can see the app's listing and open the built app. The source code is seen only by the Jennefer team members who review apps. We use it to check that the app follows the gallery rules, and we do not give it to other users. We record review decisions and notes, and show them to you.
• Opening a gallery app: when you open a published app, we record that your account opened it, so that each person is counted once in the app's number of opens. The app's author sees only that number. The Workshop downloads the built app to your computer, where it runs in an isolated window that cannot reach the internet. If you allow it to use your AI model, its requests go to the model you picked in Jennefer Hub, like your own Workshop apps. Data the app saves stays on your computer. From time to time the Workshop asks our servers whether your gallery apps have updates or were removed; that request contains the IDs of the gallery apps on your computer.
• Reports: if you report a gallery app, we receive the app's ID, name, and version, the reason you picked, your note, and your account ID.

3. How we use information

• To provide the App and Jennefer Cloud, including running agent tasks you start.
• To create and secure your account, manage plans, credits, and billing, and run teams.
• To manage the waitlist, review requests, and invite you to early access.
• To respond to messages and provide support.
• To understand how the Site is used and improve it.
• To send product updates you asked for. You can unsubscribe at any time.
• To run the Workshop gallery: review published apps, show them to other users, deliver updates, and act on reports.
• To keep our services secure, prevent abuse, and comply with law.

We do not use your prompts, code, files, waitlist descriptions, or support messages to train AI models.

4. Legal bases (EEA, UK, and Switzerland)

We rely on the performance of our contract with you to provide your account, the App, and paid services; on your consent for the waitlist, marketing emails, analytics cookies, and app usage statistics; on our legitimate interests for security, finding and fixing errors, basic Site operation, and responding to inquiries; and on legal obligations, for example tax records. You can withdraw consent at any time without affecting earlier processing.

5. How we share information

We share personal information only with service providers who process it for us under contract:

Other Jennefer users see what you publish to the Workshop gallery: the app's listing (its name, description, category, icon, version notes, the author name you chose, and its number of opens) and the built app. They do not see your email address or your source code.

We may also disclose information if required by law, to protect rights and safety, or as part of a merger, acquisition, or sale of assets, in which case this Policy will continue to apply. We do not sell personal information or share it for cross-context behavioral advertising.

6. International transfers

We are based in the United States, and members of our team work from Türkiye. Our providers may process data in the United States and other countries. For transfers from the EEA, UK, or Switzerland, we rely on the European Commission's Standard Contractual Clauses (and the UK Addendum) or the provider's certification under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions.

7. Retention

• Waitlist information: until early access opens for you, and for up to 24 months after our last contact, unless you ask us to delete it sooner.
• Account information: while your account is open, and up to 30 days after you close it.
• Billing records: as long as tax and accounting law requires.
• Support conversations: up to 24 months.
• Server error reports: up to 90 days.
• Analytics data: up to 12 months.
• Agent task content: only while the task runs.
• Run list shown in Jennefer Mobile: up to 24 hours, in memory.
• App builds from the phone (the request, the agent's steps, and its summary): up to 24 hours after the build ends, in memory, for at most your last 10 builds.
• Phone device records and push tokens: until you sign out on that phone, the token stops working, or you delete your account.
• Endpoints kept in your account, including the encrypted API key: until you turn off "Use from your phone without this computer," remove the model in Jennefer Hub, or delete your account.
• Messages from Jennefer Mobile chats, including chats with an endpoint kept in your account, and attached files: not stored on our servers. PDFs are read in memory and not kept. Chats stay on your phone until you delete them or the app.
• Reported answers: up to 12 months after we review them, or until you delete your account.
• Apps you publish to the Workshop gallery (listing, built app, source code, and icon): while the app is in the gallery, including when you hide it. When you delete it from the gallery or delete your account, we delete them within 30 days. Files of versions that were not approved or that you withdrew: up to 90 days.
• Which accounts opened a gallery app: until the app or your account is deleted.
• Reports about gallery apps: as for other reports, up to 12 months after we review them.

8. Your rights

Depending on where you live, you may have the right to access, correct, delete, or receive a copy of your personal information; to object to or restrict processing; and to withdraw consent. Residents of California and other U.S. states with privacy laws may also have the right to know what we collect, to opt out of sale, sharing, or targeted advertising (we do none of these), and not to be discriminated against for exercising their rights.

To make a request, email privacy@jennefer.dev. We will respond within 30 days, or sooner if your local law requires. We may need to verify your identity. You may use an authorized agent where the law allows. If you are in the EEA or UK, you can also complain to your local data protection authority.

We honor Global Privacy Control signals as an opt-out request for the browser that sends them.

9. Cookies and similar technologies

You can change your analytics choice at any time with the "Analytics" link in the footer.

10. Security

We use reasonable technical and organizational measures, including encryption in transit, encryption of the endpoint keys you keep in your account, and access controls. No method of transmission or storage is completely secure.

11. Children

Our services are not directed to children. You must be at least 16 to join the waitlist or create an account. We do not knowingly collect information from children under 16, and we will delete it if we learn we have.

12. Changes

We will post updates here and change the "Last updated" date. If a change is material, we will notify waitlist members and account holders by email before it takes effect.

13. Contact

Ahmet Enes LLC, 8 The Green, Ste 21427, Dover, DE 19901, USA · privacy@jennefer.dev