Privacy

Building public kits never needs an account. Livery collects as little as it can, and never sells data.

What we store

• Kits. The addresses people ask for and the kits built from them are public, in the library. Kits contain measurements of a design (colours, type, spacing, shapes, motion), never a site's text, images or code.
• Counts. Views, likes and downloads of each kit. To count each person once without accounts, we keep a random id in a first-party cookie and a one-way hash of your IP address and browser name. Raw IP addresses are never stored.
• Rate limits. A one-way hash of your IP address and a counter, kept for a day.
• Takedown requests. The email address and message you send, kept to handle the request.
• Your theme choice and taste collection. Kept in your browser only.

If you create an account

• Your account. Your email address, name and, if you sign in with Google or GitHub, the profile picture they share. Passwords are stored by our authentication provider as salted hashes; we never see them.
• Your kits and saved kits. Kits you build while signed in are linked to you. Private kits are visible only to you until you publish them.
• Email. We send only account emails (confirming your address, resetting your password).
• Deleting it. Use Delete account at the bottom of your account page. It removes your account, your private kits and the pages you measured for them, straight away. Kits you published stay in the library, no longer linked to you. If you can't sign in, email privacy@livery.site from your account's address.

The Livery browser extension

The extension lets you add pages you can only see when signed in (for example your own app's dashboard) to your kits.

• When it runs. Only on the tab you choose, only after you click its icon and press Measure. It has no access to any other tab or site, runs nothing in the background, and keeps no browsing history.
• What it reads. The page's design: colours, fonts, sizes, spacing, corner shapes, shadows, layout, its animations (timings and keyframes, with any text in them removed) and small craft details such as blur or sticky elements, and the names and versions of the libraries the page is built with (for example React or Three.js), read from the page's code. It reads nothing else from the page's scripts. The page's copy is turned into a few numbers inside your browser (average sentence length, how often headings use Title Case, whether the text says “you”), and the text itself is discarded there.
• What it sends. Those measurements and one picture of the page with all text replaced by bars and all images replaced by flat blocks, only after you have seen them and pressed Send. It never sends text, images, form contents, cookies, passwords or sign-in details.
• Where it goes. To your Livery account, as a private kit only you can see, until you choose to publish it.
• Connecting. The extension stores one token in your browser to act for your account. You can disconnect it from the extension or from My kits at any time.

Data the extension collects is used only to build your kits. It is not sold, not used for advertising, not shared with third parties beyond the processors below, and not used to determine creditworthiness or for lending.

What we don't do

No advertising, no tracking pixels, no selling of data. To see which pages are visited, Livery uses Vercel Web Analytics: it counts page views without cookies and without identifying you, and reports only totals. Pages that LiveryBot renders load without their analytics and ad scripts.

Processors

Livery runs on Vercel (hosting and cookieless page-view counts), Supabase (database, storage and authentication), Browserless (the browser that reads public sites) and Resend (account emails). Google and GitHub are used only if you choose to sign in with them. Kits are written from measurements on our own servers; no AI provider receives site data.