Privacy Commitment

Privacy First, Period.

VIVI Music is built from the ground up to respect your privacy. No trackers. No collection. Just your music.

verified_user

100% Auditable & Transparent

Our codebase is fully public and open source. Anyone can check the code to verify that no tracking, analytics, or hidden background processes exist in the application.

database_off

Zero Data Collection

VIVI Music does **not** collect, store, or transmit any personal data.

  • close No account creation or login required to use the app.
  • close No search logs, playback history, or playlists are sent to our servers.
  • close No third-party advertising, analytics, or telemetry scripts are integrated.
visibility

Public Source Code

We believe trust is built through complete transparency. The entire development history and source code for VIVI Music is completely public and hosted on GitHub.

You can verify every commit, audit our dependencies, or compile the application yourself to ensure there are no privacy or security issues:

cell_tower

External Network Connections

To stream and retrieve audio tracks, VIVI Music connects directly to public YouTube Music streaming endpoints. These connections are made **locally** from your device to Google servers.

No middleman servers or proprietary relays are utilized in this connection. The application interacts with these external platforms only as much as necessary to play your selected streams, and is subject to Google's standard privacy policies.

key

Local Storage & Permissions

All app preferences, downloaded audio cache, custom playlists, and system configurations are saved strictly inside the application's isolated sandboxed storage directory on your physical device.

The app only requests standard Android device permissions (like internet access for streaming, background service playback, and standard local directory storage checks) required to play and manage audio correctly.

alternate_email

Contact & Support

If you have any questions, concerns, or find any potential security issues in the codebase, we welcome you to open a public issue or reach out via email: