Legal

Privacy Policy

Version 2.4  ·  Effective date: 5 September 2026

1. Who we are

My Beer Shelf is a product of Nisshagen Advisory AB (Org.nr 559526-6742), a company registered in Stockholm, Sweden. We are the data controller for personal data collected through the mybeershelf.com website.

Contact hello@mybeershelf.com for any privacy question, including data subject requests under the GDPR.

This policy covers the website, including the shelf page you reach by signing in.

About the app. The My Beer Shelf app is in internal TestFlight, which means invited testers, and it is not on any public store. It has sign-in, a shelf and a tasting log, and it does not yet have a Delete account button of its own. Section 8 says what that means and what to use instead. It will carry its own policy for what happens on your phone before it reaches a store, and this page will point to it. Three services it uses are named in section 5 anyway, because they outlive a deletion and you should learn about them here rather than later.

2. Reading the site

The pages themselves

The front page, the catalogue at /beers and the styles pages are assembled on our servers and sent to your browser as finished HTML. The catalogue’s filters are a plain form that reloads the page, so searching for a brewery changes the address bar and nothing else. There is no sign-up, no interest list and no form on this site that sends us anything about you.

No page sets a cookie. There is no analytics: no page-view counter, no session recording, no product analytics and no tracking pixel belonging to us or to anyone else. Vercel Web Analytics is not switched on for this project. Our host keeps the request logs any web server keeps, and section 6 covers those. Nothing else on this site watches you read it.

The one thing that runs in your browser on every page is a check for a sign-in token on your own device. If there is no token, nothing is sent anywhere and the page stays signed out.

Where the catalogue comes from

The 4,858 beers at /beers are Systembolaget’s range: product facts about what a Swedish state off-licence stocks. We did not get them from Systembolaget directly. Their public API portal no longer resolves, so the rows were collected through a community mirror at susbolaget.emrik.org and stored in our own database, where this site reads them. They are facts about products, not about people, and there is no column in that table for a user.

We show the name, brewery, style, strength, size and country, and nothing else. The price came off the catalogue on 1 September 2026. Systembolaget’s own tasting prose and food-pairing suggestions are in the source data and are excluded from the query this site makes, so those columns never leave the database and no page can render one by accident. The catalogue leans Swedish because Systembolaget’s range does: 71% of the rows are beers brewed here.

No pictures from anyone else

The catalogue shows no product photographs. The source rows carry image addresses pointing at Systembolaget’s own servers, and we do not use them, so your browser never requests an image from them or from any other company while you browse. The cards are typographic, and so is your shelf page.

There are no photographs of yours either. Earlier versions of this policy described photographs you had uploaded. There is no way to upload one. The app has no photo-library feature and no image-editing library, its camera is a barcode reader and nothing else, and there is no file storage area for beer for a file to land in. Each beer record has an unused slot for a picture and the shelf page would render one if it were filled, but we checked every place that value could come from and no screen in the app supplies one. If that changes, this section changes first.

The app also sends no photograph anywhere, because it has no AI scan. We searched it for a scan of that kind and found none: the camera screen takes no picture, reads only barcodes, and no frame ever leaves your device. There is therefore no free scan allowance in this app, no scan ledger row written for it, and no image processor in the list in section 5. If you have read about a label scan on another Shelf app's site, that is that app; this page describes this one.

Nothing here is for sale, and where the gear links go

This site sells no beer and links to nowhere that does. There is no basket, no checkout and no arrangement with Systembolaget or any brewery. The catalogue shows no price and has no buy link on any beer.

The site does carry affiliate links to Amazon.se, on the gear page and next to the glass suggestions on the styles pages. They point at accessories: glasses, growlers, cellar kit. None of them lead to beer or to any other alcohol. Every one is marked Annons. If you buy something through one, Amazon pays us a commission and the price you pay does not change.

