lease-findr

Privacy Policy

Last updated 2026-11-02 · Effective date: 2026-11-02

This policy explains what lease-findr collects, why, and who it's shared with. lease-findr is operated by lease-findr. Contact: [email protected].

1. What we collect

WhatDetails
AccountYour email address, your display name and a Firebase user ID. This comes from Google or from the email sign-in link.
Saved searchesMake, models, years, trims, ZIP code, search radius, inventory types and the lease defaults you set.
Your activity on listingsFavorites, tags, notes and saved lease deals you add to cars in your results.
Dealer messagesIf you use Deals: dealer emails you forward or paste in, the notes and calls you log, dealer reps, quotes and follow-up dates. See section 2.
Credits and billingYour credit balance and ledger: purchases, search charges, the starter credit, refunds and any manual adjustments. Also an identifier that links your account to your Stripe customer record.
Technical recordsStandard server and security records, such as IP address and request time. Kept for up to 30 days.
Usage eventsWhich pages and features you use, collected by lease-findr itself (no third-party analytics): for example a page view, a saved search, a run, an offer written or a help topic opened, with the time, your account ID, and your device type (desktop or phone) and browser family. They hold no messages, notes, VINs, dealer names, ZIP codes or email addresses, and no IP address. On the public home page they aren't linked to an account. If your browser sends Do Not Track or Global Privacy Control, the app sends no page or click events from your browser; actions our server handles for you, such as signing in or saving a search, are still counted.
Cookies and browser storageOne essential session cookie (HttpOnly) that keeps you signed in. The Firebase sign-in library keeps its sign-in state in your browser's storage. lease-findr also saves your theme, filter presets and lease settings in your browser's local storage; they never leave your device. Cloudflare may set security cookies (such as __cf_bm) to filter bot traffic. Checkout happens on Stripe's own site, under Stripe's cookie policy. We don't use advertising or analytics cookies.

We never see or store your card number. Stripe handles card payments.

2. Dealer messages

If you use Deals, lease-findr stores what you give it about your talks with dealers:

Before a message is stored, we strip numbers that look like Social Security numbers, card numbers, bank account numbers, ID numbers and birth dates. This works by matching patterns, so it can miss some. Please don't forward credit applications or other documents that contain this kind of information.

3. How we use it

We don't sell personal data, and we don't run advertising.

4. Who we share it with

We share data only with the service providers we need to run lease-findr:

ProviderWhat they handle
Google (Firebase Authentication)Sign-in with Google or an email link.
Google CloudHosting in the United States, and Google Cloud Storage for database backups. Backups are stored in Google Cloud Storage in Iowa, United States (us-central1), encrypted at rest by Google.
CloudflareThe network in front of the service: DNS, TLS and traffic filtering. Cloudflare also receives the dealer emails you forward to your lease-findr address (Email Routing) and passes each message to our server (an Email Worker).
StripePayments through Stripe Checkout, and the payment records that go with them.
ResendDelivering the service emails listed in section 3.
Our vehicle-listings data providerVehicle listings. When you run a search, its settings (make, model, year, search area as a ZIP code and radius, states or nationwide, and inventory type) are sent to the provider to fetch listings. The provider doesn't receive your name or email from us.

Some parts of the inventory and sign-in pages load directly from other servers. Your browser contacts them itself, so they see your IP address and which site asked, but we send them nothing about your account:

ServerWhen, and what it receives
cdnjs (Cloudflare)The map library, when the inventory page shows the map. The inventory page also opens a connection to it in advance.
OpenStreetMap tile serversMap images for the area you're viewing, while the map is open.
Dealer and listing photo hostsThe listing's stock photo, when you open a car. Your browser doesn't tell them which page it came from.
Google (gstatic.com)The Firebase sign-in library, on the sign-in page.
Leasehackr (leasehackr.com)Only if you open a calculator link. The link sends the lease inputs (price, MSRP, residual, money factor, term, mileage, fees, tax rate) and a note with the car's year, trim, VIN, stock number and dealer name. Leasehackr is a separate website with its own privacy policy. It is not affiliated with lease-findr.

5. Where data is stored

The service runs on Google Cloud in the United States, with Cloudflare in front of it. Database backups are stored in Google Cloud Storage.

6. How long we keep it

7. Deleting your account

You can delete your account yourself: on the Account page, open Credits, then Delete account, and type your email to confirm.

8. Your choices

9. Security

Connections to lease-findr are encrypted with HTTPS. Sign-in is handled by Firebase, and the session cookie is HttpOnly, so scripts in the page can't read it. No system is perfectly secure. If we learn of a breach that affects your data, we'll tell you as the law requires.

10. Children

lease-findr isn't meant for children. You must be 18 or older to use it. We don't knowingly collect data from anyone under 18; if we learn we have, we delete it.

11. Changes to this policy

We may update this policy. For material changes we'll tell you by email, at least 30 days before they take effect.

12. Contact

Privacy questions and requests: [email protected]