Privacy
What we keep, and why.
Clefy helps music academies run practice between lessons. Academies buy Clefy; teachers assign work; students practise; everyone can see progress before the next class. This page says what we collect to make that work, what we do with it, how long we keep it, and who else touches it. It is written to be read.
Effective 13 September 2026
Who we are
Clefy is the practice platform for music academies operated under the Clefy brand. The marketing site is clefy.io. Teachers and academy admins sign in at app.clefy.io. Students sign in at learn.clefy.io. The API lives at api.clefy.io.
For anything in this policy, write to hello@clefy.io.
What Clefy is
Clefy connects lessons, practice, and progress. Academies buy and configure Clefy for their studio or school. Teachers and admins invite students, assign practice, and review progress. Students see what to practise and get feedback on that practice.
Demo requests from the marketing site help us schedule a walkthrough. Product accounts live in the teacher and student apps above.
What we collect, and why
We do not sell personal data to advertisers. We do not build advertising profiles from practice data.
If Clefy uses an AI model to generate practice feedback or similar help inside the product, we use it to answer that request. We do not use student practice content to train public foundation models. Token or usage counts may be kept for limits and billing where that applies.
| Data | Why |
|---|---|
| Name, work email, phone, academy name, country, and approximate student count from a demo request | To respond to demo enquiries and understand fit |
| Account email, name, role (admin, teacher, student), and sign-in credentials (for example a password hash or a third-party sign-in id) | To create and secure accounts |
| Session records, including IP address and browser or device details that started a session | To keep people signed in and to end sessions when needed |
| Academy / studio profile: name, branding you upload, timezone, instruments, levels, and class or roster structure | That is how Clefy is organised for your school |
| Student roster details the academy or teacher enters: name, contact details they choose to store, level, instrument, class membership | To place students in the right practice path |
| Practice assignments, due dates, pieces or exercises, teacher notes | So students know what to play |
| Practice activity: when practice happened, duration, completion, scores or feedback the product generates, and recordings or submissions if the academy uses those features | So teachers can see progress between lessons |
| Messages or support email you send us | To help you |
| Plan, subscription status, and a customer id from our payment provider | To know what has been paid for. Card details go to the provider and never reach us |
| Basic product analytics and diagnostics (for example feature use and errors), kept as light as we can | To keep Clefy reliable and improve it |
| Cookie consent choices on clefy.io (via CookieYes), including which cookie categories you accept and when | To remember your preference, show or hide non-essential cookies, and keep a record that consent was asked for |
| Server logs with IP address, request path, and timing | To debug outages and abuse. Kept for a short rolling period |
Cookies on clefy.io
The marketing site at clefy.io may use cookies and similar storage. Essential cookies keep the site working (for example remembering that you already answered the cookie banner). Non-essential cookies—such as analytics—only run after you accept them in the CookieYes banner, or if the law allows them without consent in your region.
You can change or withdraw cookie choices later through the CookieYes preferences link on the site. CookieYes processes consent records as our processor so we can show the banner and keep proof of consent.
Who else handles it
We use a small number of processors, each for one job. They process data only to provide that service to us.
- Hosting and infrastructure for the website, apps, and API (for example Vercel or equivalent cloud hosts).
- Database and file storage for account, academy, and practice data.
- Email delivery for invites, magic links, and transactional mail.
- Payment provider for subscriptions; they are merchant of record for card data.
- CookieYes for the cookie consent banner and consent logs on clefy.io.
- Analytics or error monitoring, if enabled and consented where required, to find what is slow or broken.
- Sign-in providers you choose (for example Google), only if you use them.
How long we keep it
To delete an account or a whole academy workspace, write to hello@clefy.io. Self-serve deletion may be added later.
- Demo requests are kept long enough to follow up and for ordinary business records, then deleted or anonymised when no longer needed.
- Account and academy data stay while the academy uses Clefy. If an academy closes its workspace, we delete or anonymise personal data on a schedule after a short retention window (intended around 30 days unless law or unresolved billing requires longer).
- Practice activity follows the academy workspace. When a student is removed, their practice history is removed or anonymised with the workspace retention schedule unless the academy asks us to keep a non-personal aggregate.
- Billing records are kept as long as accounting and tax rules require.
- Server logs are kept for a short rolling period for debugging.
Academies, teachers, and students
Clefy is usually bought by an academy. That academy decides who is invited, what roles they have, and what practice data teachers can see.
Academy admins control the workspace and billing contact details. Teachers see students and practice progress for the classes they are given. Students see their own assignments and feedback.
If you are a student or parent and have questions about what the academy stores in Clefy, start with the academy. You can also write to us and we will help within what the product and the law allow.
Your choices
Write to hello@clefy.io.
- Ask for a copy of personal data we hold about you, or ask us to correct it.
- Ask us to delete your account or remove you from a workspace, subject to the academy’s legitimate records needs and the law.
- Opt out of non-essential marketing email (product and billing mail may still be required).
- Change or withdraw cookie preferences on clefy.io through the CookieYes banner / preferences control.
- For demo requests, ask us not to contact you further.
Children and young students
Clefy is built for music academies. Many students are children or teenagers enrolled by an academy or with a parent or guardian involved.
- We do not knowingly sell Clefy directly to children for their own unpaid consumer account outside an academy context.
- When an academy invites a student who is a minor, the academy is responsible for having the right to do so (including any parent or guardian consent the law requires where they operate).
- If you believe a child has been added without proper authority, tell us at hello@clefy.io and we will work with the academy to remove the account.
International transfers
Clefy may be hosted or supported in more than one country. When personal data moves across borders, we use appropriate safeguards required by applicable law (for example contractual clauses with processors).
Changes
If this policy changes, the new version is posted on the Clefy website with a new date. A change that materially reduces your rights is announced by email to academy contacts where we can before it takes effect.
Questions? Just ask.
Write to hello@clefy.io and a person answers.
Email us