Back to Lens

Lens QR Verification

Trust & Credentials

Lens QR Verification covers scan-to-verify from shared media: a Lens QR or link opens the same kind of encoded capture context in the browser. Batch QR Verification is the optional web tool that reads Lens QR payloads from many files at once—locally in your browser. In both cases, sharing a link, file, or export can share that context with the recipient.

What Is Inside a Lens QR Verification Link

A typical Lens QR Verification URL includes an encoded payload. Anyone with that link can open the page and view the details.

Minimum Fields

Location coordinates and capture time.

→
Often Included

File name and whether the media is a photo or video.

→
Possible Metadata

Altitude, direction, and app/device camera details.

Important: the link itself is the message. There is no separate server-side unlock step for the payload.

Batch QR Verification

Batch QR Verification lets you drop or select many images and videos at once and read Lens QR payloads in one session. It complements opening a single verification URL or code on the Lens QR Verification scan page.

✓
Decode stays in your browser: Files are not uploaded to Lens for QR extraction; decoding runs locally in the tab, same trust boundary as opening a verification URL yourself.
✓
Session-only by default: Closing, refreshing, or clearing the batch removes in-tab results unless you saved them.
✓
Exports are your choice: CSV and JSON downloads go where your browser saves files—share those exports only with people who should see the decoded capture context.
✓
Same payload rules per file: Each decoded Lens QR reveals whatever was encoded (time, location, and other metadata the exporter included), just like following a Lens QR Verification link.

Open Batch QR Verification for current per-batch limits and size caps shown on the page.

Privacy Risks to Understand

Link Visibility

The full URL can appear in browser history and routine internet traffic logs, similar to any other URL.

Forwarding Risk

Email, chat, and social tools pass the full link. Anyone who receives it can view the same verification details.

Public Exposure

Public posting can increase discovery risk by people and automation, even when anti-indexing controls are in place.

What Lens Does to Reduce Exposure

✓
Discourages indexing: Verification routes are marked so search engines do not list them in normal results.
✓
Discourages mass automation: Published crawling rules reduce drive-by visits, while acknowledging that some bots may ignore those rules.
✓
Limits referrer leakage: External navigation from verification pages typically shares only the site origin, not the full payload URL.
✓
No server-side payload copy: Lens does not keep a separate queryable copy of verification contents from Lens QR Verification links or from Batch QR Verification decode in the browser.
✓
Input limits: Oversized links are blocked to reduce abuse.

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

How to Share Safely

Use this quick checklist before sharing any verification URL.

  1. 1

    Share only with people who need to verify the capture.

  2. 2

    Avoid posting links in public feeds, forums, or open channels.

  3. 3

    Use extra caution for homes, private sites, and sensitive work.

  4. 4

    Prefer private channels over broad distribution.

At a Glance

Exposure

Risk

Sending a Lens QR Verification link—or sharing Batch QR Verification exports—can expose where and when capture occurred, plus other metadata you include.

Action

Best Practice

Treat verification links as sensitive trust artifacts and share only through trusted, private channels.

Related Documentation: