People sign in with a one-time code, see what they agreed to, withdraw in one click and raise requests. Your team gets a queue with a countdown on each request, identity verification before anything is disclosed, and erasure that actually reaches your systems.
A shared inbox and a spreadsheet work for the first few. They do not work when the thirtieth day arrives on a request nobody owned.
The Privacy Centre is hosted by Nyvika in your name; the queue lives in your console. Both write to the same timeline.
Sign-in by email or phone with a one-time code; consents, requests and the notice in the person's language.
Access, correction, erasure, nomination and grievance, from the portal, the API or an operator on the person's behalf.
A code to the email or phone on record, or an operator's attestation, before access or erasure proceeds.
Executing an erasure withdraws every consent, instructs every connected processor, redacts the ledger and shreds the contact.
Each request shows its deadline, owner and status. Officers get a daily digest of what is due, and the overview shows what is late before anyone asks.
Days remaining against the configured period (30 by default), 90 for grievances.
An email at 9:00 IST listing what is due this week and what is overdue.
Notes, status changes and messages are hash-linked; the request register report shows who did what, when.
Every module writes to the same registers and the same hash-chained evidence, so nothing is re-keyed and nothing is lost between teams.
Withdrawals from the Privacy Centre are ordinary ledger entries, pushed to processors.
See notice & consent →Erasure instructs every processor connected to the purposes the person had.
See processors & connectors →The request register and the chained timeline are the proof you were on time.
See ledger, reports & audit →A one-time code to the email address or phone number already on record. If neither is usable, an officer can attest to identity after their own check and the attestation is recorded.
An officer raises them on the person's behalf from the console, with the channel recorded. Direct mailbox intake is on the roadmap.
A bundle with the person's consent history, current state, the processors their data was shared with and the data locations from the inventory. Generating it fulfils the request and is itself audited.
You can put a request on hold with a reason the person sees, but the clock keeps running and the overdue state is reported. Nyvika does not hide lateness; it makes it visible early enough to avoid.
Still have a question? Write to us.
Hosted in your name, in their language, with every request on a clock your team can see.