SimpMusic Wear OS privacy notice

Effective October 20, 2026. This notice covers the SimpMusic Wear OS watch app and lightweight Android companion, version 0.3.0-beta.1, maintained by Rahyan. The optional full SimpMusic phone app and the Face-Off website are separate from these two applications.

Information stored on your devices

The watch stores your settings, local library, playlists, playback history, cached artwork and lyrics, and downloaded music. The companion stores its settings, saved watch playback/status information and local diagnostic messages.

Sign-in is optional. If you sign in through the companion’s Google/YouTube Music web page, the companion saves the resulting YouTube session cookie and can send it to the watch over the Wear OS Data Layer. The watch stores that session and account information returned by YouTube, including the account name, email address, profile image URL and account/channel identifiers. These values let it make authenticated requests and show the selected account. The watch also keeps a session-cookie file in its private files directory for its extraction code.

Session values are sensitive credentials. They are stored in Android app-private preferences, databases or files. These apps do not add a separate application-level encryption layer to that storage. Their manifests disable Android app-data backup and exclude their data from Android cloud backup and device transfer.

After a successful phone sign-in, the sign-in view clears its WebView cookies, web storage, cache and history. The app retains the saved session needed for later use. Signing in does not create a Face-Off account.

Requests to music and lyrics services

Online features send requests from your devices to the services providing them. Those services receive connection information such as your IP address, along with the data needed for the request.

Proxy stream fallback is enabled by default. It can be disabled in the watch’s Accounts screen under Proxy stream fallback. A fallback request sends the video identifier to an independently operated Piped instance; it does not attach the Google sign-in cookie. Proxy operators and returned media hosts receive the requests you make to them. If a separate network proxy has been configured, requests routed through it also use that connection.

If a cloud translation API key has been configured, the LRCLIB lyrics path can send the fetched lyric text and target language to the selected translation provider, Google Gemini or OpenAI. The configured API key authenticates that request. Without a configured key, that translation service is not initialized. The lightweight companion does not provide a translation-key setup screen.

These providers operate independently of the fork’s maintainer. Their handling and retention of requests are governed by their own services and policies. Guest mode avoids saving a signed-in account session; it does not prevent the services used for browsing or playback from receiving network requests.

Playback reporting and diagnostics

The watch has a Send watch-time to Google setting. It is off by default. When enabled and YouTube supplies the corresponding playback endpoints, the player can send playback/watch-time updates and playback identifiers back to YouTube. You can turn it off in Accounts. Searches, streaming and account requests still contact Google/YouTube regardless of this setting.

The watch keeps bounded local diagnostic logs, and the companion keeps local status/log messages. The watch’s logger filters credential-related messages and removes full URLs, but diagnostics can still describe playback activity or errors. Neither the watch app nor the lightweight companion configures an automatic remote crash-report uploader or a separate usage-analytics service. This does not describe telemetry collected independently by Android, Google Play services or the online providers you use.

Opening source, download or support links visits GitHub, which handles those visits under its own policies. If you submit a bug report, the information you choose to post is shared on GitHub. Do not include session cookies, passwords, access tokens, account databases or unredacted diagnostic files.

Your choices and deletion

You can use guest playback, choose lyrics providers, disable proxy stream fallback and control SponsorBlock and watch-time reporting. Some provider options require a previously configured account or settings from a compatible phone build.

Use the companion’s Sign out on phone & watch action while the selected watch is reachable to clear both apps’ saved YouTube sessions. If no watch is selected, the companion clears its own session. Watch sign-out also clears the watch’s saved account/session state and private cookie export. App sign-out does not revoke Google sessions on other devices and does not delete downloaded music or local library/history records.

Remove downloads through the watch’s download controls. The companion offers a clear-log action for its local messages. Clearing an app’s Android storage or uninstalling it removes that app’s local data. The watch and phone keep separate storage, so clearing one does not clear the other. Data already sent to Google, lyrics services or other providers is handled by those providers; clearing local storage does not delete their records.

Contact and changes

Source code and release details: https://github.com/Rahyan/SimpMusic-WearOS

Privacy questions and support: https://github.com/Rahyan/SimpMusic-WearOS/issues/new/choose

GitHub issues are public. Describe your concern without posting credentials or private account information. This notice will be updated when the app’s data handling changes.