1. Who we are
Codingo is operated by Zenico Technologies SL (NIF B75884825), Plaza de Juan Zorrilla, 2, 28003 Madrid, Spain ("we", "us"). We are the controller of your personal data under the EU General Data Protection Regulation (GDPR) and Spain's data protection law (LOPDGDD). See also our legal notice. For any privacy question or request, write to hola@zenico.es.
2. What we collect
- Account data: your email address and, if you choose, a display name. If you sign in with Google, we receive your name, email address and profile picture from Google. Passwords are handled by Firebase Authentication; we never see them.
- Learning data: the code you write, test and submit; the test results; your conversations with the AI tutor and the hints you ask for; your readiness checks and their results; your mock interviews and their debriefs; your interview date and daily practice time, if you set an interview plan; and the progress we work out from all of this (mastery per pattern, recurring mistakes, edge cases you miss).
- Readiness check without an account: your answers, the time you took on each question and, if you try it, your code for the coding problem. They are stored under a random ID kept in your browser, not with your name, email or IP address. The results page (your readiness estimate, strongest and weakest patterns and the mistakes you made) can be seen by anyone who has its link, and contains nothing that identifies you. If you create an account in the same browser afterwards, the check becomes part of your learning data.
- Analytics, only if you agree: with your consent, Google Analytics records how the site is used: the pages you visit, how you arrived (for example from a shared link), your device and browser type, your approximate location (country and city, worked out from your IP address, which Google Analytics does not store), and a few events such as starting or finishing a readiness check, sharing a result, creating an account or setting an interview plan. These events carry no answers, code or names. See section 9.
- Usage counts: how many AI replies, test runs and practice problems you use per day, week and month, to apply the limits of your plan.
- Feedback: what you send with the Feedback button, with the page you were on and your browser type.
- Payment data: if you buy a paid plan, Stripe processes the payment for us. You enter your card details on Stripe's checkout page; they never reach our servers. We receive and keep your plan, its dates, the amount paid, your billing country (for tax) and the email address the receipt goes to.
- Technical data: our servers log requests and errors (for example the time, the page or endpoint, and error messages) to keep the service running and secure.
We do not use advertising or advertising cookies, we do not sell your data, and analytics runs only if you agree to it.
3. Why we use it, and on what legal basis
- To provide the service (contract): your account, running your code, choosing your next problem, tutor feedback, mock interviews and your progress.
- To apply plan limits and take payments (contract, and legal obligations such as tax records).
- To keep the service secure and working, and to improve it (our legitimate interests): preventing abuse, fixing errors, and measuring the quality of the tutor's answers. When we review tutor quality we use problems and code from our own test bank, not your submissions, unless you sent them to us as feedback.
- To understand how people use the site, and improve it (your consent): Google Analytics, only after you accept it in the cookie banner. You can withdraw your consent at any time (section 9).
- To answer your feedback and requests (legitimate interests, or our legal obligations for privacy requests).
4. The AI tutor
Tutor replies, hints, feedback and mock interview debriefs are written by a large language model from DeepSeek. To answer you, we send DeepSeek only what the task needs:
- the problem, your code and its test results;
- your question and the earlier messages of that problem's conversation (for a mock interview, how you described your approach);
- a short summary of your progress: the pattern you are practising, your level on it, how many problems you have tried and solved, and the kinds of mistakes you make most.
We never send your name, email address, account identifier or IP address: requests go from our servers, so DeepSeek cannot tell who you are or link one request to another as yours. Before anything is sent, we also remove email addresses, phone numbers and web links from your messages and code. Please do not type other personal information (such as your name or employer) into your code or tutor messages.
DeepSeek is based in the People's Republic of China and processes this data there, under its own terms.
5. Who we share data with
We share data only with service providers that process it for us:
- Google (Firebase Authentication, Cloud Firestore, Firebase App Hosting and Cloud Logging): sign-in, storage of your account and learning data, hosting and logs. Data is stored in the United States.
- Google Analytics (Google): site analytics, only with your consent. Google acts as our processor; we have turned off Google signals and advertising features, so the data is not used for ads.
- DeepSeek: the AI tutor, as described above.
- Stripe: payments, receipts and the billing portal, if you buy a paid plan.Stripe also uses payment data on its own account to prevent fraud and meet its legal duties, under its own privacy policy.
We may also disclose data when the law requires it, or to protect our rights or the safety of others.
6. International transfers
Our providers process data outside the European Economic Area, in the United States and, for the AI tutor, in China. For transfers to the United States (Google, including Google Analytics, and Stripe) we rely on the EU–US Data Privacy Framework, under which both are certified, and on the European Commission's Standard Contractual Clauses otherwise. What we send the AI tutor in China is limited to the exercise and your work on it, without any detail that identifies you (section 4), which keeps what leaves the European Economic Area to the minimum the tutor needs.
7. How long we keep it
- Your account and learning data: until you delete your account.
- Readiness check answers made without an account: deleted automatically about 7 days after you start the check.
- Readiness check results pages: kept so shared links keep working. To have one removed, send us its link.
- Readiness check answers in anonymous form (which kind of question, how hard, right or wrong; no ID, account or address): kept to measure and improve the check's accuracy.
- Analytics data (only if you agreed): up to 14 months in Google Analytics.
- Your analytics choice: in your browser, until you change it or clear the site's data.
- Server logs: 30 days.
- Payment and invoice records: as long as tax law requires (usually several years).
- Feedback you send: until it has been handled, and at most until you delete your account.
8. Your rights
You can access, correct, export or delete your data, object to or restrict how we use it, and withdraw any consent you gave. You can delete your account and all its data at any time from the account menu. For anything else, write to hola@zenico.es; we answer within one month.
If you think we have not handled your data properly, you can complain to the Agencia Española de Protección de Datos (aepd.es), or to the authority where you live.
10. Children
Codingo is for people aged 16 and over. We do not knowingly collect data from younger children; if you believe a child has given us data, contact us and we will delete it.
11. Security
Data is encrypted in transit and at rest by our providers. Code you run executes in an isolated sandbox with no network access. Access to production data is limited to the operator.
12. Changes
If we change this policy in a way that matters, we will tell you on the site or by email before the change takes effect. The date at the top shows the current version. See also our terms of service.