Privacy

Bloomalizer is built as a frontend. The visualizer — sound analysis, camera and screen capture, hand tracking, the particle rendering, recording — is code that runs in your browser on your own graphics card. There is no media server: nothing you play, film or record is sent to Bloomalizer. The one exception is an object you choose to publish, below. The small amount of server code that exists does account bookkeeping (how many clips an account has recorded, an invite or referral code), signs the upload of a published object, relays the optional Report email, and serves the public genome data one shape is drawn from. Hosting is Vercel, accounts are Clerk, published objects are stored with Cloudflare; the full list follows.

The audio stream you connect is analysed locally to drive the visuals — never stored, never uploaded. Photos you drop in are sampled in your browser, become particles, and go nowhere else. The camera and a shared screen are read the same way — frame by frame, in your browser — and hand tracking runs on those frames locally; the hand model is downloaded once from a public CDN and never sees your pictures. Any other open-source decoder the app needs is fetched the same way and never receives your files. Recorded clips (REC) are produced entirely in your browser; they are silent by default, and if music is playing you are asked — every time — whether to include the sound. With MIC as the source, a clip with sound is a recording of your room, which may include speech.

No feature sends audio anywhere. Nothing the visualizer hears is transmitted — not analysed remotely, not identified, not stored. (An optional track identification feature once sent short clips to a recognition service; it was removed in October 2026.)

REPORT is the one explicit send. Pressing SEND in SETTINGS → REPORT emails the operator a device profile — your graphics card's name, browser, platform, memory, the build number — together with whatever note and reply address you typed. Nothing is sent automatically, and the report never includes audio, video, photos or renders.

Some accounts can publish an object they made in the browser (a picture or a 3D model) so that a QR code opens it on any phone. Only when you press the button to publish is it uploaded: its files, a small preview picture and the title you gave it go to Cloudflare R2, our storage provider, where anyone with its code or link can open them. They stay until you delete them, which removes the files; an upload you start but don't finish is deleted within a day. Objects you don't publish never leave your device.

Recording in the studio or Magic needs an account, so that Bloomalizer knows who holds an invite code, how many clips an account has recorded, and whom to tell when something changes. One account serves this site, the studio (studio.bloomalizer.xyz) and Magic (magic.bloomalizer.xyz) — signing in on any of them signs you in on all. Flyer (flyer.bloomalizer.xyz) has no accounts at all. Accounts are handled by Clerk, the authentication provider, which stores your email address and sign-in credentials; Bloomalizer keeps no user database of its own. Deleting your account from the account page removes that data.

The complete list. Through Clerk: your email address, how you sign in, your session. On your Clerk record: one small invite grant (the code's label and an end date) if you redeemed an invite code, written once when you did, and the list of objects you published, if any. With Cloudflare: the files of each object you published, until you delete it. Nothing else: no table of Bloomalizer's own, no other media, no usage profile. Retention is the life of the account; deleting it deletes all of it.

Signing in sets a small number of first-party, strictly-necessary cookies that keep your session — that is what a login is. They identify your session, not your browsing; there are no advertising or cross-site tracking cookies, which is why there is still no consent banner. Don't sign in and the app works all the same.

Videos on the gallery page are hosted on YouTube. Nothing loads from YouTube until you press play on a video; the preview images are served from this site. Pressing play loads YouTube's player (youtube-nocookie.com), and YouTube's own privacy policy applies from there.

A few preferences in local storage — energy slider, chosen INPUT device, last clip FRAME, a redeemed guest code — and anything you choose to save in this browser yourself. None is sent anywhere; clearing your browser data removes them. A clip or picture you LOAD into Hands › Elements is cut into frames and held in memory for that visit only; refreshing the page forgets it. It is never uploaded, and DELETE removes it.

Aggregate page views are measured with Vercel Web Analytics, which is cookieless and builds no profile. The site is hosted on Vercel, which processes standard request data such as your IP address to serve pages, as any host does.

The controller for this data is Alan Kohler (full imprint on the terms page). Questions or a deletion request: hello@bloomalizer.xyz.