Read-only analytics with explicit non-trading boundaries
Tradia never holds funds, executes orders, or asks for withdrawal access. Here's how the platform is engineered to keep your trade history safe.
Read-only account access
Use read-only credentials wherever connectors require them. Tradia is designed for post-trade data retrieval only.
No order execution path
The platform is analytics software. It does not submit, modify, or cancel orders — there is no code path that could.
Scoped data usage
Imported payloads are used for normalization, analytics, and verdict generation only. Nothing else, nowhere else.
Background task isolation
Import, aggregate, and verdict computations run via service/task boundaries to reduce request-layer risk.
Idempotent imports
Deterministic hashes prevent duplicate trade creation during reruns and recovery. Re-importing the same file is always safe.
Operational visibility
Import logs track statuses, counters, and errors to support incident response and reproducibility.
Recommended account setup
- Create dedicated exchange API keys for analytics only
- Disable trading and withdrawal permissions on those keys
- Rotate keys when access policies or account ownership changes
- Enable account-level MFA and exchange-side IP allowlists where available
Questions about security?
Reach our security team at security@tradia.app — or start with no commitment.