Homeowners
Service history, privacy and contact controls (09 §3.5).
No homeowner endpoint is published in this deployment
admin-api declares the homeowners:read capability and answers no homeowner route. There is no list to show and no count to report.
What this module will hold
One record per verified phone or email: verification state, language preference, every report and lead, every consent including revocations, communication preferences, the do-not-contact flag and the complaint log. Contact details are masked by default and every reveal is audited against a stated purpose (ADM-41).
Reveal masked contact detailsRequires
homeowners:read · audited on useA reveal names the field and the reason, and is recorded against the operator.Export all data for this personRequires
homeowners:read · audited on useA privacy export is an audited operation; no endpoint publishes it yet.Delete, with a deletion receiptRequires
homeowners:read · audited on useDeletion cascades under 14 §4 and records a receipt. Legal holds and the immutable ledger are not overridden by it.Anonymise report history for analyticsRequires
homeowners:read · audited on useAnonymisation is a new version of the analytics projection, never an erasure of a commercial event.