WakemusicThis policy applies to Wakemusic distributed through App Store, provided by Kaka Inc. Other distribution channels have their own versions. Contact support@passlockapp.com with privacy questions or rights requests.
1. App features and data use
Wakemusic is a tool for playing local and connected cloud music libraries.
The app reads the music files you select and their metadata to build and play your library. When you connect a supported cloud service, the app may access the account display name, file metadata and authorization credentials needed to browse or download the music you request. Connections may include Google Drive, Dropbox, OneDrive, Box, pCloud and Apple storage services, depending on the version. These connections go directly to the provider; we do not operate a backend to hold your music library or cloud credentials.
When you request music recognition, ShazamKit creates an acoustic signature and sends it to Apple's recognition service to find a match. Apple describes these signatures as non-invertible; the recognition request does not share the original audio with Apple.
2. Analytics and purchases
We do not operate our own application-data backend. We do use third-party services, which process data separately:
- Firebase helps us understand app usage through installation identifiers, usage events and device/app information. Events depend on the version's configuration.
- RevenueCat handles purchase validation and entitlements using app user identifiers, transaction records and subscription status.
- App Store handles purchases, payment and store-account information for this channel under its own rules.
These purposes do not require sending your music or video content to analytics or purchase services. Service identifiers should not be assumed to be completely anonymous.
3. Permissions and connected services
File, media-library and connected-account access is used for the features you request. Manage system permissions in device settings; declining a necessary permission may prevent that feature from working. Review the requested permissions when connecting an account. Providers also process information under their own policies.
Google API data is used to provide or improve requested user-facing features in accordance with the Google API Services User Data Policy, including Limited Use requirements. YouTube API features are also subject to the YouTube Terms of Service and Google Privacy Policy. Revoke access in Google account connections.
Service information: Firebase privacy and security, RevenueCat privacy policy, Apple privacy policy, and Google privacy policy.
4. Retention, deletion and security
You can manage local files and app data and revoke connections in the provider's account settings. Uninstalling the app may not remove system backups, Keychain entries, cloud copies or third-party records, and does not cancel a subscription.
Analytics and purchase services retain records according to their configuration, purposes and legal obligations. We retain or use relevant records only as needed to provide features, respond to support requests, maintain purchased entitlements or meet legal obligations. Contact us to request access, correction or deletion, or to withdraw consent. We will verify necessary information and explain what can be acted on. Records that must be kept by law, such as certain transaction records, may not be immediately removable.
Network services use encrypted connections and device data benefits from operating-system protections. No safeguard guarantees absolute security. Protect your device and accounts, and keep backups of important files.
5. Support and international processing
When you email us or submit a website message, we process the address, message and troubleshooting information you provide. Do not send passwords, access tokens or unnecessary private files. Website messages are also subject to the notice displayed when submitting them.
Firebase, RevenueCat, app stores and connected services may process information outside your region. Their policies explain their locations and safeguards. We handle relevant requests and obtain consent where applicable rules require it.
6. Children and changes
The app is not specifically directed to children under 13, or a higher age where local law requires it. Parents or guardians can contact us about inappropriate processing of a child's information.
We update the version and effective date on this page when the policy changes. Material changes or changes requiring fresh consent will be notified or presented for consent as applicable. This policy does not limit your statutory rights.