Privacy policy

Last updated 29 October 2026

This policy explains what information the Nawa desktop app for Windows and the website nawaagent.com collect, where that information goes, and the choices you have. Nawa is made by Mohamed Qasem (“we”, “us”).

The Nawa app

What stays on your computer

Nawa keeps your chats, projects, memory, settings, the keys you enter for model providers and other services, and the sign-ins of accounts you connect in your Nawa profile, in %APPDATA%\Nawa on your computer. Keys and sign-ins are stored encrypted. You don’t need a Nawa account to use Nawa, and we can’t see what is in your profile.

With Use memory enabled, Nawa can save lasting preferences and facts you tell it automatically. A card under the answer offers Undo; you can also edit or delete saved memories in Settings → Memory. Turning memory off stops reading and saving account memories but does not delete existing notes or their earlier appearances in chats.

Separately, Nawa keeps workspace requirements and verified notes in the workspace's AGENTS.md file. Project chats share that project's file, which may be outside the Nawa profile and may be included in your own backups or version control. These notes are supplied to the model for work in that workspace. Read, edit or delete them in the file; deleting a chat or turning account memory off does not remove a project's notes.

Services you choose

Nawa works by sending your requests to services that you choose and set up yourself. Each one receives what Nawa sends it and handles it under its own terms and privacy policy:

• AI model providers, such as Anthropic, OpenAI, OpenRouter, Google Gemini, xAI or Groq, or a model server you run yourself. Each request carries your message and what the model needs to answer it: earlier messages in the chat, your memory if memory is on, and the text of files, web pages, emails or calendar events that Nawa read for that chat.
• Web search providers receive your searches. Automatic search uses a configured API or, when none is configured, Web search (DDGS), which sends queries to external search engines in the background without an API key. You can instead configure Brave, Tavily, Exa, SerpApi or your own SearXNG server.
• Websites that Nawa opens for you receive the same requests any browser sends.
• Connectors and MCP servers you add, such as Slack, GitHub or Notion, receive what Nawa sends to their tools.

We don’t run or control these services. Before you connect one, check its terms, including whether it keeps your data or uses it to train its models.

Gmail and Google Calendar

Gmail and Google Calendar are two separate connections, each with its own Google sign-in. You can connect one without the other. Nawa reads nothing from your Google account until you press Connect in Nawa and approve access on Google’s own sign-in page.

What Nawa can see

• Gmail, read only (Google’s gmail.readonly permission). Nawa can search your email and read a message’s subject, sender, recipients, date and text. It does not download attachments. It cannot send, delete, move, label or change email.
• Google Calendar, read only (Google’s calendar.events.owned.readonly permission, which Google’s sign-in page calls “See the events on Google calendars you own”). Nawa lists only the events on your main calendar, with their title, time, place, description and attendees’ email addresses. It cannot create, change or delete events.
• Your Google account’s email address and name, so Nawa can show which account is connected.

How Nawa uses it

Nawa reads your email or calendar only to carry out something you asked for: a request in a chat where that service is switched on, or an automation you set up and approved. Each email and calendar tool has a permission in Settings → Connectors: Ask first, Always allow or Off. What Nawa reads is shown in the chat or the automation’s result, and when a model works on your request, it is sent to the AI model provider you chose so that the model can answer you.

Where it is kept

• Your Google sign-in is stored encrypted in your Nawa profile on your computer.
• Email and calendar text that Nawa read becomes part of that chat, which is stored on your computer. Deleting the chat deletes it. If memory is on, notes Nawa saves from a chat are kept on your computer too, and you can delete them in Settings → Memory.
• Nawa has no server that receives your Google data. We never receive your Google sign-in, and we receive Google data only if it is part of a bug report you choose to send (see Bug reports).

Sharing

Nawa shares Google data only with the AI model provider you chose, to answer your request, and with us only in a bug report you send. We don’t sell Google data, use it for advertising, or use it to develop, improve or train AI models.

Nawa’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How to disconnect

• In Nawa: open Settings → Connectors and press Disconnect beside Gmail or Google Calendar. This deletes that sign-in from your computer and asks Google to withdraw Nawa’s access. If you connected both with the same Google account, they share one Google sign-in, so Google withdraws Nawa’s access once you have disconnected both. Nawa tells you what Google answered.
• At Google: open your Google Account, go to Third-party apps & services, choose Nawa, and remove its access. This works at any time, even without Nawa.
• To remove email or calendar text that Nawa already read, delete the chats it appears in.

What Nawa sends to us

Nawa sends information to us, or to the servers we use, only in the cases below.

Usage statistics (optional)

Help improve Nawa, in Settings → Privacy, is off unless you turn it on. Existing installations keep their choice. When it is on, and you are using Nawa (its window is in front and you have used the keyboard or mouse in the last five minutes), Nawa sends nawaagent.com at most one message every five minutes. The message holds only Nawa’s version number, today’s date and a random ID that changes every day. It contains no chats, prompts, files, accounts, Google data or settings.

We use these messages to count how many copies of Nawa are in use each day and right now, and which versions they run. Our server keeps a scrambled copy (a hash) of each daily ID for that day only and deletes it within 48 hours; after that only daily totals remain. Our server software does not store your IP address, although our hosting provider receives it with every connection, as for any website. Turning the setting off stops the messages.

Bug reports

Nawa sends a bug report only when you send one with the Report a bug button. A report contains:

