Customer records
Property records, tenancies, notices, messages, visits, approvals, documents, and related operational data are intended to remain part of the customer’s operating record.
Data ownership
The intended commercial posture is that the customer controls its operational record and can extract the records it needs for handover, audit, reporting, or dispute preparation.
TenancyOps materials
The platform software, branding, code, product design, and related materials remain part of the TenancyOps product and IP stack unless agreed otherwise.
Third-party service data
Some data may also be processed by hosting, messaging, storage, or other service providers used to operate the platform.
Export posture
The goal is to reduce lock-in anxiety by making export expectations visible, not to rely on vague promises after the relationship is already under strain.
Operational exports
Exportable records may include property-linked registers, communications, notices, visit logs, compliance records, and document metadata where supported.
Evidence packs
The product is designed around producing evidence-ready exports and supporting records so operational context does not need to be rebuilt manually later.
Exit preparation
Customers should raise any provider-specific export requirements before production rollout so they can be handled deliberately rather than at the end of the relationship.
Offboarding steps
The intended offboarding posture is structured rather than ad hoc.
Step 1
Agree the exit date, export scope, responsible contacts, and any special migration or transfer requirements.
Step 2
Prepare and deliver the agreed exports or handover package, including any agreed evidence or record registers.
Step 3
Disable or close access, then handle retention or deletion steps in line with the contract, legal obligations, and operational needs.
Retention and deletion
Final retention and deletion rules should be confirmed in the customer’s binding agreement and any legal obligations that apply to that customer’s records.
Retention
Operational and backup retention periods should be agreed and documented before a customer depends on the platform for production records.
Deletion
Deletion should be handled in a controlled way after export, access closure, and any required legal or contractual retention period.
Important limits
This page is a public summary, not legal advice and not a substitute for signed customer terms. Customers with unusual export, retention, or jurisdiction requirements should raise them before production rollout.