Bali Beacon
Privacy policy
A clear starting point for a privacy-respecting launch.
UPDATED 2026-07-15
This pre-launch privacy policy describes the minimum information practices Bali Beacon intends to use. The production policy must be completed with the final legal entity name, contact address, analytics providers, email platform, advertising providers and governing-law details before public launch.
A live site may collect technical information such as device type, page views, referral source and approximate location through analytics tools. If a reader voluntarily subscribes to email updates, the site may collect their email address and related consent record. We do not sell personal information as a product.
Affiliate partners and embedded tools may use their own cookies or tracking technologies. Their practices are governed by their policies. Readers should be given a meaningful consent choice where required by law. A production implementation should not load non-essential analytics or advertising technologies until the required consent process has completed.
The final policy must state the purpose, lawful basis, retention period and recipient category for each data practice in use. It must also explain how readers can access, correct or delete personal data where applicable, how to unsubscribe from marketing messages, and how to make a privacy complaint. A browser privacy signal should be honored where required by law.
Readers may be located in different jurisdictions, so legal requirements can differ. The production implementation must be reviewed against the markets actually targeted, the final vendors selected and the data actually collected. Adding a new email tool, advertising tag or embedded booking widget is a privacy change and should trigger a policy and consent review before it goes live.
Do not send passports, payment details, health information or other sensitive information through a general contact form. The production contact details and privacy request process must be filled in before launch. This page is intentionally transparent about what remains to be configured rather than claiming a policy that has not been implemented.