AlgoScope

Privacy

Last updated 19 November 2026

One policy for the website and the iOS and Android apps: the website, the iOS app, the Android app and what applies to all three.

Privacy in short

  • The controller is NUB LABS PRIVATE LIMITED, trading as AlgoScope. See who is responsible.
  • Every lesson works without an account, on the website and in both apps.
  • Code and input you type stay on your device and are never sent to us.
  • No ads, no advertising identifiers, and nothing sold or shared for marketing.
  • On the website, Google Analytics counts which pages and lessons are used, but only after you choose Allow analytics. It never receives your code, the words you search for or your email.
  • In the apps, version 0.1.0 sends neither crash reports nor usage. From version 0.2.0, crash reports are sent with no switch, and usage sharing only if you turn it on in Settings.
  • An account is optional and works on all three. Deleting it removes everything linked to it, with four exceptions that keeping it, and deleting it lists. Backups expire within two months.

What this website records

Reading without an account

The site remembers a few things in your browser. Nothing in this table is sent to us unless you send it, and the only row you can send is as:predict-answers. Clearing your browser data removes all of it.

The website, in your own browser
Stored asWhat it is for
as:progressWhere you are in each lesson, and which you have finished. It is never uploaded.
as:predict-answersPredict-mode answers you gave while signed out: which step, which option you chose, whether it was right, and when, with a short code for the question and an id for the answer. The latest 200 are kept. Uploaded only if you sign in and press the button on your dashboard, the review queue page or the Buy Pro form in your account settings that adds them to your account, then removed from this browser.
as:trackThe learning track you are following.
as:themeLight or dark, if you chose one.
as:motionFull or reduced animation, if you chose one.
as:loopsWhether you paused the animations on the home page, if you did.
as:consentYour answer about analytics, and when you gave it.
as:analytics-idOnly if PostHog, an analytics service that is not turned on, is ever turned on: a random id, made only if you allowed it, deleted when you withdraw and not linked to your account. Nothing writes it today. Google Analytics keeps its id in the cookies listed under Cookies.
as:langThe language you read code listings in.
as:soundWhether the player makes a sound.
as:predict-introWhether you have seen the predict mode introduction.
as:code:*Drafts of code you wrote in a lesson.
as:sessionWhether you are signed in, so pages load faster. Cleared when the tab closes.

If you make an account

An account saves your progress and answers across devices. It is the same account on the website and in both apps.

The website, in our database, and only with an account
KeptWhy
Your email addressHow you sign in and how we reach you. We also keep a normalised form of the address, so that different spellings of one Gmail mailbox count as one account. It is used for matching and nothing else.
A passwordOnly if you set one, and never in readable form.
Your Google or Apple linkOnly if you sign in with Google or Apple: their id for your account and when it was linked, and for Apple a token used to unlink it when you delete the account. We never see your Google or Apple password. Deleted with the account.
A name, if you give oneShown in the header and on your dashboard. Optional.
When you confirmed your ageOnly on an account made while we asked: when you ticked the box to say you were old enough. Nobody is asked now, so an account made since holds nothing here. Never a birth date.
Your sessionsEach browser or app you are signed in on, when it started and expires, and the browser or app name, so you can recognise it.
Lesson progressPer lesson and example: the step you reached and when you finished.
PredictionsPer question: which step, which option you chose, whether it was right, and when you answered it, plus a short code made from the question’s wording and options. Answers you gave before you signed in are here only if you added them from your dashboard, the review queue page or the Buy Pro form in your account settings. This is what the review queue, which is part of Pro, reads to work out what is due, and so does the weekly review reminder described below this table. The readiness score, also part of Pro, is worked out from it too.
Your email choicesWhether you have turned on release notes and reminders, both off unless you do.
A log of the optional email we sent youOne row per optional email that actually went out, holding your address, the normalised form of it described above, your account id, which message it was and when. There are three such messages today: the one-time welcome, release notes if you turn them on, and the weekly review reminder if you turn Reminders on. It is the one row in this table that keeps your address after the account is deleted.
A record that a reminder was held backOne row each time an account was left out of the weekly review reminder: your account id, which message it was and when. It holds no address and none of your answers, and that it exists says only that the account would have been sent the reminder that week. It is deleted with the account.
Purchases, if you make oneWhat you bought, the amount, currency and billing country, when, and the payment reference. Card and bank details go to the payment company and never reach us.
What your account unlocksWhether the account has Pro, where it came from, and when it was granted or taken back.
A sign-in code, for two minutesOnly when you sign in to an app with Google. Deleted as soon as it is used.

