Due dates, not legal decisions
Privacy Requests can help teams track due dates, but your team still makes the final call.
Product
A simple path from request to response
Privacy Requests gives your team one place to receive requests, review them, get help from others, send the response, and keep a record.
Inside the workspace
Keep the request, the work, and the decision together
An access request usually needs more than one person: someone to review it, someone to find records, and someone to approve the response. Each handoff stays connected to the case, so the owner can see what is ready and what still needs attention.
What the team produces
- A request with a named owner and a reviewed due date.
- Documented identity checks and findings from data sources.
- An approved response with explicitly selected files.
- A delivery record and a case export for later review.
Request flow
Every request has a clear next step
Instead of turning every request into a custom project, Privacy Requests keeps the handoffs simple and the record complete.
- IntakeReceive access, deletion, correction, and other requests through a hosted portal.
- VerificationReview identity, ask for more information when needed, and record why the request moved forward.
- AssignmentSend follow-up to the right people without losing context.
- EvidenceCollect notes, files, and findings in one place instead of scattering them across email and chat.
- ResponsePrepare the response, review it, and keep the decision attached to the request.
- Delivery and auditShare response materials through controlled links and keep the timeline of actions and decisions.
Operational control
Built for teams that need a clear process first
Your team can see what came in, who owns it, what is blocked, what has been approved, and what still needs attention before a response goes out.
Approvals stay human
Verification, disclosure, deletion, correction, response approval, and closure stay reviewable.
Built for proof later
Important actions create a history so your team can review how a request was handled later.
Daily operations
See the work that needs attention
A case list is not enough when deadlines, handoffs, and approvals compete for attention. Privacy Requests gives the team a clear operating view of what is due, blocked, unassigned, or ready for the next step.
Priority queues and saved views
Open focused views for overdue work, unassigned requests, verification, response approval, or the queues your team returns to every day.
Reminders and escalation
Set reminder thresholds and send alerts before a deadline becomes an overdue request.
At-a-glance case status
Track active work, overdue cases, completion time, and recent closures without rebuilding the picture in a spreadsheet.
Configured intake
Support more than one product or brand without splitting the work
Create distinct public portals or let people choose the product they use. Each flow can collect the right details, show the right guidance, suggest a jurisdiction for your team to review, and route the new case to the right team.
- Brand, product, and request-type-specific intake flows.
- Structured location details for jurisdiction suggestions that staff can review.
- Configurable ownership, priority, and task-template routing.
- One workspace for the complete case record.
What is included
The core tools your team needs
Hosted requester portal
Give people a clear way to send a request and reduce incomplete messages in personal inboxes.
Case inbox and filters
Sort by status, owner, request type, and other context that helps the team act quickly.
Task assignment
Turn follow-up into assigned work instead of informal reminders.
Response templates
Prepare consistent response language while still leaving final review with your team.
Secure delivery
Share sensitive response materials with expiring links, revocation, passcodes, and access history.
Audit history
Keep the timeline, status changes, owner changes, delivery actions, and closure notes together.
Requester status
Give requesters a secure status link with a clear next step, while keeping internal notes and case materials private.
Review before delivery
Use review checklists and human approval before sending a response. Attachment checks flag potentially sensitive information for reviewers to check.
Checks before closing
Before closing a case, confirm that verification, fulfillment, approval, delivery evidence, and the export record are complete.
People and boundaries
Know which part of the work belongs to whom
Give each person the access they need and rehearse the review handoff before your first live response.
| Responsibility | Work in Privacy Requests | Work your team still owns |
|---|---|---|
| Administration | Invite members, configure portals, and manage workspace settings. | Decide who should have access and keep membership current. |
| Case ownership | Review identity, assign work, prepare the response, and coordinate delivery. | Decide scope and handling, with advice where needed. |
| Contribution | Complete assigned tasks and attach findings to the case. | Search or change records in the relevant source systems. |
| Response approval | Approve your own response, or use designated reviewers for a separate approval step. | Review the proposed disclosure and document the decision. |
Privacy Requests coordinates request handling. It does not automatically discover personal data across your systems, carry out deletions, or decide whether a response meets a legal obligation.
Get started
Set up a workspace and handle the next request in one place
Start with a hosted portal and a simple process. Add more structure as your team needs it.