Legal

Privacy Policy

Last updated: 12 August 2026

Conflux (“we”, “us”) runs this website to share what we’re building and to collect early-access sign-ups. We’re pre-launch — there is no live product yet — so this notice is deliberately short and covers only what a marketing site and waitlist actually do. Questions: privacy@withconflux.com.

1. What we collect

Waitlist / early-access: the details you submit — typically name, email, company, role, and what you’re building.
Analytics (only if you accept): if you click Accept on the cookie banner, Google Analytics records basic, IP-anonymised usage (pages viewed, rough location, device). Decline and none of this is collected.
Essential: a small preference cookie (e.g. your theme) and standard server logs needed to run and secure the site.

2. Why we use it

To contact you about early access and launch — because you asked us to (consent), which you can withdraw anytime.
To understand and improve the site (our legitimate interest), only with your analytics consent.
To keep the site secure and meet legal obligations.

3. Who we share it with

We don’t sell your data. We use a few processors to run the site: hosting and database (EU region where available), an email provider to reply to you, and — only with your consent — Google Analytics. Each only processes what’s needed for its job.

4. Cookies & analytics

No analytics cookie loads until you choose Accept on the banner. Choose Decline and we set nothing beyond the essential preference cookie. You can change your mind by clearing the site’s cookies in your browser.

5. Keeping & deleting it

We keep waitlist details until launch or until you ask us to delete them, whichever comes first. Email privacy@withconflux.com to be removed.

6. Your rights

If you’re in the EU/UK you can ask us to access, correct, or delete your data, or object to its use — just email us. You can also complain to your local data-protection authority.

7. Changes

As we get closer to launching a product, we’ll expand this notice (accounts, stored credentials, usage data) and update the date above.