InstaSaveKit Privacy Policy

Instagram content and your session

To show controls and fulfil downloads you request, the extension reads relevant Instagram page content, media identifiers and available media sources. Requested batches may read normal post or Highlight viewer pages through your current Instagram session.

There is no separate extension login. InstaSaveKit does not ask for or collect passwords, cookies or session tokens. Instagram handles your existing login and ordinary authenticated requests. The extension does not bypass privacy or access restrictions, and normal Story viewing is recorded by Instagram.

Preferences and recovery records

Chrome’s local extension storage holds your save-location preference and the metadata needed for queues, progress and recovery. This can include local job tokens, hashed media keys, relative filenames, timestamps, statuses, errors, media types, Chrome download IDs and originating tab IDs.

Profile runs also keep the profile username, pending post or Story/Highlight identifiers and progress counters while needed. Pending identifiers are discarded when the run completes or is cancelled. The ordinary queue is limited to 50 items. Recent finished-job records normally roll off after 20 results; active work and results still needed to count profile progress may remain longer. Raw Instagram HTML and media files are not stored in extension storage.

Media URLs and Chrome’s download history

Signed media URLs are handled transiently in extension memory and messages to start requested downloads. They are not saved in the extension’s local storage or deliberately logged. Queued items resolve their media source again when needed.

Chrome separately manages downloads and its download history. That history can retain source URLs, filenames and other download details, including signed media URLs. Clearing extension records does not clear Chrome’s history.

Local files, without a media server

Chrome downloads media directly from the available Instagram media hosts to your device, normally under Downloads/InstaSaveKit. You can choose to use Chrome’s file chooser instead.

The extension has no analytics, advertising, media uploads, developer-hosted media proxy or third-party downloader service. It does not send your media or download queue to RavensMove. Instagram and its media hosts still receive the requests needed to supply pages and files.

Welcome and update pages

On first installation, InstaSaveKit opens its RavensMove welcome page. When the extension version changes, it opens the update page. These are ordinary website requests to fixed URLs, with no appended identifiers or download data.

RavensMove and its website providers can receive normal request information such as your IP address, browser information, the requested page and request time. The website’s own cookies and scripts apply when those pages open.

RavensMove website analytics and cookies

The RavensMove website loads Google Analytics and Ahrefs Analytics, plus Journey by Mediavine advertising scripts. Website analytics can measure page visits and interactions. Google Analytics and advertising providers may use cookies or similar technologies; advertising partners may process device and browsing information.

These website services are separate from the extension and are not injected into Instagram by InstaSaveKit. Website visits are not anonymous simply because the extension has no analytics. See the RavensMove website privacy policy for website data, cookies, advertising partners and contact details. Use your browser’s cookie controls and any privacy settings offered on the website to manage those choices.

Removing the extension

Uninstalling InstaSaveKit clears its local extension storage. It preserves downloaded files, Chrome’s own download history and separate website cookies. Delete those through your file manager and Chrome’s relevant controls if you wish.

Contact and policy changes

For support or privacy questions, contact us on Bluesky. We can see your Bluesky profile and the information you choose to share so we can respond. Public posts are visible to others. Do not share passwords, cookies, signed media URLs or private media.

We will update this policy when the extension’s data handling changes. This page’s date identifies the latest policy revision.