Our privacy commitment
We do not sell, rent, trade, or monetize your personal information, your music files, your listening history, or data accessed through Google Drive. Nebula uses access only to provide the music features you choose. Library metadata, artwork, caches, and listening statistics may be stored locally on your device; optional online services still require technical requests as described in Section 6. We do not claim that an internet-connected app transmits no data at all.
1. Introduction
Nebula – Music Player ("Nebula", "the App", "we", or "us") is an Android music player designed to help you organize and play audio stored on your device and, when you choose to connect it, music from your Google Drive.
This Privacy Policy describes the information the App may access, how that information is used, where it may be stored, and the choices available to you. The Google Drive connection is optional; local music playback does not require you to connect a Google account.
2. Local music and device data
With the permissions you grant, Nebula may read supported audio files on your device and associated information such as song titles, artists, albums, cover art, lyrics, file paths, track numbers, and audio properties. This information is used to build your library and provide music playback and related features.
Nebula may keep a local database of your music library, favorites, playlists, playback queue, and app preferences so that the App can operate efficiently. Local audio files are not automatically uploaded to a Nebula-operated cloud service as part of ordinary offline playback.
3. Optional Google account connection
If you choose to connect Google Drive, Google handles the sign-in and authorization process. Depending on the permissions you grant, Nebula may receive your Google account name, email address, profile picture, and authorization information. These details are used to show and manage the connected account in the App.
Nebula does not ask for your Google account password. Google presents the permissions requested by the App before you approve access.
4. Google Drive data: access and use
Nebula requests read-only Google Drive access to support its optional cloud music library. Read-only permission can potentially allow the App to view information about files beyond audio files, depending on the scope approved on Google’s consent screen. Nebula is intended to use this access only to discover, organize, read metadata from, and stream supported music files.
The data accessed for this feature may include folder names and structure, file names, file identifiers, file types, sizes, supported audio content, embedded artwork, lyrics, and track metadata. This data is used to display and play your Drive music collection; it is not used to edit, move, or delete your Google Drive files.
Nebula may temporarily cache metadata, compressed album artwork, file indexes, and portions of streamed audio on your device to improve browsing and playback while your Google Drive account is connected. When you log out, your connected Google Drive library is no longer available through that session. If you reconnect, Nebula requests authorization again and rescans your Drive music library, including relevant artwork and metadata. Rescanning does not, by itself, establish that every previously cached file has been deleted. Disconnecting does not delete or modify the original files in your Google Drive.
5. Listening history and personal statistics
To provide features such as recently played songs, most-played tracks, listening time, and top genres, Nebula may keep playback history and listening statistics locally on your device. This information is used to personalize your library and display listening insights inside the App.
Your favorites, playlists, playback preferences, and listening history may remain in the App’s local storage until you clear the data or uninstall the App, subject to Android backup and restore behavior.
6. Third-party services and external requests
Music information and artwork. To display additional artist information, biographies, images, and music details, Nebula may search public music information sources. The app includes integrations or lookup logic involving Last.fm, Deezer, MusicBrainz, Wikipedia, and public Spotify-related pages; some lookups may use Google Search to locate a public artist page. The service used depends on the available information and the feature being used. These services are not used to sell or trade your music library or personal information.
Information involved in lookups. For example, a request may include an artist name, a song or album title, a music identifier, or a search query needed to find the relevant public metadata. Providers may also receive standard connection information, such as your device's public IP address, and process it under their own privacy policies. Such lookups are different from selling personal information. Routine music metadata searches do not require uploading a complete audio file, a Google account password, or a Google Drive OAuth access token.
Google Drive and third-party lookups. If a lookup uses music information obtained through the optional Google Drive feature, the search term may be derived from the associated file's artist, album, or track metadata. A metadata service does not thereby receive authorization to browse your Google Drive. Any use or transfer of information obtained through Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. Google Drive access remains optional.
On-device translation using Google ML Kit. Nebula uses Google ML Kit's on-device translation technology for supported language features. If a required language model is not installed, ML Kit may connect to Google to download it. Translation processing takes place on the device. According to Google's ML Kit Android data disclosure, the SDK collects technical information for diagnostics and usage analytics, which may include device and app information, installation-related identifiers, performance and error metrics, SDK feature events, and configured source and destination languages. Google states that the data described in its ML Kit disclosure is encrypted in transit and is not transferred by ML Kit to third parties.
Caching and other connections. Nebula may retain downloaded artist artwork and metadata in local app storage to speed up loading. Its optional Google Drive feature communicates with Google's services for authorization, file listing, and streaming. The app may also contact GitHub Releases to check for available updates. The external services receiving requests may process network connection data according to their own policies.
No sale of personal data. Nebula does not sell, rent, or trade users' music files, listening histories, account information, or personal data to metadata providers, advertising networks, data brokers, or other parties. Necessary requests made to display public music information or to operate a feature are not sales of personal data.
For more information about the providers' practices, see Last.fm Privacy Policy, Google ML Kit Data Disclosure, Google Privacy Policy, and Google API Services User Data Policy.
7. No selling or monetizing your data
We do not sell, rent, license, trade, or share your personal information with data brokers, advertisers, or information resellers for their own commercial purposes. We do not use your Google account information, Google Drive files, local music collection, playlists, or listening history for targeted advertising, marketing profiles, or the sale of user data.
Nebula is designed to process your music library and listening history on your device, rather than upload that information to a developer-operated server for unrelated collection or analysis. Connecting Google Drive lets the App request the music files and metadata needed to show and play your collection. Accessing data inside the App for a feature is different from collecting it on a developer-controlled server.
Nebula’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide or improve the prominent, user-facing features you authorize. We do not permit routine human review of private Drive content.
Necessary service communications are not data sales. Google receives requests needed for account authorization and Drive access; providers of optional artwork or artist metadata may receive search terms and ordinary connection details, as explained in Section 6. Other disclosures, if any, are limited to what is necessary for a feature you select, for security, to comply with law, or as otherwise permitted by Google’s Limited Use requirements. We do not provide your private Google Drive file content to advertising networks or data brokers.
8. Security
Nebula is designed to use Google’s official authorization mechanisms rather than asking you to enter your Google password inside an embedded sign-in page. Communication with Google APIs uses encrypted connections, and the App is intended to handle locally retained authorization information and cached data using appropriate Android security mechanisms.
We aim to minimize data access and limit it to the features you choose. However, no application, device, internet connection, or storage system can be guaranteed 100% secure. Please protect your device and Google account, and review connected-app permissions regularly.
9. Retention, disconnecting, and deletion
Disconnecting Google Drive. When you choose Logout or Disconnect for a connected Google account in Nebula, the App disconnects the account from its active Google Drive session and no longer shows that account as connected in the App. If you decide to reconnect, Nebula asks you to grant Google Drive permissions again. You can independently review or revoke any remaining Google permissions in your Google Account settings.
Connecting again and locally stored data. When you connect again, Nebula rescans your Google Drive music library and reloads relevant album artwork, artist information, and metadata. The need to rescan does not necessarily mean that all previous cached audio, images, or metadata have been erased from device storage. Any remaining app data can be removed using the Android storage controls described below. Disconnecting through Nebula does not delete, edit, or otherwise change the original files in your Google Drive account.
Your local music stays intact. Disconnecting Google Drive does not delete audio files stored on your device or your offline music library. Other local app information, such as playback preferences, listening statistics, and settings, may remain while Nebula is installed. You can remove remaining local app data through Android Settings → Apps → Nebula → Storage & cache → Clear storage, or by uninstalling the App. Android backup and restore settings may affect whether certain app data can be restored.
Independent permission management. You can also review or revoke any applicable connection at Google Account → Third-party connections. Revoking access through your Google Account prevents further use of that Google authorization grant, but does not by itself erase local copies previously stored on your device. For questions or privacy-related requests, contact the developer using the details below.
10. Your choices and permissions
You can use local playback without signing in to Google, decline optional Google Drive access, disconnect your Google account from Nebula, or manage Android media permissions. Logging out disconnects the Google Drive session; reconnecting requires authorization and a new library scan, as described in Section 9. This does not guarantee that every previously stored cache file has been erased. Changing a permission independently through Android or your Google Account may limit the related feature but does not automatically erase unrelated local app data.
You may also manage app storage, notifications, and supported background activity through Android system settings.
11. Children’s privacy
Nebula is a general-purpose music player and is not designed specifically for children under 13. We do not intentionally ask children to submit personal information directly to us. If you believe information has been handled inappropriately, please contact us.
12. Changes to this Privacy Policy
We may update this Privacy Policy if the App’s features, data practices, or applicable requirements change. The revised policy will be posted on this page with an updated effective date. If a material change affects how Google user data is used, we will provide any additional notice or consent required before using that data for the new purpose.
13. Developer and privacy contact
Application: Nebula – Music Player
Developer: Nebula Music Player
Privacy contact: nebulamusicplayer@gmail.com
For privacy questions, access concerns, or deletion requests, please use the privacy contact above.