Privacy Policy
Version 2026-09-06 · effective 2026-09-06
This is a superseded version, kept so that what you accepted stays readable. Read the current version.
On this page
This policy explains how StudyingTools ("we") processes personal data when you use StudyingTools. It is the information required by Articles 13 and 14 of the General Data Protection Regulation (GDPR).
1. Controller
StudyingTools, (not yet published), Finland (Business ID (not yet published)) is the controller for your account data and for the operation of the Service. Contact for privacy matters: [email protected]. We have assessed whether a data protection officer is required at our size and processing and concluded that one is not; that assessment is recorded and revisited when the processing changes.
For the content you upload, the roles are different. A lecture recording contains the voices of a lecturer and of students; slides and documents may name people. For that personal data you are the controller and we are your processor: we process it only on your instruction, for your private study, under the processor terms.
2. What we process and why
| Data | Why | Legal basis | Kept |
|---|---|---|---|
| Account: email address, password hash, display name, UI language, country, the version of the terms you accepted and when | to provide the Service and its contract | contract, Art. 6(1)(b) | life of the account |
| Your material: recordings, slides, documents, and the transcripts, presentations, narrations and quizzes generated from them, plus the object-store keys that locate them | to provide the Service | contract | life of the account, or until you delete the item |
| Your study activity: quiz attempts and answers — including free-text answers and the automated feedback written about them — progress, grades you enter, the study plan | to provide the Service | contract | life of the account |
| Processing jobs: the record of each transcription, generation and narration job, including the prompt sent to and the response received from the language model | to run and debug the pipeline, to show you what happened, to correct errors | contract; legitimate interest in a working service | life of the account |
| Subscription and allowance records | to provide paid features, to account for use | contract; legal obligation for accounting records | life of the account; accounting records as the law requires |
| Notification preferences and the notifications sent to you | to tell you when material is ready and when something needs you | contract; email notifications on your consent, which you can withdraw in Settings | life of the account |
| Support conversations you open, and reports you file from inside the Service, with the diagnostic context the Service attaches | to answer you and to fix defects | contract; legitimate interest | life of the account, or for guest requests until the retention below |
| Technical logs: request logs with your IP address and the path requested, application logs with the names of submitted fields (never their values), a correlation id per request | security, abuse prevention, debugging | legitimate interest, Art. 6(1)(f) | see §5 |
Grades you enter are self-declared academic performance. They are not special-category data, but we treat them as sensitive: they are visible only to you and, in aggregate form, to the operator for the purpose of improving the Service.
We do not use your data for advertising, we do not sell it, and we do not build profiles of you for anyone else.
3. The one disclosure that matters most
Your lecture audio, the transcript made from it, and the text of your slides are sent to a language-model provider in the United States to be processed. This routinely includes other people's voices and copyrighted university material. The provider is listed on the subprocessors page with the transfer safeguard we rely on, and we only use a paid tier whose terms exclude training on submitted content. If that is not acceptable to you, do not upload material to the Service.
4. Who else touches your data
Only the processors listed on /legal/subprocessors, each under a data processing agreement, for the purpose stated there. We give 30 days' notice on that page before a new subprocessor starts receiving data. Public authorities receive data only where the law obliges us.
5. How long we keep it
Account data and your material are kept for the life of the account. Deleting an item inside the Service removes it from every view immediately, and the underlying rows and files are permanently erased 30 days later by a nightly job. Stored files that nothing in the Service refers to any more are swept weekly. A data export you request is kept for seven days and then deleted.
Technical logs: request and application logs are rotated daily and kept for 14 days. Support requests from people without an account are deleted 90 days after they are resolved, or after 180 days of silence. Password-reset links expire after one hour and expired requests are removed nightly. Automated backups of the database and of stored files are taken nightly and kept for a bounded number of copies; a deleted account leaves the live system immediately and leaves the backups as they age out.
6. Your rights
You can access, correct and export your data, ask for it to be erased, restrict or object to processing based on legitimate interest, and withdraw a consent at any time without affecting what was done before. The account page lets you change your details and preferences, export your data as a single archive, and delete your account yourself — immediately and irreversibly: every file and every row the account holds is erased, the subscription is cancelled, and what remains carries no identifier of yours (the accounting rows the law requires us to keep for six years, and the record of requests to the language model with every prompt and answer blanked). For anything the page does not cover, or if you cannot sign in, write to [email protected] and we answer within one month. You may also complain to the Finnish Data Protection Ombudsman (Tietosuojavaltuutetun toimisto, tietosuoja.fi).
7. Cookies
The Service sets only the cookies it needs to work — see the Cookie Policy. There is no analytics, no advertising and no tracking.
8. Security
Passwords are stored as salted hashes. Traffic is encrypted in transit. Uploaded files live in an object store addressed by keys that include your account id, and a link to a file is signed and expires. Access to the operator's tools is limited to the operator's own accounts. If a breach affects your data we notify the supervisory authority within 72 hours and tell you when the law requires it.
9. Changes
A material change to this policy is versioned and published at its own address, and you are asked to accept the new version before you continue. Older versions stay readable.
Previous versions
- 2026-09-29
- 2026-09-06