Klassian Privacy Policy
Klassian is operated by Elkanah (sole proprietor: Kyujin Cho). Elkanah is the data controller for the processing described below — except processing we carry out on behalf of an institution (§7A), for which the institution is the controller and we are its processor.
1. What we collect, why, and on what legal basis
1.1 Account and profile — when you sign in
| Data | Purpose | Legal basis |
|---|---|---|
| Email, name (or nickname), social sign-in identifier | Identifying you, signing you in, keeping your account in step across your devices | Contract (Art. 6(1)(b)) |
| Profile picture URL (Kakao sign-in only, and only if you agree) | Not used — see below | Consent (Art. 6(1)(a)) |
| Display name | Showing who you are in groups you join | Contract |
| Instrument (only if you opt in) | Research and personalisation | Consent (Art. 6(1)(a)) |
| Device language and region code (e.g. en-GB) — read from your device settings; not location data | Providing the service in your language and region; understanding usage by country and language | Contract; legitimate interests (Art. 6(1)(f)) for the statistics |
Sign in with Apple, Sign in with Google and Kakao sign-in are currently available. Whichever you use, the data we process and our purposes are the same.
Kakao sign-in also sends us a profile picture URL — Kakao's sign-in specification does not let us leave that item out of the request. It is optional: you can decline it on Kakao's consent screen and still sign in, in which case nothing is sent. If it is sent, we store it with your account but never display it anywhere in the app and never use it for any other purpose, and it is deleted when you delete your account.
Your display name is visible to members of groups you belong to, and changing it updates all of them.
1.2 Group collaboration — when you create, join or write in a group
- Group name, membership (role, display name), shared events (title, time, notes, venue), polls and votes, and one-to-one lesson requests made in a group and their comments (once lesson groups are available, groups no longer take new lesson requests and lessons happen in lesson groups — §1.18).
- Group notices (title and body), and the read record created when a notice is opened (who, when).
- Score distribution information: work, composer and edition; IMSLP file number, file name and page count; part assignments.
- Shared annotations: the strokes drawn on the shared layer by someone with permission to share annotations (pen or highlighter type, colour, width and opacity; point positions and pen pressure). Changes are delivered almost in real time: while a score with shared annotations is open, the app keeps a connection to our servers, and the signals sent over it say only which page of which score file changed and its version number — never the annotations themselves or who wrote them (phones fetch changes when the score is opened).
- Your part (instrument and number) and permissions (notices, score distribution, annotation sharing) within the group.
- Operation records: who posted a notice, distributed a score or shared annotations, and when (for notices, including a copy of the title and body and the number of recipients), and the member who first recorded an edition's file list.
- Purpose: sharing and coordinating group schedules, delivering notices, distributing scores and assigning parts, delivering shared annotations. Operation records are used only to deal with misuse, to recover from mistakes and — in institution groups — to let administrators see who posted or distributed what. Legal basis: contract; legitimate interests (Art. 6(1)(f)) for operation records.
- Visibility: what you write is visible to members of that group (lesson requests and comments: only the two people involved). Shared annotations can be seen by the group's members; the app shows them to members assigned the same part. The group's member list (display name, role, permissions, part and join date and, in institution groups, the name within the institution) is also delivered to the apps of the group's members. This is the feature working as designed, not a disclosure to third parties. Operation records are not shown in the app's member screens (in institution groups, administrators can see them in the dashboard).
- Read counts: people who can post notices, and institution administrators, see only a number such as "20 of 32 read" — never who has read. In groups with fewer than five members, or where the institution has turned the display off, not even the number is shown.
Only people given the relevant permission in a group can post notices, distribute scores or share annotations. Distributed score files are downloaded by each member's device directly from IMSLP and never pass through our servers (§5). Score files uploaded by an institution itself are covered in §7A, and lesson scores uploaded in a lesson group in §1.18.
While an invite link is valid, anyone holding it can see one thing before signing in: the group's name (the same applies to lesson group invitations).
Copies on your devices. When you leave or delete a group, the app deletes from that device, straight away, the scores you received from that group together with the annotations and recordings you made on them and the shared annotations. On your other devices — and when you are removed from a group or the group is deleted — the app cleans up when it next checks with our servers. If the group no longer exists, everything is deleted at once. If you are no longer a member, group information such as other members' names, events and notices is deleted at once, and received scores (with your annotations and recordings on them, and shared annotations) are deleted after a set period: the restore period (§7A) where an institution removed you or its agreement ended, otherwise 30 days from when the app first noticed. If the app cannot check with our servers it deletes nothing, so copies may remain — hidden from view — on a device that is never reopened or has been signed out; they are cleaned up when you sign in again. Scores received in a group cannot be exported, so if you want to keep notes long-term, write them in your own copy of the score as well.
1.3 Notifications — the in-app inbox and device notifications (when signed in)
- In-app inbox: group and lesson group activity notifications (type, title, body, sender, read status) are kept on our servers and shown in the app's inbox whether or not you allow notifications. If you receive a service announcement from us, it is kept there too.
- Push token (a device identifier), platform, app version, language, and whether notifications are allowed — registered when you sign in, whether or not you allow notifications (it is also used for silent signals that keep widgets and schedules up to date). It is removed from our servers when you sign out.
- Purpose: delivering event, notice and collaboration notifications and service announcements. We send marketing messages only if you have opted in (§1.9). Legal basis: contract.
- Notification titles and bodies (for example event titles, notices and comments) are delivered through Apple's push service (APNs), which may keep them for up to 24 hours for delivery. If you turn notifications off in iOS Settings, they are still delivered to the device but not displayed. See §5.
- Copies of notifications waiting to be sent are kept in a queue on our servers and deleted 7 days after sending.
- When we send an announcement to one person, we record who received it and what it said.
1.4 Practice hand-off — while a practice session is running (when signed in)
While you practise, the session's state (score name, composer, elapsed time and the like) passes through our server and Apple's push service (APNs) so that your other devices (for example the iPhone Lock Screen) can display it. It is deleted from our server when the session ends. Practice controls pressed on another device (pause, resume, break, finish) are also relayed through our server and deleted once the receiving device has handled them. For this we keep that device's Live Activity token and a random device pseudonym. Legal basis: contract.
1.5 Gaze improvement data — only with your separate consent, pseudonymous
- A pseudonymous install identifier (random UUID). It is not linked to your account or email, and we do not attempt to link it.
- Derived metrics only: calibration error, head and eye angles, distance from the screen, calibration and practice-game samples expressed as screen coordinates, page-turn success/attempts, dwell times, device model, OS version, TrueDepth availability, app version, install channel (App Store, TestFlight and the like), screen orientation, and gaze-related events (a calibration suggestion; calibration started, and the stage at which practice was finished, skipped or stopped; whether the help we show when gaze isn't working well appeared and was tapped; why gaze could not be turned on, such as split screen, camera permission or an unsupported device; page turned; recalibrated; and similar).
- If you also opted into instrument sharing: your instrument family (e.g. strings).
- What is never collected or transmitted: camera footage, photos, face images, individual frames, or any record of where you look while reading a score. All gaze computation happens on the device.
- Purpose: improving the accuracy and reliability of Klassian's gaze page-turning (calibration, dwell detection and device-specific tuning). It is not used for any other purpose, is not used to identify anyone, and is not shared with third parties. Legal basis: consent, withdrawable at any time in Settings.
- Declining changes nothing — every feature, including gaze turning, works the same.
1.6 Usage analytics — only with your separate consent
When you open the app (including the install channel — App Store, TestFlight and the like); opening the app from a notification (the kind of notification); how you use the home screen (its style; which suggestion card was shown first — such as your practice record, a practice streak, getting ready for a performance, checking fees, or a sleep reminder — and swiping, expanding or reordering); which features you use (opening scores, importing scores — where from, and why an import failed —, starting to annotate, a summary of each reading session — how long it lasted, pages turned, whether gaze turning was used, and how often a gaze turn was undone by hand right away — starting and ending practice, starting and ending performance mode (stage or recital) — how long it lasted and whether gaze turning was used —, the metronome, creating and joining events, groups and lesson groups — including why joining failed —, widgets, opening the feedback screen, progress through the introductions and gaze calibration guidance, and the results of a gaze free trial (pages turned, the goal, and how often your gaze entered a page-turn area)); moving between screens; paywall interactions (paywall shown, with the benefit offered, such as a free trial; plan comparison opened; purchase button tapped; paywall closed and how long it was open, as a range; and why products failed to load or a purchase could not start); why a sync failed; and score-search terms and the works you browse (§1.11). Most counts and durations are recorded only as ranges (for example 5–9); the pages turned, the goal and how often your gaze entered a page-turn area in a gaze trial, and which step of an introduction you reached, are recorded as they are. Each record also carries the app version, device model and App Store country. Suggestion cards are chosen on your device from your calendar, fee and practice records; the contents of those records are not included. This is linked to your account, and deleted with it. It is stored and transmitted separately from gaze data (§1.5), and the two are never combined. Your scores, annotations and playing are never part of it. Purpose: understanding which features are used and where friction occurs, and producing usage statistics (§1.19). Legal basis: consent. Declining changes nothing.
1.7 Payments — processed by Apple
- Purchases, renewals, cancellations and refunds are processed entirely by Apple through the App Store. We never receive your payment details.
- When your subscription changes (purchase, renewal, expiry, cancellation, refund), Apple notifies our server. We keep the transaction information in that notification (product, transaction ID, purchase/expiry/refund times, price and currency, storefront country, auto-renewal status, any benefit applied — such as a free trial or a promotional code — and its type, and the like), linked to your account. These notifications contain no name, email address or payment details.
- If you buy without signing in, the purchase is recorded against a random number the app creates on your device, and linked to your account when you sign in later.
- After you sign in, the app sends our server the record of your current subscription that it finds on your device — signed by Apple and containing the transaction details described above (original transaction ID, product, period, any benefit applied and the like) — and, once we have checked Apple's signature, we link the subscription to your account. Subscriptions started outside the app (such as from the App Store's subscription settings or by redeeming a code), or while you were signed out, are linked this way too.
- Purpose: features where our server needs to know your plan (such as group size limits), handling payment and refund enquiries, and understanding subscriptions and how promotions (such as codes handed out by partner institutions) are used. Legal basis: contract; for keeping transaction records for the period Korean law requires (§3), our legitimate interest in complying with that law (Art. 6(1)(f)).
- If we grant you an access tier ourselves (beta testers, goodwill), or an institution gives you a seat (§7A), we store that on our servers. Records of tiers we grant or withdraw are kept in case of disputes (§3).
1.8 Consent records
What you consented to or withdrew, when, and in which app version — kept because the law requires us to be able to demonstrate consent (Art. 7(1)). Legal basis: legal obligation (Art. 6(1)(c)).
1.9 Marketing — only with your separate consent
Whether you opted into marketing messages. Declining has no effect on the service. Legal basis: consent.
1.10 Sign-up forms on our website — no longer collected
We no longer take launch-update sign-ups or beta tester applications on our website, and the data we received through them has been deleted.
1.11 Score download records — when you download from IMSLP (required)
- The file: IMSLP file number, file name, work title, composer, the copyright/licence notice shown on screen when you downloaded, page count, file size.
- What happened: opening score search, download started / completed / cancelled / failed and when, that you saw IMSLP's notice page, and whether the file landed in My Scores.
- App version and your account identifier.
- Purpose: to respond to legitimate requests from rights holders and IMSLP, to act on breaches of the Terms, and to evidence which notice a score was downloaded under.
- Legal basis: consent (Art. 6(1)(a)) — asked once, the first time you tap Download, not at first launch. Without it you can still search, browse and preview, but you cannot download through the app. If you never use the IMSLP feature, nothing here is collected. Records of downloads already made are kept for the period in §3 so that we can handle rights holders' claims (legitimate interests, Art. 6(1)(f)).
The same applies when you download an IMSLP score distributed in a group. Search terms and works you merely browse are not part of this — they fall under §1.6 usage analytics (optional). Downloading requires sign-in; searching, browsing and previews do not. The score file itself is fetched by your device directly from IMSLP and never passes through our servers (§5).
1.12 Feedback and problem reports — only when you send one
- The area you choose: gaze tracking, annotation, scores, calendar, groups, subscription, or other.
- What you write.
- The app's state at that moment: whether you have calibrated, whether the device supports face tracking, how many scores you have, free storage, whether you are signed in.
- Technical details: app version, iOS version, device model, plan.
- Your last 20 actions — each line is only a time and an action name from a fixed list of 21 (such as "opened a score", "turned a page", "started gaze", "opened subscription info"); no other text is generated.
- Purpose: reproducing and fixing the problem you reported. Legal basis: legitimate interests (Art. 6(1)(f)).
The action list records what you did, never what you wrote: score titles, annotations, text notes, event titles, group names and search terms are never included — only that you "opened a score", not which one. Recent actions stay on the device until you send feedback. Before sending, you can see exactly what will be sent, and you can leave out the recent actions. You can also send just the area without writing anything. Sending feedback requires sign-in, and it is linked to your account.
1.13 Reports and blocking — only when you use them
- Reports: who reported, what was reported (an event, notice, poll, comment, lesson score and the like) and its author (for a lesson score, the person who uploaded it), the reason chosen, the first part of the text at the moment of reporting (up to 300 characters — for a lesson score, its composer, title, edition and file name), and the group or lesson group.
- Action taken on a report: the account number of the author whose content was acted on, and the action (including stopping and restoring the transmission of a lesson score, and warnings or suspensions of lesson score uploads).
- Requests from rights holders (received by email and the like): the name and contact details of the person making the request (a rights holder or their representative), what they claim, the lesson scores concerned, the status of the request, the scheduled restoration date, and when we were told of any legal proceedings.
- Blocking: the person you blocked, and their display name at the time.
- Purpose: dealing with objectionable content and abuse, and handling infringement notices and rights holders' requests (Terms §10, §12); hiding comments, poll responses and lesson requests from people you have blocked and, in lesson groups, not delivering what they send you. Legal basis: legitimate interests (Art. 6(1)(f)).
The first part of a reported post is kept with the report so that it can be handled even if the author deletes the post. We never tell anyone who reported them or who blocked them (in a lesson group, someone you have blocked only sees that what they try to send cannot be sent). When a lesson score is reported or a rights holder makes a request, our staff may open that lesson score file to handle it, and we log who opened which file, when, and under which report or request. We keep the requester's contact details so that we can reply and follow the restoration procedure.
1.14 Organisation enquiries — only when you send one
- What you send through "Enquire for your organisation" in the app or the enquiry form on our website: type, name and size of the organisation, your role (optional), the email address for our reply, preferred contract period and start (optional), and your message (optional). The website form also asks for your name.
- Sent with an in-app enquiry: app version, device region setting and your plan at the time — linked to your account.
- Purpose: discussing adoption and replying. Replies are written and sent by a person; no automatic emails are sent. Legal basis: steps taken at your request before entering into a contract (Art. 6(1)(b)); for the website form, your consent, given when you submit it (Art. 6(1)(a)).
- Website enquiries are stored on our servers (Supabase) and handled in the same place as in-app enquiries.
Contract renewal enquiries sent from the institution dashboard are covered in §7A.
1.15 Diagnostics — only if you have consented to usage analytics (§1.6); not linked to your account
- Daily diagnostic and performance reports provided by iOS: crash, hang, excessive-processing and disk-write reports, and a day's performance metrics — app version, iOS version, device model, and technical information pointing to where the problem occurred.
- When sign-in fails: which sign-in method and which error code.
- These contain no account number, so they are not linked to you, and no email, text or score content.
- Purpose: finding and fixing bugs. Legal basis: consent (Art. 6(1)(a)).
1.16 Server logs — automatic
- When the app, our website or the institution dashboard communicates with our servers (including the connection used to deliver annotations in real time), the systems of our server operator (Supabase) and its network provider (Cloudflare) record the IP address, time and type of request. Visits to our website and the institution dashboard also pass through Cloudflare.
- When you sign in, the authentication server records the sign-in (time, IP address, device information).
- Purpose: keeping the service running and secure (blocking attacks, detecting account takeover). Not used for anything else. Legal basis: legitimate interests (Art. 6(1)(f)).
- How long these are kept: §3.
1.17 Emails to support — only when you write to us
- Your email address, your name (if you give it), the content and attachments of your email, and our replies.
- Purpose: answering you, handling requests to exercise your rights (access, deletion and the like), and handling infringement notices (Terms §10). Legal basis: legitimate interests (Art. 6(1)(f)); legal obligation (Art. 6(1)(c)) for requests to exercise your rights.
- Emails are received and stored in Google Workspace (§4).
1.18 Lesson groups — when you create or join a lesson group
- Lesson group name; members (whether owner, lesson admin or student; display name; join date); who was made a lesson admin or stopped being one; removal requests (a lesson admin asking the owner to remove someone).
- Lesson requests, their comments and alternative times proposed; lesson schedules (title, start and end, notes, venue); lesson group notices.
- Lesson scores: the score file you upload (a PDF, which may itself carry names and the like); if you pick it from My Scores, the annotations you had made on it by then; score information (composer, title, edition, file name, page count, size); who uploaded it and for whom; when; your confirmation of rights (when you confirmed, and which version of the wording you saw); withdrawals and restorations, and the signal telling devices when to delete it (the withdrawal signal).
- Annotations on lesson scores: what a lesson admin writes on a lesson score's shared layer (the same stroke data as shared annotations in §1.2, delivered almost in real time in the same way).
- Lesson score upload records: who uploaded which file to whom in which lesson group, its size, the version of the rights wording, and when it was withdrawn, taken down or deleted.
- Purpose: arranging lessons; delivering lesson scores and their annotations and letting you open them offline; handling reports and rights holders' requests (§1.13); managing storage; keeping materials for 30 days after someone stops being a lesson admin or a lesson group closes, so that we can answer legitimate requests. Legal basis: contract (Art. 6(1)(b)) — the lesson group features you use; legitimate interests (Art. 6(1)(f)) for upload records and for keeping materials after a lesson ends.
- Who sees what: lesson schedules, requests and comments, lesson scores and their annotations are visible to the two people in that lesson (the lesson admin and the student) and to the lesson group's owner (and to a new owner if ownership passes). Lesson admins see the list of students; students see the lesson admins and their own lessons, but not other students. Notices are visible to all members. This is the same where the student is under 18. Before you join, the app tells you that the owner can see every lesson. This is the feature working as designed, not a disclosure to third parties. If you leave a lesson group and are invited back, the schedules, requests and comments that remain from your lessons become visible again. When handling a report or a rights holder's request, our staff may see the lesson score concerned (§1.13).
- Lesson scores are kept in private storage on our servers and delivered only through short-lived links, after our server has checked that the person may receive them. They are never exposed through search, recommendations or public lists.
- Copies on your devices. A lesson score you receive is stored only in that device's lesson area (excluded from iCloud sync and device backups) and cannot be moved into My Scores or exported. If the uploader withdraws it, the other participant leaves the lesson group or deletes their account (only the lesson scores that participant uploaded), or the lesson's lesson admin stops being one (only the lesson scores that lesson admin uploaded), it disappears from view at once; unless it is restored within 30 days (for a lesson admin, unless they are made one again within that time), the app deletes it from the device, together with the annotations and recordings on it, when it next checks with our servers (where the other participant left or a lesson admin stopped being one, the recordings the remaining person made on it are not deleted). A lesson score taken down after a report or a rights holder's request is deleted if it is not restored by the deadline of the restoration procedure. If the app cannot check with our servers, it deletes nothing. When someone stops being a lesson admin, or the other participant leaves the lesson group, the person who remains (the student, when a lesson admin is removed) keeps their past lesson schedules, requests and comments, the lesson scores they uploaded with the annotations on them (including the other participant's), and the recordings they made on that lesson's scores; lessons with that person already scheduled for the future are cancelled, and the person who remains is notified. If the other participant deletes their account, the lesson requests, comments and annotations they wrote are deleted under §8.
- Keeping materials, and providing them on request. When someone stops being a lesson admin, they can no longer see the lesson materials of the lessons they gave, and we keep a copy of those lessons' schedules, requests and comments and of the lesson scores they uploaded with the annotations on them in separate, encrypted storage that no user can reach, for 30 days, and then delete it. When a lesson group is deleted or closed, we keep all its lesson materials in the same way for 30 days and then delete them. During that time, if the person who stopped being a lesson admin, or the lesson group's owner (for a closed or deleted lesson group, its owner at that time), asks for them and gives a legitimate reason, we may check the reason and provide them, limited to what the person asking could originally see, and we record that we did so in our admin records (§3). You can ask to access what is kept about you under §8. Files uploaded by a member who deletes their account, and that member's own materials, are deleted rather than kept.
- Lesson time and screen-recording detection. The time elapsed and remaining in a lesson, shown on the score screen, is worked out on the device, and detection of screen recording or screenshots while a lesson score is open also happens only on the device. Neither is sent to or recorded on our servers.
- Lesson groups run by an institution under an institution agreement (institution lesson groups) are covered in §7A: there is no owner who can see every lesson, and the institution's master account sees only what §7A sets out.
1.19 Usage statistics — totals only
- We use the data above to produce statistics about how the service is used (for example, the numbers of members who sign up, are active or delete their accounts, how often features are used, the numbers of groups, lesson groups and lessons, and the numbers of subscriptions and promotions used). App-usage records are used only for people who have agreed to usage analytics (§1.6), apart from first-use steps before sign-in (§1.20), which identify no one; data that arises in providing the service, such as accounts, groups, lesson groups and payments, is counted in numbers that do not identify anyone.
- Purpose: running and improving the service, and describing it to others — such as partner institutions, investors or competition judges. When we share statistics outside the company, we share only totals from which no individual can be identified, never personal data (§6); where a number is so small that someone could be identified, we leave it out or combine it with others. Legal basis: legitimate interests (Art. 6(1)(f)); for app-usage records, consent (§1.6).
- The data used follows the retention period of each item above; the totals themselves contain no personal data.
1.20 First-use steps — before you sign in; no account or device identifier
- Until you sign in, the app sends only whether you reached each first-use step: how far you got through the introduction, whether you opened and turned a score for the first time, and, when the sign-in screen appeared, whether you signed in or closed it. The app version, iOS version, device model and the date it was sent go with it.
- It contains no account number, device identifier or advertising identifier, and each step is sent only once from a device (the app notes on the device which steps it has already sent — §10A). So it identifies no one, and it is not linked to your account even after you sign in.
- If you have previously declined usage analytics (§1.6) on this device, nothing is sent.
- Purpose: finding where new users stop, to improve the introduction and sign-in, and producing usage statistics (§1.19). Legal basis: this data identifies no one; to the extent it is personal data, our legitimate interests (Art. 6(1)(f)).
2. What stays on your device and in your own iCloud
The following never reaches our servers. It lives on your iPad and, if iCloud sync is on, in your own iCloud (your Apple account's private storage):
your score PDFs and covers · annotations, stamps and text notes · your personal calendar, including fees and settlement records · practice history · your gaze calibration state · library folders · group cover photos · app preferences (including sleep-alarm settings).
There are three exceptions. If you share annotations in a group, the strokes on the shared layer are stored on our servers and delivered to the group's members (§1.2); annotations anywhere else are not shared. If an institution uploads score files to distribute, those files are stored on our servers (§7A). And if you upload a lesson score in a lesson group, that score file (with the annotations you had made on it, if you picked it from My Scores) is stored on our servers and delivered to the other participant and the lesson group's owner, and what a lesson admin writes on a lesson score is stored on our servers too (§1.18).
iCloud sync is on by default. Data in transit passes through Apple's servers but is stored in your private iCloud space, which we cannot access. You can turn sync off at any time in Settings → iCloud Sync, or exclude just your large scores. Apple's privacy policy governs that storage.
Recordings of your playing never leave the device at all — they are excluded even from iCloud sync.
3. How long we keep things
| Data | Retention |
|---|---|
| Account, profile, notifications (including the in-app inbox), consent records | Deleted immediately when you delete your account (except where the law requires retention) |
| Group activity — events, polls, lesson requests, comments, notices, notice reads, score distribution information | Until the author or a permitted person deletes it, or the group is deleted. What happens when you delete your account: §8 |
| Shared annotations | While a distribution is live, only the latest version of each page is kept. Hidden when the distribution is withdrawn; deleted when the distribution or the group is deleted |
| Lesson groups — members, lesson schedules, requests and comments, notices, lesson admin appointments, removal requests | Until the author or a permitted person deletes it, or the lesson group is deleted (what a student keeps when someone stops being a lesson admin stays as it is). For the copy kept when someone stops being a lesson admin, and for materials of a closed or deleted lesson group: see "Kept lesson materials" below. What happens when you delete your account: §8 |
| Lesson score files (on our servers) | Deleted 30 days after being withdrawn, or — for the files a participant uploaded — 30 days after that participant leaves the lesson group; after the 30-day keeping period for the files a lesson admin uploaded when they stop being one, and for all files when the lesson group is closed or deleted; after the deadline of the restoration procedure when taken down after a report or a rights holder's request; at the next clean-up if the uploader deletes their account. Files not used in any lesson (for example, abandoned uploads) are deleted after 7 days |
| Annotations on lesson scores (including those uploaded with the score) | While the lesson score is live, only the latest version of each page is kept. Hidden when the lesson score is withdrawn or the lesson ends; deleted together with the lesson score file (row above) |
| Kept lesson materials (someone stops being a lesson admin; lesson group closed or deleted) | Deleted 30 days after we start keeping them. If the uploader deletes their account, their part is deleted at once |
| Lesson score upload records and rights confirmations | While the file is on our servers and for 1 year after it is deleted (5 years if its transmission was ever stopped). After account deletion they remain with only your account number (a random string) attached |
| Withdrawal signals (telling devices which lesson score to delete, and when) | While the lesson group exists; switched off if the lesson score is restored |
| Group and lesson group operation records (who posted notices, distributed scores or shared annotations, and when — lesson score upload records are in the row above) | 1 year from recording (the copy of a notice's body: 90 days). When you delete your account, your field in these records is cleared |
| Live practice session state | Deleted when the session ends |
| Practice controls sent from another device | Deleted when the receiving device handles them (any not handled are deleted when you delete your account) |
| Practice hand-off tokens and device pseudonyms | Deleted when you delete your account |
| Push tokens | Deleted on sign-out or when the token expires |
| Copies in the notification queue | Deleted 7 days after sending |
| Usage analytics | Deleted immediately when you delete your account — it is linked to the account |
| Payment notification records (§1.7) | 5 years from receipt (Korean e-commerce record-keeping). After account deletion no email or other account details remain — only the account number (a random string) and transaction IDs |
| Admin records — access tiers granted or withdrawn, announcements sent to one person (recipient and title), handling of reports and enquiries, staff viewing of member information, staff opening reported lesson score files, stopping and restoring lesson scores, warnings and suspensions of lesson score uploads, providing kept lesson materials | 5 years (in case of disputes). After account deletion only the account number remains. The recipient field of the announcement itself is cleared when you delete your account |
| Feedback and problem reports | 1 year from sending — to check whether the same problem recurs. Deleted immediately if you delete your account before then |
| Reports | 1 year from reporting. Deleted immediately if the member who reported deletes their account; if the author deletes theirs, only the author field is cleared. Records of action taken: 5 years |
| Rights holders' requests (§1.13) | 5 years from receipt (in case of disputes) |
| Block list | Deleted when you unblock or delete your account |
| Organisation enquiries | 1 year from receipt — moved to contract records if they lead to a contract. In-app enquiries are deleted immediately when you delete your account |
| Emails to support | 3 years after the matter is closed (the same period Korean e-commerce law sets for records of consumer complaints and disputes) |
| Diagnostics | 1 year from receipt |
| First-use steps before sign-in | 1 year from receipt |
| Server logs | Our server operator's (Supabase) logs: up to 7 days, depending on its settings · sign-in records: 3 months · our network provider's (Cloudflare) logs: for the period set by Cloudflare's policy |
| Gaze improvement data (pseudonymous) | For the life of the service. It is pseudonymised — we cannot single out whose it is — and the accumulated pool is what the accuracy of gaze tracking is built on. Because it is not linked to your account, it is unaffected by account deletion |
| Data on your device and in your iCloud (§2) | Until you delete it — we have no access |
| Score download records (§1.11) | 3 years from the download. When you delete your account, your email and anything else that identifies you is erased immediately; the record remains with only your account number (a random string) attached |
| Consent to score download records | Deleted immediately when you delete your account |
| Data entrusted to us by an institution | §7A(4) |
Retention required by law. After its purpose is served, the following is kept separately from other data, for the period and on the basis shown:
- Payment notification records (account number, transaction ID, product, price and currency, transaction time and the like) — Enforcement Decree of the Korean Act on Consumer Protection in Electronic Commerce, Art. 6: 5 years.
- Institution dashboard access logs (account, time, action, IP address, browser information) — Korean Standards for Personal Information Security Measures, Art. 8: 1 year (2 years where those Standards require it).
- Institution contract ledger (institution name and type, contract number, seats, period) — Korean Framework Act on National Taxes, Art. 85-3: 5 years from the statutory filing deadline for the tax period of the transaction.
- Among emails to support, records of consumer complaints and disputes (address, name, content) — Enforcement Decree of the Korean Act on Consumer Protection in Electronic Commerce, Art. 6: 3 years.
Deletion. When a retention period ends or the purpose is served, we delete the data without delay, in a way that cannot be recovered. When you delete your account, the server data linked to your account is deleted immediately through database constraints (cascading deletion), apart from the records this section says are kept; files in our server storage (score files uploaded by institutions, lesson score files) are deleted by a clean-up job at the times set out above (lesson score files you uploaded: at the next clean-up after you delete your account). Institution data follows the schedule in §7A(4), with a check before destruction that the right data is being deleted. Server backups are kept for at most 7 days, so deleted data disappears from backups within 7 days of deletion.
4. Processors and sub-processors
| Company | Role | Notes |
|---|---|---|
| Supabase Pte. Ltd. (Singapore) | Database, authentication, file storage, server functions, real-time delivery, hosting | Servers are in Seoul, Republic of Korea. Technical support may be provided from abroad by its sub-processor Supabase, Inc. (United States) and others (§5). Supabase's data processing agreement applies as part of its Terms of Service |
| Supabase, Inc. | Technical support (Supabase sub-processor) | United States — see §5 |
| Amazon Web Services, Inc. | Hosting of Supabase's servers (Supabase sub-processor) | Seoul region, Republic of Korea |
| Cloudflare, Inc. | Delivery and security for our website (klassian.com) and the institution dashboard (org.klassian.com) (engaged by us); delivery and security of traffic between the app or web and our servers, and file delivery (Supabase sub-processor) | See §5 |
| Other Supabase sub-processors | As listed by Supabase at supabase.com/legal/subprocessors | See §5 |
| Apple Inc. | Push delivery (APNs), payments (App Store), sign-in | See §5 |
| Google LLC | Sign-in | Only if you sign in with Google |
| Google Asia Pacific Pte. Ltd. (Google Workspace) | Receiving and storing email sent to support@klassian.com | See §5 |
| Kakao Corp. | Sign-in | Only if you sign in with Kakao. Processed in the Republic of Korea — no international transfer |
A sub-processor is a company to which a processor has delegated part of its work (Korean Personal Information Protection Act, Art. 26). For processing we carry out under an institution agreement (§7A), we are the institution's processor, and the companies above are sub-processors engaged with the institution's consent under that agreement.
5. International transfers
Our main servers are in the Republic of Korea. The European Commission has decided that Korea provides an adequate level of data protection (Decision of 17 December 2021, reconfirmed July 2026), and the United Kingdom has made the equivalent determination (Data Protection (Adequacy) (Republic of Korea) Regulations 2022). Your data may therefore be transferred from the EU or UK to Korea without any additional safeguard.
Some data is transferred onward from Korea to the companies below. Under Korean law, the basis is Article 28-8(1)(iii) of the Personal Information Protection Act (entrustment or storage needed to provide the service, disclosed in this policy). Each company handles the data under its own data protection terms with us, and some of those terms add transfer safeguards for data of people in the EU or UK — Supabase's data processing agreement, for example, incorporates the EU Standard Contractual Clauses and the UK Addendum. To find out which safeguard applies to a particular transfer, or to request a copy, write to support@klassian.com.
① Notification delivery — Apple Inc.
- Recipient and contact: Apple Inc. (apple.com/legal/privacy · contact via apple.com/legal/privacy/contact)
- Country: United States
- Data: notification titles and bodies (event titles, notices, comments, the composer and title of lesson scores, and other text written by you or by members of your groups and lesson groups), device token, unread count; and, when you use practice hand-off, the practice state (score name, composer, elapsed time and the like) and that device's Live Activity token
- When and how: over the network, each time a notification or practice update is sent
- Purpose and retention: delivery. Notifications are kept for up to 24 hours for delivery; practice updates for the period Apple sets
- How to refuse, and what happens: turning notifications off in iOS Settings stops them being displayed, not delivered. Signing out removes that device's push token from our servers and stops notifications to it; you will then not receive notifications or widget updates. Practice updates are sent only while you are recording a practice session.
② Server operation — Supabase Pte. Ltd. and its sub-processors
- Recipient and contact: Supabase Pte. Ltd. and its sub-processors (Supabase, Inc. and others — §4) · privacy@supabase.com
- Countries: Singapore, the United States and other countries where Supabase or its sub-processors have staff or facilities (the locations given in Supabase's sub-processor list). Data stored on our servers stays in Seoul
- Data: server information needed for incident response and technical support; server logs (IP address, time and the like); requests handled by server functions
- When and how: remote access during incident response and technical support; transmission over the network when you use the service (a request may be handled in a region close to where it is made)
- Purpose and retention: operating and supporting the service; logs are kept for the periods in §3
- How to refuse, and what happens: this is how the servers work, so it cannot be refused on its own. You can stop processing through our servers by deleting your account and withdrawing optional consents; features that need sign-in will then be unavailable.
③ Delivery and security — Cloudflare, Inc.
- Recipient and contact: Cloudflare, Inc. (PrivacyQuestions@cloudflare.com) — engaged by us for the website and the institution dashboard, and by Supabase for traffic between the app or web and our servers and for file delivery
- Countries: the United States, and Cloudflare servers in countries near where you connect
- Data: the traffic exchanged (IP address, browser and device information, request address and content); and, when you upload or receive score files uploaded by an institution (§7A) or lesson scores (§1.18), a delivery copy of those files
- When and how: over the network, with each connection
- Purpose and retention: delivery and attack prevention. Content passes through only in transit; access logs and delivery copies may be kept for the periods set by Cloudflare's policy
- How to refuse, and what happens: this cannot be refused on its own. You can stop processing through our servers by deleting your account and withdrawing optional consents, and avoid the other transfers by not visiting the website or the institution dashboard; features that need sign-in, the website and the dashboard will then be unavailable. Features that work only on your device (reading and annotating scores) are unaffected.
④ Emails to support — Google Asia Pacific Pte. Ltd. (Google Workspace)
- Recipient and contact: Google Asia Pacific Pte. Ltd. and its sub-processors (Google LLC and others) · support.google.com/a/contact/googlecloud_dpr
- Countries: Singapore, the United States and other countries where Google has data centres
- Data: emails you send to support@klassian.com (address, name, content, attachments) and our replies
- When and how: over the network, when emails are exchanged
- Purpose and retention: receiving and storing email; 3 years after the matter is closed (§3)
- How to refuse, and what happens: the transfer does not happen if you do not email us. You can also reach us through feedback in the app (§1.12) or by post.
IMSLP. When you use score search (§1.11) or group score distribution, your device connects directly to IMSLP (Petrucci Music Library, Canada · imslp.org — some files come from its European site, imslp.eu). This is not a transfer by us — it is traffic between your device and IMSLP — but you should know about it.
- What IMSLP receives: your device's IP address and the default information your device adds to requests (the app's internal name and build number, the versions of iOS and its networking components, language settings and the like). The screen that downloads score files connects to IMSLP the way an ordinary web browser (desktop Safari) does. We do not add our name or contact details.
- What stays on your device: cookies IMSLP sets in the app's IMSLP screens (such as accepting its notice, or signing in to an IMSLP account); the count of downloads used to decide when to show the donation prompt; and whether you tapped Donate — all stored only on your device.
- The score file is downloaded by your device directly from IMSLP. It never passes through our servers, and we do not store or redistribute IMSLP score files. If you upload a score you downloaded from IMSLP as a lesson score, however, that file is stored on our servers (§1.18).
- The file list of an edition distributed in a group (file numbers, names, page counts) is read from IMSLP by the device of the first member who opens that score, and written to our server. Our server never connects to IMSLP.
- If you tap Donate in the donation prompt, IMSLP's donation page (imslp.org) opens. Donating is between you and IMSLP; we do not know whether you donate.
- IMSLP's handling of your data is governed by IMSLP's own policy (imslp.org).
Social sign-in and App Store payments may likewise involve those providers' servers abroad, under their own privacy policies. iCloud sync (§2) is a service between you and Apple.
6. Sharing
We do not sell personal data, share it for advertising, or disclose it to third parties, except where the law requires or you separately consent. There is no third-party analytics or advertising SDK in the app. (What you write in a group being visible to its members is the feature working as designed — §1.2. What institution administrators see is either a feature you chose by joining an institution group or processing the institution has entrusted to us — §7A. In a lesson group, lesson materials being visible to the lesson's two participants and the owner, and kept materials being provided on request to a person who stopped being a lesson admin or to the lesson group's owner, are likewise part of the feature you chose by joining — §1.18. When we tell others — such as partner institutions, investors or competition judges — how the service is used, we share only totals from which no individual can be identified, never personal data (§1.19).)
There is one exception:
- Recipient: a rights holder or their representative, or IMSLP (Petrucci Music Library).
- What: the relevant entries from your score download records (§1.11) and your email address.
- When: on a request required by law, or a legitimate request from a rights holder, once we have verified that it is legitimate.
- What we cannot share: the identity behind a deleted account — it no longer exists (§3).
7. Gaze and camera — specific commitments
- The camera is used on the device only, to compute where you are looking. No footage, photo or face image is ever stored or transmitted anywhere.
- We do not record where you look while reading. The only coordinates that leave the device are discrete calibration and practice-game samples — moments when the app asked you to look at a specific target — and only with your consent (§1.5).
- Gaze data is keyed to a pseudonymous identifier, stored in a separate server environment from account data, and it is our policy never to combine the two.
- For that reason, we cannot locate and delete any one person's gaze data — we cannot tell whose it is (see §8, Art. 11). What you can always do: withdraw consent in Settings, which stops collection instantly and discards anything still queued on the device.
7A. Institutions (schools and ensembles)
When a school, orchestra, academy or other institution enters into an institution agreement with us, it gives its members an access tier (a "seat") and institution groups, and administrators it appoints run those groups from a web dashboard (org.klassian.com). In this section, "members" means members of an institution group, and the "restore period" is the period (30 days by default) during which data is kept so that an accidental removal or an ended agreement can be reversed.
(1) Who decides, and who processes
- Data the institution enters or entrusts to us to run its institution groups, including institution lesson groups (rosters, classes, parts, notices, score distribution, lessons and the like): the institution decides the purposes and scope of processing, and we process it on the institution's behalf under the institution agreement, as its processor (Korean Personal Information Protection Act, Art. 26; GDPR Art. 28). The institution informs its members of this.
- Your Klassian account and personal data (your scores, annotations, practice history, personal calendar, gaze data) do not belong to the institution, and the institution cannot see them. They remain when the agreement ends. However, scores you received in that institution group, with your annotations and recordings on them, are deleted from your device when you leave the group (§1.2).
(2) What is processed
| Who | Data | Purpose | Who sees it |
|---|---|---|---|
| Members | Seat (which institution, period), name within the institution (entered by the institution), part (instrument, number), class, permissions (notices, score distribution, annotation sharing), how they joined (invitation, roster match) | Running seats and institution groups | Administrators. Name within the institution, part and permissions are also delivered to the apps of members of the same institution group |
| People not yet signed up (roster entries) | Name within the institution, email (optional), part, class to join, record of matching after sign-up | Matching a roster entry when the person signs up | That institution's administrators only |
| Invitations | Email address invited, name attached to a personal link, note on an administrator invitation | Sending and managing invitations | Administrators (administrator invitations: master account) |
| Administrators | Account, contact email (entered by the administrator), permission expiry and status | Granting administrator rights; contact with the institution | Master account, the administrator |
| Institution shared account (master account) | Institution login ID, password (stored only in a non-reversible form), consecutive failed attempts and lockout, last sign-in time and method | Access control | Our staff (no one can see the password) |
| Dashboard access logs | Who (account), when, what (sign-in, viewing or exporting the roster and the like), IP address, browser information | Statutory access logging (Korean security standards), investigating incidents | Master account. We provide a copy at the institution's request |
| Activity records | What administrators and the master account did (invitations, permissions, parts, renaming, removals and the like), and copies kept for restoring | Recovering from mistakes, accountability | Administrators (the master account: its own records) |
| Institution contract ledger | Institution name and type, seats, period, contract number, contact email, allowed sign-up domains | Performing the contract | Administrators and master account (summary), us |
| Contract renewal enquiries | Seats and period wanted, notes, reply email | Discussing renewal | Us |
| Score files uploaded by the institution — only if the institution uses this feature | Score files (which may carry names and the like), who uploaded them and when, record of confirming the right to distribute | Delivery to the members the institution chooses | Members who receive them, administrators |
| Institution lesson groups — only if the institution uses this feature | Lesson admin appointments, how lesson groups are made up, lesson schedules, requests and comments, lesson scores and their annotations, and upload records (the items in §1.18) | Running and overseeing the institution's lessons | Lesson materials: the lesson's two participants. The master account sees only, for each lesson, the lesson admin's and student's names within the institution, the date and start and end times, the number of lessons and the titles of lesson scores (not comments, annotations or lesson score files) |
- Roster files (spreadsheets and the like) are read only inside the administrator's browser; only the columns the administrator selects are sent to our servers.
- Adding an email address to a roster does not tell the institution whether a Klassian account exists for that address.
(3) What institution administrators see
- When you join an institution group, administrators see your display name and sign-in email address (in full if it is on a domain the institution has set; otherwise only the first two characters and the domain). Legal basis: contract (Art. 6(1)(b)) — it is part of the institution-group feature you join.
- Administrators set and see your name within the institution, part, class and permissions. The apps of other members of the same institution group also receive each other's name within the institution, part and permissions.
- For notices, only the number of readers is shown; not even administrators can see who has read.
- Dashboard access logs are visible only to the institution's shared (master) account.
- If the institution uses lesson groups, its master account sees, for each lesson in its institution lesson groups, the lesson admin's and student's names within the institution, the date and start and end times, the number of lessons and the titles of lesson scores — not lesson comments, annotations or lesson score files. This is the same where the student is under 18, and the institution tells its members about it. Institution lesson groups have no owner who can see every lesson (§1.18).
- Administrators cannot see your personal data, or the other groups you belong to.
(4) Retention and deletion
- Removing a person (withdrawing a seat). The person leaves the institution group immediately and their seat-based access ends. Their name within the institution and part remain only as a restore copy, cleaned up within 5 days after the restore period ends. Deleting a roster entry deletes its email immediately. The person's notice reads, votes and events remain as institution-group activity until the agreement ends and the data is destroyed. Email addresses of invitations sent by email remain in the administrators' invitation list — even after the invitation is used or expires — until the institution group is destroyed. Who removed which account, and when, remains in the activity records until the agreement ends and the data is destroyed.
- When an agreement ends. ① Seat-based access ends on the end date. ② For 5 days, administrators can only view and export, and members can only view what they received. ③ The institution group then closes and all members leave it. ④ The data is kept for the restore period. ⑤ Within 5 days after that, it is destroyed, after a check that the right data is being deleted. A certificate of destruction is available on request.
- At the institution's written request. The data is destroyed within 5 days of the end of the agreement, with a certificate of destruction. It can then no longer be restored.
- These periods can be varied in the institution agreement.
- Keeping and providing institution lesson group materials. When someone stops being a lesson admin, or an institution lesson group is deleted, its lesson materials are kept for 30 days as in §1.18 and then deleted; during that time they are provided to the institution at its written request. The institution agreement can provide otherwise.
- What is destroyed. The institution groups and their notices, notice reads, events, polls, lesson requests, distributed scores, shared annotations, operation records and notifications; institution lesson groups and their lesson materials (including lesson score files); rosters; activity records; administrator data; the institution shared account and the contract renewal enquiries sent from it; score files uploaded by the institution.
- What is kept after destruction.
- Dashboard access logs — 1 year from recording (2 years where the law requires). This is the statutory period; the logs are kept separately from other data, protected against alteration, and deleted only once the period ends. A copy is available at the institution's request.
- Institution contract ledger — for the period set by tax law (5 years from the statutory filing deadline for the tax period of the transaction). Personal fields such as the contact email and allowed sign-up domains are cleared at destruction. The institution's name remains; for a sole-proprietor institution, that name may be a person's name.
- Reports — 1 year from reporting (only the link to the group is removed).
- Our record of handling the institution — 5 years (institution name and reason; no member personal data).
- Lesson score upload records and rights holders' requests — for the periods in §3 (kept by us to deal with infringement notices and disputes).
- When a member deletes their account. Their roster entry, name within the institution and part are deleted immediately. Their name and part values in activity records are cleaned up after the restore period, and their account number when the agreement ends and the data is destroyed. Dashboard access logs remain, with the account field cleared.
(5) Your rights over data the institution entrusted to us
Please send requests to access, correct or delete data the institution entrusted to us (such as your name within the institution and part) to the institution. If you send them to us (support@klassian.com), we pass them on and help the institution respond.
(6) Children under 14
Institution agreements require institutions not to put anyone under 14 on a roster, and the roster screen says so (§9).
(7) Sub-processing
Processing under an institution agreement also uses the processors and sub-processors in §4 (Supabase, Amazon Web Services, Cloudflare and others); the institution dashboard passes through Cloudflare, and institution-group notifications go through Apple (APNs). The institution consents to this in the institution agreement. International transfers are as described in §5.
8. Your rights
If you are in the EU/EEA or the UK, you have the right of access, rectification, erasure, restriction, portability and objection (Art. 15–21 GDPR), and the right to withdraw consent at any time without affecting prior processing (Art. 7(3)). Wherever you are, you can ask us to give you access to, correct or delete your data, to stop processing it, or withdraw your consent. Most of this you can do directly in the app: edit or delete your profile, instrument, events and scores; toggle each consent in Settings (gaze, usage analytics, instrument, marketing); delete your account in Settings.
Right to object. Where we rely on legitimate interests (Art. 6(1)(f), marked in §1), you can object at any time on grounds relating to your particular situation by writing to support@klassian.com. We will then stop, unless we have compelling legitimate grounds that override your interests, or need the data to establish, exercise or defend legal claims.
- Data export: email support@klassian.com and we will provide your data.
- Data an institution entrusted to us: see §7A(5).
- Account deletion immediately removes from our servers your account, profile, group memberships, notifications, usage analytics, consent records, feedback, reports you made, your block list, and organisation enquiries sent from the app. Things to know:
- Groups you created are not deleted — ownership passes automatically to another member. If no members remain, the group is deleted. Lesson groups you own pass to a lesson admin, or close if there is none (a closed lesson group's materials are kept for 30 days and then deleted — §1.18).
- Events, polls and notices you wrote in a group or lesson group stay there; events and polls are re-attributed to "a former member". One-to-one lesson requests and their comments (including those in lesson groups), and annotations you wrote on lesson scores the other participant uploaded, are deleted, since they are between the two people involved.
- Lesson score files you uploaded are not kept: they are deleted from our servers at the next clean-up. On the other participant's and the owner's devices, the lesson scores you uploaded disappear from view at once and are deleted once 30 days have passed, when the app next checks with our servers; the lesson scores the other participant uploaded, and their recordings, stay with them. Past lesson schedules in a lesson group stay in their calendars, with you shown as a former member; lessons already scheduled for the future are cancelled, and the other participant is notified.
- Your roster entry, name within the institution and part in any institution group are deleted immediately; values in the institution's activity records are cleaned up as set out in §7A(4).
- Nothing on your device or in your iCloud is deleted — remove it yourself if you wish. Scores you received in a group or lesson group (including lesson scores), with your annotations and recordings on them, are deleted on the device you delete your account from; hidden copies may remain on your other devices and are removed if you delete the app there.
- Pseudonymous gaze data is not deleted, because it is not linked to your account (§7). Under Art. 11 GDPR, where a controller cannot identify the data subject, Articles 15–20 do not apply unless the data subject provides additional information enabling identification (Art. 11(2)); we do not collect extra information just to make identification possible.
- Score download records, payment notification records, lesson score upload records and admin records (access tiers granted or withdrawn, action taken on reports and the like) remain for their stated periods (§3). The link to your email and other account details is cut immediately; they remain only under your account number or transaction IDs.
- Subscriptions must be cancelled separately in Apple's subscription settings.
- If you leave a group, what you wrote stays with the group, attributed to "a former member". Scores you received from that group, with your annotations and recordings on them, are deleted from your device (§1.2).
- You also have the right to lodge a complaint with a supervisory authority — in Korea, the Personal Information Protection Commission (privacy.go.kr); in the EU/EEA, the authority in the country where you live or work, or where the alleged infringement took place; in the UK, the ICO (ico.org.uk).
We do not use automated decision-making or profiling that produces legal or similarly significant effects (Art. 22).
9. Children
Klassian does not knowingly collect personal data from children under 14 (or the higher age applicable in your country, e.g. 16 where national law requires). Sign-up includes an age confirmation, and accounts cannot be created below the threshold. Institution agreements also require institutions not to put anyone under 14 on a roster, and if we learn that data of a child under 14 has been entered, we delete it without delay.
10. Security
- Encryption in transit (HTTPS) throughout; row-level security, so that no query returns data beyond your own or your group's scope.
- Identity data and gaze data kept in separate server projects with separate keys; gaze data pseudonymised.
- Session tokens kept in the device Keychain; no server admin keys in the app or repository.
- Consent history is stored append-only, so entries cannot be altered (it is deleted together with your account).
- Institution management data (roster entries, activity records, dashboard access logs, contract ledger) can be read only by that institution's administrators and master account (dashboard access logs: master account only), through defined server functions — never from the app. When our staff view member or institution information in our admin tools, this is logged.
- The institution dashboard keeps your sign-in only within that browser tab — closing the tab ends it — and signs you out automatically after 30 minutes of inactivity or 12 hours after sign-in.
- The institution shared (master) account's password is stored only as a non-reversible hash, and the account is locked after 5 consecutive failed attempts.
- Dashboard access logs are protected against alteration and deleted only once their retention period ends.
- Lesson score files are kept in private storage and handed out only through links that work for five minutes, after our server has checked that the person may receive them. Files taken down after a report or a rights holder's request are moved to quarantine that no user can reach, and kept lesson materials are stored encrypted where the app cannot reach them. When our staff open a reported lesson score file or provide kept materials, this is logged.
10A. Cookies and similar technologies
- The app sets no cookies of its own. In the app's IMSLP screens, cookies IMSLP sets (such as accepting its notice, or signing in) are stored only on your device (§5).
- To send each first-use step (§1.20) only once, the app notes on your device which steps it has already sent. This note never leaves your device and is removed when you delete the app.
- Our website (klassian.com) uses no cookies for analytics or advertising. Cloudflare, which delivers the website, may set security cookies to block attacks.
- The institution dashboard (org.klassian.com) keeps your sign-in only in that browser tab's session storage, which is cleared when you close the tab. You can block this in your browser settings, but you will then be unable to sign in to the dashboard.
11. Changes
We will announce changes on the website at least 7 days before they take effect — 30 days for material changes such as new data categories or purposes.
12. Contact
Privacy officer: Kyujin Cho (sole proprietor) · support@klassian.com. In Korea you can also contact the Personal Information Infringement Report Center (dial 118) or the Personal Information Dispute Mediation Committee (kopico.go.kr).