Privacy
PropertyQuarry keeps search preferences, listing context, generated media, and shared links scoped to the property decision they support.
Property preferences, shortlist decisions, uploaded documents, and delivery history are handled as property-workflow data, not generic assistant memory.
Shared property pages and tour links are separate publication events. They should expose only the redacted details needed for review.
What the product stores
The app can store account identity, saved search preferences, search history, shortlist decisions, feedback, generated review files, tour history, and delivery settings.
- Exact addresses, documents, and internal source URLs stay private unless a user explicitly shares a redacted page or file.
- Preference learning is used to improve ranking for the account and must stay separable from cross-customer analytics.
- Connected services should use the narrowest practical permission set for the selected workflow.
User lifecycle controls
Account export, deletion, shared-link revocation, session revocation, and retention controls are first-class product responsibilities.
- Search history and research output should be removable without deleting the entire account.
- Public share links need expiry and revocation, not just hidden navigation.
- Delivery channels need clear opt-in, opt-out, and quiet-hour controls.
Listings from external sites are external content, but the user's brief, ranking, feedback, documents, and decisions are account data.
Public tours should use a narrow public manifest. Private listing URLs and exact-location details stay out of public tour files.