Privacy policy

Practice without an account

You can train without signing in. Your phone stores your learning profile, instrument and training preferences, ear-test results, scores, XP, streaks, achievements, reminder preferences, an interrupted session and recent answer history. Exercises play sound; they do not record your microphone.

Removing the app’s local data removes that device copy. Your operating system’s device backups may contain app data, depending on your device settings. We do not operate those backups.

Optional Sign in with Apple

Launch sign-in uses Apple only. Apple identity tokens and authorization codes reach our API to verify your identity and obtain a token used to revoke Apple authorization when you delete your account. We store an Apple account identifier, internal account identifier, chosen nickname, account timestamps, authentication sessions and Apple authorization records. The app stores sign-in credentials in secure device storage. The initial Apple sign-in flow does not request your email address or real name.

Signing in enables cloud backup and public leaderboards. Our cloud backup contains your learning profile, ear-test results, XP, streak, best scores, achievements and summary statistics. Random device identifiers and earnings counters merge progress earned on multiple devices. Interrupted sessions and detailed recent answers are not sent to this backup service.

Public leaderboards

Signed-in training submits best test scores and weekly XP. Public rows show your nickname, public player identifier, scores or XP and test times. Apple sign-in identifiers are not public. Choose a nickname without personal information. Nickname reports store the reporting account, reported player and reported nickname for moderation.

To keep training separate from public scores, use the app without signing in. Signing out stops further account syncing but does not remove previous leaderboard entries. Account deletion removes those entries.

Payments and subscriptions

Apple processes payments. We do not receive your payment card number. RevenueCat processes purchase and receipt information, subscription status, app user identifiers and app/device information to validate Pro access. Signed-in purchases use your app account identifier; signed-out purchases use a RevenueCat-managed anonymous identifier. Automatic device identifier collection is disabled in our SDK configuration; this does not remove all technical app/device information.

Apple and RevenueCat keep transaction records under their own policies and legal duties. Deleting your Pitch Fox account does not cancel a subscription or automatically erase their transaction records. Contact us for help with a RevenueCat privacy/deletion request; Apple payment or Apple account requests must also be made to Apple. See Apple’s privacy policy and RevenueCat’s privacy policy.

Lesson videos and website requests

Lesson posters may load when a lesson opens. Video loads after you select Play. Our HTTPS media host receives network information such as your IP address, requested filename, request time and technical request details. Recent videos may use an evictable on-device cache targeted at 128 MB; this is not a guaranteed offline download. Bundled notes and practice remain usable without video hosting.

These static support pages use no analytics scripts, advertising pixels, contact-form trackers or cookies set by these pages. The web server still receives normal network/request information when you visit.

Reminders and analytics

Reminders are scheduled on your device through iOS notifications. Change them in Pitch Fox Settings or disable notification permission in iOS Settings. When configured in a release build, PostHog receives onboarding step views and completions, paywall interactions, subscription plan identifiers and purchase or restore outcomes to help improve onboarding and subscription flows. Events use a random identifier saved on your device, event/session identifiers, timestamps and technical SDK information. Network delivery exposes your IP address to the provider; automatic location enrichment is disabled. We do not send your Apple account identifier, nickname, email, profile answers, ear-test scores, reminder time, raw errors or payment receipts to PostHog. Session replay, automatic interaction capture, person profiles and advertising identifier collection are disabled. Development builds do not transmit these events. We do not sell personal data or share it for cross-context behavioral advertising.

Why we use information

We use account and progress information to provide sign-in, backups and leaderboards; purchase information to verify access; network and diagnostic records to operate, secure and troubleshoot services; support correspondence to answer requests; and analytics events to understand and improve onboarding and paywall conversion. Where applicable, our legal bases are performance of the services you request, legitimate interests in security and reliability, compliance with legal obligations, and consent where legally required. Optional device notification permission is controlled by iOS.

Providers and international processing

Our account API, PostgreSQL database and media files run on a self-hosted VDS provided by netcup in Germany. Apple supplies Sign in with Apple and App Store payments; RevenueCat supplies subscription validation; PostHog supplies onboarding and paywall analytics when configured. See PostHog’s privacy policy. Our PostHog project uses the US Cloud region. Support correspondence is routed through Zoho Mail (the domain uses its EU mail service). Zoho processes that correspondence under its privacy policy. Providers receive information needed for their roles. We may disclose information when legally required or necessary to protect service security, and in a business transfer subject to applicable privacy duties.

The operator is a United States company. Provider processing may occur outside your country. RevenueCat’s published policy states that customer data is sent to AWS data centers in the United States. Applicable international-transfer requirements must be respected; contact us for information about safeguards relevant to your request.

Retention and deletion

• Local practice: retained on your phone until you reset progress, remove app data or restore a different device copy.
• Active account data: retained while your account exists. Delete account removes live account records, cloud progress and leaderboard entries after successful confirmation. Apple authorization is revoked as part of that flow; if Apple cannot confirm revocation, the account is kept so you can retry.
• Web access logs: rotated daily, with 14 rotated files retained. Empty days and rotation timing can affect calendar age. New API diagnostic journals use a 14-day age limit and daily file rotation; rotation timing can extend removal to approximately 15 days. Older prelaunch infrastructure diagnostics remain in shared, storage-limited system journals and are not used as active account data.
• Server backups: daily backups use automatic age-based cleanup. Files at least 14 days old are removed at the next daily cleanup, so copies can persist for approximately 15 days. Backups are restricted operational recovery copies, not active account records. Any restoration must reapply completed deletion requests before restored account data is returned to service.
• Support correspondence and privacy requests: retained as needed to answer and document the request and meet applicable legal duties. Contact us to request deletion of correspondence; records legally needed to demonstrate compliance may be retained.
• PostHog analytics: retained under our configured project retention settings. Contact us for an analytics access or deletion request; app-account deletion does not automatically erase records under the separate random analytics identifier.
• Apple and RevenueCat records: subject to their own policies and legal retention requirements. Account deletion does not prove erasure of those independent records.

The production database started clean; development account records were not imported. Operator-held recovery copies follow the same retention/deletion procedure when they contain production account data. This policy does not promise that deleting the app cancels subscriptions or instantly erases backup and provider records.

Your controls and privacy rights

Sign out to stop account syncing. In Profile → Account → Delete account, remove the active server account while keeping local learning progress. Use Settings → Reset progress to clear learning progress; while signed in, a reset also replaces the cloud backup after server confirmation. A progress reset does not delete the account or leaderboard entries. See account deletion instructions.

Depending on your location, you may have rights to access, correct, export, delete or restrict data; object to certain processing; withdraw consent; and complain to your local privacy authority. Email dev@keyma.kr with “Pitch Fox privacy request.” We may ask for proportionate proof that the account belongs to you. Do not send passwords, Apple identity tokens, payment card details or private keys. We respond under applicable legal time limits and do not penalize you for exercising privacy rights.

Children and families

We do not request date of birth. Parents or guardians may contact us about a child’s personal information, account or deletion request. Use Apple’s family and purchase controls where appropriate. Choosing a non-identifying nickname reduces information exposed through leaderboards.

Changes

We update this page when processing changes and display the effective date. Material changes will be communicated as required by applicable law. New sign-in methods, advertising or analytics require a policy and store-disclosure review before release.