The weekly review reminder is the third optional email, after the one-time welcome and release notes. It is off unless you turn on Reminders in settings, it goes to Pro accounts only, and it is sent at most once every seven days. It says how many questions are due for review and links to your review queue. It is never sent when nothing is due, and it names no lesson and says nothing else about your progress. The number is worked out from your answers and is written in the email, so the email service that sends it sees that number.

So that we can tell whether the reminder helps anyone come back, each week about a tenth of the accounts it would have gone to are left out of it on purpose. They are picked by a calculation on the account id and the week that looks at nothing you have done, so they are drawn afresh each week, and an account left out gets the row in the table above. We then compare the accounts that were sent it with the ones left out, by counting how many answered a question in the three days after it was, or would have been, sent, using the dates already on the answers. That is a count for each group. No result is kept against any account.

Progress from before you signed in stays in that browser. The predictions you answered as a guest are the one exception, and only if you ask: your dashboard, the review queue page and the Buy Pro form in your account settings offer to add them to your account, and nothing is uploaded until you press the button.

Your code and your input never reach us

Code you write and input you run a lesson on are processed in your browser and never sent to us. The first time you run Python, your browser downloads it from a public content delivery network, which sees your IP address the way any website does.

Cookies

Two first-party cookies, neither for advertising, on the website only:

  • as_session keeps you signed in, for up to thirty days.
  • as_hint holds your account id, address, name, whether the address is confirmed and your plan, so the page header can show them without asking the server every time. It lasts thirty days.

If you choose Allow analytics, Google Analytics adds two more first-party cookies, _ga and a second whose name starts _ga_. They hold a random id for your browser, last thirteen months and are deleted when you withdraw. Until you choose, and if you choose No analytics, it sets neither. The apps set no cookies.

Measurement, and how you are asked

Google Analytics is the one analytics service the website uses. It measures which lessons get read and where people stop. For every visitor, wherever you are:

  • No Google Analytics code is loaded, and nothing is measured, until you choose Allow analytics. A bar at the bottom of the page asks.
  • Choosing No analytics, or not choosing, means no measurement.
  • Global Privacy Control and Do Not Track count as a refusal. A browser that sends one is never asked and never measured, even if it said yes before.
  • You can change your mind any time: . Saying no stops anything new from being sent and deletes the cookies. Google's tag sends in batches, so what you did in the few seconds before you said no can still reach Google, and what Google already holds stays with it until it is deleted.
  • The identifier is random, and nothing sent to Google names your account. Signing in does not change it.
  • Google's advertising features are switched off.

What is measured, once you have allowed it:

  • The pages you open, with nothing after the ? but a campaign tag such as utm_source, and the page you came from.
  • What you do in a lesson: lessons opened, predictions right or wrong, code runs and whether they passed, never the code. Searches by length and result count, never the words. Which library filter you set, by category or difficulty. Reports by reason, never what you wrote.
  • Sign-up and sign-in steps, and the method. Checkout: that you started one, the amount and currency, which payment company would take it, and why one failed. That you were shown an offer for Pro, and which. A completed purchase is not reported.
  • That you copied the link from the share card in your account settings, or sent it from your phone's share sheet, and which of the two - never who it went to. The link is the same for everyone and holds nothing about you.
  • With each of those, the version of the site.

Google's tag also records what it records on any site that uses it: how long a page was in view, your browser, device type, screen size and language, and roughly where you are, worked out from your IP address.

Server logs

Our server logs each request so we can fix problems: what was asked for, whether it worked, how long it took, and your account id if you were signed in. It never holds your IP address, your email address, a password, a cookie, or anything you typed. In a confirmation, password-reset or unsubscribe link, the secret is left out of the line. Errors are logged with the secret in a confirmation, password-reset or unsubscribe link taken out. Old logs are dropped as new ones are written.

No log of IP addresses is kept today. If our hosting starts one, it will not record the address of the page asked for, it will be kept for about ninety days, and this policy will say so first.

