Privacy policy
SELECT body
FROM legal_pages
WHERE name = 'privacy';Query executed. The result is below.
This English version is provided for convenience. In case of any discrepancy, the German version prevails.
1. Controller
The controller responsible for processing personal data on SQL-Campus is:
Mathis NeunzigUnter den Weiden 5
68199 Mannheim
Germany
Email: mathis@sql-campus.de
2. Overview
SQL-Campus is a platform for learning SQL. We process personal data only as far as needed to run the platform and the features you use. We don't use analytics or tracking tools, don't show ads and don't sell data.
3. Visiting the website and running the servers
When you visit SQL-Campus, the server necessarily processes your IP address and details of the request (requested address, time, browser identifier) to deliver the pages. The application itself keeps no access logs with IP addresses. To protect against abuse, your IP address is used in counters when you submit solutions and when you send feedback; they are deleted automatically after the counting period (60 seconds and 10 minutes by default).
The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is providing the platform securely and reliably.
4. User account
For an account we process:
- your email address, display name and preferred language,
- your password, only as a secure salted hash (Argon2id) – it is never stored in plain text,
- your role (e.g. student, instructor, administrator) and account status,
- accessibility settings you choose (e.g. reduced motion),
- timestamps such as registration and last change.
To confirm your email address and to reset your password, we send you emails containing a link. Only a hash of the code in it is stored; the link is valid for 24 hours (confirmation) or 1 hour (password). For signing in we also store hashes of session tokens, which expire after 7 days at the latest.
The legal basis is Art. 6(1)(b) GDPR (performance of the user agreement). Without this information we can't provide you with an account.
5. Signing in with Google or GitHub
Instead of email and password, you can also register and sign in with your Google or GitHub account. Signing in then takes place on the provider's pages, which are governed by the provider's privacy policy. Once you agree there, the provider sends us your provider ID, email address and name. We use them to create your account or to link it to an existing account with the same email address. We receive no other data from your Google or GitHub account.
- Google: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland – Google's privacy policy
- GitHub: GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA – GitHub's privacy statement
Signing in through these providers may involve transfers of data to the USA, for which the providers themselves are responsible. The legal basis for our processing is Art. 6(1)(b) GDPR. You can unlink a provider in your account settings at any time.
6. Learning, courses and exams
When you use the platform, we process:
- the solutions you submit (e.g. SQL queries and answers) and their automatic grading,
- exam attempts with answers, times and results,
- courses you are enrolled in, their assignments and your progress in exercise packs and learning journeys,
- notifications, e.g. about new assignments or deadlines,
- feedback on submissions (peer review) that you write or receive,
- a per-topic skill profile calculated from your grades, which we use to recommend suitable exercises.
Submitted SQL queries run in isolated database environments that are started only for that grading and discarded afterwards. The skill profile only serves your exercise recommendations; there is no automated decision with legal or similarly significant effects (Art. 22 GDPR). Automatic grading of exams only sets points; how they count towards a grade or credit is up to the instructors.
Instructors see the names, submissions and results of the participants of their courses and exams. Administrators can view accounts for administration and to prevent abuse; administrative actions are logged.
The legal basis is Art. 6(1)(b) GDPR.
7. Practice environments in courses
For some courses, administrators set up personal logins to practice environments (e.g. MySQL with phpMyAdmin, Neo4j, PostgreSQL databases and JupyterHub). We run these environments ourselves; they are separate from the learning platform. For this we process:
- a username we build from the part of your email address before the @,
- a randomly generated password that we send you once by email; SQL-Campus doesn't store it, the practice environments only as a hash,
- what you create and run in the environments, such as your own databases, tables, queries and notebooks.
The administrators of the practice environments can see this content. In Neo4j, content can't technically be restricted to individual people; what you create there can be seen by other participants too. So please don't store real personal data in the practice environments.
The legal basis is Art. 6(1)(b) GDPR. The login remains until the administrators remove it, usually after the course ends. Deleting your SQL-Campus account doesn't remove your practice-environment login automatically; write to us at mathis@sql-campus.de for that.
8. Instructor verification
Anyone who wants to be approved as an instructor submits links to proof documents. Our administrators review them; we store the links, the status and the outcome of the review. The legal basis is Art. 6(1)(b) GDPR.
9. Access via MCP (access tokens)
Instructors and administrators can create personal access tokens to use SQL-Campus via the Model Context Protocol (MCP) from their own tools, such as an AI assistant. We store the token's name, its first characters, a hash, its expiry date and when it was last used. We treat requests made with the token like requests from you.
Which tool you connect is your choice. Whatever SQL-Campus returns to that tool is processed by its provider under their own responsibility. The legal basis is Art. 6(1)(b) GDPR. A token is deleted when you revoke it or delete your account.
10. Feedback
You can send us notes through the feedback button. We store your message, the address of the address and title of the page you send it from, details of the page (e.g. which exercise was open), your screen size and language and – unless you untick the box – what you typed on the page, such as your SQL query. If you are signed in, we link the feedback to your account and store your browser identifier – unless you choose “Send anonymously”. Only administrators can read feedback.
The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is fixing bugs and improving the platform. We delete feedback once we no longer need it to deal with it. If you delete your account, it is unlinked from your account.
11. External content in exercises
Images, audio and video files
Authors can embed images, audio and video files from other websites in exercises. When you open such an exercise, your browser loads the file directly from that website, whose operator receives your IP address. For PDF exports our server fetches images itself, without passing on any data about you. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest is offering exercises with illustrative material.
Videos from YouTube and Vimeo
Videos from YouTube or Vimeo are first shown only as a placeholder, without any connection to the provider. Only when you click “Load video” does your browser load the provider's player. The provider then receives your IP address and details of the page and may set cookies or local storage entries in your browser. We embed YouTube via the youtube-nocookie.com domain.
- YouTube: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland – Google's privacy policy
- Vimeo: Vimeo.com, Inc., USA – Vimeo's privacy policy
The legal basis is the consent you give by clicking (Section 25 (1) TDDDG, Art. 6(1)(a) GDPR). It covers only that one video and isn't stored; for further videos we ask again. This may involve transfers of data to the USA; details and the safeguards for them are in the providers' privacy policies.
12. Cookies and local storage
Without consent we only store what is strictly necessary for the platform to work (Section 25 (2) no. 2 TDDDG): a sign-in cookie, your language choice, drafts of ongoing exam answers, page titles for the breadcrumbs, whether you've seen the guided tour, the view picked under “View as” and your cookie decision. Comfort settings (such as how you sort tables) are only stored with your consent (Section 25 (1) TDDDG, Art. 6 (1) (a) GDPR) and only in your browser; you can withdraw it at any time via “Cookie settings”. See our cookie notice for details.
13. Recipients
Your data is only received by the parties named in this policy: instructors and administrators to the extent described, service providers that support us in running the platform as processors and – if you use them – Google, GitHub, YouTube, Vimeo or the tool you connect via MCP. Beyond that we only disclose data where we are legally obliged to.
14. Retention
We keep your account data for as long as your account exists. If you delete your account, your email address, name and password are removed immediately; we also delete links to Google or GitHub, MCP tokens, verification proofs, notifications and pending confirmation links, and unlink your feedback from your account. Your previous submissions and results remain attached only to an anonymized account that can no longer be linked to a person. Practice-environment logins are covered in section 7. Statutory retention obligations remain unaffected.
15. Your rights
You have the right to
- access your data (Art. 15 GDPR),
- rectification (Art. 16 GDPR),
- erasure (Art. 17 GDPR),
- restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- object to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation (Art. 21 GDPR),
- withdraw a consent with effect for the future (Art. 7(3) GDPR); processing before the withdrawal remains lawful.
In your account settings you can download your data yourself (JSON export with your account, submissions, exam attempts, courses, skill profile, feedback and tokens) and delete your account. For anything else, write to us at mathis@sql-campus.de.
You can also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), for example the authority responsible for us: The State Commissioner for Data Protection and Freedom of Information Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart (www.baden-wuerttemberg.datenschutz.de).
16. Security
The connection to SQL-Campus is encrypted (TLS). We store passwords only as salted hashes, sign-in and access tokens only as hashes, and submitted SQL code runs separately from our systems in isolated environments.
17. Changes
We update this privacy policy when the platform or the law changes. The version published here applies.