Polyfrog Privacy Policy
Version: 20 November 2026 (the publication date)
Published at: polyfrog.io/privacy
Summary
- POLYFROG AS in Norway is responsible for your personal data in Polyfrog.
- We use your data to run your Account and your learning. We do not sell your data. We do not show ads. We use no third-party analytics and no advertising trackers.
- Your data is stored with Google Cloud in the EU. The website polyfrog.io and its waitlist run on Cloudflare; the waitlist is stored in the EU.
- Some features use AI from OpenAI, which processes the data in the USA: word translations, grading of written answers, the AI tutor and speech to text. We send what the feature needs, but not your name, email address or Account ID. OpenAI does not use this data to train its models.
- We do not keep your voice recordings. They are turned into text, and we keep only the text.
- In leagues, other learners see only your nickname and your weekly points. If you write a book review, they see it with your nickname.
- You can download your data and delete your Account yourself in Settings.
- You can complain to the Norwegian Data Protection Authority (Datatilsynet).
1. Who is responsible
1.1 The controller for your personal data is:
POLYFROG AS
Organisation number 938 683 123
Vollsåsen terrasse 18, 3086 Holmestrand, Norway
Email for privacy questions: [email protected]
1.2 Data protection officer. We have not appointed a data protection officer, because the law does not require one for Polyfrog today (GDPR Article 37(1)). Our managing director, Maksym Yakovliev, is responsible for privacy questions.
2. What this policy covers
2.1 This policy applies when you:
- visit our website polyfrog.io;
- use the learner app at app.polyfrog.io;
- receive emails or notifications from us; or
- write to us.
2.2 Our Cookie Notice (polyfrog.io/cookies) explains what we store in your browser. Our Terms of Service (polyfrog.io/terms) are the agreement for using Polyfrog. This policy is information for you. You do not have to accept it.
3. The personal data we process
3.1 Data you give us:
- Account: email address; password (we store only a secure hash of it); the age range you choose; your native language; your country of residence and when you last changed it; which version of the Terms you accepted and which version of this policy we showed you, and when; and your nickname if you change it.
- Learning choices from sign-up: the language you learn, the level you think you have, why you learn, the reading genres you like and their order, your daily goal, and the books you picked.
- What you do while learning: your answers to exercises, questions about what you read, topic tests and level tests (typed or spoken), including when you choose "I don't know" or skip an exercise; the reading goal you choose for a learning session; words you look up, books you save, hide or rate with stars, the reviews you write about books, the reviews you report, and your chats with the AI tutor.
- Voice: your recordings when you speak an answer or speak in a voice chat. We do not keep them (section 5).
- Settings: the language of the app, reminder time, time zone, which emails and notifications you want, whether you take part in leagues, and display settings.
- Messages to us: what you write when you contact us.
3.2 Data we create when you use Polyfrog:
- Progress: learning sessions (which part of the course you practised, how far you got, and when), reading sessions (book, position, reading time, reading speed), a record of your answers and their results, vocabulary and review schedule, estimated level per language, the grammar you should review, course progress, topic-test and level-test results, points (XP), streaks, badges, challenges and league results.
- AI tutor chats: the text of your turns (transcribed or typed), the tutor's replies, the tutor's correction of each of your turns, the summary at the end, the passage you talked about, and the computer-made audio of the tutor's replies when they are read aloud.
- Use of the Library: when you open the Library home page; what you search for; which book pages you open; which books you save or remove from your saved books, add to your reading plan or hide. (Reading itself is part of your progress above.)
- Usage records: each AI request we make for you and your voice minutes per month.
- Notifications: which reminders and summaries we sent you and when.
- Technical data: sign-in sessions; your IP address, which our servers use for a short time to stop misuse; and web server logs with IP address, time, page address, browser type and the page you came from.
3.3 Data we receive from others:
- Google, if you choose "Continue with Google": Google sends us a signed message about your Google account. It contains your Google account ID, email address, name, profile picture address and language. We keep only the Google account ID and the email address. We do not store your name or picture.
- Stripe, our payment provider, when you buy a Paid Plan: messages about your subscription and payments. They can contain your name, email address, billing address, amount, currency and payment status.
3.4 What we do not collect. We do not ask for your date of birth. We do not see or store your card number. We do not collect your precise location, contacts or photos. We store the time zone your browser reports, for reminders. We do not use your voice to identify you.
3.5 What you must give us. To create an Account, you must give an email address and a password (or use Google), your age range and your native language, and accept the Terms. Without these, we cannot create an Account. Everything else is your choice, but some features do not work without it, for example voice features without a microphone.
4. Why we use your data, and our legal basis
The law allows us to use personal data only when we have a legal basis. The table shows our purposes, the data we use, and the legal basis under the General Data Protection Regulation (GDPR) Article 6(1).
| Purpose | Data | Legal basis |
|---|---|---|
| Create your Account, let you sign in and keep your Account secure | Email, password hash, Google account ID, nickname, native language, sessions, plan | Contract (6(1)(b)) |
| Check that you are 16 or older, apply the rules for 16–17-year-olds (no purchases, leagues off at the start) | Age range | Legitimate interest (6(1)(f)): only people who meet our age rules should have an Account or buy |
| Show you the books that are free of copyright in your country, and apply the consumer rules of your country to a purchase | Country of residence | Contract (6(1)(b)) |
| Show your book reviews to other learners and handle reports about reviews | Review text, stars, nickname, the language and level of the edition you read, reports (who reported which review, and when) | Contract (6(1)(b)) |
| Keep a record of the Terms you accepted and the policy we showed you | Versions, time | Legitimate interest (6(1)(f)): to show what you agreed to and what you were told |
| Build your course and reading plan, and suggest books | Learning choices from sign-up, level, genres, progress | Contract (6(1)(b)) |
| Provide the learning service: learning sessions, reading, exercises, topic tests, level tests, vocabulary, progress, XP, streaks, badges | Learning data and progress | Contract (6(1)(b)) |
| Translate words you tap | The word and its sentence from the book (to OpenAI); the word in your vocabulary | Contract (6(1)(b)) |
| Grade free written answers with AI | Your written answer and the model answers (to OpenAI) | Contract (6(1)(b)) |
| Speech to text, voice chats with the AI tutor, and the tutor's voice | Recordings (to OpenAI, not kept by us), transcripts, chat lines, corrections, summaries, the passage, your level, your native language; the tutor's reply text (to Google) | Contract (6(1)(b)) |
| Keep and process sensitive things you mention about yourself in a tutor chat (special categories, such as health or religion) | Chat text and the tutor's replies that contain them | Your explicit consent (GDPR Article 9(2)(a)), given with the tick box before your first chat (section 5.6) |
| Improve our exercises, translations and courses | Your answers and results, combined with other learners' answers, without your name or email where the work allows it | Legitimate interest (6(1)(f)): to find exercises and translations that are wrong, unclear or too hard. We never sell your answers and never let other companies train AI models on them |
| Leagues | Nickname, weekly points per language, league tier and group | Legitimate interest (6(1)(f)): weekly competition motivates learning. You can turn leagues on or off in Settings |
| Daily reminder, streak alert and weekly summary, by email or browser notification | Email, time zone, reminder time, your settings, push subscription, notification log, progress figures for the summary | Contract (6(1)(b)): features you choose in sign-up and in Settings. Browser notifications only after you allow them in the browser |
| Emails after some days without learning, and new-book alerts | Email, settings, notification log | Consent (6(1)(a)): only if you turn them on |
| Plan limits and cost control | AI usage records, voice minutes | Contract (6(1)(b)) for the limits; legitimate interest (6(1)(f)) to control costs and stop misuse |
| Understand how the Library is used and improve its suggestions | Library records (what you open, search for, save, add to your reading plan or hide); saved, hidden and rated books | Legitimate interest (6(1)(f)): to make the Library better. Saved, hidden and rated books are also part of the service you use (contract) |
| Sell and manage Paid Plans | Stripe customer and subscription numbers, plan, status, period end, payment messages from Stripe | Contract (6(1)(b)) |
| Bookkeeping | Payment records (date, type, amount, currency, Stripe references) | Legal obligation (6(1)(c)): the Norwegian Bookkeeping Act (bokføringsloven) |
| Answer your questions and requests, including privacy requests | Your messages, Account data needed to help you | Contract (6(1)(b)); legal obligation (6(1)(c)) for privacy requests |
| Keep the Service secure and prevent misuse | IP addresses, server and application logs, sessions | Legitimate interest (6(1)(f)): security and stable operation |
| Record staff access to learner data | Staff actions with the learner concerned and the reason | Legitimate interest (6(1)(f)): accountability and security |
| Establish or defend legal claims | Relevant records | Legitimate interest (6(1)(f)) |
| Website waitlist: one email about the launch and the Beta | Email, time, the text you agreed to | Consent (6(1)(a)) |
Your right to object. When we rely on legitimate interest, you can object to the processing (section 15). For leagues, you can simply turn them off in Settings.
Learning emails are not advertising. The daily reminder, the streak alert and the weekly summary are about your own learning. They contain no offers and no prompts to buy. You choose the daily reminder and the weekly summary during sign-up. You can turn all three off in Settings and with the link in every email. Emails after some days without learning and new-book alerts are off unless you turn them on. We send no newsletters or advertising emails. If we ever want to, we will ask for your consent first.
5. AI features and voice
5.1 What we send to OpenAI. We use OpenAI's API for these features. We send only what each feature needs:
| Feature | What we send |
|---|---|
| Word translations | The word you tapped, its sentence from the book, and the language to translate into |
| Grading of written answers | Your written answer and the model answers |
| Voice chat with the AI tutor | The passage, your estimated level, the conversation so far (your turns, the tutor's replies and corrections) and the name of your native language |
| Speech to text | Your recording (at most 60 seconds) and the language you speak |
We do not send your name, email address, nickname or Account ID to OpenAI.
5.2 What OpenAI does with it. OpenAI processes this data for us as our processor, under a data processing agreement with OpenAI Ireland Ltd. According to OpenAI, data sent to its API is not used to train or improve its models unless the customer opts in. We have not opted in. OpenAI keeps prompts and replies in logs for abuse monitoring for up to 30 days, or longer where the law requires it or where OpenAI considers it necessary to protect its services or others from harm. OpenAI states that it keeps no data from speech-to-text requests.
5.3 Your voice recordings. When you speak, your browser sends the recording to us, and we send it to OpenAI to be turned into text. We do not store the recording. For a spoken answer, the text fills the answer field, and we keep it only if you submit the answer. For a voice chat, we keep the text of your turns as part of the chat. We do not use your voice to identify you.
5.4 The tutor's voice. The tutor's replies are read aloud where the service offers voice: in the Beta now, and on the public service when it is switched on there. When they are read aloud, we send the text of the reply and its language to Google Cloud Text-to-Speech. The reply can repeat words you wrote or said. Google states that it does not log the text or audio. We store the audio with the chat, so that you can play it again.
5.5 How long chats are kept. We delete each voice chat, with its transcripts, corrections, summary and the tutor's audio, 12 months after it started. You can delete any chat in the app at any time: the open chat, or any earlier chat from the list of your past chats. If you chat without having ticked the consent box in 5.6, we keep the content of that chat (your lines, the tutor's replies and corrections, the summary and the tutor's audio) only until the end of the day (UTC) on which the chat ends, and then delete it; only the voice minutes and the record of the AI request stay. A chat you leave open counts as ended at the end of the day after your last line. If you delete your Account, all chats are deleted with it (section 13). When a chat is deleted, copies of it in our backups and disk snapshots expire as section 13 describes.
5.6 Sensitive information. The tutor is for talking about the book. Please do not tell it about your health, religion, political views, sex life or other sensitive matters, or give it other people's personal data. The tutor does not ask about these things and steers back to the passage. If you share such information anyway, we use it only for that chat (to answer and correct you, and to keep the chat for you as described in 5.5), we do not analyse it for any other purpose, and you can delete the chat in the app.
Your explicit consent. Before your first chat, the app asks you once to tick this box: "If I mention sensitive things about myself, Polyfrog keeps them with the chat for up to 12 months and they are sent to OpenAI (and the tutor's lines to Google text-to-speech) to answer and correct me. I can withdraw this in Settings and delete any chat." This is your explicit consent under GDPR Article 9(2)(a). You can still chat without ticking; the app then asks again next time, and that chat is kept only until the end of the day (UTC) on which the chat ends (5.5). You can withdraw your consent at any time in Settings → Privacy. When you withdraw it, we delete your earlier chats, because they may contain what you agreed to. Before that, the app warns you and links to "Download my data", so that you can keep a copy first.
When we read a chat. We read a chat only if you report a problem with it, or to investigate misuse or a security problem. We do not use tutor chats to check the quality of exercises.
5.7 Shared AI content. Exercises and word translations made by AI are shared between learners. Exercises and test questions are written from our course material and books, not from data about you. A word translation is stored together with the book sentence, but without any link to you.
6. What other learners see
6.1 Polyfrog has no public profiles. Other learners can see you only in leagues and next to your book reviews. In your league group of up to 30 learners, they see your nickname and your points in that language this week. They never see your email address.
6.2 Every Account gets a generated nickname, such as "Quiet Otter 42". You can change it in Settings. When you do, the app reminds you that other learners in your league see this name and that you should not use your full real name.
6.3 If you write a review of a book, other learners who can see the book see the review with your nickname, your stars and the language and level of the edition you read. They do not see who reported a review. You can change or delete your review at any time.
6.4 If you are 18 or older, leagues are on when you start. If you are 16 or 17, leagues are off until you turn them on. You can turn leagues on or off at any time in Settings.
7. Payments
7.1 Payments are handled by Stripe. When you buy, Stripe collects your card or other payment details and billing information on its own payment page. We never receive your full card number.
7.2 We give Stripe your Account ID, the Plan you chose and, the first time you buy, your email address. Stripe sends us messages about your subscription and payments.
7.3 Stripe processes payment data for us as our processor. Stripe is also a separate controller for some purposes of its own, such as preventing fraud, checks against money laundering, and the requirements of banks and authorities. For those purposes, and if you choose to save your payment details with Stripe's own services such as Link, Stripe's privacy policy applies: https://stripe.com/privacy
7.4 When we purge your data, at most 30 days after you delete your Account, we delete your customer record at Stripe. Stripe keeps its invoice records as its own legal obligation. We keep only the bookkeeping fields of each payment (section 13).
8. The closed beta
8.1 When Polyfrog runs a closed beta, the Closed Beta Terms say which extra data the beta uses.
9. Who receives your data
9.1 We use the following providers ("processors"). They process data only on our instructions and under a data processing agreement as required by GDPR Article 28.
| Provider | What they do for us | Data | Where | Transfer safeguard |
|---|---|---|---|---|
| Google Cloud EMEA Ltd (Ireland) | Hosting: servers, database, file storage, backups, secret storage | All data we store | EU | Data stored in the EU. Access from outside the EEA for support or operations is covered by Google's Cloud Data Processing Addendum: the EU–U.S. Data Privacy Framework (Google LLC is certified) or EU standard contractual clauses |
| OpenAI Ireland Ltd. | AI: translations, grading, tutor replies, speech to text | As in section 5.1 | USA | OpenAI Ireland Ltd. passes the data to OpenAI companies in the USA under EU standard contractual clauses (OpenAI Data Processing Addendum, section 4.1). OpenAI was not on the Data Privacy Framework list when we checked on 29 October 2026 |
| Cloudflare, Inc. | Hosting the website polyfrog.io, storing its waitlist, and Turnstile, the check against automated sign-ups on the waitlist form | Website requests (IP address, time, page, browser); technical details of your browser and connection for the Turnstile check; waitlist emails as in section 18 | Waitlist: stored in the EU. Website pages: Cloudflare's network, from the data centre nearest to you, which can be outside the EEA | EU–U.S. Data Privacy Framework (Cloudflare, Inc. is certified) and EU standard contractual clauses (Cloudflare Data Processing Addendum) |
| Google Cloud (Text-to-Speech) | The tutor's voice, where the service offers voice | The tutor's reply text and its language | Google's global service; can be outside the EEA | EU–U.S. Data Privacy Framework (Google LLC) or EU standard contractual clauses (Cloud Data Processing Addendum) |
| Mailgun (Sinch group) — Mailgun Technologies, Inc. | Sending emails | Your email address, the subject and content of the email, the unsubscribe link | EU (Germany and Belgium). Support staff in the USA may have access | EU–U.S. Data Privacy Framework (Mailgun Technologies, Inc. is certified) and EU standard contractual clauses (Sinch Data Processing Agreement) |
| Stripe Payments Europe, Ltd. (Ireland) | Payments, subscriptions, receipts | Account ID, Plan, email; payment and billing details that Stripe collects | EEA and USA | EU–U.S. Data Privacy Framework (Stripe, LLC is certified) and the Stripe Data Processing Agreement |
| Google Workspace (Gmail), Google Cloud EMEA Ltd (Ireland) | Our email inbox | Messages you send us | Google's global service | EU–U.S. Data Privacy Framework (Google LLC) or EU standard contractual clauses |
| Fiken AS (Norway), our accounting system | Bookkeeping | Payment totals per Stripe payout, with dates and references; no customer names | Norway | No transfer |
9.2 Browser notification services. If you allow notifications, your browser gives us an address at its notification service, for example Google (Chrome), Mozilla (Firefox), Apple (Safari) or Microsoft (Edge). We send the notification to that address. The content is encrypted so that the notification service cannot read it. Your browser's provider decides which service is used.
9.3 Other learners see your nickname and weekly points in leagues, and your book reviews (section 6).
9.4 Others. We may give data to authorities, courts or advisers such as our lawyer when the law requires it or when it is needed to establish or defend a legal claim. If POLYFROG AS or Polyfrog is sold or merged, data may pass to the new owner, who must follow this policy. We will tell you before this happens.
9.5 We do not sell your personal data, and we do not share it with advertisers.
10. Separate controllers
10.1 Sign in with Google. If you choose "Continue with Google", Google shows its sign-in window and checks your Google account. Google does this as a separate controller under its own privacy policy: https://policies.google.com/privacy. For users in the EEA, the Google company responsible is Google Ireland Limited. Google may use its own cookies for this (see the Cookie Notice). We receive only the information described in section 3.3.
10.2 Stripe, for its own purposes as described in section 7.3.
10.3 Videos from YouTube. Some lessons contain a YouTube video, which loads only when you press play. YouTube then receives your IP address and information about your browser and the video you play, and may store or read information in your browser (see the Cookie Notice). Google Ireland Limited does this as a separate controller under its own privacy policy: https://policies.google.com/privacy.
11. Transfers outside the EEA
11.1 We store your data in the EU. Some providers process data in the USA: OpenAI for the AI features, and in some cases Google, Stripe, Mailgun and Cloudflare (the website and its waitlist form) (section 9).
11.2 For transfers to companies certified under the EU–U.S. Data Privacy Framework, the European Commission has decided that the protection is adequate (Decision (EU) 2023/1795). The decision applies in Norway through the EEA Agreement (EEA Joint Committee Decision No 169/2024 of 5 July 2024, OJ L, 2024/2568). For other transfers, including to OpenAI, the standard contractual clauses adopted by the European Commission in 2021 are used (Decision (EU) 2021/914, https://eur-lex.europa.eu/eli/dec_impl/2021/914/oj). For OpenAI, they are in OpenAI's Data Processing Addendum, section 4.1 (https://openai.com/policies/data-processing-addendum/). We have assessed the transfer to OpenAI and the protection it gets. You can also ask us about the safeguards.
12. Automated decisions and profiling
12.1 Polyfrog uses automated processing to run your learning:
- it estimates your language level from your own assessment and your answers, and updates it as you learn;
- it grades your answers, partly with AI;
- it chooses what you practise in each learning session, including the grammar you should review, from your answers;
- it decides whether you pass a topic test or level test, which unlocks course topics and gives points;
- it suggests books and orders the Library by your level, your genres and popularity;
- it moves you up or down between league tiers at the end of each week; and
- it applies the usage limits of your Plan.
12.2 This is profiling, because it uses your learning data to estimate your level and choose content for you. None of these decisions has legal effects for you or affects you in a similarly significant way. They change what you learn next, your progress labels and your points. They are not certificates. So the special rules in GDPR Article 22 on automated decisions do not apply.
12.3 If you think a grade, a test result or a level is wrong, write to us. A person will look at it.
13. How long we keep data
| Data | How long |
|---|---|
| Account and learning data | As long as you have an Account. After you delete your Account, at most 30 days (13.1) |
| Voice recordings | Not kept by us. Deleted as soon as they are turned into text |
| Voice chats (transcripts, corrections, summaries, the tutor's audio) | 12 months after the chat started, or earlier if you delete the chat or your Account, or withdraw your chat consent. A chat held without the consent ticked: until the end of the day (UTC) on which the chat ends |
| Data export files | 7 days after they are made |
| Sign-in sessions | 14 days, or until you sign out; expired sessions are deleted |
| Library records (what you open, search for, save, add to your reading plan or hide) | 12 months |
| AI usage records, voice minutes, notification log, push subscriptions | As long as you have an Account (push subscriptions also end when you turn notifications off) |
| Record of the Terms you accepted and the policy we showed you | As long as you have an Account |
| Payment records (date, type, amount, currency, Stripe references) | 5 years after the end of the financial year (bokføringsloven § 13). When we purge your data (at most 30 days after you delete your Account), we remove everything else, including the copy of Stripe's message |
| Your customer record at Stripe | Deleted when we purge your data, at most 30 days after you delete your Account |
| What Stripe keeps for its own purposes | Stripe decides this under its privacy policy |
| Database backups (public service) | 30 days, and 7 more days in the storage provider's deletion buffer. Your data therefore leaves our backups at most 67 days after you delete your Account (30 days before deletion, then up to 37 days in backups) |
| Server disk copies (snapshots) | 7 days |
| Web server logs | 14 days |
| Application logs | Overwritten automatically when they reach 30 MB per service |
| Staff audit log | 2 years |
| Emails you send us | 3 years after the last message in the case |
| Waitlist sign-up | Until we send the launch email, then deleted; earlier if you ask |
| Data at OpenAI | Up to 30 days in abuse-monitoring logs, or longer as described in 5.2; none for speech to text (according to OpenAI) |
| Addresses that bounced or turned off our emails | Kept on our email provider's block list so that we do not email them again; removed when we purge your data |
13.1 What happens when you delete your Account. Your Account stops working at once, and you are signed out everywhere. An active Subscription ends. The deletion is final, and your email address can be used again at once. We keep the rest of your data for at most 30 days, only so that we can finish open matters such as a refund, a payment dispute or a report of misuse, and then delete it from our database. Some data stays longer, as the table shows: payment records required by bookkeeping law, the staff audit log, and backups until they expire. Data you or we delete, including deleted chats, also stays in backups and disk snapshots only until they expire as the table shows.
13.2 We keep an Account as long as it exists. We do not delete inactive Accounts automatically at present.
13.3 We may keep statistics that cannot be linked to you after your Account is deleted.
14. Children
14.1 Polyfrog is for people aged 16 and older. We ask for your age range when you sign up, and we do not create Accounts for people under 16. If you choose an age range under 16, nothing is sent to us, and the app deletes your sign-up answers from your browser.
14.2 If we learn that an Account belongs to someone under 16, we delete it. A parent or guardian can write to us about this.
14.3 For learners aged 16 and 17: Paid Plans are only for people aged 18 or older, so the app does not let you buy one. Leagues are off until you turn them on, and others see only your nickname. We send no advertising.
15. Your rights
15.1 You have these rights:
- Access: to know what data we have about you and get a copy.
- Correction: to have wrong data corrected. You can change your nickname, learning choices and settings in the app. For other data, write to us.
- Deletion: to have your data deleted. Use "Delete account" in Settings → Account, or write to us.
- Restriction: to ask us to limit how we use your data while a question is being clarified.
- Data portability: to get the data you gave us in a machine-readable format.
- Objection: to object to processing based on legitimate interest. We then stop, unless we have compelling legitimate grounds that override your interests or need the data for a legal claim.
- Withdraw consent: where we use consent (sensitive things in tutor chats — Settings → Privacy; emails after some days without learning; new-book alerts; the waitlist), you can withdraw it at any time. This does not affect what we did before. You can turn browser notifications off at any time in Settings or in your browser.
15.2 How to use your rights.
- Download my data: in Settings → Account, "Download my data" downloads one file (JSON) at once. It contains your profile, learning choices, progress, learning sessions, reading history, your answers and their results, vocabulary, points, badges, leagues, chats, course data, reminders and settings. It contains no passwords or other security data. The file is also kept on our server for 7 days and then deleted. If you want data that is not in the file, write to us.
- Delete account: in Settings → Account, "Delete account". See section 13.1.
- Everything else: write to [email protected]. We may ask you to confirm that the request is yours. We answer within one month. If the request is complex, we may extend this by up to two more months and tell you why.
15.3 Using your rights is free. If a request is clearly unfounded or excessive, we may refuse it or charge a reasonable fee, and we explain why.
16. Security
We protect your data with technical and organisational measures. Connections and stored data are encrypted, passwords and sign-in sessions are stored only as secure hashes, and access to our servers and database is limited to the people and parts of the service that need it. Staff cannot change your learning data or act as you. When staff open a single learner's page, or change a learner's account, invitations or the service's settings, it is recorded in an audit log.
No system is completely secure. If a breach puts your rights at high risk, we tell you without undue delay.
17. Cookies and browser storage
We use only the cookies and browser storage needed to run Polyfrog. Our website has no cookies. If you sign in with Google or play a YouTube video in a lesson, Google uses its own storage, as described in the Cookie Notice: polyfrog.io/cookies.
18. Website waitlist
If you join the waitlist on polyfrog.io, we store your email address, the time and the text you agreed to: that you want emails about Polyfrog's launch and beta access. The list is stored with Cloudflare in the EU. We send one email when we launch, and then delete the list. You can withdraw at any time by writing to [email protected], and we delete your address. The waitlist is separate from Accounts.
19. Changes to this policy
We update this policy when we change how we handle personal data. If a change is important for you, we tell you by email or in the app before it takes effect. The date at the top shows which version applies. Earlier versions are available on request.
20. Complaints
If you think we handle your personal data wrongly, please write to us first at [email protected]. You also have the right to complain to the Norwegian Data Protection Authority (Datatilsynet): https://www.datatilsynet.no. If you live in another EEA country, you can also complain to the data protection authority there.