This is not a production-ready privacy policy
The final policy must reflect the actual website, analytics, forms, cookies, subprocessors, WhatsApp data flows, retention periods and legal obligations.

This page is intentionally a structured placeholder and does not constitute legal advice.

The final policy must reflect the actual website, analytics, forms, cookies, subprocessors, WhatsApp data flows, retention periods and legal obligations.


Document the categories of personal data collected, purposes and legal basis, consent and opt-out processes, cookie and analytics use, third-party processors, cross-border transfers, retention, security controls, data-subject rights, grievance contact and governing law.
Explain how business messaging data moves through WhatsApp, Tick-Twice, connected systems and authorised teams. Identify controllers, processors and access responsibilities based on the actual deployment.
Publish an approved privacy or grievance contact for Tick-Twice and Kevys Techserv. Do not use a generic address without confirming operational ownership.

No. The supplied static package contains a clearly marked legal draft that requires review and approval before publication.
It should cover collected data, processing purposes, cookies, analytics, processors, WhatsApp and Meta data handling, retention, security, rights, grievance contact and jurisdiction.
Qualified legal, privacy, security and business owners should approve the final text based on the actual production implementation.