Retrieva Back to the privacy statement

Data Protection Impact Assessment (DPIA) for Retrieva

ControllerCodea Solutions (sole proprietorship, eenmanszaak), Prinses Beatrixstraat 5, 5953 LL Reuver, the Netherlands, Chamber of Commerce (KvK) 42180669
ServiceRetrieva, a study app with AI (retrieva.nl, retrieva.eu)
Privacy contactinfo@retrieva.eu (English) / info@retrieva.nl (Dutch)
Version1.2, 26 October 2026 (see §12 for what changed)
Related documentsPrivacy statement and terms version 2026-10-26.2, the record of processing activities and the data breach procedure
StatusAdopted by the controller; legal texts reviewed by a lawyer (see §11)
Next reviewNo later than 25 October 2027, or earlier on any change listed in §10

This DPIA follows Article 35(7) GDPR. It contains:

  1. a systematic description of the processing operations and their purposes;
  2. an assessment of necessity and proportionality;
  3. an assessment of the risks to data subjects;
  4. the measures to address those risks.

The Dutch version is the original. This English version has the same content.

1. Why a DPIA?

A DPIA is required when processing is likely to result in a high risk. The Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) and the European Data Protection Board (EDPB, guidelines WP248) list criteria. If processing meets two or more of them, a DPIA is generally required. Five apply to Retrieva:

Criterion (WP248)Applies to Retrieva?
Vulnerable data subjectsYes. The target group starts at the first year of secondary school (about age 12).
Innovative use of new technologyYes. Generative AI creates explanations and questions, and assesses open answers.
Evaluation or scoringYes, limited. The AI assesses answers to practice questions. This is feedback for the pupil only and has no consequences (see §6).
Data on sensitive or highly personal mattersPossibly. Photos of homework may accidentally contain names or other data of third parties.
Transfers outside the EEAYes. Hosting, AI and backups (also) run through the United States.

Not applicable: systematic monitoring, large-scale processing (not yet at launch), matching or combining datasets from different sources, and preventing data subjects from exercising a right or using a service.

Conclusion: a DPIA is required. This assessment covers private (consumer) accounts, for which Codea Solutions is the controller. If a school uses Retrieva, the school is the controller and Codea Solutions the processor; see §10 for what is then needed in addition.

2. Description of the processing

2.1 What Retrieva does

A pupil or student creates subjects and adds study material: a photo, a PDF, a Word or PowerPoint file, or typed text. From this, Retrieva produces:

Whatever was answered wrong comes back until the pupil knows it. At the pupil's request, a parent or guardian can receive a weekly summary containing totals only.

There is a free 7-day trial. After that, a paid subscription is available: Complete (one person) or Family (three separate accounts), monthly or yearly.

2.2 Purposes

  1. Providing the study service: account, study content, AI features, planning and progress.
  2. Payment, invoicing and keeping the legally required records.
  3. Preventing misuse and protecting minors: content moderation, limits on AI use, and a limited number of trial accounts per connection.
  4. Security, availability and recovery: backups, a log of administrator actions, monitoring.
  5. Communication:
    • service emails (confirmation, trial, subscription, invoices);
    • reminders and the weekly summary for parents, only if the user switches them on;
    • news, only to people who have or had a subscription.
  6. Measuring whether promotion works, in a limited way and without tracking technologies (see §4.3).
  7. Improving the service through "Is this wrong?" reports and reasons given when cancelling or deleting an account.

2.3 Data subjects

GroupNotes
Pupils and studentsThe core group. From about age 12; under 16 with permission from a parent or guardian.
Adult usersFor example for a driving theory test, a professional exam or a course.
Payers18 or older. Often a parent on a Family subscription.
Family membersInvited by the payer. Each has their own account.
Parents or guardians receiving the weekly summaryA third party, only after their own confirmation (double opt-in).
Third parties in uploaded photosFor example the name of a classmate or teacher on a worksheet. Not intended; see R2.
Website visitorsCounted without a cookie and without lasting personal data.

2.4 Personal data

