Privacy Policy

Contact

FastAPI Interactive is an independent site run by its founder, who is responsible for the personal data described here. For anything to do with your data, write to hello [at] fastapiinteractive [dot] com.

The short version

• Lessons run in your browser. The Python runtime, your code and your progress live on your device. Nothing you type in a lesson is sent to us unless you sign in and choose to sync it.
• An account is optional. If you sign in with GitHub we store your username, display name, email address and avatar, plus your progress, so it follows you between devices.
• The newsletter is optional. We store your email address only if you subscribe, and every email has an unsubscribe link.
• Non-essential cookies are your call. Where the law requires it we ask before setting any, and everywhere you can change your mind in Cookie settings.
• We never sell your data, and no advertising is shown on the site.

What we collect, and why

Learning on the site, without an account. Your code, which lessons you have completed and where you left off are stored in your browser’s local storage. They stay on your device and we use them to restore your work when you come back. Legal basis: our legitimate interest in making the site work as you would expect.

Your account. If you sign in with GitHub, GitHub sends us your username, display name, the email address on your GitHub account, and your avatar. We keep those together with your lesson progress and the code from your lessons, so that your work is there when you sign in elsewhere. A session cookie keeps you signed in. 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, from the account menu at any time.

The newsletter. If you subscribe we store your email address and which page you subscribed from, and use them to send you news about new lessons. Legal basis: your consent, which you withdraw by clicking unsubscribe in any email or on the unsubscribe page.

Certificates. If you buy a certificate of completion we record the name you ask to have printed, the track, the date, a serial number, the amount paid and a reference to the payment. The certificate’s verification page shows the name, track, date and serial to anyone who has the link or scans the code, because that is what makes it verifiable. Payment happens on our payment processor’s own page; we never see or store your card details. Legal basis: the purchase agreement, and the accounting obligations that come with a sale.

Analytics. To see which lessons work and where people get stuck, we use an analytics service that sets cookies to tell one visitor from another and records pages viewed and events such as running code or completing a lesson. It is not linked to your account. We also count page views with a service that sets no cookies and keeps no profile of you. Legal basis: your consent where the law requires it, and otherwise our legitimate interest in understanding how the site is used, with an opt-out.

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

The contact form. If you write to us through the form we receive your message, the address you give, and the page you wrote from, and we use them to answer you. They are kept in our mailbox for as long as the conversation needs, and deleted after. 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. We use them in three groups.

• Essential. The cookie that keeps you signed in, the local storage that holds your code and progress, and the record of your cookie choice. Set by us, kept for as long as you are signed in or until you clear your browser. These do not need consent, because the site cannot work without them.
• Analytics. Cookies set by a third-party analytics service to recognise a returning browser, kept for up to two years. Set only with your permission where the law requires it.
• Marketing. Used only to measure the campaigns that bring people here, through the same analytics tools, with the same lifetime. No advertising cookies are set on the site.

Where you are matters. In regions whose law requires prior consent, nothing outside the essential group is set until you choose, and rejecting is one click, the same as accepting. Elsewhere, analytics and marketing storage are used unless you turn them off, and we honour the Global Privacy Control signal your browser can send. In every case you can change your choice at any time from Cookie settings in the footer.

Who else sees it

We use a small number of service providers to run the site. Each processes data only on our instructions and only for the purpose described here. Some are outside the European Economic Area; those transfers rely on an adequacy decision or on the European Commission’s standard contractual clauses.

• Providers that host the site and deliver it quickly around the world.
• The provider you choose to sign in with (GitHub), which confirms who you are.
• The database behind accounts and certificates, hosted in the European Union.
• The payment processor that takes certificate payments.
• The email service that sends the newsletter and holds the subscriber list.
• The analytics services described above.

How long we keep it

• Your account and its progress: until you delete the account.
• Your newsletter address: until you unsubscribe.
• Analytics data: up to 14 months in the analytics service, then deleted.
• Technical logs: a matter of days.
• Certificate records: for as long as the certificate exists, so that it can be verified. You can ask for one to be withdrawn at any time. The payment record stays for as long as accounting law requires.
• What is stored in your browser: until you clear it.

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, and where we rely on our legitimate interest you can object. Write to hello [at] fastapiinteractive [dot] com; we answer within a month. 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 create an account or subscribe to the newsletter.

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.