Deleting your account and data

1. In short

• You carry out the deletion yourself, on the account page. It happens immediately and cannot be undone.
• What is deleted is your collection, your photographs — the files themselves, not just the entries — and your sign-in account at the identity provider.
• A few things are kept and anonymised instead: contributions other people rely on. Section 4 says exactly which.
• If you can no longer sign in, an informal message to hello@brickdb.net is enough — see section 6.

2. Deleting your account

1. Sign in to BrickDb — in the application or in a browser.
2. Open the account page. It is linked from the footer of every page as “Account”.
3. Go to the “Delete your account” section. It lists in advance what would be deleted: how many owned copies of sets, minifigures, part lots and photographs are stored, and how many of your bag-code contributions are anonymised rather than deleted. If that cannot be read at the moment, the button is not offered — you are not asked to agree to something we cannot describe.
4. Choose “Delete my account”.
5. A confirmation appears. It asks you to type a word before it can be confirmed — DELETE in an English interface, LÖSCHEN in a German one. The confirmation names the word itself. Then choose “Delete everything”.

The deletion is carried out immediately. If it stops part-way it is resumed rather than undone: ask for it again and the rest is finished.

3. What is deleted

• your owned copies of sets with everything recorded about them — your own name for each, notes, tags, where you kept it, what you paid, its condition and any recorded signatures,
• your individual minifigures and loose parts,
• your wishlist,
• your photographs — the stored files together with their resized versions, not just the entries, and equally the box photographs still queued for bulk import,
• your avatar picture, if you uploaded one,
• the parts view derived from your copies,
• your event submissions, as long as they are not yet approved, or were rejected,
• your BrickDb account and your sign-in account at the identity provider you sign in through.

4. What is kept, and why

Four things are anonymised rather than deleted. What they have in common is that they are no longer only your data: the link to you goes, the content stays, because it belongs to other people or is relied on by them.

• Your contributions towards bag codes and retail barcodes. What is inside a numbered bag is a fact about a product that other users established together and rely on — it takes three different people to settle one. The contribution stays; the link to the person is replaced by a freshly drawn random value for which no account and no mapping exists (Recital 26 GDPR).
• Approved event submissions. A moderator vetted them and other people are reading them; deleting one would take it off everybody's list. They take the same freshly drawn random value.
• Copies in a collection you share with other people. The set number, the quantity and the condition stay with the collection so the other members are not deprived of their record of it. Everything personal on it goes — your own name for it, your notes, your tags, where you kept it, what you paid, what you thought it was worth, and its photographs — along with the link to you. A copy in a collection nobody else is in is deleted outright: there is no one it would be taken from.
• Support requests you opened while signed in. Your e-mail address, your name and the link to your account go — here removed outright rather than replaced by a random value, so two of your tickets can no longer be matched to each other either. The subject, the body and our replies stay, because that conversation involved us too. The link that opens a request without signing in stops working in the same step.

A support request you raised without signing in is not touched at all: it carries no link to an account, and BrickDb cannot tell whose it was. If one of those should be deleted, tell us at the address in section 6.

5. How long anything can still exist afterwards

The complete list of storage periods is section 13 of the privacy policy. That list is authoritative and this page does not repeat it — a period written down in two places is a period that can go stale in one of them. Two of them are the answer where a deletion is concerned:

• Backups: deleted data leaves them at their regular expiry, at the latest after 35 days.
• Support requests (in the anonymised form described in section 4): 24 months after the ticket is closed.

Everything processed independently of your account has its own period and its own conditions, and both are stated in the privacy policy rather than here: the audience measurement, which requires your consent, in section 10; error diagnosis, including what an error report contains at all, in section 11; logs at infrastructure level in section 3.

6. If you can no longer sign in

The right to erasure under Article 17 GDPR exists whether or not you can still reach your account — including after you have uninstalled the application or lost access to your sign-in. An informal message to hello@brickdb.net is enough; the full details of the controller are in the imprint.

So that a request can be matched to an account: BrickDb stores no e-mail address itself — the sign-in details are held by the identity provider (section 7.1 of the privacy policy). Write from the address you signed in with where you can, and name it in the message. If a request cannot be matched, we ask rather than guess.

7. Uninstalling the application deletes nothing

Removing the application from a device only ends its use on that device. It deletes neither your account nor the data stored — one of the two routes in section 2 or section 6 is needed for that.