Privacy Policy
Updated October 14, 2026
Release builds use Sentry to help diagnose crashes. Reports can include technical crash information, app version, operating system, and device characteristics. Session recording, screenshots, and view-hierarchy capture are disabled. JournalOne does not intentionally attach account details or journal records to crash reports, and filters JavaScript reports to remove messages, request data, and application state.
JournalOne is designed as a local-first trading journal. Your signed-in journal is stored on this device. Basic account sync through Supabase is available without Premium. Authentication uses Supabase whether or not you subscribe. Cloud copies include trading records, profile settings, preferences, playbooks, reviews, learning progress, drill progress, and screenshots stored privately in your account.
Basic sync stores the latest journal. For Premium accounts, the app also keeps the latest 20 cloud journal snapshots. Screenshots are stored separately and shared between snapshots so repeated backups do not duplicate the same image. Screenshot files remain in your account until account deletion.
The app stores trading records, profile settings, preferences, playbooks, reviews, lesson progress, and drill progress locally. New attached screenshots are embedded in journal records. Older attachments may still reference local files.
You are responsible for protecting your device, operating-system account, passcode, biometric unlock, cloud backup settings, shared folders, screenshots, exports, and files you create from the app.
Exports, screenshots, reports, and backups may contain sensitive financial or personal information. Once copied, uploaded, sent, shared, or stored outside the app, those files are controlled by the destination you choose.
Do not include information in notes, screenshots, imports, exports, or support messages unless you are comfortable storing and handling that information.
Device authentication is handled by the operating system. JournalOne does not receive your biometric template or device passcode. Accounts use Supabase for email confirmation, password authentication, and password recovery. The app stores session tokens in secure storage on mobile and browser storage on web; it does not store your account password. Biometric unlock protects access to an existing signed-in session and does not encrypt the local journal database. An authenticated account is required to access the journal.
Apple or Google Play processes purchases, depending on your platform, and RevenueCat verifies subscription access. RevenueCat receives your JournalOne account identifier, purchase and subscription records, and SDK device/app information used to provide billing services. JournalOne does not receive your payment-card number. Journal entries, notes, and screenshots are not sent to RevenueCat by the app. Subscription and authentication providers may retain records required for their operations or legal obligations.
You can delete your account in Security after confirming your password. This removes your account, active cloud journal, in-app cloud backups, and private screenshot files. Account deletion does not cancel a store subscription. Exported files, copies on other devices, and provider operational backups are not erased by the app. Contact support@journalone.app for privacy requests.