PRIVATE DATA ATLAS / EVIDENCE & REVIEW
From observation
to a reviewed record.
Reopen a saved reference, document its evidence and manage access within your organization.
Checking your organization session…
01 / RETAINED EVIDENCE
Select a saved reference
Selections reuse your organization's saved data. No new source collection is started.
02 / SAMPLE COMPARISON
What changed in the evidence?
Compare saved samples of the same asset and source. An event absent from one sample does not establish inactivity, deletion or a chain reorganization.
Choose a baseline and compare the retained samples.
03 / SAVED CALCULATIONS
Keep evidence for later review.
Save a complete timeline, path, pattern or comparison report with its source coverage, search limits and exact parameters. Reports remain available for their stated retention period even after the source analyses leave the history.
Up to 20 reports per organization, 6 MB each and 365 days. Expired reports occupy storage until an administrator purges them. Purpose, lawful basis and source rights are your declarations. Saved calculations are immutable; corrections and review decisions belong in separate records.
04 / INVESTIGATION DOSSIERS
Bring related reports together.
Link saved Atlas reports to your organization's investigations. Export their verified calculations and current review records together. A closed investigation is not an evidence approval.
Select an investigation to organize its Atlas reports.
Up to 20 report links. Each report and review keeps its own expiry. Unavailable reports leave an attachment ID and digest, and are marked missing in exports. Complete exports are limited to 12 MB; oversized dossiers are rejected without truncation. Reference snapshots have a separate export in the portal.
05 / REVIEW WORKFLOW
Give every review a next step.
Assign open reviews and corrections to your organization's reviewers. Prioritize the work, set a deadline and follow each recorded decision.
Priority is set by your team. Assignment does not approve evidence, verify independence or grant access. Deadlines must fit within record retention. A reviewer who leaves the organization or loses writing access needs to be replaced.
Revision history
Every saved version keeps its original expiry. Extending a record does not revive expired history. Deleting a record deletes all its versions. Up to 100 versions may be retained per record; administrators can purge expired versions. History before this feature's release cannot be reconstructed.
06 / RECORDS & REVIEWS
Private records
Create a record
Purpose, lawful basis and source rights are your declarations. A new review starts open until you explicitly record a decision.
Expiry immediately hides a record. Administrators can purge expired records. Revision checks protect newer edits. Deleting or reopening a review immediately blocks its delegated access.
07 / OFFICIAL REFERENCE SNAPSHOTS
Official source references
Look up exact listing references in the current official snapshot. Names, identity matching and wallet attribution are outside this lookup.
08 / REVIEWED ACCESS
Delegate one reviewed reference
Select a saved reference above, then choose a current review. Access covers that single reference in that saved analysis.
No saved reference selected.
The token is shown once and cannot access ordinary organization endpoints. Expiry, revocation, removal of the issuer's administrator role, deletion of the analysis or loss of a current review denies access.
09 / ADMINISTRATOR AUDIT
Trace access to Atlas evidence.
Inspect retained Atlas actions within your organization. Credential IDs and resource references appear exactly as recorded; they do not independently identify a person. Record bodies, report contents and secrets are not added to this view.
Empty dates select the most recent 30 days. Custom UTC windows may span at most 366 days. Pages share a snapshot for 15 minutes; loading a new snapshot includes later events. Reads and exports are themselves audited.
Exports re-read every matching event across pages, up to 1,000 events and 2 MB. Larger selections require narrower filters and are never silently truncated. CSV carries the JSON payload checksum and protects formula-like text. The checksum checks consistency of the JSON payload; it is not an independent attestation of the log.
Access, review and retention
Session identity, model versions and case review states. Access audit is available to organization administrators.