Privacy and security
Your trading data should stay yours.
TradeStaxx is built with private account access, encrypted connections, managed infrastructure, and third-party payment processing so your journal can remain focused on your review.
Encrypted connections
TradeStaxx is served over HTTPS so data is encrypted while moving between your browser and the application.
Private account access
Authenticated areas of TradeStaxx are restricted to signed-in users and are excluded from search-engine indexing.
Protected application data
User data is stored through managed infrastructure designed for modern web applications and access-controlled workflows.
Secrets stay server-side
Sensitive credentials such as Stripe secrets and service keys should remain in environment variables and server-only code.
Managed deployment
TradeStaxx is deployed through Vercel, which provides secure HTTPS delivery, isolated builds, and production deployment controls.
Payments handled by Stripe
Payment information is processed through Stripe rather than stored directly inside TradeStaxx.
Security principles
Practical controls instead of vague promises.
Security is a process. TradeStaxx focuses on clear access boundaries, managed services, careful handling of secrets, and minimizing exposure of private user data.
- Private routes require authentication
- Sensitive server credentials stay out of client code
- Payments are processed through Stripe
- Public marketing pages are separated from private app pages
- Robots and sitemap rules avoid exposing private application routes
- Security reports should be handled privately and responsibly
Frequently asked questions
Questions about privacy and security
Does TradeStaxx store my credit card information?
No. Payment information is processed by Stripe. TradeStaxx does not directly store complete card details.
Is my trading data public?
No. Your journal, analytics, notes, screenshots, imports, and account data are intended to remain private unless a future feature explicitly lets you choose to share something.
Can search engines index my dashboard?
Private application routes are blocked from indexing and require authentication. Robots directives are not a security boundary, so access control remains the primary protection.
How are passwords handled?
Authentication is handled through the configured identity provider rather than storing plain-text passwords inside the application.
What should I do if I discover a security issue?
Use the contact page to report the issue privately. Avoid posting sensitive vulnerability details publicly before the issue can be reviewed.
Questions or concerns?
Contact TradeStaxx privately.
Report security concerns privately so they can be reviewed before sensitive details are shared publicly.