Privacy Policy

Summary

Muzica does not require a Muzica account to listen. If you sign in, we store your email and a backup of your library on our servers so it can follow you to another device. You can delete that account in Settings; we then remove it and the backup from our servers and wipe the library on this device. Claimed invitation records are retained to prevent repeat rewards. If you connect YouTube, we temporarily read your YouTube playlists so you can copy the ones you pick into Muzica. We do not sell Google user data, use it for advertising, or keep a copy of your YouTube account on our servers after the import session expires. If you forward Telegram audio to @MuzicaImportBot, we temporarily store only song metadata (not audio files) so you can find matching tracks and create a Muzica playlist. If you allow Music library access on iPhone, we read only playlist metadata you select so you can find matching Muzica tracks; we do not download or store Apple Music audio. Optional custom playlist cover images stay in local app storage and are not uploaded, backed up by Muzica, or included in shared playlist links.

Collaborative playlists

When you choose to collaborate, we store the playlist title, song metadata, edit identifiers, membership and expiring invitation links on our servers. Accepted collaborators can add, remove and reorder songs. We display a listener name derived from the part of your email before @; your full email address and account credentials are not shown to collaborators. Uploaded playlist cover images remain private on your device.

Anyone with a valid invite link can see its playlist name and song-derived cover in the link preview, and request to join after signing in. Messaging services may cache these previews. Uploaded personal covers are never included. Invitations expire after seven days. Owners can replace links, remove collaborators or stop collaboration; others can leave at any time. Removing a collaborator also revokes existing invite links. Owners deleting a shared playlist or their account remove that shared playlist for everyone. We retain the owner's original private playlist snapshot as a recovery copy until the account is deleted. Offline edits stay on the device and sync after reconnecting, subject to current access permissions.

Invitations

If you use an invitation code, we record who invited you and which UTC days you use the app to grant referral rewards. Claimed invitation records, including the signup email and reward status, are retained after account deletion to prevent repeat rewards.

How Muzica uses Google user data

Connecting YouTube is optional. When you tap “Connect YouTube” in the App, Muzica asks Google for read-only access with the OAuth scope https://www.googleapis.com/auth/youtube.readonly (YouTube Data API v3). We do not request permission to change, delete, or upload anything on your YouTube account.

The Google user data we access is limited to:

• Your YouTube playlist list, including private playlists you own
• Playlist metadata such as playlist ID, title, channel name, thumbnail URL, and item count
• Playlist items such as video IDs, titles, channel names, thumbnails, and video descriptions
• Your Liked videos playlist, if YouTube makes it available to the App
• A short-lived OAuth access token used only to complete that import

We use that Google user data only to:

• Show you your YouTube playlists so you can choose which ones to copy
• Copy the playlists you select into your local Muzica library (title and track list: video ID, title, artist/channel, and thumbnail)
• Filter out items that do not look like music before they are copied into Muzica

Video descriptions are used only on our servers during that import to help decide whether an item is music. We do not store descriptions after the import finishes.

We do not use Google user data for advertising, retargeting, analytics products, credit decisions, sale to data brokers, or training independent AI/ML models. Muzica’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Sharing, transfer, and disclosure of Google user data

We do not sell Google user data. We do not share, transfer, or disclose Google user data to third parties for their own purposes, including advertisers, advertising platforms, data brokers, analytics companies, or other apps.

We only disclose Google user data in these limited cases:

• Google. We send OAuth and YouTube Data API requests to Google so we can list and copy the playlists you choose.
• You, on your device. After you confirm an import, a copy of the selected playlist titles and track metadata is stored in the App on your device. That copy is yours to play, edit, or delete in Muzica. It is not uploaded to other users.
• Infrastructure service providers. Our cloud hosting provider may process Google user data solely as our processor, on our servers, only to operate the YouTube import feature, and not for their independent use.
• Legal or security needs. We may disclose data if required by law, legal process, or to investigate abuse or a security incident.
• Business transfer. If Muzica is merged, acquired, or sold, Google user data would be transferred only with your explicit prior consent, as required by Google’s Limited Use rules.

We do not allow humans to read Google user data unless you give affirmative consent to review specific data, it is necessary for security (for example investigating abuse), it is required by law, or the data is aggregated for internal operations in a way that does not identify you.

Data protection for Google user data and other sensitive data

YouTube playlist contents and OAuth credentials are treated as sensitive. We take the following measures to protect them against unauthorized access, use, loss, alteration, or disclosure:

