Privacy Policy

At the start of onboarding, the app creates a user identifier from the current timestamp. It stores this identifier locally and uses it in Firebase Analytics and as a document identifier in Cloud Firestore. The app does not provide sign-in with an email address, password, or social account.

Depending on the information provided and how the app is used, Nativia processes:

• the entered name and selected gender;
• the app language, selected learning language or languages, and active learning language;
• the selected country, city, or region;
• starting and target level and self-assessments for comprehension, speaking, and grammar;
• learning-method and story-mode preferences;
• onboarding progress and a referral code;
• premium status.

Some of this information is stored locally. The name and app language may also be stored in Cloud Firestore together with activity data. Learning language, country, region, level, self-assessments, and premium status are sent to Firebase Analytics as user properties.

The app stores learning and usage progress locally and/or in Cloud Firestore, including:

• chats, messages, AI context, help messages, topic, learning language, level, and selected conversation partner;
• story, chapter, and scene progress, conversation history, scene summaries, and story memories;
• known characters, story choices, items, and virtual balances;
• XP, energy, completed chapters, message counts, and hints used;
• learned, seen, and actively used words and assigned CEFR levels;
• grammar and pronunciation scores and identified pronunciation errors;
• timestamps relating to learning and game progress.

Cloud Firestore offline persistence is enabled. Firestore data may therefore also be held in the local app cache on the device.

The app requests microphone access for speaking exercises and conversations. Recordings are sent to Microsoft Azure Speech through endpoints in Western Europe to transcribe speech and assess pronunciation. Audio, the requested language/locale, and, for pronunciation assessment, a reference text are processed.

Nativia can use the camera for simulated video calls. The camera image is shown as a local preview. The app does not transmit the camera image to an external video service.

For speech output, the text and selected voice are sent to Microsoft Azure Text to Speech. Generated audio is temporarily cached in memory and in temporary files on the device. In some cases, the device's own text-to-speech service is used instead.

To generate replies, assess grammar and naturalness, continue stories, create summaries, and simulate calls, Nativia sends the following to external AI services:

• typed or transcribed text;
• extracts from earlier conversations or their summaries;
• learning and explanation language, level, and regional context;
• role, character, story, and scene information;
• results and instructions required for assessment.

Nativia uses OpenAI and the paid Google Gemini API through Google AI Studio. Depending on the feature, content may be sent to these services separately or in parallel. Voluntary prompt and response sharing for Google model improvement is not enabled.

When a translation is requested or displayed, the AI-generated text and the source and target languages are sent to DeepL API Pro. The generated text may contain information from the conversation context and therefore personal data.

Nativia uses Firebase Analytics. Events include session starts, ends and duration, viewed screens, time spent, navigation targets, onboarding steps and selections, the mode used, conversation identifiers, round and message counts, conversation duration, grammar and pronunciation scores, device language and country code, learning language, selected country and region, level, self-assessments, and premium status.

The analytics implementation technically supports logging shortened conversation, correction, or pronunciation text if explicitly enabled. No active use of this text transmission has been identified. The app also stores the latest activity timestamp, active seconds per day, and the most recently used mode in Cloud Firestore.

Firebase Analytics is activated only after express consent. Consent can be withdrawn at any time under “Settings → Privacy” or the corresponding localized label. Event data is retained for two months and user data for 14 months.

Nativia uses Firebase Crashlytics. Unhandled serious Flutter and asynchronous errors are reported with a stack trace. The SDK may add device and diagnostic information. Crashlytics is activated only after express consent and can be disabled together with Analytics in the app's privacy settings.

After notification permission has been granted, the app uses Firebase Cloud Messaging (FCM). The FCM token is stored in Cloud Firestore under the user identifier and updated when it changes. If no learning activity has taken place on a given day, Nativia may automatically send a reminder personalized using the daily activity status and story progress.

The app also schedules local streak and trial-period reminders. Push and local notifications are controlled through the operating system's notification settings; Nativia does not provide a separate in-app switch.

Nativia uses RevenueCat and Apple's or Google's billing systems for in-app purchases and subscription status. RevenueCat uses an automatically generated anonymous App User ID. The app retrieves customer and entitlement information, restores purchases, and stores the active premium status locally. Payment-card data is not sent directly to a server operated by the controller.

Free-form feedback is stored with its date and time in Firestore without a user identifier. Feedback is deleted three years after receipt. Relevant findings may first be transferred to internal tasks or bug descriptions without a user reference.

Communications with external services necessarily involve connection data such as IP address, timestamps, protocol information, and device information. Nativia also checks network status to indicate a missing connection. The app does not access location or contacts. The Android configuration removes the advertising-ID permission, and no advertising network is integrated.