Translucent shield with amber light on a graphite surface

Video Radar Privacy Policy

Last updated: October 24, 2026.

Publisher responsible for the product: Enrique Revollo. Privacy and support contact: enrique.revollo.digital@gmail.com. Website: Video Radar.

This policy covers the Video Radar extension and its optional local Windows engine. Video Radar detects and saves authorized web media, converts files, and records a Chrome tab and its audio after you select it. It does not require a Video Radar account.

1. Information used

Pages and media: page addresses, media links, titles, thumbnails, and metadata such as format, duration, size, resolution, and playback state. This information displays available sources, prepares downloads, and, if enabled, detects when the chosen player ends. Links may contain identifiers or temporary parameters supplied by the website.
Local settings and history: appearance, quality, format, languages, output names and paths, site profiles, authorized sites, and download details and status. Video Radar history is separate from general Chrome history.
A site's session, only when authorized: compatible cookies and their scope, along with the browser identifier, are passed to the local engine for authorized operations on that site. These may include authentication cookies. Video Radar does not ask for your password or copy your Chrome profile. Tab recording does not require this session feature.
Recordings: images and audio from the tab you choose in Chrome's sharing picker, the output filename, and technical capture information. The microphone is not requested. A selected tab may show personal data, communications, or other private information; select only content you intend to include in the file.
Recovery and checks: enabling a recovery copy saves recording chunks and their metadata in the extension's private storage. Local checks use a bounded file header, metadata, and occasional image and audio-signal samples; they do not identify people or transcribe speech.
Requested diagnostics: engine and tool versions, availability, output folder, free space, and status messages. Copying diagnostics is initiated in the interface and does not send them to the publisher. Copying a link places its complete value on your clipboard.

Video Radar does not include usage analytics, its own advertising, advertising tracking, or uploads of media to AI services.

2. When pages and capture are accessed

You can scan a tab when you use Video Radar; a manual scan may update sources while that page remains open. Automatic detection on future visits requires authorizing persistent access to that site. The advanced all-sites detection option expands access only when you enable it and accept Chrome's permission request. These functions inspect media-related resources and players; they are not used to create commercial browsing profiles.

Cookie access is separately authorized for each site through the interface. Recording requires explicitly choosing a tab, sharing its audio, selecting an output file, and starting capture. You can stop recording or stop sharing through Chrome. Automatic ending reads the linked player; it does not control the page or replace Chrome's capture selection.

3. Processing and recipients

Settings, lists, files, recordings, and checks are processed on your computer. They are not sent to a Video Radar publisher server. The extension communicates with the engine on the same computer through Chrome Native Messaging.

Inspecting or downloading media connects to the websites you choose and the servers, content delivery networks, or providers used by those websites. Those servers receive the requests required for the operation, your IP address, and relevant headers. When you authorize a session, cookies are applied according to their domain, path, expiry, and secure-connection scope. The engine may send the source page as a referrer and the browser identifier when required for the operation. Displayed thumbnails may load from their source server. External websites have their own policies and terms.

Manual installation or updating of the engine may download components and dependencies from software repositories. It does not require sending your history or recordings to the publisher. Chrome and Chrome Web Store may perform their own communications, installation, and updates under Google's policies.

Visiting Video Radar's public pages or sending support email is separate from using the local extension. Web hosting and email services may process ordinary request information, such as IP address, date, connection headers, or the message you send, according to their configuration and policies. The extension does not automatically load those pages or send support requests.

We do not sell the data handled by Video Radar, use it for personalized advertisements, provide it to data brokers, or use it for creditworthiness or lending decisions. The publisher does not automatically receive your files or history. If you contact support, you decide what information to share; do not send passwords or session cookies.

4. Storage and retention

Extension: Chrome stores settings and enabled history in the extension's local storage. Source lists and player state use Chrome session storage and are updated or removed as the corresponding pages change or close. Active jobs are kept to maintain their state. Retained settings and history have no automatic time-based deletion period.
Local engine: the queue, its requests, titles, links, paths, settings, and status are stored for recovery. On Windows, engine state normally resides in %LOCALAPPDATA%\Video Radar. Temporary links may remain in these records. The installation folder may contain local configuration. If a queue is damaged, the engine may preserve a recovery copy of the queue file rather than discard it.
Authorized cookies: values remain in engine memory with validity limited to 30 minutes after each connection or refresh, without exceeding each cookie's own expiry. Disconnecting requests removal from the engine; removal is confirmed only when the engine responds. If it does not respond, the native session may remain available until revocation is applied, it expires, or you close the engine. Cookie values are not written to Video Radar history, queue, or configuration. The authorized site name, references to its use, and sites with pending revocations may remain in settings or job records. Disconnecting Video Radar does not delete Chrome's original cookies.
Saved files: downloads, recordings, subtitles, exports, and possible partial files remain in their chosen local locations until you delete them. Backup or synchronization software on your computer may copy folders you configure for it; Video Radar does not configure that synchronization.
Optional recovery copy: a second copy is saved as chunks in OPFS, private storage for this Chrome profile and extension. The limit is 8 GiB per recording, and backup can stop earlier if quota is insufficient. Exporting does not automatically delete the copy. A chunk not yet committed may be lost. Clearing extension storage or uninstalling the extension removes this copy; it does not delete files exported outside that storage.

Video Radar does not add its own encryption to local files or records. Their protection depends on your Chrome profile, system permissions, any device encryption you configure, and physical or remote access to the computer. HTTPS connections use the protection provided by the website and networking tools; a user-selected HTTP link does not have that same protection.

5. Your controls and deletion

You can revoke site access in Video Radar or Chrome's permission controls, disable extended detection, and disconnect authorized sessions. Revoking access stops the affected detectors, clears their source and player metadata from Chrome session storage, removes extension authorization, and asks the engine to revoke the corresponding sessions and cancel jobs depending on them. If the engine does not confirm the operation, Video Radar shows a persistent warning and retains the sites awaiting revocation, without cookie values. Checking the connection or diagnosing the engine retries the request. Existing authenticated jobs could continue until cancellation is confirmed or you close the engine; cookie expiry does not guarantee interruption of a transfer already established. Disabling extended access also removes sites saved for detection. These actions do not delete job records or saved files, and do not log you out of the website.

In Downloads, Clear history removes the completed, cancelled, and failed records managed by Video Radar while preserving active jobs and files. If the engine is disconnected, cleaning its records may require reconnecting it. You can turn off Keep history to stop persisting finished jobs. These options do not clear Chrome's general download history.

In the recorder, Delete copy removes the selected OPFS backup; exporting it does not. Delete final or partial files from their folders when you no longer need them. Uninstalling the extension deletes its Chrome data but does not uninstall the engine or delete its state, configuration, damaged-queue backups, or your files. The engine uninstaller removes its integration registration while keeping local files. To remove all engine data, stop its jobs and close it before removing its local state; contact support if you need help identifying the folders to keep.

6. Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used for the described media features and operations needed to provide them, not for advertising or unrelated purposes.

7. Changes and contact

We will publish policy updates here and revise the date. If a version introduces a material change to data practices, we will disclose it in the product and obtain the permissions or consent required before the new use. For privacy or support questions: enrique.revollo.digital@gmail.com.