Privacy

m0saic.io uses Vercel Analytics — cookieless and anonymized. We see aggregate pageviews and which buttons get clicked (e.g. “opened the editor”); events carry no personal data. No ad trackers, no fingerprinting, no consent banner needed.

Billing runs entirely through Stripe — we never see your card details. We keep your email to deliver and support your license key.

Rendering is local-first: your media, layouts, and outputs stay on your machine. Rendering never requires an account and never phones home to work.

The CLI and the desktop app keep a render history and usage counts on your machine and, in the default Standard mode, send anonymous, aggregated stats to m0saic.io: one day summary per UTC day plus a today-so-far update. That is counts and histograms only — renders by outcome, a duration histogram, which features and CLI commands were used and how often, which built-in templates were opened (by catalog id; community and third-party templates are counted, never named), coarse OS and architecture, major.minor versions — and install/update events. The install event also says which product it came from, whether the command line was run through npx or from an installed copy, and, only if you typed --from with a word, that word. The only identifier is a random install id — never file paths or names, template code or props, media, ffmpeg arguments, error messages, or anything personal. Error reports are off unless you turn them on.

Nothing you author leaves. Creating a Layout share link adds one to a share count; the layout string, canvas size and shape stay on your machine.

One notice is sent regardless of the telemetry mode: when you activate a license key, the CLI or the desktop app tells m0saic.io the key’s issuance id, whether it was accepted, expired or revoked, which of the two did it, and the app’s major.minor version — never the key itself, your email, your install id or anything about your machine. It is one request, never retried, and stored by day only. It is never combined with the install id: the key id is looked up against the issuance ledger by hand, and that is how we see that a key we issued is in use and notice a key that is being shared.

The desktop app fetches the public community template library and the Community M from GitHub — on by default, checked shortly after launch and then every few hours, each release signature-verified before a byte of it loads. GitHub sees an ordinary download from your address; nothing about you is sent. A community-updates.json file with { "enabled": false } in your m0saic folder turns it off. The Community page on this site loads the live M from GitHub in your browser the same way.

Mosaic Desktop also checks for a newer version of itself: once a day it fetches a small version file from the m0saic releases page on GitHub and shows a banner if there is one — it never downloads or installs anything on its own. That request carries nothing about you. M0SAIC_NO_UPDATE_CHECK=1 turns it off.

The browser app at app.m0saic.io sends the same kind of usage counts (pages and features used, built-in templates opened, and how many Layout share links were created — never the layouts themselves) and stores no identifier in your browser. The server keeps a per-day hash of your address and browser string with a key that rotates daily, and never the address itself, so counts cannot be linked across days. Global Privacy Control and Do Not Track turn it off.

See exactly what leaves your machine with m0saic telemetry preview or the Telemetry page in the app. Opt out at any time: m0saic telemetry set-mode local-only keeps history on your machine and sends nothing, ghost records nothing at all, and M0SAIC_TELEMETRY=ghost or DO_NOT_TRACK=1 are honored for usage telemetry (the activation notice above is the one thing they do not cover).

We don’t sell data, don’t run third-party ad trackers, and don’t link your renders to your identity.

Want anything we hold about you (there isn’t much) accessed or deleted? Email privacy@m0saic.io.