Privacy, in plain language.

Your archive stays in your browser.

New conversation albums, Instagram DM and My Digital Year use a separately configured private origin. That workspace has no advertising or analytics scripts and opens without an opener. Until it is activated, those features do not process files on the public site. Existing public tools retain their current advertising behavior until the owner explicitly activates the handoff.

Each origin owns its own browser storage. Activation does not move or erase saved records: export a backup on the old origin and explicitly restore it on the new one. Album redactions change a new export projection, not the original archive. Review the generated file before sharing.

ZIP, JSON, HTML, supported LinkedIn CSV and TikTok TXT files are processed on your device. The analyzer does not upload them, store them on a server, or save the raw archive in browser storage. Current results stay in this tab’s memory until you clear active data, reload, or close the tab.

Advertising on production pages

Adsterra ads load automatically on eligible production pages. Adsterra receives your IP address and browser information and may use cookies, identifiers or open ad tabs. Its scripts run in the same document and can access page content and browser storage, including data shown by the tools. Uploaded data is not isolated from third-party code. InstaScope does not intentionally send archives or credentials to Adsterra. Analytics preferences apply only to product analytics.

TikTok records stay local.

TikTok relationship, watch, activity and conversation files are read in a browser worker and kept in tab memory. Only supported fields enter the dataset; contact, payment, IP, device, login and location fields are excluded. Embedded text is inert, and source video links or attachments are never fetched automatically. A failed or cancelled replacement keeps the previous working export.

The separate optional TikTok Vault saves validated follower and following usernames, usable source dates, a label and a capture date only when you choose Save relationship snapshot. It excludes messages, searches and watch history. Storage is not encrypted or synced; backups can contain private usernames. You can review a restore and explicitly rename or delete snapshots. Fictional demo snapshots stay in memory and do not read or write your saved personal snapshots. TikTok Wrapped contains aggregate counts only.

LinkedIn records stay local.

LinkedIn connections, messages, career, Learning and supported Complete-export activity and searches are read in a browser worker and kept in tab memory. Contact details, payments, ad targeting, screening answers, IP addresses, user agents, attachments and inferred platform scores are excluded. Exported text stays inert and external assets are not loaded. Product telemetry uses fixed categories without private text, URLs, filenames or record counts.

The optional LinkedIn Vault uses separate browser IndexedDB storage. Saving explicitly keeps only connection names, validated profile URLs, company and position labels, recorded connection dates, your chosen capture date and local snapshot metadata. It excludes messages, searches, content activity, account events, emails, phone numbers and applications. This storage is not encrypted or synced; people using your browser profile may access it. You can review backups before restoring, rename snapshots and confirm deletion. Clearing the active session does not delete saved snapshots. Wrapped images contain aggregate counts only; CSV downloads and Vault backups can contain private connection or message records, so keep those files private.

Snapshot Vault stays in this browser.

If you choose “Save snapshot”, InstaScope stores only follower and following usernames plus the export date you enter and local snapshot metadata (an ID, format version and time saved) in this browser’s IndexedDB site storage. It does not save the raw ZIP, private connection lists, relationship timestamps, messages, media, passwords or session cookies. No Vault data is stored on InstaScope servers. You can browse, replace or delete saved snapshots in Snapshot Vault. Deleting saved history does not clear the active export; clearing active data does not delete saved history.

An older single saved snapshot is automatically migrated once. Its original local copy is kept for compatibility with an older deployment until you delete that snapshot or all saved history. Clearing browser/site data may remove your Vault. There is no cloud backup. “Export Vault backup” downloads a private JSON file containing usernames; keep it safe. Import validates and previews this specific backup format before you confirm a local merge. Existing dates are kept.

Circle Pulse summarizes saved Vault snapshots locally, independently of your active export. Make sure the selected saved records belong to the same Instagram account. For a two-snapshot comparison, choose the snapshots and confirm the dates and that both exports belong to the same Instagram account. InstaScope does not automatically verify account identity. Saved totals describe individual exports, not continuous monitoring or a complete relationship history.

