Who this policy covers
This Privacy Policy explains how Trading Practice (“we”, “us”, or “our”) handles information when you use the Trading Practice Android app, its supporting services, this website at tradingpractice.app, or contact support (together, the “Service”). The proposed operator is currently shown as Loren Ipsum (placeholder); final controller details are pending as explained above.
Trading Practice is a simulation. All balances, trades, and rewards are virtual. We do not open brokerage accounts, hold customer investment funds, or execute orders on a financial exchange.
Information we process
| Category | Examples and purpose |
|---|---|
| Guest account | An app-generated installation identifier, account identifier, creation time, and locale. An authentication credential is kept on your device; the server stores a verifier to authenticate your account. |
| Simulation activity | Virtual balances, positions, orders, trade history, operation identifiers, reward claims, and related timestamps. This data lets us maintain progress and resolve interrupted or duplicate operations. |
| Usage and diagnostics | Session-start events, app version, timestamps, error codes, request identifiers, and account-linked operational events. These help us operate the Service, understand use, and investigate faults. |
| Rewarded advertising | Where enabled: ad attempt identifiers, placement, ad unit and network, impression and interaction events, completion status, and ad revenue measurements. Advertising providers may also process device and advertising identifiers, IP address, device and app details, and approximate location derived from IP. |
| Website and security | Hosting and network providers receive technical request information such as IP address, browser details, requested URL, and time to deliver the website and protect it from abuse. |
| Support | Your email address, message, and any account identifier or other information you choose to send. Do not send passwords, guest credentials, payment card details, or identity documents. |
The current guest account flow does not require your name or email address. The core simulator does not request your contacts, precise GPS location, microphone, or camera. Clearing app data or uninstalling can remove the local guest credential and make the same guest account inaccessible; it does not by itself delete server records.
Why we use information
- Provide and authenticate a guest account; keep virtual progress, balances, positions, and history consistent.
- Calculate and record simulated trades and rewards, prevent duplicate actions, and recover interrupted operations.
- Maintain reliability, investigate errors, detect fraud and abuse, and measure use of the Service.
- Show optional rewarded advertising where available, verify ad completion, and measure advertising performance.
- Answer support messages and privacy requests, and meet applicable legal obligations.
Where data protection law requires a legal basis, we rely on performing the service you request for core account and simulation functions; legitimate interests in security, reliability, abuse prevention, and service measurement where appropriate; legal obligations where applicable; and consent where required for advertising, device access, or similar technologies. You can withdraw consent without affecting processing that was lawful before withdrawal.
You may object to processing based on legitimate interests, including related profiling, on grounds relating to your situation. You may object to direct marketing at any time. We do not use simulated performance to make decisions about credit, employment, insurance, or other real-world financial eligibility.
Advertising and your choices
Some app builds support optional bonus videos through AppLovin MAX. Advertising availability depends on the build, configuration, and provider. Where enabled, we work with AppLovin to show ads; AppLovin and its advertising partners may collect and use information about your device and ad interactions to deliver, personalise where permitted, measure, and improve advertising and prevent fraud.
Learn more in AppLovin’s Privacy Policy and its partner information. The app may use Google’s User Messaging Platform for privacy choices; see Google’s Privacy Policy. This does not mean every advertising network is integrated into Trading Practice.
Where required, the app presents a consent or privacy-choice flow before relevant advertising processing. You can use the privacy options made available in the app or contact us for help. Android also provides advertising ID and ad privacy controls in system settings; their names vary by Android version. You can choose not to watch a bonus video. Virtual rewards are subject to verification and do not have cash value.
We do not sell personal information for money. Some advertising disclosures can be considered “sale”, “sharing”, or targeted advertising under certain local laws. Where those rules apply, you may request the applicable opt-out through the available privacy controls or by contacting us. Advertising providers are also responsible for the processing described in their notices.
Google accounts, analytics, and advertising partners
Where Google sign-in is enabled, you can choose to link a Google account to your guest account or sign in to an existing linked account. We process the sign-in token for verification, a derived Google account identifier, and the display name supplied by Google. We do not ask for your Google password. Your display name, selected avatar, ranking, and public simulator statistics may be visible to other players through profile and leaderboard features.
Configured app builds use AppMetrica (Yandex) and Google Analytics for Firebase for product analytics and advertising measurement. Information includes app and device identifiers, device and app details, installation source, screen views and interaction events, account ID, language, whether Google is linked, virtual trading and reward events, and ad impression and revenue information. These measurements help us understand how the app is used, investigate problems, and measure installs and conversions from advertising campaigns, including Google Ads. SDKs are inactive when their configuration is absent; applicable consent and privacy choices control activation in supported builds.
See AppMetrica’s data collection notice, Yandex’s Privacy Policy, and Firebase’s privacy information. AppMetrica’s notice describes processing on Yandex infrastructure in the EU and the Russian Federation. Google and other providers may process data internationally under the arrangements described in their notices. Contact us to exercise applicable rights or for help with privacy choices.
The current advertising integration can show rewarded video and other formats such as native, interstitial, and app-open ads, depending on configuration. Google AdMob demand may be provided through AppLovin MAX. Google’s privacy policy linked above applies to its advertising and consent services. Only choosing a bonus video is optional; other advertising formats may appear as part of app use. Advertising and analytics SDKs are part of the Android app, not this landing website.
Website storage and cookies
This landing website does not require registration. We do not add advertising SDKs, marketing pixels, or non-essential analytics cookies to it. The interactive scenario runs in your browser without saving its inputs or sending them to an account or trading API. Fonts and site assets are hosted with the site.
Cloudflare may process technical network information and use necessary security mechanisms when delivering and protecting the website. Following an external link or emailing support is subject to the relevant provider’s privacy practices.
The Android app stores guest credentials, cached account state, preferences, and pending operations locally so it can authenticate you and resume activity. Those records are separate from website cookies.
How long we keep information
We keep account and simulation records while needed to provide your guest account, preserve progress and operation consistency, investigate disputed outcomes, prevent abuse, or meet legal requirements. Usage and advertising events are kept while needed for those operational and measurement purposes. The current backend targets a 30-day retention window for structured error events; removal happens through its operational cleanup rather than an immediate deletion timer.
Support correspondence is kept for as long as needed to resolve the request and any related follow-up or legal obligations. Infrastructure and advertising providers apply their own retention rules.
When you request deletion, we assess the records associated with your account, verify the request as needed, and delete or de-identify information that is no longer necessary. If some information must be retained for a legal obligation, security, fraud prevention, or a dispute, we restrict its use to that reason and explain the relevant exception. Any retained backup copies, where applicable, are subject to the provider’s deletion cycle and restricted use.
Your rights and deletion requests
Depending on your location and applicable law, you may have rights to request access to or a copy of your information, correction, deletion, restriction, portability, and objection to certain processing. You may also withdraw consent where processing depends on it, and exercise applicable rights relating to targeted advertising or sharing. These rights are subject to lawful limits.
Send a request to support@tradingpractice.app. Our account deletion page explains what to include. We may ask for proportionate information to confirm account ownership. Do not send a password, guest secret, or identity document with your initial request. We will respond within the period required by applicable law.
You may complain to the data protection authority where you live or work. For UK matters, you can contact the Information Commissioner’s Office. Contacting us first can help us resolve the issue but is not a condition of your right to complain.
International processing and security
Our infrastructure and advertising providers may process information in countries other than your own. Applicable safeguards depend on the provider, processing location, and relevant law. You can contact us for information about the arrangements that apply to your data. Final operator and transfer details will be completed before public app release.
We use measures appropriate to the Service, including encrypted network connections, account authentication, and restricted operational access. No system can guarantee absolute security. Keep your device secure and do not share your guest authentication credential.
Children
The Service is a general-audience trading simulator and is not directed to children. We do not knowingly seek personal information from children in breach of applicable law. If you believe a child has provided information without any required consent, contact us so we can review and remove it where appropriate. Final audience and age-related settings will be confirmed before public app release.
Changes and contact
We will update this policy when the Service, providers, or confirmed operator details change. The date at the top identifies the latest version. Material changes will be communicated where required.
Trading Practice
Proposed operator: Loren
Ipsum (placeholder; details pending)
Privacy and support:
support@tradingpractice.app