Last updated October 12, 2026

This policy covers Waku Memory: waku.one, the console, the API and MCP server at api.waku.one, and the Waku plugins that connect coding agents to it. It is run by AutoManus Technologies, Inc. ("AutoManus", "we"). The open-source Waku agent, which runs on your own computer, has its own section at the end.

1. What we collect

• Your account. When you sign in with GitHub or Google, we receive your email address and the basic profile they share, such as your name and picture. We do not ask either provider for anything else. When you sign up with an email address and a password instead, we receive the address, and Supabase stores the password only as a one-way hash, which no one at AutoManus can read.
• Memories you store. What you save through the console, the API, the MCP tools or an import.
• Captured sessions, if you turn capture on. What you type, what your agent replies, and the names of the tools it used. Your files, the commands the agent runs and its reasoning are not sent, unless they appear in a reply. Turning capture on for Claude Code can also import up to 180 days of your past Claude Code sessions, its memory files and your user-level CLAUDE.md. Once installed, the Codex plugin sends every turn.
• Voice recordings, if you record with Waku. The audio you record with the Waku app on your watch or phone, and the text it is turned into.
• Billing. Your plan, its status, the number of seats, billing dates, and the IDs Stripe gives your customer record and subscription. Card details go straight to Stripe; we never see them.
• Technical records. Server logs record request IDs, not the content of your memories, and are kept for 30 days. The waitlist form uses your IP address briefly to limit abuse, and does not store it.
• Match records. We keep the text of each search. We also keep the first 2,000 characters of each prompt a Waku plugin sends, including short replies that Waku does not search with. We keep both beside the record of which memories each search found, for 30 days. Only you can read them, on the Matches page.
• The waitlist. Your email address, if you join it.

waku.one runs no analytics and no advertising trackers.

2. Cookies and local storage

Sign-in cookies keep you signed in, and a small cookie tells the site whether you are. Your browser also remembers your theme and a cached GitHub star count; to get that count, your browser asks GitHub's public API directly.

3. How we use it

Only to run Waku Memory: to store, search and return your memories, to turn imports and captured sessions into memories, to share what you choose with your spaces, to bill you, and to keep the service secure. We do not sell your data, we do not use it for advertising, and we do not use it to train AI models.

4. Who else processes it

• Anthropic reads imports and captured sessions to pull memories out of them, and reads each new memory beside your similar earlier ones to decide whether it replaces or repeats one of them, and reads the memories of a project when you ask for a view of it, under its commercial API terms.
• Voyage AI reads each memory we keep, and each search you type, to build the index that finds memories by meaning. With a Waku plugin installed, it also reads the first 2,000 characters of each prompt you give your agent, whether or not capture is on, so the memories that bear on it can be shown beside it. It does not read a short reply such as “yes”, and it does not read a command. We keep the first 2,000 characters of that prompt in its match record for 30 days.
• OpenAI turns your voice recordings into text, under its API terms. It receives the audio only, not your memories or your account.
• Supabase handles sign-in and hosts the database.
• Amazon Web Services runs the API, the background workers and the server logs.
• Vercel hosts this website and the console.
• Stripe processes payments.
• GitHub, Google and Apple confirm who you are when you sign in.

Your data is stored in the United States.

5. Spaces

Your memories are private until you propose one to a space. Accepted memories are visible to every member of that space, and proposals waiting for review are visible to its owners and admins. What you wrote before proposing stays private.

6. Keeping and deleting

• Forgetting a memory removes it from search, recall and your spaces. The record itself stays in our database, marked as deleted, as part of that memory's history, and you can still see it yourself.
• Captured session text is removed once it has been turned into memories. If that step fails, the text is kept so it can be retried.
• Voice recordings. We delete the audio as soon as it has been turned into text, and within one day if that never happens. We delete the text when you save or discard what Waku found in it, or after 7 days if you do neither. Deleting a recording deletes both at once.
• Deleting your account. In the phone app, open Settings and tap Delete account. On the web, sign in and open Settings, then Account, or read how to delete your account. We cancel your subscription, then delete your memories (including forgotten ones), your API keys, your reports and your sign-in. It cannot be undone. If you cannot sign in, write to us from the email address on your account and we will delete the account within 30 days.
• A copy of your data. There is no export button yet either. Write to us and we will send you one.
• Cancelling Pro deletes nothing.

7. Your rights

Wherever you live, you can ask to see, correct, export or delete the personal data we hold about you, or object to how we use it. Write to us and we will answer within 30 days.

8. Security

Traffic is encrypted, and the database only lets each account read its own memories and those of the spaces it belongs to. Waku Memory is still an alpha, so keep your own copy of anything you cannot afford to lose.

9. Children

Waku Memory is not meant for anyone under 13, and we do not knowingly collect their data. The Waku phone app is for people 18 or older, and we do not knowingly collect data through it from anyone younger.

10. The Waku agent

The open-source Waku agent runs on your own computer and keeps its data in a .waku folder there. It sends no telemetry to AutoManus. To answer you, it sends your conversation to the AI model provider you chose, using your own API key, and to any messaging service you connect, such as Telegram.

Google Calendar. If you connect Google Calendar, the agent asks Google for read-only access to your calendar events. The sign-in token stays on your computer. The agent reads events only to answer your requests, passes them to the model provider you chose, and never sends them to AutoManus. Waku's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

If you connect the agent to Waku Memory, the memories it saves go to waku.one, and the rest of this policy applies to them.

11. The Waku phone app

The phone app, on iOS and Android, uses the same Waku service as the website. It shows your memories and lets you chat with the Waku agent hosted at agent.waku.one.

• Kept on your phone. Your sign-in session, in the phone's secure storage (the iOS Keychain or the Android Keystore), and a note that you agreed to how Waku uses AI models.
• Sent from your phone. Your sign-in token, the messages you type and your memory searches, to api.waku.one and agent.waku.one over an encrypted connection. The hosted agent answers with AI models, so your message and the memories it finds go to the model providers in section 4.
• Not collected. The app has no advertising and no analytics. It does not read your contacts, location, photos or microphone.
• Signing in. You can sign in with Apple, GitHub, Google or an email address and password. With Sign in with Apple you can hide your email address, and we then see only Apple's relay address.
• Reporting a reply. Under any reply from the Waku agent you can tap Report this reply and choose a reason. We keep the reply text, your reason and your note so we can review the report, and we delete them with your account.

12. Changes

When we change this policy we will update the date above. If a change materially affects you, we will tell you by email or in the console before it takes effect.

13. Contact

AutoManus Technologies, Inc. · hello@automanus.io