Is It Safe to Analyze a LinkedIn Data Export?
Check the tool's data flow before choosing an export. InstaScope reads supported LinkedIn files in your browser. The working archive, an optional saved connection snapshot and a downloaded CSV have different contents and lifetimes.
Three separate places your data can exist
| Where | What it contains | How it is kept |
|---|---|---|
| Active workspace | Supported normalized records, including private text when supplied | Memory in this tab until reload or close |
| Optional Snapshot Vault | Minimal connection fields, a chosen label and capture date | Browser storage only after explicit saving |
| Downloaded files | The records or aggregates you chose to export | Files on your device until you manage or delete them |
Account access and network requests
The archive analyzer does not request a LinkedIn password, session cookie or account connection. ZIP extraction and supported CSV parsing run locally. Opening a profile link or invoking native sharing is a separate action you choose.
Ordinary page resources and the site's stated analytics or optional services are separate from archive processing. Archive contents, names, message text, searches and credentials are not sent in product analytics. Read Privacy for the current service details.
What the connection Vault leaves out
A saved connection snapshot contains names, validated profile URLs, company and position labels, recorded dates and your snapshot label and capture date. Messages, emails, phone numbers, applications and search text are not part of its schema.
Browser storage is not encrypted or automatically synced. Clearing the active session does not delete a snapshot you deliberately saved. Use the Vault's delete controls or manage its private backup separately.
A CSV and a Wrapped card disclose different things
A conversation CSV can contain full messages, and an activity CSV can contain search text. Treat those downloads as private records. LinkedIn Wrapped includes aggregate counts and excludes names, companies, messages, private words and individual job details.
Before sharing, inspect the actual file or card. A local tool cannot take back a file after you send it to someone else. Keep archives and backups on a device you control.
Related LinkedIn guides
Sources and responsibility
LinkedIn's documentation describes the export request and the records it can supply. The worked examples use independent fictional inputs and InstaScope's current reader. Account coverage and upstream file formats can vary.