1. Overview
Pilot is a browser extension that provides media controls, audio tools, screenshots, image copying and downloading, temporary text editing, YouTube and Instagram Focus controls, keyboard shortcuts, and website-specific compatibility behavior. Features and availability depend on the website and browser; Pilot does not promise that every feature works on every site.
Pilot processes information in the browser to provide these features. The extension code inspected for this policy contains no Pilot developer-operated backend, analytics, advertising tracker, or telemetry service. This does not mean Pilot never makes network requests: image and thumbnail actions can request resources from their source hosts, as described below.
“Process” includes using information in the browser. Some website information may be processed locally even when it is not sent to Pilot’s developer or stored by the extension.
2. Information Pilot accesses and processes
Pilot’s content scripts run on web pages matched by its Chrome permissions. Depending on enabled features and the current page, Pilot may inspect page structure, media elements, visible text, image links, and the current page URL. It uses this access to identify media, apply Focus rules, provide controls, and respond to actions initiated by the user.
- Page text and website content: When Text Editing is used, Pilot reads the visible text at the clicked position and lets the user edit that text in the current page. The edit changes the rendered page in the browser; Pilot does not post the edit or save it as extension data. Website scripts may observe changes to the page, depending on the site. Focus controls inspect page elements to hide or restore the selected content.
- Screenshots and images: Screenshot features capture page or media pixels in the browser. Image features process image data for copying or downloading. A screenshot can contain anything visible in the captured area, including personal or sensitive information displayed by a website. Pilot does not send screenshots or copied image data to its developer.
- Media and audio: Playback, quality, volume, audio sync, and floating-player controls operate on media elements in the page. If the user chooses a custom audio file, Pilot loads it locally for playback in that page; the extension code does not upload that file.
- URLs and video identifiers: Pilot uses the current page URL and page-provided media or image URLs to determine which controls apply and which image or thumbnail resource to retrieve. YouTube thumbnail URLs can include a video ID. Pilot does not keep a chronological browsing-history log.
- Keyboard input: Pilot handles configured shortcut keys and the keys needed while its text editor is active. It uses these events locally to run the selected action; the inspected code does not record or transmit a keystroke history or typed form contents.
- Clipboard: When the user chooses a copy action, Pilot writes the selected image, screenshot, or UPI ID to the device clipboard. The inspected code does not read clipboard contents.
Pilot does not specifically seek health, financial, authentication, location, or personal-communication information. Such information could nevertheless appear in page text, images, or screenshots that the user chooses to process. Pilot does not read website passwords or cookies as a feature.
3. Network requests and sharing
When the user copies or downloads an image or thumbnail, Pilot may try one or
more candidate image URLs taken from the page. For YouTube thumbnails, a
candidate may be requested from i.ytimg.com. Other destinations
depend on the image URLs supplied by the page and may include redirects to
additional image hosts.
The image host receives the resource request and the URL being requested. Because it is a network request, the host also receives the user’s IP address and ordinary request metadata. A URL may contain a video ID, query parameters, or a temporary resource token. Depending on the browser, request context, and destination, other request details such as referrer information may also be sent. Pilot does not intentionally attach page text, screenshots, clipboard contents, or extension settings to image requests.
YouTube thumbnail candidates use HTTPS. For image URLs found on a page, Pilot uses the URL provided by that page and does not force every URL to HTTPS; an HTTP resource may be requested where the browser permits it. HTTP requests are not encrypted in transit.
Pilot’s code does not send settings, screenshots, page text, custom audio files, or keyboard logs to a Pilot developer server. The code has no developer analytics or telemetry endpoint. If the user opens a support or social link, the chosen external service receives the browser request under its own privacy practices. Current links include Buy Me a Coffee and Instagram.
Pilot does not control how image hosts or external services log, retain, or otherwise use requests they receive. Their own privacy policies apply.
4. Storage and retention
- Chrome extension storage: Pilot saves feature preferences, enabled states, keyboard shortcut assignments, Copy/Download Mode, theme, Focus settings, compatibility-site settings, onboarding completion state, whether you accepted the Terms and Conditions and Privacy Policy, the acceptance timestamp, installation date, and the local date the daily support banner was shown. These values are stored with Chrome’s local extension storage, not sent to a Pilot server, and remain until changed or the extension data is cleared.
- Website local storage: Pilot saves the Workspace dialog’s position and size in the current site’s local storage so the dialog can reopen in the same place. This small layout value is stored separately for each site and may be readable by that site’s scripts. It remains until that site’s storage is cleared.
- Temporary processing: Page text edits, screenshot tiles, image data, and custom audio are handled in the current browser session for the requested feature. Pilot does not retain a separate archive of them. When the user chooses to copy or download, the browser or operating system handles the resulting clipboard item or file; those outputs are under the user’s control.
Pilot has no account system and the inspected code has no cloud synchronization service. To remove extension settings, clear Pilot’s extension data in Chrome or remove the extension. To remove the saved dialog layout, clear the relevant website’s local storage using the browser’s site-data controls.
5. Your choices and controls
You choose whether to use copy, download, screenshot, text-editing, and custom-audio features. You can enable or disable Pilot features and change shortcuts and Focus settings in the Workspace. Avoid using capture or image features on information you do not want copied, downloaded, or requested from an image host.
Pilot requires you to accept the Terms and Conditions and Privacy Policy during onboarding before its features are enabled. The acceptance choices and timestamp are stored locally. If you leave onboarding without accepting, Pilot stays unavailable; you can reopen onboarding from the extension toolbar button. Pilot also stays unavailable if it cannot verify the stored acceptance.
6. Chrome Web Store User Data Policy
Pilot’s use and transfer of user data follows the Chrome Web Store User Data Policy, including its Limited Use requirements. Pilot uses page information only to provide user-facing extension features; it is not sold, used for advertising, or sent to data brokers. Image requests are made only as part of image or thumbnail actions, and the source host is the recipient needed to retrieve that resource. This description reflects the extension code reviewed for this policy.
7. Changes to this policy
This policy may be updated if Pilot’s features or data practices change. The effective date at the top indicates the date of the current version.
8. Contact
If you have questions or concerns about this Privacy Policy or how Pilot handles user data, email glitcho.in@gmail.com.