• Encryption in transit. All Google OAuth, YouTube API, and App-to-server traffic uses HTTPS/TLS.
• Least privilege. We request only read-only YouTube access. We do not request write, delete, upload, or YouTube account management scopes.
• No long-lived Google login. We use access_type=online and do not request or store Google refresh tokens. You must connect YouTube again the next time you import.
• Short-lived tokens. The access token is kept only in server memory for about 10 minutes, then deleted automatically. It is not written to a database, disk, logs, or backups.
• PKCE. The OAuth code exchange uses Proof Key for Code Exchange (S256). The OAuth client secret stays on the server and is not shipped in the App.
• Session controls. Import sessions are random, single-use identifiers with automatic expiry. OAuth and import endpoints are rate-limited.
• No persistent YouTube library on our servers. After the session expires, we do not keep your YouTube playlists, tokens, or Google account identifiers on our servers. Imported copies remain only on your device until you delete them or uninstall the App.

You can revoke Muzica’s access at any time in your Google Account permissions. You can also delete imported playlists inside the App, or clear app storage / uninstall Muzica to remove local copies.

Telegram song import (@MuzicaImportBot)

Importing from Telegram is optional and starts only when you choose to message the Muzica import bot on Telegram (a third-party messaging service operated by Telegram Messenger Inc.). You voluntarily forward audio messages or audio files to @MuzicaImportBot.

Muzica does not download, host, or store Telegram audio files. The bot reads only the metadata needed to search for matching songs in Muzica, which may include:

• Song title
• Artist / performer
• Filename
• Caption text, when needed to parse title or artist

While you are building an import, that metadata is stored in a temporary import session on Muzica’s servers, together with a Telegram chat identifier used only to keep your session tied to that bot chat. Sessions expire automatically after 24 hours. After you finish in the bot and successfully create a playlist in Muzica, the session is marked consumed and can no longer be reused. You can also clear an in-progress import in the bot before finishing.

We use this metadata only to find matching songs in Muzica’s catalog and to help you create a Muzica playlist. We do not use it for advertising, sell it, or share it with other users. Telegram’s own handling of messages you send is governed by Telegram’s privacy policy; Muzica only receives what you forward to the import bot.

Apple Music / Music Library playlist import

Importing from Apple Music is optional and available on iPhone. It starts only when you choose Apple Music playlist in Library and explicitly grant Music library access through Apple’s system permission prompt (NSAppleMusicUsageDescription).

After you allow access, you manually choose a playlist from your on-device Music library. Muzica uses Apple’s official MediaPlayer APIs to read only the metadata needed for import, which may include:

• Playlist name
• Song title
• Artist
• Artwork, when available, for temporary display during import

Muzica does not download, copy, upload, store, or play Apple Music audio files. Playback in Muzica continues to use Muzica’s existing catalog. Title and artist are used only to search for matching Muzica tracks when you tap Find songs, and to help you create or add to a Muzica playlist. Temporary Apple artwork shown during import is replaced by Muzica catalog artwork for matched tracks and is not kept as the permanent cover for imported songs. There is no background syncing with Apple Music.

This metadata is read on your device. We do not upload your Apple Music library to Muzica’s servers. You can revoke Music access anytime in iOS Settings, and you can delete imported playlists inside the App.

Muzica accounts

Signing in is optional. If you sign in with email, we store on our servers:

• Your email address
• A backup of your playlists, On repeat, and recently played
• Shared playlist links you create, until you delete the account
• Short-lived sign-in codes, which expire and are then deleted

In the App, open Settings and tap Delete account. That permanently deletes the account row and the data above from our servers, including shared playlist links. It also wipes the matching library, listening history, identification history, and offline downloads on this device. We do not keep a copy for recovery. Signing in later with the same email creates a new, empty account.

Public SoundCloud playlist import

If you choose to import a public SoundCloud playlist, Muzica opens SoundCloud’s embedded widget to read the available song titles, artists, artwork, and durations. Your playlist link and ordinary connection information, such as your IP address, are sent to SoundCloud to load its public content. SoundCloud handles these requests under its Privacy Policy.

This feature does not connect your SoundCloud account or access private playlists. Muzica does not download SoundCloud audio. When you choose Find songs, the selected song metadata is used to search Muzica’s catalog. You can review the matches before saving. Saved playlists follow the library backup and sharing choices described in this policy.

Private playlist cover images

Choosing a custom playlist cover is optional. Open a playlist’s options, choose Change cover, and select one image through the system Photos or Files picker. Muzica receives the image you select; it does not browse or scan your photo library. No camera or microphone access is needed for this feature, and you can continue using the App without choosing a photo.

The selected image is processed on your device into a square, compressed cover, up to 1024 × 1024 pixels and 2 MB. Muzica keeps one cover per playlist in local app storage, separately from the playlist’s song metadata. It may appear in your own playlist views and on your connected CarPlay display. Muzica does not upload these cover images to its servers or send them to advertising, analytics, or image-processing services.

Custom cover images are excluded from Muzica’s library backup and from shared playlist links and previews. When you share a playlist, its public artwork is generated from the most recently added songs instead of your selected image. Your device’s own backup settings may apply to locally stored app files.

