Privacy Policy

Privacy Policy: The Parent Data Firewall

Your child's fit data is not inventory. Smart Wizard measurements stay local unless you deliberately choose account features.

BalanceBikeToddler handles sizing data like a volatile sample: use it for the current measurement, keep the minimum needed, and never sell it to the advertising machine.

01 / Smart Wizard

Height, inseam, and fit math burn locally

The Smart Wizard on the Guides page may ask for child height, age, weight, inseam-like fit clues, and riding context. Those calculations are performed in the browser to return sizing guidance and category suggestions.

We do not package, sell, or broker children's biomechanical data. The point is to help the parent choose a safer product, not to build a child-profile commodity.

02 / Local drafts

Browsing history and comparisons begin in your browser

Recent views, comparison drafts, and unauthenticated shortlist behavior are stored in local browser storage so the site can feel useful without forcing a login. Clear the browser storage and those drafts disappear.

When a user signs in, account features may support bookmarks, saved reports, and admin access. We keep that scope narrow and tied to site utility.

03 / No ad marketplace

We do not sell parent attention as a product

BalanceBikeToddler avoids advertising trackers and does not sell personal data. We use privacy-sensitive analytics and operational logs only to keep the site stable, detect abuse, and understand which safety resources actually help families.

Analytics runs in Google's Consent Mode. Until you agree, the tag is loaded with analytics storage denied: it sets no analytics cookie and builds no identifier, though Google still receives a cookieless ping so we can count the visit. Agreeing switches analytics storage on and gives us full page and event data; declining leaves it denied, and the ping stays cookieless.

If we ever expand data use, the rule remains simple: explain it plainly, keep it proportional, and never turn a child's measurements into a growth-hacking asset.

04 / Accounts and sign-in

What an account stores, and who else sees it

Accounts run on Firebase Authentication, a Google service. Registering with an email address and a password means that address and a hashed version of the password are kept by Firebase; the password itself never reaches us. You can also sign in with Google, and on that path Google is the third party identity provider — once you approve, it shares your name, email address and profile picture with us.

Before an email account is created we send a six-digit verification code to the address you entered, delivered by Resend, the service that delivers our mail. The code expires after five minutes, and what we keep is a hash of it, not the code.

Bookmarks, the saved child fit profile, view history and comparison drafts stay in your own browser's local storage. They are not written to our cloud database, and clearing browser storage deletes them.

Use the review center to see how privacy-light research, safety evidence, and product verdicts connect without selling child-fit data.

Move from local sizing logic into the product hub when you are ready to compare safer candidates.