Account history is derived locally from usernames in saved snapshots. Mutual Origins compares both recorded relationship dates in the active export, in memory. These dates and results are not uploaded or added to Vault storage. Snapshot presence does not establish exact event times; recorded dates may reflect refollows rather than uninterrupted following.

Circle Pulse retention, stable membership, reappearance and state-change summaries exist only in memory. They are not stored in Vault, added to backups or sent to analytics. Optional saved-history Wrapped cards use only aggregate facts after you choose to include them, without usernames or private-list data. Observed presence does not prove uninterrupted following or what happened between saved exports.

Review Memory is private and local.

Keep, Reviewed, Watch and optional private notes are decisions you enter, stored in a separate IndexedDB database in this browser. Usernames, notes, flags and watch targets are not uploaded or sent to analytics. They survive new imports and clearing active data. Clearing Review Memory does not delete Snapshot Vault; deleting snapshots does not delete Review Memory. Clearing browser/site data may remove both.

Watch Circle compares the local export with a strictly earlier readable saved snapshot only after you provide the export date and confirm the same Instagram account. InstaScope cannot verify account identity. Differences are observations, not live monitoring, notifications, exact change times or evidence of intent.

Review Memory has its own private JSON backup containing usernames, flags and notes. It is downloaded and imported locally, with a preview before confirmation. Existing local records and notes are kept, even if an incoming backup is newer. There is no automatic or cloud backup. Fictional demo memory is held in this tab’s memory only and never overwrites your real decisions.

Your WhatsApp chat stays on your device.

InstaScope reads WhatsApp TXT and ZIP exports in your browser. Message text, participant names and raw exports stay in this tab's memory until you clear the chat, reload or close the tab. Switching WhatsApp tools keeps the working chat available. No WhatsApp login or account connection is needed.

Chat Vault saves only anonymous aggregate snapshots when you choose to save. It does not save message text, participant identities, phone numbers, URLs or raw exports. Saved snapshots and manual backups remain local; there is no cloud sync. Clearing the active chat does not delete saved snapshots, and clearing browser/site data may remove the Vault.

WhatsApp Wrapped images are generated on your device with exported display names and qualifying message-derived words. Number-only labels are replaced. Review their contents before sharing. Downloads and your device's share menu are only used when you choose them.

Facebook snapshots save only when you choose.

Friends Comparison reads two exports locally. Names and results stay in this view’s memory until you leave or reload. Only an explicit Save stores a minimal snapshot in the separate Facebook Friends Vault: display names and source rows, coverage, your label, save time and optional user-supplied export date. ZIPs, messages and media are never saved. Other Facebook tools keep their existing memory-only behavior.

Friend display names are sensitive personal data. Saved Facebook snapshots and downloaded backups are unencrypted and readable by anyone with access to this browser or file. Rename or delete each snapshot, or delete the entire Facebook Vault in Friends Comparison. Clearing a comparison or shared export does not delete saved records. Browser/site-data deletion can remove them. Backups are validated and reviewed before an explicit restore; no cloud sync exists. Names, friend lists and results never enter analytics, URLs or metadata. Fictional comparison demos cannot be saved to the private Vault.

Facebook Vault changes use IndexedDB transactions in this browser. An older V1 local-storage copy is read without changing it; your next explicit save, rename, delete or restore moves the current state into IndexedDB. The older copy is removed only after that change commits. A failed removal is shown in the Vault; clearing this site's browser data removes any remaining local copy. Deletion keeps only an empty migration marker so an older copy cannot return. V1 downloaded backups keep their existing format.

Appearance stays local.

Your Light or Dark appearance preference is saved locally in this browser when storage is available. It is shared between the Instagram and WhatsApp areas and is not sent to analytics or linked to your exports.

