Shift+Click processes website content and resources from the current page in order to detect images, SVGs, canvas elements, CSS background images, favicons, and video resources, including direct video sources, poster images, and fallback images, when the user triggers an action.

Shift+Click also accesses the current page URL, origin, and page title, plus limited on-page metadata such as X/Twitter tweet identifiers or tweet metadata when available, only as needed to enable the extension on the current site, organize downloads, improve file naming, and perform the requested action.

For X/Twitter video downloads, Shift+Click may read the X/Twitter session CSRF cookie (ct0) for x.com or twitter.com only to authenticate requests to X/Twitter's own endpoints and retrieve the real MP4 URL after the user explicitly triggers a download with Shift+Click.

Shift+Click stores user preferences using Chrome storage sync, including shortcut settings, enabled or disabled toggles, enabled origins, and optional download folder preferences.

Shift+Click uses this data only to provide its core functionality: detecting assets on the current page, copying them to the clipboard, downloading them, resolving X/Twitter video files when needed, improving download file names, and remembering the user's preferences.

No unrelated site cookies are used for this feature, and cookie data is not used for analytics, advertising, or user tracking.

Shift+Click does not sell user data.

Shift+Click does not transfer user data to the developer or to third-party analytics, advertising, or tracking services.

When the user requests a copy or download, the extension may request the selected asset directly from the website hosting that asset, trigger a browser download from that source, or for X/Twitter video downloads send authenticated requests to X/Twitter's own endpoints to resolve the direct MP4 file.

Settings stored with Chrome storage sync may be synchronized by Google across the user's signed-in Chrome browsers, subject to Google's own policies.

User preferences remain in Chrome storage until changed by the user or removed with the extension.

X/Twitter cookie data and related request headers are used only in memory for the active request and are not stored in Chrome storage or on a developer-operated server.

The developer does not operate a backend that stores extension user data.

For privacy questions, contact: contact@shiftclick.cc