What Bridge keeps about you

As little as it can: enough to sign you in and know which teams you belong to. Your design system never leaves your repository.

What Bridge keeps

Your account email and the name you gave.
Your GitHub login, when you link GitHub.
The teams you belong to, and your role on each.
A team you create in Bridge: its name, the email of the person who created it, when, and later the Storybook address or the repository connected to it.
Invitations waiting for you or sent by you.
Your requests to join a team: your name and email, shown to that team's admins, for 14 days at most.
For teams an admin opened to their work domain: that domain and who opened it. Colleagues with an email at that domain who are not on the team see exactly this: the team's name, how many people are on it, the admin's name, and the first names of up to 4 members (with the initial of their last name) on small avatars. Never anyone's email, and never the team's repository. Public mailboxes like Gmail or Outlook never match.
For an invite link: after the invite is used or expires, the team's name and who invited, for 30 more days, so the link can say whom to ask for a new one. Never the invited email.
Which changes you sent through Bridge with your email (no GitHub), so your home shows your own work: for a year. On a private repository, the change also says who asked, with your name and email.
Short-lived copies of what Bridge reads from your team's repository on GitHub, so pages open fast: minutes for most answers, 7 days at most for file contents. Your browser tab keeps its own for seconds to minutes, and forgets them when you sign out.
The public GitHub name and picture of the people on your team's changes, for a day, so members without GitHub see names. Nothing else from their profile.
The one-time sign-in codes, hashed, for 10 minutes.
If you joined with your email: what happened to your own work that Bridge emails you about (a question for you, something ready for your look, what shipped), as a title, a name and a link, never the comment itself. Kept until your daily summary goes out, 30 days at most. Also your email choices (Account settings, Email) and your time zone, so the summary comes at 9:00 where you are. Every email has a link to stop them in one click.
When you connect your own AI assistant to a team: your GitHub sign-in for that connection, encrypted, until you remove it or 90 days after its last use.
When you sign in to the Figma plugin with Bridge: your GitHub sign-in, for 5 minutes at most, until the plugin collects it.

What Bridge never keeps

Passwords: there are none. You sign in with GitHub or a code sent to your email.
Your GitHub sign-in in Studio: it stays in your browser.
A lasting copy of your design system: it stays in your repository. Bridge reads it on GitHub when you open it, and keeps only the short-lived copies above.

Where and for how long

Your account lives in an Upstash Redis database in Frankfurt, Germany, with a daily backup in Vercel Blob in Paris, France. Bridge keeps it until you delete your account. Backups are kept 30 days, then removed.

Sign-in codes and invites are sent by Resend. The emails about your work are sent by Brevo, in the European Union: it receives your email address and the text of each email, nothing else.

How to delete it

In Studio, open the menu with your name, choose Account settings, then Delete my account. Bridge removes your account, your email memberships, your join requests and your sessions at once. If you are the only admin of a team with other members, make someone else an admin first: Bridge tells you before you confirm, and offers to do it there. A team you created and were alone on goes with your account.

The changes you sent stay in your team's history, signed "A former member": Bridge forgets which ones were yours and removes your name and email from the line that says who asked. The commits saved for you stay in your team's repository as git recorded them (on a public repository, never with your email).