The Record
Privacy Policy
Last updated · November 14, 2026
SlowBurns.app turns a plain message into a Civil-War-style field dispatch and a short documentary film. This policy explains how accounts, messages, photographs and generated work are handled. Please also read the Terms of Service. Do not submit secrets or photographs you do not have permission to use.
One account across the site
The grove (/), /about and /office use one Clerk-backed account. Google is a sign-in option through Clerk, not a separate browser-only account. Clerk handles identity, sign-in details, sessions and profiles, including your name, email address and profile image when available. SlowBurns verifies Clerk session tokens and associates your Clerk user identifier with service-held account and job records.
Messages, films and storage
- Messages and letters. Submitted text reaches the SlowBurns API and OpenRouter and its routed model provider to write the dispatch. The resulting letter goes to our render worker for film production and narration. Part of the original message also goes to fal.ai to illustrate the dispatch as an engraved plate.
- Cloudflare D1 records. Our database holds user identifiers, accounts and memberships, usage and entitlement records, job ownership and state, and share records. A share record includes the recipient name, any note, its token and first-view timestamp. D1 is not where we store film bytes or letter text.
- Cloudflare R2 objects. Object storage holds job manifests with messages, letters and processing metadata, generated portraits and their account-linked status records, engraved plates, and finished film bytes. The render worker also handles working files while producing and uploading a film.
Photographs and portrait sittings
A sitting can start automatically. When a signed-in account has no portrait and the client finds an available Google/profile photograph, it can start a sitting without a separate upload or sitting-button click. The client limits this automatic attempt using a per-account sessionStorage flag. This can happen on the grove as well as on /about and /office.
- Uploaded photographs. The upload client attempts to resize your photograph in the browser to a maximum 1024-pixel long edge before sending it to SlowBurns. If browser conversion fails, it may send the original file instead, subject to the API's file checks. SlowBurns forwards the received image to fal.ai for the portrait transform.
- Google/profile photographs. For this path, the browser asks SlowBurns to use your account photograph. The server looks up the photograph URL through Clerk, fetches the image from its source and forwards the image to fal.ai. This path does not use the upload client's browser downscaling.
- What we keep. The portrait API handles source image bytes in memory to send them to fal.ai; it does not write those original photograph bytes to SlowBurns storage. It does store the generated portrait in R2 and an account-linked record with status, identifiers, source type, source URL when available, timestamps and Clerk-sync results. A source URL can remain in that record after a later upload. The /about page can separately keep an upload preview in your browser.
- Your Clerk profile image. SlowBurns sends the generated portrait to Clerk to set it as your account profile image. This is best-effort: the R2 portrait can be ready even when Clerk has not updated. Failed syncs have a bounded retry limit, not a guarantee of eventual success.
Sit again or remove a portrait
The portrait panels on /about and /office offer re-sitting and a self-service Remove control when a portrait is ready. Re-sitting stores a new portrait and attempts to delete the previous image. Remove deletes the stored image and removes or clears its R2 status record, then separately attempts to clear the Clerk profile image. An R2 deletion can fail, and a Clerk failure can leave the Clerk image in place even after the R2 copy is gone. The current interface may not display that partial-cleanup warning; contact us if a likeness remains.
Remove also sets a sessionStorage flag to suppress another automatic sitting in that browser session. It is not a permanent account-wide opt-out; a new session can attempt another sitting. Removal does not clear a saved browser preview, delete dispatches or recall copies already downloaded or cached. We cannot guarantee immediate or universal deletion, including deletion from fal.ai or Clerk's own retained data.
Seven-day films; retained letters and plates
The film policy is seven days, measured from the job's creation time, not seven days after you first watch it. After expiry, the archive and share responses stop offering new playback links. Physical cleanup of finished film bytes is request-driven: archive requests attempt a limited batch of deletions, so cleanup is not guaranteed at an exact deadline. Previously issued playback links can remain usable while valid and while the bytes remain.
Film expiry does not erase the original message, generated letter, engraved plate, job manifest, account/job record or share record. Those records remain unless separately removed; the seven-day policy is not an all-data deletion policy.
Account access and links
Listing your archive requires a signed-in account and membership checks. A share link is different: anyone holding a valid link can read the shared letter, recipient name and note without signing in, and obtain playback while available. A signed playback link likewise permits viewing without signing in while valid. Portrait and engraved-plate URLs use hard-to-guess image identifiers rather than sign-in checks; anyone holding one can retrieve that image. Links can be forwarded. Treat them as access to their content, not as private merely because they are unlisted.
Cookies, browser storage and analytics
Clerk uses cookies and session mechanisms for sign-in. These necessary account mechanisms
are separate from SlowBurns browser storage: localStorage holds the sb-theme
preference, the sb-account returning-account hint and, on /about,
slowburns.portraitSource upload previews. sessionStorage holds office draft,
recipient, letter and job state under slowburns:* keys, plus per-account
automatic-sitting flags under slowburns.passiveSit.*. These are not a
browser-only substitute for your Clerk account.
The grove, office and recipient dispatch page load Plausible for page and named-event analytics. The /about page and these standalone legal pages do not include that analytics script. Plausible describes its visitor analytics as cookie-free in its data policy; this does not mean the account service uses no cookies. Cloudflare also processes connection and request information to serve the site, and service logs can contain job identifiers, status and error information.
Services that handle information
- Clerk — account identity, sessions and profile images across the site.
- Google — when used for sign-in or as the source of a profile photograph.
- Cloudflare — Pages hosting, D1 records, R2 objects and delivery.
- OpenRouter — message processing and routing to the selected model provider.
- fal.ai — photograph-to-portrait processing and message-based engraved plates.
- Narration — the configured primary is our self-hosted vox engine, which receives the generated letter. Cartesia can receive that letter as a fallback for qualifying capacity or availability failures; it is not used for every film.
- Plausible — page and event analytics on the pages described above.
These links explain the providers' own practices. This policy does not promise their retention periods, deletion outcomes or model-training practices.
Sign-out, account deletion and requests
Signing out ends the Clerk session and hides signed-in views; it does not delete your account, R2 objects or D1 records, revoke shared links, or clear every browser key. Theme choices, saved previews and draft/job state can remain. Clear site data in your browser to remove local copies; that does not delete service-held data.
Deleting a Clerk account is an identity-provider action, separate from portrait removal. SlowBurns has no automatic account-deletion cascade into D1 or R2 and no self-service control to purge all dispatch data. Clerk account deletion does not automatically purge our account/job records, messages, letters, plates, portraits, share records or remaining films.
For access or deletion requests, or a portrait that did not fully clear, email [email protected] with your account email and relevant job id or URL. Do not send passwords or session tokens. We may need to verify the request and establish which service and provider copies are involved; this is not a promise of an instant, all-provider purge.
Children
The service is not directed at children under 13, and we do not knowingly collect information from them.
Changes
If this policy changes, the revised version is posted at this address with a new date. Material changes will be noted on the site.
Contact
Questions or requests about your information: [email protected].