PlaylistPortGoogle Play

PlaylistPort · Privacy Policy

This Privacy Policy applies to PlaylistPort for Android distributed through Google Play (package com.PlaylistPort.android), provided by Kaka Inc. It explains what information the app accesses, how it is used and shared, and your choices. Contact [email protected] for privacy questions or requests. The Apple and website editions have separate notices.

1. Playlist transfer and connected accounts

You do not need to create a separate PlaylistPort account. You can provide a playlist link or connect a supported music service. Depending on the feature, we process playlist links, playlist names and descriptions, track and video identifiers, titles, artists or channel names, artwork, durations, library items and liked music. A connected service may provide account identifiers, display names, avatars or email addresses to identify the account you selected.

The app uses this information to read and display playlists, search for corresponding tracks, let you review matches, and create or update the destination playlist you request. A transfer moves references and metadata, not ownership of music or copies of audio or video files. Playback previews, where available, are provided by the relevant service.

Music requests are made from your device to the relevant music service or the server you specify. We do not operate a central PlaylistPort server that receives your music library for these transfers. Track-matching terms and the necessary playlist metadata and destination-track identifiers are shared with the destination you choose, not with every supported platform. Providers process those requests under their own terms and privacy policies.

2. Sign-in, browser sessions and device storage

Connecting a music account may use the provider's authorization page, an installed provider app or an in-app browser. The provider receives information entered on its sign-in page. The app retains authorization tokens and relevant session information on your device so it can perform the functions you request. In-app browser cookies and website storage may keep you signed in; those services may also receive IP addresses, browser/device information and page interactions.

If you connect a personal music server, the app processes the server address and credentials or access token you provide and sends authenticated requests to that server. Use a server you trust. The app does not send one provider's account password or authorization token to a different destination music provider.

Local data can include settings, connection details, cached artwork, playlist working data and transfer history. Clipboard text is used when you choose to paste a playlist link. The app checks whether supported music apps are installed to offer the corresponding opening or authorization flow. It does not require access to your contacts or precise location for playlist transfers.

3. Analytics and crash diagnostics

The Android release integrates Google Firebase Analytics and Crashlytics. They process app-instance or installation identifiers, app and device information, operating-system details, usage events, timestamps and crash or diagnostic information. Firebase may also process network information, including IP addresses, when receiving requests. These services help us understand usage and diagnose reliability problems; identifiers are not necessarily anonymous.

App-specific analytics include onboarding page views and completion. Optional playlist-link diagnostics are off by default. If you enable that option in the app's profile/settings, the current implementation sends only the source-platform name and whether reading succeeded; it does not attach the playlist URL, clipboard text or server error message. Disabling that option stops these optional events, but is not a switch for all Firebase Analytics or Crashlytics collection.

Our custom analytics events do not include music-account access or refresh tokens, private playlist contents, lists of track titles and artists, or account passwords. Google describes SDK processing, retention and controls in Firebase Privacy and Security and its Privacy Policy.

4. Purchases and subscriptions

Where paid features are available, Google Play handles checkout and payments, and RevenueCat validates purchases and manages entitlements. They process relevant app-user identifiers, purchase tokens or transaction records, product identifiers, subscription status and app/device information. PlaylistPort does not receive your complete payment-card details. RevenueCat does not require you to create a separate PlaylistPort login.

These integrations do not require sending your music library or music-service authorization credentials to RevenueCat. See the RevenueCat Privacy Policy and Google Privacy Policy. Prices and purchase conditions are shown before you confirm a purchase.

5. Google and YouTube API data

PlaylistPort uses YouTube API Services for its YouTube Music features. With your authorization, it reads selected playlists, liked music and related video metadata to display your library and match tracks. The Android authorization flow requests https://www.googleapis.com/auth/youtube.force-ssl for supported read and destination-transfer features. The current destination implementation creates private playlists and adds the matched video identifiers you confirm. This permission is not used to upload or delete your videos or manage comments.

Google receives the authorization requests, search terms and playlist data needed to perform those actions. When YouTube is the source, the chosen destination receives the metadata needed for matching and transfer. Destinations can include Apple Music, SoundCloud, TIDAL, KKBOX and a supported personal music server, depending on the version. Google authorization tokens are not passed to those destinations. Firebase receives only the app/diagnostic information described above; RevenueCat receives the purchase information described above.

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. We do not sell Google user data, use it for targeted advertising, provide it to data brokers, or use it to train generalized AI or machine-learning models. These limits also apply to information derived from Google API data.

You can sign out in PlaylistPort and separately revoke its access through Google Account connections. Signing out and revoking authorization are different actions. YouTube use is also subject to the YouTube Terms of Service and the Google Privacy Policy.

6. Retention, deletion and your choices

  • On your device: connection credentials and saved preferences remain until removed by the relevant sign-out/reset action or by clearing the app's storage. Working data and caches may remain until replaced or cleared. In Android Settings, open Apps → PlaylistPort → Storage and clear app data to remove the app's local data, including its in-app browser storage. This resets local settings and connections. Manage any separate device backups through your backup provider.
  • Connected services: revoke access in the provider's account settings. Removing local data or revoking access does not delete playlists you already created on a destination service. Delete those in that service. External browsers and installed music apps manage their own sessions separately.
  • Analytics and diagnostics: Firebase retains information according to its service-specific retention rules and the project's configuration. Contact us to request deletion of identifiable records under our control. We may need limited additional information to locate records; we do not ask for your music-account password or tokens.
  • Purchases: Google Play and RevenueCat retain records to verify entitlements, process renewals/refunds, prevent fraud and meet applicable obligations. Clearing app data or uninstalling does not cancel a subscription or erase store records. Manage subscriptions in Google Play subscriptions.
  • Support: we retain correspondence while needed to handle your request and related follow-up, or to meet legal obligations. You can request deletion by emailing [email protected] with the subject “PlaylistPort Android data deletion”. Identify the information concerned without sending passwords, tokens or unnecessary private data.

You may contact us to request access, correction or deletion, or to exercise other rights available in your location. We will verify only the information needed to handle the request, explain any legal retention requirement, and distinguish records we control from records held by a connected provider. There is no separate PlaylistPort account to delete.

7. Security, support and international processing

We use operating-system protections for local app data and encrypted connections for supported internet services. Personal-server features may allow unencrypted HTTP connections on a local network; use HTTPS where available and avoid untrusted networks. No storage or transmission method guarantees absolute security.

If you contact support, Kaka Inc. receives your email address, message and any attachments or troubleshooting details you choose to send. Our support staff do not routinely have access to the music library on your device. We may disclose information we actually hold when necessary to comply with applicable law or address fraud, abuse or security incidents. Any business transfer involving Google user data remains subject to Google's Limited Use rules.

Google, RevenueCat, music providers and support services may process information outside your country. Their policies explain their processing and safeguards. Applicable privacy rights and required consent are respected.

8. Children and policy changes

PlaylistPort is not specifically directed to children under 13, or a higher minimum age where applicable law requires it. Parents or guardians may contact us about a child's information.

We update this page and its effective date when practices change. Material changes will be communicated, and additional consent obtained where required. This policy does not remove your statutory rights.