Privacy (draft)
How enquiries, webinar registrations and shared documents are handled in this review build, and what changes at launch.
What we collect now
Enquiry and webinar forms store the details you submit in this site's own database. Paid checkout uses an essential browser cookie to recover and protect your checkout. Campaign source, medium, campaign name and referring page may be stored with a webinar registration; payment card and UPI details are handled by Razorpay, not collected by our form. No advertising pixel is added by this programme.
What may be collected at launch
Only what you choose to send: name, business email, document type, intended audience, required timeline and your message — plus project documents later, through an agreed secure route.
Confidential material
Confidential proposals, employee data and private meeting recordings are never uploaded to a public form. Secure sharing, access limits and retention are agreed per project before documents move.
How it would be used
Solely to respond to the enquiry, prepare the agreed scope and deliver the work. Contact data is not sold or shared. Newsletter or promotional updates require a separate, optional permission.
Third-party tools
Where AI or collaboration tools are used, they stay inside client-approved systems and permissions. Pasting sensitive client material into a random public tool is not part of the process.
Webinar registrations
Free registration stores your name, email, session, consent choices and optional campaign attribution. Paid registration additionally stores payment order and payment references, amount, currency and test/live mode. These records manage your place, payment verification, session reminders and follow-up resources. Optional programme updates require a separate permission. The essential checkout cookie lasts up to one year; your browser may also store the checkout reference and campaign attribution to recover an interrupted registration.
Email and WhatsApp delivery
Email is delivered through Resend and WhatsApp through the Meta Cloud API, each acting only as a delivery processor holding the address or number and the message text. Until those credentials are configured the programme runs in draft mode: messages are queued and previewable by the operator, and nothing leaves the site.
Message limits
Logistics messages — confirmation, reminders and the worksheet — go only to people registered for that session. Feedback, next-route and check-in emails are capped at two per address per week, and anything beyond the cap is deferred rather than dropped.
Retention and removal
Registration rows and their queued messages are kept for the running programme year, so a seat can be honoured and a session record stays complete. Ask at the support address and your registration, queued messages and log entries are deleted. Unsubscribing stops programme updates and marketing while a seat you already hold keeps its logistics emails.
Your choices
You can ask to see, correct or delete anything you have sent, and ask for project files to be removed after delivery.