Free tool . nothing uploaded

Consent receipt generator

Fill in what you are actually processing. Get back a machine-readable consent record in the ISO/IEC TS 27560 structure, plus the plain-language receipt a person should be handed.

Everything runs in this page. There is no server call, nothing is stored, and it keeps working offline. A tool that harvested your data while helping you document consent would refute itself.

The organization accountable for the processing.
Country or region code.
Use an internal pseudonymous id. Do not put a real name or email in a record you will pass around.
One specific purpose. If you have three purposes, you need three processes, and honestly three separate asks.
Comma separated. Name the categories, not every column.
Semicolon separated. Leave blank if nobody else receives it.

What this actually produces

Two artifacts, because the standard separates them. The consent record is what you keep: the full structure describing the processing, the parties, and the consent event. The consent receipt is what the person gets: a short object that identifies itself and points at the record. That split is why a receipt needs only three mandatory fields while a record needs the substance.

The output is JSON-LD using DPV, the W3C Data Privacy Vocabulary, because published work maps the ISO structure onto DPV terms. That matters for a boring but important reason: the field names below are not invented for this page, so another system can read the file without a bilateral agreement with you first.

The field groups

A record requires one data subject, at least one process, storage conditions, and event information. If you cannot fill those in for a purpose you are already processing under, that gap is the finding, not the form.

What it does not do

It does not make you compliant, and nothing can. Consent is valid because of how you asked, not because of how you filed it: freely given, specific, informed, unambiguous, and as easy to withdraw as it was to give. This tool gets the plumbing right. It is engineering scaffolding, not legal advice, and it does not check your answers against reality.

It also cannot prove the consent happened. A record you generated about yourself is a claim. Proof needs an issuer whose signature someone else can verify, which is the harder problem and the one we work on.

Why we built this

Because the same gap keeps showing up. Everyone can write a consent record. Almost nobody can hand a third party something that proves a specific human agreed to a specific thing at a specific time, and then revoke it later and have the revocation actually land. Pupul is the layer for that: identity a person owns, that travels only where they send it, and that they can pull back with one action.

See what that looks like for an AI product, or watch a revocation take effect in two beats.

Grounded in ISO/IEC TS 27560:2023 (ISO catalogue) and the published DPV mapping in Implementing ISO/IEC TS 27560:2023 Consent Records and Receipts for GDPR and DGA. The standard itself is paywalled by ISO; field groupings here follow that published mapping. Not legal advice.

Pupul, Inc.  ·  Privacy  ·  Other free tools