KeepableAsk with the full context dem need
Who dey ask, why, which lawful basis and how long. Templates carry the legal basis you dey rely on, so request complete before you send am instead of rebuilding am later.
Ask clearly. Keep the answer.
Ask from your verified organisation, show which information, wetin you wan use am do and how long. Person answers yes or no inside Keepable, and both sides keep request and sealed receipt.
Example to explain am
Claims assessment · one heart specialist report
- Asked
- 12 Jun · why, legal basis and how long
- Answered
- 12 Jun · approved, confirmed with passkey
- Sealed
- Receipt wey both of una hold
- Fit export
- By itself or with the full register
Wetin you fit do with am
Keep the answer, no be screenshot of checkbox
Every decision dey sealed inside receipt wey both sides hold. E shows wetin dem ask, the answer, when and say person confirm by themself. Request and decision stays together inside receipt.
Answer audit with simple search
Your return dey due every 31 March. If question na which basis you use for one customer, just search. If dem want the full picture, export register as file.
A clear request. A record of the answer.
Wetin request carries
Who, wetin, why, which lawful basis, how long and whether na once or ongoing.
Wetin answer becomes
ISO 27560 receipt, the same one person holds, wey you fit export as JSON or PDF.
Wetin audit gets
Register wey you export as file, for one person or everybody.
Questions and answers
Which lawful bases I fit declare?
The six wey NDPC recognises under GAID 2025: consent, contract performance, legal obligation, legitimate interest, vital interests and task for public interest. Only consent goes out as question; the other five go as processing notice. If law require you to use person data, you dey tell them, no be ask them. To package that as choice na its own breach.
Wetin dey inside receipt, and regulator go recognise am?
E follows ISO/IEC 27560 and carries W3C Data Privacy Vocabulary, so basis, purpose and processing na terms wey machines fit read, no be just your wording. We no store am as document: we generate am from sealed records each time, so your copy and person copy no fit change apart. Get JSON or printable PDF; na same bytes wey person holds.
Wetin e says about withdrawing permission?
Wetin you tell am, for your own words and through your channels, because na you must act on withdrawal. If you no add anything, receipt tells person to contact your company by name. E no promise button inside our app. Keepable holds request and answer records; withdrawal process na your responsibility.
I fit record ongoing permission instead of one-time use?
Yes, receipt must say which one. “You fit email me once about this” and “you fit email me until I say stop” no be the same permission. Record wey no show difference no fit prove either. You also set when permission expires.
Wetin exactly dey inside exported register?
CSV of decisions, one row per person, starting with person then your own reference for them. E derives from sealed answers, no be second copy, so no matching-up step or separate copy to reconcile.
Our return dey due 31 March. How that day go be?
Request, wording, answer, person and time were recorded when each decision happened. On 31 March, you fit read or export register without gathering those details again from different systems.
The limit
Receipt proves wetin person agree to and when. E no enforce am: nothing here enters your systems to stop process wey should stop. E gives you record wey that process should check, and record wey you fit review or export on 31 March.