Privacy policy

Who runs this site

Interactive Frameworks, at interactiveframeworks.com, is an independent site, run as a sole trader by the developer who writes the lessons and who is responsible for the personal data described here. For anything to do with your data, write to hello@interactiveframeworks.com, which is the fastest way to reach a human, since there is no contact form on the site.

The short version

• Everything here is free. There is nothing to buy, so there is no payment, no card and no billing data.
• An account is optional. If you sign in with GitHub we store your GitHub username, display name, email address and avatar, together with your progress and the code from your lessons, so they follow you between devices. There is no password.
• Lessons run in your browser. The framework, the compiler and your code all run on your device. Nothing you type in a lesson is sent anywhere unless you have signed in, and then only to us, to keep it for you.
• Without an account your progress stays with you. Which lessons you have finished and the code you wrote are kept in your browser’s own storage, and we cannot read them.
• Non-essential cookies are your call. We ask before setting any, and you can change your mind at any time in Cookie settings.
• We never sell your data, and no advertising is shown on the site.

What is kept in your browser

The site keeps your work on your device, under keys beginning with ifw: in your browser’s local storage: which lessons you have completed, the code in each lesson’s files, whether the lesson sidebar is collapsed, and your cookie choice. A service worker also keeps a copy of the compiled files of the lesson you are running, so that the app in your tab can load them.

Unless you sign in, none of this reaches us. It is on your device, it is readable by you, and clearing site data in your browser deletes it, along with your progress. Legal basis: our legitimate interest in the site working the way you would expect it to.

What we collect, and why

Your account. If you choose to sign in with GitHub, GitHub sends us your username, display name, the email address on your GitHub account and your avatar, and nothing else: we ask GitHub for no access to your repositories. We keep those together with your lesson progress, the code from your lessons and the lesson you last opened, on a server we rent in the European Union, so that your work is there when you sign in on another device. A cookie keeps you signed in for ninety days. Legal basis: the agreement you enter into when you create the account. You can download everything we hold about you, or delete the account and all of it at once, from your account page at any time.

Analytics. To see which lessons work and where people get stuck, we use Google Analytics, which sets cookies to tell one browser from another and records pages viewed and events such as running code or completing a lesson. It is not linked to your account. It runs only if you allow it. Legal basis: your consent.

Marketing measurement. If you allow marketing cookies, the same analytics tool may also be used to measure which links and campaigns bring people to the site. We do not show advertising here and we do not build advertising profiles. Legal basis: your consent.

Email you send us. If you write to the address above we receive your message and your address, and use them to answer you. They stay in the mailbox for as long as the conversation needs and are then deleted. Legal basis: our legitimate interest in answering you.

Technical logs. Like every website, the systems that deliver this one record requests for a short time, including IP addresses, to keep the service running and to detect abuse. Legal basis: our legitimate interest in security.

Cookies and similar storage

Cookies are small files a site asks your browser to keep; local storage is the same idea with more room. Your progress and your code are in local storage, your cookie choice is stored beside them, and the only cookie the site sets itself is the one that keeps you signed in, if you sign in. We use them in three groups.

• Essential. The local storage that holds your code and progress, the cache of the lesson you are running, the record of your cookie choice, and, once you have signed in, the cookie that keeps you signed in for ninety days. These need no consent, because the site cannot do what you asked without them.
• Analytics. Cookies set by Google Analytics to recognise a returning browser, kept for up to two years. Set only if you allow them.
• Marketing. Used only to measure which links bring people here, through the same tool and with the same lifetime. No advertising cookies are set on the site.

Rejecting is one click, exactly like accepting, and refusing costs you nothing: every lesson works the same either way. If your browser sends a Global Privacy Control signal we take that as a refusal and do not ask. You can change your choice at any time from Cookie settings in the footer.

Who else your browser talks to

The site is small and so is this list. Each of these sees your IP address, because that is how the internet delivers a file; none of them is given anything else about you by us.

• The provider that hosts the site and delivers its pages around the world.
• jsDelivr (cdn.jsdelivr.net), the public code network the Monaco code editor is downloaded from when you open a lesson.
• GitHub, only if you choose to sign in with it: GitHub confirms who you are and hands us the profile details listed above, and its own privacy policy governs what it records about that.
• Our accounts server, in the European Union, which the site talks to only while you are signed in, to save and fetch your progress.
• Google Analytics, and only once you have allowed it.

Fonts are served from this site itself, so opening a page makes no request to Google for them. The lessons themselves make no requests off your device: the server you write runs in your tab and answers itself. Some of these providers are outside the European Economic Area; those transfers rely on an adequacy decision or on the European Commission’s standard contractual clauses.

How long it is kept

• What is stored in your browser: until you clear it.
• Your account and the progress kept with it: until you delete the account.
• A signed-in session: ninety days, or until you sign out.
• Analytics data: up to 14 months in the analytics service, then deleted.
• Technical logs: a matter of days.
• Email: as long as the conversation needs.

Your rights

You can ask us to show you what we hold about you, correct it, delete it, restrict what we do with it, hand it over in a portable form, or stop processing it. Where we rely on your consent you can withdraw it, from the cookie settings or by writing to us, and where we rely on our legitimate interest you can object. If you have an account, the two requests that matter most need no email: your account page lets you download everything we hold and delete the account yourself, at once. For anything else write to hello@interactiveframeworks.com; we answer within a month. Without an account we usually hold nothing that identifies you, so the honest answer to most requests is that there is nothing to show. If you are not satisfied you can complain to the data protection authority in the country where you live.

Children

The site is not aimed at children. If you are under 16, please do not allow analytics cookies without asking whoever looks after you.

Changes

When this policy changes, the date at the top changes with it, and if the change matters to you we say so on the site rather than quietly editing the page. The terms the site is offered on are in the legal notice.