What that means for your privacy is short. The links are ordinary links: nothing from Amazon loads on our pages, no Amazon cookie is set here, and Amazon learns nothing about your visit unless you click one. If you do click, your browser goes to Amazon.se and the address carries our affiliate tag, so Amazon knows the visit came from our link; from that moment Amazon’s own privacy policy governs. What Amazon reports back to us is totals of clicks and purchases, never who you are.

Beer staying unsold and unlinked is still a standing rule rather than a description of how things happen to stand today. If it changed, this page and the terms would say so before anything on the site did, which is how the gear links themselves arrived: section 11 records it.

3. Signing in, and your shelf

Your account

Most of the site needs no account. One page, your shelf, does, and there is a Sign in button in the navigation on every page. Sign-in runs on Supabase, our database and authentication provider, hosted in the EU. What we hold depends on how you sign in:

• Email and password: your email address, and a password we never see in readable form. It is hashed by Supabase.
• A magic link: your email address. We send you a link, and following it signs you in.
• Sign in with Google: your email address and the account identifier Google returns. We do not receive your Google password, your contacts or anything else in your Google account.
• Sign in with Apple: the account identifier Apple returns, and the email address you choose to share. If you use Apple’s Hide My Email, we only ever see the relay address, never your real one.

If you type a name when you create the account, we store it and use it to greet you on your shelf. Nothing else about you is asked for.

One login across the shelf apps

The account is the ShelfHub account, and it is one login across My Bar Shelf, My Whiskey Shelf, My Wine Shelf, My Beer Shelf, My Cigar Shelf, My Coffee Shelf and My Supply Shelf. Signing in here signs you in with the same credentials you use there. The login is shared. The shelves are not: your beers are not visible to those apps, and what you keep in them is not visible here. This matters most when you delete something, so section 8 sets it out in full.

Where your session is kept

Nothing on this site sets a cookie. When you sign in, one entry goes into your browser’s local storage, named sb-tlqlbnhaqpqgaxfihdlj-auth-token after our database project, holding the token that keeps you signed in. Signing out removes it. If you sign in with Google or Apple, the token comes back in the address bar and is moved into that same entry.

That entry is the only thing this site stores on your device, and it is there because you asked to be signed in. Storage that is strictly necessary for something you requested does not require consent under the ePrivacy rules, which is why you are not looking at a cookie banner. If we ever add storage that is not necessary, you will be given a real choice about it and this policy will say so first.

What the shelf page shows

It shows what the app holds against your account, and nothing else:

• Your beers: the name and brewery, the style, strength, bottle or can size, vintage year, how many you have, whether it is open, whether it is cellaring or in the fridge, your notes, and when the record was made.
• Your tastings: which beer, the date you drank it, the score out of five, the flavour notes you tapped, and anything you wrote. The page fetches the forty-eight most recent.

Read as a run, those records are a dated account of what someone owns and what they have been drinking. We would rather say what it amounts to than file it under “your data”. It is private to your account: the database restricts every row in both tables to the account that created it, and that restriction lives in the database rather than in this website’s code, so it holds no matter what this page asks for.

This page reads and does not write

Nothing you do on this website changes your shelf. Adding a beer, logging a tasting and editing anything happen in the app. There is not one write to shelf data anywhere in this site’s code. The only things this site can change are the account itself: creating it, resetting the password, and the deletion described in section 8.

What this site does not do

• No ad networks, no advertising identifiers, no ad tracking. The gear links are the one piece of advertising here, each marked Annons, and they carry no tracker and load nothing.
• No analytics, no page-view counting, no session recording, no third-party trackers.
• No location on this website: no page here asks your browser for a position, and we found no geolocation call anywhere in this site’s code. The app does not ask for it either. We searched it for every way a position can be read and found none, and the location library is not among its dependencies at all.
• No camera, contacts, calendar or photographs of yours. There are none to have: the app cannot upload one.
• No selling, renting or sharing of personal data with data brokers, ever.
• No purchases. There is no subscription, no in-app purchase and no paywall on this site.

If any of that changes, we will update this policy before the change goes live rather than after, and analytics in particular would stay switched off until you consent to it.

