Privacy Policy
This policy explains how Daily Trade ("Daily Trade", "we", "us") handles information when you use our Android and iOS mobile application, its Apple Watch companion, widgets, and connected services. Contact Daily Trade about privacy at support1@dailytrade.pro. Our website is www.dailytrade.pro.
1. Information we access or collect
Account and profile
- Email address, display name, account identifier, authentication provider, sign-in/security records, and preferences. Optional fields may include country, phone number, profile photo, language, and leaderboard alias.
- Google or Apple sign-in can provide an identifier and basic profile information you authorize. We do not receive your Google or Apple password. Authentication/session credentials are processed to keep you signed in; Apple authorization tokens may be kept server-side to support authorization revocation when deleting an account.
Challenges, trades, and financial records
- Firm, account type/size, selected challenge account, rules, status, targets, loss limits, dates, P&L, trade details, journal notes, tags, psychology/session entries, screenshots, and calculated progress or statistics.
- Imported statements are parsed on the device. Extracted trade records, source filenames/platforms, and selected journal images may be sent to Supabase when you enable supported cloud sync. The original import file is not uploaded by the trade-import feature.
- Business-ledger records and payout schedules may include fees, payouts, amounts, dates, firm names, notes, reminders, and synchronization preferences. Online features can require server storage independently of the trade-import sync setting.
Community, rewards, support, and uploads
- Payout certificates/images/PDFs, trader name or anonymous-display choice, firm, account size, payout amount/date, market, challenge type, ratings, notes, reviews, and moderation decisions. Approved submissions may be published as described in section 5.
- Points balances and ledger entries, referrals, quests, pack openings, rewards, prize claims and delivery status. Purchase-proof submissions include firm/product, order reference, amount/currency, purchase date, invoice/receipt image, and review status. Giveaway entry can require name, country, phone number and eligibility/terms acceptance.
- Support and bug reports include the subject, message text, optional images/screenshots, account/display name, timestamps, read/status information, and technical details you choose to include. Support can record temporary visit/typing presence and conversation events. Authorized support staff can access relevant tickets and attachments; these are not a public user-chat feed.
- Private performance links and follow invitations include selected sharing scope, expiry, approvals and revocation status. Access tokens are stored as hashes. Link-view records can include a salted IP-address hash, shortened user agent and view time for access history and abuse prevention.
Self-reported wellbeing
Wellbeing Journal: if you use this separate feature, you may deliberately enter a date, sleep duration, subjective sleep quality and resting heart rate. Submitted values are stored with your account in Supabase and may be compared with your recorded trading-day results. This is an association, not a diagnosis or proof of causation. The supported trade-import local-only setting does not by itself prevent a deliberate online Wellbeing Journal submission.
Device, installation, diagnostics, and optional analytics
- Online services may process IP address, request/security metadata and user agent. Signed-in mobile installations send Supabase an installation identifier, account ID, platform, app/build version, distribution track and last-active timestamps. These functional/security and installation records are separate from optional PostHog analytics.
- Notifications use Expo push tokens, Android FCM tokens, platform, topics, payload and delivery information.
- Sentry crash diagnostics: configured production builds can send errors/crashes, stack traces, app version, device model, OS/platform, timestamps and limited sanitized screen-navigation breadcrumbs. The implementation restricts diagnostic fields and redacts common sensitive values; it does not intentionally attach email/account profiles, authentication/request payloads, trade records, health readings, chat text, screenshots or session replay. Technical connection metadata can still be processed by the service. Crash diagnostics are not controlled by the optional usage-analytics switch.
- Optional PostHog analytics: off by default and enabled only by a signed-in user's separate account-and-device consent. It sends app openings and coarse section visits, app version, platform, language, session identifiers and an account-derived pseudonymous identifier to PostHog's US service. Pseudonymous does not mean anonymous. Our allowlist excludes names/email, raw authentication IDs, trade amounts, journal/AI/support content, health readings, precise location and screen recordings. Autocapture, session replay and GeoIP enrichment are disabled in this integration.
We do not intentionally request access to contacts, microphone recordings, SMS, call logs, installed-app lists or device location. IP/network metadata is distinct from requesting location permission. The mobile app does not use Firebase Analytics or Firebase Crashlytics in the reviewed configuration; Firebase Cloud Messaging delivers Android notifications. Promotional banners and affiliate links are present, but that is not a claim that the app has no diagnostics or analytics.
2. Permissions and on-device features
- Notifications: permission supports selected announcements, offers, challenge/payout reminders, support replies. Change notification settings in the app and operating system.
- Photos/files: system pickers select profile photos, certificates, journal/support images, invoices or trade imports. Selected uploads are sent only for the feature you use. Saving an exported card to Photos is a separate user action and may request photo-add permission. The app does not need broad Android photo/storage access, camera access or microphone recordings for these features.
- Calendars: optional payout-calendar sync requests permission to find/create a writable calendar and create, update or remove the payout events you choose. The sync stores app-created event/calendar IDs, installation ID, schedule/revision, status, timestamps and errors in Supabase. It is not intended to upload unrelated personal event contents. Your calendar provider may sync created events under your own calendar-account settings. Revoke access in system settings and manage existing events in your calendar.
- Biometrics: Face ID/fingerprint checks are performed by the OS; Daily Trade does not receive biometric templates. Optional sign-in credentials/session material are kept using device-protected storage.
- Local storage: preferences, supported local trade data, saved AI conversations, app-created exports, session information, widget snapshots may remain on the device. Signing out is not a promise to erase every optional local history, exported file, backup or copy held by another app.
Widgets, Live Activities, Dynamic Island, and Apple Watch
If enabled, these features use a summary of the selected challenge account, such as account/firm label, currency, progress, available P&L/target/loss metrics, status and update time. Widget extensions use on-device shared storage; the Watch companion receives snapshots over Apple's paired-device connectivity and caches a recent summary. Widget preferences may also be stored with your account.
Amounts may appear on the Home/Lock Screen, Live Activities or Dynamic Island according to your controls; use privacy masking and account selection settings before enabling them. Disable Watch/widget tracking or stop a Live Activity to stop that display. Account changes/sign-out clear or replace current app-managed snapshots, but a disconnected Watch cannot receive immediate clearing instructions; the Watch hides expired summaries after about an hour without a valid update. Reconnection is required to deliver pending changes. Widgets and Watch summaries are recorded-account information, not guaranteed live broker data.
3. Purposes and optional AI processing
We process information to authenticate and secure accounts; provide the features you request; sync supported data; calculate and display challenge/journal results; deliver notifications; operate support, rewards and moderation; prevent fraud/abuse; diagnose failures; and meet applicable obligations. Optional analytics helps us understand coarse product usage, separately from core-service processing.
Daily Trade AI
Saved-rule lookup can run without sending your question to an AI provider. Before Daily Trade AI generates an answer, the app asks you to agree. If you agree, your question, recent conversation messages, language, the name in your profile, relevant firm rules and current offers, and a summary of your tracked challenge accounts (firm, account type/size, stage, limits, deadline, balance, profit/loss, trading days, best day, consistency and payout-tracking figures) are sent through the authenticated Supabase AI proxy to our AI provider, Google (Gemini API). If it is busy or unavailable, the same request may be sent to a backup provider: Groq or Cloudflare (Workers AI). Older app versions whose consent names Cloudflare AI send only your question, recent messages, language and firm/account-rule context, and only to Cloudflare. Authentication and request-usage counters are handled by Supabase; passwords, account credentials, email and phone number are not included in the AI prompt. AI providers process these inputs under their own terms; on free service tiers a provider such as Google may use submitted content to improve its products.
You can decline and continue with available saved-rule lookup. Apart from the account summary described above, do not include passwords, identity documents, other private financial records or health information in your prompts. Our AI endpoint is not designed to store conversation transcripts in the app database; optional saved conversations are stored on your device. This does not mean the infrastructure/provider never processes technical logs or retains information under its applicable policies. End the conversation or decline further AI use to stop sending new prompts. AI answers can be inaccurate; verify firm rules with their official source.
4. Service providers, recipients, and international processing
| Provider/category | Purpose and information |
|---|---|
| Supabase | Authentication, database, storage, Edge Functions and realtime services: account/profile, enabled online data, self-reported wellbeing, selected uploads, support, rewards, installation/sync/security records and AI proxy/request limits. |
| Google (Gemini API) | Optional AI inference when you consent: the AI inputs and account summary described in section 3. On free tiers, content may be used to improve Google's products. |
| Groq | Backup optional AI inference when you consent: the AI inputs and account summary described in section 3. |
| Cloudflare | Website hosting/infrastructure and backup optional AI inference: website/request technical metadata and AI inputs/context described above when you consent. Visiting our public website also involves its own page features and provider/network processing. |
| Sentry | Limited crash/error diagnostics and device/OS/app context described in section 1. |
| PostHog (US) | Optional, consent-based pseudonymous product-usage events described in section 1. No session replay in this integration. |
| Expo, Apple push services, and Google Firebase Cloud Messaging | Notification delivery: tokens, selected notification content and technical delivery metadata. |
| Google and Apple sign-in | Federated authentication and the identifiers/basic profile information you authorize. |
| Paired Watch, widgets, calendar/photo/share services | OS-authorized on-device access, paired-device summaries or the calendar events/files you choose to save/share. These are not all public uploads to Daily Trade. |
| Authorized administrators/support and user-selected recipients | Relevant support/moderation submissions, or the specific public/private content you deliberately submit or share. |
Providers operate under applicable service/privacy terms and our configured safeguards. Information may be processed outside your country, including the United States. We use available contractual and technical safeguards where required; data residency is not promised to be limited to your country. We may disclose limited information when legally required, to address abuse/security, or in a business transfer subject to applicable protections. We do not sell personal information.
5. Public and user-directed sharing
Approved payout proofs and reviews may be public, including the content/amounts and trader attribution you submit. An anonymous-display choice does not automatically redact names or other details inside your uploaded image. Review and redact files yourself. Optional leaderboard publication uses the selected alias and intended performance fields, not an unrestricted view of your private journal.
If enabled, private snapshot links expose the selected aggregate performance to anyone holding a usable link, without sign-in, until its expiry, first permitted use or revocation. Follow invitations require approval for ongoing read-only access to the selected challenge scope and can be revoked. Intended shared views exclude broker passwords, account numbers and private journal text. A recipient can copy or screenshot information while access is valid; revocation cannot recover copies already made.
Share/export actions send the selected file or card to an app, Photos, calendar provider or recipient you choose. Their copies and privacy rules are separate from Daily Trade. Do not include information you are not permitted to disclose.
6. Affiliate links and external services
Some firm links/codes are affiliate links. We may receive a commission when you use them. External destinations may receive referral parameters and ordinary browser/network information and apply their own privacy policies. We do not automatically send your journal or private account balance as affiliate-link parameters. Optional in-app PostHog analytics is not an advertising-tracking permission or consent to unrelated cross-app tracking. Visiting the website is a separate context and may involve website analytics/cookies.
7. Retention and local copies
Account and associated online feature data are kept while needed for your account, requested services and supported record/history functions. Public submissions, support correspondence, reward/purchase verification and security records have different purposes; records required for legal obligations, disputes or proportionate fraud/security protection may need to be retained after ordinary use ends. Do not assume a universal automatic deletion period for every category.
Turning off optional analytics stops new app events; it does not itself erase earlier events already processed. Infrastructure backups, operational logs and provider records are separate from the live account database and are governed by applicable retention/deletion processes. Contact us for access/deletion questions; we will identify any applicable retention reason when handling a request rather than promise instant removal from every system.
Local-only records, optional saved chats, wellbeing history and exported files may remain until removed through the relevant feature, app storage controls or device tools. System backups, calendar events, shared files and recipient copies are not automatically recalled by deleting the Daily Trade account. Removing the app is not a guarantee that cloud, Keychain or independently backed-up/exported data has been deleted.
8. Account and data deletion
For help deleting an account or specific data, including earlier diagnostic/analytics records or files not removed by an automatic feature, email support1@dailytrade.pro with subject “Daily Trade Account Deletion Request.” Where possible, use your account email; we may verify ownership. We handle deletion requests subject to applicable law and explain any lawful retention exceptions. Do not send passwords or unnecessary identity/financial documents.
- Remove optional saved AI chats in the AI saved-conversations controls.
- For manually entered wellbeing, use Tools → Wellbeing Journal → Delete all wellbeing data. It is separate from your trading journal.
- Reconnect a paired Watch after sign-out/deletion so it can receive the cleared snapshot. Review/remove any exported photos, calendar events or files in the apps where you saved them.
9. Security
Online connections use HTTPS/TLS. Database/storage access controls, including Supabase Row Level Security, separate private account data from explicitly shared content and authorized administrative access. Server secrets remain server-side; device-protected storage supports sensitive authentication material. Not every local record is a separately encrypted vault. No system, redaction rule or network is perfectly secure. Protect your device/credentials and notify support of suspected exposure.
10. Age and children
Daily Trade is intended for adults aged 18 and over, not children. We do not knowingly seek children's personal information. A stated minimum age or eligibility checkbox is not a claim that every user has undergone identity-based age verification. Contact us if you believe a child has supplied personal data so we can address it.
11. Nonmedical and financial limitations
Self-reported Wellbeing Journal information is for personal reflection, not medical diagnosis, treatment or emergency monitoring. Daily Trade's trading features organize information; they do not execute trades, accept trading deposits or guarantee funding, payouts, profits, eligibility or future results. Verify firm rules and offers independently. Separate rules govern rewards and giveaways; this privacy policy does not replace official prize terms or establish legal eligibility.
12. Your choices and rights
- Edit supported profile/preferences; choose local-only or cloud sync for supported trade features in Profile → Privacy & data. Switching back to local-only does not automatically erase earlier cloud copies.
- Enable/disable optional usage analytics in Profile → Privacy & data. This setting is separate for each account on each device and does not disable core authentication, installation/security records or crash reporting.
- Decline optional AI processing (Google Gemini, Groq or Cloudflare); control saved chats, sharing/follow permissions, public submissions, notification topics, widget/Watch amounts and Live Activities through their respective controls.
- Request access, correction, a supported data copy or deletion using the contact below. Depending on applicable law, you may also have rights to object, restrict processing, withdraw optional consent or complain to a competent authority. Withdrawal affects future optional processing, not past lawful processing or required service/security records.
13. Updates
We may revise this policy when features or data practices change. We update the date above and provide additional notice or consent when required for a material change. New optional processing is not authorized merely by publishing a revised policy.