Privacy Policy

1. Who we are

nenva is developed and maintained by Anjadhe LLC. You can reach us at support@anjadhe.ai.

2. Information we access

When you choose to connect a Google account, nenva requests the following OAuth scopes:

• gmail.modify, to read your email, and to mark messages as read or archived on your behalf when you act on them inside the app.
• calendar.events, to show your events alongside your tasks and, when you explicitly create or edit an event from the app, to write that change back to your calendar.
• calendar.calendarlist.readonly, to list which calendars the account has, so you can choose which ones to show.
• userinfo.email, to identify which Google account is connected and display it in the settings screen. This one is requested when you connect Calendar, or Gmail and Calendar together.

nenva also stores the content you create inside the app: notes, journal entries, goals, bookmarks, tasks, and similar personal productivity data.

3. How your information is used

Information accessed through Google APIs is used solely to provide the features you turn on inside the app:

• Displaying your emails and calendar events in the nenva interface.
• Running AI analysis over incoming email to extract action items, deadlines, and summaries. This runs on the AI model set in the app: nenva Cloud on a new install, or a model you choose instead. Section 5 covers each option.
• Writing changes back to Gmail and Google Calendar when you explicitly take an action in the app (archive, mark read, create or edit an event).

nenva does not use your Google user data for advertising, targeting, profiling, or training any AI model. It is not sold, rented, or transferred to third parties, except as strictly necessary to deliver a feature you explicitly invoke (see AI processing below).

4. Where your data is stored

nenva has no server of its own. All data lives on your machine:

• App data is saved to a folder on your Mac, inside the standard macOS Application Support area (a folder named Anjadhe).
• Google OAuth tokens are stored locally and are used only to talk directly to Google APIs from your Mac.
• If you enable multi-device sync, nenva writes encrypted change files to your own iCloud Drive so your other Macs can pick them up. Files are encrypted with AES-256-GCM using a key kept on your machine. Nothing in that sync stream is sent to us, and we cannot read it.
• Gmail message contents are not written into the sync stream; each machine fetches email directly from Google.

5. AI processing

nenva’s AI runs on open-weight models. A new install uses nenva Cloud, described below. You can instead run a model locally on your Mac through the built-in llama.cpp engine; with a local model, your email content and everything else the assistant sees do not leave your machine.

Besides a local model, there are three options. You can switch between them at any time in Settings › AI Assistant:

• Your own OpenAI-compatible server, an endpoint you host and control. Requests go directly from your Mac to your server; they are not routed through nenva.
• An OpenAI or Anthropic model with your own API key. Requests go directly from your Mac to that provider; they are not routed through nenva, and what you send is governed by your own agreement with that provider.
• nenva Cloud, the default for new installs: an open-weight model we host at api.anjadhe.com. This is the one AI option where your content passes through a server we operate, so here is exactly what that server does: it forwards your request to the inference provider running the model under zero-data-retention terms, counts requests and tokens against your install’s free monthly allowance, and does not log or store the text of your prompts or the model’s responses. No account is required; the app uses the same per-install key as its built-in search, and nothing it handles is read by us or used to train any model.

Selecting any of these models applies to every AI feature, not only chat, so while AI email features are on it also sends the sender, subject and body of incoming messages for the app to summarise. A new install uses nenva Cloud; any other model is used only when you add it, and nenva never falls back from the model you chose to a different one. nenva does not send your data to any AI service other than the one set in the app, and nothing you provide is used by nenva to train any model.

6. Sharing and third parties

We do not sell your data. Not to anyone, for any price, under any circumstances. We also do not rent, trade or license it, do not pass it to data brokers, advertisers or analytics companies, do not use it to build a profile of you or to target advertising anywhere, and do not read it ourselves. No business model here depends on your information: nenva is paid for by the people who buy it. The one server of ours your content can pass through is nenva Cloud, the AI model a new install starts with, and section 5 states exactly what it does and does not keep.

What follows is every service the app can send anything to, and the reason. Sending happens for one reason only, which is to do the thing you asked the app to do.

Three can receive data obtained through Google APIs, and only as described:

• Google, to fulfil your own requests against Gmail and Calendar.
• The AI model set in the app, when it is not running on your Mac, as described in section 5: nenva Cloud on a new install, or your own server or a provider you added a key for. A model running on your Mac sends nothing anywhere.
• Apple iCloud Drive, if you turn on sync, as encrypted files in your own account. Message contents are not written into the sync stream; tasks and reminders created from your mail are.

The app also contacts these, none of which are ever sent anything from your mail or calendar:

• Search providers receive the words you searched for, so the app can search the web. That is api.anjadhe.com by default, which counts how many searches an install has run and does not store the words themselves, or Tavily or Brave if you choose one and add your own key.
• Yahoo Finance receives ticker symbols and nothing else, so the app can price the holdings you entered. No account, position or transaction is sent.
• Our analytics endpoint receives event names from a short published list plus a random install number, so we can count which features get used. It is off unless you switch it on and can never carry the contents of anything.
• Our feedback endpoint receives what you wrote, an email address if you give one, and the diagnostics shown to you on screen first, so we can answer you. Nothing is sent until you press Send.
• GitHub and Hugging Face receive nothing about you or your data. The app downloads updates, its configuration file, and the local AI engine and models you choose to install.
• Google News receives the topics you follow, so the News app can fetch headlines.

Finally, some features exist to reach the wider internet and send wherever you point them: the built-in browser loads the sites you visit, the assistant reads pages and runs searches you ask it to, and any tool servers you connect do what you added them to do. None of these are contacted on their own.

One honest note about that last group. If you ask the assistant to search the web about something in an email, the search it writes can contain text from that email, and that text goes to the search provider. You are directing it rather than the app deciding on its own, but it is the one route by which the contents of your mail can reach a service listed above.

7. Limited Use compliance

nenva’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except to provide or improve user-facing features that are prominent in the app’s UI, do not use it for advertising, do not allow humans to read it, and do not use it for any other purpose.

8. Analytics and telemetry

nenva does not collect product analytics by default. The app contains an optional, opt-in usage-analytics feature that the user can enable from Settings. When enabled, it records only anonymous event counts (for example, “email view opened” or “assistant response marked helpful”) tagged with a randomly generated install ID.

Analytics do not include the contents of your notes, journal, goals, emails, calendar events, or AI prompts and responses. Settings provides an inspector that shows exactly what would be sent before anything is transmitted, and a one-click toggle to disable and clear any pending data.

Google user data is not included in analytics, consistent with the Google API Services User Data Policy.

9. Retention and deletion

Because all data is stored locally, deleting it is under your control:

• Disconnect a Google account from Settings → Accounts. nenva removes the stored OAuth tokens immediately.
• Revoke nenva’s access at any time from your Google Account at myaccount.google.com/permissions.
• Uninstall the app and delete the local ~/Library/Application Support/anjadhe-app directory to remove all app data.
• If you use sync, delete the ~/.anjadhe_sync directory in iCloud Drive to remove the sync journal.

10. Security

Google OAuth tokens and sync journal files are encrypted at rest. Data in transit to Google, iCloud, and any AI server you configure is sent over TLS. No security system is perfect; if you suspect a vulnerability, please contact us at the address below.

11. Changes to this policy

If this policy changes in a material way we will update the effective date at the top of this page and, where appropriate, surface a notice inside the app the next time you open it.

12. Contact

Questions or requests related to this policy can be sent to support@anjadhe.ai.