Back to Billing & FAQ

Data Security and Privacy

How your trading data is stored and protected

TradeLog takes data security seriously. Your trading data, personal information, and API credentials are protected using industry-standard security practices.

Database Security

  • Hosted on Supabase (PostgreSQL) with enterprise-grade infrastructure
  • Row-Level Security (RLS) enforced at the database level -- users can only access their own data, period
  • All database connections use SSL/TLS encryption
  • Regular automated backups ensure data is never lost

Authentication

  • Authentication handled by Supabase Auth with secure session management
  • Passwords are hashed using bcrypt -- TradeLog never stores or has access to your plain text password
  • Session tokens are short-lived and automatically refreshed
  • Sign in with email/password or Google
  • Optional two-factor authentication (TOTP authenticator app + backup codes)

API Key Storage

When you connect external platforms (MT4, MT5, Binance, etc.), your API keys are stored encrypted in the database. The encryption ensures that even if the database were somehow accessed, the keys would not be readable. TradeLog only uses these keys to read your trade history -- never to place trades or move funds.

Data Privacy

  • Your data is never sold to or shared with third parties
  • No advertising trackers or data brokers have access to your information
  • Your public profile only shows data you explicitly choose to make visible
  • You can delete your account and all associated data at any time

Payment Security

All payment processing is handled by Stripe, a PCI Level 1 certified payment processor (the highest level of certification). TradeLog never sees, stores, or has access to your credit card numbers. All payment data goes directly to Stripe.

For maximum security on your connected trading accounts, always create API keys with read-only permissions and use IP whitelisting when your exchange supports it.
Row-Level Security (RLS) means that every database query is automatically filtered to only return data belonging to the authenticated user. This is enforced at the database level, not the application level, providing an additional layer of protection.

Was this helpful?