Privacy Policy
Last updated: November 9, 2026
This policy explains what BuildMyMTB does (and does not do) with your information. It is written to match how the site actually works, not from a generic template.
BuildMyMTB (the “Site”, “we”, “us”) is a free tool for picking mountain-bike parts and checking whether they fit together, with a running price and weight. It is operated by D-Dubs Works LLC. You can reach us at Doug@buildmymtb.com.
The short version. You can use the whole Site without an account, and if you do, nothing that identifies you is sent to us. For page views, the only analytics we use is cookie-less, aggregate counting (Cloudflare Web Analytics) that cannot identify or follow you. We also count how often each feature is used, as daily totals that identify no one, to improve the site. The home page also carries the tracking tag of Impact, an affiliate network (see sections 5 and 6). Apart from that tag, we use no advertising and no cross-site tracking. The only data we store about you is what you actively create if you choose to sign in: your login email, the builds you save, your parts inventory, and anything you post in the forum. You can delete it at any time.
1. Using the Site without an account
The builder runs entirely in your browser from a built-in catalog. If you never sign in:
- No account is created and no personal information is sent to us.
- We also count how often each feature is used, as daily totals that identify no one, to improve the site.
- Your in-progress build lives only in your browser. A share link encodes the build inside the URL itself (client-side), and it is not saved on any server of ours. Anyone you send that link to can open the same build.
- We store two small functional preferences in your browser’s local
storage so the Site remembers how you like it:
tb-theme(light or dark mode) andtb-view(card or list layout). These never leave your device and are not used to identify or track you.
2. If you create an account (optional)
Accounts are optional and exist so you can save builds and track the parts you own. Sign-in is handled by Supabase (our authentication and database provider) using either:
- a one-time “magic link” sent to your email address, or
- Sign in with Google, in which case Google shares your basic profile and email with our authentication provider so an account can be created.
When you have an account, we store:
- Your email address, used to identify your account, to send the sign-in link, and to send you a safety notice if a product recall we have recorded names a part in your garage. Those notices are their own separate channel: it is on by default, we send nothing else on it (no newsletter, no promotions, no product news) and you can leave it at any time from your garage. Leaving it means you may not hear from us about a recall affecting a part you own, so we say so plainly at the point you turn it off. We only know about recalls we have found and recorded, so not hearing from us is never an all-clear.
- Saved builds (“Garage”): the parts in a build, plus a name and a status you set.
- Your parts inventory (“Inventory”): the catalog parts you mark as owned, and a quantity. You can also add a frame serial number to a bike in your inventory. It is visible only to you, and it is printed on your build sheet only if you tick the box to include it.
- Forum posts: any threads or replies you write (see below).
Every one of these rows is tied to your account and is protected by database Row-Level Security, so only you can read or change your builds and inventory. Your account identifier is never sent from your browser. The database assigns it from your logged-in session.
3. The community forum
If the forum is enabled, threads and replies you post are stored by Supabase and tied to your account. Forum posts are public: anyone visiting the Site, signed in or not, can read them, so please don’t include anything private in a post. Only you (via your logged-in session) can edit or delete your own posts.
4. Reporting a wrong result or a bug
If you use the “report a wrong verdict” feature, you can either copy the report to your own clipboard, or open a GitHub issue. Choosing the GitHub option takes you to GitHub, where the report (the build details and any notes you add) becomes part of a public issue on our repository. What is submitted is shown to you first, and GitHub’s own privacy terms apply once you are on their site.
5. Analytics, cookies and tracking
We deliberately built the Site to be privacy-friendly:
- Cookie-less, aggregate analytics only. We use Cloudflare Web Analytics to count page views. It sets no cookies, stores nothing on your device, and does not fingerprint or identify individual visitors. We see aggregate numbers (pages viewed, referrer, country, browser type), never a profile of you. No Google Analytics, no Segment, and no other ad-tech analytics apart from Impact’s tag below.
- No advertising or cross-site tracking, no tracking pixels, and no data brokers, with the one exception in the next point.
- Impact’s affiliate tracking tag, on the home page only. Impact is the
affiliate network we use; today our Competitive Cyclist, Jenson USA and Backcountry links go through it. Its tag loads on the home page
and is used to credit purchases made through our affiliate links. It counts views of the page
and may change links to brands in Impact’s network into its own tracking links. Impact says data
captured through the tag may be shared with the advertisers in its network. The
Count my visits switch below does not turn it off; the Cookie settings link
at the foot of every page does. Switch off “Allow the affiliate tracking cookie” there and, in this
browser, the tag stops and no longer loads, the Impact cookies the page can reach are cleared, and the shop links go
straight to the shop’s own page with no tracking of ours (a link that has no such untracked page is
removed). The choice is saved on this device.
Impact’s documentation says
the tag sets a first-party cookie,
IR_MPI, that lasts five years and helps Impact recognize the same browser across visits. - No tracking cookies of our own. The Site does not set cookies to follow you; Impact’s cookie above is the one exception, on the home page. Besides sign-in and the preferences above, the only other things we store are your Cookie settings choice and a few on-device settings such as currency.
— On
Turning this off stops the visit count, the daily feature counts and the Amazon button count for this browser only; the choice is saved on this device.
Apart from Impact’s tag described above, the only storage we use is functional (needed to make the Site work as you asked). As with any website, our hosting provider (see below) processes standard technical request data, such as your IP address, in its server logs to deliver the pages and guard against abuse; we do not build profiles from this.
6. Third-party processors
We keep the moving parts to a minimum. The services that may process your data are:
- Supabase (Supabase, Inc.): authentication and the database that stores your account email, saved builds, inventory, and forum posts. See Supabase’s privacy policy.
- Google (Google LLC): if you choose “Sign in with Google”, Google shares your basic profile and email with our authentication provider so an account can be created. See Google’s privacy policy.
- Resend (Plus Five Five, Inc.) delivers the email we send you: the sign-in link, and any safety notice described in section 2. It processes your email address to deliver those messages. We do not keep a mailing list with them. See Resend’s privacy policy.
- GitHub (GitHub, Inc., a Microsoft company) hosts the Site’s source repository, and receives any bug report you choose to file as an issue. See GitHub’s privacy statement.
- Cloudflare (Cloudflare, Inc.) serves the Site (Cloudflare Pages; as host, processes standard request logs), provides the cookie-less web analytics described in section 5 (aggregate page-view metrics; no cookies, no fingerprinting, no cross-site tracking) and our domain’s DNS/email routing. See Cloudflare’s privacy policy.
- Impact (impact.com), an affiliate network: its tracking tag on the home page, described in section 5, may set a cookie and is used to credit purchases made through our affiliate links. Impact says data captured through the tag may be shared with its advertisers. See Impact’s privacy policy.
We do not sell your data, and, apart from what Impact’s tag collects (described above), we do not share it for advertising. These services are based in the United States, so if you use the Site from elsewhere your data may be processed there.
7. Retailer and affiliate links
Some parts link to Amazon, to Competitive Cyclist, to Jenson USA or to Backcountry, and those links are affiliate links; the links to Competitive Cyclist, Jenson USA and Backcountry go through the Impact network. Links to other retailers, if we add any, may be affiliate links too. When you click one you leave BuildMyMTB and go to the retailer’s own site, which has its own privacy practices; Amazon, for one, may set its own cookies when you follow a link. See our Affiliate Disclosure for how this works and why it never affects the compatibility results.
We count how many times the Amazon button is clicked, as a daily total for each builder page. The count uses no cookie and no identifier, records nothing about you or the part, and stops when Count my visits is off.
8. How long we keep data, and your rights
We keep your account data until you delete it or ask us to. You can:
- Delete individual builds and inventory items yourself, in the app.
- Delete or edit your own forum posts yourself.
- Delete your whole account and everything tied to it: email us at Doug@buildmymtb.com and we’ll remove it.
- Ask what we hold about you, or ask for a copy: email the same address.
Depending on where you live, you may have additional rights (such as access, correction, deletion, or objection) under laws like the GDPR or the CCPA. We’ll honor those requests; just contact us.
9. Children
The Site is not directed to children under 13, and we do not knowingly collect information from them. If you believe a child has created an account, contact us and we will delete it.
10. Security
Account data is owner-scoped at the database level by Row-Level Security, and sign-in uses a modern authentication flow. No method of transmission or storage is ever 100% secure, so we can’t guarantee absolute security, but we keep the surface area small on purpose.
11. Changes to this policy
If we change how we handle data, we’ll update this page and change the “last updated” date above. Material changes will be made clear on the Site.
12. Contact
Questions about privacy? Email Doug@buildmymtb.com (D-Dubs Works LLC).