tIDl — Privacy Policy

Last updated: May 3, 2026

tIDl is a Chrome extension that lets you highlight text on any webpage, search TIDAL for matching tracks, and add those tracks to your favorites or playlists.

Data We Collect

tIDl collects only what is required for it to function:

• TIDAL OAuth tokens — when you sign in with your TIDAL account, an access token and refresh token are stored locally by TIDAL's browser SDK using Chrome extension storage. These tokens are never transmitted to any server other than TIDAL's own authentication, API, and playback endpoints.
• Selected text — text you highlight and explicitly search is sent directly to the TIDAL Open API (openapi.tidal.com) to perform a search query. It is not logged or stored by this extension.
• Library metadata — playlist and favorite track identifiers may be cached locally so the extension can show faster add-to-library controls.

Data We Do Not Collect

• We do not collect, transmit, or store any personal information on our own servers.
• We do not use analytics, crash reporting, or any third-party tracking services.
• We do not collect browsing history, page content, or form data. The content script runs on pages so it can detect highlighted text, but the extension only sends text after you click the tIDl search control or context-menu item.

Third-Party Services

tIDl communicates exclusively with TIDAL's official services:

• auth.tidal.com — for OAuth authentication
• openapi.tidal.com — for track search
• api.tidal.com — for adding tracks to favorites and playlists

Your use of these services is governed by TIDAL's Privacy Policy.

Local Storage

OAuth tokens, display name, country code, playlist cache, favorite cache, and the popup preference are stored using Chrome extension storage on your device. This data is never synced by tIDl and is removed when you uninstall the extension or sign out.

Permissions

tIDl requests the following Chrome permissions:

• contextMenus — to add a right-click menu item for searching selected text
• storage — to persist your login tokens locally
• identity — to launch the TIDAL OAuth sign-in flow via Chrome's identity API
• tabs — to observe the TIDAL OAuth fallback popup redirect if Chrome's identity window cannot load it
• all URLs content script access — to show the optional search button beside highlighted text on any webpage
• TIDAL host permissions — to authenticate with TIDAL, search the TIDAL catalog, update favorites/playlists, and play previews through TIDAL services

Changes to This Policy

If this policy changes, the updated version will be posted at this URL with a revised date.

Contact

Questions? Open an issue at github.com/Matcote/tidl.