Skip to main content
LeaseRedFlag

Privacy

Privacy policy

What we capture, what we never capture, and the redaction pipeline — verifiable at the network layer.

Last updated 2026-05-08.

This is the legally-binding privacy policy. The user-facing description of the same architecture (with diagrams) lives at /how-our-analyzer-works. If the two ever conflict, that page describes the code; this page is the legal contract.

What we capture

  • Server access logs. Standard nginx logs (URL path, timestamp, IP address, user-agent). Rotated and purged on a 30-day rolling window unless required for security-incident investigation.
  • Aggregate analytics (when enabled). When site analytics is wired (post v1 soak), only anonymized page-view counts are collected, under Consent Mode v2 with analytics_storage=denied by default. No content from your paste is captured.

What we never capture

  • Your lease text.v1 has no server endpoint that receives lease content. The analyzer runs entirely in your browser. You can verify this by opening your browser's Network tab — no fetch fires when you paste text.
  • Tenant or landlord names, addresses, phones, emails. The redaction pipeline strips these locally before any pattern match runs. The redaction patterns are documented at /how-our-analyzer-works.
  • Cross-site identifiers.We don't set cross-site cookies. We don't share data with property managers, tenant-screening platforms, or marketing networks. We don't fingerprint.

Redaction patterns

The regex patterns the browser applies before any classification:

tenant_name ← (Tenant|Lessee|Resident)(?: Name)?\s*[:\-]\s*(name) landlord_name ← (Landlord|Lessor|Owner|Property Manager|Management Company)\s*[:\-]\s*(name) property_addr ← multi-line block: <house#> <street> ... <STATE> <ZIP> phone ← (\d{3})\s*[-.\s]?\d{3}[-.\s]?\d{4} email ← [A-Z0-9._%+-]+@[A-Z0-9.-]+\.[A-Z]{2,} ssn (safety) ← \d{3}-\d{2}-\d{4}

Future Pattern F tier

When the AI extraction tier ships, the same redaction pipeline runs first; only redacted text leaves the browser. Server-side request logs for the AI tier capture only site_id, request_class, success_bool, and timestamp. Request and response bodies are NULL — never logged. The kill switch (/monitor/ai-tenants pause toggle) returns 403 at the Central middleware instantly if the contract is ever broken.

Cookies

v1 sets no cookies. When analytics is wired post-soak, cookies will operate under Consent Mode v2 with ad_storage opt-in only.

Your rights

Because we don't collect personal data from your lease, the usual data-subject rights (access, deletion, portability) are not relevant to your analyzer use. For server access logs (URL + timestamp + IP), you may request information or deletion by contacting the operator listed on the about page.

Operator

Operated by a U.S. LLC (formation pending). This privacy policy applies only to the LeaseRedFlag site. Pages that link off-site (state legislature, attorney referrals, primary sources) operate under their own policies; we don't control them.