Security
How we protect your building's records
A board holds owners' contact details, financial records and legal documents. This is how HearthlyOS looks after them.
- Each building is sealed off
- Every record belongs to one building, and the database itself refuses to return another building's data. If it cannot confirm which building a request is for, the request fails.
- Sign-in handled by Clerk
- Sign-in and passwords are handled by Clerk, a dedicated identity provider. HearthlyOS never stores a password.
- Two roles, set by the board
- Admins manage who is on the board. Other directors work with the building's records but cannot change who has access.
- A change log that cannot be edited
- Every change is recorded with who made it and when. The log is append-only, so entries cannot be altered or removed.
- History is corrected, not rewritten
- A wrong work record is replaced by a linked correction. The original stays, with the reason for the change.
- Documents checked on upload
- Each file is scanned for malware before anyone can open it.
Where AI fits
Where HearthlyOS suggests something, it shows the basis for the suggestion and waits for a person to accept it. Nothing it suggests is saved until someone on the board approves it.
Reporting a concern
If you think you have found a security problem, email hello@hearthlyos.com. We will reply and keep you updated until it is resolved.
Run your building on HearthlyOS
We are opening HearthlyOS to a small group of self-managed condo boards in Alberta first.