Kavach Privacy Note

This page explains the beta waitlist data collected on `kavachbrowser.com` during the early Kavach launch.

What the waitlist collects

The beta form may collect email, name, role, company, use case, consent timestamp, page/source values, and UTM campaign fields. The system also stores a generated submission ID and a hashed browser user-agent value for basic abuse debugging.

What not to submit

Do not submit passwords, OTPs, payment data, banking data, identity documents, health data, private customer data, confidential files, or sensitive account details.

How the data is used

Waitlist details are used to understand beta demand, prioritize onboarding, and contact people who asked to hear about Kavach. Public emails are not sent until the owner approves the sender, list, unsubscribe footer, and email platform setup.

Where the data is stored

Waitlist submissions are stored in AWS DynamoDB under the Kavach AWS account. Domain email receiving is handled through Amazon SES into a private S3 archive.

Contact

For now, contact Brilliant Minds Global through the owner-approved channel. Public role-address receiving exists for `support@kavachbrowser.com`, `privacy@kavachbrowser.com`, and `security@kavachbrowser.com`, but these routes archive mail in AWS and should not be used for password, OTP, or recovery workflows until a human mailbox provider is active.