The short version: your code, threads, memory and keys stay on your computer. We receive data only if you join the waitlist or turn on sync, and we never sell it, use it for advertising, or use it to train models.
The Quaka app
Quaka runs on your computer. Your code, your threads and their history, what Quaka remembers about you and your projects, and your API keys (kept in your operating system's keychain) stay there. The app sends us no analytics, usage data or crash reports.
Some features talk to other services. Those requests go straight from your computer to the service, never through us, and that service's own privacy policy applies:
- The model provider you choose, with your own key, receives your prompts, the files you attach and what the agent reads to answer.
- DuckDuckGo receives the agent's web searches.
- GitHub, Linear, Slack, Discord or Telegram receive what Quaka sends them once you connect them.
- A memory store such as Supermemory, Mem0 or Zep receives your memory notes if you connect one.
- GitHub or Google confirm who you are when you sign in to the app. The sign-in token stays in your keychain; we never receive it.
When Quaka checks for updates, it downloads a small file from our download server. Like any download, that request shows the server your IP address.
Sync, if you turn it on
Sync is off until you sign in to it with GitHub or Google. It carries your threads, memory notes and settings between your own devices through our sync service. API keys never sync.
- What we store: whether you signed in with GitHub or Google, your account id there, and the email address and name it gives us; your devices' names and sign-in times; your synced entries, encrypted; the keys for your account, encrypted under a master key we keep apart from the database; and a record of each time a device received your key.
- Who can read it: we can. Signing in is all a new device needs, so our service holds your account's key. We don't look at synced data to run the service, but it is data we are able to read, and could be required by law to hand over.
- Why: to deliver your data to the devices you sign in on. That is the service you asked for, and the only use we make of it.
- Where: on a server in Sydney, Australia, run on Amazon Web Services.
- How long: until you delete it. Delete synced data in the app's Settings, Sync removes everything listed above at once, and backups taken before that are gone within 14 days.
- Logs: the service keeps no access logs. Your IP address is used in memory to limit how many requests one address can make, and is written down only if a request fails inside the web server in front of the service, in that server's error log.
The sync page explains what syncs and what stays on each device.
The waitlist
If you join the waitlist, your email address goes to our server on Amazon Web Services in Sydney, Australia, which keeps it. Your IP address is used to limit how often one connection can sign up. We use your email to invite you to Quaka and to tell you when it is ready, nothing else. Ask us at any time and we remove it.
This website
quaka.app sets no cookies and runs no analytics or tracking scripts. It is hosted by Vercel, which receives your IP address and browser details to deliver the pages, as any web host does.
Services that handle data for us
- Amazon Web Services: hosts the sync service and the waitlist.
- GitHub and Google: sign-in for the app and for sync.
- Vercel: hosts this website.
Your choices
You can ask us what we hold about you, ask for a copy, have it corrected, or have it deleted, wherever you live. Write to hello@quaka.app from the email address involved and we will answer within 30 days. Sync data you can delete yourself, from the app.
Children
Quaka is not meant for anyone under 16, and we don't knowingly collect data from them.
Changes
When this policy changes, the date at the top changes with it. If a change affects what we store or who can read it, we will say so on this page before it takes effect.