Proposed Privacy Policy

Effective date: Not set
Proposal updated: October 11, 2026

1. About this proposed policy

AndromedaX, LLC operates Link and linklanguages.win. This is a preview of the privacy policy proposed for a future public release in the United States. The practices described here are proposed for that release and may change before it becomes available.

The proposed minimum age is 13. This does not change the current beta, which remains limited to adults aged 18 and over. We have not set an effective date for this proposed policy.

Contact [email protected] or write to AndromedaX, LLC, 23860 Greenlawn Ave., Beachwood, OH 44122.

2. Account and learning information

Sign-in. Link requires an account. We use Google’s Firebase Authentication for email-and-password sign-in and Google sign-in. Firebase processes your sign-in credentials. We receive your account identifier, email address, email-verification status, sign-in provider, and display name where available.

Your profile. We store your profile in Cloudflare. It includes your account identifier, email address, first and last name, full date of birth, assigned public username, app language, selected curriculum and its identifiers, learning pace, review preferences, and paid-access status. Your password is not included in this profile. These details support account management, learning settings, feature access, and age-related settings. Your assigned public username identifies you on leaderboards.

Learning activity. Link processes learning progress, practice results, review scheduling, and activity information to select exercises, track progress, and provide achievements. Learning information is stored on your device, and account-linked activity information is also stored in Cloudflare. Activity information includes learning time, completed sessions, streaks, achievement scores, languages, and curriculum identifiers. Analytics and AI processing are described below.

Support and feedback. When you contact us or submit feedback, we receive the contact details, message, attachments, and diagnostic information you provide. We use them to respond, investigate problems, improve Link, and keep a record of the request. Avoid including sensitive personal information that is unnecessary for your request.

Separate marketing subscriptions. Creating a Link account does not itself subscribe you to marketing emails. If you separately subscribe to Link news and offers, we use your email address and subscription record for that purpose. That subscription is optional and separate from your app account. It continues after app-account deletion until you unsubscribe or request its deletion. Use the unsubscribe link in a marketing email, or contact [email protected]; you do not need to sign in. A request to erase all your personal information also covers the subscription, subject to applicable legal exceptions.

3. Microphone, speech recognition, and AI

Speaking exercises are planned to use your microphone with your device permission. You will be able to revoke microphone permission in device settings; features requiring speech will then be unavailable.

Speech recognition may use Apple’s service on iOS, the provider available on Android, or a downloadable Whisper model that transcribes locally. Device speech recognition can involve a provider’s servers. Local transcription can create an audio file on your device, and it does not by itself prevent recognized text from being sent for AI features.

AI exercises may process typed or transcribed responses, exercise prompts and reference material, images used in exercises, language and learning-level context, and conversation history to return feedback or replies.

Still being finalized: the AI service and agreement for the future audience, age eligibility for AI features, the sharing disclosure and choices, and retention of practice content. The paid Gemini service described in the beta policy must not be assumed to be available to teenagers in the future release. We will identify the actual provider and data handling before offering those features to that audience.

4. Analytics, advertising, and diagnostics

App analytics. We use Google Analytics to understand registration, learning activity, feature use, and performance. When enabled, analytics are associated with your account identifier. We send learning language, app language, curriculum identifier, free or paid account status, and sign-in method, together with events such as signup progress, session activity, exercise outcomes, timing, and feature errors.

Google Analytics also processes device and app information, session information, an app-instance identifier, and approximate location. Depending on platform permissions and settings, advertising or vendor identifiers may be available to the SDK. See Google’s Analytics data-collection description. The website does not use analytics; see Section 7.

Advertising. We plan to use Google AdMob. The final advertising choices and eligibility rules will be described before launch. Non-personalized ads also involve data collection. Google’s advertising SDK processes information such as IP address and approximate location, device or advertising identifiers where available, ad interactions, and diagnostic information for ad delivery, measurement, and fraud prevention. See Google’s non-personalized ads explanation and its SDK disclosures for Android and iOS.

Planned choices. The future release is intended to provide advertising and optional-analytics choices, with appropriate protections for teenagers. The final policy will explain how to accept, decline, or withdraw each choice and which features remain available. Consent will not override age restrictions imposed by law or a provider. These planned controls are not a statement that they are already available in the beta.

Crash and error reporting. We use Firebase Crashlytics in the mobile app to diagnose crashes and other errors. Reports can include installation identifiers, device and app details, error messages, stack traces, and logs describing the events around a failure. Diagnostic context can include account identifiers, email addresses, or details relevant to the failing operation. Some diagnostic records are also stored locally on your device. See Firebase’s privacy information.

Security and network information. Our backend, hosting, and authentication providers process network requests, including IP addresses and technical request information, to deliver and protect the service. Firebase App Check uses device or app integrity checks and tokens to help prevent abuse.

