Privacy on your device
Privacy policy
The extension connects browser playback and optional, user-approved tab audio analysis to Dance to Music in your local Phase Pal desktop app.
This policy covers the Music Bridge extension and its local native-message data path. It does not cover every feature of the separate Phase Pal app, Chrome, music services, or GitHub. Their privacy practices apply separately.
What the extension accesses
- Playback information: playing/paused state on the supported music-player hosts and on custom sites you explicitly approve. It checks whether title, artist and timeline metadata exists, and may read explicit MediaSession playback state. Actual title and artist text stays in the page.
- Local tab information: tab addresses identify supported sites; local tab IDs select the playback source. The extension does not read Chrome's browsing-history database.
- Optional tab audio: after the popup capture action, the selected tab's audio is processed in extension memory to estimate energy, tempo, beat timing, confidence and section intensity. This can include speech, podcasts and ads. No microphone permission is requested.
- Your settings: Auto Beat Sync, the Don't show again reminder preference, and exact custom site origins that you add.
What is sent to the local app
The native host forwards a fixed set of fields to the local Phase Pal app: provider IDs; playback and capture flags; metadata-presence booleans; protocol and extension versions; a random browser-service session ID; sequence numbers and timestamps; numeric energy, estimated tempo, beat phase, confidence, beat pulses, onset density and section intensity; and fixed capture-stop reason codes.
Song names, artist names, URLs, page titles, page text, browsing history, account credentials, transcripts and raw audio are not sent through this protocol. The host reads a local app runtime descriptor containing a port and session token and authenticates to the app on 127.0.0.1. The desktop app's handling after receiving a frame is outside this extension policy.
Local processing, storage and retention
The extension has no analytics service, advertising endpoint, remote audio upload or speech-transcription path. It does not save captured audio to a recording. Audio samples and playback/analysis state are held in memory while needed for the active browser session or capture, rather than retained in a cloud database.
Two booleans are saved in chrome.storage.local: Auto Beat Sync and Don't show again. They are not synced or sent to the app. Custom site origins are stored locally in Chrome's persistent content-script registrations; URL paths, query strings, fragments and credentials are not saved. The custom origins are not sent to the native host. These local settings persist across restarts until changed or removed.
Host installation writes a native-message manifest and executable into the user profile and a per-user Windows registry entry where applicable. The separate Phase Pal application owns its runtime descriptor and its own retention practices.
Your controls
Select Enable Beat Sync to start tab capture and Stop Beat Sync to stop it. Chrome shows a capture indicator, and the extension routes captured tab audio back to your output so it stays audible. Auto Beat Sync is off by default. If saved on, opening the popup on a ready tab attempts capture once. It can preserve the approved stream through pauses and same-site track changes; it never authorizes unattended capture of a new stream or another tab.
Stop, opting out of Auto Beat Sync, turning Dance to Music off, app disconnect, permission loss, leaving the site, tab close or stream end stops capture. Failed or stopped captures do not automatically retry. Not now dismisses a site reminder for the current document. Don't show again saves a local preference; the reminder itself never starts capture.
Remove a custom site in the popup to delete its registration, revoke its optional permission and stop its capture. Chrome's extension settings also let you change site access. Disable or remove the extension to stop automatic playback reporting. Removing the extension removes its Chrome-local preferences and registrations; it does not uninstall the separate desktop app or delete that app's data.
Why these permissions are needed
| Permission | Purpose |
|---|---|
| Named music-site access | Observe playback and metadata presence on supported player hosts. |
| Optional HTTP(S) site access | Request access to one exact custom site after you add it, rather than granting all-site access automatically. |
scripting | Register and inject the packaged playback monitor on approved custom websites. |
nativeMessaging | Send the fixed fields described above to the installed local bridge. |
tabCapture | Obtain the selected tab audio stream after your popup action. |
offscreen | Analyze the approved stream outside the popup's short lifetime. |
storage | Remember the two local boolean preferences. |
Sharing and Limited Use
The extension does not sell user data, transfer it for advertising or unrelated purposes, or use it for creditworthiness or lending decisions. The local bridge uses the disclosed fields to provide Dance to Music. The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
This website and other services
These setup and privacy pages have no added analytics, forms, cookies or third-party embeds. They are hosted by GitHub Pages. GitHub logs visitors' IP addresses for security purposes; see the GitHub Privacy Statement. Visiting a music website or using the separate app remains subject to that service's policies.
Changes and contact
Updates will be published here with a revised date. For privacy questions or help with local data controls, contact hello@consistencyai.net. If you email us, your message and contact details are handled to respond to your request; do not include raw audio, credentials or private page content.