Terms of service
Version 1, effective 16 November 2026.
These terms are the contract between you and Bridge. They apply to every plan, including Free. Please read them before you create a team. If anything here is unclear, write to hello@bridgedesignsystem.com.
1. Who we are
Bridge is a service published by Florian Gouloubi, an individual entrepreneur (entrepreneur individuel) established in France.
- SIREN: 947 632 055
- VAT not applicable, article 293 B of the French tax code (Code général des impôts)
- Activity: computer programming (APE 6201Z)
- Address: 26 rue de la Tramontane, 34680 Saint-Georges-d'Orques, France
- Phone: +33 7 45 39 40 27
- Contact: hello@bridgedesignsystem.com
- Publication director: Florian Gouloubi
- Website hosting: Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, United States (see the legal notice)
In these terms, "Bridge", "we" and "us" mean Florian Gouloubi as publisher of the service. "You" means the business or organisation that creates or joins a team, and the people it lets use Bridge on its behalf.
2. Who Bridge is for
Bridge is a professional tool. By creating a team or starting a paid plan, you confirm that you act for the purposes of your trade, business, craft or profession, and not as a consumer. If you sign up on behalf of an organisation, you confirm that you are allowed to bind it to these terms.
3. Accounts and teams
3.1 You sign in with GitHub or with a code sent to your email. Bridge has no passwords. Keep access to your email and GitHub account secure: anything done from your account is treated as done by you.
3.2 A team is the space where your people work on one or more design systems. Each team has at least one admin. Admins invite and remove members, choose roles and manage the plan.
3.3 An "editor" is a team member who can propose or approve changes to a design system. People who only view are not editors. The roles available, and which ones count as editors, are shown in the product and on the pricing page.
3.4 Your design system stays in your own repository. Bridge reads it from GitHub and keeps only short-lived copies, as described in the privacy policy.
3.5 You are responsible for what your team puts into Bridge and for having the rights to it. You must not use Bridge to break the law, to infringe someone else's rights, to attack or overload the service, or to get around plan limits by technical means.
4. Plans and prices
Bridge is free for every team today. Paid plans open in 2027, not before 1 April 2027; we write to every team at least 30 days before, with the final prices. When paid plans open, the plans below apply.
The plans and their planned prices are below. The pricing page shows them too; if the two ever differ, the pricing page at the date of your order applies to that order.
Free
- 0, never billed. A Free team never receives an invoice.
- Up to 3 editors and 1 design system.
- No availability commitment and no support commitment.
Team
- EUR 12 per editor per month billed yearly, or EUR 15 per editor per month billed monthly (USD 14 and USD 17).
- You are billed for at most 10 editors per design system, however many editors you have.
- Up to 3 design systems.
- Written support with a reply within 2 business days.
Organization
- EUR 490 per month (USD 550), billed yearly.
- Paid by invoice, due 30 days from the invoice date.
- 99.5% monthly availability with service credits (section 9).
- Support with a reply within 1 business day, Monday to Friday, 9:00 to 18:00 Paris time, except French public holidays.
VAT is not applicable to these prices (section 6).
5. Billing and payment
5.1 When paid plans open, Team plans are paid by card through Stripe, our payment provider. Bridge never sees or stores your full card number. Organization plans are paid by bank transfer against an invoice, or by card if you prefer.
5.2 When paid plans open, paid plans renew automatically for the same period (one month or one year) unless you stop the renewal before the end of the current period. You can stop it at any time from your team settings or by writing to us.
5.3 Removing editors takes effect at the next renewal.
5.4 Late payment (businesses only, as required by French law). Any amount not paid by its due date automatically bears late-payment interest, without any reminder being needed, at the rate of the European Central Bank's most recent refinancing operation plus 10 percentage points. A fixed compensation of EUR 40 for recovery costs is also due for each late invoice, and further recovery costs may be claimed on proof. No discount is given for early payment.
5.5 If an invoice stays unpaid 15 days after a written reminder, Bridge may move the team to read-only (section 8) until payment. Nothing is deleted.
6. VAT
VAT not applicable, article 293 B of the French tax code (Code général des impôts): Bridge is a French micro-enterprise under the VAT franchise. Prices are the amounts you pay, and every invoice carries this mention.
If Bridge starts charging VAT, we tell you 30 days before and prices stay the same, VAT excluded.
7. Refunds and price changes
When paid plans open, these rules apply to them.
7.1 Monthly plans. When you stop, you keep access until the end of the month you paid for. Months already started are not refunded or prorated.
7.2 Yearly plans. You can ask for a full refund within 30 days after your first yearly payment, and the plan then ends. After those 30 days, if you stop, you keep access until the end of the year you paid for, and the plan does not renew. The 30-day refund applies to the first yearly payment only, not to renewals.
7.3 Price changes. A new price never applies to a period you have already paid. It applies to paying teams only from their next renewal, and we tell admins before that renewal, so you can stop the renewal if you disagree.
7.4 Our price-change promise. If we raise a price and later go back to the previous price, we refund each affected team the difference between what it paid at the higher price since the change and what it would have paid at the previous price over the same period. "Going back" means publishing again, for the same plan, the price that applied before the change.
7.5 Refunds go back to the payment method used, within 14 days of our confirmation.
8. Limits
8.1 When paid plans open and a team goes over a plan limit, for example after moving from a paid plan to Free, or when a payment fails, Bridge never deletes your work. It will, depending on the case:
- put the extra design systems or the team in read-only mode;
- hide features that the current plan does not include; or
- pause actions that would go over the limit.
8.2 Everything comes back as it was when the team goes back under the limit or the payment is made.
8.3 A Free team is never billed. Bridge never moves a team to a paid plan without an admin choosing it.
9. Availability and support
9.1 Free and Team. We work to keep Bridge available and fast, but these plans come with no availability commitment.
9.2 Organization. When paid plans open, Bridge commits to 99.5% availability per calendar month.
- "Availability" means the share of minutes in the month during which the hosted Bridge application at bridgedesignsystem.com responds and lets signed-in members open their team.
- Not counted as unavailability: maintenance announced at least 48 hours in advance; outages of GitHub, Figma or other third-party services Bridge reads from; problems on your side (network, browser, identity provider, repository permissions); force majeure as defined by article 1218 of the French Civil Code; and suspension under section 11.
- If availability falls below 99.5% in a month, the team receives a credit on its next invoice. Credits for a month are capped at one month's fee.
- Ask for the credit in writing within 30 days after the end of the month concerned.
- Credits are the agreed compensation for missed availability. This does not limit your other rights if availability falls so low that the essential purpose of the contract is defeated, including your right to terminate under section 12.3, nor does it limit liability for gross negligence or wilful misconduct.
9.3 Support. Write to hello@bridgedesignsystem.com from an admin's email.
- Free: no support commitment. We read every message and answer when we can.
- Team: a written reply within 2 business days.
- Organization: a reply within 1 business day, Monday to Friday, 9:00 to 18:00 Paris time, except French public holidays.
"Reply" means a first answer from a person, not necessarily a fix.
10. Founding teams
10.1 Who. A founding team is any team created on Bridge up to and including 31 March 2027.
10.2 What they keep. For as long as this commitment lasts (section 10.4), a founding team keeps, at no charge:
- everything it can do on the day paid plans open; and
- everything the Free plan gains after that day.
No price change made after that day applies to a founding team for what it keeps under this section.
10.3 Support and availability. Founding teams receive the support and availability of the Free plan. If a founding team chooses a paid plan, that plan's terms apply to it for as long as it pays, and it returns to its founding rights when it stops.
10.4 Duration and the only way it ends. This commitment is made for an indefinite period. The founding team may leave at any time. Bridge may end it only in these cases:
- (a) Bridge stops operating the hosted service for all teams. Bridge then gives every founding team at least six months' written notice to the admins' email, and during that notice provides a complete export of the team's Bridge data in a format that can be loaded into a self-hosted Bridge, together with the self-hosting rights in section 14, with no limit on editors, design systems or duration.
- (b) The founding team seriously breaches section 3.5 and does not remedy it within 30 days after written notice, or the breach endangers the service or other users.
Bridge will not end this commitment for any other reason, including to move founding teams to a paid plan.
10.5 If Bridge changes hands. If the Bridge service, or the business that runs it, is sold, contributed or otherwise transferred, Bridge will transfer the contracts with founding teams together with the service, and will require the acquirer to take over this section 10 in full. Each founding team agrees now, in advance, to that transfer of its contract, which will take effect for it once it has been notified. Bridge guarantees (se porte fort) that the acquirer will honour this section; if the acquirer does not, Bridge remains liable for the consequences. No transfer of the service may be made in a way that removes these rights.
10.6 Changes to these terms (section 16) cannot reduce the rights in this section 10 for an existing founding team without that team's written agreement.
11. Suspension
Bridge may suspend all or part of a team's access, without notice where the urgency requires it, if:
- the account is being used to attack, overload or compromise the service or other users;
- the account appears compromised;
- a payment is more than 15 days late after a written reminder (in that case the team goes to read-only, as in section 8); or
- a court or authority requires it.
We tell the admins why, unless the law prevents us, and we lift the suspension as soon as the reason has gone. Suspension never deletes your work.
12. Termination and export
12.1 By you. You can stop a paid plan at any time; it ends at the end of the paid period (section 7). You can delete your account or your team at any time from Account settings. Deleting an account is described in the privacy policy.
12.2 By Bridge, for breach. If you seriously breach these terms, Bridge may terminate your team's contract after written notice giving you 30 days to remedy the breach, unless the breach cannot be remedied.
12.3 By you, for our breach. If Bridge seriously breaches these terms, including missing the Organization availability commitment in three months out of any six, you may terminate with immediate effect by writing to us, and we refund the fees paid for the unused part of the period.
12.4 If Bridge stops the hosted service. Bridge will give paying teams advance notice and refund the fees paid for any period after the end date. Founding teams receive the notice and export in section 10.4.
12.5 Your data at the end. Your design system is in your own repository and stays there. Until the end date, and for 30 days after it, admins can export the team's Bridge data. After that, we delete it, subject to the backup and retention periods in the privacy policy.
13. Data
How Bridge handles personal data, where it is stored, for how long, and which providers process it is described in the privacy policy. In short, at the date of these terms: the account database is hosted by Upstash (Redis) in Frankfurt, Germany; a daily backup is stored with Vercel Blob in Paris, France, and kept 30 days; Resend sends sign-in codes and invites; Brevo sends work emails; GitHub is where your design system lives and where Bridge reads it from; and Stripe processes payments for paid plans.
14. Licences and self-hosting
14.1 Bridge's components and design tokens are licensed under the MIT licence.
14.2 The rest of Bridge's source code is licensed under the Functional Source License, version 1.1, with MIT as the future licence (FSL-1.1-MIT). Each released version becomes available under the MIT licence two years after its release.
14.3 You may self-host Bridge for your own use, with no limit on editors, design systems or duration, under the licence terms in 14.1 and 14.2. The hosted plans in these terms only govern the service Bridge runs at bridgedesignsystem.com.
14.4 You keep all rights in your design system, your code and your content. You give Bridge only the rights it needs to run the service for you: to read, process, display and send them as you instruct. Bridge claims no ownership of them.
14.5 The names "Bridge" and the Bridge logo are not licensed by these terms.
15. Liability
15.1 Bridge is liable for direct damage caused by its breach of these terms, within the following limits.
15.2 For each team, Bridge's total liability over any twelve-month period is limited to the amounts that team paid Bridge in the twelve months before the event giving rise to the claim.
15.3 Bridge is not liable for indirect losses, such as loss of profit, revenue, business or goodwill, or for losses caused by third-party services Bridge reads from or relies on (such as GitHub), by your own systems, or by force majeure (article 1218 of the French Civil Code).
15.4 None of these limits apply to damage caused by gross negligence (faute lourde) or wilful misconduct (faute dolosive), to bodily injury, or to any liability that cannot be limited by law. Nothing in these terms deprives Bridge's essential obligations of their substance.
15.5 Your design system lives in your repository. You remain responsible for your repository, its backups and the changes your team approves.
16. Changes to these terms
16.1 We may update these terms, for example when the product or the law changes.
16.2 For paying teams, a new version applies from their next renewal. We email admins before it applies. If you disagree, stop the renewal and your current terms apply until the end of the paid period.
16.4 Changes required by law, or that only make the terms more favourable to you, may apply sooner.
16.5 No update can reduce the rights of an existing founding team under section 10 without its written agreement (section 10.6).
17. General
17.1 These terms, the pricing page at the date of your order, the privacy policy and, where relevant, the data processing terms and any signed order form for an Organization plan, form the whole agreement. If they conflict, a signed order form prevails, then these terms.
17.2 Your own purchasing terms do not apply unless Bridge agrees to them in writing.
17.3 If a clause is held invalid, the rest of the terms still apply.
17.4 You may transfer your contract to another entity only with our written agreement, which we will not refuse without good reason. Bridge may transfer these terms only under section 10.5 or together with the whole service, and only to an acquirer who takes them over.
17.5 These terms are written in English.
18. Governing law and courts
18.1 These terms are governed by French law.
18.2 Before going to court, we both agree to try to settle any dispute amicably for 30 days after one of us writes to the other.
19. Contact
Bridge, Florian Gouloubi, entrepreneur individuel
26 rue de la Tramontane, 34680 Saint-Georges-d'Orques, France
hello@bridgedesignsystem.com