Marketing consent and opt-out
Distinguish enquiry responses, service notices and marketing, preserving choices and suppression across systems.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
Record contact provenance, purpose, notice version, choices and timestamps, and propagate suppression to every relevant system. Receiving an enquiry does not establish permission for unrestricted marketing. Check applicable requirements against PCPD guidance and the actual use of personal data.
When to use this guide
For teams synchronising contact records and preferences between forms, CRM and campaign tools.
Preference management checklist
| Data | Retain | Test |
|---|---|---|
| Source and purpose | Channel, purpose, notice version | New source and legacy import |
| Choice | Channel, category, timestamp | Permission, suppression, update |
| Sync | Master state and downstream status | Outage, delay and retry |
| Review | Actor, reason, evidence | Merge, deletion, resubscription |
Separate purposes and channels
Map enquiry handling, transactional notices and campaigns to their purposes, data and systems rather than one ambiguous permission field. Forms, preference pages and sending rules must agree. Assess business cards and public contact details in their actual context rather than assuming unrestricted use.
Propagate suppression
Assign a master preference record and prevent queued marketing after suppression while updating downstream tools. Test outages, legacy re-imports and merges for accidental re-enrolment. Minimise any necessary suppression record to its purpose rather than retaining unnecessary full profiles.
Make preference changes traceable
Retain the notice shown, choice, provenance and timestamp, distinguishing user updates from staff corrections. Require verifiable evidence for re-enrolment; a service enquiry should not automatically remove suppression. Check notices and operations against official guidance before launch.
Illustrative scenario
Hypothetical design: a customer opts out of email marketing while an enquiry remains open. Keep purpose states distinct, stop campaign queues and let staff respond to the service request. Failed preference synchronisation enters an exception queue.
Frequently asked questions
Can every enquiry enter a campaign list?
Do not assume so. Check the notice, choices and applicable requirements at collection.
Does deleting a CRM record suppress messages?
Not necessarily. Downstream lists and queued campaigns may still exist.
What matters when merging contacts?
Preserve suppression, purpose restrictions and traceable choice history.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
- PCPD: Personal Data (Privacy) Ordinance and direct marketing
- PCPD：Artificial Intelligence: Model Personal Data Protection Framework
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service