Privacy Policy

Last updated:2026-10-17

1. Introduction

Muky ('we,' 'our,' or 'us') is committed to protecting and respecting your privacy. This Privacy Policy explains what data the Muky iOS app and website collect, how it is used, and the rights you have. We collect as little as possible and never sell or share data with advertisers.

2. Information We Collect

The Muky iOS app collects a small amount of pseudonymous usage data (telemetry) to help us understand how features are used and to improve the product. The muky.app website uses a self-hosted, cookieless analytics tool for the same purpose. The details of what is collected - and how to turn the app telemetry off - are described in section 3.

We never collect or transmit:

• Passwords, contacts, photos, microphone input, or precise location.
• IDFA, advertising identifiers, or any cross-app tracking signals - there are no ad SDKs in the app.
• Any data that directly identifies you as a person.

3. Telemetry / Usage Statistics

Muky uses telemetry to understand which features are used and to spot crashes and regressions early. The data is pseudonymous and aggregated; it is never used to build a profile of an individual user.

Self-hosted analytics

We run a self-hosted instance of the open-source analytics tool Aptabase on our own server. No data is shared with Aptabase the company or any other third party. The only sub-processor involved is our hosting provider, Hetzner Online GmbH (Germany / EU).

Legal basis

Processing is based on Art. 6(1)(f) GDPR - our legitimate interest in understanding feature usage in order to improve the product. The data is pseudonymous and aggregated, which keeps the impact on your privacy minimal.

Pseudonymous, daily-rotating ID

Aptabase derives a user identifier on the server as SHA(client IP + User-Agent + daily salt). The raw IP address itself is not stored. The salt rotates every 24 hours, so the same device produces a different hash each day and users cannot be re-identified across days.

How to disable telemetry

Telemetry is on by default. You can disable it at any time in the app under Settings → Disable telemetry. Once turned off, no further events are sent.

What we collect

Event names indicating which actions happen in the app, for example: app_opened, playlist_created, playlist_imported, playlist_visibility_changed, items_added, suggestions_refreshed, suggestion_added, suggestions_toggled, music_service_selected, subscription_loaded, telemetry_enabled, telemetry_disabled, backup_exported, backup_imported, paywall_shown, paywall_dismissed, paywall_plan_selected, purchase_started, purchase_completed, purchase_cancelled, purchase_pending, purchase_failed, restore_completed, offer_code_redeemed, family_upgrade_shown, onboarding_step_completed, onboarding_finished, profile_created, player_opened, player_session_ended, browse_opened, browse_item_added, search_performed, freeze_dance_started, sleep_timer_started, carplay_connected, skip_policy_changed, history_opened, history_cleared, share_extension_added, update_banner_shown, update_banner_tapped, playback_failed, import_failed, music_auth_denied.

Aggregate counts and flags attached to those events, for example:

• Number of playlists, items and profiles in the app.
• Whether freeze dance is enabled, and the count of profiles that use it.
• Days since install, the selected music service, theme preference, and the auto-start flag.
• Whether an audio-player password is set (a boolean only - the password itself is never transmitted or stored on our servers).
• Aggregate buckets per player session: listening time and number of tracks as ranges (for example "5-15 minutes" or "4-10 tracks"), the number of blocked skips and wrong password attempts, and whether the device was offline or connected to CarPlay. No song, playlist or profile names, and nothing from the listening history.
• Plan names (for example monthly, yearly or lifetime), which screen opened the purchase page, whether a free trial is active, and the error code of a failed purchase. The purchase itself is handled by Apple.
• Error codes of failed playback or imports (error type and number, music service, and whether an item is a library or catalog item, never the item itself), how far the installed app is behind an available update (patch, minor or major), and the onboarding step reached.

Website analytics

The muky.app website uses a self-hosted instance of the open-source analytics tool Umami (umami.is), also running on our own Hetzner server in Germany / EU. Umami is cookieless and collects only aggregate, anonymous data: page URL, referrer, browser, operating system, screen size, and country (derived from the IP address - the IP itself is not stored). Visitor identifiers are generated server-side from a hash that rotates daily, so individual visitors cannot be re-identified across days. No data is shared with any third party.

Listening history (stays on your device)

To show parents what their children listen to, the app keeps a listening history on the device: which songs were played, in which playlist, for how long, and whether they were skipped, per profile. This history is stored only locally on your device. It is never sent to us, to telemetry, or to any third party, and it is not part of iCloud sync. It is also excluded from device backups (iCloud and computer backups) and is deleted together with the app. It is only included in a Muky backup file when you export one yourself in the app (you can leave it out), and that file stays wherever you save it. By default entries are deleted automatically after 30 days; in the app under Account → Listening history you can choose 90 days, 1 year or never delete, turn recording off, or delete the history of one profile or all profiles at any time. Deleting a profile also deletes its history. Uninstalling the app removes it entirely.

4. Third-party integrations

Muky can connect to third-party services that you activate yourself. When you do, those services process data under their own privacy policies; we do not receive that data, except where noted below.

• Apple Music / MusicKit - Opens in new tab - used to browse and play music in your Apple Music library. Apple handles authentication and streaming directly.
• Spotify - Opens in new tab - used to browse and play music from Spotify. OAuth tokens are stored only in the iOS Keychain on your device and are never sent to our servers.
• In-app purchases and subscriptions are handled entirely by Apple via StoreKit. We receive only the transaction status needed to unlock features; payment details remain with Apple.
• App Store version check - to tell you when an update is available, Muky asks the Apple App Store for the latest version number at most once a day. The request goes only to Apple and contains the app's bundle ID and your App Store country. It contains no personal data and nothing from your library or listening history.

5. How We Use Your Information

The telemetry described above is used only to operate and improve Muky - for example, to measure how often a feature is used, to find regressions, and to prioritize what to build next. We do not use it for advertising, profiling, or any automated decision-making.

6. Sharing Your Information

We do not sell or rent your data. Telemetry is stored only on our own infrastructure at Hetzner (Germany / EU); it is not forwarded to Aptabase the company or any other third party. Data may be disclosed only where required by law.

7. Data Security

Telemetry is transmitted over HTTPS and stored on servers hosted in the European Union. Access to the analytics database is restricted to the operator. While no system is ever fully secure, we apply reasonable technical and organisational measures to protect the limited data we hold.

8. Your Rights

Under the GDPR you have the following rights with respect to personal data we process:

• Right of access - to obtain confirmation of whether we process data about you and a copy of it.
• Right to rectification - to have inaccurate data corrected.
• Right to erasure - to have your data deleted.
• Right to restriction of processing.
• Right to object to processing based on legitimate interests.
• Right to data portability.
• Right to lodge a complaint with a supervisory authority.

Because telemetry is pseudonymous and there is no user account, we are usually unable to attribute events to an individual. If you would like to exercise any of these rights, please contact us at the address below; we will respond as far as identification of the data is possible.

9. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Material changes will be reflected by an updated 'Last updated' date at the top of this page and, where appropriate, communicated in the app or on this website.

10. Controller and Contact

The controller responsible for the processing described in this Privacy Policy is Oliver Janssen. Full postal contact details are available in the Imprint.

• Email: hi@muky.app