Privacy
Last updated 4 October 2026.
This page explains what happens to information about you when you read the guides, use the community or play the Norwegian learning game at /play/.
The short version
You can read the guides and earn three game badges as a guest. A free game account is required to continue, and it saves progress across devices. Community accounts use a separate sign-in system. Anonymous community posts are published as “Anonymous”; an account is required to reply. The newsletter is optional.
These things may happen:
- Our host records ordinary technical information every time a page is served, and produces visitor statistics from it. This does not involve cookies and happens on every visit.
- If you accept analytics cookies, we also count visits in more detail, so we know which guides are useful. If you decline, no analytics cookies are set and no analytics data is sent to Google.
- The guides' typefaces are served from our own domain, so reading a guide does not send your details to a font provider.
- If you enter your email address and press Subscribe, it is sent to Brevo. Brevo sends a confirmation link, and you join the list only if you click it.
- If you rate or comment on an article, Netlify stores the rating or the public comment and uses technical information to limit abuse.
- If you use the community, Supabase stores posts and replies. You can start a discussion anonymously, or sign in to use a display name, reply and manage your contributions. Your email address is used only for account access and is never shown publicly.
- The game saves progress and offline lesson files in your browser. If you sign in, Firebase Authentication and Firestore handle the game account and cloud progress. The game currently loads typefaces from Google Fonts.
On guide pages, optional analytics remain off until you accept them. A random identifier is stored if you rate an article. The game uses device storage and offline caching when you play; its fonts are fetched from Google.
We do not sell anything about you, we do not share it for advertising, and there is no third-party advertising on this site.
Who is responsible
The data controller for this site is Bani Younes ENK, organisation number 934 103 424, Oslo, Norway.
You can reach us at privacy@muntligb1.com. That is the same address as muntligb1.com, because the same controller is behind both.
What we collect, and why
When you simply read a page
Serving a web page requires a server, and the server keeps a log. Those logs contain your IP address, the page you asked for, the time, your browser and operating system, and the page you arrived from. This happens whether or not you accept cookies, because without it the site cannot be delivered or kept secure.
Our host, Netlify, also turns those logs into visitor statistics for us: how many people visited, which pages they read, which country they came from, and which site referred them. This is worked out at the server, not in your browser. It sets no cookies, stores nothing on your device, and cannot follow you to any other website.
We rely on legitimate interest for both (GDPR Article 6(1)(f)) — delivering the site, keeping it available and secure, and understanding at a coarse level which guides are worth writing more of. We do not use any of it to build a profile of you or to identify you as a person, and you can object to it at any time by writing to us.
If you accept analytics cookies
We use Google Analytics 4 to understand readership in more detail than server logs allow.
Worth stating plainly rather than burying: it sets a client ID — a randomly generated identifier stored in your browser that lets Google recognise the same browser across visits. That identifier is what makes this tracking rather than simple counting. Alongside it, Google receives your approximate location — which for this property is resolved to city level, not just country — your device and browser type, which pages you viewed, and how you arrived.
This only happens if you actively accept. Analytics is off until you do, the script is not loaded and no data is sent. Declining costs you nothing; the site works identically either way.
The legal basis is your consent (GDPR Article 6(1)(a), and the cookie rule in the Norwegian Electronic Communications Act).
If you use the learning game
The game stores lesson progress and settings in your browser and caches lesson files for offline use. Guest progress stays on that device. If you create an account or sign in, Firebase Authentication handles your sign-in details and the game saves progress to a private record in Firebase Firestore. The game offers email and password, Google and Apple sign-in. Its account is separate from the site's Supabase community account. Signing out does not delete cloud progress. Contact privacy@muntligb1.com to request deletion of your game account and saved progress.
Audio recorded for listening back stays in the browser tab and is not uploaded by the game. Guided speech recognition may use your browser's speech service; its processing depends on the browser. The game does not save speech transcripts to your account. The game loads fonts from Google Fonts, so your browser contacts Google when those fonts are fetched.
You can collect your first three game badges without an account. To continue playing after that, you must create a free account or sign in. We process account details and saved progress to provide the account and sync your progress across devices.
If you join the newsletter
We use Brevo to manage the newsletter. When you submit the form, Brevo receives your email address and sends you a confirmation email. We use double opt-in: your address is added to the newsletter list only after you click the confirmation link.
We use the address only to send new guides and closely related updates from b1muntlig.no. Brevo also records the operational information needed to run email delivery, such as when you subscribed, whether a message was delivered, and — where email tracking is enabled — whether it was opened or a link was clicked. We do not use that information for advertising or sell it to anyone.
The legal basis is your consent (GDPR Article 6(1)(a)). You can withdraw it at any time using the unsubscribe link in an email or by writing to privacy@muntligb1.com. Withdrawing consent does not affect the lawfulness of messages sent before you withdrew it.
If you contact us
The contact form asks for your name, email address and message. Netlify receives the submission on our behalf so that we can read it and reply. We use those details only to deal with your enquiry; submitting the contact form does not add you to the newsletter.
We rely on legitimate interest (GDPR Article 6(1)(f)) — making it possible for readers to ask questions, suggest corrections and receive a reply. You can object or ask us to delete the message by writing to privacy@muntligb1.com.
If you comment on or rate an article
Comments are published immediately. We store the article, the display name you choose, your comment and its publication time. A name is optional and the site uses “Anonymous reader” if you leave it blank. We do not ask for or publish your email address. Please do not include health information, identity numbers or other sensitive details in a comment. You can ask us to remove a comment at privacy@muntligb1.com. Because comments are anonymous and have no verified contact details, include the article URL, displayed name and exact comment text so we can identify it; we may not be able to verify who originally posted it.
If you rate an article, your browser creates a random identifier for that article. The identifier is stored on your device and an article-specific one-way hash is stored with the rating, allowing one current rating per browser and article without linking ratings between articles. It is not used across other websites or joined to analytics data. You can change or remove your rating by pressing the button again. We also record the time and type of rating changes in a private moderator activity feed. These activity entries contain no browser identifier, voter hash, email address or IP address. The feed also shows public article comments and community posts and replies so moderators can review new reader activity.
Netlify processes the request and applies rate limits using connection information such as your IP address. We rely on legitimate interest (GDPR Article 6(1)(f)) to provide reader discussion and feedback while limiting spam and abuse.
If you use the community
You may publish a community post without signing in. In that case, Supabase stores the content and publication time without an account identifier, display name or email address, and the post appears publicly as “Anonymous.” Because it is not linked to an account, you cannot edit or delete it yourself later. You can ask us to remove it at privacy@muntligb1.com; include the page, exact text and approximate publication time so we can identify it. Replies require an account.
If you choose to create an account, we use Supabase for sign-in. You can sign in using an email link, Google or Apple. Supabase stores the account identifier, email address, sign-in provider and the technical records needed to keep the session secure. Google or Apple also processes the sign-in under its own privacy terms. Your email address is not placed in community posts or made visible to other members.
You choose a public display name. We store it with your posts and replies, together with their publication times. Community content is public, so do not include case numbers, identity numbers, health information or other private material. You can delete your own posts and replies, or delete your community profile and all of its content from the community page. Removing the community profile does not delete a separate MuntligB1 practice-app account that uses the same sign-in system; contact privacy@muntligb1.com if you want the underlying account removed as well.
We rely on performance of the service you request (GDPR Article 6(1)(b)) to create and operate an account when you choose one, and legitimate interest (Article 6(1)(f)) to publish community discussions and protect them from misuse.
Site moderators can review and remove community posts, including anonymous posts. Removing a post also removes its replies. Moderator access and the time they last marked posts reviewed are stored privately to help manage the community.
Cookies, and changing your mind
| Purpose | When is it stored? |
|---|---|
| Saving game progress and offline lessons | Yes, when you play the game |
| Remembering your consent choice | Stored in your browser the moment you choose, not before |
| Analytics | Only if you accept |
| Remembering an article rating | A random browser identifier is stored only after you rate an article |
Guide pages store nothing on your device before you make an analytics choice, rate an article or sign in to the community. The game stores progress and offline lesson files when you play.
You can change your analytics choice at any time using the cookie settings link in the footer of every guide page. Withdrawing takes the same single click that accepting did.
If you accepted earlier and then switch to Reject, the analytics cookies are deleted from your browser at that moment. We do not simply stop collecting and leave them sitting there.
You can clear browser storage, but doing so can remove guest progress saved by the game on this device. Sign in to the game if you want to save progress across devices.
Where the information goes
We use Netlify for hosting, Google for optional analytics, game fonts and Firebase services, Supabase for the community, and Brevo for the newsletter. Google or Apple also handles the game sign-in process if you choose that option. Brevo is operated by Sendinblue SAS in France; Brevo states that its database hosting is within the European Union. The community database is hosted in Supabase's EU region.
| Who | What they do | Safeguard for the transfer |
|---|---|---|
| Netlify, Inc. | Hosting, server logs, visitor statistics, comments and article ratings | EU–US Data Privacy Framework (certified, including the UK Extension and the Swiss–US framework) |
| Supabase, Inc. | Community authentication, profiles, posts and replies; database hosted in the EU | EU–US Data Privacy Framework and Supabase Data Processing Addendum |
| Google LLC | Optional analytics, game fonts, Firebase game accounts and cloud progress | EU–US Data Privacy Framework (certified, including the UK Extension and the Swiss–US framework) |
| Apple | Game sign-in, only if you choose Apple | Apple's applicable privacy terms |
| Sendinblue SAS (Brevo) | Newsletter signups, contact-list storage and email delivery | EU-based processor; Brevo says its databases are hosted in France, Germany and Belgium. Its DPA governs subprocessors and uses appropriate safeguards where a transfer outside the EEA applies. |
Netlify's and Google's participations were checked against the official Data Privacy Framework list at dataprivacyframework.gov. If either ever ceases to participate we will move that transfer to standard contractual clauses and say so here. Brevo's current storage information is published on its data-storage page. Where standard contractual clauses apply, you can ask us for a copy by writing to privacy@muntligb1.com.
We do not sell your information.
How long it is kept
- Server logs and visitor statistics: Netlify does not publish a fixed retention period for these. They are kept for as long as they are needed to deliver and secure the site, and no longer.
- Analytics event data: 2 months.
- Analytics user data: 14 months, reset each time the same browser returns.
- Newsletter data: kept while you remain subscribed. If you unsubscribe, Brevo retains the minimum suppression record needed to ensure we do not email you again. You can ask us to delete the contact record entirely.
- Contact messages: normally deleted within 12 months after the enquiry is closed, unless we need to keep them longer to establish, exercise or defend a legal claim.
- Public comments: kept while the article and its discussion remain published, unless you ask us to remove yours or we remove it to prevent abuse.
- Article ratings: kept while the article remains published or until you remove or replace the rating from the same browser.
- Anonymous rating activity: the time and type of previous rating changes are kept while the article remains published, without a reader or browser identifier.
- Signed-in community content: kept while your community profile remains active. You can delete individual posts and replies or remove the profile and all of its content from the community page.
- Anonymous community posts: kept while the discussion remains published, unless you ask us to remove one or we remove it to prevent abuse.
- Your consent choice: stored in your own browser until you clear it or change it.
- Game progress: guest progress remains on your device until you clear browser storage. Account progress remains in Firebase until you request deletion.
Your rights
Under the GDPR you can ask us to tell you what we hold about you, correct it, delete it, restrict how we use it, or object to us using it. You can also ask for a copy in a portable format, and where we rely on consent you can withdraw it at any time.
For a guide reader who has not joined the newsletter, rated an article or used an account, we usually hold only the information described in the hosting section. Comments, ratings, community accounts and newsletter subscriptions add the information described above. A game account also includes its sign-in details and saved cloud progress. Ask about your data or request deletion at privacy@muntligb1.com; we will respond within one month.
If you are unhappy
You can complain to the Norwegian Data Protection Authority, Datatilsynet, at datatilsynet.no. You can complain to them directly; you do not have to come to us first, though we would rather have the chance to put something right.
Changes
If we change what we collect, we will update this page and change the date at the top. If the change is significant, we will say what changed rather than quietly replacing the text.