Privacy, with the actual product in mind

EDITH may collect the information you enter directly, including income, expenses, debts, account balances, due dates, planning inputs, and feedback you choose to submit.

If you connect financial institutions, EDITH receives account and transaction data through Plaid so it can ground balances, recent activity signals, and connected-account views.

EDITH also collects limited product analytics, such as event data, onboarding completion state, and session-level behavior signals used to improve the beta experience.

Manual EDITH inputs can be saved locally in your browser on the device you are using. That local browser copy may include the financial information you entered, such as bills, debts, due dates, and account values.

EDITH also stores a small amount of device-level state locally, such as theme preference, welcome-flow completion, and analytics/session identifiers that help the app work consistently.

If you use EDITH only in manual mode and do not choose to save a server-side snapshot, your planning inputs can remain device-local.

Signed-in Wealth users may have server-side records that support account access, plan entitlement, synced account views, Plaid connections, transactions, feedback, product events, and manual financial snapshots they explicitly choose to save.

Connected institution data may include institution name, account metadata, balances, recent transactions, sync state, and encrypted Plaid access tokens. EDITH does not store your financial institution login credentials.

If you choose to save your manual data to your EDITH Wealth account, that manual snapshot may also be stored on EDITH's servers separately from synced account data.

Plaid handles the secure connection between EDITH and your financial institution. EDITH receives the account data Plaid is authorized to share, but EDITH does not receive or store your bank username or password.

Disconnecting an institution from EDITH removes the active connection and deactivates the synced data tied to that connection inside the product. Manual data you entered separately is not treated as the same source.

Connected coverage can still be partial. If only some accounts are synced, EDITH may combine synced data with manual data and label the result accordingly.

EDITH uses your data to generate planning guidance, calculate runway and debt metrics, surface timing-aware alerts, show connected-account state, improve product quality, and maintain the security and reliability of the service.

EDITH does not sell your personal financial data. EDITH may rely on service providers that help deliver the product, such as hosting, authentication, analytics, and financial-data infrastructure.

If EDITH offers paid subscriptions, payment processing is handled by Stripe. EDITH does not store your full card number. Stripe may collect billing details needed to process subscriptions, manage renewals, handle failed payments, and comply with legal obligations.

EDITH may store limited billing metadata tied to your account, such as subscription tier, customer ID, subscription status, and Stripe session or invoice references.

Some EDITH outputs are calculated estimates. Timing-sensitive guidance depends on the due dates you enter or the connected timing data EDITH can actually read. If that timing data is missing, EDITH falls back to average-based estimates instead of claiming exact precision.

You remain responsible for reviewing your accounts, confirming real bill dates and balances, and deciding whether to act on any recommendation.

EDITH uses product analytics during beta to understand what is working, where users get stuck, and which parts of the experience need refinement. This may include event tracking and session-level product analysis.

Today that can include third-party analytics tooling used to improve the beta experience, such as PostHog, Google Analytics, and Microsoft Clarity.

EDITH does not use this analytics layer to build an advertising profile or sell user behavior data.

Connected financial data is currently supported through Plaid and may expand over time. The exact scope of synced balances, transactions, and future connected bill data may evolve as EDITH's connected mode matures.

EDITH will continue to distinguish between what is read from connected sources and what is inferred from manual entries or incomplete timing data.

You can keep using EDITH manually without connecting institutions. If you connect accounts, you can later disconnect them from Data Controls.

If you saved manual inputs only on your current device, resetting EDITH on that device clears the saved browser copy and reloads the demo profile.

During beta, broader data or account-deletion requests are handled through the support channel associated with your EDITH beta access.

For privacy, billing, or data questions during beta, contact support@getedith.io. This contact path may be updated before general release.

This policy is written for EDITH's current beta product state. It is intended to be readable and accurate today, not bloated. It should still be reviewed and expanded before a broader commercial release.