Digital Personal Data Protection Act · Control TR-001 · Priority: high · Component: Transparency

What this control covers

Provide a standalone privacy notice to data principals at or before seeking consent. The notice must be: (i) clear, plain, and not embedded in Terms & Conditions; (ii) specify all personal data collected and purposes; (iii) explain how rights under DPDPA may be exercised; (iv) provide details of how to complain to the Data Protection Board; and (v) provide DPO contact details. Objective: Ensure data principals are fully informed before giving consent, making all consent legally valid under the DPDPA.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

GCP

Use Cloud KMS with customer-managed encryption keys (CMEK) for BigQuery, GCS, and Compute. Sensitive Data Protection (DLP API) inspects/de-identifies PII at scale.

Google Workspace

Enable client-side encryption for Drive/Docs and turn on Drive Labels + DLP rules to prevent external sharing of regulated data classes.

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.

Signed policies, procedures, and registers document the safeguard. Focus: Standalone Privacy Notice.

Quick checklist

  • Ensure — Standalone Privacy Notice
  • Provide — Standalone Privacy Notice

Related articles on this site