Skip to content
Skip to content

Your client ticks a box that is never pre-ticked and chooses Agree and continue, we write the consent record before the page accepts any file or answer, and the record points to the exact notice version they agreed to.

Your client's link opens on the notice and the list of what you asked for. We record that the link was opened, and your audit trail shows it as "Link opened".

Your client cannot add a file or type an answer until they agree. The box is never pre-ticked, and Agree and continue stays disabled until they tick it. The law asks for a clear affirmative action (DPDP Act, section 6(1)). Our guide explains what valid consent needs. We hold the same rule on our side. Until a consent record exists for that link, we refuse every upload and every answer.

The moment they choose Agree and continue, we write two things in one step. The first is the consent record. It holds the person, the request, the exact notice version, the link the consent was given through and the time. The second is an entry on the proof record, which your audit trail shows as "Consent recorded".

A consent is given once for each link and covers the items the notice lists. If your client returns to the same link later, the consent is already on file and they are not asked again. If they do not agree, nothing is stored and no consent is recorded.

When your client has sent everything, or chosen to finish with what they have, the page shows their receipt once. It carries the notice version and the notice's SHA-256 fingerprint. The same fingerprint is stored with the notice version in your account, so the two can be compared to confirm that the receipt shows the exact notice your client agreed to. The receipt also carries the rights link, which lets your client withdraw the consent as easily as they gave it.

A client who sends only part of a request and then leaves has a consent on file and no receipt yet. The receipt and the rights link appear when the request is finished.

Two other kinds of request take consent in their own way. A request that records consent only asks your client to agree or decline, and a decline is recorded too. A consent renewal shows a fresh notice and records a fresh consent.

You can show what was agreed at any time. Your client's folder shows each consent and your audit trail lists it. Your evidence export carries every consent with the notice it was given against.

For example

Farhan Qureshi opens his link on 1 July 2027, ticks the box and sends one of two required documents. His consent is on file from that moment and his document is stored. He closes the page without finishing, so he has no receipt and no rights link yet. If he returns and sends the second document, the receipt appears then. If his link expires first, you can withdraw the consent for him from his folder.