Read privacy and account-history records in your export

Direct profile facts

The profile card mirrors supported exported values

The full-export adapter reads personal_information/personal_information.json when its string-map structure is recognized. Supported fields can include username, name, biography, website, private-account value, email, and date of birth.

These are direct values from the supplied export. The analyzer does not verify that an old email remains reachable, that a listed phone belongs to the user, or that an inferred location is physically accurate.

Change history

Profile changes form a source-backed timeline

For profile_changes.json, the importer records the changed field, previous value, new value, and Change Date timestamp. Rows are sorted newest first and the report can show the covered window.

The count, sort order, and date range are derived from direct records. A change row does not reveal motive, who performed the change, or whether a security incident occurred.

Direct row: Profile Name | Old Studio -> North Studio | Apr 10
Direct row: Profile Bio Text | old text -> new text | Mar 02
Derived summary: 2 recorded profile changes, Mar-Apr

Oldest observed record

An activity floor is not account age

Advanced Insights scans supported capability date ranges and reports the oldest positive timestamp it can observe. This gives an evidence floor: activity is represented at least as far back as that date.

It cannot prove the account was created then. The selected date range, deleted data, missing categories, format changes, and account-specific retention can all make the account older than the oldest included record.

Export request context

Requested range helps qualify other findings

When your_information_download_requests.json is included and recognized, the importer can record the requested start, requested end, and completion time for the latest request.

That context can explain why comments or content stop at a boundary. It does not guarantee that every category obeys the same retention window or that every record within the chosen dates was supplied.

Security-neutral interpretation

The current report does not issue login or device verdicts

The archive catalog can detect broader category directories, but login and security records are not currently interpreted as proof that a device or session was authorized. Message bodies are also outside the analyzer scope.

A profile change, possible phone value, location label, or device-related record should not be presented as evidence of compromise without separate authoritative investigation.

Privacy boundary

Sensitive values belong only in the private report

Email, birth date, phone, location, and previous profile values can be highly sensitive. Public pages explain the dataset structure with fictional examples; they do not expose uploaded account values.

Private report routes are noindex and excluded from sitemaps. Processing and retention details remain governed by the privacy policy and the export-based analysis guide.

Questions

Common questions

Keep exploring

Related guides and tools

• Advanced Insights overview

  See the full evidence and coverage model.

• Advertiser activity data

  Understand audience matches, targeting labels, and distinct counts.

• Content and comment analytics

  Separate exported activity records from cadence and concentration calculations.

• Export privacy and processing

  Review retention, private routes, and processing limits.