Privacy policy

Brickmaster collects only what it needs to run your collection: an email address to sign you in, and the collection data you enter. There are no analytics or third-party tracking SDKs in the app, no display ads, and your personal data is never sold or shared with third-party advertisers.

What we collect

• Account.Your email address. Sign-in is passwordless: a one-time code sent to your email, Sign in with Apple, or Sign in with Google. We never store a password. If you use Apple or Google, we receive the identifier (and email) that provider shares. We don't ask for your name or a photo.
• Your collection. The data you enter to manage your bricks: the sets and minifigures you want, own, or have built and their statuses, notes, prices paid, and build timing. This data belongs to your household (see below).

Households

Collection data is scoped to a household. If you join or create a shared household, its members can see the household's collection data. A household owner adds a member by email address, which is used only to find the matching account.

Camera

The CMF box scanner uses your device camera to read the code printed on sealed Collectible Minifigure boxes. This happens live and entirely on your device. No photos or video are uploaded or stored, and the camera is only active while the scanner is open. If you help identify a box the scanner doesn't recognize yet, the box code and the figure you match it to are saved to improve scanning for everyone.

Where your data lives

Your account and collection data are stored with Supabase (database and authentication, hosted in the United States). The website is served by Vercel, our API runs on Render, and set catalog and alternate-build requests pass through a Cloudflare edge cache. The public set catalog comes from third-party catalog data sources; none of your personal data is ever sent to those sources or the AI tooling we use to maintain the catalog. If you explicitly request the one-time launch notice described below, Resend processes that email address and delivers the confirmation and launch messages.

On your device

The app keeps your session tokens and preferences (theme, view mode, selected household) in local storage on your device. We don't set tracking cookies.

Email

We send transactional email for sign-in codes, sign-in links, and invitations. If the TestFlight beta is full, you may separately opt in to one general-availability notice. We use double opt-in: the address is not added to the launch segment until you confirm within 48 hours. The purpose is limited to one message containing both public store links, not a newsletter or beta invitation. Resend manages delivery, suppression, and unsubscribe. We do not use open or click tracking for this list. Thirty days after launch, we remove the temporary segment and delete contacts that have no other separately consented purpose.

Shareable Moments

If you deliberately create a Shareable Moment, Brickmaster makes an immutable public snapshot available to anyone with its unguessable link. The snapshot contains only the selected set or loose-minifigure identity and catalog image, a light/dark card choice, and—when you share a completed build—the truthful dates, piece count, and timing facts recorded for that build. It never includes your email, household or collection name, account or inventory identifiers, price paid, seller, acquisition source, notes, or item location. Figures inferred from sets, private custom sets, and MOCs cannot be shared in this version.

Share pages are public but excluded from search indexing. Social and messaging services may fetch and cache their preview image. A Shareable Moment is a frozen snapshot, so ordinary later catalog or collection edits do not rewrite it. Brickmaster automatically makes its link unavailable when an action explicitly corrects or invalidates its underlying facts (for example, editing or deleting a mistaken build completion), when its creator loses access to the collection or deletes their account, or when Brickmaster must remove it for an emergency safety or legal reason. Brickmaster then stops serving the snapshot after its short cache window, but cannot recall screenshots, downloaded cards, posts, messages, or copies already retained by another service or person.

Affiliate purchase links

Wanted-set pages and eligible public Shareable Moment pages may include links to retailers. A link is labelled and disclosed beside the destination when it carries paid attribution; otherwise it remains an ordinary retailer link. Brickmaster may earn commissions from purchases through paid links. As an Amazon Associate I earn from qualifying purchases. Clicking one takes you to the retailer in your browser. The retailer or its affiliate network receives the outbound request and may use cookies or similar technologies under its own privacy policy to attribute a purchase. Brickmaster does not put your user, household, or share identifier in an affiliate link and does not receive your retailer account, cart, or payment information.

AI connections

If you deliberately connect Brickmaster to an MCP-compatible AI app, you choose which collections that connection may read. Brickmaster sends the selected service only the inputs and bounded results for collection tools used in your AI conversation. Those results can include safe catalog identifiers and images, item and build states, aggregate collection statistics, theme progress, minifigure progress, and build timing. They exclude your email address, household members, prices paid, seller or acquisition source, private notes, authentication credentials, and internal database fields. The first connector release is read-only.

Your AI provider processes those tool inputs and results under its own terms, retention, and training policies; Brickmaster cannot apply its own retention policy to a copy the provider receives. Settings → AI connections lets you change selected collections or disconnect. Brickmaster stores the client's display metadata and the collection grants, but not the AI conversation, tool arguments or results, or OAuth access and refresh credentials. Operational logs contain only non-reversible identifiers, tool name, timing, status, and result count.

Deleting your account

Settings → Delete account removes your sign-in record immediately. If you are the only member of your household, all of its collection data is deleted with it. If you belong to a shared household, you are removed from it (ownership passes to another member if needed) and the household's shared data remains for its other members. Links to any public snapshots you created stop working before your account is removed. You can also email us to request deletion.

Children

Brickmaster is not directed at children under 13.

Changes

If this policy changes, the new version will be posted here with an updated effective date.

Questions about privacy? Use our contact form.