Security

The safest port for trading data is the one designed like a vault.

Trading history is sensitive. Broker keys are sensitive. Even account names can expose identity. VantageGrid treats the journal as financial infrastructure, not a casual note-taking app.

Start securely Read privacy policy
AES-256-GCM privacy vault showing encrypted broker credentials and hashed lookup
AES-256-GCM

Secrets are encrypted with authenticated encryption.

Broker credentials, webhook secrets, Pro API keys and integration tokens use AES-GCM encrypted storage paths with random nonces.

Hash lookup

Raw keys are not required for search.

API key matching uses SHA-256 hashes, while encrypted copies serve controlled audit and compatibility needs.

Local redaction

Import intelligence does not need your identity.

Extension blueprints preserve structure, mapping and confidence while using a privacy version for locally redacted payloads.

Data integrity fingerprint preventing duplicate trades across imports
Bulletproof Data Integrity

A copied trade, a reloaded PDF and a repeated scan should not corrupt the journal.

VantageGrid fingerprints the shape of each imported trade and scopes it to the user. Repeated imports increment the ledger instead of creating phantom trades.

1Instrument, side, entry, exit, quantity and close time define the trade shape.
2Normalized account name acts as the account salt for copy-trader safety.
3A user-scoped unique database constraint blocks duplicates under race conditions.