Frequently asked questions

Yes. The import loads whatever you give it: it asks you to write where that consent came from and keeps your answer, but it verifies nothing and passes no judgement on whether that consent holds. It records that you uploaded them and from which file: that is your word, not proof from us. People who come through the consent form bring a signed proof instead, one that anyone can verify for themselves. If the file comes from a tool we know, the Forensic Engine reads its traces and keeps them apart from native proof. The full diagnosis, with the legitimate paths, is in development. An import of 25,000 rows has already run in production.

We use the official Meta Cloud API and you send only to verified opt-ins: the risk is minimal. The "Account health" tool warns you with a traffic light if anything starts to slip.

It answers about your real numbers (consents, conversions, sends) and how to use the app. You can attach PDF, Word, Excel, CSV and images: it reads, summarizes and analyzes them. It also generates images for promos and streams replies word by word.

To access the beta, submit an application. If your application is selected, you will receive an invitation and controlled access.

Each customer's data is kept separate; for every consent collected through the form you keep a verifiable proof (hash, IP, date, text), and withdrawal is one click away. The security measures are described on the Security page.

We play on the same field (sending on official WhatsApp, email and SMS, automations, flows, AI assistant, CRM, e-commerce), but we start from a different point: verifiable consent, with proof and an OTP code. We produce the proof, not a verdict on your compliance: that stays yours, and the proof is what you need to show it. You send only to those who really said yes: healthier list, less ban risk.

No. You export your audience from Mailchimp and upload it: the Forensic Engine reads the traces the file carries (when people signed up, from which network address, whether and when they confirmed) and keeps them apart from native proof. It does not invent consent. The full diagnosis, with the legitimate paths, is in development. Nobody becomes reachable just because you imported them, and a state declared by the supplier is not unusable just because it comes from outside.

Same road: you export the contacts from HubSpot and upload them. We read the columns HubSpot puts in the export, such as email confirmation status and unsubscribes, and keep them apart from the proof that is born with OptinProof. Today OptinProof sends your deals to HubSpot; reading contacts directly is among the connections coming.

Yes, it is a starting point. You upload the CSV, write where the list came from, and your answer is kept with the upload. The file does not become proof, but you do not throw it away: you know who is in it, where it came from, and from there you decide how to ask those people for the consent that is missing.

A contact left in an ad form is not, on its own, consent to receive marketing on every channel. If the ad leads to your OptinProof page, whoever signs there has full proof. Leads from the native forms of Facebook, Instagram, Google and TikTok come in from export files for now and stay contacts to be confirmed; direct connections are coming.

An acquired contact is a way to reach someone that you hold: an email, a number. A proven consent is native proof: what the person agreed to, when, on which channel and with which text in front of them. A state declared by a supplier, for example a subscriber on Mailchimp, is not that proof and does not replace it. Your word on the file stays a third fact, apart from the other two. A send follows the rules of the channel: an external contact does not become a native green, and it is not unusable just because the declaration comes from outside.

No. It reads and reconstructs the evidence your files already contain, and says clearly what is missing. It does not invent dates, texts or confirmations, and an imported contact does not become a signed consent: native proof is born only when the person signs your form.

Yes, they are one chain. Contacts carry their origin and their permissions per channel, and campaigns on WhatsApp, email and SMS start from there: they reach only people with permission for that channel, and a withdrawal turns off that channel and nothing else.

With the Business plan you manage several clients from a single account. Each client has their own space, contacts and proof, kept apart from the others; your clients' social posts go out only with your approval, and you talk to them from the panel chat.