Who else is involved

  • An email service sends our email: confirmations, password resets, notices about changes to your account, the welcome, release notes and the weekly review reminder if you turn them on, and receipts. It receives your address and the message, and each optional email carries a random id of our own record of that send, so a spam report can be matched to the message. It receives nothing else, with one exception: the reminder says how many questions are due for review, so they see that number.
  • Google, only if you choose to sign in with it. Google tells us your address, your name and its id for your account.
  • Apple, only if you choose Sign in with Apple. Apple tells us its id for your account, an address (yours, or a relay address if you chose Hide My Email) and, the first time, your name. When you delete the account, we tell Apple to forget the link.
  • The payment company, if you buy Pro on the website. It receives your card or bank details, which never reach us. It is named at checkout and on your receipt. In the apps, the App Store or Google Play takes the payment.
  • Our hosting provider, which runs the site and its database.
  • Backblaze, which stores the backups of the database, encrypted, in its EU region.
  • A content delivery network, only if you run Python, as your code and your input describes.
  • Google Analytics, on the website, only if you choose Allow analytics. It receives the pages you open and the events listed under measurement, a random id kept in two cookies and, as with anything a page loads from another site, your IP address and your browser's details. PostHog, a second analytics service the site can use, is not turned on, and this policy changes first if it is.
  • A bot check on sign-up. It receives your IP address and technical details of your browser, never what you type.
  • An error-reporting service receives details of unexpected errors: what failed, the page or endpoint, and what the page or server did just before, including what it wrote to its console. An address in a report has nothing after a question mark, the secret in a one-time link is taken out wherever it turns up, a line written to the console included, and an email address in an error message is replaced before the report is sent. It never receives your IP address or cookies.

Nobody else. Data is not sold, not shared for advertising, and not handed to anyone for their own purposes.

Keeping it, and deleting it

Progress and predictions are kept while the account exists. Password resets last thirty minutes, address confirmations twenty-four hours and sessions thirty days, and each is deleted after it expires.

Google Analytics keeps the events it receives for two months and then deletes them. Reports that add events up, without any one visit in them, are kept longer. None of it is linked to an account, so deleting an account does not change it.

Deleting the account removes it and everything linked to it, with four deliberate exceptions named below. Deleting your account says how. An account switched off for two years is deleted the same way, with an email thirty days before. A sign-up never confirmed is deleted after thirty days, unless it holds a purchase.

The first thing that survives a deletion is the do-not-send list. If you unsubscribed, or an email to you bounced or was reported as spam, your address stays on it so we never email you again. It holds the address, a normalised form of it so that different spellings of one Gmail mailbox count as one - an unsubscribe from one spelling stops optional email to all of them - the reason it was added, and when it was added. If the reason was a spam report and the report names one of the optional messages in the log below, it also holds a pointer to that message's entry in the log, which says which message it was and when. For every other row the pointer is empty. Nothing else is in it. Write to us to have it removed.

The second is a record of anything you bought, if you did: the amount, currency, date and payment reference, kept for eight financial years as Indian tax and company law require. It no longer names you after the account is deleted.

The third is a log of the optional email we sent you, and like the do-not-send list it keeps your address in full. Each row holds your address, a normalised form of it so that different spellings of one Gmail mailbox count as one, the account id it was sent for, which message it was, and when. There are three such messages today: the one-time welcome, release notes if you turn them on, and the weekly review reminder if you turn Reminders on.

It is kept so that no address is sent too much: the cap counts this log by the address, with the normalised form that counts every spelling of one Gmail mailbox together, and not by the account. It holds nothing else about you: no progress (not even the number a reminder carried), no predictions and no message text. To have it removed, write to contact@algoscope.net.

The fourth is the entry recording when what you bought was switched on or off, if you had anything switched on. It no longer names you after the account is deleted, and is kept so a later refund or chargeback can be settled.

Backups of the database are made every night and stored with Backblaze, a storage company separate from our hosting provider, in its EU region, in a private bucket encrypted at rest. The newest 30 are kept and older ones are deleted, so a deleted account is gone from every copy within two months.

What the iOS app records

Without an account, what the app remembers stays on your device. Signed in, your progress is also saved to your account.

What it keeps on your device

Eighteen values, in the app's own storage. No other app can read them, and neither can we.

