07 / For organisations

Ask clearly.Keep the answer.

Ask from your verified organisation, showing what information is involved, what you want to do with it and for how long. The person answers yes or no in Keepable, and both sides keep the request and sealed receipt.

Data sharing · processing · credit checks · medical records · marketing permissions

Inside the app

One permission, on the record

Claims assessment · one cardiology report

Granted

  • Asked12 Jun · what for, on what basis, for how long
  • Answered12 Jun · granted, confirmed with a passkey
  • Sealeda receipt, held by them and by you
  • Exportablealone, or with the whole register

  1. Ask

    You ask with the required context

    Who is asking, what for, on what lawful basis, and for how long. The templates carry the basis you are relying on, so the ask is complete before it goes out rather than reconstructed later.

  2. Record

    You keep the answer, not a screenshot of a checkbox

    Every decision is sealed into a receipt that both sides hold. It records what was asked, what was answered, when, and that the person confirmed it themselves. The receipt carries the request and decision together.

  3. Produce

    You answer an audit with a lookup

    Your return falls due every 31 March. When the question is what you were relying on for one particular customer, the answer is a search, and when it is the whole picture, the register exports as a file.

₦766m

the largest NDPC fine so far, for using people's information without permission.

NDPC · July 2025

What the ask carries
Who, what, what for, on what lawful basis, for how long, and whether it is once or standing.
What the answer becomes
An ISO 27560 receipt, the same document the person holds, exportable as JSON or PDF.
What an audit gets
The register, exported as a file, for one person or in full.

The detail

Which lawful bases can I actually declare?
The six the NDPC recognises under GAID 2025: consent, performance of a contract, a legal obligation, legitimate interest, vital interests, and a task in the public interest. Consent is the only one that goes out as a question; the other five go out as a processing notice, because somebody whose data you are using under a legal obligation is being told, not asked, and dressing that up as a choice is its own breach.
What is in the receipt, and would a regulator recognise it?
It follows ISO/IEC 27560 and carries the W3C Data Privacy Vocabulary, so the basis, the purpose and the processing are machine-readable terms rather than your prose. It is not a document we store: it is computed from the sealed records every time it is asked for, which is why your copy and the person's copy cannot drift apart. Ask for it as JSON or as a printable PDF, and it is the same bytes they hold.
What does it say about withdrawal?
Whatever you tell it to say, in your words and pointing at your channels, because you are the one who has to act on it. Say nothing and the receipt tells the person to come to you by name. It will not promise a button in our app. Keepable holds the record of the request and answer; the withdrawal process remains your responsibility.
Can I record that a permission covers standing use rather than one use?
Yes, and the receipt has to say which. "You may email me about this once" and "you may email me until I say stop" are different things to have agreed to, and a record that cannot tell them apart is not evidence of either. You also set the date it runs out.
What does the register export actually contain?
A CSV of the decisions, one row per person, leading with the person and then your own reference for them. It is a projection over the sealed answers rather than a second copy, so there is no reconciliation step and no separate copy to reconcile.
Our return is due on 31 March. What does the day look like?
The request, wording, answer, person, and time were recorded when each decision was made. On 31 March, the register can be read or exported without reconstructing those details from separate systems.

The limit

A receipt proves what somebody agreed to and when. It does not enforce it: nothing here reaches into your systems and stops a process that should have stopped. What it gives you is the record that process should have been reading, and a record you can review or export on 31 March.

Start here

Open Keepable Workspace

For developers: Exports reference.