Privacy policy
How Nilla Trader thinks about account data, local broker credentials, analytics, payments, and support.
Nilla should collect the least it can while still running a useful terminal. The most important rule: local broker secrets should not be baked into public builds or casually sent through support channels.
01What we collect
Email, profile, sign-in provider identifiers, preferences, and support messages.
Saved views, chart settings, watchlists, screener choices, and trading-workspace preferences.
Broker/server/login metadata and local MT5 reads when you connect a terminal. Saved MT5 passwords are intended to remain encrypted on your device.
Basic events that help us understand reliability, performance, and which screens need work.
02Local desktop data
The desktop app may store theme choices, radio state, chart settings, and local account preferences on the device.
When Local MT5 credential saving is enabled, the desktop bridge uses Electron safeStorage so saved passwords are encrypted by the operating system where possible.
03Processors
Nilla may use Supabase for auth/database services, OAuth providers for social login, Stripe for payments, market-data or broker providers for trading-related services, and hosting/observability providers to operate the app.
Those providers process data under their own terms and privacy notices where applicable.
04How we use data
We use data to authenticate users, load profiles, operate the trading workspace, remember preferences, provide support, improve reliability, process payments, prevent abuse, and comply with legal obligations.
We do not sell personal information.
05Your controls
You can request access, correction, export, or deletion of personal data associated with your account, subject to records we must retain for legal, security, billing, or abuse-prevention reasons.
Contact support for privacy requests. Do not include broker passwords or API secrets in email.