Your workspace
On your device
Charts, watchlists, strategies, journal and settings are stored locally by default.
Security
Understand where your data goes.
Your research is stored locally by default. Connected services have distinct purposes and data paths. Know what stays on your device, what you choose to share, and which protections depend on your platform.
Your data, path by path.
Market data
Your chosen provider
Market requests go directly between your device and the data source you connect.
Account & licence
Essential online services
Account and licence operations use online services. Local-first research does not mean every app interaction is offline.
Support & diagnostics
Submitted or consented data
Support submissions and optional usage or crash diagnostics have separate data paths. Diagnostics can send automatically within the consent you grant; review those settings and their limits.
AI context · In development
Your chosen model provider
The planned companion makes selected context visible. Information sent to a model is subject to that provider’s terms.
Cloud sync · In development
Your personal cloud
Workspace sync is designed to send encrypted content to storage you own. Sync is not operational yet.
Local storage and recovery
Your charts, watchlists, drawings, strategies, journal and settings share a local database by default. This is the research store; the data map above describes the separate connected services. Provider accounts and API-key requirements are listed in Integrations.
The app opens only its current database schema and current saved-record formats. A different database version is rejected without migration or rewriting. Before changing builds, preserve the old profile and a supported Analess backup export. Verify a backup restore in the target build before resetting or discarding the old profile. Newer backup formats can be rejected. See the storage recovery guide (coming soon) for the manual app-owned-data steps if you choose to start fresh.
Age declaration stays on this device
App use requires a declaration that you are 18 or older, including when you do not have an account. The answer and its time are stored on this device; they are excluded from cloud sync and backups, and are not sent to Analess. A new or restored device asks again. The declaration is not identity verification or advertising consent. See the privacy guide (coming soon) for the first-run flow.
Encrypted at rest
That local database is encrypted at rest using SQLite Multiple Ciphers. The file — headers, schema, and rows — is unreadable without its key; a test in the app writes a marker, then confirms the on-disk file can’t be opened, or the marker found, without the correct key.
Desktop & mobile
Encryption is on by default, and the key is held in your operating system’s secure store — Keychain on macOS and iOS, the Android Keystore, Windows DPAPI, or libsecret on Linux. The key is never written to disk in plaintext.
In the browser
The database is still encrypted, but browsers have no OS keystore, so by default the key is stored in the browser’s own storage unprotected. Turning on Browser protection seals the key with your recovery phrase (and, optionally, a passkey) — this step is opt-in, and until you enable it, the key is unprotected.
What encryption does — and doesn’t — protect
Encryption at rest protects the database when its key remains separate and protected. In the default unprotected browser state, access to browser storage may also expose the key. Malware or unauthorised access to an unlocked device can compromise information while the app uses it. Protection depends on the platform and its access controls; encryption does not replace device security.
Optional cloud sync — designed to be zero-knowledge
Optional cloud sync is built to be end-to-end encrypted: it syncs to your own cloud drive, with no Analess server in the path, and your device uploads only ciphertext derived from your recovery phrase — designed so the storage provider can’t read your content. It isn’t available to turn on yet; we’ll describe it as live only when it is. Two honest notes for when it ships: even with content encrypted, a storage provider can still infer some metadata (how many devices, roughly how often, approximate size); and if you lose your recovery phrase and your device, the encrypted cloud copy can’t be recovered — by you, by us, or by anyone. There is no reset link. See the personal-cloud destinations.
Service safeguards and account restrictions
We use access controls and data minimisation to protect information handled by our services. No system is completely secure. Security checks may flag or restrict suspicious account activity; you can request review through the privacy contact. Before introducing an automated decision with legal or similarly significant effects, we will provide the information and safeguards required by applicable law.
What we don’t claim
- We hold no security certifications, and we show no security badges.
- We describe the encryption library and its limits without claiming a security grade.
- The planned sync design excludes your API keys and exchange credentials.
Found a security issue? See our security.txt or reach us through the contact form.