Privacy Policy

Knowledge Loop is operated by Knowledge Loop Limited, a company registered in England and Wales. When you use the app we decide what is collected and why, which makes us the data controller for it under UK data protection law.

Write to enzo@k-loop.app about anything on this page. It reaches a person, not a queue.

Knowledge Loop has no sign-up form. The first time you open it, the app creates an anonymous account: a random identifier and nothing else. No email address, no name, no phone number, no social login. Everything you learn is stored against that identifier.

Connecting an email address is optional and only ever does one thing: it lets the same account be reached from another device, and survive this one. We send a six-digit code to the address to prove you can read it, and from then on the address is stored with the account.

The trade-off is real in both directions. Without an email we hold almost nothing that identifies you, and we also cannot give the account back if the device is lost.

Nearly all of it is the app remembering what you did in it, because an app that tracks a streak and schedules a review has to. Here is the whole of it, by category.

Your account

An account identifier, when it was created, and the email address if you connected one. A display name and a username, both visible to other learners. Optionally a name to print on certificates. The avatar, colour, background and title you picked, and the switches controlling what your profile shows.

Your learning

Topics you follow, including any you add yourself. How you rated each factoid (interested, already knew, not for me). Courses you started, chapters you finished, and where you stopped. Review items, when they are next due and how you graded them. XP, level, streak, badges, daily activity, learning time per day, gems earned and spent, and how much of each day's generation allowance you have used.

Other learners

Friendships and friend requests, invites you accepted, journeys you shared or were sent, and your place on the weekly league board.

What you write

Messages to the in-app coach, explanations you type when mastering a course, and reports you file about wrong or unpleasant material, which carry a copy of the material as it looked when you reported it.

Two coarse signals from your device

The time zone and the two-letter region from the device's own settings, sent when the app starts. The time zone is what rolls your streak on your day rather than on a server's, the region is what picks the currency you are quoted, and both give the writing model a rough sense of where a reader is. There is no permission prompt because there is nothing precise here: no GPS, no address lookup, nothing narrower than a country and a zone.

Payments

Whether you are on the free or premium plan, when the period runs to, the identifiers our payment provider uses for you, and a record of purchases. We never see or store your card number.

Settings that never leave the device

Reminder times and days, sound, theme and narration preferences are stored by the app on the device itself and are not sent to us.

Technical records

The services that host the app keep ordinary server logs, which include IP addresses and the time of a request, so that faults and abuse can be investigated. We do not build profiles from them.

Stated plainly, because these are the things an app like this is usually assumed to do:

• No advertising, no ad networks and no ad identifiers.
• No third-party analytics or tracking software in the app or on this website. There is no Google Analytics, no Firebase, no crash-reporting service and no marketing pixel of any kind.
• We never sell or rent your information, and we do not share it with anyone for their own marketing.
• No precise location. The app never asks for location permission.
• No access to your contacts, photos or files. The one exception is saving a certificate image, which the app writes to your gallery only when you ask it to.
• No decisions made about you by a machine that have a legal or similarly significant effect. The model chooses what to teach you, nothing more.

The factoids, courses, chapters and coach replies are written by a large language model. We do not run one ourselves. Each request goes to GM (saygm.com), which passes it to whoever hosts the model that answers it. Each of them handles it to produce that answer for us and for nothing else of ours.

Which model writes your lesson changes as better ones appear, and so, sometimes, does who hosts it. So the part of this worth reading is not the name, it is what leaves us.

What we send with a request:

• the subject being written about, and the language it should be written in;
• a summary of you as a learner: which topics you follow, how deep you already are in them, your level, and the time zone and country described above;
• for the coach and the mastery conversation only, the messages you typed and the chapter you are on.

What we never send: your email address, your name or username, your payment details, or your account identifier. The model is told about a learner, not about a person, and it is told the least that produces a good lesson: a chapter's actual prose is written with no personal context at all, because everybody reading that course reads the same words.

If we add a second routing service, or move to a different one, this page is updated to name it.

Under UK GDPR everything we do with your information sits under one of these:

To provide what you asked for (performance of a contract)

Your account, your progress, your reviews, friends, shares, and running a subscription you bought. Without this data there is no app to use.

Our legitimate interests

Keeping the service working and secure, stopping abuse and enforcing daily limits, fixing bad generated material, and understanding in aggregate how the app is used so it can be improved. We look at these as counts and trends rather than at individuals.

Consent

Where we ask for it, such as permission to send notifications from your device. You can withdraw it at any time in the app or in your device settings.

Legal obligation

Keeping records of payments for as long as tax and company law require.

We use a small number of service providers, each of which handles data only on our instructions and for us:

Supabase

Hosts the database, the sign-in codes and the server functions. Effectively everything in the section above lives here.

Stripe

Takes payments. Your card details go to Stripe and never to us. Stripe is a data controller in its own right for parts of what it does, and its own privacy notice applies to that.

