Back to Lens

Trust and Credentials

Lens QR Verification Privacy

Sharing a Lens QR verification link or export can share capture context. This page explains what is exposed, what Lens mitigates, and how to share safely.

Quick read

A verification link is effectively the payload. If someone has it, they can view the encoded context. Treat these links and exports like sensitive trust artifacts.

Sharing posture at a glance

Think about a verification link the same way you would think about a document that already contains sensitive capture context.

Private share

Best option for routine verification. Send the link or export only to the person who needs it.

Broad forwarding

Risk increases as links move between teams or channels because every recipient gets the full encoded context.

Public posting

Highest exposure. Anyone who encounters the URL or export can inspect the payload, and automated discovery becomes more likely.

What Is Inside a Lens QR Verification Link

A verification URL carries encoded capture context. Anyone with the full link can open and inspect it.

Minimum fields

Capture time and location coordinates.

Often included

File name and media type indicators.

Possible metadata

Altitude, direction, and camera details.

There is no separate server-side unlock step for the payload.

Batch QR Verification

Batch mode reads Lens QR payloads from multiple files in one browser session.

Use Batch QR Verification to decode many files locally. For single-link verification, use Lens QR Verification.

  • Decoding runs in your browser tab; files are not uploaded for extraction.
  • Results are session-scoped unless you explicitly export them.
  • CSV/JSON exports can contain sensitive context; share only when necessary.
  • Each decoded file reveals whatever the source payload included.

Privacy Risks to Understand

These risks exist whenever verification links or exports are shared broadly.

Link visibility

URLs can appear in browser history and routine traffic logs.

Forwarding risk

Recipients can reshare the full link and payload context.

Public exposure

Public posting increases discovery by people and automation.

What Lens Does to Reduce Exposure

Lens applies controls that reduce accidental discovery, while acknowledging shared payload limits.

  • Verification routes are configured to discourage search indexing.
  • Crawling rules are published to reduce drive-by automation.
  • External navigation minimizes full payload referrer leakage.
  • Lens does not maintain a separate queryable copy of shared payloads.
  • Oversized payload inputs are blocked to reduce abuse paths.

These controls reduce discovery risk, but they do not remove data already embedded in a shared link or export.

How to Share Safely

Use this checklist before sending a verification link or export.

  1. 1

    Share only with people who need verification access.

  2. 2

    Avoid posting links in public channels or feeds.

  3. 3

    Use extra caution for sensitive locations or private sites.

  4. 4

    Prefer private distribution over broad forwarding.