Bruce Bassi, MD MS
Newsletter
BrickSorter · Legal

Privacy Policy

BrickSorter needs very little about you, and this page lists all of it. You sign in with your Apple ID, your Google account, or an email address and a password; the app never asks for a name, a phone number, contacts or location.

Last updated: October 16, 2026

Who this covers

This policy covers the BrickSorter app for iPhone, published on the App Store by My Medical Records Inc. and made by Bruce Bassi. It does not cover this website, which has its own cookie policy.

What the app sends off your phone

Everything below travels over an encrypted connection to our server. (Settings lets you point the app at a different server instead; if you do, that server’s operator, not we, receives what follows.)

  • Cropped pictures of your pieces. When you take or choose a photo of the sorting sheet, the app finds the pieces on the sheet on your phone and uploads only a small cropped picture of each piece: a square drawn around that one piece, with the other pieces and the sheet’s printed marks painted out. The original, full photo never leaves your phone. The crops carry no metadata of any kind: no location, no camera make or model, no date. A crop shows whatever lies inside its square, so keep fingers and anything private off the sheet. With the crops the app sends a short technical record of the shot — the camera’s field of view and closest focus, the photo’s pixel size, the phone’s tilt, whether the photo came from the camera or your photo library, and the app version — so the identification can be tuned. That record can indicate which iPhone model took the photo; it holds nothing about you or where you were.
  • Who identifies them. Each crop is identified twice: by BrickSorter’s own recognizer, a service we run on Microsoft Azure, and by Brickognize, a third-party part-recognition service our server forwards the crop to. Brickognize receives the crop and nothing else: no account, no scan, no shot record. Brickognize’s terms, not ours, govern what it does with crops: they grant it a perpetual license to uploaded images, including to train its models, and let an uploader ask it to remove content.
  • Crops kept to teach the recognizer. Our server keeps every crop it receives. When you confirm a piece — with Done, with a correction on its page, or by sending it to the unclassified pile — that crop and the part you named go to BrickSorter’s recognizer, which keeps a numeric fingerprint of the crop with the part and color, not the picture, so it recognizes that kind of piece better next time, for everyone. Undoing the confirmation removes the fingerprint again; deleting the library or your account does not. How long the crops themselves stay is under How long things are kept.
  • Your collection. The libraries, sets, scans, placed pieces and unclassified piles you create are stored on our server, so every phone signed in to your account, or set up with its connect code, sees them. For each piece the server keeps the result of the identification, the measured size and color reading, the shot record above, the crop, and a fingerprint (a hash) of the crop so the same crop is not identified twice. The set searches you type are cached on our server for a day.
  • Your sign-in. You sign in with Apple, with Google, or with an email address and a password. Our server keeps the stable user id the provider assigns to this app and, when the provider shares one, a verified email address — used only to recognize the same person signing in with the other provider, never for mail. Apple’s sign-in shares no email unless you choose to; the app asks Apple for no name and no email. Everything the app receives from Google, and how it is used, kept and deleted, is set out under Google user data below. Each signed-in phone holds a session token in its Keychain, never synced to iCloud; signing out on any phone ends that session, and the connect code you can show another phone copies the session, so anyone who scans it can see and change your sets. With an email address and a password, our server keeps the address and a one-way hash of the password (Argon2id), never the password itself, and confirms the address by emailing it a 6-digit code — when you create the account and when you reset the password. A code works for 15 minutes; our server keeps only a hash of it, deleted within a day, and an account is created only once its code is entered. If the address is already the verified email of an account you made with Apple or Google, the email sign-in joins that account.
  • Server logs. Like any web server, ours records each request’s network address, path and outcome in a log that is kept for about three days.

Google user data

