Mortgage Dorks

Privacy Notice

Last updated: June 27, 2026. This notice describes the current Learner OS v0 launch surface and the provider-backed activation path.

What we collect

If you join the waitlist, we collect the email address you submit plus basic context such as where the form was submitted, your selected role, interest level, and experiment attribution.

If you use Learner OS v0 before account sync is activated, profile and progress data primarily stay on your device. When account sync is activated, signed-in profile, progress, and learner event data may be stored in the Mortgage Dorks database.

When analytics is configured, we collect intentional product events such as CTA views, waitlist submissions, role selections, and learner progress events. Browser autocapture, automatic pageview/pageleave capture, and session recording are disabled for V0.

How we use it

We use waitlist data to send launch updates, community invitations, and related Mortgage Dorks notices.

We use learner data to save progress, improve the learning experience, understand which content is useful, and keep the product safe and reliable.

For client learner analytics, learner identifiers are hashed before analytics identification and raw learner email is not sent as an analytics identify property.

We use operational logs to diagnose failures. Logs should use hashed identifiers or local metadata where possible instead of raw email addresses.

Providers

V0 is built to use Clerk for authentication, Postgres for durable learner storage, Beehiiv for waitlist/newsletter capture, PostHog for product analytics and A/B testing, and Skool for the community link once configured.

Some providers may not be active until production credentials are attached. The launch health endpoint reports which provider integrations are still activation-required.

Your choices

You can choose not to join the waitlist or not to create an account.

If you want your waitlist or learner data reviewed or removed, contact the Mortgage Dorks team through the current launch channel.

Browser controls may let you clear local storage, block cookies, or limit analytics scripts.

This notice is a product transparency document for launch readiness, not legal advice. It should be reviewed before full credential-backed production activation.