Privacy

Manual planning comes before paid Plaid sync.

debtmo starts with free manual planning and is being built toward a paid Plaid sync option with stricter server-side controls.

Get early access Try sample dashboard

Free manual planning data

The current sample planning experience stores debt, settings, challenge, and progress data in your browser local storage. Manual entry should be limited to planning-level bank and debt details while Supabase is pending.

Do not enter account numbers, login credentials, Social Security numbers, or bank routing details.

Use planning-level details such as institution names, labels, balances, APRs, payment amounts, and due dates.

You can clear local demo data from the app settings.

Early access requests

The early access form is intended to collect only contact and product-fit information. It does not ask for financial account access or sensitive identity data.

Email is used for invite timing and product follow-up.

Goal and note fields help prioritize the first product workflows.

Waitlist capture can be routed through a configured server-side webhook before Supabase is connected.

Paid Plaid sync

The planned paid sync option should use Plaid for account connection instead of asking users to type banking credentials into debtmo. It should be added only after authentication, row-level security, server-side validation, audit-friendly data boundaries, and billing controls are in place.

Plaid credentials should be handled through Plaid Link, not debtmo manual forms.

Provider access tokens and secrets must stay server-side.

Sensitive financial details should be minimized and should not be logged unnecessarily.

Authorization must be checked in Route Handlers or Server Actions, not inferred from UI state.