Skip to main content

Security

A journal holds something sensitive

A complete record of how you trade, and a connection to the account you trade with. Here is exactly how both are protected.

Read-only by construction

The broker adapter has two methods: verify credentials and fetch trades. There is no method that places, modifies or closes an order, so there is no code path through which Alpha Ledger could trade your account — not a policy, a property of the code.

Credentials encrypted at rest

Investor passwords and API keys are encrypted with AES-256-GCM before they touch storage, decrypted only at the moment a sync runs, and never returned to the browser in any form.

Row-level security on every table

Ownership is enforced in Postgres, not just in the application. A query issued with your session can only ever return your own rows, so an application bug cannot leak another trader’s journal.

Two-factor authentication

TOTP from any authenticator app, with single-use recovery codes shown once at enrolment.

Rate limiting and audit logging

Every API and AI route is rate limited per user, and sensitive actions are written to an audit log you can export.

No card details, ever

Payments go through Stripe. Alpha Ledger stores only a customer reference so the billing portal works, and never sees a card number.

Deletion actually deletes

One click plus a typed confirmation removes your profile, every trade, plan and screenshot. There is no soft-delete and no recovery window.

Privacy by default

Analytics cookies are off until you accept them, and declining is exactly as easy as accepting. Your trading data is never sold or shared.

Reporting a vulnerability

Email security@the-alpha-ledger.com with enough detail to reproduce the issue. We will acknowledge within two working days and keep you updated until it is resolved.

Please do not access another user’s data, degrade the service, or disclose publicly before we have had a reasonable chance to fix it. We will not pursue anyone who reports in good faith under those conditions.

See also the privacy policy for what we store and how to get rid of it.