4. Legal basis for processing

Version 2.2 of this policy gave a basis for the website and none for the app, while section 5 described the app’s processing in full. That left the largest things this policy describes with no lawful basis attached to them. Both are covered here.

• Performance of a contract, Article 6(1)(b): creating and holding your account; reading your shelf back to you on this site; and, in the app, storing your beers and your tastings, running a barcode lookup when you scan one, sending the notifications you turned on, and honouring a subscription bought on the same account. Without this there is no service to provide.
• Consent, Article 6(1)(a): the app’s usage analytics, and nothing else. Off until you switch it on yourself, withdrawable in the same place at any time, and withdrawal does not affect what was processed before. Nothing on this website relies on consent: there is no marketing list, no newsletter and no non-essential storage. Version 2.2 said consent was relied on for nothing at all, which was true of the site and not of the app.
• Legitimate interests, Article 6(1)(f): keeping the site working and secure, and serving the public catalogue to the people reading it; crash and error reporting from the app, so that we find out when it is broken; the subscription check the app makes on launch, so that what you paid for is honoured and what you have not paid for is not; and the pooled barcode table in section 6, so that a lookup which works for one person works for the next and we do not ask an outside database the same question twice. Against the last of those sits the fact that the pooled row carries your account identifier, which section 6 states plainly and does not dress up.

Giving us this data is not a statutory requirement. It is what the app needs in order to be a shelf: without an account there is nowhere to put a beer. There is no automated decision-making that produces legal or similarly significant effects, and no profiling.

5. Third parties we use

• Supabase – the database and the sign-in system, holding the catalogue, your account and your shelf records. Hosted in the EU. The sign-in emails (confirmation, password reset, magic link) are sent through it.
• Vercel – hosting for this website. No analytics product is switched on for this project, so Vercel sees the server-side request logs any host sees and nothing beyond them.
• Amazon – the partner behind the gear links, under the Amazon Associates programme. Nothing on this site loads from Amazon and no page here sends it anything about you. A gear link is a plain address pointing at amazon.se with our affiliate tag in it, so Amazon first hears from your browser if you click one, and from then on Amazon’s own policy applies. The reporting we get back is aggregate: clicks and purchases as numbers, never names.
• Google and Apple – only if you choose to sign in with one of them, and only for that sign-in. Choosing one sends your browser to them. Not choosing one means your browser never contacts them for sign-in.

Fonts are the last one, and it applies to three pages rather than the site. This policy, the terms and the deletion page are static pages that load their two typefaces from Google Fonts, so your browser requests those files from Google’s servers and Google receives your IP address as part of that request. No font cookies are set. Every other page on the site serves its fonts from our own domain, so reading the catalogue involves no request to Google at all.

We do not sell your data to any third party. Supabase and Vercel are the two companies we contract with to run this site, and neither uses your data for advertising. The Associates agreement with Amazon is a contract too, but it runs nothing on this site and your data plays no part in it. If we ever add a provider that would, we will update this policy before the arrangement starts.

Google and Apple are not working for us, so we will not make a promise on their behalf. What their servers do with a request they receive is governed by their own policies. What we control is how little we hand them, and section 2 says exactly what that is.

Three that the app sends your account identifier to

None of these is contacted by this website. They are named here because the deletion in section 8 does not reach them, so they outlive it however you ask. They are not the whole of what the app contacts: the barcode lookup below asks three more, and those receive a barcode rather than anything about your account.

• Sentry – crash and error reports from the app, on Sentry’s German service. We switch off the sending of personal data and we never attach an account to a report. The honest limit is that the library keeps a trail of the network requests leading up to a fault, and some of our database requests carry your account identifier in the address, so a report can contain it. We are not going to claim a crash report holds nothing about you.
• Mixpanel – usage events from the app, on Mixpanel’s EU service, and only if you turned analytics on yourself. It is off until you do, and while it is off the library is never started at all. The events are keyed to your account identifier rather than your name or your email, which makes them pseudonymous rather than anonymous.
• RevenueCat – in the United States. The app asks it on launch whether your account holds a subscription, so it receives your account identifier when you sign in whether or not you ever buy anything, along with your platform and the IP address of the request. Nothing on this website contacts it and nothing on this website is for sale.

