Privacy and confidentiality by design
Real estate agencies hold information about tenants, landlords, vendors, buyers, contractors, properties, payments and internal operations. NeoScript treats privacy, confidentiality and data security as core design requirements.
Privacy regulators consistently hold that privacy obligations apply to personal information entered into and produced by AI systems, and recommend due diligence, human oversight and careful control over access. Applicable privacy law generally requires reasonable technical and organisational measures to protect personal information.
Agency data remains agency data
Your agency retains ownership and control of its customer information, property information, internal documents, workflow information, communications and business rules.
Used only to provide the agreed service, subject to agreed contractual terms.
Minimum necessary access
Each Digital Worker has access only to the information and systems required for its specific role.
A Maintenance Worker does not automatically receive sales, finance or employee records.
Model use, documented
Data-handling and model-use arrangements are documented before deployment. Confidential client information is not used for unrelated client solutions or public-model training under the agreed service terms.
Claims published only where architecture and vendor terms support them.
Human oversight
Digital Workers gather, prepare, coordinate and recommend. Authorised employees remain responsible for decisions involving:
Security controls
Depending on the agreed solution, controls may include:
In-region hosting and offshore access
In-region hosted deployment and restricted offshore-access options can be considered as part of the solution architecture, based on your privacy, security and operational requirements. Where personal information is disclosed to an overseas recipient, cross-border disclosure rules generally require reasonable steps to ensure handling consistent with your local privacy principles.
Data retention and deletion
Before deployment we agree what is retained, why, where it is stored, who can access it, how long it is kept, how it is deleted or de-identified, and which legal retention requirements apply.
Confidentiality terms
Engagements may include a mutual confidentiality agreement, data-processing terms, an approved provider list, an access-control schedule, incident-response responsibilities and subcontractor terms.
Privacy Impact Assessment
For workflows involving personal information, we can document data flows, risks, controls and human oversight before production use, alongside data-breach response obligations.