0067. Jev duplicate check sends many landlords’ addresses to TypeSafe

Status: Accepted (2026-09-26)

Context

TypeSafe Jev judges whether two landlords’ properties are the same home (design: docs/superpowers/specs/2026-09-26-typesafe-jev-duplicate-check-design.md). Each call sends one property’s address plus up to 10 candidate addresses owned by other landlords. ADR-0064 accepted sending a listing’s own address when that listing is submitted. This check sends more: The TypeSafe terms from ADR-0064 still apply: no training on customer data, no fixed retention on the standard plan, US hosting. An address with a unit number can identify a person.

Decision

Send the address fields (type, building, address line, unit, area, city, state, postcode) of the subject and the candidates, unredacted. Never send ids, owner names or emails. Gremlin is the accountable owner of this trade-off, as in ADR-0064. TYPESAFE_RENTAL_DUPLICATE_ENABLED is separate from TYPESAFE_RENTAL_ENABLED and stays off by default. Turning it on is gated on:
  1. Gremlin confirming the landlord-facing disclosure covers addresses of properties that were never submitted, sent to TypeSafe for duplicate checks.
  2. Calibration (design §6.4) using only synthetic pairs by default; real addresses need an explicit opt-in flag, gated on the same confirmation.
  3. The pre-enable candidate-count check (design §5.1) returns 500 or less. This is not a privacy gate. It stops the backfill from starting while any postcode overflows the candidate cap.

Consequences

  • The backfill queues every live-mode property with a postcode once (design H9), so a later or concurrent deploy never re-queues them. The first time the switch is on, the sweep works through that queue within about a day. It sends addresses only for a subject that has candidate pairs: the subject plus up to 10 candidates. A subject with no candidates makes no TypeSafe call. Data already sent cannot be recalled.
  • Properties with a blank postcode are never sent (design H19).
  • Admins see two landlords’ properties and identities side by side on the Duplicates page. They already see this data in the listing review queue, so no new access is granted.
  • The listing check can be enabled without enabling the duplicate check.
  • A zero-retention plan or a decision to send less data would supersede this ADR.