5. Providers and other disclosures

We plan to use Google Firebase for authentication, backend functions, app-integrity checks, and crash reporting; Cloudflare for hosting, content delivery, backend services, and account and learning-data storage; and Google Analytics and AdMob for analytics and advertising. Platform speech-recognition providers may process audio. AI arrangements for the future audience remain to be finalized as described in Section 3.

Provider information is available in Firebase’s privacy documentation, Cloudflare’s privacy policy, Google’s privacy policy, and Apple’s privacy information. The final provider list will match the released features.

We may also disclose information at your direction, when required by law, or when reasonably necessary to protect rights, safety, and the security of Link. Information may be transferred in connection with a merger, acquisition, or transfer of the business, subject to applicable protections and notice requirements.

6. Retention and account deletion

We keep account and learning information while it supports your account and the service. Other retention depends on the purpose of the record, whether an issue or request remains open, security needs, provider retention rules, and legal obligations. We do not promise that signing out, uninstalling Link, or finishing an exercise immediately removes all copies.

Request deletion. Email [email protected] to request account deletion. We may ask you to verify that the account belongs to you. Our target is to begin promptly and complete deletion of account data under our control within 28 days of a valid request, sooner where possible. This includes the sign-in account and associated profile and learning records. Account deletion is permanent, with no recovery period; you can register again if you return. The planned release will include an in-app deletion request and a web request route. The final policy will provide the available steps.

Your separately chosen marketing subscription is handled independently as described in Section 2. You can unsubscribe at the same time, or ask us to delete all your personal information.

Some records may remain where needed to meet legal obligations, investigate abuse, resolve disputes, or establish or defend legal claims. Provider records and backups may take longer to expire than active account data. For example, Firebase describes removal of authentication information from live and backup systems within 180 days after customer-initiated deletion. Crashlytics retains crash information and associated identifiers for 90 days before starting removal. See Firebase’s retention descriptions.

Retention by the AI and speech providers will be specified after the future-release arrangements are finalized. Provider retention and backup expiry are separate from our account-deletion target.

Local learning records, diagnostic logs, and speech-recognition files can remain on your device. Device or cloud backups may also contain copies. Contact us if you need help identifying and removing Link data on your device.

Still being finalized: system-specific retention periods for analytics, diagnostic logs, recordings, support records, and backups, and verification of the deletion process.

7. Website cookies and tracking

The following describes the website configuration used as the starting point for this proposal. Website controls and disclosures will be updated if they change before the future release.

Our website does not use analytics, advertising, or tracking services, and it does not set cookies. Cloudflare, which hosts the website, processes network requests, including IP addresses and technical request information, to deliver and protect it; see Section 4 and Cloudflare’s privacy policy linked in Section 5.

The website does not track visitors, so there is nothing for browser Do Not Track or Global Privacy Control signals to turn off. Contact us about any applicable privacy rights using Section 8.

8. Your choices and privacy requests

The planned choices include device microphone permissions, selection of the speech-recognition source, the advertising and analytics controls described in Section 4, and unsubscribe for separately chosen marketing emails. Providing an account and its required setup information is necessary to use Link. Speech and AI features require the processing described in Section 3.

Depending on where you live and which laws apply, you may have rights to access, correct, delete, or obtain a copy of personal information; opt out of sale, sharing, or targeted advertising; or limit certain uses of sensitive information. Where we rely on consent, you may withdraw it without affecting earlier lawful processing.

Send requests to [email protected]. We may request proportionate verification and will respond within the applicable legal time limit. Where permitted, an authorized agent may act for you. You do not need to create an account solely to make a privacy request. We will not unlawfully discriminate against you for exercising your rights. If a right to appeal applies, send the appeal to the same address.

9. Children and teenagers

The proposed public release is intended for people aged 13 and older in the United States. Children under 13 would not be permitted to use Link, including through a parent’s account.

Before admitting teenagers, we will finalize age checks, age-appropriate privacy settings, and provider arrangements for the features offered. The current beta remains 18 and over only; this proposal does not authorize anyone younger to join it.

If you believe an underage person has provided personal information, contact [email protected] so we can investigate and take appropriate action.

10. Security and processing locations

We use technical and organizational safeguards designed to protect personal information, including authenticated access to account data and encrypted connections to our service providers. No method of transmission or storage is completely secure.

Although the proposed release is initially limited to the United States, our providers operate internationally and may process information in other countries. The final policy will describe the arrangements applicable to that release. Contact us for information about the handling of your data.

11. Finalization and changes

This proposal is not in effect and may change. Before a public release, we will publish the final policy with its effective date and explain material changes. We will provide notice and obtain consent where required before applying a changed practice.

Until then, consult the adult-beta privacy policy for the beta. Questions or feedback about this proposal can be sent to [email protected].