Last updated: 17 September 2026
This policy explains what TradeLock collects, why, and what you can do about it. It covers TradeLock on iOS, Android, and the web. It is written under the UK GDPR and the Data Protection Act 2018.
1. Who we are
TradeLock is operated by Tradeily, London, United Kingdom. Tradeily is the data controller for the personal data described in this policy.
Privacy queries, data rights requests, and general support: help@tradelockhq.com
2. What we collect
Account data
We store a unique user ID, your name (display name), and your email address.
If you create an account with email and password, we also store a hash of your password. We never store your password in a readable form.
If you sign in with Google, Google sends us the email address and name associated with that Google account (and may include a profile image URL) so we can create and recognise your TradeLock account. We receive a Google account identifier through Google Sign-In. We do not receive your Google password.
Payment data
How you pay depends on where you subscribed. We never see or store card numbers, bank details, or Google/Apple wallet credentials.
- Website: payments are handled by Stripe. We hold Stripe customer and subscription identifiers, your plan, and its status.
- iOS (App Store): payments are handled by Apple. We hold App Store subscription identifiers, product, plan, expiry, and renewal status so we can unlock paid features.
- Android (Google Play): payments are handled by Google. We verify the purchase with Google and store subscription status and purchase tokens as described in TradeLock for Android below.
Broker connection credentials
Where you connect a trading account (on iOS, Android, or the web), we store the credentials required to maintain a read-only connection to it. These are encrypted at rest.
They are used only to read account state so that we can evaluate the rules you have set. They are never used to place, modify, or close a trade, and they are never shared with third parties.
For MetaTrader 5, that includes the investor (read-only) password, account login, and server name. For cTrader, the connection uses an authorisation you grant in cTrader itself. When you disconnect or close your account we delete our copy of the access credentials and invalidate them so they can no longer be used. cTrader does not provide a way for us to withdraw the authorisation on your behalf, so the app will also point you to the Open API tab of your cTrader ID settings, where you can remove TradeLock's access directly.
Trading account data
Balance, equity, open positions, and closed trade history, read from your connected account solely to detect rule breaches and to populate your journal. We also store a display snapshot of balance, equity, and related margin fields from the last successful poll.
Journal entries
If you use the journal, we store the entries you save: the date, why you stopped, how you felt, what you would do differently, the outcome (win, loss, or break-even), and whether you respected your limit. Journal entries sync across TradeLock on iOS, Android, and the web for the same account.
Voice dictation
On Android and iOS you can dictate journal or other in-app text instead of typing. Dictation uses the microphone and the operating system's speech-recognition service (on Android, typically Google). Audio is processed on the device or by that OS service. We do not receive or store audio recordings. We only store the text you save, as journal or profile fields.
You can refuse microphone access and type instead.
Uploaded photos
You can take or choose a profile photo. The app uploads the image file to our storage (Cloudflare R2). We save the resulting URL on your TradeLock account. Allowed types are JPEG, PNG, GIF, WebP and SVG, up to 10MB. Files are stored under an account-specific key and are deleted from storage when you delete your account.
We do not use uploaded photos for advertising or facial recognition.
Usage data
Which rules you set, when locks fire, and session timings.
Push notification tokens
On iOS, a device token so we can notify you when a lock fires or is released, delivered through Apple Push Notification service.
3. Screen Time data (iOS)
TradeLock uses Apple's FamilyControls, ManagedSettings and DeviceActivity frameworks to block the apps you select.
App usage data collected through these frameworks stays on your device. It is not transmitted to our servers or to any third party. We cannot see which apps you use or for how long.
This section applies to the iOS app. It does not describe Android.
4. TradeLock for Android
This section describes data that TradeLock for Android uses, in addition to the categories above. The Android app shares the same TradeLock account as iOS and the web.
Account information
The Android app uses your TradeLock name, email address, and user ID. You can sign in with email and password or with Google Sign-In. When you use Google Sign-In, we receive the Google account information needed to identify you (email, name, and Google account identifier) and link it to your TradeLock user ID. Google processes that sign-in under Google's terms and privacy policy.
Google Play subscriptions
Paid Android subscriptions are sold through Google Play Billing. Google handles payment details. We do not receive your payment-card number, Play balance, or other payment-instrument data.
When you subscribe or restore, the Android app sends us the purchase token, product ID, and package name. We verify the purchase with the Google Play Developer API, then store:
- the purchase token (the record that proves the subscription belongs to a TradeLock account);
- subscription status (including trial, renewal, expiry, grace period, and revocation where Google provides them);
- product, plan, package name, and related Play identifiers (such as order ID); and
- an account association: Android sets Play's obfuscated account ID from a hash of your TradeLock user ID, and we check that it matches before linking the purchase.
Google also sends us Real-time Developer Notifications when a subscription is purchased, renewed, cancelled, expired, or otherwise changes, so we can keep entitlement up to date.
A purchase token can be linked to only one TradeLock account. If you delete your TradeLock account, the Play purchase-token record is kept, unlinked from your user ID, so the same purchase cannot be restored onto a different account. Deleting your TradeLock account does not cancel the Google Play subscription; cancel it in Google Play.
Optional broker connections
Connecting a broker is optional. If you connect one from Android, we store the same read-only credentials and trading information described in section 2 (encrypted MT5 investor password, login and server, or cTrader authorisation; balances, equity, positions, and closed-trade history used to monitor your rules). This is the same backend as iOS and the web.
Journal entries
Journal entries you write in the Android app are stored on our servers as described in section 2 and are available on your other TradeLock devices when you are signed in. If you dictate an entry, only the saved text is stored (see Voice dictation in section 2).
Uploaded photos
If you set a profile photo from Android, the image is uploaded and stored as described in section 2. The app needs camera or photos/media access only while you take or pick that image.
Android permissions
TradeLock for Android asks for permissions only to provide the features you use. You can deny optional ones in system settings; related features will not work.
| Permission or access | Why we ask |
|---|---|
| Internet / network | Sign in, sync your account, journal, rules, broker monitoring, and Play purchases |
| Google Sign-In | Create or recognise your TradeLock account with Google |
| Google Play Billing | Start, restore, and manage a paid subscription. Google handles payment details |
| Notifications | Optional alerts when a lock fires or is released (you can skip this in onboarding) |
| Microphone | Optional voice dictation. Audio is not sent to TradeLock servers |
| Camera | Optional: take a profile photo |
| Photos / media | Optional: choose an existing profile photo |
| Usage access and app list | Let you pick which trading apps to lock, and detect when those apps are opened so a lock can be applied. We do not upload a history of your other app use to our servers. Which apps you selected may sync as lock settings with your account |
| Display over other apps / special lock access | Show and enforce the lock over the apps you chose, equivalent in purpose to Screen Time on iOS. This access stays on the device |
Android does not use Apple's Screen Time APIs. App-lock behaviour on Android is handled with the device permissions above. Usage data used to block apps stays on your device: we cannot see a feed of everything you use on the phone.
5. Why we process it
| Purpose | Lawful basis |
|---|---|
| Creating and running your account, including Google Sign-In, and syncing locks and journal entries | Performance of a contract |
| Reading connected account state to evaluate your rules | Performance of a contract |
| Verifying subscriptions and managing entitlement (Stripe, Apple, or Google Play, depending on where you paid) | Performance of a contract |
| Storing a profile photo you upload | Performance of a contract |
| Security, abuse prevention, diagnosing faults, improving the service | Legitimate interests |
| Marketing email, including waitlist updates | Consent |
| Meeting tax, accounting, and other legal duties | Legal obligation |
Marketing consent is separate from your account and can be withdrawn at any time, either by using the unsubscribe link in any marketing email or by emailing help@tradelockhq.com. Withdrawing it does not affect the emails we must send you to operate your account.
6. Who we share with
We use the following sub-processors, and no others:
| Sub-processor | Purpose |
|---|---|
| Stripe Payments Europe / Stripe, Inc. | Website payment processing and subscription billing |
| Apple Inc. | App Store subscriptions and delivering push notifications to iOS devices |
| Google LLC | Google Sign-In, Google Play Billing (including purchase verification and subscription notifications), and OS speech recognition if you use dictation |
| Cloudflare, Inc. | Storing uploaded profile photos (R2) |
| Vercel Inc. | Application hosting |
| Neon Inc. | Managed Postgres database hosting |
| Resend | Transactional and waitlist email delivery |
| MetaApi | Read-only connectivity to MT5 broker accounts |
We do not sell personal data. We do not serve advertising. We do not share your data with brokers, prop firms, or anyone else for their own marketing.
We may disclose data where we are legally required to, or to establish or defend legal claims.
7. Retention
- Account data is retained while your account is active and for 90 days after you close it, after which it is deleted. Billing records are retained for 7 years where tax law requires.
- Google Play purchase-token records remain after account deletion, unlinked from your user ID, so a purchase cannot be restored onto a different account.
- Broker connection credentials are deleted immediately when you disconnect the account or close your account, and are invalidated with the provider at the same time so they cannot be reused.
- Trading account data, journal entries, and usage data are retained while your account is active and deleted within 90 days of closure.
- Uploaded photos are removed from live storage when you delete your account.
- Push notification tokens are deleted when the device is removed or the account is closed.
- Waitlist email addresses are retained until you unsubscribe or ask us to delete them.
8. Your rights
Under the UK GDPR you have the right to:
- access the personal data we hold about you;
- rectify data that is inaccurate or incomplete;
- erasure of your data where we no longer have a basis to keep it;
- portability — receive your data in a structured, machine-readable format;
- restrict our processing in certain circumstances;
- object to processing carried out on the basis of legitimate interests; and
- withdraw consent at any time where consent is the basis we rely on.
To exercise any of these, email help@tradelockhq.com. We will respond within one month. We may ask you to confirm your identity first.
You can also request deletion of your TradeLock account at tradelockhq.com/delete-account.
If you are not satisfied with our response, you can complain to the Information Commissioner's Office (ICO), the UK supervisory authority, at ico.org.uk or on 0303 123 1113.
9. International transfers
Our application and database are hosted in the United Kingdom or European Economic Area.
Some sub-processors listed in section 6 process data in the United States. Where personal data leaves the UK or EEA, we rely on the UK International Data Transfer Addendum to the European Commission's Standard Contractual Clauses, or on UK adequacy regulations where the receiving country is covered by them.
10. Age
TradeLock is for users aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe a person under 18 has given us data, email help@tradelockhq.com and we will delete it.
11. Changes
If we make a material change to this policy we will email the address on your account and post a notice in the app at least 14 days before it takes effect. The "last updated" date above always reflects the current version.