RateCommunity Extension Privacy Policy

The RateCommunity Extension helps the user blur video content on websites at user-configured time intervals and in user-configured blur zones. It can also help the user search, import, save, and re-use timing data for supported pages and can run optional remote NSFW analysis for video frames when the user explicitly enables those features.

Some features work entirely locally in the browser. Some optional features send user-selected or extension-generated data to external services that are necessary to provide that feature. This policy describes both cases in detail.

For the core local blur feature, the extension may process the current tab URL or origin, iframe URLs needed to locate the video player frame, the video element's playback state and current playback time, and user-created settings such as blur intervals, blur zones, blur strength, timing offsets, enabled or disabled state, and per-site preferences.

This locally processed data is used only to find the active video element, apply the blur effect, restore the user's saved settings, and render the extension's controls.

When the user enables optional remote NSFW scanning, the extension may capture still image frames from the current video page and send those frames, together with scan settings and technical metadata needed for the request, to the user-selected provider. Depending on the selected configuration, that provider is either OpenAI directly or RateCommunity acting as a proxy endpoint.

When the user uses the timing library, manual timing save, film or series search, or timing import features, the extension may send the user's search query, selected title identifiers, timing ranges, blur zones, page URL or origin, page title, and related metadata to RateCommunity services or to api4.rhserv.vu in order to search for, fetch, create, update, vote on, or import timing data.

When the user explicitly connects a RateCommunity account or uses account-linked features such as cloud timing management or music-related import tools, the extension may send authenticated requests to RateCommunity and may transmit links, identifiers, imported media metadata, and other user-submitted data required for that feature.

Depending on which optional feature the user chooses to use, data may be shared with the following parties: RateCommunity at rate.community, OpenAI at api.openai.com, and api4.rhserv.vu.

RateCommunity may receive user-submitted timing data, search requests, links, imported media data, authenticated extension requests, and, if the user configures RateCommunity as the scan endpoint, image frames used for NSFW analysis. OpenAI may receive image frames for NSFW moderation when the user chooses direct OpenAI scanning or when RateCommunity forwards a moderation request to OpenAI. api4.rhserv.vu may receive title or timing search requests used by the extension's library features.

RateCommunity does not sell extension data and does not use extension data for advertising, marketing profiling, or unrelated analytics.

Local extension settings are stored in Chrome extension storage on the user's device until the user changes them, clears them, or removes the extension.

Data submitted through optional cloud features may also be stored on RateCommunity servers as part of the requested feature, for example when the user saves timing data to the shared timing library or imports media information into their RateCommunity account.

RateCommunity retains server-side data only as needed to provide the requested feature, operate the service, moderate user submissions, and maintain account-linked functionality. Users can request deletion of account-linked data by contacting RateCommunity support.

The storage permission stores local settings and feature state. The activeTab and scripting permissions let the extension run its content scripts in the user-selected page. The webNavigation and tabs permissions are used to identify the active tab and the frame that contains the video element, communicate with that frame, and apply saved settings. Host permissions are required because supported sites often load their actual video player inside third-party iframe domains that vary by region, CDN, or player provider.

The extension requests these permissions to support its user-facing blur, search, import, timing, and scan features. It does not request browser permissions for advertising or unrelated data collection.

Users can use the local blur feature without signing in to RateCommunity. Optional remote features are user-initiated and can be left unused.

Users can remove local data by clearing the extension's storage or uninstalling the extension. Users can also restrict site access in Chrome's extension settings.

If a user does not want image frames or timing data to be sent off-device, they should avoid enabling or using the remote NSFW scan, timing library, import, save, and account-linked cloud features.

Remote requests made by the extension use HTTPS endpoints.

The extension's use of user data is limited to providing and improving the user-facing features described in the extension UI and Chrome Web Store listing. The extension does not sell user data, does not use user data to determine creditworthiness, and does not use or transfer user data for unrelated advertising purposes.

The use of information handled by the RateCommunity Extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

For privacy questions about the RateCommunity Extension, contact: support@rate.community