• Your description of the problem, and your email address if you enter one.
• Diagnostic records: Nawa’s own logs (startup, updates and errors), facts about the app and your computer (such as the Nawa and Windows versions, processor and memory), and Nawa’s settings with keys and passwords removed. Model connection diagnostics include the provider, server address, model, whether a key is saved, its length and public format prefix, and whitespace or non-ASCII flags. They do not include the key’s secret characters or your setup names.
• If you send it from a chat: that chat’s entries in Nawa’s logs (the tools it used, errors, timings and short tool inputs) and its stored records, including builds and automation runs with their results. With Include recent messages from this chat on (it starts on), the report also holds the chat’s last 8 messages and its recent tool results. These can include email or calendar text that Nawa read in that chat. Turning the switch off leaves out the messages and tool results, but not the short tool inputs (such as an email search) or automation results. To keep your email and calendar out of a report entirely, send it from a chat that did not use them.

A report never includes your other chats, images, attachments, workspace files or Nawa’s chat database. Passwords and keys are removed, and your Windows user folder name is replaced. Our website also records when the report arrived, the IP address it came from, and the app identification (user agent) it was sent with.

We use a bug report only to find and fix the problem it describes, and to reply to you if you gave an email address. We keep reports until we delete them. To have a report deleted, email us at nawa@nawaagent.com with the reference Nawa showed when you sent it.

Reports about AI content

In the report dialog, turn on Report inappropriate AI content to send a content concern. We receive only the description and content you enter, your email if provided, Nawa's version, and the report reference and time. This mode does not attach chats, logs, settings, files or device diagnostics. Our website receives your IP address and app identification with the request. We use these reports to review the concern, take appropriate action, and reply if you supplied an email. The retention and deletion contact above apply to content reports too.

Updates

The website edition of Nawa checks for updates every six hours and downloads them from our update server, which is hosted by Cloudflare. Each check carries a random ID that Nawa’s update component creates once on your computer, for releasing updates in stages. The ID is not linked to you, your accounts or your usage statistics. Cloudflare sees the IP address and this ID with each request, as part of serving the download. We don’t receive or keep either: from Cloudflare we get only total download counts.

The Microsoft Store edition does not use the website update feed. Updates require a newer Store-edition installer. It disables Tailscale remote access and remote device pairing and listens only on the local computer.

The website

Public beta and release updates

Public downloads do not require your email or a Nawa account. If you enter your email and press Subscribe or Download for Windows, we subscribe you to release updates and store your email address, signup time and an unsubscribe token separately from the historical waiting list. We use that subscription only for Nawa release updates. Unsubscribe through the link in an update, or email nawa@nawaagent.com to have it removed. Existing waitlist contacts are not automatically subscribed.

Our hosting and download providers process network requests to serve the installer. We do not add public downloads to personal invitation records. Aggregate download-request statistics do not identify a completed installation.

When you press a website Download button, we set a random first-party cookie named nawa_download_browser for up to one year to estimate unique download starts. It is sent only to our download pages. We keep a hash of this identifier, the UTC day and the number of starts for 365 days, separately from emails, accounts and invitation records. We do not add IP addresses or browser descriptions to these measurements. Admin reports and exports contain only aggregate counts; application backups exclude this measurement database. The hosting provider’s own backups follow its separate policy. Clearing or blocking the cookie does not prevent downloads but can cause repeated starts to count as different browsers. These measurements do not establish completed downloads or installations.

Historical waiting list and personal invitations

If you joined the waiting list, we retain what you entered: your email address, your name if you give it, your profession, what you use agentic AI for, and anything you add. We use it only to review your request and to email you about Nawa. If we approve you, you get a personal download link, and each download through it is recorded with its time, IP address, browser and Nawa version. We keep your application until we delete it, and deleting it also deletes its download record. To be removed, email us at nawa@nawaagent.com.

Visiting the site

Apart from the download-measurement cookie described above, the site sets no cookies for public visitors and loads no advertising or tracking scripts. Its fonts, images and video thumbnails come from nawaagent.com. The home page remembers whether you chose to play or stop its animation, in your own browser’s storage. Like any website, our hosting provider may keep standard server logs, such as IP addresses, the pages requested and browser types, under its own policy. We use the host’s aggregate HTTPS traffic reports to measure monthly visits and estimated unique visitors. The admin dashboard receives monthly counts and report timestamps, not visitor IP addresses or browsing histories.

Demo videos are hosted on YouTube. Its player loads only when you click a video thumbnail, using YouTube's privacy-enhanced mode. Playing a video connects your browser to Google/YouTube, which receives network and playback information and may use browser storage under its own privacy policy. Closing the player stops the video and removes the embed.

Your choices and rights

• Most of your information never leaves your computer, and you control it there: delete chats and memory notes in Nawa, or uninstall Nawa and delete the %APPDATA%\Nawa folder to remove everything.
• For what we hold, which is your waiting-list application and any bug reports you sent, you can ask us to show, correct or delete it by emailing nawa@nawaagent.com.
• Depending on where you live, you may have further rights under your local law, and you can contact your data protection authority.

Security

Nawa connects to Google and to nawaagent.com over encrypted HTTPS connections. Keys and sign-ins on your computer are stored encrypted. Waiting-list data and bug reports on our server are kept outside the public website and are open only to us.

Children

Nawa is not meant for children under 13, and we don’t knowingly collect information from them.

Changes to this policy

If we change this policy, we will update this page and its date. Before Nawa uses Google data in a new way or for a new purpose, it will ask for your consent in the app.

Contact

Questions about privacy: email Mohamed Qasem at nawa@nawaagent.com.