Tester communication
If you request alpha testing access, we use your email to send invitations, confirmations, and important updates about the alpha program.
Privacy policy
Learn++ explains what data the app and website use, what we store, and how code execution and future redeem codes are handled.
Last updated: January 28, 2026
Learn++ - tablet view
Overview
We collect only the data we need to run Learn++, support alpha testers, and keep the service secure.
Learn++ includes: (1) a website with analytics, (2) an alpha tester signup flow, and (3) a mobile app that can run code by sending it to our backend for compilation/execution. This policy covers all three.
What the app uses
We only use data needed to run Learn++ and support testers.
Device context
When you share device details (like model/OS version), we use them to troubleshoot bugs, reproduce issues, and improve performance.
Learning progress
Progress and preferences (language selection, last visited example, UI settings) are stored on your device so you can pick up where you left off.
Code execution (compile & run)
When you run code in the app, your code is sent to our backend service for compilation/execution and the output is returned to you. We use this to provide run code without a PC functionality.
Google sign-in (optional)
If you choose to sign in with Google, we receive basic account identifiers (such as your name, email, and a Google account ID token) so we can authenticate you and keep your experience consistent across sessions.
Website analytics
Our website uses Google Analytics (via Google Tag / gtag.js) to understand traffic and improve the site. This may involve cookies and device/usage data such as pages visited and approximate location derived from IP.
Ads (if enabled)
If ads are enabled in the app, an advertising SDK may collect device identifiers and basic usage data to show and measure ads. You can limit ad tracking through your device settings where available.
What we save
We store only what you share or what is required to operate the service.
Tester request details
Email, name (if provided), device model, Android version, and notes from the tester request form. This information may be stored in a CSV file for managing the alpha program and sending the opt-in/invite link.
Support conversations
Feedback emails and attachments you send so we can respond, track fixes, and improve Learn++.
Operational logs
Basic server logs (timestamps, IP address, request metadata, errors) to keep the service secure and reliable, prevent abuse, and troubleshoot issues.
Code execution requests
Your code and its output are processed to provide execution results. We do not intend to permanently store your code, but we may temporarily retain limited request/error data for debugging, performance monitoring, and abuse prevention.
Authentication data (if you sign in)
If you use Google sign-in, we store whats necessary to keep you signed in (for example, a secure session identifier). We do not sell your account data.
Third-party services
Some features rely on third-party providers that may process data under their own policies.
- Google Play (testing/installation, distribution, and store-related processing).
- Google Analytics (website analytics via Google Tag / gtag.js).
- Google Ads (including Customer Match / customer lists, where enabled) to provide advertising, audience matching, measurement, and policy-compliance services on our behalf.
- Google Sign-In (if you choose to authenticate with Google).
- Google Mobile Ads / AdMob (in the app, where enabled) and Google AdSense / Funding Choices (on the website) to display, personalize (where permitted), and measure ads.
- Firebase Authentication (to support sign-in and account security).
Google Ads, cookies, and certified partners
When AdSense is active on public content pages, Google may use cookies and local storage to deliver, personalize, and measure ads.
You can change your cookie preferences at any time via Cookie settings.
- Google may store and read cookies to serve ads based on prior visits.
- Personalized ads in EEA/UK/Switzerland require consent via our CMP (Google Funding Choices).
- Non-personalized ads may still use limited data such as coarse location and fraud-prevention signals.
- Google and its certified advertising partners may process data under their own policies: Certified ad technology vendors.
- You can manage ad settings via Google Ad Settings and revisit consent choices in the CMP message where available.
Google Ads Customer Match and customer lists
If we use Google Ads Customer Match or similar audience features, we may share customer data with Google or approved service providers to perform advertising, audience matching, measurement, and policy-compliance services on our behalf.
- We only use customer data collected in a first-party context, such as information you provided directly through Learn++ websites, apps, tester forms, account registration, support messages, or similar direct interactions.
- Customer data may include identifiers such as email address, name, phone number, country, device/account details, or other contact details you provided.
- Before upload, customer identifiers are formatted and hashed where required by Google Ads Customer Match rules.
- Google uses uploaded Customer Match data to match our customers to Google accounts, create or update audience lists, provide advertising and measurement services, and help ensure compliance with Google policies.
- Where required by law or Google policies, including Google’s EU User Consent Policy, we obtain consent before sharing customer data for personalized ads, Customer Match, or similar audience features.
- You can contact info@learnplusplus.online to request access, correction, deletion, withdrawal of consent, or removal from marketing/customer-list use.
- Consent to join internal testing (for Google Play invites) is separate from consent for marketing or personalized ads; we do not use testing consent for Customer Match or marketing audience uploads.
Future redeem codes
When we introduce redeem codes, we will store redeemed codes (and the account or device that used them) to prevent reuse and to provide access to the correct plan.
Security and retention
We apply reasonable security measures and keep data only as long as needed.
We limit access to tester records and operational logs, and we retain data only for legitimate purposes (alpha program management, troubleshooting, abuse prevention, and legal compliance). You can request deletion of tester data at any time.
Your choices
You can request access, updates, or deletion of tester data by contacting info@learnplusplus.online.
If you used Google Sign-In, you can also revoke access in your Google Account security settings.
Changes to this policy
As Learn++ evolves (especially during alpha), we may update this policy. We will update the Last updated date and publish the latest version on this page.