PlaylistPort · Privacy Policy

This policy applies to PlaylistPort distributed through App Store, provided by Kaka Inc. Other distribution channels have their own versions. Contact [email protected] with privacy questions or rights requests.

1. App features and data use

PlaylistPort is a tool for transferring playlists between supported music services.

When you connect a music service, the app accesses the playlists, track metadata and library information needed for your transfer. The service may also provide profile information such as a display name, avatar or email address to identify the connected account. Authentication credentials and working data are kept on your device; the app connects directly to the music services rather than through a Kaka Inc. backend. To carry out your request, track metadata is sent to the destination music service. Your connected services may include YouTube Music, Spotify, Apple Music, KKBOX and TIDAL, depending on the app version and region.

Music-platform data is used for the transfer and related user-facing features, not for advertising or training machine-learning models. You can revoke access through the connected platform's account settings. The provider's privacy policy also applies to its processing.

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.

The Apple version may also use AdServices to measure Apple Search Ads acquisition. This is separate from using music content for advertising.

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.

7. Google and YouTube user data: sharing and disclosure

This section explains specifically who receives Google user data and why, supplementing the sections above. Features and diagnostics vary by app version and distribution channel; the descriptions below apply when the relevant feature is available and you use it.

Data accessed and purpose

PlaylistPort uses YouTube API Services for supported YouTube Music transfers. When you connect Google, the app processes authorization credentials and the account information Google supplies, such as your account identifier, display name, email address and profile image. For transfers from YouTube, it reads the playlists and music items you select, including playlist names, descriptions, video identifiers, titles, channel or artist information, thumbnails and related metadata, to display your library and match tracks.

For transfers to YouTube Music, the app requests https://www.googleapis.com/auth/youtube.force-ssl to create playlists and add the matched videos you confirm. The current destination flow creates private playlists. This permission is used for the transfer features you request, not to upload or delete your videos or manage comments. Transferring a playlist transfers references and metadata; it does not download or transfer the audio or video files.

Who receives data

• Google / YouTube: the app sends authorization credentials to Google and sends search terms, the playlist name and description, and matched video identifiers to YouTube to find music, create the requested playlist and add its items. These requests go directly from your device to Google's services. Google processes this information under the Google Privacy Policy.
• The music service or server you select as the destination: when YouTube is your source, the app sends the necessary track-matching terms and the playlist name, description and matched destination-track identifiers to your chosen provider to complete your transfer. Supported destinations may include Apple Music (Apple), TIDAL, KKBOX, SoundCloud, and a Subsonic-compatible server you specify, depending on the version. The recipient is the provider you select, or the operator of your specified server; the app does not send the same transfer to all of them. Google access tokens, refresh tokens and Google account passwords are not shared with these destination providers. Each destination handles the resulting playlist under its own privacy policy and account settings.
• Google Firebase Analytics and Crashlytics: these services receive app/device information and usage or diagnostic events to help us understand and improve transfer reliability. Events can include source and destination service names, import method, whether a liked-music collection was selected, track and match counts, duration, success/failure categories and an operation identifier. In versions offering optional link diagnostics, only after your separate agreement, a sanitized public playlist URL may also be sent to Firebase, including a public YouTube playlist URL; sensitive URL parameters are removed. Our analytics and purchase integrations do not send Google OAuth access or refresh tokens, private playlist contents, or lists of individual track titles and artists to Firebase or RevenueCat. See Firebase privacy and security.
• RevenueCat: where integrated, RevenueCat receives purchase and subscription information and app identifiers to manage paid features. Some Apple versions also send a Firebase app-instance identifier and Apple AdServices attribution token for purchase attribution. These are separate from Google OAuth credentials and music-library contents. See RevenueCat's Privacy Policy.
• Kaka Inc. support: if you choose to contact us, we receive the email, message and Google-related troubleshooting information you decide to provide. Our team accesses that information to answer your request; it has no routine access to the Google music library stored on your device. Do not send passwords or authorization tokens.

Limits on sharing and use

We do not sell Google user data, disclose it to data brokers, use it for advertising or credit decisions, or use it to train generalized AI or machine-learning models. We limit its use and sharing to the user-facing functions and support described here. Any exceptional disclosure to relevant authorities or security responders must be necessary to comply with applicable law or address security or abuse, and limited to information we actually hold. A transfer in connection with a business acquisition would require your prior explicit consent where required by Google's Limited Use rules.

PlaylistPort's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. This commitment also applies to information derived from that data.

Storage, revocation and deletion

Authorization credentials are managed on your device, including secure storage managed by the Google sign-in SDK where used. Transfer working data and locally retained app data remain on your device; we do not route your Google music library through our own application backend. The third parties named above separately process the information they receive for the stated purposes.

You can sign out of the connected account in the app and revoke PlaylistPort's Google access in Google account connections. Signing out and revoking Google authorization are different actions. Manage local app data on your device; signing out or uninstalling may not remove every saved record or system backup. Revocation or local deletion does not delete playlists already created in YouTube or another destination; manage those in the respective service. Contact [email protected] to ask about or request deletion of Google-related information held by us, including support records. We will explain the applicable deletion steps and identify records controlled by the relevant provider.