Prepare the view
Define a justified investigation scope and period.
Linking unknown observations can create a persistent personal record even without a name. Confirm necessity, authority and retention before deployment, and require each association to remain reviewable rather than implying a verified person or continuous presence.
Catalog workflow. Confirm detector availability, permitted use and event delivery for the proposed deployment. Website examples are illustrative.
Assess unidentified-history governance

The Process
A history of candidates is not a known identity Avoid turning uncertain links into personal facts.
Define a justified investigation scope and period.
Validate the available association method on relevant footage.
Review each proposed link and retain uncertainty.
Discard unsupported associations and apply the approved retention process.
Illustrative demonstration
Example footage and simulated events explain the review workflow. They do not measure detector performance.
No matching events.
EXPLORE WHAT’S POSSIBLE
01 / 04 · CREATION OF VISIT HISTORIES FOR UNKNOWN OR UNIDENTIFIED INDIVIDUALS
Several unresolved sightings may be unrelated.
Example event: A repeat candidate is proposed.
Operator response: Compare source evidence before linking.
Practical value: Avoids mistaken histories.
Discuss this capability02 / 04 · CREATION OF VISIT HISTORIES FOR UNKNOWN OR UNIDENTIFIED INDIVIDUALS
Clothing changes across observations.
Example event: The association becomes uncertain.
Operator response: Keep records separate unless supported.
Practical value: Preserves evidence quality.
Discuss this capability03 / 04 · CREATION OF VISIT HISTORIES FOR UNKNOWN OR UNIDENTIFIED INDIVIDUALS
A proposed history exceeds its purpose.
Example event: Long-lived unidentified profiles accumulate.
Operator response: Narrow scope and retention before use.
Practical value: Prevents unnecessary tracking.
Discuss this capability04 / 04 · CREATION OF VISIT HISTORIES FOR UNKNOWN OR UNIDENTIFIED INDIVIDUALS
Use only approved source cameras.
Visibility: Appearance similarity and image quality limit links.
Configuration: No operational unidentified-history engine was verified.
Privacy: Require purpose, retention and access review before deployment.
Human review: Confirm every link and remove unsupported associations.
Discuss this capabilityFrequently asked questions
A proposed workflow for linking unconfirmed sightings into a reviewable visit history without assigning a verified identity.
No. Persistent movement histories can still concern identifiable people.
No. It is a candidate association.
No. Repeated presence does not establish motive.
No blanket tracking is justified by this catalog entry.
Find your fit
Clarify the evidence and privacy limits of repeated-sighting analysis. For Authorized investigators, Privacy governance teams.
Workflow to discuss
Creation of visit histories for unknown or unidentified individuals + Make repeat links reviewable.Discuss a camera view, a monitoring question and the review process your team needs.