Industry playbook

DPDP for agencies (India): client-territory playbook

Audience: account leads, paid media, ops, freelance leads · Last reviewed: March 2026

Agencies process clients’ customers’ data while controlling martech, drives, and contractor access. DPDP turns vague MSAs into questions about subprocessors, purpose limitation, and provable deletion on churn. Pair with DPA review, vendor checklist, and marketing team norms.

Treat each major client as a data territory: separate ad accounts, workspaces, and export policies—shared Business Managers and root drives are where stories break.

30-day playbook

  1. Week 1 — Territory audit: List client workspaces (Meta, Google, ESP, CDP). Remove shared “test” audiences.
  2. Week 2 — MSA alignment: Subprocessors, deletion SLAs, India data handling—match roles to ops.
  3. Week 3 — Contractors: Access tiers; ban raw list downloads to personal devices policy-wide.
  4. Week 4 — Offboarding script: Client churn checklist—exports deleted from Figma, Loom, Slack Connect.

Lifecycle

  1. BD: Your own prospects—not mixed with client warehouses.
  2. Ingest: Lists, creatives with PII in comments, UGC rights.
  3. Execute: Day-to-day campaigns; experiments that duplicate audiences.
  4. Exit: Stale exports in personal Downloads and “archive” drives.

Martech grid

Agency-side layers (customize)
Layer Govern Questions
Ads / CAPI Pixels, catalogs, offline imports Client consent vs your enrichment; audience overlap across brands
ESP / CRM Journeys, suppressions Sync latency after unsubscribe; shared IP pools?
Collaboration Notion, Figma, Slack Connect PII in comments; guest access expiry
Reporting BI templates Accidental unions of client datasets

Disclosure: Categories for planning; we do not sell top placements. Tool comparisons may later include affiliate labels per editorial policy.

Failure modes

Illustrative hypothetical (fiction, not factual): “NorthRiver Digital” debugs a Klaviyo sync by downloading a suppressed list to a personal sheet. Months later another client’s campaign reuses a tab template and overlaps emails. Fix: client-scoped workspaces, expiring links, and MSAs that name subprocessors—territorial discipline, not another consent banner.