Last updated · 22 August 2026
Privacy
SQL.tn limits collection to the data required to provide, improve and secure the service.
SQL environment and local progress
SQL queries run in your browser on fictional data. They are not sent to the server. Progress is stored locally and can be synchronised when you use an account.
Waiting list
If you join a waiting list, SQL.tn stores your email address, optional first name, chosen path, form source and proof of consent. The IP address of attempts is kept temporarily to limit spam. This information is used only to measure interest and notify you when the content opens.
Audience measurement
Audience measurement is off by default. With your explicit consent, SQL.tn uses Google Analytics (ID G-Q5MZSVKES7) and may store internally a random identifier, the page and an action such as starting or completing an exercise. Google may then receive technical visit data. SQL.tn does not enable advertising tracking, and refusing consent does not disable any feature.
Account data
When you register, SQL.tn stores your email address, display name, a password protected through salted cryptographic derivation, sessions and synchronised progress. The plain-text password is never stored.
Orders and access
An access request records its reference, plan, amount, status, optional message and processing dates. Administration uses the account address to confirm arrangements and records activation. SQL.tn collects neither card numbers nor security codes.
Technical logs
The infrastructure may record the IP address, date, requested resource, browser and HTTP status to secure the service and diagnose errors.
Contact and notifications
The contact form stores the name, email address, subject, message, language and a pseudonymous fingerprint of the IP address to reply and prevent abuse. Account, waiting-list, commercial-request and contact confirmations are queued internally and then delivered through the configured mail server. They do not subscribe you to marketing.
Account recovery
A password reset request creates a one-time token stored as a fingerprint for 30 minutes. Attempts are limited and other sessions are closed after a change. The message never reveals whether an address has an account.
Learning-content feedback
Feedback stores its category, message, page, language, content reference, browser, screen size, a pseudonymous IP fingerprint and, when signed in, the account reference. SQL typed in the editor is never attached.
Beta invitations
An invitation code is stored only as a fingerprint with its cohort, language, source, expiry and redemption date. On activation it is linked to the account to grant temporary access with no payment or renewal.
Beta survey
For a signed-in beta tester, SQL.tn may store overall rating, perceived difficulty, understanding, bugs, missing or appreciated elements, willingness to pay, an optional indicative price, a comment, language, date and account reference. This data improves the product and is not published as a testimonial.
Testimonials
A testimonial may only be published with explicit consent linked to the text and display name. Consent may be withdrawn through Contact. If no real authorised testimonial exists, no review is displayed.
Future payments
SQL.tn currently collects no card data. If a payment provider is enabled, this policy will be updated before launch to identify the provider, exchanged data, purposes and applicable retention periods.
Your choices and requests
You can clear progress and the audience measurement choice from your browser's site data. An account without a confirmed payment can be deleted directly and permanently from ‘My space’. When payment has been confirmed, authentication and progress data are deleted, the profile is anonymised and the minimum financial references are kept for accounting. For a correction request or removal from a waiting list, write to contact@sql.tn.