Legal
Privacy Policy
What we collect, why, who else handles it, and for how long.
Last updated: November 14, 2026
People who photograph bullion are photographing what they own. We built BullionBase to collect as little about you as it can, and to keep who you are out of everything we publish. This policy says exactly what we do collect, why, who else handles it, and for how long.
1. Who is responsible
BullionBase is operated by Browser7 Data Limited, 13 Adelaide Road, Dublin 2, D02 P950, Ireland (company number 779289). We are the controller of the personal data described here. Questions and requests: the contact form ("Privacy or my personal data"), or our email address.
2. The short version
- Reading BullionBase needs no account and sets no cookies. There is no analytics, no advertising and no tracking of any kind.
- To contribute you need an account: an email address and a username. Your email is never shown to anyone.
- Your work is credited the way you choose: your username, or "a BullionBase contributor". The monthly open release of the catalog contains no information about who made any change.
- Location, time and device details are removed from every photo before anyone else can see it.
- Our servers and database are in the European Union, in Germany.
- We never sell your data.
3. What we collect, and why
3.1 When you visit
Every request to the site passes through our content delivery network and our servers, which record, for security and to find faults: your IP address, your browser's user-agent text, the page requested (with any sensitive values removed), the time, and the result. If you are signed in, the record also carries your account's internal number - never your email or username. Requests to the sign-in pages and the contact form are never recorded, only counted.
Why: to keep the site running and secure, investigate faults, and stop abuse. Legal basis: our legitimate interest in operating a secure service (GDPR Article 6(1)(f)).
Counting visits. To see which pages are read and how readers find the catalog, each page you open sends our servers a short note of its own: the page's address (never any search words), the name of the site you came from (such as reddit.com), any campaign tags in the link, how long the page was in front of you, your country, the kind of device and browser, and whether you are signed in. Our servers turn your IP address and browser into a code that changes every day, so a reader is counted once a day without being followed from one day to the next; the note never contains your IP address. Every hour the notes are added up into daily totals - views per page, visitors, countries, sites - and only those totals are kept beyond the 30 days our server records last. No cookie is set and nothing is stored in your browser, and if your browser sends a "Do Not Track" or Global Privacy Control signal, no note is sent. It all happens on our own servers; no other company sees it.
Why: to learn what readers find useful and how they find the catalog. Legal basis: our legitimate interest in understanding how the site is used (6(1)(f)).
3.2 When you sign in
- Your email address, to send you sign-in codes and identify your account. The emails are sent through our email provider (section 4).
- The invitation list. While BullionBase is invitation-only, we keep each invited address, a short note of who the person is, and when they first signed in.
- Your session. When you sign in we keep a record of the session with the IP address and browser it started from, so we can spot misuse of your account. It ends after 7 days without use.
Legal basis: providing the service you asked for (Article 6(1)(b)); for the session's IP and browser, our legitimate interest in account security (6(1)(f)).
3.3 Your account
Your username (permanent and public), how you choose to be credited, your trust level, and counts of your contributions and points.
Legal basis: providing the service (6(1)(b)).
3.4 When you contribute
- Changes to records. We record which account made each change, so the site can credit you as you chose and moderators can deal with abuse. The reason you give for a change is public, in the record's history and in the monthly open release - but the release says nothing about who made it.
- Votes on the quality of records, with any explanation you write, are shown publicly with your credit choice.
- "I have one" / "I want one". These are shown only as a count, and only once at least three people have said so. Your name is shown with them only if you choose to make yours public.
- Drafts of records you have not published are visible only to you. To label a draft saved on another device, your browser keeps a random device number (section 12).
- Reports you make about a record or photo are seen only by moderators.
- Notifications about changes to your work are visible only to you.
Legal basis: providing the service (6(1)(b)); for the account behind each change, our legitimate interest in moderating a public catalog (6(1)(f)).
3.5 Photos
Before a photo is stored or shown to anyone, our servers re-create it and discard everything a camera hides inside the file: GPS location, the time it was taken, the device's make, model and serial numbers, any owner name, and embedded thumbnails. The only details written back are the license and the generic credit "BullionBase contributor - CC BY-SA 4.0" - never your name.
A published photo is public, under CC BY-SA 4.0. It may still show things in the picture itself, such as a reflection or what is behind the piece, so check before you upload.
The file you uploaded. We also keep a private copy of each photo exactly as you uploaded it - the same picture in the same format - with every one of those hidden details removed in the same way; only the picture's orientation and color profile are kept. It is never published: only you and our moderators can ever be shown it, and it is deleted when the photo is. We keep it so that a photo can be restored or framed again from what you sent.
Photos you never publish. A photo you upload while adding a piece is stored straight away, before the record exists. Your work is saved as a draft automatically as you go, and a draft keeps its photos for as long as the draft is kept. Photos that never became part of a draft - a form left before it was saved, or photos added to a record and never confirmed - are deleted, with their private copies, 7 days after the last one was uploaded.
Automatic screening. Every photo is checked by an AI model, run by our AI service provider (section 4), for content that breaks our rules, before it is stored. The model receives the cleaned photo only - no account or email. A photo it is unsure about is held, unseen, until a moderator reviews it. Identification: if you press "Identify from photos" while adding a piece, the cleaned photos of that piece are sent to the same provider to suggest what it is; you review the suggestion before anything is saved.
Legal basis: providing the service (6(1)(b)); screening, our legitimate interest in keeping illegal and harmful content off the site (6(1)(f)).
3.6 When you contact us
The contact form keeps what you send - your email address, your name if you give it, your message, and for a takedown notice the link you report - and passes it to our inbox, so we can answer you. If you are signed in, we note which account sent it, so a privacy request can be matched to its account. We never add you to any mailing list, and never send anything to the address you give except our reply.
The launch list. If you choose "Tell me when BullionBase launches", we keep your email address for one purpose: to email you once, when BullionBase opens to everyone. Then we delete it. Joining the list does not give you an account or an invitation. You can ask to be taken off it at any time through the same form.
Legal basis: answering you, our legitimate interest (6(1)(f)); the launch list, your consent (6(1)(a)), which you can withdraw at any time.
3.7 Preventing abuse
To limit how often sign-in codes, searches, uploads and edits can be made, we keep short-lived counters keyed on a hash of your IP address, email address or account. They expire within hours. The firewall also records the addresses of blocked connection attempts.
Legal basis: our legitimate interest in protecting the service (6(1)(f)).
4. Who else handles your data
We use other companies, our service providers, to run BullionBase. Each processes personal data only on our instructions, under a data processing agreement. The names of the providers are available on request, through the contact form.
| Provider | What for | What it receives | Where |
|---|---|---|---|
| Hosting provider | Our servers and database | Everything stored on the site | Germany |
| Content delivery and security network | Delivering pages and photos quickly, filtering attacks, DNS, storing photos | Your IP address and requests; photos | European Union, with delivery points worldwide; photos stored in Germany, with copies in the United States and Singapore |
| Email delivery provider | Sending sign-in emails and emails about our decisions on your contributions, and passing contact-form messages to our inbox | Your email address and the sign-in code or the decision; your contact-form message | European Union |
| AI service provider | Screening and identifying photos (3.5) | Cleaned photos | United States |
| Backup storage provider | Backups of photos | Photos | European Union |
| Mailbox provider | Our email inbox | Emails and contact-form messages you send us | European Union |
We share personal data with anyone else only if the law requires it, to protect people or the service from serious harm, or if BullionBase's operation passes to another organization (such as the non-profit steward the Open Data Pledge describes), which would then be bound by this policy.
We never sell personal data, and there are no advertisers.
5. What is public
Public: your username (if you chose to be credited by it), your contributions, the reasons you give for changes, your votes and their explanations, and your photos.
Never public: your email address, IP addresses, sessions, drafts, reports, notifications, and "I have one" / "I want one" unless you choose otherwise.
The monthly open release contains the catalog and its full change history, but no contributor identifier of any kind. One thing to be aware of: if you are credited by your username, the site shows it next to your changes, so someone comparing the site with the release could tell which changes in the release are yours.
6. How long we keep it
| Data | Kept for |
|---|---|
| Sign-in codes | 10 minutes, and used once |
| Sessions | Until 7 days after last use |
| Server records with full IP addresses | 30 days |
| Summarized server records, with IP addresses shortened | 90 days |
| Abuse-prevention counters | A few hours |
| Your account | Until you close it (section 7) |
| Drafts | Until you publish or delete them |
| Photos uploaded but never published | 7 days after the last upload, unless they are part of a draft |
| Contributions, votes, photos | Permanently, as part of the open catalog; see section 7 for closing your account |
| Photos removed from the site | Gone from the site at once, and from its delivery network within a minute; copies can remain in our private backups until those are cleared out |
| Database backups | 15 days |
| Reports and moderation records | 2 years after they are resolved |
| Contact-form messages | 2 years after they are sent |
| The launch list | Until the launch email has gone, then deleted |
7. Your rights
Under the GDPR you can ask us for a copy of your personal data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Use the contact form ("Privacy or my personal data"), or email our email address, from your account's address if you have one, so we can match the request to it. We answer within one month.
Closing your account. We delete your email address, username, sessions, drafts, notifications and your "I have one" / "I want one" choices, within one month of your request. Your contributions stay in the catalog - the licenses you granted keep them open - and are credited from then on to "former contributor". Your photos stay too, as their license cannot be withdrawn, but if a photo shows personal information, or you uploaded it by mistake, tell us and we will remove it.
If you think we have handled your data wrongly, please tell us first. You can also complain to the Data Protection Commission in Ireland (www.dataprotection.ie), or the authority in the country where you live.
8. Transfers outside the European Economic Area
Our servers and database are in Germany. Some providers work outside the EEA: our AI service provider, in the United States; our content delivery network, whose delivery points around the world see your IP address when you visit from near them, and which keeps copies of photos in the United States and Singapore. Where data leaves the EEA, it is protected by the European Commission's standard contractual clauses or an adequacy decision, as each provider's data processing agreement sets out.
9. Security
Connections are encrypted. The database is on a private network with no public access, and server access is limited to a few addresses. Sign-in uses single-use codes rather than passwords. Sign-in pages and the contact form are never recorded in logs, and IP addresses are removed from the text of error messages.
10. Children
BullionBase accounts are for adults: you must be 18 or over to have one. Reading BullionBase needs no account. We do not knowingly hold the personal data of anyone under 18; if you believe we do, contact us and we will delete it.
11. Automated decisions
The automatic photo screening (3.5) can hold a photo back, but never removes anything or acts against your account on its own: a person reviews every held photo. We make no automated decisions with legal or similarly significant effects on you.
12. Cookies
BullionBase uses only the cookies it needs to work. There are no analytics, advertising or tracking cookies, and none from other companies, so there is nothing to accept or refuse. Reading the site sets no cookies at all. Counting visits (section 3.1) uses no cookie and stores nothing in your browser.
| Cookie | What it does | Lasts |
|---|---|---|
__Secure-better-auth.session_token | Keeps you signed in. Set when you sign in; removed when you sign out. | 7 days after you last use the site |
bb_fresh | Set for a few minutes after you publish or edit something, so you see your change straight away rather than an earlier copy of the page. A random value, nothing about you. | 3 minutes |
Both are strictly necessary for the parts of the site you choose to use - being signed in, and seeing your own edits - which is why they need no consent. If our security network suspects an attack, it may ask your browser to pass a check and set a short-lived cookie to remember that it did; that is strictly necessary for security, and carries nothing about you.
Your browser also keeps one item in its own storage, bb.clientId: a random number for that browser, used only to tell you when a draft was last saved on a different device. It stays until you clear your browser's storage.
If BullionBase cannot be reached while you are adding an edition, your browser also keeps a copy of what you have entered so far, so the work is not lost (an item named bb.unsaved. and a random number). It leaves your browser only to be saved to your own drafts once BullionBase is back, and is removed as soon as it has been.
Photos are served from a separate address, img.bullionbasemedia.com (and their smaller sizes from sizes.bullionbasemedia.com), which set no cookies.
13. Changes
We will post any change here with its date and, for a significant change, tell contributors by email or on the site before it takes effect.