Onbrand

Privacy policy

Last updated 17 October 2026

Onbrand turns a frontend's code into a hosted design system page at sites.onbrand.tools/<name>/. It is run by Lamine Cheloufi. This page explains what data the hosted service handles and why. It is short because the service collects very little.

Your Onbrand account

To use the Onbrand dashboard, you sign in with Google. For this, Onbrand asks Google for the openid, email and profile permissions: your email address, whether Google has verified it, your name and your profile picture. It does not ask for, and cannot see, your Google password, contacts, files, calendar or anything else in your account.

Signing in to a private page

A team can make its design system page visible only to people at its own email domain. When you open such a page, you can sign in with Google. Onbrand asks Google only for the openid and email permissions, which tell it your email address, whether Google has verified it, and an account identifier. It does not ask for, and cannot see, your Google password, contacts, files, calendar or anything else in your account.

Onbrand uses that information for one thing: to check that your email address belongs to a domain the page's owner allowed. Then:

Onbrand's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is not sold, not shared with anyone, not used for ads, and not used to train AI models.

Password-protected pages

If a page uses a shared password, the password you type is checked against a stored hash and not kept. You get the same kind of page cookie as above.

Publishing a design system

When a team publishes, Onbrand stores what it needs to host the page: the colors, type, icons, components and other design files read from their code, a hash of their publish key, a short hash of the invite code they used, and the change history. If the team's workflow passes it along, each change records the name of the commit author, which is shown in the page's changelog. Teams can delete their page and all of this data at any time with npx onbrand unpublish.

Everything else

Your choices and rights

You can stop a page's sign-in at any time by clearing its cookie, and remove Onbrand's access in your Google account settings. Onbrand doesn't store the email addresses of people who sign in to a private page, so unless you have an Onbrand account there is usually nothing about you to delete. If you want to ask what data relates to you, have it corrected or deleted, or have any other question, email lamine@cheloufi.de.

Changes

If this policy changes, the new version will be posted here with a new date.