FingerMate Privacy Policy
Last Updated: November 8, 2026
This Privacy Policy explains how personal information is handled when using the FingerMate application ("App"). Please read this before using the App.
1. Information We Collect
1.1 Information provided by users
- Repertoire information: song title, artist name, difficulty, tuning, notes
- Tuning settings: custom tuning names and string notes
- App settings: theme, reference pitch (Hz), language
1.2 Microphone audio (tuner and recording features)
- Tuner feature: used only for real-time pitch detection; audio is not recorded or saved
- Practice recording feature: audio recorded by user action is saved only on the device
- Recording files are never sent to external servers
1.3 Diagnostic and usage information sent automatically
- Usage statistics (Firebase Analytics): which features are used and how often, plus device information such as model, OS, and language
- Crash information (Firebase Crashlytics): error details when the App crashes, device model, OS, and App version
- Details of what is sent and why are described in "3. Sharing with Third Parties"
The App does not collect personally identifiable information (PII) such as name, email address, or phone number. In-app data such as your repertoire, recordings, and settings is stored only on the device and is not sent to our servers. However, the diagnostic and usage information in 1.3 and the information related to ad delivery are sent to the providers of the services listed in Section 3 (such as Google).
2. How We Use Information
- Providing repertoire management (song registration, search, and organization)
- Providing tuner feature (real-time pitch detection from microphone audio)
- Providing metronome feature (BPM settings, tap tempo)
- Providing practice recording feature (recording, playback, and management)
- Saving app settings (theme, reference pitch, language)
- Investigating and fixing bugs (reviewing crash information)
- Improving the App (reviewing feature usage statistics)
3. Sharing with Third Parties
3.1 Google AdMob (ads, free plan only)
- Device information and advertising ID may be used for ad delivery
- See Google's Privacy Policy for details
- Pro plan users will not see ads
- In regions where consent is required (such as the EEA and the UK), the ad SDK is not initialized until you give consent in Google's consent form (UMP)
3.2 Google Play Billing (in-app purchases)
- Pro plan purchases are processed via Google Play Billing
- Payment information is processed directly by Google and not stored on our servers
3.3 Firebase Analytics (Google, usage statistics)
- Purpose: to understand which features are used and how often, and to use that to improve the App
- What is sent: the occurrence and count of actions such as completing onboarding, viewing the Pro plan prompt and starting, completing, canceling, or failing a purchase, adding a song, saving a recording (with its length), starting the tuner or metronome (with the BPM), importing (with the file format) and opening a score, adding a reference audio track, and viewing a prompt for a Pro-only feature. For purchase errors, the error message returned by Google Play (up to 100 characters) is attached. Text you enter, such as song titles and notes, and the audio you record are not sent
- Device and user attributes: whether the device is an emulator, whether the Pro plan has been purchased, and the App version. Firebase also automatically sends launch and session information, device model, OS, language, approximate region, and an anonymous installation ID issued per app. The device's advertising ID may be used (you can reset or delete it in your device settings)
- Relation to consent: collection is turned off when the App starts. It begins after the consent check is complete. In regions where consent is required, such as the EEA and the UK, it begins after you give consent in Google's consent form (UMP)
- See Privacy and Security in Firebase for details
3.4 Firebase Crashlytics (Google, crash information)
- Purpose: to investigate why the App crashed and fix the bug
- What is sent: the time of the crash and its stack trace (where the error occurred), device model, OS, App version, and an anonymous installation ID issued by Crashlytics. No information that identifies you, such as name or email address, is attached
- Relation to consent: collection is turned off by default and begins after the same consent check as in 3.3. It is not collected in development builds
- See Privacy and Security in Firebase for details
We do not provide personal information to third parties beyond the above without user consent.
4. Data Storage and Security
- Repertoire, tuning, and recording data are stored in the device's local database
- Recording files (m4a format) are stored in the device's internal storage
- This data is never sent to external servers and cloud sync is not performed (except for the diagnostic and usage information in Section 3)
- All data on the device is deleted when the App is uninstalled
5. User Rights
- Individual deletion: songs, recordings, and custom tunings can be deleted individually within the App
- Full deletion: all data on the device is deleted when the App is uninstalled
- Diagnostic and usage information: this is sent to the provider (Google) in a form that does not identify you, so it cannot be deleted for an individual user. To stop collection, please uninstall the App. You can reset or delete the advertising ID in your device settings
6. Children's Privacy
The App does not intentionally collect personal information from children under 13.
7. Changes to Policy
This Privacy Policy may be updated as needed. Updated policies take effect upon posting on this page.
Privacy inquiries: yukinon.lab@gmail.com