Client-defined scope
The client approves the enquiry journey, required fields, response boundaries, follow-up rules and handoff destination before launch.
Security & Data
Clear data decisions before the workflow goes live.
EstateMeld is early-stage and implementation-led. We agree what is collected, where it goes, who can access it, when a human takes over and how long it is kept before a production journey begins.
Discuss your requirementsOperating principles
Purposeful collection. Agreed destinations. Human responsibility.
Data minimisation
A production journey should collect only the information needed for the agreed enquiry and agent handoff.
Human control
Agents remain responsible for advice, exceptions, property decisions and the customer relationship. A human takeover point is agreed during setup.
Visible boundaries
The assistant should identify what it can help with, avoid unsupported answers and route sensitive or uncertain matters to a person.
What is true today
Public demo and client deployments are different.
The marketing-site demo is an illustration. A client production environment is configured and documented separately.
Use fictional details only. Demo entries and ROI-calculator inputs stay in the visitor's browser and are not submitted to EstateMeld. The booking and careers forms prepare an email or WhatsApp message that the visitor chooses whether to send.
The current product code includes an embeddable website widget, a lead workspace, conversation records and configurable qualification logic. A specific hosting setup, integration, model provider and operational control are not assumed for every client.
The data fields, destination, access roles, retention period, deletion process, follow-up consent, opt-out method, providers and human handoff are agreed in writing for that implementation.
Production checklist
Decisions documented before launch.
- Purpose of the workflow and the minimum fields required
- Approved sources of property and business information
- Handoff destination, access roles and authorised people
- Human takeover triggers and prohibited AI decisions
- Consent wording, follow-up channels and opt-out handling
- Retention period, correction and deletion request process
- Hosting, AI, messaging and other providers used for that deployment
- Testing, monitoring, incident contact and change approval
No unsupported assurance. EstateMeld does not currently claim a security certification, fixed Australian data residency, a universal subprocessor list or that every deployment uses the same controls. Those details must be verified for the chosen production configuration.
Need the legal detail?