Forms
You keep the form. Overturo keeps the record.
Organisations already collect consent in their own sign-up, lead, intake, booking and checkout forms. Overturo becomes the consent system of record behind that checkbox: the versioned wording the person read, a signed receipt they hold, a withdrawal path that reaches you, and evidence you can hand to a regulator.
What a checkbox in your CRM cannot prove
-
Which wording was shown
A boolean records a tick, not the text beside it or the version that was live that day.
-
A receipt the person holds
The person leaves with nothing; the organisation holds everything.
-
A withdrawal that reaches anything
Unsubscribing from one tool changes nothing in the others.
-
One answer across every system
The form, the CRM and the mailing tool each hold a different version of the same decision.
Four ways in
Three you build, one you connect. Every path issues the same receipt.
| Path | You need | The receipt says |
|---|---|---|
| Your form + the Overturo field | Two script tags and one element where the checkbox was. | Rendered by Overturo inside your form; shown unticked; the person's own change recorded. |
| Your form + the capture snippet | One script tag and a map from purposes to your inputs; your server commits. | Captured in your form, committed by you. |
| TypeformBeta | A connected form and a field mapping; Typeform's signed webhook commits. | Captured in a Typeform form, delivered by its signed webhook. |
| Your server: the Record API and the import | Your application credential. | Attested by you; an import keeps your original date beside ours. |
What the record proves
Overturo proves when the decision was recorded, which wording was in force, who attested it and that nothing has changed since; for a record an organisation captured in its own form, Overturo does not vouch that the control was shown unticked; for a record captured through the Overturo field, Overturo rendered the control, showed it unticked and recorded the person's own change, and does not vouch for what the page placed around it.
Every receipt names where the decision was captured and who attested it, so a reader never has to guess what Overturo saw.
A pre-ticked box is never consent
A capture states, for every purpose, the decision and how the control was shown. Overturo applies the same rule to a form it never rendered as to its own pages.
- A consent purpose shown ticked by default, or made mandatory, is refused by name.
- A right-to-object purpose left unticked is recorded as an objection.
- Your terms-of-service checkbox stays yours: it is a contract, not a consent.
What the person gets
A receipt by email with the wording as published and your organisation named, a page to withdraw from, and a way to say a record was not theirs.
What a receipt means for you →Questions
- Do I need a server?
- For the field and the snippet, your server commits the capture with your application credential. Without a server, enable browser commit on the application; its records carry a lower-assurance channel in the receipt. A connected form platform needs no server: its signed webhook commits.
- Does it work when third-party cookies are blocked?
- Yes. The field runs in its own frame and sets no cookie; a signed proof known only inside the frame authenticates the capture.
- What about my terms-of-service checkbox?
- It stays a required control of your own form. Terms acceptance is a contract purpose; the field never renders a required control.
- Does it count against my plan?
- A record captured in your form, delivered by a platform or imported counts like any hosted decision. On the free plan an Opt-ins flow includes 500 opt-in records a month, and an import is checked against what is left before it runs.
- Can I import the consents I already hold?
- Yes, in a batch with a dry run. Each row keeps your original capture date beside the date we recorded it, and rows that break the pre-ticked rule are refused by name.