GM

Takes each request and routes it to the model that answers it, so that the learning material can be written and the coach can answer. The model providers it routes to receive the same request, and they are covered by what goes to the AI service above.

Our email provider

Delivers the six-digit codes and any message we send you about your account.

Vercel

Hosts this website and the browser version of the app.

Google Play and the App Store

Distribute the app, and handle any subscription bought through them. What they collect is covered by their own policies, not this one.

Two more are worth naming even though we send them nothing about you. The app looks up Wikipedia directly from your device when you tap a key term or search for a topic to follow, so Wikipedia sees that request coming from your device in the ordinary way a browser would. Our servers separately read Wikipedia and OpenAlex when writing a chapter, identifying themselves as us and carrying nothing about any learner.

We will also disclose information where the law requires it, or to protect our rights or somebody's safety, and we would tell you unless we are not allowed to.

This website sets no tracking or advertising cookies, which is why it shows no cookie banner. The only cookie it ever sets is the one that keeps an administrator signed into our private statistics panel, and only for us.

The app stores a few things on the device itself: the token that keeps you signed in, your reminder schedule, and your sound, theme and narration preferences. Deleting the app clears them. The browser version keeps the same things in your browser's local storage.

We are based in the United Kingdom. Some of the providers above process data outside the UK, including in the United States. Where that happens we rely on the safeguards UK law provides for it, which in practice means an adequacy decision covering the destination or the standard contractual clauses with the UK addendum in our agreement with that provider.

Email us if you would like more detail about a particular provider.

• Your account and everything in it: for as long as the account exists. An account that has not been used for three years may be deleted, and we will warn a connected email address first.
• If you delete your account: immediately. Deleting it is one button in the app (Settings, then Account, then Advanced) and one page on this site, and both erase it there and then rather than queueing a request.
• Payment records: six years, because tax and company law require it. Deleting your account deletes you as a customer of our payment provider, which takes your name, address and card details with it; the invoices for payments already made stay with them, attached to a customer that no longer has any details on it.
• The fact that a deletion happened: kept, as a row carrying the date, a note of whether it came from the app or this website, and whether the account had an email address and a subscription. No user id, no address, nothing that could be matched back to a person. It exists so we can see the deletions working and count them, and a list of people who have left is precisely the data somebody has just asked us to stop having.
• An account nobody deletes and nobody uses: kept. An account with no email connected cannot be reached by anybody, us included, once the app is removed from the device, and removing the app tells us nothing. What is stored stays stored, tied to a random identifier and nothing else, unless and until the inactivity rule above applies to it. Deleting the account rather than only the app is the way to have it gone now.
• Server logs: a short period set by the providers that keep them, typically weeks rather than months.
• Shared courses and factoids: kept, because they belong to every learner reading them rather than to the account that triggered them, and they carry nothing about you.

You can ask us to:

• tell you what we hold about you, and give you a copy;
• correct anything that is wrong;
• delete your account and the data in it;
• restrict or stop a particular use of it, including anything based on our legitimate interests;
• send you your data in a portable format, or send it to somebody else;
• withdraw a consent you gave, without affecting what was done before you withdrew it.

Deleting is the one you can do without us: it is in Settings under Account in the app, behind the Advanced section, and at k-loop.app/delete-account if the app is already gone from your phone. In the app you are already signed in, so it asks you to type a word to confirm. On the website it sends the same six-digit code the app uses, so that only somebody who can read your email can delete the account behind it. Both erase it there and then.

For anything else, email enzo@k-loop.app and we will do it, free, within one month. If your account has no email address connected we may have no way to know it is yours, so please write from the address on the account or tell us enough about it that we can be sure.

If you are unhappy with how we handled it, you can complain to the UK Information Commissioner's Office at ico.org.uk, or to the data protection authority where you live. We would rather you told us first, so we can fix it.

Knowledge Loop is for people aged 13 and over, and it is not directed at younger children. We do not knowingly collect anything from them. If you believe a child under 13 is using the app, tell us and we will delete the account.

Because the app is used by teenagers, it collects as little as it can, shows no advertising, and lets a learner control what other people can see on their profile.

Everything travels over encrypted connections and is stored encrypted at rest by our hosting provider. The database enforces per-account access rules of its own, so one learner's app cannot read another learner's rows even if it asks. Anything that shows you somebody else's details, such as a friend row or a profile, goes through a server function that decides what may be shown, so a switch you turned off is enforced before the data leaves us rather than hidden by the app.

Access to production data is limited to the people who run the service, and the internal statistics panel is behind an allowlist and an emailed code. No system is perfect; if something goes wrong that puts your information at risk, we will tell you and the regulator as the law requires.

When the app starts doing something new with your information, this page is updated before or as that happens, and the date at the top changes. For anything significant we will also tell you in the app or by email.