Log in
Skip to content
LotContext
Sign in

LotContext privacy

Privacy

Last updated: October 15, 2026

LotContext stores account email addresses, submitted property searches, generated report snapshots, source-status metadata, and usage events needed to run and improve the product.

Sign-in is handled by Google Identity Platform (Firebase Authentication). It stores your email address, a password hash if you set a password, and the Google account link if you sign in with Google. LotContext stores your email address and the identity provider's account identifier, never your password.

Report data is assembled from public NYC datasets. Account data is used to authenticate users, save report history, prevent abuse, understand product usage, and support customer requests.

Cookies and browser storage

We use necessary cookies and local browser storage for encrypted sessions, authentication, fraud prevention, and to remember your privacy choice. These functions are required for the site to operate securely. We also use a first-party event ledger and, only after you allow optional analytics in the cookie preference center, Google Analytics 4 to measure search outcomes and feature usage. We never send email addresses, names, exact addresses, BBL/BIN values, report identifiers or contents, authentication tokens, or free-text search input to Google Analytics; only coarse, allowlisted event names and categories are sent. LotContext does not use PostHog or any other browser session recording. Analytics is rejected by default and its script does not load or transmit data until you allow it. You can accept all, reject non-essential storage, or customize your choice; changing your mind is available at any time through “Cookie settings” in the footer or your account settings. We ask again after six months or when this preference model materially changes.

Account, verification, sign-in, and support email is sent from lotcontext.com through Resend. Support replies route to a monitored inbox.

Stripe processes paid subscriptions on Stripe-hosted checkout and billing pages. LotContext sends Stripe your account email, an internal account reference, and the plan you selected. Stripe Checkout collects billing name and address for payment processing, fraud prevention, and, when enabled, tax calculation. Stripe may also collect device and network signals for fraud detection. LotContext does not receive or store card details. We retain Stripe customer, checkout-session, and subscription identifiers plus a minimized event ledger for access, cancellation, dunning, deduplication, and financial reconciliation; the ledger excludes email, name, billing address, tax IDs, device signals, and report or property contents.

Demo and professional access requests

When you request a demo or professional access, we store your name, work email, organization, role, intended use, optional message, the page you came from, and the campaign tags in the link you followed (for example utm_source). We use them only to reply and to understand which outreach reaches professionals. They are visible only to LotContext operators, are never sent to Google Analytics, and are not shared or sold. Ask us through support to delete them at any time.

If you choose to answer property-brief pricing research, we also store your selected price hypothesis and preferred improvement with your request. These are preferences, not an order or payment authorization. Aggregate research events contain only fixed categories, never your contact details or message.

If we contact you first, we record your name, organization, role, any business contact details you published, and our notes, so we do not contact you twice or after you ask us to stop. Tell us to stop and we will delete the record.

Service providers

These providers process data on LotContext's behalf:

  • Google Identity Platform: sign-in, email verification, and password reset.
  • Google Cloud: the application database and storage of retrieved public records.
  • Fly.io: application hosting and server logs, including IP addresses.
  • Sentry: error reports, with credentials, tokens, and share links removed before sending.
  • Resend: delivery of account, alert, and support email.
  • NYC Planning GeoSearch: receives address text (not account details) to place addresses that are not yet in LotContext's index.
  • OpenFreeMap: serves map tiles directly to your browser, so it receives your IP address and the map area you view.
  • Cloudflare Turnstile, when enabled: a bot check on account creation and the support form.
  • Google Analytics 4: only if you allow optional analytics.
  • Stripe: only when paid checkout is open (described below).

Transactional account messages are separate from product announcements. Creating an account does not add your address to a marketing broadcast list. Questions or requests about your data can be sent through the support page.

Signed-in users can delete their sign-in from Settings after every open subscription is canceled. That action removes credentials, sessions, and alerts, then detaches temporarily retained report, saved-property, and usage history from the deleted identity. The retained history is not accessible to the deleted account or a later account using the same email. Contact support to request a data export or permanent purge of retained account history.