This section states, point by point, how BrickSorter handles data from your Google account when you choose Sign in with Google. It is the only Google data the app ever touches.

  • What Google user data the app accesses. When you sign in with Google, Google’s sign-in (OpenID Connect, with the openid and email permissions) sends our server three things: your Google account’s email address, whether Google has verified that address, and the stable identifier Google assigns to your account for this app. The app requests nothing else. It has no access to Gmail, Google Drive, Calendar, Contacts, Photos, YouTube or any other Google service or data, and it never asks for your Google password.
  • How the app uses it. The identifier is your account key: it is how the server knows which libraries are yours when you sign in again, on any phone. The email address is used for one purpose: to recognize the same person when they also sign in with Apple, so both sign-ins reach one collection. Google user data is never used for advertising, marketing, analytics, profiling, model training or anything beyond providing the app’s own features, and never to send you mail.
  • With whom it is shared, transferred or disclosed. No one. Google user data is not sold, not shared with other companies and not transferred to third parties. It is stored only on our server, which runs on Microsoft Azure in the United States; Azure is our hosting provider, stores the data on our behalf and does not use it. Brickognize receives only cropped pictures of bricks and Rebrickable only set and part look-ups; neither receives your email address, your Google identifier or anything else about your account. We would disclose data only if the law required it.
  • How it is protected. Every connection between the app and our server, and between our server and Google, uses HTTPS with TLS 1.2 or newer; plain HTTP is refused. On the server your data sits in a database on Microsoft Azure storage that is encrypted at rest, and the daily backup lives on the same encrypted storage. Sign-in sessions are stored only as one-way hashes, the server never holds a Google password or any Google access token with further permissions, and the key that signs Apple’s sign-in requests is kept in Azure Key Vault. Only the developer can reach the server and its backups, and the app contains no advertising or analytics code that could carry data elsewhere. BrickSorter holds no sensitive data in Google’s sense: no financial, health, biometric, location or government-identifier information.
  • How long it is kept, and how to delete it. Your Google identifier and email address are kept for as long as your account exists. Settings → Account → Delete account removes them, together with every library, scan and session, from the live database at once; the daily server backup that may still hold them is replaced within 7 days, and no other copies exist. You can also revoke BrickSorter’s access in your Google Account (Security → Third-party apps & services), which stops any further sign-in, or ask us to delete your data by email to support@mymedicalrecords.ai or through the chat window on this site; we do so within 30 days.
  • Google’s rules. BrickSorter’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data from other services

  • Rebrickable supplies the set and part data. Our server fetches it. Set and part pictures load on your phone directly from Rebrickable’s picture server (cdn.rebrickable.com), which sees your phone’s network address the way any website does.
  • Links you tap — a set’s building instructions, a part on a marketplace — open in your browser, and those sites (rebrickable.com, bricklink.com, brickowl.com, lego.com) then see you the way any website does.
  • Brevo sends the emails that carry sign-in codes, from noreply@brucebassi.com. It receives the address and the email to deliver it, and keeps delivery records under its own privacy policy. Nothing else goes to Brevo, and BrickSorter sends no marketing email.
  • Our server and BrickSorter’s own recognizer run on Microsoft Azure in the United States.

What the app does not do

  • No advertising, no analytics or tracking SDKs, and no selling or sharing of data for marketing.
  • No location: the app never asks for it, and photo metadata is removed before anything is uploaded. No readable passwords: an email sign-in’s password is kept only as a one-way hash, and Apple and Google sign-ins have none.
  • No access to your photo library: Choose a photo opens the iOS photo picker, which hands the app only the photo you pick, and the app never saves anything to your library. The camera is used only on the scan screens.
  • No payment details: Apple takes the payment for the app. We never see your card, and nothing about the purchase reaches our server.
  • No crash-reporting SDK. If you have chosen in iOS Settings to share crash reports with developers, Apple may pass them on to us. On TestFlight, Apple also shares crash logs and any feedback you send through TestFlight with us.

On the App Store privacy label this is declared as four kinds of data — Email Address, Photos or Videos, Other User Content and User ID — all linked to you, used only for the app’s own functionality, and never for tracking.

How long things are kept

  • Each piece’s result, the crop’s fingerprint and the shot record stay with the scan for as long as its library exists, and for 30 days after you delete the library. Brickognize’s raw answers, kept so the same crop is not sent twice, are pruned 90 days after they were received, even if the library was purged earlier.
  • The crops themselves stay on our server after you delete a library or your account: we keep them to train the recognizer, and what the recognizer has learned from your confirmations stays learned. Once the scan is purged nothing links a crop to you. Undoing a confirmation while the library exists removes that piece’s fingerprint from the recognizer.
  • Removing a set from a library hides it; its data, and the record of every piece you placed or un-placed, stay until that library is purged.
  • A deleted library waits 30 days in Recently Deleted, where you can restore it; then it and its scans are purged. Delete Now in Recently Deleted purges it at once.
  • A full copy of the server database is taken daily and kept for 7 days, so a purged library is gone from server backups about a week after the purge. No copies are kept anywhere else.
  • Settings → Account → Delete account removes your collection at once: every library, set, scan and pile, your sessions, your sign-ins (an email sign-in’s password hash with them), any sign-in codes and the email, and it asks Apple to revoke its sign-in. Only the crops described above, and what the recognizer learned from them, outlast it. To stop without deleting, sign out or delete the app: nothing more is sent.
  • The app keeps a reduced copy of your last photo and its crops on the phone, outside iCloud and device backups and never in your photo library, until the scan is confirmed or replaced. Deleting the app deletes it.
  • Brickognize cannot tell whose crops are whose: our server sends them, and only our server holds the reference numbers Brickognize assigns. If you want crops removed from Brickognize, ask us and we will send Brickognize the reference numbers for your scans; its terms let an uploader request removal.

Your rights

Wherever you live, you can ask us for a copy of what we hold about you, to have it corrected, or to have it deleted: email support@mymedicalrecords.ai. We answer within 30 days. You can also delete your account yourself at any time, as described above.

Children

BrickSorter is not directed at children under 13. Beyond the sign-in described above, it asks for no name, phone number, address or other personal details; what it does keep is listed above.

Changes

Changes to this policy are posted here with a new date at the top. The date is when the page was last checked against the app, not a guess.

Questions

Email support@mymedicalrecords.ai, or ask through the chat window on this site.

BrickSorter is an independent app. It is not affiliated with, sponsored by or endorsed by the LEGO Group. LEGO® is a trademark of the LEGO Group of companies.