Privacy

Last updated: 24 October 2026

Noodle is a free family of apps for running AI agents on your Mac, iPhone and iPad, made by the Noodle project. Noodle's source code is publicly available under the Apache 2.0 licence: https://github.com/pdparchitect/noodle

The short version

• Running agents does not send your conversations, files, Google data or sign-ins to Noodle's developers. Apart from the technical data listed below, they only see what you choose to send them, such as TestFlight feedback or an email.
• There are no Noodle accounts and no ads. Noodle's own code does not send analytics or crash reports. Noodle Mobile is a beta on Apple's TestFlight, and Apple shares some data with the developers while you test it (see below).
• Your agents send what they work on to the AI provider you chose. That provider's terms and your account settings decide how it is used.
• A few services the developers use see limited technical data, such as IP addresses. They are listed below.

What Noodle keeps, and where

On your Mac. Noodle stores your conversations, agent workspaces and settings on your Mac.

On a Hub. Noodle Hub runs agents for a group, such as a family or a team. A Hub keeps its conversations, agent files, memory and tool sign-ins on the Mac that runs it. If you join someone else's Hub, that data is on their Mac, not yours.

On your iPhone and iPad. Noodle Mobile connects to Hubs. It keeps your Hub pairings, widget data and some cached content on your device.

In your iCloud. Spaces you create, with their names, members and pins, sync between your Mac and iPhone through your own private iCloud, encrypted. Noodle's developers cannot read them.

Sign-ins. Sign-ins for tools you connect, such as Google, are kept in the macOS Keychain of the Mac or Hub that uses them. They are not synced to iCloud and are never written to an agent's files. Each restricted agent gets its own copy of your AI provider sign-in in its workspace, so it can work.

Voice. Voice messages are transcribed on your device, on your Mac or iPhone. The agent then receives the audio and the transcript. Voice calls are different: your voice is sent to OpenAI through the agent's sign-in.

What your agents can reach

A new agent is restricted. It can use its own workspace, the folders you share with it, its conversations, and the tools, computers and browsers you assign to it. It cannot read your other files, other agents' files, Noodle's own storage or your Keychain, though it may see that some files exist. It can reach the internet. These file restrictions apply to the agent itself; assigned tools, computers and browsers can act with their own permissions.

A Local Mac computer is a separate macOS user account on your Mac. It can reach what macOS lets that account reach. It is not a virtual machine.

If you make an agent unrestricted, it runs as you and can reach your files and signed-in services.

Within the access you give, agents use their tools without asking you each time.

Your AI provider

Noodle does not sell a model. Each agent uses an account you already have, such as Claude, ChatGPT or Gemini, or a model that runs on your Mac.

Everything an agent works on is sent to that provider: your prompts, the files it reads, and what its tools return. That includes Google data, if the agent uses a Google connection.

If an agent switches provider. Harness fallback is off unless you turn it on in Settings › Harnesses and choose a list. It applies to agents on your Mac. Agents on a Noodle Hub don't switch. With fallback on, an agent that runs out of usage continues with the next provider in your list, and can switch back once the original harness has usage again. The next provider receives what the agent works with: its instructions, its workspace and memory files, new messages, and the conversation history it can read. If the next harness uses a model running on your Mac, that work is not sent to a cloud AI provider.

Whether the provider trains AI models on this depends on your account type and settings. Many consumer accounts may use your conversations for training unless you turn it off, and some do not let you turn it off. API and business accounts usually do not by default. Models that run on your Mac send nothing. Noodle cannot control this, so check your provider's settings.

Google user data

Noodle can connect to Gmail, Google Calendar, Google Docs and Google Drive. You choose whether to connect each one, from the Noodle Mac app. Each connection asks only for its own permissions:

• Gmail (gmail.modify): search and read email, create and list drafts, and add or remove labels. Noodle's Gmail connection offers no send or delete action today.
• Google Calendar (calendar.calendarlist.readonly, calendar.events): see your calendars and events, suggest times, create, change and delete events, and respond to invitations.
• Google Docs (documents): read and edit your documents.
• Google Drive (drive.readonly, drive.file): search, read and download any file in your Drive, and create and copy files. It offers no delete action.

