Use your authority. Check every claim.

Use a real profile only for yourself or a person who has clearly authorized you. Do not make a residency, identity, statutory-right, or authorization statement that is not accurate. Brokers may require the consumer to verify identity directly.

Residency and legal coverage are explicit user decisions. The software does not treat a postal address as proof that a law applies, and a template is not a legal conclusion about a particular request.

You are responsible for deciding whether a broker’s terms and applicable law permit automation in your situation. UnlistFast does not bypass CAPTCHAs, access controls, government-ID steps, phone codes, or unsupported mailbox confirmations. Those steps return to a person.

The current agent is dry-only and rejects UNLISTED_DRIVER=live at startup. The deterministic browser driver and read-only AI extraction adapter are dormant; configuring an Anthropic API key alone does not activate either path.

UnlistFast records submission, verification, and re-listing as separate events. A form confirmation does not prove that a listing disappeared. The project has not been independently measured on live broker accounts, broker behavior changes, and some cases will require manual follow-up.

The included letters are general templates, not legal advice. Review every request and get qualified advice when the facts or stakes call for it. No request, deadline, template, or local status is a promise of eligibility, compliance, or outcome.

Removing a public source may reduce future exposure. It cannot prove or reverse data already crawled, copied, cached, indexed, used for training, retained in model weights or memory, or reproduced in an output.

UnlistFast does not integrate with California’s Delete Request and Opt-out Platform (DROP) and does not file a DROP request. Use the state portal for that process and read its current eligibility and authority rules before submitting.

The marketing site includes a skip link, semantic headings, keyboard-visible focus, labelled status text, reduced-motion support, and layouts that reflow or contain wide tables on narrow screens.

The project has not commissioned an independent accessibility audit and does not claim certification or universal conformance. A public operator must provide a working contact for accessibility feedback and publish any service-specific accommodations it actually supports.

This repository does not identify a legal operator, privacy contact, public domain, hosting provider, or governing jurisdiction. Those facts cannot be guessed, so these project-level documents are not a complete privacy notice or commercial agreement for an unidentified deployment.

Before a public or hosted release, its operator needs to document:

• the operator’s legal identity and a working contact method;
• the host, service providers, regions, logs, and retention periods;
• the lawful basis, rights process, audience, and minors policy that apply;
• service terms, support, governing law, and dispute terms, if any; and
• payment, cancellation, and refund terms before charging anyone.

Release boundary: name the operator and deployment stack, then have qualified counsel review the facts and the jurisdictions actually served.