Sign in

Security · Privacy · Audit

Built like the legal record it has to be.

An HOA board holds sensitive data on every household in the community. We built HomeownerHub so the security posture is the product, not a checkbox.

Illustration · AI run log

AI runs. Logged. Cited.

Each AI workflow run is recorded with its workflow and prompt version, the model, an input hash, the output and its citations. Drafts still wait for the board.

stream homeownerhub.eventlog

  • covenant-brain · Answered query: "Can residents paint their fence?"

    tenant=madison_park model=gpt-oss-120b

    Bar C

  • violation-drafter · Generated notice for 211 Oak St · trash bins

    tenant=madison_park model=gpt-oss-120b

    Bar B

  • meeting-minutes · Drafted minutes from transcript · captured 4 decisions

    tenant=madison_park model=gpt-oss-120b

    Bar B

  • reply-drafter · Drafted inbox reply · contact details removed first

    tenant=madison_park model=gpt-oss-120b

    Bar B

  • bill-scan · Read vendor bill · Green Lawn Co. · sent to Approvals

    tenant=madison_park model=gpt-oss-120b

    Bar B

  • covenant-brain · Answered query: "Are satellite dishes allowed?"

    tenant=cumming_hoa model=gpt-oss-120b

    Bar C
per association · readable by its board and adminssample entries, not real activity

Encryption everywhere

TLS 1.3 in transit. AES-256 at rest. Encrypted backups. Customer documents are stored in scoped, signed-URL-only object storage with short-lived access tokens.

Tenant isolation at the DB layer

Postgres Row-Level Security scopes every read and write to your association. Integration tests check the RLS policies on every CI run, and a failure blocks the merge. A bug here is treated as severity-1.

AI providers, named

Answers are generated by open-weight models (OpenAI gpt-oss) served by Groq, and document search uses an embeddings provider. They see only what an answer needs: when the assistant looks up an owner, the AI gets placeholders instead of the email and phone number, and inbox drafts have contact details removed first.

AI runs are logged

AI workflow runs are recorded in a run log: workflow and prompt version, model, input hash, output, citations and status. Only your own board and admins can read your association’s runs.

No training on customer data

We never train models on documents you upload. Period. We use anonymized synthetic fixtures for eval, never real customer text.

Operating + reserve fund separation

For HOA boards: operating and reserve are separate funds in the general ledger, and a database trigger rejects any journal entry that doesn’t balance within each fund. Moving money between funds has to be an explicit transfer.

Security posture at a glance

For your security team, your insurance carrier, or your own peace of mind.

Encryption at rest
AES-256
Encryption in transit
TLS 1.3
Backups
Managed by Supabase
Tenant isolation
Postgres RLS
Auth
Supabase · email magic link or password
Inference
Groq API · open-weight models
AI run log
Per association, board-visible

Have a security question, vendor risk assessment form, or DPA request? Email support@homeownerledger.com. We reply within one business day.