Privacy policy
We keep the app lightweight and the data footprint narrow.
Last updated: March 29, 2026. This page explains how Song to Watch handles search activity, service operations, and third-party lookups tied to the app experience.
What we collect
Song to Watch currently runs without user accounts. The app may store search analytics such as search text, selected track IDs, result views, timestamps, and request source metadata so the product owner can understand how people use the experience.
How data is used
Search and results data is used to operate the app, improve recommendation quality, debug failures, and understand which songs or flows people use most often. Analytics storage is not intended to build advertising profiles.
Third-party services
Song to Watch may send search or lookup requests to Spotify and TMDB to fetch track metadata, soundtrack context, artwork, and watch-provider availability. Those services apply their own terms and privacy practices to the requests they receive.
Hosting and storage
The app is hosted on Firebase App Hosting and may store operational data in Firestore. Standard platform logs, request metadata, and error traces may also be processed by Google Cloud infrastructure as part of normal app operations.
Cookies and browser storage
The current product is designed to use only technical browser storage and platform behavior required to render the site, navigate between pages, and deliver secure traffic. If non-essential analytics, marketing tags, or account sessions are added later, this policy should be updated before rollout.
Retention and future updates
Song to Watch keeps operational data only as long as reasonably needed to run, secure, and improve the service. This page may be updated over time to reflect new features, legal requirements, or support processes.