Privacy and cookies

Last updated 1 October 2026. AI Playbooks is operated by an individual based in Singapore.

What is stored, and where

Identity and application data are held in two separate places on purpose, and the split is what keeps personal data out of the application database.

Held by Clerk, the identity provider

When you sign in, Clerk holds your account: your email address, your name and avatar if the provider you used supplies them, the identifier of that provider, and your sign-in history. If you sign in with Google, GitHub or LinkedIn, that provider tells Clerk who you are. AI Playbooks never receives or stores your password.

Lawful basis: performance of a contract. There is no account without it, and the account is the only thing you asked for.

Held in the application database

The database stores an internal identifier for you, the opaque user id Clerk issues, and the times your record was created and updated. That is the whole user record. It contains no email address, no name and no avatar.

Linked to that internal identifier, it also stores:

• Saved problems. The identifier of each problem you saved, and when you saved it.
• Reading history. The identifier of each problem you opened, when you first opened it, when you last opened it, and how many times. This is a deduplicated list of what you have read, held as one row per problem, rather than a log of every visit.

Nothing else about your activity is recorded. Server logs, which every web service keeps, are described below.

Lawful basis: performance of a contract. Saved problems and reading history are the account, not a by-product of it.

Backups of the application database

Once a day, at 03:00 Singapore time, a copy of the application database is written to a private Google Cloud Storage bucket in Google's Singapore region, asia-southeast1. The copy holds exactly what is described above: the user records, saved problems and reading history. Each backup is deleted 30 days after it is written.

Lawful basis: performance of a contract, the same as the data it copies. A backup is what keeps your saved problems and reading history from being lost to a fault.

What is not collected

• There is no analytics, no tracking pixel and no advertising script anywhere on this site.
• No cookie is set for analytics, advertising or profiling.
• Your personal data is never sold, rented or shared for advertising.
• Public knowledge pages are fully readable signed out, and reading them records nothing against any person.

Cookies

The only cookies set are Clerk's session cookies, which exist so that you stay signed in and so that a request can be verified as yours. They are strictly necessary for the sign-in feature and are not used to profile you. Signed out, no cookie is required to read the site.

Lawful basis: strictly necessary, so no consent is required for them, and none is asked for.

The theme preference, stored in your browser

If you set the light or dark theme by hand, that choice is saved in your browser's local storage under ai-playbooks-theme. It is read before the page paints so the site does not flash the wrong theme at you. It is not a cookie, it is never sent to the server, and it is not tied to your account, so it stays on the device you set it on. Leaving the control on System stores nothing at all, and clearing your browser storage removes it.

Lawful basis: strictly necessary for a preference you asked for, so no consent is required. It holds one of three words and identifies nobody.

Why there is no cookie banner

Because there is nothing to consent to. A consent banner exists to ask permission for cookies that are not strictly necessary, and AI Playbookssets none. Showing one anyway would be theatre, and a platform whose whole subject is knowing when a technology is unnecessary should not perform it.

This is a statement about today, not a promise about forever. If analytics is ever added, nothing will load or be sent until you have accepted it, and this page will change in the same release rather than afterwards.

Who else processes your data, and where

AI Playbooks runs on third-party infrastructure. Each of these acts as a processor, each has its own privacy policy that governs what it does, and each is named here with the region it processes in:

• Clerk, a United States company, handles authentication and account storage, and processes account data in the United States, on a standard United States instance.
• Supabase hosts the PostgreSQL database that holds your saved problems and reading history, in AWS's Singapore region,ap-southeast-1.
• Google Cloud Run runs the application, in Google's Singapore region, asia-southeast1.
• Google Cloud Storage holds the daily backups of that database, in Google's Singapore region, asia-southeast1.
• Cloudflare serves as the network edge, terminating TLS and passing requests through. Cloudflare is a global network and terminates at whichever location is nearest to you.

Transfers outside Singapore rely on the providers' own standard contractual clauses and equivalent safeguards. Your personal data is never sold.

Clerk also sends the transactional email tied to your account, such as sign-in codes and password resets, delivered on behalf of this domain.

Server logs

Requests produce operational logs held by Google Cloud and Cloudflare. These can include IP addresses, timestamps, requested paths and user agents. They are used to keep the service running and to investigate faults and abuse. They are not joined to your account to build a profile of you.

How long it is kept

One line per thing, so you do not have to parse a paragraph for it:

• Account data, held by Clerk. Until the account is deleted.
• Your user row. Until the account is deleted, and it is removed with it.
• Saved problems. Until you remove the bookmark, or the account is deleted. Removing one deletes the row immediately.
• Reading history. Until you remove the entry or clear the history, or the account is deleted. There is no automatic expiry today, which is a known gap rather than a decision, and it is recorded as one.
• Database backups. 30 days. Each daily backup is deleted 30 days after it is written, so anything removed from the live database, including a removed bookmark, a cleared history or a deleted account, can persist in backups for up to 30 days after it is removed.
• The theme preference, in your browser. Until you clear your browser storage. It never reaches the server, so there is nothing forAI Playbooks to keep or delete.
• Server logs, held by Google Cloud and Cloudflare. Governed by those providers' own retention, not by AI Playbooks.

Your choices

• See what is stored. Your saved problems and your reading history are both visible in the site itself, on the Saved and History pages, and those pages are the complete contents of your account.
• Delete parts of it. You can remove any saved problem, any single history entry, or your entire history, from those pages.
• Delete the account. Email security@aiplaybooks.app and the Clerk account and every associated row will be deleted. This is handled by hand today rather than by a self-service button, so allow a few days. Copies already in the daily backups are not edited, and expire within 30 days.
• Correct your details. Your name and email live in Clerk, and Clerk's account controls in the site header are where they are changed.

Under Singapore's Personal Data Protection Act you may ask what personal data is held about you, ask for it to be corrected, and withdraw consent to its use. Withdrawing consent means deleting the account, because the account is the only reason any personal data is held.

Children

This is a service for people doing professional work and is not directed at children. Accounts are not knowingly created for anyone under 13.

Changes

If this policy changes in substance, the date at the top changes with it. Continuing to use the service after a change means accepting the updated policy.

Contact

Questions about this policy, requests about your data, and security reports all go to security@aiplaybooks.app.