HōMI
Will you be okay?
Decision Readiness ScoreThreshold Compass
- READY
- ALMOST THERE
- BUILD FIRST
- DO NOT PROCEED
Educational guidance only. HōMI explains the Decision Readiness Score. It does not approve a loan, a lease, or a purchase.
Privacy · Prelaunch
Privacy, without invented certainty.
What HōMI currently handles, what stays private by default, and which legal details are still waiting on verified facts or counsel.
01
Scope and eligibility
HōMI Consumer Core v1 is being prepared for United States consumers age 18 and older. This prelaunch privacy draft describes current product behavior and founder-approved privacy policy choices. It is not yet final counsel-reviewed legal text.
02
Information HōMI may handle
Depending on the features you use, HōMI may handle:
- Account information such as your email address and optional display name.
- Assessment answers and deterministic Decision Readiness results.
- Money evidence you enter, confirm, or choose to connect through supported bank data flows.
- Decision Companion messages and the permitted deterministic context used to explain HōMI outputs.
- Subscription status and billing references needed to connect your HōMI account with Stripe billing.
- Technical and security information needed to operate, protect, and troubleshoot the service.
HōMI does not treat missing financial evidence as zero, and it preserves evidence provenance and freshness rather than describing every financial value as verified.
03
Bank connections and Money evidence
A bank connection is optional. A connected bank does not approve, deny, or automatically change a Decision Readiness result.
Plaid access tokens are server-only and stored through HōMI's protected secret boundary. Public product surfaces receive client-safe connection state and evidence labels rather than those secret tokens.
Bank-verified evidence is tied to a specific source and time. If the source is stale or requires reauthentication, HōMI should not present that evidence as currently verified.
04
Artificial intelligence
HōMI may use an external model behind A Decision Companion. The model is not the authority for Decision Readiness. Deterministic code calculates scores, pillar values, hard stops, verdicts, and money figures.
HōMI does not intentionally send Plaid access tokens, service-role credentials, API secrets, or other blocked Guardrail data to the Companion.
Provider-specific statements about model training, API retention, processing region, or data-processing agreements are intentionally not made in this draft until HōMI verifies the applicable account settings and contracts.
05
Sharing and partner access
Partner readiness sharing is dark by default. HōMI does not provide a public member readiness directory or a lender-facing Decision Readiness Score API.
A readiness share must be initiated or explicitly authorized by the member. Current sharing is designed to be revocable and may include an expiry when the product contract permits it. Partner sharing is an educational readiness workflow, not underwriting or eligibility.
06
Cookies and analytics
HōMI Consumer Core v1 is not intended to use advertising cookies or behavioral advertising SDKs. Essential authentication cookies are permitted.
Stripe-hosted Checkout or billing management may use Stripe-controlled cookies on Stripe domains. Any future analytics tool requires privacy review before HōMI adds it to production or makes new privacy claims about it.
07
Deletion and retention
Self-service account deletion and Companion message deletion are not shipped. You may contact info@homitechnology.com for an access, correction, or deletion request.
HōMI's product policy is not to retain user-owned application data indefinitely after a verified deletion request without a documented reason. Security, fraud, billing, tax, legal, dispute, provider, and backup records may require separate treatment.
Exact retention periods are intentionally not stated in this draft until they are verified against legal requirements and current provider contracts.
08
Security posture
Current verified control categories include HTTPS transport, Supabase authentication, row-level security where implemented, server-only secret handling, Vault-backed Plaid secret storage, ownership and role checks, and rate limiting where implemented.
HōMI does not claim perfect security, breach impossibility, universal field-level encryption, or a certification that has not been independently verified for the current product.
09
Privacy rights and unresolved legal clauses
Jurisdiction-specific privacy rights language, statutory disclosures, exact retention requirements, and provider-specific processing claims remain subject to counsel and verified provider facts.
This section exists so the prelaunch product does not silently fill those gaps with generic legal boilerplate.
10
Contact and policy changes
Privacy questions and requests may be sent to info@homitechnology.com. Read this with the Terms draft.
HōMI may revise its privacy text as the product and verified provider facts change. Material changes that reasonably affect member rights or data use should also receive an in-product notice or email when operationally available and legally appropriate.