3. What we collect
Account information. When you create an account we receive your email address and, if you provide them, your name and profile picture. If you sign in with Google, we receive your name, email address and profile picture from Google. Passwords are handled by our sign-in provider; we never see or store them.
Learning records. For each answer you check while signed in, we record the exercise, the track (visual, SQL or Python), whether it passed, how many of the test datasets matched, how long the check took and when it happened. From these we keep your progress: which exercises you've started and completed.
Teams and classrooms. If you join an organization by invitation, its owners, admins and instructors can see your name, email address, role, when you joined and the status of its assignments (not started, in progress, completed, completed late), and can download that as a CSV file. They cannot see your drafts, code, notes or tutor conversations. When you leave or are removed, they no longer see your status; your own progress stays in your account.
Certificates. When you claim a certificate of completion, we store the name you enter for it, the date and a certificate ID. The certificate has its own web address so that you can share it and others can verify it; anyone with that link can see the name, date and what was completed. Certificate pages are not listed in search engines.
Your work. When you check an answer, the pipeline or code you wrote is sent to our servers so it can be run and compared with the expected result. We don't keep a copy of it after the check; we keep only the result described above. Drafts you haven't submitted are saved in your browser on your device, not on our servers.
AI tutor requests. When you ask the tutor for help, we send the exercise rules, a few rows of the exercise's fictional dataset, your current draft, any error message shown to you and your question to our AI model provider to produce the answer. We don't store the question or the answer. We record how many tutor turns you've used and how much processing each used, to apply your monthly allowance.
Payment information. When you buy a plan, our payment processor collects your card or other payment details directly. We never receive your full card number. We receive and keep a customer reference, the plan you bought, its price, status, renewal and end dates, and your billing country where needed for tax.
Messages to us. When you email us or use the contact form we receive your email address, your name if you give it, the topic and your message, and whether you were signed in. We send you an automatic confirmation and reply by email.
Technical and usage information. Like most websites, our hosting provider processes your IP address, browser type, device type, the pages requested and timestamps to deliver the site and protect it against abuse. We also measure aggregated page views and site performance with privacy-friendly analytics that don't use cookies and don't identify you across websites.
Advertising measurement. We advertise on Google. When you arrive from one of our Google ads and allow it, the Google tag sets cookies that remember the ad click, and tells Google Ads when you create an account or buy a plan: the plan price, a transaction reference and, if you're signed in, your email address, which the tag hashes (turns into an irreversible code) in your browser before sending. Google uses this to match the sign-up or purchase to the ad click. We don't send your name, your learning records or your code. We tell Google not to use this data to personalise ads.
12. What not to send us
The exercises use fictional data, and you never need to enter real personal or confidential data to use Data Cleaning Exercises. Please don't paste real customer records, passwords, card numbers or other sensitive information into exercises, the AI tutor or the contact form.