CategoryDataSource
Accountname, email address, password (scrypt hash only; older accounts still bcrypt); when logging in with Google: name, email and Google IDUser, Google
Study contentsubjects, questions, answers, notes, flashcards, tests, planning, results, photos and filesUser, AI
Settingslanguage, theme, daily goal, reminders, parent's email addressUser
Usagedays and hours of activity (hourly data kept 90 days), AI actions and AI costs per daySystem
Payments and invoicesplan, amount, date, status, Mollie reference, invoice details; for bank transfers also the name and account number shown on the bank statementUser, Mollie, bank
Consent recordstime and version of acceptance of the terms and privacy statement, age confirmation, waiver of the right of withdrawalUser
Originchannel, campaign and ad from the link, language page, country (from the browser language), sign-up methodThe link with which the app was opened
SecurityHMAC of the IP address at sign-up (7 days); IP address only briefly in working memorySystem
Content moderationcategory and time of a hit, never the contentOpenAI moderation
Reports and reasons"Is this wrong?" (with the account), reason for cancelling (with the account), reason for deleting (anonymous)User
Email logaddress, subject, type, delivered or not; no contentSystem

Special categories of personal data (Art. 9 GDPR) and criminal-offence data are not requested and not needed. Users are asked not to upload such data: in the terms, in the privacy statement and when uploading. See R2 for what happens if they do anyway.

2.5 Systems and parties

PartyRoleWhat they receiveWhereTransfer basis
Replit, Inc.Processor: hosting of the app, the database (SQLite, with PostgreSQL for durable storage), uploaded files and server-side backupsAll data in §2.4European Union (Replit, Inc. is based in the US)Replit's general terms and privacy policy; Replit only offers a separate data processing agreement on more expensive plans
Anthropic, PBC (Claude)Processor: AI for explanations, questions, summaries, study plans and assessment; the analyst in the admin panel receives totals onlyText and images the user submits for an AI feature, with language and level; no name or email addressUnited StatesSCCs in Anthropic's data processing agreement (part of its commercial terms)
OpenAI (agreement with OpenAI Ireland Ltd.)Processor: moderation of input before the AI; only when photo questions are switched on, also creating an image for a questionInput for AI features (text, photos, files) without name or email; for images only a description written by our AIIreland / United StatesSCCs in OpenAI's data processing agreement
Google (Google Ireland Ltd. / Google LLC), via Google WorkspaceProcessor: all outgoing email (info@retrieva.nl and info@retrieva.eu); Google Drive of the Workspace account for the encrypted backups and the invoice PDFsEmails (address, content of service emails); backups encrypted only (AES-256-GCM, key not held by Google); invoice PDFsIreland / United StatesEU-US Data Privacy Framework (Google LLC is certified) and SCCs in the Google Workspace data processing terms
Mollie B.V.Independent controller for payment dataName, email, amount; bank and card details go directly to MollieNetherlandsn/a (EEA)
Google (Sign in with Google)Independent controllerOnly if the user chooses to log in with GoogleIrelandn/a
Monitoring service, MetaNot recipients of personal data: the monitoring service only checks whether the site is reachable; from Meta we only fetch totals for our own adsNothing about individualsn/an/a

No Meta Pixel, no Conversions API, no third-party analytics. By default, Replit injects its own statistics script into published pages. It has been switched off in the deployment, and our Content Security Policy would block it in any case.

2.6 Data flow (simplified)

