Privacy · Terms · Security and data

Privacy

style.artifacts.boo is run by Michael Thiesen ("we"). This page says what we store, why, who else handles it, and how long we keep it. Questions or requests: michael@thiesen.dev.

What we store

• Your email address, to sign you in with one-time codes (or a passkey, if you save one), to know who an artifact is shared with, and to email you invitations, shares and notifications (on by default; you can turn notification emails off).
• Your display name, if you set one; it's shown on your comments.
• Passkeys, if you save any: each one's public key, a name for it (such as "iCloud Keychain"), and when it was added and last used. The private key never leaves your device or password manager.
• Artifacts: the files your agent writes (up to 50 versions each), images and data files, and live data fetched from hosts a workspace admin approved.
• What people do on an artifact: comments, votes, approvals, form responses, checklists, notes and other shared state; which version you last saw and which comments you've read; an activity log (the latest 5,000 events per artifact).
• Billing, for a workspace on a paid plan: the payment provider's customer and subscription ids, the subscription's status and when the paid period ends. Card details go to the provider, never to us.
• Workspace membership: who belongs to which workspace and in what role, and when members last signed in; for a workspace someone made themselves, who made it and which version of the terms they agreed to.
• Guest visits: which workspaces you've opened a shared artifact in as a guest, and when you last did, so they show up in your workspaces list.
• Agent access: OAuth grants and personal agent tokens, stored only as hashes, with when each was last used.
• Notification settings: whether you want emails, and any channels you add (browser push subscriptions, Pushover user keys, ntfy topics and tokens, webhook URLs and their signing secrets).
• Render checks: after each change a headless browser renders the artifact; we keep the result, a screenshot and any errors. Viewers' browsers also report runtime errors (the latest 30 per artifact).
• Sign-in records: when codes were sent and checked, with your IP address or network, to limit abuse. Kept for an hour.
• Your inbox: a copy of each notification for you (what happened, on which artifact, and the start of any comment), your latest 200, for up to 90 days. A notification leaves your inbox when its artifact or workspace is deleted, when you're removed from the workspace or from the artifact's sharing, or when you delete your account.
• Support requests: what you send us from Help & feedback (or your agent sends for you), and what you chose to include with it (the page you came from, your browser and an error code), kept as a page in our support workspace that only you and we can open, with our replies. We never include what's in your artifacts. You can ask us to delete a request.
• Errors: when something fails on our side or in our own pages, we keep where (with ids removed), a message with addresses and links taken out, the version and your browser family, counted together with the same errors. Errors inside artifacts go to their owners, not to us.
• Reports: if you report an artifact, what you wrote and, if you give it, your email go to us by email and into our operations log; your network address is kept for an hour to limit repeat reports. The workspace isn't told who reported it.
• Request logs: Cloudflare keeps the Workers request and error logs for a few days (up to 7), for debugging. They can include workspace addresses and error text, never passwords or codes.

In your browser

A session cookie per site you sign in to (it lasts 30 days from your last visit), a short-lived cookie during sign-in, and cookies that remember OAuth approvals. Artifacts can keep per-person data in your browser's storage, separately for each artifact. No advertising or cross-site tracking. Pages load Cloudflare Web Analytics, which counts visits without cookies.

Who can see what

• An artifact is visible to its owner, the admins of its workspace, and the people, domains or workspace it's shared with; a public artifact to anyone with its link.
• Workspace admins can see and manage every artifact in their workspace and its member list.
• An artifact's owner, its workspace's admins and their agents can see who has opened it while signed in, which version each person last saw and when. Visits through a public link without signing in aren't recorded.
• People signed in to an artifact see who else is viewing it at the same time, by name or email address. Someone on a public link without signing in sees nobody, and isn't shown.
• Everyone who can open an artifact sees its comments, votes, approvals and form responses, with who made them.
• We, as operator, can access stored data to run the service: backups, restores and support. We don't sell it, use it for advertising, or train models on it.

Who else handles it

• Cloudflare hosts everything: compute, storage (Durable Objects, R2, KV), email sending, the headless browser for render checks, analytics and logs. Data lives on Cloudflare's network; a workspace's database is placed near where it was first used.
• Creem (payments, for paid plans): the merchant of record, which processes payments and handles tax; it receives the billing details you give at checkout.
• Services you choose: if you add Pushover, ntfy, a webhook or browser push, notifications go to that service. Live data sources are fetched from the hosts your workspace approved.

How long we keep it

• As long as the artifact or workspace exists. Deleting an artifact removes it from the live database at once.
• Each workspace is backed up nightly when it changed; up to 30 backups are kept (7 on Free), so deleted data leaves backups within about a month.
• Deleting a workspace deletes its data and its backups, the notifications about it in people's inboxes, and ends its agents' access. Our directory's records about it (members, notifications and billing ids) leave our backups within about a month, and payment entries about it in our operations log stay until they roll off.
• Accounts are backed up the same way: your email, name, passkeys, notification channels (with their keys and secrets), memberships, guest visits, inbox and billing records. The newest 30 backups are kept, so after you delete your account these leave backups within about a month.
• A workspace's billing record (its subscription's status, and the payer's email) is kept while the workspace exists, and in payment log entries until they roll off.
• After you delete your account, your address stays in two places, to limit abuse: our record of who made which self-serve workspaces (so the free plan can't be farmed), and in the list of people removed from each workspace you left (so joining by email domain doesn't add you back).
• What you did in a workspace stays there under your address after you delete your account, until an admin removes it or the workspace is deleted: your comments, votes, approvals and form responses, and the artifact's activity log.
• Support requests you sent stay in our support workspace, with your address, until you ask us to delete them.
• Our operations log (sign-ups, billing changes, reports and failures, with workspace names and sometimes an email address) keeps its latest 500 entries.

Your choices

Turn email notifications off in your account. Leave a workspace from its notifications page, or ask the owner or an admin to remove you from an artifact or workspace. Delete your account from your account page: it removes you from every workspace, and your name, notification channels and passkeys (comments you wrote stay in their workspaces, under your address, until an admin there removes them). Workspace admins can download a full export of their workspace from its settings at any time. To get a copy of your own data, or to have anything else deleted, email michael@thiesen.dev; we reply within 30 days.

Changes

We'll update this page when what we do changes, and change the date below.

Last updated 2026-10-18.