Skip to main content

Default DPDPA Notice Templates

Writing a notice and its purposes from a blank page is the slowest part of onboarding onto CMP. These are three ready-to-use templates covering the scenarios almost every org needs — a general privacy notice, a cookie/tracking notice, and a standalone marketing opt-in. Adjust the wording and purpose list to match what your org actually does; don't publish these verbatim if they don't reflect your real processing.

Where these get created

Notices and purposes are authored from the Bytemonk dashboard (CMP → Notices & Purposes), not through the public API this site otherwise documents. This page is a reference for what each template contains — the wording, the purposes, and why each is set up the way it is — so you know what you're reviewing and adjusting before you publish it, whichever way you create it.

Why these purposes, specifically​

DPDPA requires consent to be specific to a stated purpose — bundling "we use your data" into one giant purpose defeats that. Each template below splits processing into the smallest units a principal can meaningfully say yes/no to independently, and marks only what's genuinely required to deliver the service as mandatory (locked-on in your widget) — everything else defaults to an honest, ungated choice.

retentionDays is set wherever the purpose has a natural expiry (marketing consent going stale after a year of inactivity, analytics data aging out) — this is enforced automatically by the platform once published, no extra work needed. Purposes tied to the account's own lifecycle (e.g. core service delivery) are left with no retention period, since "how long" there is "until the account is deleted," not a fixed window.

legalBasis values below come from DPDPA's own Sec 7 "certain legitimate uses," not GDPR's six-basis framework — see Consent Notices → Purposes for what each value actually means and why there's no general "legitimate interests" option under DPDPA.

Don't collect for minors what DPDPA prohibits outright

Section 9 of DPDPA bars targeted advertising and behavioral tracking directed at children, full stop — this isn't something a guardian can consent around. If a principal is registered with isMinor: true, your widget should never show the marketing_communications, analytics_cookies, advertising_cookies, or third_party_sharing purposes as available to consent to at all — not even as an optional toggle. See Handling Minors & Guardians for the rest of that flow.


1. General Privacy & Data Processing Notice​

Suggested noticeGroupKey: privacy-policy

Title: Privacy & Data Processing Notice

Content (starting point — replace the bracketed parts):

We collect and use your personal data to provide [Product/Service Name]. This notice explains what we collect, why, and the choices you have. You can withdraw any non-essential consent at any time from your account settings or by contacting us at [privacy contact email].

Purposes:

purposeCodeNameLegal basisMandatoryRetentionData categoriesNotes
account_service_deliveryAccount & Service DeliveryVOLUNTARILY_PROVIDED_DATA✅— (account lifetime)name, email, mobileCreating/authenticating your account and delivering core features. Can't be declined — it's what makes the product work.
customer_supportCustomer SupportVOLUNTARILY_PROVIDED_DATA✅730 daysemail, mobileResponding to your queries and support requests.
marketing_communicationsMarketing CommunicationsCONSENT❌365 daysemail, mobilePromotional emails, SMS, or WhatsApp messages about offers and product updates.
analytics_product_improvementAnalytics & Product ImprovementCONSENT❌730 daysusage dataUnderstanding usage patterns to improve the product.
third_party_sharingSharing With Trusted PartnersCONSENT❌365 daysname, email, mobile, addressSharing data with named third parties for a specific stated reason (payments, logistics, etc.) — name the actual partners/purpose in your real notice, not generically.

Suggested noticeGroupKey: cookie-consent

Title: Cookie & Tracking Notice

Content:

We use cookies and similar technologies on our website. Some are strictly necessary for the site to function; others help us understand usage or show relevant content, and only run if you agree.

Purposes:

purposeCodeNameLegal basisMandatoryRetentionData categoriesNotes
strictly_necessary_cookiesStrictly Necessary CookiesVOLUNTARILY_PROVIDED_DATA✅—device id, session dataSession, security, and load-balancing cookies. Can't be declined — the site doesn't function without them.
analytics_cookiesAnalytics CookiesCONSENT❌180 daysdevice id, usage dataAggregate usage/traffic analysis (e.g. page views, session duration).
advertising_cookiesAdvertising CookiesCONSENT❌180 daysdevice id, usage dataAd targeting and frequency capping.
personalization_cookiesPersonalization CookiesCONSENT❌180 daysdevice id, preference dataRemembering preferences (language, layout, recently viewed items).

3. Standalone Marketing Opt-In​

Use this instead of (or alongside) the marketing purpose in Template 1 if you want a dedicated opt-in flow — e.g. a newsletter signup form that's separate from account creation.

Suggested noticeGroupKey: marketing-consent

Title: Marketing Communications Preferences

Content:

Tell us how you'd like to hear about new features, offers, and updates. You can change your mind at any time.

Purposes:

purposeCodeNameLegal basisMandatoryRetentionData categories
email_newsletterEmail NewsletterCONSENT❌365 daysemail
sms_whatsapp_promotionsSMS/WhatsApp PromotionsCONSENT❌365 daysmobile
personalized_offersPersonalized OffersCONSENT❌365 daysemail, mobile, usage data

Using these templates​

From the dashboard, CMP → Notices & Purposes offers these three templates as a starting point when creating a new notice — they come in as DRAFT, never auto-published, with placeholders (e.g. "[Product/Service Name]") that need editing for your actual product before principals should see them. The tables above are what to review before you do.

To build one of these — or any custom notice — from scratch instead of starting from a template, use New Notice and add each purpose from the tables above via + Add Purpose, matching the purposeCode, legal basis, mandatory flag, retention, and data categories shown. Publish once it's ready — your widget can then fetch it via the public GET /notice endpoint. See Quickstart for the principal-facing side of this flow once a notice is live.

If you need the same notice in another language, create a new draft under the same noticeGroupKey with a different language (see Versioning Notices for how groupKey/language/version interact) — content and purpose wording should be translated, but keep the same purposeCodes so consent stays comparable across languages.