Misuse data
Do not use the platform to access, copy, disclose, or export records outside authorised role scope or customer authority.
Use the platform for lawful rental-operations work
TenancyOps is intended for lawful property-management, communication, workflow, and record-keeping purposes. It must not be used to facilitate unlawful conduct, harassment, fraud, or unauthorised disclosure of personal information.
What users must not do
Abuse the service
Do not overload, interfere with, probe, scrape, reverse engineer, or attempt to bypass platform security or access controls.
Send unlawful or misleading content
Do not send unlawful notices, misleading claims, spam, harassment, malware, or unsafe files through the platform.
Role-based use expectations
Property managers
Property managers should only invite users, share records, and trigger workflows they are authorised to manage for their agency or branch scope.
Tenants, owners, and contractors
External users should only use the role-specific views and should not attempt to access unrelated records or accounts.
Internal teams
Internal users should protect account credentials, use exports responsibly, and avoid storing unnecessary personal information in free-text notes or uploads.
Fair-use and cost-heavy features
Some product capabilities may be subject to fair-use, plan-based controls, or separate commercial scope where they create unusually high cost or operational risk.
Examples
Messaging volume, export volume, file storage, heavy media use, bulk broadcasts, custom integrations, and unusual support needs may be controlled commercially.
Why this matters
It keeps the platform economically sustainable without pretending every high-cost behaviour is automatically included with no limits.
Enforcement
TenancyOps may need to suspend access, restrict features, or take other protective action where misuse, security risk, or unlawful conduct is identified.
Important limits
This page is a public summary, not legal advice and not the full customer agreement. Production customers should receive binding acceptable-use language in the final contract pack.