Our privacy principles.

The minimum required to operate the account and provide support:

• Account identifiers — email address, bcrypt password hash, display name, optional avatar URL.
• Billing data — last four digits of card, expiry month/year, country, and Stripe customer ID. Full card numbers are never transmitted to or stored by us; they live with Stripe.
• Product telemetry — anonymous page views, error stack traces (sanitised of any inline values), feature usage counts. No third-party analytics SaaS is loaded.
• Trade history — the trades you execute through the desktop app, written to your local SQLite by default and to your hosted Postgres only if you opt into cloud sync.
• Audit log — append-only record of authenticated mutating requests for security investigation (action, IP, user agent, response status, duration). Sensitive fields are sanitised at capture time.
• Optional channels — Telegram chat ID, alert email address, SMTP credentials — only if you turn these on.

• Your exchange API keys. Keys are encrypted on your device with AES-256-GCM using a scrypt-derived per-user key (private to your install) and stored locally. The ciphertext never reaches our servers in the desktop product.
• Wallet seed phrases or private keys — we never ask for them and the product has no surface that accepts them.
• Browsing data outside the app — no advertising pixels, no cross-site cookies, no third-party trackers.
• Biometric data, location data, contacts, or any device-resident information beyond what the desktop app needs to operate.

• To provide, maintain, and improve the service.
• To authenticate your account, route alerts, and process payments.
• To investigate fraud or unauthorised access via the audit log.
• To comply with legal obligations and respond to lawful requests.

We do not sell or rent personal data, do not use it to train machine-learning models, and do not share trading data with any third party for any commercial purpose.

A sub-processor is a third party that processes personal data on our behalf. As of May 13, 2026 we use:

We will notify subscribed users by email at least 30 days before adding a new sub-processor that materially changes how personal data is handled.

• Account data — kept while your account is active and for 90 days after deletion, then purged.
• Trade history — kept until you delete it (settings → export/delete) or your account is closed.
• Audit log — 12 months, then automatically deleted.
• Billing records — 7 years to satisfy tax-record obligations under Indian and US law. Card-number metadata never leaves Stripe.
• Backups — encrypted snapshots are kept for 30 days and then overwritten.

Our primary infrastructure runs in AWS Asia-Pacific (Mumbai, ap-south-1). Stripe processes billing data in regions per its own published infrastructure (typically US/EU). If you are located in the EEA / UK / Switzerland, transfers outside your home region are made under the EU Standard Contractual Clauses where applicable. Contact privacy@cryptoroute.io for a data-processing addendum (DPA).

Subject to verification of identity, you can:

• Access — request a machine-readable export of all data we hold about you.
• Correct — update inaccurate or incomplete data via the settings page.
• Delete — request erasure of your account and all associated data.
• Restrict / object — limit specific processing activities (e.g., disable alerts).
• Portability — receive your trade history as CSV at any time.
• Withdraw consent — for any processing based on consent.

Email privacy@cryptoroute.io with your request. We respond within 30 days; complex requests may extend to 60 with notice.

California residents (CCPA/CPRA) and EEA/UK residents (GDPR) have additional named rights under those statutes; we honour them on the same response timeline.

The marketing site uses only a single first-party preference cookie for your theme selection. The authenticated app uses a session cookie for login state. We do not use third-party analytics or advertising cookies. The desktop app uses local storage only — no remote cookies.

We hold credentials encrypted at rest (AES-256-GCM), enforce HTTPS in transit, sign desktop installer updates with a public/private keypair (the desktop app refuses unsigned bundles), and rate-limit and log every authenticated mutation.

In the event of a personal-data breach that is likely to result in a risk to your rights or freedoms, we will notify affected users by email within 72 hours of becoming aware, alongside any required regulator notification.

CryptoRoute is not intended for and is not directed at anyone under the age of 18. We do not knowingly collect data from minors.

We will post a new effective date at the top of this page for any change. For material changes (new data classes, new sub-processors, expanded purposes) we will additionally notify subscribed users by email at least 14 days before the change takes effect.

Privacy questions: privacy@cryptoroute.io. Data-protection authority complaints: you may contact the supervisory authority in your country of residence at any time, but we encourage you to write to us first so we can resolve the matter.

Diviners Solution, India · Last updated May 13, 2026.