01
Purpose-bound collection
Data is collected for account access, purchases, beta communication, product safety, and improving the learning engine.
DATA + PRIVACY
A serious English ecosystem needs serious data boundaries.
Mingle EN is being designed around accounts, purchases, beta access, learning logs, review signals, media activity, and app progress. This page explains the privacy posture behind that ecosystem in plain language.
Current build statusBeta-stage policy architecture
OPERATING PRINCIPLES
Privacy is product infrastructure, not legal decoration.
The goal is simple: collect only what the learning engine and account system need, protect it with deliberate boundaries, and make user control visible as the ecosystem grows.
02
Learning data stays contextual
Signals like latency, accuracy, review history, and domains are treated as learning telemetry, not advertising inventory.
03
No sale of personal data
Mingle EN does not build the ecosystem around selling personal information to data brokers or third-party ad networks.
04
User control by design
Account, newsletter, purchase, and learning records should be reviewable, correctable, exportable, and removable as the product matures.
DATA MAP
What the ecosystem may handle.
A real product has more than one kind of data. Separating those categories keeps the system honest and makes future controls easier to understand.
Identity
Email, login provider identifiers, account status, beta interest, and consent records.
Commerce
Product purchases, checkout state, receipts, plan status, and access entitlements handled with payment partners.
Learning engine
Course progress, review outcomes, latency, consistency, domains, listening activity, and readiness signals.
Support + operations
Messages, bug reports, admin actions, security logs, abuse prevention, and product diagnostics.
USER CONTROLS
The account area should become the control room.
Privacy controls belong close to the user account, not hidden in a static policy. The website account now gives users practical controls for commerce, newsletter, export, deletion, and manual review.
Manage newsletter and beta communication preferences from the account area.
View connected purchases and product access.
Download a JSON export of website account, newsletter, entitlement, and purchase records.
Submit correction, export help, deletion review, or other privacy requests.
Delete the website account connection while retaining only anonymized commerce records when required.
This is a product-facing privacy architecture page, not a final legal privacy policy. Formal policy text should be reviewed before public launch.