Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 6 min read

Consent management implementation checklist

A grouped implementation checklist for consent: lawful basis, notice, collection points, withdrawal, audit records, vendors, deletion and testing.

E
EncryptTechBD · 0 comments
Two people shaking hands across a table
Photo: Kristin Hardwick / StockSnap

Consent management is usually bought as a banner and then discovered to be an operating process. The banner asks a question. The hard work is proving, months later, what a person agreed to, when, through which channel and with which version of the notice. Without that record, a consent programme is a design preference rather than a control.

This checklist is for a business handling customer data in Bangladesh: an online store, a clinic, a coaching centre, a service company or a distributor. Bangladesh's Personal Data Protection Act, 2026 makes the record-keeping duty explicit, and the operational detail sits with the business, not the banner vendor. It is an implementation aid, not legal advice. Work through the groups in order, assign an owner and keep the evidence.

Before you start: scope and lawful basis

  • List every category of personal data you collect and every purpose you use it for.
  • Decide which purposes rely on consent and which rely on another lawful basis, such as performing a contract or meeting a legal obligation.
  • Map the populations involved: customers, prospects, students, patients, employees, suppliers and their contacts.
  • Map the channels: website, app, checkout, WhatsApp, phone, paper forms, events and marketplaces.
  • Review existing consent records and identify gaps before choosing a tool.

Evidence: a data map and purpose register approved by the business owner. Owner: operations or compliance lead.

1. A notice people can actually read

  • Write the notice in plain Bangla and English, with the same meaning in both.
  • State what is collected, why, who receives it, how long it is kept and how to withdraw.
  • Use a layered notice: a short summary at the point of collection and the full notice one click away.
  • Give a contact route for questions and complaints, not just a generic email address.
  • Version and date every notice so old consents can be tied to the text people saw.

Evidence: published notice with a version identifier and a readability review. Owner: marketing with legal review.

2. Collection points and defaults

  • Inventory every form, checkout, app screen, call script and paper form that collects personal data.
  • Use separate, unticked choices for separate purposes. Do not bundle marketing consent into terms acceptance.
  • Collect only what the purpose needs; every extra field increases risk and deletion work.
  • Make the "no" option as clear and as easy as the "yes" option.
  • Check that call-centre scripts read the notice and record the answer consistently.

Evidence: screenshots or copies of each collection point, with the notice version and date. Owner: product or digital lead.

3. Preference centre and withdrawal

  • Put a working preference link in every marketing message and on the website.
  • Make withdrawal as simple as giving consent, with no extra steps or retention arguments.
  • Propagate the change to the CRM, email platform, SMS gateway, WhatsApp tool and analytics within a defined window.
  • Maintain a suppression list that survives list imports and campaign builds.
  • Record the withdrawal itself, not only the resulting opt-out status.

Evidence: an end-to-end withdrawal test with timestamps showing propagation to every system. Owner: CRM or customer operations lead.

4. Records and audit trail

  • Store who consented, when, to which purpose, through which channel and against which notice version.
  • Keep the exact wording shown, not a paraphrase.
  • Protect the log from edits; corrections should create a new entry, not overwrite history.
  • Link the consent record to the customer record without duplicating identity data unnecessarily.
  • Define how long consent evidence is retained after the relationship ends.

Evidence: a sample audit trail for ten records, including one withdrawal and one re-consent. Owner: data or engineering lead.

5. Vendors, tags and data flows

  • List every tool that can see or set consent: analytics, advertising pixels, CRM, messaging, call recording, survey and support tools.
  • Check that tags fire only after the relevant choice, and that declined tags stay off.
  • Put purpose limitation and breach notification duties into vendor contracts.
  • Record any cross-border access or storage and the safeguards around it.
  • Re-audit tags after every website release and campaign template change.

Evidence: a vendor register with data categories and a tag audit report. Owner: marketing operations with procurement.

6. Retention, deletion and exceptions

  • Set a retention period for each purpose, not one blanket period for all data.
  • Document how deletion works across production, backups, exports and third-party tools.
  • Define legal-hold and dispute exceptions, with who can approve them.
  • Test a deletion request and record the result, including what could not be deleted and why.

Evidence: a deletion runbook and one completed test with a dated record. Owner: IT or data protection lead.

7. Testing and monitoring

  • Sample consent records each quarter and trace them from collection to use.
  • Review complaints and unsubscribe failures as signals, not as isolated admin issues.
  • Add a consent review to the launch checklist for new forms, campaigns and integrations.
  • Report coverage and defects to management with owners and dates.

Evidence: quarterly test results, a complaints log and a remediation list. Owner: compliance lead.

Verification: what good looks like

  • A new customer can complete a form and see the exact notice version they accepted.
  • A withdrawal reaches every system within the promised window, and the suppression survives the next import.
  • A sample of ten records traces from collection to use without a missing timestamp.
  • A deleted record is gone from production, exports and the tools that copied it.
  • A new campaign cannot go live without a consent review.

If any of these fail, the programme is still a banner. Fix the process before adding another tool.

Common mistakes

  • Treating a cookie banner as the whole programme while forms and call scripts stay unchanged.
  • Recording a checkbox state without the notice version or timestamp.
  • Letting a new campaign tool become a shadow consent system.
  • Making withdrawal possible only by emailing a generic inbox.
  • Keeping consent records forever and personal data longer than needed.

Metrics

  • The share of collection points with a current notice and tested consent control.
  • The share of consent records with a complete audit trail.
  • Withdrawal requests completed within the defined window.
  • Tags firing without a valid choice, measured in a monthly audit.
  • Deletion requests completed and evidenced.
  • Consent-related complaints and the time to resolve them.

Where this fits

If you need the data map, notice design and audit trail built together, start with Managed Technology & Cybersecurity. The pricing page explains how assessment and implementation are scoped. For a sector example of consent and retention in practice, read how student data privacy obligations change year by year.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes