Data Ownership
Owner-controlled records and exports
PropertyWork should be designed so business owners can access, export, back up, and review their own operational records without losing control of critical property data.
Business records
Property records, work history, expenses, receipts, proof uploads, messages, payment records, documents, check-ins, and analytics belong to the business context that created or received them, subject to role permissions.
Exports and backups
Owners/platform admins should be able to generate exports and backups. Backup bundles should clearly state whether they include the database only, uploads, documents, photos, or the full bundle.
Access control
Workers and supervisors should only see records they are permitted to view. Owner-only financial and sensitive records must remain restricted unless the owner explicitly shares them.
Support-view logging
Support access must be visible and audit logged. Support View should be used only for testing, troubleshooting, and assisted setup.
Leaving or migrating
The product should support practical export/backup workflows so owners are not trapped without their records if they need an accountant, migration, archive, or manual review.
Review before launch
Final customer-facing data ownership language should be reviewed against the actual hosting, storage, backup, retention, and subscription model before public paid launch.