Back to home
DEVELOPMENT / PRIVACY DRAFT

A private workspace by design.

This is a development-stage privacy explanation, NOT a reviewed production notice. Do not enter real financial information until the operator has completed legal, security, retention, and deployment reviews.

Self-reported assessment information

If Supabase is configured, registered users can voluntarily enter a housing goal, optional self-reported score, approximate income, savings, debt payments, account nicknames, card limits and balances, and status flags. No SSN, full account numbers, credit-report uploads, or credentials for third-party services are requested.

Purpose and access

Account authentication uses Supabase. Assessment data is saved to PostgreSQL under row-level security so the signed-in user can retrieve their own information. Sharing is off by default; after you explicitly approve an enrolled agent using that agent's share code, the agent sees only your chosen label, whether your program is Rental Ready or Mortgage Ready, and aggregate completed/total checklist counts. You can revoke access in /sharing. If you separately opt in to an AI explanation request, only your housing goal, goal timeframe, a broad utilization range, and rule-based action IDs/titles/priorities/categories are sent to OpenAI. Account nicknames, scores, individual balances, income, contact details, and raw reports are excluded. The request is sent with store:false; this does not mean zero retention by the provider. Only after an AI request and fresh consent, validated AI explanations are stored with your private plan. The application retains up to twelve most recent plan versions, including action descriptions, completion flags and a private progress-change log. Plan exports may contain financial estimates and must be handled privately. A per-user date and request count are stored for rate limiting.

Data deletion

The settings page includes an account deletion request that works when the server-only administrator credential is configured. Deleting an Auth account cascades to assessment, account, plan, progress and sharing rows. Before real-client onboarding, confirm the process, vendor retention, backups, operational logs, and required disclosures.

Third parties and further requirements

Supabase and the website host may process account, network, and technical information. A production notice must document vendors, retention, safeguards, rights, contact information, and incident procedures before handling real client data.

Building toward clarity, step by step.Explore programs