Pupil's browser ──https──▶ Retrieva server (Replit, EU)
   │                          ├─▶ database and files (Replit, EU)
   │                          ├─▶ moderation (OpenAI) ──▶ AI answer (Anthropic, US) ──▶ back to the pupil
   │                          ├─▶ email via Google Workspace (service email, invoice, parent's weekly summary)
   │                          ├─▶ daily backup, encrypted ──▶ server + PostgreSQL (Replit) + Google Drive (Workspace)
   │                          └─▶ Mollie (only when paying; bank/card directly at Mollie)
   └── only functional storage in the browser (login cookie, settings); no tracking cookies

2.7 Retention periods

DataPeriod
Account and everything the user createdUntil the user deletes it, or after 24 months without activity, with an email warning about 30 days in advance. A running paid subscription is never removed.
After deletionRemoved from the database and disk immediately. If an administrator deletes the account, a snapshot is kept for 30 more days.
BackupsOne per day, encrypted, 10 days at most, in all three locations.
Payments and invoices7 years (tax retention obligation). Payments are unlinked from the account when it is deleted.
Reason for deletionAnonymous, 24 months at most.
Email log6 months.
Log of administrator actions12 months.
Hourly activity, content moderation hits90 days.
Payment attempts that were not completed30 days.
HMAC of the IP address at sign-up7 days.
Messages to usAs long as needed, then 2 years at most.
Login sessions24 hours at most, or 7 days with "Remember me".

The app enforces these periods itself every night.

3. Lawfulness

ProcessingLegal basis (Art. 6 GDPR)
Account, study content, AI features, settings, planningPerformance of a contract (b)
Payments, invoices, withdrawalContract (b) and legal obligation (c, tax retention)
Consent records, age confirmation, waiver of the right of withdrawalLegal obligation and legitimate interest (proof)
Content moderation, limits on AI use, trial accounts per connectionLegitimate interest (f): protecting minors and preventing misuse
Backups, log of administrator actions, securityLegitimate interest (f)
Origin at sign-upLegitimate interest (f). Nothing is stored on the device (see §4.3). Users can object.
Reminders, weekly summary for parentsConsent (a). Can be switched on and off in Settings, with an unsubscribe link in every email.
News by emailLegitimate interest plus Art. 11.7(3) of the Dutch Telecommunications Act (own customers, own service). Only to people who have or had a subscription; can be switched off at sign-up, in Settings and from every email.
"Is this wrong?", reason for cancellingLegitimate interest or consent; always voluntary

Minors. The account is based on the contract, so the age-16 threshold of Art. 8 GDPR does not apply to the service itself. It does apply to processing based on consent: reminders and the weekly summary. At sign-up, a separate checkbox has users confirm that they are 16 or older, or that a parent or guardian has given permission. For processing based on consent, Retrieva goes further (since version 1.1):

The controller considers these reasonable efforts within the meaning of Art. 8(2) GDPR, because:

Only someone aged 18 or over can take out a paid subscription.

4. Necessity and proportionality

4.1 Purpose limitation and proportionality

Each processing operation belongs to a purpose in §2.2. Study content is not used for advertising, not sold and not used to train AI models. Under the API terms of Anthropic and OpenAI, they do not use API data for training.

4.2 Subsidiarity

The AI features are the core of the service and cannot work without sending the study material. An AI service within the EU was considered. Anthropic (Claude) was chosen for the quality of its explanations, combined with data minimisation (no name or email) and contractual safeguards (SCCs). Replit was chosen for hosting, with the servers, the database and storage in the European Union.

4.3 Data minimisation

4.4 Accuracy

AI can make mistakes. This is stated in the terms, on the website and in the app. Therefore:

4.5 Storage limitation

See §2.7. Everything is removed automatically, including from backups (after 10 days).

4.6 Transparency

4.7 Data subject rights

5. Transfers to the United States

PartyMechanismAdditional safeguards
ReplitReplit's general terms and privacy policyhttps; passwords hashed; backups encrypted with our own key; uploads accessible to the owner only
AnthropicSCCs (Anthropic data processing agreement)No name or email; no training on API data; only what is needed for one answer
OpenAISCCs (agreement with OpenAI Ireland Ltd.)No name or email; moderation without the content being kept by us; images only from an AI-written description and only when photo questions are on
Google (Workspace)DPF (Google LLC) and SCCs (Workspace terms)Backups encrypted with AES-256-GCM; Google does not hold the key. Email is transactional. Workspace account protected with two-step verification

Transfer assessment. We consider the risk of access by US authorities to this data to be low. It concerns study material and learning data with no political, financial or special-category sensitivity. Content goes to the AI services without identifying data. Backups are stored at Google in encrypted form only. The live database at Replit is not encrypted in this way. It is stored in the European Union, but Replit is a US company and can be asked for access under US law. Without a data processing agreement with standard contractual clauses (which Replit only offers on more expensive plans), this is the largest residual risk. It is accepted, with the safeguards in the table.

An appeal against the EU-US Data Privacy Framework is pending before the Court of Justice of the EU. If the framework falls, the SCCs remain as the legal basis.

6. Automated decision-making and AI

7. Risks to data subjects

Scale: likelihood low, medium or high; severity limited, significant or serious. Residual risk is the risk after the measures.

#RiskLikelihoodSeverityMeasuresResidual risk
R1Unauthorised access to study content and photos through a stolen password or a flaw in the separation between accountsMediumSignificant (photos of minors, personal notes)scrypt hashes; limits on login attempts; session cookie httpOnly and not sent to other sites; uploads only for the logged-in owner (a link gives no access); automated test of separation between accounts; "Log out everywhere" and a notice on every new admin login; Sign in with Google availableLow
R2Third-party data or special-category data in uploaded photos (classmates' names, health)MediumLimited to significantInstruction in the terms, the privacy statement and at upload to cover such data; sent to the AI without the user's name or email; photos for the owner only; deletion always possible; retention periods; no training on contentLow to medium (accepted; depends on user behaviour)
R3AI provider retains or uses input longer or differently than expectedLowSignificantData processing agreements with SCCs; under their terms no training on API data and only temporary retention for safety; no identifying data sent; only what is needed for one answerLow
R4Access by authorities outside the EEA (US)LowSignificantSCCs or DPF per party; backups encrypted with our own key; minimisation towards the AI; nature of the data (study material)Low to medium (accepted; see §5)
R5Incorrect AI explanation or assessment, so a pupil learns something wrongMediumLimitedClear notice that AI makes mistakes; showing first what was read; review screen; no question without an explanation; "Is this wrong?"; assessment can be changed; no consequences outside the appLow
R6Minors and inappropriate content or misuse (sexual material, hate, self-harm, using the AI for things other than learning)MediumSeriousModeration of all input before the AI; inappropriate uploads deleted immediately and kept out of backups; for self-harm a notice with help resources, counted without the account; AI can be switched off for an account after repeated hits; safety rules in every AI prompt; usage limitsLow
R7Data breach via backups (Drive or PostgreSQL)LowSeriousAES-256-GCM with our own key, not held by Google; Workspace account with two-step verification; 10 days at most; administrators onlyLow
R8Keeping data too longLowLimitedAutomatic deletion per §2.7, every night, including backups; warning before deletion after inactivityLow
R9Profiling or unwanted marketingLowLimitedNo tracking cookies, pixels or third-party analytics; origin not stored on the device and limited to domain or campaign; news only to (former) paying customers and can be switched off at sign-up; unsubscribe link in every email; no profilesLow
R10Weekly summary gives a third party (parent) insight into learning behaviourLowLimitedOnly if the user sets it up; the parent confirms themselves (double opt-in); totals only; can be switched off by user and parentLow
R11Misuse by an administrator (insider) or a compromised admin accountLowSeriousAdmin panel with password, emailed code and authenticator app; notice on every new login; actions logged (12 months); one administrator; two-step verification on all linked supplier accountsLow
R12Loss of data (availability)LowSignificantDaily backup in three locations (server, PostgreSQL, Google Drive); restore tested, with an automatic safety copy and a per-table check; availability monitoring; export for the userLow
R13Payment dataLowSignificantBank and card details only at Mollie; we keep only amount, status and reference; invoices 7 years as required by lawLow
R14Rights cannot be exercisedLowLimitedExport and deletion by the user in the app; response within 2 working days; parents can make requests for their childLow
R15Credentials or keys leaking (API keys, sessions)LowSeriousKeys in a protected secrets store, not in the code (checked, including the history); the source code is not public; admin sessions stored as hashes only; breach procedure with steps to revoke keysLow

8. Measures in summary

Technical

Organisational

9. Conclusion

After the measures, the residual risks are low. For R2 (third parties in photos) and R4 (transfers to the US) the residual risk is low to medium. Both are deliberately accepted, for the reasons in §5 and §7.

No high residual risk remains. Prior consultation of the Dutch Data Protection Authority (Art. 36 GDPR) is therefore not required. The processing may proceed as described.

10. When this DPIA must be revisited

Review on:

11. Record

Prepared15 October 2026, updated 25 and 26 October 2026, based on Retrieva's working code and documentation
Legal reviewThe legal texts were reviewed by a lawyer in October 2026. The advice has been implemented, except the point about ending a yearly subscription early after a change in features (a deliberate choice).
Open actions(1) Keep copies of the accepted data processing agreements of Anthropic, OpenAI and Google Workspace, with dates. (2) At the first school: the points in §10. (3) Check whether Art. 50(2) AI Act (machine-readable marking) applies to the images with questions; they are made with AI.
Adopted byThe owner of Codea Solutions, 25 October 2026

12. Changes

Version 1.2 (26 October 2026)

Version 1.1 (25 October 2026)