Effective Date: August 6, 2026
Last Updated: August 6, 2026
This Privacy Policy explains how PixelPlayer (the "App"), including its companion Wear OS app, accesses, uses, stores, and transfers information. PixelPlayer is developed and maintained by Theo Vilardo (the "Developer").
PixelPlayer is a local-first music player. The Developer does not operate a PixelPlayer account system, advertising platform, analytics backend, or cloud database containing your music library. Most information remains strictly on your devices. Information leaves a device only when required by a feature you choose to use, by a connected third-party service, or by the Google Cast SDK as detailed below.
Depending on the features you choose to use, PixelPlayer may access or create:
Audio Files & Metadata: Audio files and associated metadata, including titles, artists, albums, genres, durations, file paths, and embedded artwork.
Selected Images: Artwork or image files you select via Android's system photo picker.
Library & App Data: Playlists, favorites, playback queue, listening history and statistics, search history, bookmarks, lyrics, equalizer settings, BPM or song analysis data, and user preferences.
Cached Content: Locally cached lyrics, artwork, cloud-library metadata, AI responses, and offline copies of cloud or watch content.
Backups: Backup archives that you explicitly create.
Service Credentials: Account identifiers, profile details, credentials, tokens, server addresses, and API keys for optional services you connect.
This information is used exclusively to provide core functionality, including playback, library organization, search, personalization, lyrics display, metadata editing, backup/restore, casting, watch synchronization, and cloud playback. Local information is never sent to the Developer.
PixelPlayer may request the following system permissions as needed:
Music and Audio / Storage: Required to discover, play, edit, organize, and transfer audio files. (Legacy storage permissions are requested on older Android versions).
Selected Photos: Uses Android's native system Photo Picker when you choose custom artwork. PixelPlayer does not request broad access to your photo library.
Nearby Devices, Bluetooth & Wi-Fi State: Used to discover and connect to audio outputs, Cast devices, and nearby Wear OS devices. On Android 11 and earlier, location permission may be required by the OS for Bluetooth or Wi-Fi discovery. PixelPlayer does not use this permission to track, store, or transmit your physical location.
Notifications & Foreground Services: Required to display media controls, playback status, and active transfer progress.
Modify System Settings: Requested only if you explicitly choose to set an audio file as a system ringtone or notification sound.
Battery Optimization Exemption & Wake Lock: Supports uninterrupted background media playback when explicitly allowed.
You can review or revoke these permissions at any time in your device's Android Settings. Revoking permissions may disable the associated features.
LRCLIB (lrclib.net): When remote lyrics are fetched, song metadata (title, artist, album, duration) is sent to LRCLIB.
Deezer API (api.deezer.com): When remote artist artwork is requested, the artist name is sent to Deezer.
GitHub (github.com & raw.githubusercontent.com): Fetches public contributor and announcement data. Standard network info (such as your IP address) is visible to these hosts during network requests.
AI integration is strictly optional. Local NLP processing runs entirely on your device. If you enable an online AI provider:
PixelPlayer sends your prompt, configured system instructions, relevant music library context, and your user-provided API key directly to the chosen provider.
Supported Providers: Google Gemini, DeepSeek, Groq, Mistral AI, NVIDIA NIM, Moonshot/Kimi, Zhipu GLM, OpenAI, and OpenRouter.
Providers process data according to their respective privacy policies and terms. Do not send content you do not wish third-party AI models to process.
API keys are stored in app-private storage and excluded from Android Cloud Backups. You can delete API keys or clear local AI cache anytime in the App settings.
When connected via OAuth (drive.file scope):
PixelPlayer accesses basic profile info (display name, email address, profile image) to display account status.
Access is scoped strictly to files created by PixelPlayer or explicitly opened with it.
Media files, artwork, and backup archives are uploaded, downloaded, or streamed only upon user action.
Disconnecting Google Drive clears active authorizations, local profile data, and cached Drive metadata from the device (files stored on Google Drive remain until manually deleted).
Integration uses Telegram's native client library (TDLib):
Phone numbers, verification codes, and 2FA passwords are sent directly to Telegram for authentication.
Accesses channels, topics, message metadata, and audio files required for user-added music sources.
Logging out ends the session. Cached Telegram files and database records can be removed by deleting the source or clearing App storage.
Sends server address, credentials, library queries, and playback requests directly to your self-hosted server.
HTTPS is strongly recommended. Unencrypted HTTP is permitted for local network setups, though unencrypted traffic can be observed by local network third parties.
Disconnecting a server removes cached credentials and synced library data from the device.
Streaming to Cast receivers transfers media metadata, commands, and temporary audio streams over your local network using a temporary HTTP server.
Google Cast SDK Telemetry: The built-in Google Cast SDK automatically collects anonymized diagnostic data (discovery events, session lengths, device/SDK specs). Google states these logs are encrypted in transit, aggregated, and contain no personally identifiable information. SDK telemetry cannot be toggled off by the Developer or user.
Syncs playback state, volume, metadata, artwork, and user-selected audio files to your smartwatch using Google Play Services' Wearable Data Layer.
Purchases and subscriptions are handled by Google Play Billing. PixelPlayer receives transaction status and entitlement tokens to activate features. The Developer never receives or stores payment card information.
The Developer does not sell, rent, or monetize your personal information, nor do we display third-party advertisements.
PixelPlayer contains no advertising SDKs, Firebase Analytics, or Developer-operated tracking trackers. Data is shared exclusively with third-party APIs you intentionally connect or via standard device-to-device transfers (such as Google Cast or Wear OS).
Device Security: PixelPlayer utilizes Android's scoped storage, app-private storage directories, and system Keystore encryption for sensitive credentials.
Backup Exclusions: Credentials, Telegram session files, and AI API keys are explicitly excluded from Android cloud backups.
System Backups: Non-sensitive local app data (like settings and local playlists) may be included in standard Android system backups if enabled on your Google account.
Network Security: Third-party services use TLS/HTTPS encryption. User-hosted local HTTP servers or local Cast streams operate without encryption over local networks.
Because the Developer does not operate a central server, there are no central user records to delete.
Local Data Removal: Go to Android Settings > Apps > PixelPlayer > Storage > Clear Storage (or the equivalent setting on Wear OS) to instantly wipe all local app data.
Third-Party Data: Data stored on Google Drive, Telegram, self-hosted media servers, or AI provider platforms must be managed or deleted through those respective services.
PixelPlayer does not create or manage user accounts. Connecting to third-party services (Google, Telegram, Jellyfin, Navidrome) connects directly to external providers or self-hosted servers. Disconnecting from PixelPlayer does not terminate or delete your underlying account with those external services.
PixelPlayer is a general-audience application and is not intended for or directed toward children under 13 (or the applicable legal age in your jurisdiction). The Developer does not knowingly collect data from children.
This Privacy Policy may be updated to reflect app changes, feature additions, or legal requirements. Updated versions will be published on this page with a revised "Last Updated" date. Significant changes may also be announced in the App's release notes.
If you have questions about this Privacy Policy or data handling in PixelPlayer, you can contact the developer:
Developer: Theo Vilardo
Support Channel: https://t.me/thevelopersupport
Please do not include sensitive information (such as passwords, API keys, or verification codes) in support messages.