Cometitle Privacy Policy

Effective date: October 8, 2026

Cometitle is a browser extension that identifies the movie or series page currently opened by the user and displays related community comments in an on-page panel. This policy describes the data processed by the Cometitle beta service.

Data processed

Cometitle may process:

• Account information such as email address, username, profile biography and selected avatar.
• Google identity information provided during optional sign-in, limited to the OpenID, email and profile scopes.
• User-generated content such as comments, replies, spoiler choices and votes.
• Favorites, follows and other profile relationships created by the user.
• Media context needed to identify a title, including its name, TMDB identifier, media type, season and episode.
• Viewing activity only after the user separately enables activity sharing: the title, TMDB identifier, media type, poster reference and session timestamps. Season, episode, streaming platform and page URL are not included in data shown to friends.
• Personal viewing history only after the user separately enables history saving: the title, TMDB identifier, media type, optional season and episode, poster reference and session timestamps. Viewing history is visible only to its owner.
• The origin and path of the active media page. Query parameters and fragments are removed before its URL is sent to the Cometitle API.
• Public comments collected from explicitly supported external comment sources, together with the source name, source page URL, public author or nickname, and comment date. Query parameters and fragments are discarded from the source page URL stored in server memory. External profile images are not collected.
• Feedback explicitly submitted by the user, including the description and report type, together with the extension version and interface language. Compatibility and technical reports may additionally include the browser family, the page URL after query parameters and fragments are removed, the platform content identifier when it can be read from that URL, the domain, anonymized route pattern, detection method, detected title, matched TMDB title and identifier, media type, available season/episode scope, source result categories, source processing durations and total loading duration. Query parameters, URL fragments, page content, comment content, the full browser user-agent, authentication credentials and account details are not stored as feedback diagnostics.
• Security and operational information generated by the hosting service, such as request timestamps, IP addresses and error logs.

How data is used

Data is used only to:

• Authenticate users and provide account features.
• Match the active page with the correct movie or series.
• Display, create and synchronize relevant comments.
• Provide profile, favorite, follow and voting features.
• Show recent viewing activity to mutual friends only when both users have enabled activity sharing and neither user has blocked the other.
• Save a private viewing history for the account owner when history saving is enabled.
• Prevent abuse, diagnose failures and operate the beta service.
• Review user feedback, compatibility reports and comment complaints.

Cometitle does not sell personal data and does not use it for personalized advertising, credit decisions or unrelated purposes.

Service providers

Cometitle relies on service providers required to operate the extension, including cloud API hosting, managed PostgreSQL database hosting, optional Google sign-in, movie and series metadata providers, avatar image providers, and explicitly supported external comment sources. Current core infrastructure providers include Render for API hosting and Neon for PostgreSQL database hosting. The extension also contacts the explicitly supported external comment sources to retrieve public comments for the detected title. These providers and sources process network information according to their own terms and privacy policies.

Cometitle's use and transfer of data received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is not transferred except when necessary to provide or improve Cometitle's user-facing features, maintain security, comply with law, or as part of a merger, acquisition or sale of assets.

Storage and retention

Account and user-generated data is retained while the beta account remains active or while it is needed to operate and secure the service. Activity sharing and history saving are separate, disabled-by-default choices. Live activity is refreshed by heartbeats, is treated as current for two minutes, and is not a permanent activity archive. Personal viewing history is limited to the newest 500 sessions and 12 months. Users can delete one history item, all history for a title, or their entire history. Turning off history saving stops new history records but keeps existing records until the user deletes them from the History screen.

A user can schedule account deletion from the extension. The account, public profile, and authored comment content become inaccessible immediately and are retained for a 30-day recovery period; signing in during that period cancels deletion and restores them. After the period ends, account data, viewing activity, viewing history, comment and reply content, votes and relationships are permanently removed. A content-free placeholder may remain for a deleted top-level comment only when needed to preserve replies written by other users. Submitted feedback is retained while it is needed to review and resolve the report. Some preferences and authentication state are stored locally in browser extension storage. In Firefox, durable authentication credentials are kept in the extension's private IndexedDB storage, separate from content scripts. Access tokens remain in protected session storage. When a signed-in user's extension retrieves external comments, it may send them to the Cometitle API. Those comments may be held in server memory for no more than one hour and shown during that period to other users viewing the same title. They disappear earlier if the service restarts and are not stored in PostgreSQL.

Deletion and access requests

Users can schedule deletion of their Cometitle account and associated personal data from the extension's account screen. The current username is required as confirmation. Users can also email info@cometitle.com for access or deletion requests. Support requests are handled after account ownership is verified.

Security

Firefox asks for required data transmission consent during installation. Optional technical and interaction data consent controls automatically attached feedback diagnostics, including version, interface language, browser family and processing timings. If that permission is absent, only the explicitly submitted report and complaint target are sent; diagnostic metadata is omitted. This permission can be managed in Firefox's add-on settings and is separate from the in-app choices for viewing activity sharing and personal history.

Cometitle uses HTTPS for network communication and limits extension network access to declared service and scraper hosts. No internet transmission or storage system can be guaranteed to be completely secure.

Children

The beta service is not intentionally directed to children under the minimum age required to consent to online services in their country.

Changes

This policy may be updated as beta features or service providers change. The effective date will be updated when material changes are made.

External content removal and objections

An external comment author or source operator can email info@cometitle.com with the source name, public page address, and enough information to identify the content. Do not include passwords, Google tokens, or other authentication secrets. Requests are reviewed before the content or source is removed or disabled.

Contact and support

Email info@cometitle.com for privacy questions, data requests, technical support, or requests concerning an external comment or source. Product problems can also be submitted through the extension's feedback screen, which includes limited diagnostics where permitted by the user's consent, but never passwords or account tokens.