Stremio Insights
GitHub Project

Chrome Web Store Compliance Document

Privacy Policy

Your data belongs to you. Stremio Insights processes and stores your viewing history entirely locally, keeping your privacy secure.

Last Updated: August 22, 2026 Classification: Public / Local Only

1. Introduction

At Stremio Insights, we believe that your digital footprints and viewing history are deeply personal. We are committed to transparency, security, and developer integrity. This Privacy Policy outlines exactly how our browser extension interacts with your data, what information is accessed, and how it is securely stored.

Unlike modern SaaS tools or tracking scripts, Stremio Insights is a privacy-first, local-only Chrome Extension. It contains no tracking scripts, no advertisements, and no analytics cookies.

2. What the Extension Does

Stremio Insights is designed to enhance your experience on web.stremio.com. Stremio's default cloud dashboard provides a simple "Continue Watching" carousel but does not maintain a complete, searchable, chronological timeline or long-term analytical metrics.

Stremio Insights fills this gap by reading your library updates from Stremio, calculating aggregate viewing metrics (such as total hours watched, favorite genres, top directors, and yearly breakdown charts), and presenting this information in a neat, responsive sidebar and dashboard directly integrated into the Stremio interface.

3. What Data Is Processed

To compute your dashboards and construct your chronological timeline, Stremio Insights accesses and processes the following data:

  • Stremio Authentication Token (authKey): Extracted strictly from Stremio's native localStorage profile object to authenticate local HTTP requests to Stremio's authorized endpoints (such as retrieving library items and sync states).
  • Viewing Library Data: List of library items, watched counts, playback progress, video runtimes, and watch timestamps fetched from Stremio's official developer API.
  • Content Identifiers: Unique IMDb IDs (e.g., tt0117951) detected from the page URL or rendered on-screen media cards to determine which movie or television show is currently being viewed or displayed.
  • Rich Media Metadata: Non-personally identifiable metadata including titles, genres, actors, directors, descriptions, release years, and poster images retrieved to display your charts and lists.

4. What Data Is NOT Collected

We follow a strict data minimization principle. We do not collect, read, store, or transmit:

  • Personal Identifiable Information (PII): We do not collect your name, email address, physical location, IP address, password, or Stremio account login credentials. While your email is stored natively in Stremio's own profile storage, the extension completely ignores it and only extracts the authorization token.
  • Broad Browsing History: The extension is strictly sandboxed. It is technologically blocked from viewing, reading, or interacting with your history, sessions, or tabs on any website other than web.stremio.com.
  • Session Cookies & Device Fingerprints: We do not drop tracking cookies, utilize unique browser canvas fingerprinting, or generate device trackers.

5. How Viewing History Is Processed

Stremio Insights employs a dual-channel pipeline to process your viewing history:

  1. Authoritative Sync Pipeline: When you open the extension sidebar or dashboard, Stremio Insights pulls the latest watch records directly from Stremio's cloud database (datastoreMeta and datastoreGet endpoints). It merges these records with your local history database, automatically repairing corrupted dates or missing metadata.
  2. Real-time Playback Interception: The extension content script injects a lightweight hook into the main page window. This hook intercepts Stremio's outgoing datastorePut network requests (dispatched when Stremio updates your playback progress). When intercepted, the playback progress, timestamps, and duration are processed immediately to keep your local analytics dashboard up-to-date in real-time.

6. Storage, IndexedDB & chrome.storage

We store data securely using official browser database standards:

  • Stremio localStorage: We read Stremio’s localStorage.getItem('profile') strictly to fetch your profile's authKey. We do not edit, delete, or write back any data into Stremio's localStorage or Stremio's native IndexedDB databases (such as stremio-core).
  • chrome.storage.local (Primary Database): All processed watch history records, metadata caches, user-configured settings, and computed statistics (e.g. favorite directors, monthly activity counts, heatmap tallies) are stored exclusively inside your browser's secure chrome.storage.local database. This database is sandboxed by Chrome for Stremio Insights and cannot be read by other websites or other extensions.

7. Does My Data Leave the Device?

No. Your data never leaves your device.

