Privacy Policy
Clef for iOS is live on the App Store, and the free browser sight-reading trainer runs at clefdrills.com. This page explains, in plain language, exactly what each one collects, why, and how to get it deleted.
Clef for iOS needs no account or login. You can optionally sign in with Apple or give an email address, only to save your place and to get practice reminders and tips if you choose; the app works the same without it. Without an account, your practice history and progress stay on your device (Apple-managed device backups may contain a copy). If you sign in, Clef also keeps a copy of your practice progress on its own server so it follows you to your other devices; deleting the account deletes that copy. Apple handles payments. We use RevenueCat to process purchase records and measure which subscription offers are viewed and purchased, using an automatically generated customer identifier. Clef measures its own Apple Ads through Apple's AdServices framework, without your advertising identifier. Pseudonymous usage analytics (linked to a random install ID) are on by default; turn them off any time in the app's Settings. Clef does not receive your card details, use ad networks, or sell your data. The web trainer keeps your score in your browser; the website also uses the analytics described below.
Clef for iOS: what's stored, and where
Clef stores your practice preferences, drill sessions, streaks, accuracy history, and review due dates locally on your device. If you do not sign in, none of this is uploaded to our servers or to RevenueCat, and it is not synced between your devices. If you sign in, the practice progress described in the account sync section below is uploaded to Clef's server. The pseudonymous app-usage events described below carry only summary counts, never your individual answers.
If you enable iCloud Backup or make a device backup on your computer, Apple may include Clef's local app data. Those copies are managed through your Apple backup settings; see what iCloud backs up.
Clef for Android: what's stored, and where
Clef for Android keeps your practice history, progress and settings in a private database on your device. Version 1.0.0 has no account, no purchases and no analytics, and it does not connect to the internet, so none of that data reaches us.
Version 1.1.0 and later connect to the internet for the following. Accounts are optional: if you give an email address, we use it to sign you in, and to send practice emails while the email switch on that screen is on. In some countries the switch starts on, in others it starts off, and you can turn it off at any time. Google Play handles payments, and we use RevenueCat to process purchase records with an automatically generated customer identifier. Product analytics go through our own domain to PostHog, using a random install identifier and including onboarding steps, drills started and finished, paywall views, trials and purchases. In Clef for Android 2.0 and later they also record which screens you open and how long you stay on each, how far you scroll, when the app goes to the background or closes, where on the screen you tap (a named control or a rough area of the screen, never text you type), how long the paywall stayed open, which practice note was shown, the note you answered, whether it was right and how long it took, and the app version, build, device model, Android version, language and Google Play country. Each event carries a random session identifier and, once you buy or restore, your RevenueCat customer identifier. Clef uses the Google Play install referrer to learn which link or campaign an install came from. It does not use your advertising identifier and keeps no recordings of your screen. You can turn analytics off in Settings at any time.
Crash reports (Clef for Android 2.0 and later): when the app crashes or stops responding, Clef sends one event about it the next time it opens, through the same analytics path and the same switch. It carries the app version and build, your device manufacturer and model, your Android version, the type of crash, and the technical crash location (the names of the program classes and lines of the crashed thread, and the exception's class name). It contains no content: no practice answers, text you typed or exception messages. While the switch is off, Clef sends no crash reports and keeps none to send later.
Install facts (Clef for Android 2.0 and later): RevenueCat also receives the first app version and build this install ran, the date it was first installed, and whether it is a test install, so that test installs can be left out of our sales numbers. These go with the customer identifier above, whether or not analytics are on.
Uninstalling the app or clearing its storage deletes the data on your device.
Delete your Clef account
If you created a Clef account, open Clef, then Settings, Account, and choose Delete account. You can also ask without the app by emailing support@clefdrills.com from the address on the account. Deleting the account removes your email address and the progress saved with it. Purchase records are kept where tax and accounting rules require it.
Clef asks for Bluetooth permission only when you choose to connect a Bluetooth MIDI keyboard. On Android 11 and earlier, the system also requires the location permission for that Bluetooth search. Clef never reads or stores your location.
Notifications
If you opt in, Clef for iOS can send local practice-reminder notifications, scheduled entirely on your device using iOS's local notification system. These aren't sent from a server and don't involve any third party. You can turn them off any time in iOS Settings > Notifications > Clef.
Clef for Android can also send a daily practice reminder if you allow notifications. It is scheduled on your device, not sent from a server, and you can turn it off in Clef's Settings or in Android Settings.
Purchases, subscriptions, and RevenueCat
Apple processes subscription payments and the one-time Lifetime purchase through In-App Purchase. Clef and RevenueCat do not receive your card number, billing address, or Apple Account password. We do receive purchase information, such as the product purchased, transaction identifiers, dates, price and currency, and subscription status.
We use RevenueCat, a purchase-management service, to process purchase records and analyze subscription offers. RevenueCat assigns a random customer identifier without requiring a Clef account, name, or email address. If you create the optional account and agree to practice emails, your email address is also shared with RevenueCat as described in the account section below. Purchase records and offer-view events are associated with this identifier so we can understand purchases, renewals, and the results of pricing experiments. From Clef 2.0, RevenueCat also receives the first app version, the first build and the first download date of this install, and whether it is a test install; this stays on whether or not usage analytics is on.
- Purchase records: receipt or transaction information, product identifiers, and purchase and subscription history, used for purchase verification, reporting, and support.
- Offer views: which subscription offer was displayed and when, including its paywall and experiment offering identifiers, used to measure the effectiveness of offers.
- Apple Ads measurement (always on, no tracking): Clef uses Apple's AdServices framework to measure its own Apple Ads. This needs no permission and does not use your advertising identifier (IDFA) or App Tracking Transparency. Clef asks Apple for an attribution token. Clef and our purchase service RevenueCat each send it to Apple, and Apple replies whether the install came from one of our Apple Ads and, if so, the ad's organization, campaign, ad group, keyword and ad identifiers. These identifiers describe our ad, not you. Clef keeps this result on your device and stores it on your RevenueCat customer record, so we can see which of our own ads lead to trials and purchases. When RevenueCat reports a direct purchase, a free trial converting to a paid subscription, or a refund to our server, we keep a record of that event without your customer identifier: the purchase type, product, billing period, price, currency, store, date, the refund reason if there is one, these ad identifiers and, while pseudonymous usage analytics are on, the source category described below. We use these records only to count the purchases each campaign and channel brought. Your RevenueCat customer record also notes which version of the first-run screens you were shown (the
clef_flow_armexperiment label), so we can compare versions; this label does not identify you. We do not combine this with data from other companies, and we do not use it to target ads. - Technical information: RevenueCat's SDK sends app and operating-system versions, device model, language preferences, App Store country, and Apple's vendor device identifier (IDFV) with service requests. It also receives connection information needed to communicate with the app.
The app may keep pending purchase reports on your device and retry delivery later. These reports contain purchase and customer identifiers, not your practice answers or payment credentials. Deleting the app does not remove records already processed by Apple or RevenueCat.
We use this information to operate purchases and understand our own subscription offers. We do not use it for cross-app advertising, send it to ad networks, or sell it. You can contact us about purchase-related data using the details below.
Optional Clef account (Sign in with Apple or email)
After your first completed lesson, and any time later in Settings > Account, Clef for iOS offers an optional account. It is never required: every lesson, track and purchase works without one, and you can skip the offer. There are two ways to create it.
- Sign in with Apple. Apple verifies you and gives Clef a stable Apple user identifier and, if you allow it, your email address or Apple's private relay address. Our server checks Apple's signed identity token before it stores anything.
- Email only. You enter an email address. The switch for occasional practice reminders and tips is shown next to it and can be turned on or off before you continue. We send one message asking you to confirm, and send nothing more until you do.
What we store: the Apple user identifier (Sign in with Apple only), the email address, whether you agreed to practice emails and when, the RevenueCat customer identifier of your app, the language of your device, a creator or offer code you redeemed (if any), and the time the account was created. We use this to keep you signed in to one account, to send the practice emails you agreed to, and to credit a creator whose code you redeemed. Your synced practice progress is stored with the account as described in the next section.
Practice emails are a separate choice. The switch for weekly practice reminders and tips is shown on the account screen before you continue, and you can turn it off there. A sign in button on a screen without the switch never turns emails on. Depending on the country of your App Store account, it may start turned on; in the European Economic Area, the United Kingdom, Switzerland and Canada it starts turned off. Signing in to an account that already exists never turns emails on by itself. Every email has an unsubscribe link that works with one confirmation, and you can change this at any time in Settings > Account. While it is on, we also pass your email address to RevenueCat as a customer attribute so purchase and email records match. The legal basis for these emails is your consent, which you can withdraw at any time without affecting the app.
Deleting it. Settings > Account > Delete account removes the account record from our server immediately. Emails already processed by Apple, Resend (our email sender) or RevenueCat are handled under their own policies; write to support@clefdrills.com if you want us to ask them to delete their copies. Account data is kept on our own server and is not sold or used for advertising.
Microphone
Listening to your piano is optional and only starts when you turn it on. Clef then asks for the microphone. Sound is processed in memory on your device to check the notes you play, and it is overwritten within a second. Clef never records it, never saves it and never sends it anywhere. Your calibration result (a room level and a tuning number) stays on your device. Analytics about listening contain numbers only, never audio.
Account sync
What is uploaded. When you sign in, Clef uploads a snapshot of your practice progress: the review schedule for each note or card (when it was last reviewed, how well it is remembered, when it is due again), accuracy counts and response times, your streaks and progression, your onboarding profile (your goal and level), and your app settings. It also sends the email address you used for the one-time code, or your Apple user identifier if you signed in with Apple. It does not send the audio of anything you played.
Where it is stored. On Clef's own server, linked to your account. It is used to restore your progress on a new device and to keep your devices in step, and for nothing else. It is not sold, shared with advertisers or used for advertising.
Deleting it. Settings > Account > Delete account removes the account and the synced practice progress from our server. If you never sign in, nothing is synced.
The web trainer's practice scores
When you ask the website to send you the App Store link, we send one email and keep a scrambled (hashed) record of the address for a day to avoid duplicate sends and to limit abuse, not the address itself. The address is never added to a mailing list or sent to analytics.
The name-the-note drill at clefdrills.com needs no account or sign-up. Individual answers and the running session state are held in your browser, and your best streak is saved there using localStorage. When you complete a web drill, the site sends its final score, best streak, accuracy, and page address to our self-hosted Umami analytics. We use these completed-session events to understand the web trainer; they are not linked to a name, email address, or iOS purchase record.
Email me the app link (website only)
If you enter your email address in the website's optional form, we use Resend to send you the Clef App Store link you requested. Your address may also be stored in our Resend contact list. This form is separate from the iOS app's RevenueCat customer records and from the optional app account; we do not connect an address entered here to those records.
We use your IP address to limit repeated submissions. When a request is recorded through an owner-notification email instead of the contact list, that email includes your address, IP address, and request time and is delivered through Resend to Clef's operator. Email addresses and delivery results also appear in our operational logs; delivery errors may be reported to Sentry for troubleshooting. You can ask us to access, correct, or delete your email-related records using the contact details below. This also applies to addresses submitted through the earlier launch waitlist.
Clef for iOS: usage analytics and how you found Clef (pseudonymous, on by default)
Pseudonymous usage analytics, linked to a random install ID, are on by default; turn them off any time in the app's Settings. The switch is Settings > Privacy > Share pseudonymous usage analytics. While it is off, the app sends no usage events, no identifier and no source information. The only data that still leaves the app is the Apple Ads measurement and the purchase records described in the RevenueCat section above.
While it is on, Clef:
- creates one random identifier (a random UUID) the first time you open the app and keeps it in your device's Keychain, so it survives a reinstall but is not synced to other devices. It is not your name, email, Apple Account, advertising identifier (IDFA) or vendor identifier (IDFV).
- sends usage events with that identifier to our self-hosted Umami server on our own domain (
clefdrills.com/stats) and to our product analytics service PostHog (PostHog Inc.), which stores the data on servers in the United States and uses the same random identifier. Events include onboarding steps, drills started and finished, paywall views, trials and purchases. They carry summary numbers such as item counts, accuracy and duration, plus app version, build number, iPhone or iPad model, iOS version, App Store country, language and screen size. They also record which screens you open and how long you stay on each, when the app goes to the background or closes and how long the session lasted, which buttons you tap (the name of the control, never text you type), how long the paywall stayed open, and which plan or offer variant you were shown, so we can compare versions and tests. For each practice note question the app records which lesson it was, the note shown, the note you answered, whether it was right and how many milliseconds it took, so we can see which notes are hard and whether people improve. Each event also says which app session it belongs to: a random session identifier, the number of that session on this install (1 for the first), whether it is the first, how long the session has run, and whether you are signed in to the optional account (never your email or account token). A new session starts when the app opens fresh or comes back after more than 30 minutes in the background. Test builds from TestFlight and developer builds are marked as internal so we can leave them out of our numbers. They also include the Apple Ads identifiers above. PostHog events and its pseudonymous profile also carry your approximate country from your App Store region and how you found the app (for example an Apple search ad), so we can see which channels and countries lead to trials and purchases; this is kept by the first source only and is not linked to your name or email. Your IP address is not passed on to our analytics server. - records how you found Clef, as one of these categories: Apple Ads, a website or partner link, App Store product page, email, search, AI assistant, social media, app directory, App Store search, or unknown. It also records a short campaign label. The category comes from the
ctorsrclabel in a Clef link that opened the app, a creator or teacher code you redeemed, or your answer to a one-time question, "How did you find Clef?", which you can skip. The answer is a fixed choice, never free text. - stores that identifier, source category, campaign label and your analytics setting on your RevenueCat customer record, which also holds your purchases, so we can see which channels lead to trials and paid subscriptions. If you create the optional Clef account while it is on, the account record also stores the source. This data is linked to your RevenueCat customer record (and to your account, if you have one).
Crash reports (Clef 2.0 and later): when the app crashes, Apple's MetricKit gives Clef a crash report the next time the app opens. While usage analytics are on, Clef sends one event per crash to the same analytics services, with the app version and build the crash happened on, your device model, your iOS version, the type of crash, and the technical crash location (the names of the program files and code offsets of the crashed thread, and for an Objective-C exception only its class name). It contains no content: no practice answers, notes, text you typed, exception messages or file contents. While the switch is off, Clef sends no crash reports and keeps none to send later.
Screen recordings (session replay, from Clef for iOS 2.0.1): while usage analytics are on, Clef records how you use the app as a screen recording and sends it to our product analytics service PostHog, so we can see where people get stuck. All text, text fields and images are masked before anything leaves your device, so what you type, the notes and text on screen and any pictures are never in a recording. It shows only the layout of the screens and where you tap and scroll. The recording uses the same random identifier as the events above. While the switch is off, Clef records nothing and sends no recordings; turning it off stops recording right away. Email support@clefdrills.com and we will delete recordings already received.
What it never contains: audio or recordings of your playing, readable text or images from your screen, free text, contacts, precise location, your IDFA, or anything used for advertising across other companies' apps or websites. We do not use App Tracking Transparency, do not track you across other companies' apps or websites, and do not sell this data or share it with data brokers or ad networks.
Turning it off stops all usage events right away. Clef deletes the random identifier from your device and from PostHog's device storage, the stored link touches and your "How did you find Clef?" answer from your device, clears the identifier and source fields on your RevenueCat customer record, and clears any source saved in your optional Clef account (the analytics field on RevenueCat then reads "denied"). Turning it back on creates a new random identifier that is not linked to the old one. Deleting your Clef account also resets the identifier. The Apple Ads measurement stays, as described above. Events already received by our analytics server are not erased automatically. Email support@clefdrills.com and we will delete them.
Earlier versions: versions 1.0.7 to 1.0.9 sent usage events with a random install identifier. Versions 1.0.10 to 1.0.12 kept analytics off until you agreed in a one-time card or in Settings. Version 1.0.13 and later have pseudonymous analytics on by default, with the in-app switch above to turn them off; if you had said no, that choice is kept.
Website analytics
Every page on this site loads small first-party analytics scripts, hosted on our own server, so we can see how many people visit, which pages they read, how long they stay and what they click. Page views and visits are counted with Umami, an open-source, cookieless analytics tool that runs from clefdrills.com/stats, our own domain. Product analytics (the pages you view and leave, how long you stay and how far you scroll, which buttons you click, the campaign tag on the link you arrived by, and the checkout steps) are sent through our own domain to PostHog (PostHog Inc.), described below. The iOS app's usage events are described above, and its purchase and offer analytics in the RevenueCat section.
- No cookies. Umami runs without cookies. To count visits and countries, our server passes your IP address, rough country and browser details on to it, and Umami identifies a "visit" using a regularly rotating hash of them instead of storing your IP address. If your browser sends Do Not Track or Global Privacy Control, the site sends no analytics at all. The iOS app's usage events never include your IP address.
- No account identity. Reports include visits, page views, referrers, rough country, browser, and completed-drill events. We do not link these records to your name, email address, or iOS purchase records.
- PostHog on the website. The website's product analytics go to PostHog (PostHog Inc.) through our own domain, using a random identifier kept in your browser's local storage (not a cookie). No IP address, name or email is sent. The same Do Not Track and Global Privacy Control rule applies: if your browser sends either, nothing is sent.
- Never an ad network. Website analytics are never sent to Google, Meta, an ad network, or any other company except PostHog as our analytics service provider.
What we don't do
- No advertising cookies, no cross-site tracking, no ad-network pixels, no selling or renting of email addresses, practice data, or analytics data to third parties.
- No Clef account or password is required. An account is optional, as described above; without one the iOS app uses RevenueCat's random customer identifier for purchase and offer records.
- No advertising identifier (IDFA) collection and no App Tracking Transparency prompt. Apple Ads measurement for our own campaigns uses Apple's AdServices framework, as described above. Pseudonymous app usage analytics are on by default and can be turned off in Settings.
Your rights: access, correction, deletion
Deleting Clef removes its local app data from that device. Any copies in device backups must be managed separately through your Apple or computer backup settings. If you signed in, we hold a server copy of your synced practice progress; Settings > Account > Delete account removes it. If you never signed in, we hold no server copy of your practice history.
For access, correction, or deletion requests concerning purchase and offer records processed through RevenueCat, or a website email request, contact support@clefdrills.com. We may need information to locate the relevant record and verify your request; never send a card number or Apple Account password. We will explain any records that must be retained to meet legal obligations or resolve a transaction. We aim to respond within a few business days.
Deleting the app or requesting data deletion does not cancel an Apple subscription. Manage or cancel it in your Apple Account's subscription settings; see Apple's cancellation instructions.
Children's privacy
Clef is not directed at children under 13. The app and web trainer do not ask for a child's name, age, or contact details. If you believe a child has provided personal information to us or through our service providers, contact us so we can investigate and address it.
Changes to this policy
The November 9, 2026 update adds crash reports for Clef 2.0 and later on iOS and Android, sent through the same analytics switch, and the install facts and reminders of Clef for Android. The November 8, 2026 update also describes the session fields on each event, as above. It adds the account sync section (signed-in users have practice progress stored on Clef's server), corrects the analytics version range to 1.0.10 to 1.0.12, and describes the analytics data as pseudonymous. It also states that PostHog events also carry your approximate country from your App Store region and how you found the app. The November 7, 2026 update makes pseudonymous app usage analytics on by default, with a switch in Settings > Privacy, and removes the one-time consent card. The October 24, 2026 update covered Clef 1.0.10 and later: app usage analytics became opt-in, source attribution is added for people who opt in, and the Apple Ads measurement now also stores the attribution result on your RevenueCat record and in our purchase counts.
We update the date at the top of this page when this policy changes. The October 8, 2026 update adds the optional Clef account. The October 1, 2026 update explains requested website resources, page and campaign attribution, browser storage, and optional marketing email.
Tools, downloads, and website attribution
When you ask for a printable PDF or the App Store link by email, the request can include your email address, the signup page path, the tool or resource requested, and limited attribution information: the first and current signup campaign and the referring website's hostname. We use this information to deliver the requested item, understand which Clef pages and campaigns are useful, prevent abuse, and troubleshoot delivery.
The website keeps first-touch attribution in your browser's localStorage for up to 90 days and keeps current signup attribution in session storage. A request is assigned a random request identifier. The notes, chords, tablature, or other contents you paste into the browser tools stay in your browser and are not sent to Clef.
Requested PDFs and app-link emails are delivered through Resend. Marketing email is optional: we send practice tips or offers only after you separately confirm that choice, and every marketing message includes an unsubscribe option. Asking for a PDF or app link alone does not subscribe you to marketing.
To request access to or deletion of these website email and attribution records, email hello@clefdrills.com.
Clef in ChatGPT and other AI assistants
Clef offers read-only tools that AI assistants such as ChatGPT can call through our MCP endpoint at clefdrills.com/mcp: finding Clef guides, transposing chord symbols, spelling chords as piano notes, and mapping guitar tab to piano pitches. No Clef account or sign-in is needed.
When you use these tools, Clef receives only what the assistant sends to the tool, such as the chord symbols, tablature, or search words in your request. We use it to compute and return the answer. We do not store these inputs, link them to you, or use them for analytics or marketing. Clef does not receive your conversation, your assistant account details, or your memory.
As with any website request, our hosting and network providers process standard technical data, such as IP address and time, to deliver and protect the service. If a tool request fails, an error report may be sent to our error-monitoring provider (Sentry) so we can fix the problem.
Your conversation itself is handled by the assistant you use, under its own privacy policy (for ChatGPT, OpenAI's). You can disconnect Clef from your assistant at any time in the assistant's settings.
Optional email in the Clef app
This section applies from the first version of the Clef app that offers optional email sign-up.
If you choose to submit your email in Clef, we collect your email address, a hashed app install identifier, your locale and app version, the capture location, the consent text and version you saw, and, if you agreed to be asked “How did you find Clef?” and answered, that self-reported answer (for example “Search” or “A friend or teacher”), which is sent with your email. After you confirm your email, the app also sends the date (the day only, with no time or activity details) on which you last opened Clef, at most once a day; we store only the latest date with your email to time reminders and to stop them when you come back. Your email is linked only to hashed install identifiers: one for the device you signed up on, plus one for each other device you approve by confirming a link we email you. Each is a random ID created on that device and hashed before it is sent; it is stored only on our server. This email sign-up record is not tied to a Clef account, your Apple ID or your name. We use your email to send the weekly practice plan and progress report. If you separately turn on the unchecked-by-default marketing consent, we may also send practice tips and reminders after you stop practising. The legal basis for both uses is your consent.
Your email is stored only on our own server. It is not used for third-party advertising or tracking and is not shared with ad networks or data brokers. Emails are sent by our processor, Amazon Web Services (Amazon SES), via mail-api.opsibyte.com.
We keep your email until you unsubscribe. Unconfirmed addresses are deleted after 30 days. Every email includes an unsubscribe link, and you can also remove your email in Clef Settings. Unsubscribing or removing it deletes the email address and consent record; we keep only a one-way hashed suppression entry to honour your opt-out.
Questions about your data
Email support@clefdrills.com any time. A person reads it, not a ticket queue. See also our Terms of Use and the Support page.
Get Clef on the App Store →Free to download. Annual starts with a 1 week trial, then $59.99/yr (just $5.00/mo), monthly $9.99, or $99.99 lifetime. Try the free web drill