Everything about your code, in one click.

1. 01

   The short version

   Every paid code has a one-click Export button on its detail page in your dashboard. There is no request form, no identity check, no waiting period, and no limit on how often you do it. You get a JSON file with everything about the code, plus its scan history as a separate CSV.

   This page lists exactly what those files contain, as of 2 September 2026.

2. 02

   How to export

   1. Open your dashboard and click the code or page you want.
   2. Click Export. The JSON bundle downloads immediately.
   3. For just the raw scan log, use the Download scans (CSV) option on the same page.

   Free static codes are generated entirely in your browser and never stored by us, so there is nothing to export — you already downloaded the finished file when you made it.

3. 03

   What the JSON export contains

   For every paid code, the export file includes:

   • short_id— the code’s permanent identifier.
   • redirect_url — the full qrever.com/r/… address encoded in your printed QR.
   • type— whether it is a redirect code or a hosted QR Page.
   • label— your internal name for the code.
   • destination_url— where it points right now.
   • destination_history— every URL the code has ever pointed at, each with the timestamp it changed. The complete audit trail, not just the current value.
   • status — active, or deleted_by_owner if you have retired it. There is no other status a code can have.
   • created_at— when you made the code.
   • design— the colours, frame, logo settings, and error-correction level, so you can regenerate an identical-looking code.
   • scan_count and scan_history_csv — the total, and the full scan log embedded as CSV text (also downloadable on its own, below).
4. 04

   What the scan CSV contains

   One row per scan, oldest first, with exactly these columns:

   • scanned_at— timestamp of the scan.
   • country and city— coarse location derived from the network edge. City is approximate.
   • device_type— mobile, desktop, or tablet.
   • referrer— the page the scan came from, when the browser provides one.

   There is no more than this, because we store no more than this. No IP address, no precise location, no device fingerprint, no identity for the person who scanned. See the privacy policy.

5. 05

   What a QR Page export adds

   If the code is a hosted QR Page, the export also carries the entire page so you can rebuild it on any other platform:

   • template— business card, menu, link-in-bio, event, or reviews & feedback.
   • content— every field you filled in: menu sections and items with prices, contact details, links and button labels, event date and venue, and so on.
   • theme— the page’s colours and styling.
   • rsvps— for an event page, the full guest list (name and phone) that was submitted to you.

   One caveat, stated plainly: images you uploaded are referenced in the export by their current URL on our storage, not bundled as files. While your account exists those links keep working; to hold the image files yourself, download them from the page first.

6. 06

   The static fallback is separate

   Export gives you your data. For a dynamic code, the Static Fallback on the same dashboard page gives you a working replacement: a new QR image that encodes your current destination directly and needs no redirect and no QRever. Between the two, a dynamic code can fully outlive the service. A hosted QR Page cannot become a static QR — its escape hatch is the content export above. Both are covered in reliability and the promise.

7. 07

   Deleting your data

   One code. Delete it from its dashboard page. Deletion is permanent and takes two confirmations, because it stops every printed copy.

   Your whole account. Email support@qrever.com from your account address. We complete account and data deletion within 30 days. Purchase records are kept only as long as tax law requires. Export anything you want first — deletion is real and cannot be undone.

8. 08

   Formats and portability

   The bundle is standard JSON and the scan log is standard CSV — both open in any spreadsheet, database, or script, with no QRever-specific tooling required. This is a portability guarantee under the GDPR and the UK GDPR (your right to receive your data in a structured, commonly used, machine-readable format) and it is available to everyone, everywhere, by default.

9. 09

   Operator

   QRever is operated by Sanora Technologies. For anything about export or data access: support@qrever.com.

See also: Reliability · Security · Privacy Policy · The Promise