No Instagram credentials.

We do not ask for a password or session cookie. No Instagram account connection is required.

You choose what to share.

Wrapped images contain aggregate relationship statistics and dates, not individual usernames. Pending requests, close friends, blocked or restricted accounts, story visibility lists and your unfollow history stay local and are excluded from Wrapped images. “Download CSV” contains the full filtered account list, including other pages, with profile URLs and recorded calendar dates where available. Cleaner’s selected CSV contains only the accounts you select. These files are created in your browser; keep them private unless you choose to share them. Review flags and private notes never enter Wrapped, shared images or any account CSV. Opening a profile takes you to Instagram, which has its own privacy practices.

A calendar event, without notifications from us.

After saving a real snapshot, you can download a calendar file to remind yourself to export fresh Instagram data and return. It contains a generic event and future calendar date, with no usernames, snapshot counts, notes or archive contents. Its random calendar-event identifier stays only in the temporary offer and downloaded file; it is not a tracking identifier. InstaScope stores no reminder and sends nothing to a calendar service or analytics. Import the file and choose any alert in your own calendar. InstaScope sends no notification.

Product events, without your social graph.

This deployment sends an allowlisted product event, a coarse referring-source category and a webdriver automation hint to a same-origin analytics endpoint. The collector stores these with bounded platform, tool, outcome and categorized failure dimensions, server-side automation evidence and a count of one. The source is classified once per browser document and held only in memory as you navigate within the site. It stores no raw referrers, referring hostnames or URLs, search queries, page URLs or paths, User-Agent strings, IP addresses in analytics, archive data, filenames, usernames, follower/following counts, notes, review flags, watch targets or snapshot dates. Without optional daily measurement, there are no analytics cookies, session IDs, persistent anonymous IDs or fingerprints, and no analytics identity is saved in browser storage. Daily browser measurement requires the separate choice below. Do Not Track and Global Privacy Control disable remote delivery. Analytics failure never blocks the tools. The event collector uses a connecting IP only temporarily for rate limiting and does not write it or user agents to analytics storage or intentional request logs. Hosting and security infrastructure can receive normal request information such as your IP address when you visit the site.

A Google-family referrer does not prove a Google Web Search or Google Search Console click. The category “none” means no referrer was visible; apps, browsers and privacy settings can hide it, so this does not prove direct traffic. The webdriver hint comes only from your browser's automation flag. A “yes” value is strong automation evidence; “no” does not prove a human. The server briefly checks the normal User-Agent header for obvious automation signs and keeps only “automation”, “browserish” or “unknown”. A “browserish” value does not prove a human. These hints can be spoofed and are not fingerprints.

The document_entry_observed event means client JavaScript ran for one browser document. It is sent at most once for that document, including navigation within the site; a full reload can count again. It does not count unique visitors, users, sessions or Search Console clicks. Historical events without a source category are pre-audit data; they cannot be attributed to a source later.

Public photo lookup is separate.

The profile reference you explicitly submit is sent to a separate public-photo lookup service for the selected platform. A matching public image is delivered through the bounded same-origin photo route. No account passwords or session cookies are used. It has no access to your uploaded export. Restricted content is never bypassed.

Photo enhancement happens on your device.

Photos selected from your device stay in this tab's memory and are removed from the preview when cleared, replaced or closed. WhatsApp photo viewing uses this local source without phone-number lookup. Optional AI upscaling runs in a browser worker on your device; model and runtime files download from InstaScope when needed. The photo is not uploaded for enhancement. Estimated details can change facial features; the result is not an authentic higher-resolution original. You choose whether to save or share it.

External links and sharing a problem.

The footer's Project maintainer link opens a public GitHub profile in a new tab. It does not submit a report or attach your data. If you describe a problem elsewhere, use the tool, file format and steps with fictional examples. Do not attach your export, saved snapshot, credentials or screenshots that expose personal accounts.