For Individuals & Families

When AI can imitate your child's voice, your face, your writing, or your authority — your family needs a proof home.

A cloned voice can call at night and ask for money. A fake message can carry a relative's name. PlenaProof does not stop the scam — it helps your family agree in advance how to check, and keep a clear record afterwards. Build a family code-word, a trusted-contact list, a "do not send money until verified" rule card, an incident log, and a report packet you can hand to a bank, the police, or a platform. Everything below is built on your own device.

Front-end preview   No real charge   Nothing leaves your device

Honest limits. PlenaProof is not a lawyer, a court, a bank, the police, or a government office, and it cannot stop a scam or reverse a payment. What it gives you is a receipt — a dated record of what happened and who was involved — that you can keep and share. We help you keep the proof; we do not stop the scam. A receipt is a record, not a verdict on who is right.

Build your family defense pack

Five plain steps. Fill in what you can, skip what you cannot, and save or print at the end. Your answers stay in this browser unless you choose to print or save them yourself.

Step 1

Family emergency code-word

Agree on one word your family says to confirm a real emergency. If a caller cannot say it, treat the call as unverified — even if the voice sounds exactly right.

Choose something not on social media. Change it if it is ever used out loud to a stranger.

Step 2

Trusted-contact list

List the people your family will call back to verify — on a number you already know, never a number from the suspicious message.

Name · relationship · a number you already trust.

Step 3

"Do not send money until verified" rule card

A printable card for your family. The default rules:

  • No money or codes are sent on a voice or video call alone.
  • We hang up and call back on a number we already know.
  • We ask for the family code-word.
  • Urgency and secrecy are warning signs, not proof.
Step 4

Incident log

Record what happened: a cloned voice, a fake message, a screenshot. Note the date, who or what it imitated, and where it arrived.

Step 5

Report packet — for a bank, the police, or a platform

PlenaProof turns your entries into a clear cover message and an evidence index you can send. It does not contact anyone for you.

This packet organises your own record and a request for review. It does not promise that any bank, platform, or authority will act, and it is not legal advice.

Your report packet

Fill in the steps above, then select “Generate report packet & receipt”.

Incident receipt

A dated, self-attested record of what you logged. It is checked with a fingerprint (a SHA-256 hash) of its own contents — there is no signing key and no outside authority behind it.

No receipt yet.
QR placeholder
(public check
not yet live)

Your Vault is a preview that saves to this browser only. Nothing is uploaded.

Human Reviewer of Record Available in pilot

The part AI cannot do: a named person who confirms they looked at your record. You can fill this in now; co-signing by a verified reviewer is offered in pilot, not yet live. PlenaProof never adds a signature you did not enter yourself.

This block is optional and is included in your receipt only if you fill it in.

Why a code-word and a call-back beat any clever reply. A scam built on a cloned voice depends on speed, fear, and secrecy. A code-word your family agreed on, plus a call-back to a number you already know, removes the one thing the imitation cannot fake: a shared secret and a trusted channel. PlenaProof helps you set that up before a crisis, and keep the proof after one.