These actions come from Google's own connection servers. Noodle passes them on to the agents you assign.

How it is used. Noodle uses Google data only to provide the features you turn on: the agents you assign a connection to use it for the tasks you give them, including recurring ones. Noodle's developers do not use it for advertising, do not sell it, and do not use it to train AI models.

Where it goes. Google data goes from Google to the Noodle app on your Mac, or to your Hub. From there it goes to the agent that asked for it, and to that agent's AI provider (see above). It does not reach any server run by Noodle's developers.

How long it is kept. Noodle has no separate Google-data cache. Content an agent has used stays where the agent put it, such as in conversations, its workspace, files it saved or the agent tool's session files, until you delete it.

How to remove it. Removing a connection, revoking access, and deleting copies are three separate steps.

• Remove the connection. In Noodle, go to Settings › Tools, select the connection and choose Remove Connection. Agents lose access at once, and the stored sign-in is deleted from the Keychain.
• Revoke access at Google. Removing a connection does not cancel Noodle's access on Google's side. To do that, open your Google Account's list of apps with access (https://myaccount.google.com/connections), choose Noodle, then select Remove all access. This ends access for all of that Google account's Noodle Google connections.
• Delete copies. Neither step deletes Google data an agent already used. It can still be in conversations, agent workspaces, agent tool session files, a Hub or your backups. Delete those to remove it. Copies sent to your AI provider follow that provider's deletion rules.

Limited Use. Noodle's use of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

Services the developers use

Noodle has no servers that can read your content. Noodle Push, below, carries call alerts it cannot read. These services the developers use see some technical data:

• Noodle Push (push.usenoodle.app) rings your iPhone when an agent calls, even when Noodle Mobile is closed. The developers run it on Cloudflare. Noodle Push itself writes nothing to disk.
• Signing up. Your iPhone sends Push its Apple call token, a public key and a signature. Push sends back a sealed copy of the token that only Push can open, and keeps nothing. Your Hub or Mac keeps the sealed token, your iPhone's signed permission to ring it, and a key from your iPhone used to encrypt who is calling.
• A call. Your Hub sends Push the sealed token, that permission, a call ID and who is calling. Who is calling is encrypted so that only your iPhone can read it. Push and Apple cannot.
• To Apple. Push passes Apple's push service the call token, the call ID, when the ringing stops, a code that identifies your Hub and the encrypted caller. Nothing else.
• In memory. To limit abuse, Push counts requests by IP address (for IPv6, by network), by Hub and by iPhone. It also remembers call IDs for five minutes. These are held in memory only and are lost when the service restarts.
• Logs. Push's own logs contain no IP addresses, tokens or call contents. Cloudflare keeps request logs for up to seven days. They may include IP addresses and approximate location.

• GitHub hosts this website, the app downloads and the update feed. It sees the IP address and browser or app information of each request, such as website visits, downloads and daily update checks, under GitHub's privacy statement.
• Apple iCloud (CloudKit) delivers new-message notifications to Noodle Mobile. It holds a random device code, a conversation ID and an unread count. It holds no message content.
• Cloudflare provides DNS for usenoodle.app and carries website visits, so it sees visitors' IP addresses and browser information.
• Apple TestFlight. Noodle Mobile is a beta on TestFlight. While you test it, Apple collects crash logs and usage information and shares them with Noodle's developers; this cannot be turned off. Feedback you send through TestFlight also reaches them. If you joined through the public link, they do not see your name or email address. On the Mac, Apple's settings control whether you share diagnostics with Apple.

When you ask, Noodle downloads agent tools and models from their publishers. It also checks those publishers regularly for new versions of the agent tools it installed, and installs them automatically unless you turn this off in Settings. The publishers see these requests.

Changes

If this policy changes, we will update this page and the date at the top. Earlier versions stay in the public history of the website's code.

Contact

Questions about privacy: [email protected]