The request has a deadline.The answer has a link.
DekkoCORE gives privacy officers and customer teams one end-to-end encrypted place to answer requests for personal information. Collect identity documents through a secure link, gather the records in one folder, send even very large files through a link that expires, and keep a record that the person received them.
Access request AR-2026-118Example deadline: 30 days
- Day 0Request received
- Day 2Identity confirmed
- Day 12Records gathered
- Day 20Reviewed
- Day 24Released
The problem
A right to their data, and no safe way to send it.
Under privacy laws such as Australia's Privacy Act and the GDPR, people can ask for the personal information an organisation holds about them, and the organisation has a limited time to respond.
The answer is often large: emails, account history, recordings and data exports. Too large for email, too sensitive for a file-sharing link anyone could forward, and hard to prove it ever arrived.
One request
From the request to the release.
Follow request AR-2026-118, a fictional customer's request, against an example deadline of 30 days.
Day0of 30
Request received
A customer asks for the personal information you hold about them. A Hub opens for the request, visible only to the people handling it.
- One Hub per request
- Visible only to the request team
Day2of 30
Identity confirmed
The customer uploads their identity documents through a secure submission link or QR code that needs no account. The documents are encrypted before they leave their phone.
- Submission links with no account
- Encrypted on the sender's device
Day12of 30
Records gathered
Teams add what they hold to the request's folder: emails, account history, call recordings and large data exports, with no file size limits.
- No file size limits
- Recordings play in the browser
Day20of 30
Reviewed
A reviewer checks every file and redacts other people's details. Redaction makes a separate copy, so the original isn't changed and the recipient can't undo it.
- Redaction makes a separate copy
- Recipients can't remove redactions
Day24of 30
Released
The customer gets a guest link that opens their folder and expires. The file history shows when they opened and downloaded each file.
- Guest links that expire
- A record of every download
Protections
What your privacy officer will ask.
- Zero-knowledge, end to end
- Files are encrypted on the device that uploads them. DekkoSecure can't read the personal information inside.
- Only the request team
- Each request's Hub is shared only with the people handling it, at the level each needs.
- Hosted in-country
- Hosted in Australia, the United States and Canada, so personal information stays where you keep it.
- Proof of delivery
- Every view and download is logged against the file, ready to export if the request is ever questioned.
- Links that end
- Guest links and shares expire on the date you set, and can be revoked at any time.
- Kept only as long as you need
- A data expiration policy deletes the request's files after the number of days you set.
In the product


Questions
Asked by privacy teams.
Can people send their ID without creating an account?
Yes. Send them a secure submission link or QR code, which needs no account. Their documents are encrypted on their device before they're uploaded.
What if the files are too large for email?
There are no file size limits. Add large exports in the browser or through the Upload Accelerator, then release them through a guest link that opens the folder.
How do we keep other people's details out of the release?
Redact them before you share. Redaction makes a separate copy, so the original isn't changed, and the person who receives it can't remove the redactions.
Can we show the person received their information?
Yes. Every view and download is logged against the file with the date and time, and can be exported.
What's the deadline for a request?
It depends on the law that applies to you and the request. The 30 days on this page is an example, not legal advice. Check the rules that apply to your organisation.
Answer the next request on time.
Show us how access requests reach your team and how answers go out today. We'll show you the same request in a Hub, from the ID check to the release.