The second bridge
Forensic Engine
Don't start over. Start from the consent you've already collected: the Forensic Engine reads the exports of your tools and keeps declared states apart from native proof.
Two bridges to the same place
New consent
Whoever signs your form from today leaves native proof: text, time, channel and confirmed code, signed and verifiable by anyone. It is the strongest proof the product can produce.
The consent you already have
People who arrived earlier, on other tools, bring states declared by the supplier: a sign-up with a date, a confirmation, an unsubscribe. The Forensic Engine reads them in the exports and keeps them apart from native proof. It does not invent consent that is not there. The full diagnosis, with the legitimate paths, is in development.
Then the same road for everyone
- Acquisition
- CRM
- Consent
- Evidence
- Verification
- Marketing
- Automation
- Measurement
- Traceability
Where the contacts you already have come from
Today, from exports
HubSpot, Mailchimp and other CRMs; your website and WordPress forms; landing pages; WooCommerce and Shopify; leads from Facebook, Instagram, Google and TikTok; legacy lists and any CSV. You download the file from the tool and bring it here.
Coming, direct connections
Reading directly from HubSpot and Mailchimp, and Meta, Google and TikTok leads without going through a file, are where we are heading, and when they arrive we will say so here. Until then the road is the export, and it is the same for every source.
A shop with 5,000 contacts on Mailchimp
Export and upload
The shopkeeper downloads their audience from Mailchimp and uploads it to OptinProof, writing where it came from. That statement is kept with the upload.
We read the traces
For each contact the Forensic Engine reads what the export carries: the date and address of the sign-up, the confirmation, the status declared by the supplier. That status stays a declaration: it does not become native proof.
Nobody leaves on the import alone
People with a trace of sign-up and confirmation, people with weak evidence, people with none: these are readings of the file, not a verdict. None of the 5,000 gets a campaign just for having been imported.
Whoever signs moves to full proof
The shopkeeper invites their contacts to sign the form: whoever signs has native proof from that moment, and from there campaigns on WhatsApp, email and SMS follow the usual rules.
An acquired contact is not a proven consent
Available evidence
This is what another tool recorded: a date, an address, a confirmation. We read each one, channel by channel: traces, revocations, contradictions and fields that cannot be read. They do not give permission to send. The full assessment of how far they hold, and of the paths to send, is in development.
Native proof
This is the proof born with OptinProof: the text read, the time to the second, the confirmed code, all signed and verifiable by anyone. It is not derived from a file: it is collected.
It reconstructs, it does not invent
An import is not proof
Uploading a list records that you uploaded it and from which file: it is your word. It stays apart from the state declared by the supplier and from signed native proof.
It does not fill gaps
If a date, a text or a confirmation is missing, the report says so. It does not make them up.
It does not open sends on its own
The evidence tells you where you stand; which campaigns go out is decided by permissions per channel and your signature, as for every other contact.
It does not make you start from scratch
You do not throw the list away: you know who is in it, where it came from and what can be shown for each person, and from there you decide the next step.
Ready to start
Your brand deserves a flawless channel
We are in invite-only beta: from “Create your account” you leave your email and we write to you when it is your turn. Meanwhile, try the demo landing page as your customer would. No credit card.