A short notice for a short list.

How we use it

We use this information to send a signup confirmation, manage the queue, and send an invitation when a studio is available. Service providers that host the application, database, and email delivery process it for us. We do not sell waitlist information.

Web research

Exa web research is disabled by default during the pilot. If separately activated, research Figments send search query text verbatim to Exa Search. A query may include words from your question, manuscript or conversation. It is not anonymized or redacted. Exa processes it under its own service terms and returns source titles, URLs and excerpts. The writer Ask uses these results as model context. Your signed receipt records each search query and its outcome. Retrieved sources include titles, URLs, dates and excerpts. Sharing a receipt also shares those queries and excerpts. The receipt verifies the retrieval record; it does not establish that a source supports a claim. Configuring an Exa key alone does not activate search.

Website analytics

Vercel Web Analytics separately processes page views — including the page URL, timestamp, referrer, country, browser, device, and operating system — so we can understand site traffic. It also records anonymous product events, such as opening a document, creating a document, a coarse amount of typing, a large paste, typing the editor judged automated and which timing rule judged it, whether the browser writing in a document was judged automated, when a Figment suggests a change, what you decide about a Figment suggestion, downloading a receipt, checking a receipt, and whether a new account arrived from an invitation, the waitlist, or another path. Those events do not include your writing, document titles, email address, or account. The editor compares the timing of your key presses on your device to detect typing injected by software; those timings never leave your browser. When it judges typing automated, it does not stop you writing. The document’s signed receipt records the suspicion and the rule that raised it, and anyone you give the receipt to can read it. Your browser keeps a local note of documents you have opened and when you first visited, so a return visit can be counted without sending those details. Vercel describes this as anonymous, aggregated analytics without cookies and not associated with an individual or IP address. Analytics data is not added to your waitlist row.

Vercel BotID’s script also runs on Click Clack’s pages. It is separate from analytics: it checks whether your browser is automated when you open a document to write or join live collaboration. When it judges the browser automated, it does not stop you writing, and the document’s signed receipt records the suspicion.

After you sign in, and only while the studio is open, we send product events to PostHog — creating a document, installing a pack, asking a figment, deciding a suggestion, exporting — keyed by account and workspace ids. The event payloads do not contain your email or manuscript. PostHog stores your account email on your profile and links it to studio activity, including when you ask a Figment. We do not add these events to your waitlist row. During this study, a signed-in studio session can be replayed with the manuscript, document titles, and the conversation with a Figment masked. We record clicks on buttons and links, without the words those controls show. When you ask a Figment, we also record the model, how long it took, token counts, cost, and the error class. By default, these traces leave out the question and reply. If AI debugging is enabled for your workspace, new Ask conversations can also send PostHog questions, replies, selected manuscript text and nearby context, conversation history, Figment instructions, and tool requests and results. Settings shows whether this mode is enabled for new conversations. Earlier conversations are excluded from live content capture. We plan to import saved questions, replies and tool activity from earlier conversations on active documents in selected pilot workspaces into PostHog as labeled historical records. Some planned records contain a saved question without a reply. The import will not recreate original model calls. Turning AI debugging off stops new live content capture; it will not delete imported records. Deleting a source document will not automatically remove its imported snapshot. We limit payload sizes and try to remove credentials before sending them, but filtering can miss sensitive information. Authorized Click Clack operators use the traces to investigate failures and improve Figment behavior. Session replay remains masked. To request access, correction or deletion, email hello@clickclack.studio.

How long we keep it

We retain a waitlist entry after invitation as invitation history until you withdraw or ask us to delete it. Joining the waitlist does not create an account or grant account access; account access is managed separately.

Your choices

To withdraw, request deletion, or ask a privacy question, email hello@clickclack.studio.