Privacy Policy
Last updated: 21 November 2026
1. Introduction
Welcome to Diclasso! We are committed to protecting your privacy and ensuring the security of your personal information. This Privacy Policy describes what data we collect, how we use it, and how we protect it.
Diclasso is operated by Forloop OÜ (registry code 16192929, Estonia). We are the data controller for this data within the meaning of GDPR Article 4(7).
Scope: this policy applies to all of our domains — digiklass.ee, its English-language version diclasso.com, the Estonian-language site for kindergartens digiaed.ee, and the supporting domains liitu.ee and classo.it (join links for games and polls) and lingi.ee (short links). All of them share the same data controller, the same servers, and the same databases. There is one account across all sites: an account created on digiaed.ee can also be used to sign in on digiklass.ee and vice versa.
2. Scope of Service and Our Role
Diclasso is a web-based toolkit that is free to use and intended for the personal use of the registered user. The primary user group is teachers in their own teaching, but the tools are equally suitable for other private or small-scale events — for example, team activities at work, the programme of a party, a club's activities, or other similar situations. The user registers an account as a private individual using their email or Google/Microsoft account.
Session participants (e.g., players, respondents) do not create accounts in Diclasso and are not required to. A participant joins only via a link or session code shared by the user, predominantly anonymously or under a nickname of their own choice. The exception is list-linked tools (e.g. Portfolio, Computer Skills, Sociometry): there the participant is linked to a member of a list entered by the user — via a class code and name selection, a personal code, or a personal card — but even there they do not create an account.
The user is responsible for ensuring that the data they enter (e.g., the names of persons in a list) is permitted to be entered under the applicable rules and law.
3. Information We Collect
3.1 Authentication Data
When you sign in with Google or Microsoft, we collect:
- Account ID (Google or Microsoft)
- Email address
- Name
- Profile picture URL
- Account creation and last login timestamps
When you register with email and password, we collect:
- Email address
- Name
- Password (stored as a cryptographic hash, never in plain text)
- Email verification status and token
- Account creation and last login timestamps
3.2 Security-Related Data
To ensure account security, we collect:
- Login attempt history (IP address, timestamp, success status)
- The IP address and browser description of the last sign-in, stored with the account — overwritten at every sign-in and deleted together with the account
- Password reset tokens (temporary, expire automatically)
- Account lockout status (activated after 5 failed login attempts)
- Security audit trail — a record of the system refusing access to someone else's content, or of an account security action (email change, content sharing, admin export): timestamp, IP address, account and type of action, without the content itself
- Submission attempts on the contact form and the license request form — a record in the same audit trail of whether the form was sent or rejected by the spam guard: timestamp, IP address, browser description, message length and script (e.g. Latin or Cyrillic), without the message, name or email address. We use it to keep spam out
- Join code entries (joining a game, poll or other activity with a code): IP address, browser description, the code entered, timestamp and whether joining succeeded. We use this to prevent codes from being guessed — if many different wrong codes are tried from one IP address, it is blocked temporarily
- Web server request log (IP address, timestamp, requested address without sharing tokens, response code) — we keep a copy so that in the event of a security incident we can determine whose data was affected and to what extent. Without it, we would have to assume the worst in case of a breach. In the archive, the keys of sharing links are replaced with a hash. In the hosting provider's own log (7 days) and in backups, addresses may appear in full until they expire.
3.3 Content You Create and Session Content
To provide our services, we store content entered by the user or generated in their sessions:
- Names of lists (e.g., class, team, group)
- Names of list members (entered by the user — we recommend using first names, initials, or nicknames where entering the full real name is not necessary)
- Responses and results from polls, votes, games, and quizzes
- In practice applications (e.g., Computer Skills), the progress of a learner linked to a list: completed exercises, time taken, number of mistakes, a mark for hint use, and active practice time (time during which the exercise was open and the learner was active)
- When a signed-in user joins a Computer Skills course that is not linked to a list with their own account ("Join the course"): the fact of joining and the same progress as for a learner linked to a list. The course organiser sees the account name, email address and progress on that course — this is stated before joining. On joining, exercises already completed on the account are also added to the course (without time and mistakes). The member can leave the course at any time and the organiser can remove them; in both cases the progress on that course is deleted.
- Event registrations
- In Portfolio (e-portfolio), entries linked to a list member: text written by the member, photos of their work, audio recordings, the member's self-assessment (how it went, what they will try next), feedback from the portfolio owner and entry times; also the code of the member's personal card. Photos are re-encoded, which removes their metadata (including location and camera data).
- Personal list cards (if the list owner turns them on): each member's card code and the member's optional PIN, which we store only as a one-way hash (we cannot see the PIN itself), together with the number of consecutive wrong PIN attempts. A new card also removes the PIN; card and PIN data are deleted once the member or the list has been permanently deleted (after 30 days in the trash).
We do not ask for or store from session participants email addresses, phone numbers, dates of birth, profile pictures, national identifiers, or other direct identifiers. For participants we only store what the participant themselves enters when starting the game/poll (e.g., a nickname), plus a technical session ID. In most tools, asking for the participant's name is optional and the user can turn it off. In list-linked tools (see §2), the participant's name comes from the user's list, not from the participant.
Exceptions:
- Sign-ups (Event, Choice): the organiser may require an email address from the person signing up. We use it to send the sign-up confirmation with an edit link, the organiser's messages, reminders and change notices, and — on a Choice waiting list — a notice when a place becomes free. Only the organiser sees the address, and it is kept with the sign-up until the organiser deletes the event or the choice.
- Team contribution assessment (Team Input): team members rate each other by name. The rater's name, the rated member's name, the points and a comment are stored. The creator of the assessment sees who rated whom and how; members do not see each other's ratings.
- Friend Words, Friend Drawings and Friend Colors: participants write, draw or pick a color about a classmate by name. The giver's name, the recipient's name and the content (text, drawing or color) are stored. The recipient sees the result without the giver's name. The creator of the round and a co-organizer see who wrote or drew what for whom, so that unsuitable content can be hidden before it is shown. The names are entered by the creator of the round.
- Exercises linked to a list (Video quiz, Fill in the blanks, Timeline, Preference groups): the list member's name, their answers or preferences, the result and the times of activity are stored. If the exercise is not linked to a list, the name entered by the participant is stored.
- Extra info in Preference groups: the creator of an allocation may add extra info about participants (e.g. an email address or class) — by importing it from a table, entering it manually or asking participants to enter it when responding. It is stored together with the participant's response. The extra info is visible to the creator and their co-managers; a participant is only shown their own details. Diclasso does not send emails to these addresses — the creator can copy them to pass on the results themselves. The extra info is deleted together with the participant's response (see §10) or immediately when the creator removes the field.
3.4 File Collection (Koguja)
When using the file collection feature with Google Drive or Microsoft OneDrive integration, we store:
- Encrypted cloud service credentials (Google Drive or OneDrive)
- Collection session data (title, description, folder ID)
- File metadata (name, size, type)
- Submitter name (if requested)
3.5 Technical Data
We automatically collect:
- Session cookies (for authentication, 30-day validity) — the full cookie list is in §12
- Browser and device information
- IP address — used for security purposes (see §3.2) and to determine the country at the time of the request; the IP address is not stored in page-view statistics
- Country and network operator (e.g. "Elisa Eesti AS") — derived from the IP address using a database file located on our own server. No IP address is sent to any external service for this. We do not determine or store city-level location. The network operator name lets us separate real visitors from data-centre bots in our statistics
- Application usage statistics and page views (server-side, no cookies or third parties). A visitor who is not signed in is identified only by a daily-salted hash (IP + browser information) — it cannot be traced back to a person and is different the next day. For signed-in users, page views are linked to the account, see §4
- Search queries — text typed into the site's search boxes, with time, language and domain, without IP address or account link. We use them to see what people search for and do not find
- Game run results in some games (Inimene linnas, Mereröövel, Ninjalohe, Tuli vs jää) — how far the player got, points, duration, number of players and whether a touch screen was used, without name, IP address or account link. We use them to see where players get stuck and whether a game is too hard
- Campaign link source — if you open the site through a QR code in our printed material or a partner's link (
utm_sourcein the address), we store the source and material identifier with the page view (e.g. "tife / exit ticket"). The source is kept in your session for 30 days, and if you create an account in the same browser during that time, it is linked to the account. We use this only to learn which materials bring in users; no new cookie is set for this - Arrival source — if you come to the site from another website (e.g. a search engine or an AI chat), we store that site's domain and page path without query parameters with the page view (e.g. "google.com", "/search"). The first such domain is kept in your session for up to 30 days, and if you create an account in the same browser during that time, only this domain (or a note that you came directly) is linked to the account — not the full address or the search terms. We use this only to learn how people find the site; no new cookie is set for this
3.6 Browser Storage
We store in your device:
- Theme preference (light/dark)
- Application card order preferences
- Newsletter subscription status
- Local settings and unfinished work (e.g. drafts) in some applications, so that your work is not lost on page refresh
- In apps for children (e.g. Sõnasõber, Sõnavara, Inimene linnas), the child's profile or the players' names and their progress — on the device only, never sent to the server (see §11)
3.7 Feedback and Correspondence
If you send us a message using the feedback form or the contact form on the site, we store:
- The message content, chosen category, and rating
- Your name and email address — the feedback form takes them from your account, on the contact form you enter them yourself; for signed-in users the message is also linked to the account, so that we can reply
- The page address and browser information from which the feedback was sent (to reproduce issues)
- Our replies and the course of the conversation
3.8 Licenses and Quote Requests
If you request a license quote or conclude a license contract (see Terms of Service section 11), we store:
- The institution's name, registry code, and email domain(s); the number of pupils (the basis of the price) and the request message
- The contact person's name and email address — for signed-in users also the link to the account
- The license period, storage limit, price, invoice number, and payment date
- Email addresses on a list provided by the institution (e.g. colleagues using a personal email address), so that the license applies to them
- If you confirm your email address for a license: the address and the time of confirmation
- If you start a Plus purchase by card: the time you started the purchase, so that we can see whether it was completed
- For a Plus subscription: the Stripe subscription and customer identifiers and the subscription status (active, cancelled), so that we can extend the license after each annual payment
We neither collect nor see card details. A school license is paid by bank transfer against an invoice; a Plus card payment takes place on the page of the payment provider Stripe (see §7.11). From Stripe we see the amount, date, the buyer's name and email, and the card type and last four digits. Invoices, receipts and accounting source documents are kept in Forloop OÜ's accounting records for the period required by law.
3.9 Public Collection
If you publish your content in the public collection (see Terms of Service section 5.4), we store:
- the title, description, subject, grade and classroom situation of the published content, the publication time and the link to your account. These are public and may be indexed by search engines;
- a public name, if you enter one yourself. Without it, the author is shown as “Diclasso user” — your account name and email address are not shown in the collection;
- likes from signed-in users, the number of copies, and which item a copy was made from;
- reports: the reporting account, the reason and the explanation. The author does not see who reported; if an admin hides an item, the reason is emailed to the author.
When you unpublish, the item disappears from the collection. When you delete the content or your account, the item, its likes and its reports are deleted.
4. How We Use Your Data
- Service provision: delivering educational tools and features
- Authentication: user identification and account management
- Personalization: remembering your preferences
- Communications: sending important updates and newsletters
- Analytics: collecting application usage statistics to improve our service (server-side, without cookies or third parties)
- Licenses: responding to quote requests, activating licenses, and notifying about their end
- Security: detecting and preventing misuse
How "anonymous" the statistics really are. Statistics about visitors who are not signed in are pseudonymous: we store only a daily-salted hash from which a person cannot be identified. For signed-in users, page views and application launches are linked to the account. We use this for three things:
- Your own usage overview on your dashboard — when and which tools you have used. Only you see it (along with the system administrator, who has access to the database).
- Aggregate statistics — how often an application is used, at what times of day, from which country. Individual users are not distinguished in aggregate figures.
- Organisation summary — if an account's email address is on an organisation's domain (e.g. @school.edu), we may share usage figures aggregated by that domain with the organisation: how many users used Diclasso, which tools, and how often per month. The summary contains no names, email addresses or any individual's activity; figures below three people are hidden, and no summary is shared if fewer than five users from the organisation have created content. Accounts with a personal email address (e.g. Gmail) are not included.
We do not make automated legal or similarly significant decisions on this basis, we do not pass profiles to any third party, and we do not use them for advertising. If you do not want your usage linked to your account, let us know — we will remove the link manually (see also the right to object in §9).
5. Data Security and Hosting
We implement the following security measures:
- Secure database storage
- Secure password hashing
- Encryption of cloud service credentials (AES-256-CBC)
- Secure cookies (HttpOnly, Secure flags)
- HTTPS connection for data transmission
- Login attempt rate limiting (brute-force protection)
- Automatic account lockout after repeated failed attempts
- Email address verification on registration
- API request rate limiting
- Backups encrypted with AES-256 before they leave the server (see §10)
- Regular security updates
Hosting: Diclasso servers are located in the Opalstack hosting provider's Frankfurt (Germany) data centre. Videos uploaded by users are kept separately in Hetzner object storage in data centres in Germany and Finland (see §7.13), and encrypted backups in Hetzner's data centre in Finland (see §7.3). Data is stored in the European Union; host access from the US is described in §13.
Security updates and vulnerability management: We monitor security advisories for the libraries and server software in use and apply updates within a reasonable timeframe. Vulnerability tracking relies on public CVE databases. We do not perform regular external penetration testing — Diclasso is a free service intended for personal use.
Internal access: Access to the Diclasso system and databases is limited to Forloop OÜ representatives for the purpose of system administration. As part of this, the administrator may review files uploaded by users in order to detect and remove content that violates the terms; participants’ personal files (such as voice recordings and learning portfolio entries) are hidden by default in the administration view and every time one is opened, it is logged. In addition, the hosting provider (Opalstack) has technical access to the server infrastructure.
While we follow best practices, no system can guarantee 100% security.
6. Personal Data Breaches
If we become aware of a personal data breach (e.g., data leak, unauthorised access, loss or alteration of data), we will act as follows:
- We identify and document the nature, scope, and likely consequences of the breach.
- We assess the likely impact of the breach on users' rights and freedoms.
- If the breach is likely to result in a risk to the rights and freedoms of natural persons, we will notify the Estonian Data Protection Inspectorate within 72 hours of becoming aware of the breach (GDPR Article 33).
- If the breach is likely to result in a high risk, we will also notify the affected users without undue delay at their registered email address (GDPR Article 34).
- We maintain a register of breaches in which all identified personal data breaches are recorded together with the circumstances, consequences, and measures taken.
If you suspect that a personal data breach has occurred affecting the Diclasso system, please notify us immediately at mikk@digiklass.ee.
7. Third-Party Services
7.1 Google Services
- Google OAuth: for authentication, only if you choose to sign in with Google (Google Privacy Policy)
- Google Drive: for file storage, only if you choose this option
7.2 Microsoft Services
- Microsoft Azure AD / Entra ID: for authentication, only if you choose to sign in with Microsoft (Microsoft Privacy Statement)
- Microsoft OneDrive: for file storage, only if you choose this option
7.3 Backup Storage (Hetzner)
Our own automated backups (see §10) are uploaded encrypted to Hetzner Online GmbH object storage in its Helsinki (Finland) data centre — data remains within the European Union. Encryption happens on the server before upload and the key is held only on our server and in a password manager — Hetzner cannot read the backup contents. To protect against deletion and ransomware, no backup can be deleted for 30 days after upload. Until 29 October 2026 we kept backups in Google Drive; these were deleted on 2 November 2026 and Google permanently removes them from its systems within 30 days.
7.4 Fonts and Web Libraries
All typefaces (including Inter and OpenDyslexic) and web libraries (Bulma, Font Awesome and others) are served from our own server. They previously came from external content delivery networks (jsDelivr, cdnjs, Google Fonts), which meant every visitor's IP address reached those networks on page load. Since August 2026 no such request is made — loading the site's appearance no longer transmits anything to a third party.
7.5 YouTube
Some applications (Kuldvillak, Viktoriin, Kiirviktoriin, Sein, Klassitahvel, Luugikalender, Seiklusrada, Videoharjutus) allow users to add YouTube videos. The video player is loaded from the youtube-nocookie.com domain, which does not set tracking cookies until a video is played. Kiirviktoriin and Videoharjutus additionally load YouTube's script from www.youtube.com to control the player.
In participant views, the video is loaded only when the participant chooses to. On Sein, in Viktoriin, in a self-paced Kiirviktoriin game, on Seiklusrada, in Luugikalender and on a shared Klassitahvel, a "Show YouTube video" button is shown instead of the video — nothing is loaded from YouTube before it is pressed, and the participant's IP address does not reach YouTube (Google) servers. The video thumbnail shown on the button is fetched from YouTube by our server and kept in its cache for up to 60 days; YouTube then sees only our server's address. In Videoharjutus the video is loaded when the participant presses "Start". On the organiser's own screen (for example Kuldvillak, the Kiirviktoriin host view, the Klassitahvel editor) the video is loaded when the page is opened.
7.6 Hosting Provider and Email Delivery
Opalstack (a US-based company, with servers in Frankfurt, Germany) provides server hosting and email delivery (SMTP). Opalstack has technical access to Diclasso database files as part of the hosting service, but is not entitled to use the data for any other purpose.
7.7 Geolocation Database (DB-IP)
We determine a visitor's country and network operator from a database file stored on our own server (DB-IP Lite, licensed under CC BY 4.0), which we download once a month. No visitor IP address is ever sent to DB-IP or any other service — this is not a query-based service but a static file on our server. Data source: IP Geolocation by DB-IP.
7.8 Ko-fi (Donations)
Our support page contains a link to the external service Ko-fi. The link itself transmits no data — Ko-fi sees you only once you click and leave Diclasso. If you choose to donate, the entire payment takes place within Ko-fi (and their payment provider) under their terms; we neither see nor store payment details. Donating is not required in order to use the service.
7.9 Maps (OpenStreetMap)
Some applications display a map: Adventure Trail (GPS checkpoints along a route) and Event (the event's exact location, if the organiser has set one). Map imagery (so-called tiles) is loaded from OpenStreetMap Foundation servers. At that moment OpenStreetMap can see your IP address and which map area is being viewed; their privacy policy permits short-term retention of such data to protect the service.
- On the event page the map loads only after you click ("Show map"). Until you do, no request goes to OpenStreetMap. The location can also be opened in an external map app — that is an ordinary link, which likewise transmits nothing until clicked.
- In the Adventure Trail player view the map is part of the game and loads with the page.
- Address search (when setting an event location or building a trail) goes through our server to OpenStreetMap's Nominatim service — the searcher's IP address never reaches OpenStreetMap; only the address being searched is passed on.
7.10 Weather (MET Norway)
The Class Board weather widget shows the weather for the chosen place based on open data from the Norwegian Meteorological Institute (MET Norway) (licence CC BY 4.0). Requests go through our server: MET Norway receives only the rounded coordinates of the place, never the IP address of the person viewing the board. Place search in the widget settings likewise goes through our server to OpenStreetMap's Nominatim service (see §7.9). We cache the responses on our server without linking them to any user — weather for up to a few hours, place-name searches for up to 30 days.
7.11 Stripe (Plus card payment)
Plus can be paid by card on the page of the payment provider Stripe (Stripe Payments Europe, Ltd., Ireland). The buy button takes you to Stripe's payment page and passes along your email address and your Diclasso account number so that we can link the payment to your account. You enter card details directly with Stripe — we neither see nor store them. Plus is an annual subscription: Stripe keeps your card for the next annual payment and notifies our server when a payment is received or the subscription is cancelled. Stripe processes payment data under its own privacy policy, including for fraud prevention. You only go to Stripe's payment page if you decide to buy Plus.
7.12 Text-to-speech (Microsoft Azure Speech, Jutusta)
In some applications the computer reads text aloud. For this, our server sends only the text to be read to a text-to-speech service and receives an audio file in return — your name, account or IP address is not passed to the service. We use two services: Microsoft Azure Speech (Microsoft's North Europe data centre in Ireland, Microsoft Privacy Statement) and Jutusta, which provides Estonian voices (jutusta.ee).
- Dictation and Flashcards: sentences and words entered by a signed-in user. We store the finished audio with the content so the same text does not have to be sent again; it is deleted together with the content.
- Video Editor: the narration text of a signed-in user. The audio goes straight to your browser — it is not stored on our server.
- Computer Skills accessibility exercise (“Content for everyone”): the image description and link text a participant writes (up to 120 characters) are read aloud in a screen-reader voice, also without an account. The text goes only to Microsoft Azure Speech; we store neither the text nor the audio. We recommend not writing names in the exercise.
- The ready-made audio in applications (for example Bingo, Vocabulary, Time) was synthesised by us in advance — listening to it sends nothing out.
To monitor costs we keep a daily total: how many characters were synthesised and in which application. For a signed-in user the total is linked to the account, and that link is removed when the account is deleted. We do not keep the text itself in this total.
Jutusta is provided by Häälmeedia OÜ (Estonia). Its speech synthesis models run on Häälmeedia's own hardware in Estonia, and requests pass through the infrastructure of Cloudflare (Cloudflare, Inc.) at server locations in the European Union (Jutusta sub-processors).
7.13 Video storage (Hetzner)
When you add a video to your content (for example in Kiirviktoriin, Kuldvillak, Esitlus, Üritus or Klassitahvel), it is prepared in your browser and uploaded directly to the object storage of Hetzner Online GmbH (Germany). The primary copy is in Falkenstein (Germany) and a backup copy in Helsinki (Finland) — data remains within the European Union. Only the video file itself reaches Hetzner; your name and email address are not sent with it. The storage is not public: the viewing link is issued by Diclasso and is visible to everyone who can see the content the video was added to (for example the players you shared a quiz with).
A video stays in your video library until you delete it yourself. If a video is not in the library and no content (including content in the trash) refers to it any more, it is deleted automatically after 7 days. A video deleted by mistake remains in storage for up to 30 more days for recovery and is then permanently deleted. When your account is deleted, the video's link to your account is removed and the video is deleted under the same rule — if another user has made a copy of your content (for example from the public library), the video is kept for that copy.
7.14 Image search (Pixabay, TartuNLP)
In some apps (currently Sõnakaardid) you can search for free-to-use images. The search is made by our server: Pixabay (Pixabay GmbH, Germany) receives only the search word, and the images reach your browser from our address — your IP address, name and account do not reach Pixabay, and no Pixabay cookies are set. Because Pixabay does not search in Estonian, an Estonian search word is first translated into English with the University of Tartu machine translation service TartuNLP; it too receives only the search word. We keep search words and results in a cache, not linked to any user, so that the same search does not have to be repeated (Pixabay requires caching for 24 hours). The image you choose is saved with your content like any other uploaded image. If you click the “Pixabay” link in the search window, the Pixabay website opens and Pixabay's own terms apply there.
7.15 Leaked password check (Have I Been Pwned)
When you create or change a password, we check whether it appears in publicly leaked password lists (the Have I Been Pwned “Pwned Passwords” service). The check is made by our server, and only the first five characters of the password's SHA-1 hash are sent to the service — neither the password nor its hash can be derived from them. Your password, its full hash, your email address and your IP address do not reach the service, and the result of the check is not stored. If the password is on the list, we ask you to choose another one.
7.16 Timetable from EduPage
The Class Board timetable widget can be linked to a school's public EduPage timetable (EduPage, aSc Applied Software Consultants, Slovakia). The request is made by our server, and EduPage receives only the school's EduPage address and the timetable number — not your data, nor the data or IP address of anyone viewing the board. We do not use EduPage accounts or passwords. From the school's public timetable we cache on our server the part needed to build the timetable: the names of classes, rooms and subjects, lesson times and teachers' names, in the form the school itself has published them. The list of teachers' names is shown to a logged-in user who enters the school's address (to choose a teacher's timetable); only the timetable of the chosen class, teacher or room is saved on the board. The legal basis is legitimate interest (GDPR Art. 6(1)(f)): the school has published this data itself and we only display it as a timetable. The cache is refreshed once a day and deleted when no board has used the school's timetable for 90 days.
7.17 Dictionary (EKILEX)
Sõnalahing checks words and shows their meaning using EKILEX, the dictionary database of the Institute of the Estonian Language. The request is made by our server, and only the word being checked is sent to the Institute — the player's name, account or IP address is not passed to the service. We keep the answers in a cache on our server, not linked to any user, so that the same word does not have to be looked up again.
7.18 External image links (Kuldvillak)
The creator of a Kuldvillak game can also add an image to a question by giving the address of another website (“Image URL”). We do not store such an image: while the game is being created and played, it is loaded directly from the source website to the computer showing the game and to the game host's phone. The source website then sees the IP address of those devices, as with opening any web page. Participants' phones (the answer buttons) do not load images. If this does not suit you, upload the image to Kuldvillak instead — an uploaded image is served from our server.
8. Data Sharing
We do not sell or rent your data. We only share data:
- With your consent
- With service providers: who help operate the application (e.g., Google)
- For legal reasons: when required by court or authorities
- To protect rights: our or users' rights, safety, and security
- With an organisation, in aggregate: only the organisation summary described in §4, which does not distinguish any individual
9. Your Rights
Under the EU General Data Protection Regulation (GDPR), you have the right to:
- Access: obtain a copy of your personal data
- Rectification: request correction of inaccurate data
- Erasure: request deletion of your data
- Restrict processing: limit certain data processing
- Data portability: receive data in machine-readable format
- Object: prohibit data processing for certain purposes
- Withdraw consent: at any time
To exercise your rights, please contact us (see §15). You also have the right to lodge a complaint with the Estonian Data Protection Inspectorate (www.aki.ee/en).
10. Data Retention
- User account: retained while the account is active. If an account has not been signed in to for 12 months, we send a notice to the account's email address and delete the account together with all its content 30 days later, unless someone signs in during that time (Terms of Service section 3.4). We delete an account within 30 days of a deletion request.
- Unconfirmed account (created with an email address and password, email not confirmed, never signed in to): the name, email address, and password hash are deleted 30 days after registration. About a week after registration, we send a reminder with a new confirmation link (Terms of Service section 3.4).
- Unused account (no application used and no content created within 30 days of creating the account): we send a notice to the account's email address and delete the account 30 days later, unless someone signs in during that time (Terms of Service section 3.4).
- Trash (deleted content): when you delete content you created, it does not disappear immediately — it moves to the trash for 30 days, where you can restore it yourself (Dashboard → Trash). Participant responses and results linked to that content are kept with it during this period; without them the content would only be restored as an empty shell. The same applies to lists: a deleted list, or a member removed from a list, is kept in the trash together with the names, and learners’ progress linked to that list is not deleted during this period. After 30 days everything is deleted automatically and permanently. You can also delete an item from the trash permanently before that. When an account is deleted, the trash is deleted immediately along with the rest of the data.
- Files removed by the administrator: if the administrator removes a file that violates the terms, it is kept in a separate closed folder for up to 90 days so that it can be restored if the decision was wrong; after that the file is deleted automatically and permanently. The record of the removal (which file, the reason, the time) is kept until the account is deleted. When an account is deleted, both the files and the records are deleted immediately.
- List data and member names: retained until the user deletes them or closes the account. In the results of some applications (for example Kuulamistest), participants' names are kept as a copy until the creator deletes the result or the session — deleting the list does not remove these copies.
- Learner progress in practice applications (Computer Skills): deleted automatically 300 days after the learner's last activity, immediately when the list is unlinked from the course, and together with the course (after 30 days in the trash). The progress of a learner who joined with their own account is also deleted 300 days after their last activity, immediately when they leave or are removed from the course, together with the course, and when the account is deleted.
- Learner progress linked to a list in Touch typing and Flashcards: deleted automatically 300 days after the learner's last activity, immediately when the list is unlinked from the course or set, and once the course, set, list or learner has been permanently deleted (after 30 days in the trash).
- Participants' work in exercises and rounds (Video quiz, Fill in the blanks, Timeline, Preference groups, Friend Words, Friend Drawings, Friend Colors): a participant's answers, results, writings and drawings are deleted automatically 300 days after their last activity in that piece of work; in Preference groups, 300 days after the allocation was last changed. The creator can delete them earlier. The exercise or round itself remains until its creator deletes it.
- Team contribution ratings (Team Input) (the names of raters and rated members, points and comments): deleted automatically 300 days after the team's last rating, all of that team's ratings at once. The creator can delete them earlier; the assessment itself, together with the team members' names, remains until its creator deletes it.
- Quick Quiz game history (players' names, points and answers): deleted automatically 300 days after the game. The creator can delete it earlier; the quiz itself remains.
- Group dynamics mapping responses (Sociometry): a round's responses, together with participants' names and personal codes, are deleted automatically 300 days after the round is closed (then kept for another 30 days in the trash), or sooner if the creator deletes the round.
- Portfolio entries and files: a portfolio is valid for 12 months from creation (the owner can extend it). When a portfolio is closed or expires, its entries together with photos, audio recordings and feedback are kept for another 30 days — the owner receives a reminder about a week before deletion — and are then deleted automatically; the portfolio itself and its topics remain. Entries of a member removed from the list are kept until the owner deletes them or the portfolio's lifetime ends. Entries are also deleted together with the portfolio (after 30 days in the trash) and when the account is deleted.
- Newsletter sending data: for each newsletter sent, the recipient's email address is kept so that the unsubscribe link at the bottom of the email works. The recipient's name is deleted after the email is sent, and sending records are deleted after 365 days. The address of someone who has unsubscribed is kept as proof of the opt-out, so that we do not email them again.
- Poll, game, and session data: deleted according to application-specific logic — mostly per-session (e.g., Foor, Klassitahvel widgets, Lumememm), some until the user deletes them. Presentation responses (anonymous, no names) are kept for 12 months after the session ends, or until the owner deletes them sooner; the results view shows the exact deletion date for each session. Top Answers survey responses (anonymous, no names) are kept for 12 months after the last response, or until the owner deletes them sooner; after that the free-text responses are deleted and only the game board rows remain (answer label and points).
- Images in the Images and Puzzle tools: kept until you delete them yourself or the account is closed (see account retention above); there is no automatic expiry.
- Audio Recorder recordings: a recording stays on your device (in the browser) and only reaches our server if you share it with a link — for that you need to be logged in. We store a link between the shared clip and your account so you can manage the share from your dashboard (stop it); the clip is kept until you stop sharing it or the account is closed, and the link is deleted together with the clip. Without an account you can only download the recording.
- Text Sharing texts: a text created without logging in is kept for 30 days after it was last opened and then deleted automatically. A text created while logged in is kept until you delete it yourself or the account is closed; there is no automatic expiry.
- Crosswords created without logging in: deleted automatically if the crossword has not been opened for 12 months — every time the solving link is opened, the period starts again. A crossword created while logged in is kept until you delete it yourself or the account is closed.
- Word searches created without logging in: deleted automatically if the word search has not been opened for 12 months — every time the solving link is opened, the period starts again. A word search created while logged in is kept until you delete it yourself or the account is closed.
- Session data: 30 days after last activity.
- Password reset link: expires within 1 hour. Email verification and email change link: expires within 24 hours (the link in the reminder email for an unverified account within 7 days).
- Login attempt logs: up to 90 days.
- Join code entry log: up to 30 days. A temporary block record (IP address and reason) is deleted 30 days after the block ends; a permanent block set by the administrator applies until the administrator removes it.
- Security audit trail and web server request log copy: up to 180 days. This is longer than for login logs because a data breach is often discovered only weeks or months later, and these logs are then the only way to identify the people affected.
- Collection sessions: until user deletes or they expire.
- Application usage statistics and page views: individual records for up to 400 days, then daily aggregate figures only, with no link to a person.
- Search queries: up to 400 days.
- Game run results (without name or account link, see §3.5): up to 400 days.
- Feedback messages and correspondence: up to 24 months after the matter is resolved.
- License quote requests: up to 24 months.
- License data (institution, period, storage limit, price, invoice number, contact person): while the license is valid and for up to 7 years after it ends, so that we can evidence the contract and billing. When an account is deleted, we immediately remove the account link and contact details from a personal license.
- Email addresses on a school license list: up to 12 months after the license ends.
- License email confirmation: until the account is deleted; an unconfirmed confirmation link is deleted after 7 days.
- Short links (lingi.ee): until the user deletes them; an expired link remains renewable for 30 days (redirection is disabled during that time) and is archived afterwards.
- Not-found (404) request log: up to 400 days, requests identified as bots 30 days — we store only the requested address and the day, without the IP address.
- Security policy (CSP) reports: in aggregate form only (which rule was violated on which page), without IP address or account link.
Backups: there are two layers of backups. (1) The hosting provider's (Opalstack) own backups, made as part of the hosting service (see Opalstack documentation). (2) Our own encrypted backups: databases and site files daily. We keep the copies of the last 7 days, 4 weeks and 6 months (one per day, week or month). These are encrypted with AES-256 on the server and then uploaded to Hetzner object storage in Finland (see §7.3) — the key never reaches Hetzner. Videos (see §7.13) are kept in two locations, not in these backups. When an account is deleted, we remove the data from the production system immediately; it disappears from our backups through rotation within up to 7 months (6 months of retention plus up to 30 days of deletion protection) and from the host's backups according to their own schedule. We use backups only to restore data after a failure or error.
You may request deletion of your account and data at any time.
11. Privacy of Minors
An account can only be created by users who are at least 18 years old (of legal age), and by accepting the terms of service the user confirms their age. We do not verify age with a document, and we have seen that students sometimes create accounts too (for example in class). If we learn that an account was created by a minor, we send a notice to the account's email address and delete the account together with its content after 30 days; if the account holder is in fact an adult, they can reply to us within that time. Unused accounts are also deleted automatically (see §10).
No account is needed to take part in games and polls — minors take part without an account, via a shared link or code. When you use Diclasso together with minors (e.g., in class with students, in training, at a children's event, or in club activities) such that they take part in games or polls:
- participation is anonymous or under a nickname chosen by the participant;
- the data collected is minimal (session-based responses, optional nickname);
- data is typically deleted after the session ends, depending on the tool.
List-linked tools are different: the participant is linked to a member of the user's list and the data is kept longer (see §10). This applies in particular to Portfolio, where a child collects photos of their work, audio recordings and self-assessments over the year. These are visible only to the child (with their personal card) and to the portfolio owner; peers see a child's entries only if the owner turns on the exhibition view — and even then without the self-assessment and the owner's feedback. The child can download their own portfolio. The user is responsible for informing parents (section 3.3 of the Terms of Service); we recommend photographing the work, not people.
When a child uses an app on their own (for example, Sõnasõber, Sõnavara or the game "Inimene linnas" on a tablet in a kindergarten), the child does not create an account and nothing is sent to our server. The child's profile (the name entered and the picture chosen), players' names, progress and game state are stored only in the browser of that device (see §3.6). They disappear when you delete the profile in the app or clear the browser data. The only things that reach our server are pseudonymous page-view statistics and, in some games, the result of a game run without a name (how far the player got and how long they played, see §3.5), which cannot be used to identify the child.
If you record children's voices (e.g. with the voice recorder, voice assignment or portfolio tools) or upload pictures showing children, section 3.3 of the Terms of Service applies: the user is responsible for having permission to do so.
The user is responsible for ensuring that the use of the tools with minors complies with the applicable rules (e.g., the school's internal rules, instructions from the event organiser, notice to parents). If a user enters minors' real names into a list, we recommend first consulting with the responsible party and considering the use of nicknames or initials.
If your child's data has been entered into Diclasso and you wish to have it deleted, please contact us — we will delete the data without undue delay.
12. Cookies
Diclasso only uses cookies strictly necessary for the service to function — we do not use tracking or advertising cookies:
- Session cookie (PHPSESSID): to remember your login (30-day validity). The CSRF token for forms is kept inside the same session — we do not set a separate CSRF cookie
- Login redirect cookie (login_redirect): a temporary cookie remembering which page to return you to after sign-in; it expires after sign-in or within an hour at the latest
- Session device cookie (live_device): used in shared activities and games where participants do not create accounts. It lets the server recognise that the same browser is the same participant — so the same person's answers are not counted twice and unfinished work is not lost on refresh. It contains only a random code, no personal data; it lasts 32 days from last use and is protected from JavaScript (HttpOnly)
- Time zone cookie (dk_tz): stores your device's time zone name (e.g. "Europe/Tallinn") so that deadlines and expiry times are shown in your local time. It contains only the time zone name, not your location or any personal data; it lasts one year
- Quiz device cookie (viktoriin_device): links a quiz participant to the same browser so that answering in progress is not lost on refresh and the same participant is not counted twice. Only a random code; lasts one year, HttpOnly
- Listening test device cookie (kt_device): links a listening test participant to the same browser so that listening and answering in progress are not lost on refresh and rate limiting is per device rather than per shared school IP. Only a random code; lasts one year, HttpOnly
- Preference groups device cookie (el_device): links a preference groups participant to the same browser so that they can change their choices and later see their result, and rate limiting is per device rather than per shared school IP. Only a random code; lasts one year, HttpOnly
- Sociometry device cookie (sm_dev): links an unfinished sociometry response to the device where it was started — only that device can see the draft (another person opening the personal link, e.g. a mentor, cannot). Only a random code, the database stores just its hash; lasts 60 days, HttpOnly, only on /sotsiomeetria/ pages
- Typing Race device cookie (tv_dev): links a race participant (name and result) to the device without an account, so the page recovers when reopened and a participant removed by the organiser cannot rejoin. Only a random code, the database stores just its hash; lasts 30 days, HttpOnly, only on /trukivoistlus/ pages
- Curriculum self-assessment device cookie (ok_seade): set when the curriculum mapping self-assessment form is opened, so that the same self-assessment cannot be submitted several times from the same device. Only a random code; lasts 180 days, HttpOnly
- Hangman device cookie (lumememm_device): distinguishes participants in the same game without accounts. Only a random code; lasts one year, HttpOnly
- Sign-up session cookie (valik_session): holds a temporary reservation in a sign-up list so that the slot you picked is not lost while you register. Only a random code; lasts 30 minutes, HttpOnly
- Scheduling poll cookie (uhisaeg_voter_…): lets you change your availability answer later without creating an account. A separate cookie per poll containing only a random code; lasts 90 days, HttpOnly
- Wall author cookie (sein_authors): holds random codes for the wall posts you added yourself, so that you can edit or delete them later. It contains no post content or personal data; lasts 90 days, HttpOnly
- Wall device identifier (sein_fp): distinguishes participants on the same wall and limits post flooding. Only a random code; lasts 90 days
- Q&A wall device cookie (pollDeviceId): lets you manage the questions you submitted and counts your vote once. Only a random code; lasts one year
Local storage (localStorage) is used on your device to remember theme preferences (light/dark), application card order, and some applications' local settings and drafts — this data never leaves your device.
Because we only use strictly necessary cookies, we do not need prior consent for cookie use (EU ePrivacy Directive art. 5(3) exemption). You can manage cookies through your browser settings, but this may affect application functionality.
13. International Data Transfers
The primary Diclasso data (user account data, class lists, game and poll results) is hosted in Opalstack's Frankfurt (Germany) data centre, user videos in Hetzner's data centres in Germany and Finland (see §7.13) and encrypted backups in Hetzner's data centre in Finland (see §7.3) — data is stored in the European Union. Country detection also happens entirely on our server (see §7.7) — no IP address leaves the EU for that purpose.
Host access from the US: our hosting provider Opalstack LLC is a US company. Its staff can access the server in Frankfurt from the United States for administration and technical support, and Opalstack's own backups are kept by Wasabi Technologies LLC (also a US company) in its Frankfurt data centre. Legally, this is a transfer of personal data to a third country. It is based on the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914, Module Two), which are being concluded with Opalstack, and we have assessed the impact of US law on this transfer. A copy of the clauses is available on request (mikk@digiklass.ee).
Providers' sub-processors in the US: Opalstack's system logs, including email sending logs (email addresses and IP addresses), are collected for 7 days in the log management service Mezmo, Inc. (USA). This transfer also falls under the standard contractual clauses being concluded with Opalstack. The text-to-speech service Jutusta (see §7.12) uses the infrastructure of Cloudflare, Inc. (a US company), but requests are processed at server locations in the EU and data is stored under EU jurisdiction.
Otherwise, data travels outside the EU only when the user chooses a third-party service:
- Third-party services the user optionally chooses to use — Google OAuth, Google Drive, Microsoft Entra ID, OneDrive, YouTube, Ko-fi, Stripe. Map tiles (see §7.9) come from OpenStreetMap Foundation servers located in Europe and the United Kingdom (which has an EU adequacy decision), fronted by a global content delivery network. The address search service Nominatim (see §7.9) also runs on OpenStreetMap Foundation servers in Europe and the United Kingdom; our server sends it only the address being searched for.
Such transfers take place under the respective providers' standard contractual clauses and data protection frameworks. The user can decide whether to use these third parties — authentication is also available with email and password.
14. Changes
We may update this policy from time to time. We will notify you of changes by:
- Updating this page and the date
- Sending email for significant changes
15. Contact and Data Controller
For questions or requests, please contact us at the email address above.
16. Governing Law and Supervisory Authority
This Privacy Policy is governed by Estonian law and the EU General Data Protection Regulation (GDPR). The supervisory authority is the Estonian Data Protection Inspectorate (www.aki.ee/en), with which you have the right to lodge a complaint.