Security

Sign-in

You sign in with your Google account. Google's Identity-Aware Proxy (IAP) stands in front of the app, and only accounts the owner has added get past it.

Kept apart

Every query is scoped to your account, and the database backs that with row-level security, so your rows are kept apart from every other account's.

What is sealed

• Under a key of your own: Work's request notes and drafts, resource links, project context and notes, Repository Information's notes, contacts and clients' working preferences.
• Under the app's key: your Anthropic key and your scheduled tasks' tokens.
• Kept apart, not sealed: names, time entries and invoice amounts.

AI output

Anything a model drafts is shown as plain text and waits for you. It is never applied without your click, and nothing is sent to a client.

GitHub text is untrusted

Issues, comments and pull requests are shown as plain text, never as HTML, and the app never acts on them. A session works only on the issue and comments your passkey approved.

Launches need your passkey

Launching a session, pricing a request and adding a relay token or a scheduled task each ask for your passkey. Each approval is used once, expires after two minutes and is bound to what the page showed you. If you turn on launching several issues at once, one passkey approves up to 4 issues without showing their text.

What the owner can see

The owner runs the app and can decrypt your data. Your keys protect it from a leaked database dump, a stolen backup or a bug in a query, not from the owner.

Leaving

When you leave, your rows are deleted and your key is destroyed. Backups are kept for 7 days, then they are gone too.

The only sign-in

The only sign-in is my.thistlewick.app, through Google. Nobody will ask you for a password, a code or a key by email.

Request an invite