Brickguess Privacy Policy
Last updated: April 30, 2026. How KroWVeBricks handles information when you use the Brickguess web application at brickguess.com.
Images You Upload
When you upload a photo for minifigure identification, we strip EXIF metadata (GPS, device IDs, timestamps) before any further handling, then run AI detection and identification against the cleaned image. Most uploads are processed and discarded; the only exception is the public scan pool described below.
Public Scan Pool (Hero Card and Top Figs)
Brickguess shows a "Just Identified" hero card on the homepage and a Top Figs page ranked by community scan frequency. Two separate stores power these:
- Anonymous per-fig counters. Every identified minifigure (>=75% confidence) increments a counter for that fig ID. Counters are pure aggregates with no link to your IP, session, or upload, and exist indefinitely.
- Recent qualifying scans. A scan only enters the public hero rotation when it identifies >=2 figures at >=75% confidence, totals >=$50 in estimated value, and you have given the appropriate share consent for your region. The 100 most recent qualifying scans are kept in a rolling list.
- Hero crops. Only the single most recent hero scan has its cropped fig images kept on disk. As soon as a newer $50+ scan replaces it, the previous hero's crops are deleted automatically.
We never store the original full-resolution lot photo on disk and never link a public scan record to your IP, session, or any identifying signal.
Cookie Consent
On first visit, Brickguess shows a single cookie banner with Accept and Decline. The site works either way — there is no wall and no second prompt.
- Accept: we load advertising cookies (Google AdSense) and your scans may be added to the public community library shown on the homepage hero, /top-figs, and per-fig pages — de-identified from you, your IP, or your session.
- Decline: no advertising cookies are set, no public-pool participation. Your scans are processed for your own identification only and discarded.
Your decision is stored in your browser's localStorage so we don't ask repeatedly. Clear your browser data to reset.
No User Accounts
Brickguess does not require accounts, logins, or personal information.
Cookies and Local Storage
Local storage holds your cookie consent preference, your share-consent decision (GDPR users), and your last 10 scan results so you can revisit them locally. None of this is sent to our servers. If you accept non-essential cookies, Google AdSense may set advertising cookies; if you reject, none are set and ad placeholders appear instead.
Third-Party Services and Affiliate Disclosure
Affiliate disclosure: Brickguess is a participant in the eBay Partner Network. Click-throughs to eBay from buttons or search links on this site that result in a purchase may earn us a small commission at no additional cost to you. This commission helps keep Brickguess free.
Other third-party services we integrate with: Brickognize (cropped fig images sent for identification, no user-identifying data); BrickLink API (fig IDs only, no user data); Google AdSense (loads only after explicit cookie consent); Cloudflare (edge proxy + country signal for the GDPR geofence).
Operational Logs
Short-term logs include request IPs for rate limiting and abuse detection, purged after 24 hours and never joined to public scan records.
Data Retention Summary
- Original uploaded photos — discarded after processing.
- Per-fig training crops — retained indefinitely in anonymous per-fig folders for AI model improvement; not linked to your IP, session, or any identifier.
- Hero crops — only the current $50+ hero scan; replaced on next qualifying scan.
- Public scan list — 100 most recent qualifying scans (rolling).
- Anonymous per-fig counters — retained indefinitely (no per-user attribution).
- Operational logs with IP — 24 hours.
- Cookie / share-consent preferences — in your browser, removable any time.
Lawful Bases (GDPR)
- Consent (Article 6(1)(a)): Public-pool participation, ad personalization cookies, and any cookies beyond strictly necessary.
- Legitimate interests (Article 6(1)(f)): Operational logging for abuse prevention; EXIF stripping to protect users from accidental metadata leaks.
- Contract performance (Article 6(1)(b)): Image processing required to return your identification results.
Your Rights Under GDPR
EU/UK/EEA/Switzerland visitors have the right of access, the right to deletion, and the right to withdraw consent. Operational logs auto-purge in 24 hours; cookie + share-consent preferences are in your browser and you control them directly.
Children's Privacy
Brickguess is not directed at children under 13. No personal information is required to use the service.
Site Operator
Brickguess is operated by KroWVeBricks. For questions about this policy or to exercise your data rights, use the contact form on the homepage.