The iOS app, in this device's own storage
Stored asWhat it is for
progressThe step you reached in each lesson, and which you finished.
trackThe learning track you are following.
themeLight or dark, if you chose one.
motionFull or reduced animation, if you chose one.
langThe language you read code listings in.
soundWhether the player makes a sound.
analyticsWhether you turned on usage sharing. Off unless you do.
predict-introWhether you have seen the predict mode introduction.
predictionsPredict-mode answers you gave, the latest 200, so the review queue can find them.
api-queueOnly while signed in: changes waiting to reach your account when you are back online.
update-checked-atWhen the store last answered the app about a newer version.
update-dismissedThe version you dismissed the update notice for, so the same version does not show it again.
update-offeredThe newer version the store last said is out, so the update notice is there each time you open the app.
rating-asked-versionThe version of the app in which it last asked the store to show its rating card, so it asks at most once per version.
rating-asked-atWhen the app last asked the store to show its rating card, so it leaves a gap between two asks.
last-seen-versionThe version of the app that last ran, so the first launch after an update can show what is new in it, once.
savedThe topics you saved to come back to, each a lesson and an example, newest first. Kept on this phone and never uploaded.
welcome-seenWhether the app's opening pages have been shown or skipped, so they come once and not at every launch.

While you are signed in, your sign-in token and a note of your plan are kept encrypted on this device only. Signing out deletes both. The app does not collect your contacts, photos or location.

What it sends

Without an account, nothing about you reaches our server. Signed in, the app sends it your sign-in details, your progress and predictions, the settings actions you take, and a record of any Pro purchase, which we check with Apple.

Version 0.1.0 sends neither crash reports nor usage. From version 0.2.0, crash reports go to Google from release builds, with no switch, so crashes can be fixed: what failed, the device, its system and the app version, and a random id for the install, which Google keeps to count how many installs a crash reached. They carry no account id.

From version 0.2.0, usage sharing is off unless you turn on Share anonymous usage in Settings. When it is on, the app tells Google which lessons you open and finish, predictions you answer, searches by length and result count, which of its four tabs you open, whether you see or dismiss the update notice, whether you open Send feedback, when it asks the store for a rating, whether you are shown an offer for Pro and which, and similar steps, never what you type or write, with the app version, the kind of device and roughly where you are, worked out from your IP address. It is never linked to your account. Turning it off stops it and resets the random id on your device.

To tell you when a newer version is out, the app asks the App Store which version is current. It asks when you open the app or come back to it, and once the store has answered it does not ask again for a day. The question names the app and carries no sign-in, account or progress. It goes to Apple, not to us. Like any request, it shows Apple your IP address and the usual details a device adds to a request.

What the App Store privacy label declares

Linked to you, only if you sign in: your email address, name, account id, progress and any purchase. Not linked to you, from version 0.2.0: crash data, to fix crashes, and, only if you turn on usage sharing, product interaction and a device identifier, for analytics. No tracking and no advertising identifier.

What leaves the app, when you ask it to

  • Further reading links open in your browser.
  • Share this step sends a link to the lesson and step, nothing about you.
  • Report a problem writes a message you send yourself, by email or from your clipboard.
  • Send feedback writes a message you send yourself, by email or from your clipboard. It holds the kind you picked, the note you wrote, the app and system version and the device model. Sent by email, it shows us the address you send it from, as any email does.

Turning it off, and getting rid of it

  • Reset progress, in Settings under Data, clears progress on this device.
  • Sign out deletes the token and the plan note. Your progress on the device stays.
  • Delete account, in Settings under Data, deletes your account, as deleting your account describes.
  • Deleting the app removes what it keeps. Sign out first to remove the sign-in token too.

What the Android app records

Without an account, what the app remembers stays on your device. Signed in, your progress is also saved to your account.

What it keeps on your device

Eighteen values, in the app's private storage. No other app can read them, and neither can we.

The Android app, in this device's own storage
Stored asWhat it is for
progressThe step you reached in each lesson, and which you finished.
trackThe learning track you are following.
themeLight or dark, if you chose one.
motionFull or reduced animation, if you chose one.
langThe language you read code listings in.
soundWhether the player makes a sound.
analyticsWhether you turned on usage sharing. Off unless you do.
predict-introWhether you have seen the predict mode introduction.
predictionsPredict-mode answers you gave, the latest 200, so the review queue can find them.
api-queueOnly while signed in: changes waiting to reach your account when you are back online.
update-checked-atWhen the store last answered the app about a newer version.
update-dismissedThe version you dismissed the update notice for, so the same version does not show it again.
update-offeredThe newer version the store last said is out, so the update notice is there each time you open the app.
rating-asked-versionThe version of the app in which it last asked the store to show its rating card, so it asks at most once per version.
rating-asked-atWhen the app last asked the store to show its rating card, so it leaves a gap between two asks.
last-seen-versionThe version of the app that last ran, so the first launch after an update can show what is new in it, once.
savedThe topics you saved to come back to, each a lesson and an example, newest first. Kept on this phone and never uploaded.
welcome-seenWhether the app's opening pages have been shown or skipped, so they come once and not at every launch.

