Quaka

Sync between your devices

Sync carries your threads, memory and settings to your other computers. It stays off until you sign in to it. This page says what it stores and who can read it.

Updated

Quaka keeps your work on your machine. Sync is the one feature that sends some of it to a server of ours, and only after you turn it on and sign in.

What syncs

  • Your threads: messages, titles, and each thread's mode and model.
  • Memory: the notes Quaka keeps about you and your projects, including notes still waiting for your approval.
  • Settings that make sense on every machine.
  • Your saved command rules, network allowlist and trusted repositories.
  • Which threads read untrusted content, so a thread that did stays careful on every device.
  • Custom model providers, without their API keys.

What stays on each device

  • API keys and sign-in tokens, which stay in your operating system's keychain.
  • Your code. Git already moves code between machines.
  • Folder paths, local models, the dictation model and the browser profile.
  • Chat-app connections, automations and pull request watches. Each runs on one device so it never runs twice.
  • The network log and the usage log.

How it works

Turn it on in Quaka under Settings, Sync, and sign in with GitHub or Google. Each device keeps its own log of changes, encrypts and signs every entry before it leaves the machine, and sends it to our sync service at sync.quaka.app. Your other devices download the entries and merge them. A device that was offline catches up when it comes back, and an outage on our side only delays sync.

To add another computer, sign in with the same account on it. Nothing else is needed: no code to type, no device to approve.

Who can read what you sync

We can. Signing in is all a new device needs, so our service holds the key for your account. That key is stored encrypted under a master key we keep apart from the database. We don't look at synced data to run the service, but you should treat it as data we are able to read, and could be required by law to hand over.

Anyone who takes over your GitHub or Google account can sign in a new device and receive your synced data. Your devices list every device that received it under Settings, Sync, and you can remove one there. Protect the account you sign in with, two-factor authentication included.

What the sync service stores

  • Your account: whether it's GitHub or Google, its account id, and the email address and name it gives us.
  • Your devices: their names and when each signed in or last synced.
  • Your synced entries, encrypted, with their sizes and the times they arrived.
  • The keys it holds for your account, encrypted under the master key.
  • A record of each time a device received your key.

It 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 service runs on a server in Sydney, Australia.

Turning it off and deleting it

Turn off sync on a device and it leaves your devices: it stops sending and receiving, and keeps its own threads and notes. What it already synced stays on the service and your other devices.

Delete synced data in Settings, Sync deletes your account on the service: every synced entry, the keys we held for you, your devices' sign-ins and the record of which devices received your key. Your devices keep their own copies. Database backups taken before you deleted are removed within 14 days. Signing in again afterwards starts from nothing.

For anything else, write to hello@quaka.app. The privacy policy covers the rest of Quaka.