Privacy & data protection

Every request, on the clock.

Each regulation brings its own request types and deadlines. Switch between them: the due date is stamped the moment a request arrives, and overdue requests raise alerts.

Pick a regulation

Windows are reference values for planning, not legal advice.

The life of a request

From an email in the inbox to proof it was handled

Request logged
Type, requester, regulation
Due date stamped
From the regime's window
Owner assigned
Reminders as it nears due
Fulfilled
Resolution notes recorded
Disposed
Erasure proven with evidence
The registers

Four registers, filed in one place

Open a folder. Each one is a working register in CompliLens, not a template.

Rights & consent

Rights requests answered on the clock

A log of consents you have collected and requests people make about their data.

Privacy laws (DPDP, GDPR and others) give people rights and set strict response deadlines.

How it works
  1. In Consent Register, record each consent: who, for what purpose, through which channel, when given and when withdrawn. Use Withdraw when someone takes consent back.
  2. In Data Principal Requests, log each request: choose the regulation (for example DPDP or GDPR), then the type (access, correction, erasure, grievance, or regime-specific types).
  3. CompliLens calculates the legal due date automatically from the regulation's response window.
  4. Track status: Received → In progress → Completed or Rejected, assign an owner and record the resolution.
  5. Overdue requests show in red, and reminders are sent before the deadline.
app / privacy / consent
Data principalPurposeChannelStatus
a.sharma@…Marketing emailWeb formGiven
+91 98•• ••42Order updatesCheckoutGiven
j.wong@…AnalyticsCookie bannerWithdrawn
r.iyer@…LoyaltyStoreGiven
Example
A customer asks to erase their data under GDPR. The request is logged on day 1, a due date 30 days out is set, and it is completed on day 12 with notes.
Classification

Know how every kind of data must be handled

A list of the kinds of data you hold and how each must be handled.

Not all data is equally sensitive, and laws limit how long you may keep it.

How it works
  1. Add a data category (for example "Customer PII," "Financial records").
  2. Pick a classification level: Public, Internal, Confidential or Restricted.
  3. Record the retention period, the legal basis, the disposal method and an owner.
  4. Restricted categories are also used as a safeguard so AI features avoid exposing related content.
Publicwhile live
Marketing site content
Internal3 years
Wiki and meeting notes
Confidential7 years after end
Customer contracts
Restricted8 years · excluded from AI
HR and payroll records
Disposition

Prove data and devices were destroyed properly

A record that data or equipment was properly destroyed.

"We deleted it" needs proof: when, how, by whom, and who verified.

How it works
  1. Add a record: choose customer data, employee data, or asset.
  2. Link what was disposed of: an asset, a DPDP request, a portal user, or type an external identifier for things not in CompliLens (a paper file, an outside system).
  3. Record the method, date, who did it and who verified it, plus a disposal reference (for example a destruction certificate number).
  4. Attach the certificate as evidence.
  5. Optionally mark the asset as disposed in the same step.
Disposal · Laptop LT-009Verified
FieldValue
SubjectAsset · Corporate laptop
MethodCertified disk wipe
Disposed byIT operations
Verified byCompliance manager
ReferenceCERT-WIPE-2211
Certificate attached as evidence
Regulations

Nine regulatory clocks, built in

A built-in catalog of privacy and cyber laws with their deadlines.

Deadlines differ by country. CompliLens already knows them, so nobody has to look them up.

How it works
  1. The catalog covers CERT-In, DPDP (India), GDPR (EU), UK GDPR, CCPA (California), PDPA (Singapore), LGPD (Brazil), POPIA (South Africa) and the EU AI Act.
  2. Each entry holds the reporting window (for example 6 or 72 hours) and the types of data-subject requests that law recognises.
  3. In Context, you select which laws apply to you. Those then appear as options on Incident and Data Subject Request screens.
  4. CERT-In and DPDP are always on.
RegimeIncident windowRequests
CERT-In6 hours—
DPDP—30 / 90 days
GDPR · UK GDPR72 hours30 days
EU AI Act48 hours—
CCPA—45 days
PDPA72 hours30 days
LGPD · POPIA—15 · 30 days
Nine regulations, one register

Every deadline you owe, side by side

Turn a regulation on and its request types, response windows and incident clocks apply across CompliLens straight away.

IN
DPDP ActIndia · data principal rights
Requests30 daysGrievances 90 days
IncidentsNone setNo fixed hours
IN
CERT-InIndia · cyber incidents
RequestsNoneNot a rights law
Incidents6 hoursFrom detection
EU
GDPREuropean Union
Requests30 daysPer request
Incidents72 hoursTo the supervisory authority
UK
UK GDPRUnited Kingdom
Requests30 daysPer request
Incidents72 hoursTo the ICO
EU
EU AI ActSerious AI incidents
RequestsNoneNot a rights law
Incidents48 hoursStrictest tier
US
CCPACalifornia
Requests45 daysOpt-out in 15
IncidentsNone setNo fixed hours
SG
PDPASingapore
Requests30 daysPer request
Incidents72 hoursTo the PDPC
BR
LGPDBrazil
Requests15 daysPer request
IncidentsNone setNo fixed hours
ZA
POPIASouth Africa
Requests30 daysPer request
IncidentsNone setNo fixed hours

Windows are reference values for planning, not legal advice.