Privacy

What we collect

Taula has no account, no analytics, no telemetry and no crash reporting. It makes exactly one kind of request to us: the licence check described below. Nothing about your databases, your queries, your schema or your files is part of it.

The other record we hold is on your download page, where signing in with a licence key leaves a line per download. Both are described below.

Activating Taula

A licence covers a fixed number of Macs, so the first run asks for your key and registers the Mac against it. That request carries five things: the key, a name for the computer (the one in System Settings, so you can tell your Macs apart on your account page), its model identifier such as Mac16,8, the macOS version and the Taula version.

It also carries a device fingerprint, which is a SHA-256 hash of your Mac’s hardware UUID with a fixed salt. The hardware UUID itself never leaves your Mac, and the hash cannot be turned back into it. It exists so that re-activating the same Mac takes the same seat instead of a new one.

After that, Taula repeats the check about once a day. Each check refreshes the same record and stores a truncated IP address such as 83.45.•.• and the country Cloudflare reports, exactly as a download does. If we cannot be reached, Taula keeps working offline for fourteen days and then asks to be connected once.

You can see every Mac on your licence, and release any of them, on your account page, or from Settings → Licence inside the app. Releasing deletes nothing we would otherwise keep — it frees the seat and locks that Mac until a key is entered again.

If a licence is refunded or revoked, the next check fails and Taula locks. That is the point of the check, and it is the only thing it decides.

Where your data lives

Connections, query history, snippets, the change journal, assistant transcripts and settings are plain files in the Application Support folder of your Mac. Passwords, API tokens and keys are stored in the macOS Keychain. None of it is synced or uploaded by Taula.

Your databases are reached directly from your Mac over the connection you configured, or through an SSH tunnel you configured. Query results are shown to you and kept only as long as the window is open, except where you export them yourself.

The assistant

The assistant runs on a llama.cpp server on your own machine. Prompts, your schema and any rows it reads stay on that machine. The model file is downloaded once from its public host on first use; that download is the only network request the local assistant makes.

If you choose to add an Anthropic API key in Settings, the assistant, ghost text and inline edit send your prompts and schema context to Anthropic. That data is handled under Anthropic's terms, not ours. Remove the key to stop.

The MCP server

taula-mcp exposes your saved connections to agents you wire up on your own Mac, over standard input and output. It listens on no network port and sends nothing anywhere. It is read-only unless you start it with writes enabled. Whatever an agent does with the results is governed by that agent's own policy.

Buying Taula

Purchases are handled by Polar, acting as merchant of record. Polar takes the payment, handles VAT, issues your licence key and emails it to you, all under their own privacy policy. Your card details never reach us and we never see them.

What reaches us is the email address on the order and the licence key record behind it, so that we can recognise your key on the download page and answer support requests. We do not sell or share it. If you refund the order, Polar tells us and the licence stops working.

Your download page

Downloads and updates are tied to your licence, so the download area keeps a small record against it: the email address you bought with, when the licence was created, and one line per download with the version, the time, a truncated IP address such as 83.45.•.•, the country Cloudflare reports, and the browser or app that asked. Nothing else.

Your licence key itself is never stored. We keep a keyed hash of it, so a copy of our database does not hand anyone a working key, and the last five characters so you can recognise which key you are using.

Why the record exists: to show you the downloads on your own account page, and to notice a key that has escaped into the wild. It is not analytics, it is not sold or shared, and it is never joined to anything you do inside the app, because the app tells us nothing beyond the licence check above.

Signing in sets one cookie. It is strictly functional — no tracking, no third parties — and signing out deletes it. Downloads are served from a link signed to your licence that stops working after five minutes.

Ask us and we will show you every row we hold for your licence, or delete them. Deleting the download history does not affect your licence.

Changes

If any of the above changes, this page changes with it and the date at the top moves.

Questions

Write to [contact email].