Privacy
How Quokka Bot handles data: on this website, in the Mac and iPhone apps, and on a Quokka Bot server.
Last updated 19 October 2026
The short version
- Quokka Bot runs on a server its owner controls. Tasks, chats, files and saved logins are stored on that server. We do not receive them.
- The Mac and iPhone apps connect only to the server you sign in to. They contain no analytics, advertising or tracking.
- The agent's work goes to Anthropic, the maker of Claude, under the Claude plan the server's owner signs in with.
- Saved passwords and 2FA secrets are encrypted on the server. Quokka Bot types them into pages; the AI model never sees them.
- This website sets no cookies and runs no analytics or scripts.
- We receive personal data when you write to us, and on servers we run ourselves, such as app.quokkabot.com.
Who we are
Quokka Bot is open-source software. MB Nexus consulting ("we") publishes this website, the Mac app and the iPhone app, and answers email sent to support@quokkabot.com:
MB Nexus consultingLeičių g. 17-20
LT-12109 Vilnius
Lithuania
support@quokkabot.com
A Quokka Bot server
Each Quokka Bot server is run by its owner: the person or organisation that installed it. The owner decides what the agents do and who signs in, and is responsible for the data on the server. We have no access to servers that other people run, and the software sends us nothing. For servers we run ourselves, such as app.quokkabot.com, we are the owner.
What the server stores
- The owner's name and passkeys (public keys only), and the signed-in sessions and devices.
- Tasks and chats: the owner's messages and images, the agent's replies, a one-line summary of each step (the page it opened, the command it ran) and a short excerpt of what each step returned.
- Files: downloads, attachments and each agent's workspace.
- Each agent's browser profile: cookies, history and site data for the sites it used.
- Saved logins: a name, the sites and the username. Passwords and 2FA secrets are encrypted with AES-256-GCM; the key is kept outside the database.
- If Gmail is connected: the Gmail address and an encrypted refresh token.
- The Claude account the agent signed in with (its email and plan type) and the Claude CLI's own sign-in file.
- An activity log of what the agent and the owner did: pages, files, commands, downloads and the names of logins used. Text typed into messages and forms is stored there only as a hash. Each entry is chained to the one before it, so changes can be detected.
- Logs: requests to the server with the visitor's IP address, and every host an agent's computer connected to.
Everything is stored on an encrypted volume on the server.
How long it is kept
- Until the owner deletes it. Deleting a login or disconnecting Gmail removes it at once; disconnecting Gmail also revokes the access at Google.
- Removing an agent deletes its tasks, files, browser profile, logins and Gmail connection. The activity log stays, so the record of what happened is complete.
- Request and connection logs are kept up to a fixed size, then the oldest lines are dropped.
- If backups are on, snapshots are kept for up to 12 months, so deleted data can remain in them until they expire.
Who the server sends data to
- Anthropic, for every task. The agent runs Claude Code signed in with the owner's Claude plan. Anthropic receives what the agent works with: the owner's messages and images, page text and screenshots, files it reads, command output, email it reads, and the names, usernames and sites of saved logins (never passwords or 2FA codes). Anthropic's terms and privacy policy apply, including whether it uses this data to train models. Quokka Bot turns off Claude Code's telemetry, error reporting and other non-essential traffic.
- Sites the agent visits, only those the owner allowed. They see the server's IP address and what the task needs: searches, form entries and sign-ins. DuckDuckGo is allowed by default for searching.
- DNS resolvers: Cloudflare (1.1.1.1) and Quad9 (9.9.9.9) look up the names of the sites the agent may reach, unless the owner sets other resolvers.
- Google, only if the owner connects Gmail, through a Google project the owner sets up: to search, read and draft mail.
- Let's Encrypt: the server's domain names, for its HTTPS certificates.
- A storage bucket the owner chooses, only if backups are on: encrypted copies of the database and the agents' files, browser profiles included. Claude sign-ins and the encryption keys are never in backups.
The Mac app
- It connects only to the server address you enter, over HTTPS.
- You approve its sign-in with a passkey on the server. It names itself "Quokka Bot on" followed by your Mac's name, so you can recognise it in the server's list of devices.
- On your Mac it stores its settings (server address, notifications, download folder, window position), its session cookie, which macOS keeps encrypted, and the files you download, in Downloads/Quokka Bot.
- Notifications are shown by macOS. By default they include the agent's question; turn off "Show details in notifications" to hide it.
- It checks for updates every 6 hours, from the server you connected to.
- It has no analytics and sends no crash reports.
- The installer downloads from app.quokkabot.com, which logs your IP address like any request to a Quokka Bot server.
The iPhone app
- It connects only to the server you sign in to and keeps the sign-in in the iOS Keychain.
- What you write and approve in it goes to that server, which handles it as described above, Anthropic included.
- It has no analytics, advertising or tracking of its own.
- Apple delivers the app through the App Store under Apple's privacy policy. If you allow it in iOS Settings, Apple shares crash reports and usage statistics with us.
This website
quokkabot.com is a set of static pages served by Cloudflare. It sets no cookies, runs no scripts and loads nothing from other sites. Cloudflare processes your IP address and request details to deliver the pages and protect them from attacks, under Cloudflare's privacy policy. We see only total traffic counts in Cloudflare's dashboard.
Email and GitHub
- Email to support@quokkabot.com is forwarded by Cloudflare Email Routing to our mailbox at Google. We use it only to answer you, keep it while we help you and follow up, and delete it when you ask.
- Issues and discussions on GitHub are public, apart from private security reports. GitHub's privacy statement applies there.
Legal basis
We answer email and keep this website running and secure because we have a legitimate interest in supporting our software (Article 6(1)(f) of the GDPR). On a Quokka Bot server, the owner decides why data is processed and on what basis.
Processing outside the EU
Anthropic, Cloudflare, Google and GitHub may process data outside the European Economic Area, including in the United States, under safeguards such as the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.
Your rights
You can ask us for a copy of the data we hold about you, and ask us to correct it, delete it, restrict its use or stop using it. You can also complain to a data protection authority, for example in the country where you live. For data on a Quokka Bot server someone else runs, ask that server's owner; we cannot reach it.
Children
Quokka Bot is not meant for children under 16, and we do not knowingly collect their data.
Changes
We update this page when the software or our services change. The date at the top shows the last change, and the page's full history is public in the GitHub repository.
Contact
Questions and requests: support@quokkabot.com.