What Twig keeps in your account

Twig works without an account: then everything stays in your browser on your device and never leaves it (except a calendar address you choose to show in Today, and what an AI assistant you connect reads, below). This page is about what changes when you sign in.

What is stored

• Your email address, to sign you in (or the email your Google account shares with Twig).
• Your workspace: your cards with their notes, statuses, dates and reminders, your groves, labels, automations and templates, and what’s in your Trash.
• Earlier versions of your workspace: your last 20 saves, plus the last one from each of the latest 48 hours you used Twig, so a mistake can be undone.
• The files you add to cards (each up to 10 MB), so they open on your other devices too. A file added while you were signed out is copied to your account once you sign in. Signed out, a file stays only in the browser you added it in.
• A random name for each browser you use, so your devices can tell their own saves apart.
• If you connect Google Calendar: the email of that Google account and a key from Google that lets Twig keep your planned times and your calendar in step. Only Twig’s server reads the key; your browser gets a new short-lived one each hour.
• If you turn on automatic backups to Google Drive: the email of that Google account and a key from Google that lets Twig put its backups in your Drive. Only Twig’s server reads the key; your browser gets a new short-lived one each hour and sends the backup straight to a “Twig backups” folder in your Drive, which is the only part of your Drive Twig can see. Google’s privacy policy covers what’s kept there.
• If you connect your Outlook calendar: the email of that Microsoft account and a key from Microsoft that lets Twig keep your planned times and your calendar in step, as for Google Calendar; only Twig’s server reads the key. Twig connects one calendar both ways at a time.
• If you turn on Remind me when Twig is closed: each browser’s address for notifications, and the reminders of the next two weeks (card title, time and the due-date line) until each is sent.
• If you use your Twig email address (Settings → Save from anywhere): the address, and each email sent to it (its subject, its sender and its words; never its pictures or files) until a browser signed in to your account puts it in your Inbox, then it is deleted; one no browser takes is deleted after 30 days. Emails reach Twig through Cloudflare’s email routing, which passes them on without keeping them.
• If you connect Telegram (Settings → Save from anywhere): your Telegram chat’s number and username, and each message you send Twig’s bot (its words, and who a forwarded one came from; never pictures or files), kept and deleted as emails are. Telegram itself carries the messages, under its own privacy policy. /stop in the chat or Disconnect in Settings unlinks it.

If you turn on Automatic backups to Dropbox (Settings → Account & backup), your browser sends the backup straight to a Twig folder in your own Dropbox; it never passes through Twig’s server, and the key that lets it do so stays in that browser. Dropbox’s privacy policy covers what’s kept there.

Twig has no ads and no analytics, doesn’t sell or share your data, and doesn’t read your cards for anything but keeping them in sync.

Where

In a database run for Twig by Supabase, which stores it encrypted at rest and sends it over encrypted connections. It is kept in Australia (Sydney).

Who can read it

Only you, when signed in: the database refuses every other account’s requests for your rows and your files, and nobody can change them except through your own signed-in devices. The people who run Twig and Supabase can reach the database to keep it running, and don’t look at your cards.

Google Calendar, both ways (optional, signed in)

Connecting Google Calendar in Backup & settings → Calendar in Today lets Twig see and edit the events of your main Google calendar, nothing else of your Google account. A time you set aside on a card becomes an event there (with the card’s title and a link back to it), and moving or deleting that event changes the card. Twig reads your other events only to show them in Today, in this browser. Disconnect takes back the access at Google and deletes the key; events already in your calendar stay. You can also remove Twig’s access in your Google Account’s security settings.

Twig uses what it gets from Google only to show your events to you in Twig and keep them in step with your cards. It doesn’t sell it, use it for ads, or share it with anyone. Twig’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Your calendar in Today (optional)

If you paste a calendar’s secret address in Backup & settings → Calendar in Today, Twig keeps that address and the next two weeks of its events in this browser only: not in your account, not in backups. Calendars don’t let web pages read them directly, so each time Twig reads it, the address goes to Twig’s server, which fetches the calendar, passes it back and keeps nothing: no copy of the address or the events, and no log of them. Disconnect forgets both.

Twig never changes a calendar shown this way. Add to Google Calendar on a card opens Google’s own page with the event filled in; nothing is sent until you save it there.

AI assistants (optional)

Connecting an assistant such as Claude or ChatGPT is off until you allow one, in Twig, in your browser. Twig then makes a key for that assistant and keeps only a fingerprint of it, in that browser (not in backups). While Twig is open in a tab there, the assistant’s requests pass through Twig’s server to that tab, and the tab’s answers (the cards it asked for) pass back the same way. The server keeps none of them: no copy and no log of your cards, and nothing about the connection once the tab closes. Disconnect in Settings → AI assistants stops that assistant at once.

If you turn on Also while Twig is closed (it starts off) and you’re signed in, that browser also lists the fingerprint in your account, with the assistant’s name, whether it may change cards, and when it last read them, so it can reach your account’s copy of your cards while Twig is closed. Its requests then go to Twig’s server, which reads that copy from your account and, if you allowed changes, saves the change there as a new version (Earlier versions keep the one before). The server keeps nothing of it once it has answered. Turning off Also while Twig is closed or Let assistants connect, Disconnect, or Remove Twig data from this device takes the fingerprints off your account, and deleting your account removes them with everything else.

Whatever an assistant reads from Twig becomes part of your conversation with it, so it is sent to that assistant’s company (for Claude, Anthropic; for ChatGPT, OpenAI) and kept under its terms, not Twig’s.

Your currency

When you first log money in a grove (or type an amount, plan one for a project, or open Money before then), Twig asks its server which country your connection comes from, to pick a currency to start with (you can change it). The server answers with the country and stores nothing: no log of it, and no copy. It finds the country in its own copy of a public list of internet addresses, so no other company is asked: IP Geolocation by DB-IP (CC BY 4.0).

When something goes wrong

If part of Twig fails in your browser, Twig says so and offers Send report. Nothing is sent unless you press it. A report holds only where in Twig’s own code it happened, the error’s wording with anything quoted taken out, Twig’s version, your browser’s name, whether it is a phone, and which place in Twig was open: never your cards, their titles or notes, your address or your account. It is written to the server’s log, kept by the host, and read only to fix Twig. When a request to Twig’s server fails, the server logs its address within Twig and the error, without anything you sent.

Deleting it

• Delete account in Backup & settings → Account removes your account, your workspace and all its earlier versions, and the files on your cards, at once. Supabase’s own backups of the database are replaced within a week.
• A file you remove from a card, or that leaves with its card when you empty Trash, stays in your account for 30 days (so Undo still has it), then is deleted.
• Signing out with Remove Twig data from this device deletes what Twig saved in that browser; your account keeps its copy.
• Export a backup from Backup & settings any time to keep your own copy.