Development privacy notice

Account and trading information

Sign-in information is handled by the configured authentication service. The app uses your display name, email, language, theme and time zone, along with trading-account settings, uploaded statements, trades, cash records, strategies, notes, reviews and attached screenshots. When sync is enabled, the database keeps a credential hash, a short hint, expiry/revocation and successful-sync metadata. The raw token is shown only when created and is not saved in browser drafts. When invite-only waitlist capture is enabled, consenting requests keep an unverified email and language for access review. Requests are eligible for removal after 30 days; new requests prune a bounded expired batch, and operators must prune an idle queue. Submitting does not approve an account or send an invitation. When feedback is enabled, the private inbox stores your message and an optional owned import reference. Explicit source-sharing consent allows the operator to retrieve an existing available failed/review source for up to 30 days without creating another copy. Reports stay until the relevant account or user is permanently deleted; deleting an account immediately hides its reports and source access. Operator exports are private copies and require separate retention/deletion handling. No feedback is sent to external analytics, AI or email by this local flow.

Why the build uses this data

The data supports sign-in, importing and checking history, calculating reports and saving your reflections. The development build does not execute trades. Live AI generation and product analytics are not enabled as part of these local features.

Access and service providers

Saved records are scoped to the signed-in owner, with authenticator checks where enrolled. Statements and screenshots use private storage. Authorized operators can access private infrastructure for maintenance. Authentication, database, storage, email and background delivery depend on the configured environment; provider identities and hosting locations for launch remain to be confirmed.

Cookies and browser drafts

Cookies maintain sign-in, language and theme. Unsaved text drafts are stored in this browser tab when JavaScript is available; they clear on successful save or sign-out and are not a synchronized backup. New image selections can be lost on reload and may need reselection.

Files and saved history

Where automatic cleanup is enabled, successful statement files become eligible after 90 days unless the account keeps them; queued removal cannot be undone. Saved trades and reflections remain. Abandoned unreferenced files have a 24-hour grace. Files needing import review remain available until resolved or separately removed.

Automatic file cleanup is disabled in this development environment; files are not removed on the scheduled 90-day policy.

Export and deletion scope

Settings offers complete trade and journal CSV downloads; these do not bundle original statement or image files. Where account deletion is enabled, a trading account is hidden and can be restored for 30 days before private purge starts. This does not delete the entire sign-in identity or guarantee erasure from backups. A verified request channel and full retention policy remain pending.

Trading-account deletion is disabled in this development environment.