Sample result detail

See how the final evidence view is structured

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.

Active 3h ago
Megan, 23
Los Angeles, CA · Tinder
Match confidence
High
Profile metadata
Age, city, activity note, and visible bio cues.
Evidence state
Screenshots grouped for side-by-side review.
Screenshot stack
Review note

This mocked view shows the detail layout only. Real orders reflect the specific apps and profiles unlocked in checkout.

Profile summary

The detail page starts with the strongest identifying cues first: avatar, name/age, location, activity signal, and app source.

Screenshot sequence

Screenshots are grouped together so the user can compare multiple frames from the same profile before drawing conclusions.

Review guidance

The page reminds users to review evidence privately and carefully rather than treating one image as a final verdict.

Evidence standard

What this sample is meant to prove

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.

  • Mock screenshots can demonstrate layout and review flow without exposing a real customer or target.
  • A strong detail page helps users compare screenshot sequence, not just the first image.
  • Downloads and proof review happen after the profile detail is opened from unlocked results.
Privacy

Why the content is mocked

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.

Next move

Use the sample, then return to the live flow

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.