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), the guidance written from them, and a reference copy of the public page: its markup with the words replaced by filler, its stylesheets, drawings, pictures and fonts, screenshots, and short films of its animations.
• 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.
• Your copies for Figma. Websites you copy with the extension, with everything in them (see below), are stored privately for your account. Only you can open them, on livery.site and in the Livery plugin in Figma, through links that expire after an hour. They stay until you delete 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, the pages you measured for them and your copies for Figma, 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 does two things: it copies websites into Figma, and it measures pages you can only see when signed in (for example your own app's dashboard) for your kits.

Copying a site for Figma

• When it runs. Only after you click its icon and choose Copy to Figma. For one page, it copies the tab you're on. For a whole site, it opens that site's pages one after another in a tab of its own, up to your plan's limit, then closes it. For a walkthrough, it records the tab you chose until you press Stop or the time limit is reached, then copies each page of that site you visited.
• Permissions. The first time you copy, Chrome asks you to let Livery read websites, so it can open the site's pages and download the pictures, videos and fonts they use, which often live on other servers. Recording a walkthrough uses Chrome's tab capture for that one tab.
• What a copy contains. Everything shown on the pages you copy: their text, images, videos, icons and fonts, the structure and styles of each element, the links between the pages, a full-page screenshot of each, and your walkthrough recording if you made one. What you typed into forms isn't included (fields keep their placeholder), and your cookies, passwords and sign-in details are never sent to Livery. Pages behind a login are copied with your browser's own session; the session itself stays in your browser.
• Where it goes. Straight from your browser to your account's private storage on Livery, until you delete it.

Measuring a page for a kit

• When it runs. Only on the tab you choose, only after you click its icon and press Measure.
• 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.

Either way

• 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 and copies. 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. Copies you open in Figma go from Livery straight into your Figma file; Figma handles them under its own terms. Kits are written from measurements on our own servers; no AI provider receives site data.