Profile summary
The detail page starts with the strongest identifying cues first: avatar, name/age, location, activity signal, and app source.
This mocked detail page shows the kind of profile summary, screenshot stack, and review guidance users see after unlocking results. Everything here is reconstructed to protect privacy.
This mocked view shows the detail layout only. Real orders reflect the specific apps and profiles unlocked in checkout.
The detail page starts with the strongest identifying cues first: avatar, name/age, location, activity signal, and app source.
Screenshots are grouped together so the user can compare multiple frames from the same profile before drawing conclusions.
The page reminds users to review evidence privately and carefully rather than treating one image as a final verdict.
The point of this page is not to imitate a real customer file. It is to show the structure of the unlocked detail view before a user commits to checkout.
We do not expose real customer screenshots, names, cities, or timestamps publicly. Sample pages are reconstructed so the trust question gets answered without violating privacy.
If this resolves the “what will I actually get?” question, the right next step is to go back to the search flow while the lead is still current.
Use these pages to move from trust-building into the live flow or the broader sample package.
Begin the live intake if the sample detail answered the proof-format question.
See the broader report packaging beyond the single detail-view example.
Review anonymized use cases that show how users moved from teaser signal into proof.