Security
Security & Credential Handling
How Argix Labs protects your API keys and account data.
Credential encryption
The keys you can save with Argix — for market data providers and AI models — are encrypted at rest using industry-standard authenticated encryption. Argix does not accept brokerage credentials: it stopped connecting to brokers on 28 September 2026, and the brokerage keys it held were deleted.
- Credentials encrypted immediately upon submission
- Decrypted only in memory, when fetching data or calling the AI model you chose
- Never stored in plaintext anywhere in the system
- Never sent to the frontend after initial submission
- Never included in logs or error reports
No fund custody
No access to your brokerage account
Argix Labs never has custody of, or access to, your funds. It does not connect to your brokerage account and cannot place orders.
Authentication
- Passwords hashed using industry-standard algorithms
- Secure authentication with encrypted sessions
- All communications encrypted via TLS 1.2+
Payments (Stripe)
Paid plans are billed through Stripe. Card and payment details are collected and stored by Stripe—not on Argix Labs servers—so we never handle or retain your full card number.
- Checkout and billing run on Stripe’s PCI-compliant infrastructure
- We only receive the tokens and metadata needed to manage your subscription
- Connections to Stripe use TLS; see Stripe’s security documentation for certifications and practices
Your responsibilities
- Use a strong, unique password for your Argix Labs account
- Rotate the data-provider keys you save with Argix periodically
- Revoke a key at its provider immediately if you suspect compromise
- Never paste brokerage credentials into Argix; it has nowhere to use them, and anything asking for them in Argix’s name is not us
Security contacts
Report security vulnerabilities to: security@argixlabs.com