What we collect, what we don't, what you can do about it.

We try to keep this short. If something here isn't clear, email sean@blxze.ai and I'll explain.

What we collect

A few things:

1. What you send us. If you book a call through Calendly or email sean@blxze.ai, we receive whatever you put in those forms or messages — your name, your email, what you wrote.

2. How you use the site. Our own first-party analytics. A small script on each page records events — page views, which buttons you click, and page-load speed — and sends them to our own database. To tell visits apart it keeps a random visitor ID in your browser's localStorage (not a cookie) and gives each visit a session ID, and it records the page that referred you plus any campaign (UTM) tags on the link you arrived through. This log is pseudonymous — no name is attached unless you book a call, at which point your session is linked to your booking record. No cookies, no fingerprinting.

3. Product analytics (third-party). To see where the site confuses people, we use Microsoft Clarity (heatmaps and anonymized session replay) and Google Analytics (aggregate traffic stats). These set their own cookies and are covered by their own privacy policies. Clarity masks form fields and sensitive content by default, so what you type isn't captured.

4. What you enter in the Revenue Leak Scorecard. If you complete the scorecard, we store your email address together with the answers you gave — your trade, team size, call volume, and the other questions on the form — plus your browser's user-agent string, in our own database, so we can send you the score breakdown we promised and follow up. We do not store your IP address.

5. Cloudflare's standard request logs. Anyone serving a website behind Cloudflare gets these — IPs, timestamps, request paths. We don't review them unless we're debugging an outage.

That's it.

What we don't collect

No advertising trackers or pixels — no Facebook Pixel, no ad retargeting, no data we resell, package, or share with advertisers. No browser fingerprinting. The only cookies are the product-analytics ones described above, used solely to understand how the site is used.

Note: When you book a call through Calendly, your interaction with Calendly's widget is governed by Calendly's own privacy policy, and they may set their own cookies during the booking flow. We don't add tracking ourselves; Calendly does what Calendly does.

How we use what we do collect

Inquiries you send get used to talk to you and, if we end up working together, to deliver the service. Analytics help us see whether the site is working and where it confuses people — pseudonymous, with no name attached unless you book a call, at which point your session is linked to your booking so we can prepare for it. Request logs are for debugging outages and abuse.

Subprocessors

The third-party services we use to run the site:

• Cloudflare — hosts the website, serves the pages, and stores our first-party analytics events.

• Calendly — handles call scheduling. Their privacy policy: calendly.com/privacy.

• Microsoft Clarity — heatmaps and masked session replay, to improve the site. Their privacy policy: privacy.microsoft.com.

• Google Analytics — aggregate traffic statistics. Their privacy policy: policies.google.com/privacy.

• Google Workspace — backs sean@blxze.ai. Standard email retention.

• Stripe — processes card payments for some services. Their privacy policy: stripe.com/privacy.

• ntfy.sh — sends a push notification to my phone when a scorecard is submitted, so a lead does not sit unanswered. The notification carries the score and the recommended tier only — never your email address or any other contact detail. Their privacy policy: docs.ntfy.sh/privacy.

• Mercury — processes business banking and invoice payments. Their privacy policy: mercury.com/legal/privacy.

We don't add new subprocessors casually. If we ever do, we'll update this list.

How long we keep things

Calendly bookings: Calendly retains them under their current policy, and we also store a confirmation record — your name, email, and the scheduled call time — in our own database so we can prepare for and follow up on the call. Scorecard submissions: your email and answers are kept until you ask us to delete them. Email correspondence: indefinitely unless you ask us to delete it. Aggregate analytics: stored in our own database; we keep them as long as they're useful for understanding the site.

Your rights

You can ask what we have on you, ask us to delete it, or ask us to fix something wrong. The mailto in the footer goes to me directly. Same channel, same person, usually within a week.

If you're a Virginia resident, the Virginia Consumer Data Protection Act gives you specific rights to access, correct, delete, or port your data. If you're a California resident, the CCPA gives you similar rights. Use the same email for either — we don't run separate compliance pipelines.

Children

This site is for owners and operators of service businesses. It is not directed at children under 13, and we don't knowingly collect data from anyone in that range.

Changes

If we change this policy, we'll update the effective date at the top and post the new version at this URL. Substantial changes — like adding a new subprocessor that handles personal data — we'll note in the page itself for at least 30 days so they aren't sneaked through.

Updated July 2026 — added Stripe (payments) as a subprocessor and expanded the description of our first-party analytics.

Contact

sean@blxze.ai
BLXZE LLC, Arlington, VA.