Trust
Security and privacy, said plainly.
Builders trust Bindr Home with the record of every home they sell, and homeowners trust it with their home. This is how that trust is kept, without jargon and without promises we cannot show.
In short
- Each builder's records are kept apart by the database itself, and tests try to break that wall on every change.
- Sign-in uses a dedicated identity provider with emailed one-time codes; Bindr Home stores no passwords.
- Code and libraries are scanned for known weaknesses and leaked keys on every change.
- The database is backed up daily, and a builder can download all of its data at any time.
- The Privacy Policy names every service used and where information is kept, in plain English.
Each builder walled off, in the database itself
Bindr Home serves many builders from one platform, so the most important rule is that no builder ever sees another's homes, homeowners or trades. That rule is enforced by the database for every table that holds a builder's records, not only by the screens.
It is tested on every change: automated tests sign in as one builder and try every database operation, page and file link against another builder's records. Role rules for staff, such as who may approve a purchase order or change another person's role, are enforced in the database too.
Day-to-day protections
What is in place today, stated plainly.
Sign-in
Handled by a dedicated identity provider, with emailed one-time codes and bot protection. Bindr Home does not store passwords.
Roles
Homeowners, builder staff with their role titles, and Bindr Home each see only what their role allows.
Private links
Shared closeout packages, trade links and calendar feeds use unguessable links that can be revoked.
Scanned on every change
The code and its software libraries are checked for known weaknesses and leaked keys on every change; the running app is scanned on a separate test copy, never on builders' data.
Careful by default
Input is checked on the server, requests are rate limited per person, uploaded files are checked for type and size, and a browser security policy limits what each page can load.
A record of changes
Administrative and builder actions are kept in an audit log.
Backups and export
The database is backed up daily and copies are kept for 14 days. A builder can download all of its data at any time.
Errors without personal data
The app reports its own errors with homeowners' personal details removed.
Hearth and your information
Hearth reads only the parts of the homeowner's own record that a question needs. The AI providers behind it receive the question and that context, nothing that identifies the homeowner, and may not use it to train their models.
Hearth never decides coverage. A gas smell, a carbon monoxide alarm, fire or flooding gets a fixed reply with the builder's emergency lines. A builder's office cannot read a homeowner's chats; it sees only the wording of questions Hearth could not answer, without a name or address.
Where information is kept
Bindr Home relies on a small number of well-known service providers for sign-in, the database and files, email, hosting, error reports and the AI models, and each receives only what it needs for its job. Several of them store and process information outside Canada, mainly in the United States.
The Privacy Policy names every provider, says what each receives, how long information is kept and what choices people have. It is written in plain English and describes what the app actually does.
Questions people ask
Can one builder ever see another builder's homes?
No. Each builder's records are kept apart by the database itself, and automated tests try to break that separation on every change.
Does Bindr Home store passwords?
No. Sign-in is handled by a dedicated identity provider, usually with a one-time code sent by email.
Can we take our data with us?
Yes. A builder can download all of its data at any time, one spreadsheet per table.
Is information kept in Canada?
Some of the services Bindr Home relies on store and process information outside Canada, mainly in the United States. The Privacy Policy names each of them.