All calculations, statistics aggregation, graph generation, timeline formatting, and searches are performed entirely in your browser using local JavaScript. We do not run any backends, analytical collectors, or proxy servers. There is no cloud storage, meaning we could not inspect your viewing history even if we wanted to.

8. External Services and APIs

To display posters, genres, and directors in your dashboard, the extension communicates directly from your browser to external official databases:

  • Stremio Datastore API (api.strem.io): Authenticated queries are made securely via HTTPS using your local token to fetch your profile's saved library item list and metadata states.
  • Stremio Cinemeta API (v3-cinemeta.strem.io & cinemeta-catalogs.strem.io): Unauthenticated queries are made to these public catalog services to retrieve media details (runtimes, casting, descriptions, posters, and release years) based on standard IMDb IDs.

These external endpoints are contacted directly from your browser. They only receive the media ID (like IMDb ID) and have no access to your personal identifier, Stremio Insights profile, or extension-computed history.

9. Optional Integrations

Stremio Insights includes an optional OMDb API (Open Movie Database) integration. If Stremio's default metadata provider fails to return details for a specific item, the extension can fallback to OMDb.

This integration is entirely optional and remains inactive unless you input your own personal OMDb API Key in the extension options. Your OMDb API key is saved strictly in your local chrome.storage.local cache.

10. Data Retention

Since your data is stored locally in your browser's sandboxed storage, it is retained until:

  1. You explicitly delete your data using the extension's user controls.
  2. You uninstall the Stremio Insights extension from Google Chrome.
  3. Google Chrome is reset, or its browser storage cache is manually wiped.

11. User Controls (Export & Delete)

We give you absolute control and digital sovereignty over your viewing history:

  • Export Backup (CSV/JSON): You can export your entire local database at any time. Simply open the Dashboard, click the Export buttons in the header, and select either CSV format (for spreadsheet software) or JSON format (for developer diagnostics or offline backups).
  • Wipe History (Delete): You can instantly and permanently purge all stored history from the extension. Clicking the "Clear History" button in the settings panel instructs chrome.storage.local to wipe all library, analytics, and lastSync data. This action is irreversible.

12. Security Practices

Our development practices prioritize absolute security:

  • Secure Content Communication: The Stremio auth token is extracted securely in the main browser context and bridged to the isolated content script via strict custom window events (REQUEST_STREMIO_PROFILE and STREMIO_PROFILE_EXTRACTED) to avoid DOM sniffing and security vulnerabilities.
  • Sandboxed execution: All analytics rendering, script execution, and layout logic run within Chrome’s strict Extension sandbox, preventing external pages from accessing the extension state.
  • HTTPS Enforcement: All network queries to Stremio and Cinemeta endpoints are forced over encrypted Transport Layer Security (HTTPS).

13. Chrome Extension Permission Usage

To comply with Google Chrome Web Store policies, here is a complete explanation of the permissions declared in our extension manifest:

Permission Name Technical Scope Justification / Why It is Required
storage Accesses browser storage APIs. Required to save your chronological watch records, enriched genres, caching directories, and options locally in chrome.storage.local.
activeTab Accesses current active tab. Enables the extension popup to send a rescan command (FORCE_RESCAN) to your current active Stremio window when you click the manual sync button.
Host Permission:
https://web.stremio.com/*		 Enables content script injection. Allows the extension to inject its content scripts (to intercept playback updates via fetch and render the integrated slide-out statistics panel inside Stremio's web container).

14. Changes to This Policy

We may update our Privacy Policy from time to time. Any changes will be posted directly to this page, and the "Last Updated" date at the top of the policy will be updated accordingly. Because the extension has no network channels to send you notifications, we encourage you to review this page periodically to remain informed about how we safeguard your data.

15. Contact Information

Stremio Insights is a fully open-source project. If you have any questions, concerns, or bug reports regarding this Privacy Policy or our code implementation, you are welcome to reach out:

  • GitHub Issue Tracker: Submit an issue or question directly on our official GitHub repository.
  • Developer Contact Email: Contact the maintainers through the open-source repository issue tracker or specified extension support email.