DRAFT · AWAITING OPERATOR REVIEW
Privacy notice
Support contact pending
Who handles your information
The service operator and support contact are shown above. This notice explains how the private beta handles personal information.
What we collect and why
We use the signed-in account identifier to keep your collection private. We store the collection records, photos, locations, counts, condition, valuations and sale records you choose to enter so those features work. Every customer provides a name and verified account email. Age in years, profession, country, approximate yearly LEGO spending range and currency, collecting interests and favourite themes are optional profile fields. We do not request a date of birth. The owner can view, filter and analyse these details to understand the collector community and improve the product. Customers can edit or clear optional details in Account. Account email supports service administration and is not marketing permission. We record terms acceptance, privacy choices and support requests. The standalone release also stores trial activation and expiry and essential recognition-credit counts to deliver plan allowances; optional analytics consent does not control these operational records. We count recognition provider calls by account and day for cost control and abuse prevention; those essential counts do not include photos or recognition results. Hosting and provider systems may also retain technical security logs under their own policies.
Scanning and external services
Photos submitted for recognition are sent to Brickognize to identify items. Catalogue data comes from Rebrickable and price guides may come from BrickLink. Cloudflare provides the hosted database and object storage; This private edition uses ChatGPT sign-in. The standalone edition uses an email/password account, verification and recovery emails, and secure session records. Passwords are hashed; the operator cannot read them. These providers may process information outside your country. Do not upload images containing people, addresses or other unnecessary personal information.
Optional product analytics
If you opt in, we record which app sections you open, grouped by day, to understand useful features. We do not include photo contents, collection contents, item values or sale recipients in those events. Reports cover a 90-day window. Older daily usage records are removed as usage is recorded, and your events are erased when you withdraw this choice. The owner can inspect account-level daily counts and the first campaign source recorded after opt-in, combine them with shared profile interests to understand feature preferences and repeat use, and suggest relevant product improvements. Segments are descriptive and do not infer sensitive traits or willingness to pay. Aggregate reports suppress small cohorts. Campaign sources are erased on withdrawal. No third-party advertising pixel runs in this release.
Optional email updates
If you opt in, your signed-in email address can be used for product news and beta invitations. This version records that permission; it does not send campaigns. You can withdraw it in Account & privacy. Essential service communications are separate.
Recognition improvement
Your personal corrections help your own recognition history. Sharing verified examples for possible future shared model improvement is a separate, optional choice in Scan studio. Enabling it marks examples as eligible; it does not mean an external model is being trained.
Your control and retention
Your information is not sold or shared with advertisers. You can edit your profile, withdraw optional consent, export records or submit an access, correction or deletion request in Account & privacy. Photos are separate from the JSON records export; request a photo copy through the access request workflow. Collection records are retained to provide the service until removed or an account deletion request is completed, subject to necessary legal retention. Privacy requests remain visible for follow-up. Contact support about privacy concerns. This beta notice must be reviewed against the operator's actual business and provider arrangements before wider release.
Help, feedback and optional AI
We store your guide progress and feedback conversations so you can resume walkthroughs and receive replies inside the app. Feedback is visible to your account and the platform owner and is included in your records export. If the owner enables AI help and you choose an AI explanation, your question and relevant app help text are sent to OpenAI. Inventory, photos, valuations and account profile records are not automatically attached. The app does not persist help-chat transcripts; the provider may retain service and abuse-monitoring records under its policies. We request store:false for AI responses. Essential daily provider-call counts enforce usage limits. Avoid entering passwords, payment details or unnecessary personal information.
Billing and Stripe
If you choose a paid membership, we send your verified account name and email to Stripe to create a billing customer for this app. Stripe handles payment details and recurring payments. We store the Stripe customer and subscription references, plan, payment status, paid-through dates, checkout attempts and event-processing receipts to manage access and resolve billing issues. Card details are not stored by this app. Account restrictions, in-app notices and your read/dismiss actions are stored to administer the service. Guide preferences and walkthrough progress let you turn onboarding on or off and resume it. These essential service records are separate from optional product analytics and marketing consent.