All traffic to and from Home Health Intel is served over TLS. Data at rest in Supabase Postgres and storage buckets is encrypted by the platform. Photos, report PDFs, and images from your walk are stored in a private bucket, and our servers send them only to a signed-in account that is allowed to see that report. Some files from earlier reports are still held in an older file store, where anyone who has a file’s exact link can open it. Those links are long and random, so they cannot be guessed, but they are not access-checked. Report emails include a link to your PDF that opens without an account for 7 days.

Accounts are managed by Supabase Auth. Passwords are never stored in plaintext. Supabase hashes them using industry-standard algorithms. We support email-based password reset and plan SSO and MFA in a future release.

Database access uses Postgres Row Level Security (RLS). An account can read or modify only its own properties, assessments, photos, and reports, plus the reports described under “Who can see your report” below. RLS is enforced at the database layer, not just the app layer. A few server routes, such as the shared summary link and the photo route, read with a service key that bypasses RLS, and those routes check access themselves.

You, as the account the property belongs to. A report can also be seen by:

• The contractor who ran it, if a contractor ran the report on your home. They keep access after you claim it.
• The fire department team, if a member of a fire department ran the walk. A walk you start yourself, including from a department’s link, is not visible to the department.
• Anyone who has the report’s summary link. The summary shows the address, the HealthIntel score and grade, and the top findings.
• Home Health Intel staff with admin accounts, who can see reports and photos to run and support the service.

We do not share, sell, license, or syndicate your reports to carriers, agents, contractors, or data brokers.

Our subprocessor list lives on the privacy policy. If we add or change a subprocessor in a way that affects how your data is handled, we update that page and email account holders.

Every photo is SHA-256 hashed on upload and the hash is bundled into the NGDS JSON record, so anyone holding the report can check that a photo has not been altered since upload. A photo small enough to upload as it is keeps any embedded data your camera wrote, such as the time and place it was taken. Larger or HEIC photos are resized or converted first, which removes that data. We do not read or store it separately. C2PA + PAdES-LTV PDF signing ships in a later phase once our commercial X.509 certificate is issued. Today’s PDFs are unsigned but the evidence bundle hashes give downstream readers a verifiable chain.

Supabase performs continuous Postgres backups for our project. We also take an encrypted daily snapshot of the database, stored in a private bucket that only our servers can read. Reports stay in your account until you delete them. When you delete your account, your photos, report PDFs, and images are deleted from storage 30 days after your request. Backups taken before then are not changed, so they still hold a copy of your data.

If you find a security vulnerability, please email info@homehealthintel.com with the subject line “Security”. Please give us a reasonable window to investigate and remediate before public disclosure. We don’t currently run a paid bug-bounty program, but we credit researchers who report responsibly.

Out of scope: denial-of-service, social engineering, physical attacks, and reports that require physical access to a user’s unlocked device.

If a security incident affects your data, we will notify you by email within 72 hours of confirming the impact, along with what we know, what we’re doing about it, and what you should do.