Privacy policy
Simple by design.
Private by default.
FlickCue saves films and shows you want to watch and reminds you about them. This policy explains exactly what happens to your data.
Last updated: 15 September 2026
The developer runs no server and receives no data from you. There is no analytics, telemetry, advertising, or developer account. Data stays on your device or goes directly to a service identified below.
01
What is stored on your device
FlickCue uses the browser's extension storage, which is readable only by the extension, for:
- Saved titles, media type, year, rating and poster image URL.
- Reminder times and whether you marked a title as watched.
- Deleted-title markers kept for 90 days so sync does not restore a deletion.
- Settings and preferences, including whether online matching is enabled, your selected streaming-region country code, and your list or poster view choice. FlickCue does not determine your physical or precise location.
- If you enable Google sync: sync state, the private Drive file identifier, the connected Google account email, and OAuth tokens where the browser sign-in method requires FlickCue to store them.
02
What leaves your device
Page scanning
FlickCue reads the current page's title, headings, image labels, structured metadata and address to determine whether it is about a film or show. This happens entirely on your device. The full page and address are never transmitted.
Online matching is on by default so FlickCue can avoid false positives and show posters, synopsis, ratings and streaming availability. Only a candidate title or identifier derived from the page may be sent to the services below.
Candidate title, or an IMDb/TMDB identifier read from the page
Candidate title
Candidate title
Candidate title
Each web request reveals your IP address to that service, as any web request does. Those services process it under their own linked policies.
03
Optional Google sync
Google sync is off until you enable it. When enabled, FlickCue writes your saved list to the hidden application-data folder in your own Google Drive account.
The extension requests only the drive.appdata scope. It cannot read, list or modify other files in your Drive. FlickCue reads the connected account email only to label the active account in the popup. The email remains local, is not added to the synchronized watchlist, and is never sent to the developer.
Google OAuth tokens are sent only to Google's HTTPS endpoints. On Chrome, the browser can manage the Google token for the signed-in browser profile. On browsers that use the Google sign-in window, FlickCue stores the tokens locally so sync can continue. Signing out clears FlickCue's local connection data, while the private Drive copy remains until you delete it. Google handles that copy under Google's privacy policy.
04
What is never collected
FlickCue never sells user data or transfers it for advertising.
05
Permissions and their purpose
FlickCue does not request the browsing-history permission.
06
Data retention and removal
Local data remains until you remove the extension. Deleting a title removes it immediately, leaving only a dated marker for 90 days so that deletion reaches your other synchronized browsers.
If Google sync is enabled, uninstalling or signing out does not delete the private Drive copy. To remove everything, uninstall FlickCue, revoke its access at Google Account permissions, and delete its application data from Drive.
Questions?
Contact the developer
For privacy or support questions, use the developer contact shown on FlickCue's Chrome Web Store listing.