Offline capture

Clinics, gyms, schools and sales offices collect most personal data in person. OptProof records consent at the front desk, over WhatsApp and from your existing lists, with the same ledger events and receipts as the website.

QR codes#

Create a location (for example "Reception, Indiranagar clinic"), then a QR code for that location with the purposes it should ask about. Download the poster or standee as a PDF and put it where people wait.

When someone scans it:

1. Their phone opens your hosted notice on my.optproof.in, with a language picker limited to the languages you have published.
2. They enter their mobile number and confirm it with a one-time code.
3. They choose purposes, with nothing pre-ticked, and submit.
4. OptProof records the consent with channel: "qr", the location and, if staff showed them the poster, the staff member's id. The person sees the receipt on screen, and receives it by email when they confirmed with their email address. (Receipts by text message come later.)

Each QR code has a short code you can disable at any time, for example when a poster is taken down. A disabled code stops accepting consent.

Kiosk mode#

Kiosk mode turns a tablet at reception into a consent station locked to one property and location.

1. In the console, open Kiosks and register a device. You get a pairing link, shown once. Open it on the tablet.
2. A staff member unlocks the kiosk with their personal PIN. Each consent taken while they are signed in records their staff id.
3. The visitor reads the notice in their language, enters their phone number, confirms the one-time code and makes their choices.
4. After 60 seconds without a touch, the kiosk clears the screen and goes back to the start, so the next visitor never sees the previous visitor's details.

Kiosks send a heartbeat, so the console shows when each device was last seen. Unpair a lost tablet from the console and its token stops working immediately.

WhatsApp Phase 3#

Send a templated consent message from your WhatsApp Business number. The person taps a button to agree or refuse, and OptProof records the reply with channel: "whatsapp" and a receipt link. A later withdrawal, on WhatsApp or anywhere else, propagates like any other.

Because WhatsApp has no opt-out API, OptProof checks consent before it sends any template on your behalf. If you send WhatsApp messages from another tool, use the WhatsApp opt-out list connector or check consent through the server API first.

Import existing consent lists#

If you collected consent before OptProof, on paper forms, in Excel or in another tool, you can bring it in with its evidence.

1. Prepare a CSV with one row per person: a phone number or email, the purposes they agreed to, and the date they agreed. Other column names are fine; you map them during the upload.
2. In the console, open Imports, upload the CSV, and attach an evidence file such as a scan of the signed forms or an export from the old tool.
3. Describe where the consent came from (for example "Paper intake forms, Jan–Sep 2026"). This description is stored with the batch.
4. OptProof records each row as a ledger event with channel: "import", the original date as occurred_at, and a link to the batch.

Imported events are clearly flagged as imported everywhere they appear. They carry no notice version, because no OptProof notice was shown. If you are unsure the original consent meets today's standard, start a re-consent campaign from the batch: OptProof asks each person again by SMS, email or WhatsApp and records their new answer.

You can also import over the API with POST /v1/imports (up to 5 MB of CSV inline).