While you are signed in, your sign-in token and a note of your plan are kept encrypted on this device. Signing out deletes both. The app does not collect your contacts, photos or location.

What it sends

Without an account, nothing about you reaches our server. Signed in, the app sends it your sign-in details, your progress and predictions, the settings actions you take, and a record of any Pro purchase, which we check with Google Play.

Version 0.1.0 sends neither crash reports nor usage. From version 0.2.0, crash reports go to Google from release builds, with no switch, so crashes can be fixed: what failed, the device, its system and the app version, and a random id for the install, which Google keeps to count how many installs a crash reached. They carry no account id.

From version 0.2.0, usage sharing is off unless you turn on Share anonymous usage in Settings. When it is on, the app tells Google which lessons you open and finish, predictions you answer, searches by length and result count, which of its four tabs you open, whether you see or dismiss the update notice, whether you open Send feedback, when it asks the store for a rating, whether you are shown an offer for Pro and which, and similar steps, never what you type or write, with the app version, the kind of device and roughly where you are, worked out from your IP address. It is never linked to your account. Turning it off stops it and resets the random id on your device.

To tell you when a newer version is out, the app asks Google Play, through Play's own update library. When it asks the store for a rating, it does so through Play's own review library, and Google Play decides whether to show its card. Neither of these sends anything to our server.

Permissions, and the advertising identifier

Two permissions: internet access, for your account and, from version 0.2.0, for crash reports and usage sharing, and Google Play billing, to buy Pro. The app cannot read the advertising identifier, and has no ads.

Android's own backup

Android can back up the app's settings and progress to your Google account. Your sign-in token is never backed up. You can turn this off in your system settings.

What leaves the app, when you ask it to

  • Further reading links open in your browser.
  • Share this step sends a link to the lesson and step, nothing about you.
  • Report a problem writes a message you send yourself, by email or from your clipboard.
  • Send feedback writes a message you send yourself, by email or from your clipboard. It holds the kind you picked, the note you wrote, the app and system version and the device model. Sent by email, it shows us the address you send it from, as any email does.

Turning it off, and getting rid of it

  • Reset progress, in Settings under Data, clears progress on this device.
  • Sign out deletes the token and the plan note. Your progress on the device stays.
  • Delete account, in Settings under Data, deletes your account, as deleting your account describes.
  • Clearing the app's storage, or uninstalling it, removes everything it keeps.

What is true of all three

Four things do not differ by platform.

Who is responsible, and where to complain

The controller is NUB LABS PRIVATE LIMITED, trading as AlgoScope. Its postal address is under contact. Questions and grievances go to contact@algoscope.net, and you will get an answer within 30 days. In the EU or UK you can also complain to your data protection authority.

Children

There is no minimum age to make an account or to buy Pro, as the terms say, and nobody is asked their age. Reading needs no account, and what the website records about a reader without one is only what the website part of this policy lists. If you are a parent or guardian and want a child's account removed, write to contact@algoscope.net and you will get an answer within 30 days.

Your rights

You can ask for a copy of your data, correct it, delete it, object to how it is used, or withdraw consent. In settings you can download a file of what your account holds, correct your name and address, and delete the account. For anything else write to contact@algoscope.net, and you will get an answer within 30 days.

The file holds your account, sessions, the Google or Apple accounts linked to it, progress, predictions, email choices, which optional emails were sent to the account and when, the times a reminder was held back from it, purchases on the website and in the stores, and whether the account has Pro, where it came from, and when it was granted, ends or was taken back. It leaves out passwords and tokens. It does not repeat the address and the normalised form of it that each row of the log of optional email holds. Ask for the log as it is kept and you will be sent it.

Changes

Before we collect anything new, this policy changes first, with a new date. The current version is always at this address.