Hearth
Security
How Hearth protects your office's data, in plain terms. Everything below describes how the product works today. Open “Technical details” for the specifics.
Only your office can see your files
Your leads, deals, documents, and messages stay inside your office. Another brokerage on Hearth can never see them. Inside your office, each person sees only what their role allows, and your broker decides what the adjustable roles can do. Hearth support staff can open an office's desk only to help with support.
Technical details
Every desk page and API route checks the signed-in person's role and office on the server before returning data, not just in the browser. Roles: broker, office manager, agent, transaction coordinator, ISA; brokers adjust the configurable ones in Roles & permissions.
Your connection is private
Everything you send or see in Hearth travels in a protected, encrypted connection, so people on the same Wi-Fi can't read it. Your browser is told to always use the secure connection, and other websites can't load Hearth inside their own pages to trick you.
Technical details
HTTPS (TLS) from our host, Vercel, with HSTS. Security headers on every response: frame-ancestors / X-Frame-Options against clickjacking, X-Content-Type-Options, a strict Referrer-Policy (no referrer at all on signing, invite, and password links), Permissions-Policy, and a Content-Security-Policy. The sign-in cookie is HttpOnly, Secure, and SameSite=Lax.
Your password is never stored
We keep only a scrambled fingerprint of your password that can't be turned back into it. Passwords must be at least 10 characters, and we turn down passwords that have already leaked in other companies' data breaches. Too many wrong tries lock the account for 15 minutes.
Technical details
Salted scrypt hashes (memory-hard). Minimum 10, maximum 256 characters, no forced symbols. Breach check via Have I Been Pwned with k-anonymity: only the first 5 characters of the password's SHA-1 hash leave our server; the password itself never does. If that service is unreachable, the length rule still applies. Sign-in, invite, reset, and 2-step requests are rate-limited.
Your office's service keys are locked away
The passwords and keys your office saves for email, texting, MLS/IDX, and e-signature services are encrypted before we store them. After saving, the desk only ever shows the last four characters.
Technical details
AES-256-GCM with a server key kept outside the database (HEARTH_KEYS_ENCRYPTION_KEY). Each value is bound to its office and field, so a copied value won't decrypt anywhere else. Non-secret settings, such as a sender address, are stored as entered.
Automatic sign-out when access changes
If your role changes, you move offices, your account is turned off, or your password is reset, every place you were signed in is signed out right away. You sign in again with your current access. The desk also signs you out 12 hours after you sign in, and after 2 hours without activity (your broker can choose between 15 minutes and 12 hours), with a 2-minute warning first.
Technical details
Sessions carry the password generation, a session version, and the sign-in time; all are checked on the server on every request. Sessions last at most 12 hours from sign-in, whatever the cookie says.
Stored with a major provider, and backed up
Hearth's database runs on Neon, a managed database service. Neon encrypts the disks your data sits on and keeps a history of changes, so if something goes wrong we can bring the database back to an earlier moment. How far back we can go depends on the history window set on our Neon plan.
Technical details
Neon storage encryption: AES-256 (see neon.com/docs/security/security-overview); connections to the database use TLS. Recovery uses Neon's point-in-time restore. Hearth's own office-key encryption (where it is switched on) is described separately on this page.
Payments
Your card details go straight to Stripe, a leading payment company. They never reach Hearth's servers. Subscriptions and invoices are handled on Stripe's own pages.
Technical details
Stripe's hosted pricing table, checkout, and billing portal. Stripe's payment notices to Hearth are signature-checked before we act on them.
What we don't claim
Hearth doesn't hold SOC 2, ISO 27001, HIPAA, or PCI DSS certifications, and we don't display security seals.