Your audio is for analysis, not for show.
JamKey exists to help you move faster in rehearsal, writing, practice, and session prep. This page explains what information JamKey may collect, how it may be used, and the practical boundaries around audio, account data, and support activity.
Information JamKey may collect
- Audio files or recorded clips you submit for analysis.
- Analysis results such as detected key, tempo, mode, and transposition data.
- Account details you provide if sign-in or synced history is offered.
- Device, app, crash, and diagnostic information used to keep the service stable and secure.
- Subscription status or purchase signals provided through Apple for Premium features.
How JamKey may use it
- To analyze your audio and return musical results inside the app.
- To provide history, account, and Premium features when those features are enabled.
- To improve accuracy, performance, reliability, and support.
- To manage subscriptions, prevent abuse, and maintain product security.
- To respond when you contact support or send feedback.
Audio handling
Audio you submit is used to run the analysis you asked for. If JamKey stores submitted audio, derived results, or history beyond the immediate analysis window, that retention should stay limited to what is needed to provide the feature, maintain the service, or troubleshoot legitimate support issues.
Sharing and service providers
JamKey does not sell personal information. Information may be shared with service providers that help operate the app, store data, process subscriptions, deliver infrastructure, or support security and reliability. Those providers should only receive what is reasonably needed to do that work.
Your choices
- You can contact JamKey with privacy questions or support requests at support@jamkey.app.
- You can manage or cancel Premium through your Apple account settings.
- You can stop using the website or app at any time.
- If JamKey later adds account deletion, export, or privacy-rights workflows, those requests should route through the support contact above unless a more specific in-app path is provided.