Why verification exists
Typical social-proof apps stop at a badge. Recently can open a public event page that shows what powered the notification: event type, when it was captured, and which store it came from — without inventing activity.
Event pages
When a shopper taps Verified (or equivalent) on a notification that has a public id, they land on /events/:id on recently.cloud. That page replays the notification and lists forensic meta: date, time, timezone, source, and store.
- Only events published for public proof appear
- Sensitive fields stay redacted according to merchant settings
- Each page has a stable public id for support and sharing
Store profiles
Merchants who opt in get a public profile at /stores/:handle — store name, optional blurb, and a grid of recent public events. Featured stores can appear on the stores directory.
Merchant settings
In the Recently app, open Public profile to configure:
- Enable or disable the public profile
- Choose a public handle (slug)
- Opt into the featured directory
- Control whether first names appear on public events
- Turn verification / public proof publishing on or off
Developers embedding or mirroring proof data can use the public read API. It only exposes what merchants have opted to publish.