Privacy Policy

This policy describes what PropPencil collects, what it is used for, and your choices. The short version: we collect the minimum needed to run the product, we never see your card number, and we do not sell your data.

1. What we collect

• Account data — your username, a salted hash of your password (never the password itself), and an optional email address used for receipts and account recovery.
• Usage data — the property addresses you analyze, your saved pencils, assumptions and search history, so they follow your account across devices.
• Billing data — handled entirely by Stripe. We store only your Stripe customer ID and subscription status. Card numbers never touch our servers.
• Technical data — server logs (IP addresses, timestamps) for security and rate limiting. Rate-limit records store a one-way hash of your IP, not the IP itself.

2. What we do with it

• Run the product: analyses, saved state, plan limits.
• Process subscriptions and send billing receipts (via Stripe).
• Prevent abuse (rate limiting, duplicate-account detection).

We do not sell or rent your personal information, and we do not use third-party advertising or cross-site tracking. The only cookie we set is the session cookie that keeps you signed in.

3. Who else sees data

• Stripe — payment processing (your email, if provided, and payment details you enter on Stripe's pages).
• Vercel (hosting) and Neon (database) — our infrastructure providers, which process data on our behalf.
• Data providers — the address you analyze is sent to the sources that price it (U.S. Census geocoder, HUD, BLS, FEMA, and, where configured, ATTOM and Mashvisor). It is not linked to your identity in those requests.
• Authorities, if legally required.

4. Retention and deletion

Account and usage data are kept while your account exists. To delete your account and its data, email luke.f.miller.8@gmail.com from your account email (or include your username) and we will remove it within 30 days, subject to records we must keep for tax and billing compliance.

5. Security

Passwords are hashed with scrypt; sessions use signed, httpOnly, secure cookies; all traffic is encrypted in transit. No system is perfectly secure — use a password you don't reuse elsewhere.

6. Changes and contact

Material changes to this policy will be noted here with a new date. Questions: luke.f.miller.8@gmail.com