On the Mixpanel entry, one thing worth being exact about: your analytics answer is one row on your account, and five apps read and write that row: My Beer Shelf, My Bar Shelf, My Whiskey Shelf, My Wine Shelf and My Cigar Shelf. So it is the same answer in all five. It is not the answer in My Coffee Shelf, which keeps a separate one in its own table and asks you again there. My Supply Shelf sends no analytics at all.

On the RevenueCat entry, one more: what a subscription unlocks depends on which one you bought. A bundle subscription is honoured by the Shelf apps that check for it. A single-app subscription, which is what most current subscribers hold, unlocks the app it was bought for and is not honoured elsewhere. This page has never claimed otherwise and is not going to start; it is written down because the neighbouring Shelf policies used to claim otherwise and have been corrected.

Scanning a barcode in the app asks three outside databases

This was missing from version 2.1 and it belongs here, because it is the app sending something to companies we have not named.

When you scan a barcode, the app checks the pooled table in section 6 first. If that misses, it asks up to three external barcode databases in order and stops at the first that gives a usable answer:

• Open Food Facts and Open Products Facts, run by the same non-profit in France.
• UPCitemdb, in the United States.

Each request is made by your phone rather than by our server, so the database answering it receives the barcode digits and your device’s IP address, and a fixed line identifying the app as My Beer Shelf. None of them receives your account identifier, your email or anything from your shelf: the request carries the barcode and nothing else of yours.

A barcode is not personal data, but the address it arrives from is, which is the reason this paragraph exists.

6. How long we keep things

• Your account and your shelf: for as long as the account exists. Delete it and every beer, every tasting and anything else the app has recorded against the account go with it. Nothing expires on its own and no clean-up job removes it.
• Barcode contributions: if you scanned a barcode in the app and it matched a Systembolaget product, that mapping goes into a pooled table so the next person who scans it gets an answer. The row holds the barcode, the product, its name and the account identifier of whoever contributed it. That identifier is cleared only when your sign-in record itself is deleted. If your sign-in is kept because another Shelf app still holds your data, it stays on the row until the sign-in goes. Version 2.1 of this policy said the table had no column for a contributor and there was nothing about you in it. That was false: the column exists, the app fills it with your account identifier, and any signed-in user can read it. Section 8 sets out what deletion does and does not reach.
• Crash reports, usage events and the subscription record: Sentry, Mixpanel and RevenueCat keep their own copies on their own schedules, and no deletion of ours reaches them. Section 8 says what to do about it.
• The catalogue: kept until a Systembolaget import replaces it, and not touched when an account is deleted, because it is not about you. A catalogue row says a beer is stocked, not that anyone owns one, and it has no column for a user.
• On your own device: the single sign-in entry described in section 3. Signing out removes it.
• Request logs: our host keeps server-side request logs on its own operational retention schedule. We do not read them to build a picture of any reader, and there is no tool on this site that would let us.

7. Your rights under the GDPR

As a user in the European Economic Area you have the right to:

• Access: request a copy of the data we hold about you
• Rectification: ask us to correct anything inaccurate
• Erasure: ask us to delete your account and everything on your shelf
• Portability: request your data in a portable format. There is no export button on this site. We assemble the file by hand and send it to you.
• Withdraw consent: tell us to stop at any time, without giving a reason; withdrawal does not affect processing carried out before then
• Object and restrict: object to processing based on legitimate interests, or ask us to restrict it

To exercise any of these, write to hello@mybeershelf.com from the address on the account. We will respond within 30 days. You also have the right to lodge a complaint with your national supervisory authority; in Sweden that is Integritetsskyddsmyndigheten (IMY).

8. Deleting your account

