Nacrelia AI Dictionary Privacy Policy
Last updated: August 3, 2026
This Privacy Policy explains how Nacrelia ("we", "our", or "us") collects, uses, shares, and retains information when you use the Nacrelia AI Dictionary mobile application (the "App").
Information We Collect
Account and authentication data
If you sign in, we may receive and store your name, email address, authentication provider, and account identifier. Sign-in is optional for core dictionary lookup, but it is used for account-backed features such as cross-device history and favorites sync and account deletion. Premium purchase and restore do not require a Nacrelia account.
Dictionary requests, history, and favorites
- Search terms, source and target languages, and monolingual or bilingual mode are processed to provide dictionary results.
- History and favorites are stored on your device. When you are signed in, they are also synchronized with Firebase under your account so they can be restored and used across sessions.
- Dictionary requests are sent through our backend to an AI model provider. Generated dictionary results may be stored in a shared service cache for reliability, consistency, and faster responses. Shared cache entries are not stored as account-owned history.
Purchase and subscription data
When you buy or restore premium access, we process the product identifier, subscription status, store transaction identifiers, purchase and expiry dates, revocation or cancellation status, store environment, and a security-scoped device or installation association needed to verify and restore access. Canonical subscription status is associated with the Apple or Google store transaction, not with a Nacrelia sign-in account. Payment card or bank account details are handled by Apple or Google and are not available to us.
AI feedback and content reports
If you rate or report an AI-generated result, we may store the vote, selected reason, relevant word and languages, a compact snapshot of the displayed result, runtime information, and an optional note you provide. We use this information for quality review, moderation, abuse prevention, and targeted repair of weak dictionary entries.
Device, security, advertising, and usage data
The App and our service providers may process:
- app version, platform, device model, operating system, Firebase app-instance ID, installation or device identifiers, and integrity or attestation results;
- IP address and approximate country or region;
- consent status and advertising preferences;
- app launches, feature interactions, ad impressions and interactions, and other usage data;
- crash, performance, and other technical diagnostic data.
On iOS, the App uses App Tracking Transparency. If you authorize tracking, Google Mobile Ads may access the device advertising identifier for personalized advertising and advertising measurement across apps or websites owned by other companies. If you deny permission, the App does not authorize access to that identifier and requests limited or non-personalized advertising where applicable.
We use Firebase Analytics for aggregate product analytics. It may process a Firebase-generated app-instance ID and coarse app, device, session, screen, feature-interaction, language-pair, latency-bucket, advertising-flow, premium-flow, and account-state information. We do not send raw dictionary search terms or words, translations, meanings, definitions, examples, idioms, history contents, email addresses, account identifiers, advertising tickets, purchase transaction identifiers, tokens, or error stacks to Firebase Analytics. We do not assign a signed-in account identifier as the Firebase Analytics user ID.
Firebase Analytics may use an iOS Advertising Identifier or Android Advertising ID when it is available and the applicable User Messaging Platform consent, iOS tracking permission, and platform choices allow that use. If those choices do not allow advertising identifiers or advertising personalization, the related Analytics and advertising features are limited accordingly. Advertising identifiers are not included in our application-defined Product Analytics event payloads.
We link each iOS and Android app data stream in Firebase Analytics with its corresponding Google AdMob app. Subject to applicable consent and platform choices, this allows Analytics and AdMob to exchange app-engagement and advertising performance or revenue data for reporting, traffic-quality analysis, and monetization optimization. We also link the Analytics property to Google Ads for campaign attribution, conversion measurement, acquisition optimization, and consent-eligible audience creation or export. We do not currently run remarketing or re-engagement campaigns, and we do not export raw Analytics event data to BigQuery. These links do not change the raw dictionary and account content exclusions described above.
How We Use Information
- Authenticate users and provide dictionary, sync, history, favorites, premium, restore, and account-management features.
- Process AI dictionary requests and maintain reliable shared dictionary results.
- Verify purchases, prevent entitlement fraud, and respond to subscription lifecycle events.
- Secure the App and backend, enforce rate limits, detect abuse, and maintain service availability.
- Review AI feedback and content reports and improve dictionary quality.
- Diagnose crashes and performance problems and understand aggregate feature usage, retention, and product funnels.
- Measure advertising campaign acquisition and, where consent permits, optimize campaigns and audiences.
- Display, measure, and manage personalized or non-personalized advertising according to consent and platform settings.
- Comply with legal obligations and enforce our terms.
Data Linked to You and Tracking
Account information, signed-in history and favorites, and signed-in feedback may be linked to your account. Subscription records are linked to the verified Apple or Google store transaction and a security-scoped device or installation association, not to a Nacrelia account. Device, advertising, and usage data may be linked to an account, device, or app instance by us or our service providers. Firebase Analytics product events use an app-instance ID rather than a Nacrelia account ID; we do not intentionally send the raw dictionary or account content listed above. Crash, performance, and other diagnostic data are not intentionally linked to your identity in our App Store disclosure.
The only data category we declare as used for cross-app or cross-website tracking on the App Store is device identifiers, and only where the required permission and consent allow that use.
Service Providers and Sharing
We do not sell personal data. We disclose information only as needed to operate the App:
- Google Firebase and Google Cloud for authentication, database storage, app integrity, hosting, backend processing, and aggregate product analytics;
- OpenAI for AI-assisted dictionary generation and repair;
- Apple and Google for sign-in, app distribution, purchases, subscription verification, and store services;
- Google Mobile Ads, Google Ads, and User Messaging Platform for advertising, campaign attribution and optimization, consent management, and related measurement;
- infrastructure, monitoring, and operations providers that help us secure and maintain the service;
- authorities or other parties when required by law, necessary to protect rights and safety, or involved in a lawful business transfer.
These providers process data under their own terms and privacy policies and may process it in countries other than yours.
Data Retention
- Account profile data is retained while your account is active and during the account-deletion waiting period.
- Signed-in history and favorites are retained until you clear them or delete your account. Local copies remain on the device until cleared, app storage is reset, or the App is removed.
- Store entitlement records are retained while needed to verify, provide, and restore subscription access, including after a Nacrelia account is deleted. Purchase audit records are generally retained for up to 180 days after the latest relevant purchase, expiry, cancellation, revocation, or verification event.
- AI feedback and content reports are retained for up to 365 days.
- Consent-change records are retained for up to 30 days.
- Short-lived advertising workflow records are generally retained for one to three days. Operational, security, and diagnostic records are generally retained for seven to 90 days.
- Firebase Analytics event and user-property data may be retained for up to 14 months. Aggregated or de-identified reports may remain after source-level retention expires.
- Shared dictionary cache entries and aggregated or de-identified information may be retained as needed for service reliability and improvement when they are not maintained as account-owned records.
We may retain information longer when required by law, needed to resolve a dispute, or necessary to protect the service and its users.
Your Choices and Rights
Depending on your location, you may have rights to access, correct, delete, restrict, object to, or request a copy of your personal data.
You can:
- delete dictionary history without deleting your account by opening the History tab, selecting Clear, and confirming the deletion; signed-in deletions are synchronized with your account;
- manage advertising and usage privacy choices from the App through Google's User Messaging Platform when privacy options are required; if a valid choice state cannot be resolved, Firebase Analytics collection remains disabled;
- allow or deny tracking through iOS system settings;
- request account deletion from Profile > Delete account while signed in;
- submit an account-deletion request without the App using the public deletion page and support email;
- contact us to ask about access, correction, deletion, or another privacy request.
When account deletion is requested, you are signed out and account-owned data is scheduled for permanent deletion after a 30-day recovery period, including the account profile, synchronized history and favorites, and signed-in AI feedback or reports. Signing in again with the same Apple or Google account before the deadline cancels the request and restores the account. After the deadline, deletion is permanent and the former account data cannot be restored; a later sign-in creates a new account. Store transaction, premium entitlement, and security-scoped device access records are not Nacrelia account-owned data; account deletion does not cancel a store subscription. Detached device-security state, aggregated or de-identified information, store records controlled by Apple or Google, and records we must retain by law may remain under the retention rules above.
Public account-deletion guidance and an app-independent email request path are available at https://nacrelia-ai.web.app/delete-account/. Support verifies account ownership before scheduling a web request. Never send a password, authentication code, identity token, private key, or full purchase receipt.
Security
We use technical and organizational safeguards such as HTTPS, Firebase security controls, app attestation, access controls, and limited retention. No storage or transmission method is completely secure, and we cannot guarantee absolute security.
Children's Privacy
The App is not directed to children under 13 and is not positioned as a child-directed or Families app. We do not knowingly collect personal data from a child in violation of applicable law. If you believe a child has provided personal data improperly, contact us so we can review and delete it where required.
International Processing
The App is available internationally. Information may be processed in countries where we or our service providers operate. Where required, we use appropriate safeguards for international data transfers.
Changes to This Policy
We may update this Privacy Policy as the App, providers, or legal requirements change. We will post the updated policy at the same public URL and revise the "Last updated" date.
Contact
For privacy questions or requests, contact nacrelia.app@gmail.com.