To remove your selected cover, open the playlist’s options and choose Use default cover. Replacing a cover removes the old stored copy. Removing the playlist from your library, resetting the library, or deleting your Muzica account also removes its local cover. This does not delete or change the original photo in Photos or Files.

Information stored on your device

The App may store the following locally on your device:

• Personal playlists you create and tracks you add to them
• Optional private playlist cover images you select
• Copies of YouTube playlists you choose to import
• Playlists you create from Telegram import metadata (on your device after you confirm the import)
• Recently played tracks
• Playback session state (for example, current queue)
• Optional app settings related to music catalog access
• Temporary cached audio files used for playback

Local copies remain until you remove them through the App or your device settings, delete your account in Settings, or uninstall the App. If you sign in, playlist and listening metadata is also backed up as described above. Private cover images are excluded from Muzica’s server backups and playlist sharing.

Network requests and third parties

To search for music and stream audio, the App sends requests to third-party music catalog and media services. Those requests may include search terms, playlist or track identifiers, and standard technical information such as IP address and device/user-agent details processed by those providers.

YouTube import is separate from general catalog search. Catalog search does not use your Google account. YouTube import uses Google user data only as described in the Google user data sections above.

Telegram import is also separate from catalog search. It uses only the metadata you voluntarily forward to @MuzicaImportBot, as described in the Telegram song import section above. Telegram is a third-party service; Muzica does not require Telegram account login inside the App.

Apple Music / Music Library import is also separate from catalog search. It uses Apple’s official on-device MediaPlayer APIs after you grant Music access, and only for playlists you choose, as described in the Apple Music import section above. Title and artist may be sent as search terms to Muzica’s existing catalog search when you tap Find songs. Muzica does not use undocumented Apple Music endpoints and does not download Apple Music audio.

We do not control the privacy practices of third-party services. Their handling of data is governed by their own policies.

Analytics and advertising

The App does not include third-party analytics SDKs or advertising SDKs for the purpose of tracking you across apps or websites.

Children’s privacy

Muzica is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information through support channels, email support@muzica.app and we will take appropriate steps.

Your choices

• Delete your Muzica account in Settings. This removes it and the backed-up library from our servers and wipes that library on this device
• Delete personal playlists and library items inside the App, including copies imported from YouTube, created from Telegram import, or created from Apple Music import
• Clear an in-progress Telegram import in @MuzicaImportBot, or wait for the 24-hour session expiry
• Remove a private cover using the playlist’s Use default cover option; this leaves your original photo unchanged
• Revoke Music library access for Muzica in iOS Settings
• Revoke YouTube access in your Google Account permissions
• Clear app storage or uninstall the App to remove remaining local data such as theme preference
• Email support@muzica.app with privacy questions or if you cannot use the in-app deletion control

Data deletion

You can delete your Muzica data at any time, and you do not need to give a reason. What is removed depends on whether you signed in: a signed-in account has a backup on our servers, while signed-out use keeps everything on your device only.

Signed-in accounts — delete in the App:

• Open Settings and tap Delete account, then confirm.
• We immediately and permanently delete from our servers the account record (your email address), the backup of your playlists, On repeat and recently played, the shared playlist links you created, any pending sign-in codes, and any problem reports linked to that account.
• The same action wipes the matching data on this device: your library, listening history, identification history, offline downloads, suggestion caches, and the account and sign-in keys.
• Deletion is immediate and permanent. We keep no copy for recovery, and signing in later with the same email creates a new, empty account.

If you cannot use the in-app control (for example you cannot sign in, the account is suspended, or you only used the App signed out), email support@muzica.app with the subject “Data deletion request”. Send it from, or include, the email address of the account. We reply to confirm the request and complete the deletion within 30 days. Never send your password or a sign-in code.

Signed-out use:

• With no account, your playlists, listening history, downloads, and settings exist only on your device and are never uploaded to us.
• Uninstalling Muzica, or clearing its storage in your device settings, removes all of it. No request to us is needed.

Other data and retention:

• Google / YouTube. We do not keep your YouTube playlists or Google account after the import session ends; the OAuth access token lives in server memory for about 10 minutes. You can revoke access at any time in your Google Account permissions.
• Telegram import. An in-progress @MuzicaImportBot session (song metadata plus the Telegram chat identifier) is deleted automatically after 24 hours, or immediately when you clear it in the bot.
• Apple Music. Playlist metadata is read on your device and is not uploaded to us; revoke Music access in iOS Settings.
• Support and security records. Emails you send to support may be kept while your request is handled and for a limited period afterwards for legal or abuse-prevention reasons. Server and rate-limiting logs are kept for a short time and do not contain your playlists or listening history.

If any part of your data is still not deletable through the options above, or you have questions, contact support@muzica.app and we will delete it for you.

Contact

For privacy questions, email support@muzica.app or use the Muzica App Store listing.

Changes

We may update this Privacy Policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the App after updates means you accept the revised policy.