Polyfrog Cookie Notice
Version: 20 November 2026 (the publication date)
Published at: polyfrog.io/cookies
Summary
- Polyfrog uses only cookies and browser storage that are needed to provide the service you ask for: signing in, security, the Beta invitation, your own settings and the answers in a test you have not handed in yet.
- We use no analytics, advertising or tracking cookies, and no third-party trackers. The app sends no reports about what you look at.
- Because we use only what is strictly necessary, we do not ask for cookie consent. The law does not require consent for this kind of storage.
- If you choose to sign in with Google, Google uses its own cookies. Google is responsible for them.
- If you choose to play a YouTube video in a lesson, YouTube (Google) may store or read information in your browser. Nothing is loaded from YouTube before you press play.
1. What cookies and browser storage are
A cookie is a small text file that a website stores in your browser. Websites can also store information in your browser in other ways, for example in "local storage", or read information from your device with scripts. The rules are the same for all of these. In this notice, "storage" means all of them.
2. When storage is allowed without consent
The Norwegian Electronic Communications Act (ekomloven § 3-15) says that a service may store or read information on your device only if you are told about it and have given consent. There are two exceptions. Consent is not needed when the storage is only for sending a communication over the network, or when it is strictly necessary to provide a service that you have explicitly asked for. Everything Polyfrog stores or reads falls under the second exception. You still have the right to know what it is, and this notice tells you.
3. The website polyfrog.io
The website stores nothing in your browser. It is hosted by Cloudflare. Pages that show our email address load a small Cloudflare script that hides the address from spam programs and shows it to you; it stores nothing in your browser. The website loads no other scripts or fonts from other companies until you open the waitlist form. The form then loads Cloudflare Turnstile, a check that tells people from automated programs. Turnstile reads technical details of your browser and connection, such as the browser type and IP address, and sets no cookies. This is strictly necessary to protect the form from automated sign-ups. If you join the waitlist, the form sends your email address to us without cookies.
4. The learner app
4.1 Cookies set by Polyfrog
The public service uses names that start with __Host-. The Beta test environment uses names that start with __Secure-.
| Name | Purpose | How long | Why it is strictly necessary |
|---|---|---|---|
__Host-pf_learner_session / __Secure-pf_learner_session |
Keeps you signed in | 14 days | Without it you cannot stay signed in |
__Host-pf_csrf / __Secure-pf_csrf |
Protects your Account against forged requests from other websites | Until you close the browser | Security for the service you use |
__Host-pf_invitation / __Secure-pf_invitation |
Remembers your Beta invitation from the moment you open the invitation link until you sign up | Up to 7 days, or until the invitation expires if that is sooner. Deleted when used | Without it the invitation is lost before sign-up |
All these cookies are protected against reading by scripts and are sent only over encrypted connections.
4.2 Information stored in your browser by the app
| Name | Type | What it holds | Purpose | How long |
|---|---|---|---|---|
pf_onboarding |
Local storage | Your answers during sign-up: native language, the language you learn, your level, reasons, genres, picked books, daily goal and age range | Keeps your answers until your Account is created, also when you sign in with Google on the way | Deleted when your Account is created, or when you choose an age range under 16 |
pf_prefs |
Local storage | Text size, sound effects, "download only on Wi-Fi" | Remembers the settings you chose | Until you change them or clear your browser |
pf_active_enrolment |
Local storage | Which of your courses is active | Opens the course you chose | Until you change course or clear your browser |
pf_app_language |
Local storage | The language the app is shown in | Shows the app in your language | Until you sign out, change the language or clear your browser |
pf_test_draft:… |
Local storage | Your answers in a test you have not handed in yet | Keeps your answers if you leave the test and come back | Deleted when you hand in the test; otherwise until you clear your browser |
| Staff tools and old keys | Local storage | reader-generator-width: width of a staff panel, used only by Polyfrog staff. pf_learner_auth: left by earlier app versions, deleted by the app when it starts |
Staff layout; clean-up | Until cleared; deleted at once |
4.3 Browser notifications and the service worker
If you allow notifications, the app installs a small background script (a "service worker", /sw.js). It only shows the reminders you asked for. It stores no pages or data. Your browser gives us an address at its notification service, which we store so that we can send you reminders. You can turn notifications off in Settings or in your browser.
4.4 Fonts
The app's fonts are stored on our own servers. Loading them sends no data to other companies.
5. Sign in with Google
5.1 The sign-in screen shows our own "Continue with Google" button. Google's sign-in script from accounts.google.com is loaded only when you choose it. Google then shows its sign-in window and may store or read its own cookies in your browser, for example to know whether you are already signed in to Google and to protect the sign-in. Google is responsible for these cookies as a separate controller under its own policies: https://policies.google.com/privacy and https://policies.google.com/technologies/cookies. After the sign-in window has been shown, Google's script may also set the cookie g_state on the app's own address. It remembers whether you closed Google's sign-in prompt, so that Google does not show it again too often. Google sets its content and lifetime.
5.2 Sign in with Google is available in the Beta and on the public service.
6. Videos from YouTube
6.1 Some lessons contain a video from YouTube. The lesson first shows our own placeholder with a play button. Until you press it, nothing is loaded from YouTube or Google.
6.2 When you press play, the app loads YouTube's video player from youtube-nocookie.com, YouTube's privacy-enhanced mode. Your browser then connects to YouTube, which receives your IP address and information about your browser and the video. YouTube may store or read information in your browser, for example to play the video and remember your player settings. Google Ireland Limited is responsible for this as a separate controller under its own policies: https://policies.google.com/privacy and https://policies.google.com/technologies/cookies.
6.3 If you do not want this, do not press play. The rest of the lesson works without the video.
7. Payments
When you buy a Paid Plan, you go to a payment page run by Stripe on Stripe's own website. Stripe uses its own cookies there, for example to process the payment and prevent fraud. Stripe is responsible for them: https://stripe.com/privacy and https://stripe.com/legal/cookies-policy. Payments are not available during the Beta.
8. Emails
Our emails contain no tracking pixels and no tracked links. Open and click tracking is switched off for every email we send.
9. How to control storage
You can delete cookies and other stored information in your browser settings at any time. If you block or delete Polyfrog's cookies, you are signed out and cannot sign in again until you allow them. If you delete local storage, the app forgets your settings, its language and the answers in a test you have not handed in yet.
10. Changes and contact
We update this notice when we change what we store. If we ever want to use storage that is not strictly necessary, we will ask for your consent first, and saying no will be as easy as saying yes. Questions: [email protected].