Privacy

This page describes what Whitelabel stores about the people who use it, where that data lives, how long it is kept and how to have it removed. It is written from the code that runs the service, not from a template, and it changes when the code does.

What is stored, and where

Account. Signing in with Google creates an account holding the Google account identifier, the email address and the display name Google shares. Nothing else about the Google account is requested or kept. Accounts live in a Cloudflare D1 database.

Sessions. A browser sign-in creates a session record on the server and sets an HttpOnly cookie that names it. The cookie lasts thirty days. Signing out ends the session; "sign out everywhere" on the profile page ends all of them.

Connected applications. When an application or an AI agent asks for access, the consent it is given is recorded as a grant naming the application, the scopes approved and the times it was created and last used. Refresh tokens belong to that grant. Authorization codes and pending sign-in requests are held for a few minutes in Cloudflare KV and then expire on their own. Grants can be reviewed and revoked from the profile page; revoking one invalidates every token issued under it.

Uploads. Files a signed-in person uploads through the API are stored in Cloudflare R2 under that person's account and are served only to them.

Workspace drafts. Drafts made in the workspace are kept in the browser's local storage on the device that made them. They are not sent to the server unless sync is turned on. A service worker caches the public pages so they open offline; it caches nothing personal.

Request logs. Cloudflare records each request (address, URL, user agent, timing) for operating the service and is the processor for that data. Logs are retained for the period Cloudflare's observability product keeps them and are not used for profiling.

What is not collected

There are no analytics scripts, advertising networks or third-party tags on any page. The content security policy allows scripts only from this origin, so nothing else can load. Email addresses are used to sign you in and to answer your messages, and for nothing else.

Who else sees data

Google, to sign you in; Cloudflare, which hosts the service and stores the data above. Applications you connect see only what the scopes you approved allow, and only while the grant stands.

Your choices

Sign out of one browser or all of them from the profile page. Revoke a connected application from the same page. To export or delete your account and everything held under it, contact krasnoperov.me and name the address on the account so the request can be matched to it; deletion removes the account, its sessions, its grants and its uploads.

Changes

The date at the top of this page's entry in the sitemap is when it last changed. Questions about anything here go to the contact page.