Mobile app disclosures
Data safety and privacy labels
This page summarizes the mobile app data practices used to complete App Store privacy labels and Google Play Data safety forms.
This is a store-submission aid and public transparency page. The full legal terms remain the Privacy Policy, Terms & Conditions, Risk Disclosure, and Refund Policy.
Data collected
| Category | Examples | Purpose | Association |
|---|---|---|---|
| Contact info | Email address, username, optional phone number | Account creation, login, support, account recovery, and notifications | Linked to user |
| User content and preferences | Watchlists, selected symbols, trading profile, broker setup state, notification preferences | Provide core app features, personalization, broker-backed market data workflows | Linked to user |
| Purchases | Subscription plan, order id, payment status, billing metadata from Cashfree | Subscription activation, fraud prevention, payment support, accounting reconciliation | Linked to user |
| Identifiers | User id, session identifiers, Expo push token, device/app metadata | Authentication, push notifications, security, analytics, diagnostics | Linked to user |
| Usage data | App opens, screen views, login method, feature usage, drop-off analytics | Product analytics, reliability, funnel analysis, DAU/engagement reporting | Linked to user |
| Diagnostics | Crash/error context, logs, device OS/app version where available | Debugging, abuse prevention, service reliability | May be linked to user |
| Approximate location | IP-derived region/city when available | Security, login audit, fraud prevention, analytics aggregation | Linked to user |
Data sharing
We do not sell personal information. Data may be processed by infrastructure, authentication, analytics, push-notification, payment, communication, broker-integration, and security vendors that help operate AlgoTradingAI. Payment processing is handled through Cashfree, and broker authorization happens through supported broker portals or APIs.
Security practices
- Authentication uses access and refresh tokens.
- Transport should use HTTPS/WSS in production environments.
- Broker credentials and secrets are handled by backend services and are not exposed in public app pages.
- Analytics events are used for product reliability and funnel reporting, not for selling personal data.
User controls
- Users can edit profile details from Profile.
- Users can adjust notification categories from Settings.
- Users can disconnect broker integrations from Brokers.
- Users can initiate account deletion from Profile or by contacting support.
Continue with your account
Go back to login if you already have access, or create a new account to continue into the product.