Data we handle
Estate administrators may store member profiles, household records, dues, payment evidence, meeting records, documents, signatures, gate activity, incidents, supplier records, and feedback submitted by testers.
Privacy
Last updated: 2026-07-03. Hoodly is built for estate records that need tenant isolation, access control, and auditability.
Estate administrators may store member profiles, household records, dues, payment evidence, meeting records, documents, signatures, gate activity, incidents, supplier records, and feedback submitted by testers.
The data is used to run the estate workspace, verify access, reconcile obligations, preserve decision evidence, and help platform operators support the deployment.
Tenant business data is stored in tenant-isolated schemas. Server-side permissions decide who may read or change a record; UI state is not treated as authorization.
Operational and audit records are retained for the estate lifecycle unless an agreed offboarding process says otherwise. Immutable audit and signature evidence is not silently edited or deleted.
For privacy questions, contact the Hoodly launch team or the estate administrator responsible for your workspace.