The Delete account button in the account panel on this site works. It tells the shared deletion function that it is being called from My Beer Shelf, the function has a My Beer Shelf branch, and that branch removes your tastings and then your beers, and nothing belonging to any other shelf app. Version 2.0 of this policy said the function had no branch for beer and refused the request. That was true when it was written and stopped being true shortly afterwards, and this page is late saying so. Section 11 records it.

The app does not have a delete button yet, and that is a separate thing. It is not that the app tries and fails. The screen simply has no such button on it, so there is nothing to press. This is the opposite way round from what version 2.0 implied: the website route is the one that works and the app is the one still missing. When the app gets one, this section will say so, and we would rather you held us to that than took it on trust, given the last promise of that shape.

You can also email hello@mybeershelf.com from the address on the account and we will delete it by hand, which is the route to use if you cannot get into the account you want gone. Either way we remove everything held against it: every beer, every tasting, and the notification records for this app. Deletion is permanent and we cannot restore it afterwards. Deleted rows can sit in our database provider’s routine backups until those age out, and we are not going to quote a number for that, because it is our provider’s schedule rather than ours. The deletion page sets out the whole procedure and is reachable without signing in.

One thing to know about the shared login. If the same login is also used for another shelf app, deleting your beer records does not delete the login itself, because that would destroy your account in the other app. The function checks the other shelf apps for you, erases the beer records, and keeps the login. Ask and we will remove the login too.

What is left afterwards. Saying “nothing” would be easier and it would not be true. Crash reports at Sentry, usage events at Mixpanel if you ever turned analytics on, and your subscriber record at RevenueCat all survive, because no deletion of ours reaches those three.

The rest depends on whether your sign-in record is deleted or kept, and version 2.1 of this policy described only one of the two:

• If the sign-in is deleted, your identifier comes off any pooled barcode row you contributed and the mapping stays without it, and your analytics choice and the log of notifications sent to you go with the sign-in.
• If the sign-in is kept because another shelf app still holds your data, three things are kept with it: your analytics choice, the log of notifications sent to you, and your identifier on any pooled barcode row you contributed. Nothing in the deletion clears that column, and you cannot remove the row yourself.

Write to us and we will remove by hand whatever the button cannot, including a barcode attribution on either path.

9. Age

My Beer Shelf is about keeping beer and writing down what you thought of it, and it is meant for adults who are of legal drinking age where they live: 21 in some countries, 18 or 20 in others. It is not directed at anyone below that age, and we do not knowingly hold data about them. If you believe a minor has an account here, write to us and we will delete it.

This site does not put an age prompt in front of you and stores no answer to one. Version 1.0 of this policy said otherwise; see section 11.

10. International transfers

Our database, our authentication and everything on your shelf are hosted in the European Union.

What stays inside it: crash reporting on Sentry’s German service, usage analytics on Mixpanel’s EU service, and two of the three barcode databases, which are in France.

These reach past the boundary:

• Sign in with Google and Sign in with Apple, handled by Google and Apple under their own terms, and only if you pick one.
• Google Fonts, which serves the typefaces on this page, on the terms and on the deletion page.
• RevenueCat, in the United States, which receives your account identifier. This belongs to the app rather than to this site, and section 5 sets it out.
• UPCitemdb, in the United States, which receives a scanned barcode and your device’s IP address when the app asks it. Also the app rather than this site.

For RevenueCat we rely on the European Commission’s standard contractual clauses, which form part of the data processing terms it publishes. Version 2.1 of this policy counted three transfers and left out UPCitemdb, because it did not describe the barcode lookup at all. If a provider we choose ever needs to process data outside the EEA, we will only use one that relies on an adequacy decision or those clauses, and we will say so here.

11. Changes to this policy

If we make material changes we will publish the updated version here and update the version number and effective date at the top of this page. If a change materially affects data we already hold about you, we will tell you before it takes effect.

12. Contact

Questions or concerns about your privacy? Write to hello@mybeershelf.com.

Nisshagen Advisory AB, Stockholm, Sweden.