Privacy policy
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.
- Onbrand stores your email address, name, profile picture link, when you joined and when you last signed in, so it can show you your design systems and email you about them.
- Your browser gets a sign-in cookie that lasts 30 days. It holds your account's identifier, an expiry date and a signature.
- Onbrand emails you only about your account: a welcome email, a note when a design system goes live, and (later) changes that need your review. The emails are sent through Resend, which handles your address only to deliver them.
- To delete your account and everything in it, email the address at the bottom of this page.
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 does not store your email address, name or Google account identifier. They are checked and discarded.
- If you're allowed in, your browser gets a cookie for that one page. It holds an expiry date and a signature, not your email or any other personal data. It lasts 30 days, or until the page's owner changes who can see the page.
- If you're not allowed in, Onbrand shows you the email address you used so you can pick another account, and stores nothing.
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
- Page view counts. Onbrand counts how many times each design system page is opened per day, so its owner can see it in the dashboard. Only the number is kept: not who opened it, nor their IP address.
- No analytics services, no ads, no tracking cookies. The home page keeps one value in your browser's local storage so its intro animation plays only once.
- Server logs and abuse limits. Like any web server, the hosting platform (Railway) logs requests, including IP addresses, to run and secure the service. Onbrand keeps IP addresses in memory for a few minutes to limit repeated sign-in and publish attempts.
- Third-party files. The home page loads fonts from Google Fonts and animation scripts from cdnjs (Cloudflare), so those services see your IP address when you visit it. Design system pages may load the fonts their owners chose.
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.