Privacy Policy for Seed

Last updated: June 25, 2026

This Privacy Policy explains how the mobile application "Seed" (the "App"), provided by Alex Goncharov ("we", "us", "our"), collects, uses, stores, and shares information when you use the App on Android and iOS.

Contact: alexeyg2006@gmail.com

1. Information We Collect

1.1 Information You Provide Directly

• Account information. When you create an account or sign in, we collect information such as your email address, nickname, authentication provider, and Firebase user ID. If you use email/password sign-in, your credentials are processed by Firebase Authentication on our behalf. On iOS, sign-in is offered through Sign in with Apple; if you choose Apple's "Hide My Email" option, we receive an Apple-generated private relay email address instead of your real address, and we use that relay address to identify your account. On Android, sign-in is offered through Google. We only receive the basic profile information the provider returns (such as an email address or relay address and a user identifier).
• Profile and settings. We store settings such as your interface language, learning language, daily goal, theme preference, reminder time, and related profile preferences.
• Social profile and friends data. If you use social features, we store your public profile — your nickname, avatar selection, profile wall layout, and the word cards you choose to showcase — together with learning statistics shown on it (such as your level, learning language, streak, weekly and total XP, words learned, and cards collected). We also store your friends list, friend requests, and invite codes you create or redeem. See Section 6 for what is visible to other users.
• Learning and progress data. We store data needed to run the App, such as your words, topics, review history, streaks, achievements, quests, gem or emerald balance, virtual items, premium status, word cards and collection data (including card rarity, discovery numbers, chests opened, upgrade shards, and card upgrades), and similar progress data.
• Imported or pasted content. If you paste text or choose files to import (such as .txt, .csv, .doc, or .docx), the App reads that content so it can extract words, build learning lists, or generate study content from it.
• AI and translation requests. When you use AI-generated features or translation features, the App sends the text you choose to process (for example words, phrases, topic names, or imported snippets) together with language settings. We do not intentionally include profile fields such as your email address or nickname in those content prompts.
• Microphone input. If you use speaking practice, the App accesses your microphone while that feature is active. Seed does not store raw audio recordings or upload raw microphone recordings to our own servers. Speech recognition is handled by your device or platform speech-recognition provider under that provider's own terms — on iOS this is Apple's speech recognition, which may send audio to Apple to perform the recognition; on Android it is the device's speech-recognition service.
• Support requests. If you contact us, we collect the information you include in your message.

1.2 Information Collected Automatically

• Device and app information. We may collect device model, OS version, app version, locale, timezone, and connectivity-related information needed to run the App and keep data in sync.
• Crash and diagnostics data. Firebase Crashlytics collects crash reports and related diagnostics such as stack traces, device model, OS version, and app version.
• Notification data. If you enable reminders or notifications, we may store your Firebase Cloud Messaging token, timezone, and reminder settings so we can send reminder notifications. Push notifications are delivered through Firebase Cloud Messaging, which uses the Apple Push Notification service (APNs) on iOS and Google's messaging service on Android.
• Advertising and consent data. If ads are shown, Google AdMob and Google's consent tools may process advertising identifiers, consent choices, and ad interaction data. Google may also infer approximate location from IP address for ads, fraud prevention, or legal compliance. On iOS, the App asks for your permission through Apple's App Tracking Transparency (ATT) framework before using the device advertising identifier (IDFA) to personalize ads or measure ad performance across other companies' apps and websites. If you grant permission, ads may be personalized using the IDFA; if you decline, iOS ads are non-personalized and use Apple's SKAdNetwork for privacy-preserving attribution only. On Android, where you consent, ads may be personalized using the device advertising ID. You can change your ATT choice in iOS Settings at any time, and you can reset your advertising ID or opt out of ad personalization in your device settings.
• Purchase and virtual currency data. If you make purchases or use virtual currency features, RevenueCat and Google Play may process your app user ID, product identifiers, entitlement status, purchase token, transaction status, and related purchase history. RevenueCat may also store virtual currency information, such as gem balances and transaction history, as part of your RevenueCat customer profile. We do not receive your full payment card details.
• Card discovery counters. Word-card discovery numbers are based on a global counter of how many users have collected a given word's card. This counter contains only word identifiers and counts — it does not include your name, nickname, email, or other personal information.

2. Third-Party Services and SDKs

The App uses the following third-party services. Each service has its own privacy policy governing how it handles data.

We do not sell your personal data.

3. How We Use Your Information

• To operate the App and keep you signed in.
• To sync your profile, progress, and settings across devices.
• To personalize your learning experience.
• To operate the word-card collection, chests, upgrades, and collection milestones.
• To operate social features such as your public profile, profile wall, friends, friend requests, and invite codes.
• To translate text and generate study content you request.
• To process imported content you choose to use in the App.
• To send optional push reminders and notifications if you enable them.
• To show ads according to your consent choices where required.
• To process purchases, subscriptions, virtual currency balances, rewards, and premium access.
• To diagnose crashes, prevent abuse, and improve reliability.
• To respond to support, privacy, and account-deletion requests.

4. Permissions the App Requests

Depending on your platform (Android or iOS) and version, Seed may request the following permissions. Each is requested only when relevant, and you can decline most of them and still use the core App.

• Internet & network state — to connect to Firebase, translation services, image services, ads, and purchase services, and to adapt behavior based on connectivity.
• Notifications — to send reminders and other notifications. On Android 13+ and on iOS the App asks for your permission first; you can deny this and still use the core App.
• Microphone — only when you use the speaking practice feature.
• Speech recognition (iOS) — on iOS, speaking practice also requests permission to use Apple's speech recognition to check your pronunciation.
• Photo library (Save / Add) — only when you choose to save or share an image of your progress, such as a word card or your profile.
• Haptics / Vibrate — for optional haptic feedback during interactions such as opening chests.
• Billing / In-app purchase — to support purchases and subscriptions through the app store.
• Tracking (App Tracking Transparency, iOS) — on iOS, the App asks for permission to track before using the advertising identifier (IDFA) to personalize ads. You can decline and still use the App; iOS ads will then be non-personalized.

Each platform build may also include supporting capabilities used by the notification, messaging, and ads SDKs, such as background notification delivery, wake locks (Android), and advertising-identifier access. Seed does not request precise location permission on either platform.

5. Data Storage and Retention

• Cloud data is stored in Firebase services for as long as your account remains active or as otherwise needed to provide the App.
• On-device data is stored on your device using tools such as ObjectBox, SharedPreferences, and image caches so the App can work faster and support offline use where available.
• Imported and generated content may be stored locally or in your account data when needed to provide the feature you used.
• Third-party processing of text sent to AI, translation, image, ads, purchase, and other providers is handled under those providers' own retention practices and terms.
• Deletion. If you delete your account, we aim to delete associated server-side account data — including your public social profile, friend connections, and word-card collection — within 48 hours unless a longer retention period is required by law or needed for fraud prevention, dispute handling, or legal compliance. Anonymous aggregate data, such as global card discovery counters, does not identify you and may be retained.

6. Data Sharing and Disclosure

We do not sell your personal information. We share data only as described in this policy:

• With the third-party providers listed in Section 2, as needed to operate the App.
• With law enforcement or government authorities, if legally required.
• To protect the rights, safety, security, and integrity of Seed, our users, or others.
• In the event of a business transfer such as a merger, acquisition, financing, or sale of assets.

6.1 Information Visible to Other Users

If you use social features, your public profile is visible to other users of the App. This includes your nickname, avatar, profile wall, showcased word cards, and learning statistics such as your level, learning language, streak, weekly and total XP, words learned, and cards collected. Other users may see this information when they are your friends, when they redeem an invite code you shared, when they receive a friend request from you, or when they find your nickname through in-app search.

Choose a nickname and showcase content you are comfortable sharing publicly. Do not put personal information (such as your real full name, contact details, or address) in your nickname. You can change your nickname, avatar, wall, and showcased cards at any time in the App, and deleting your account removes your public profile and friend connections as described in Section 5.

7. Your Choices and Rights

Depending on where you live, you may have rights to access, correct, export, delete, or restrict the use of your personal data, and to withdraw consent for optional processing.

• Manage notifications — you can change notification permission in your device settings.
• Manage ad settings — on iOS you can change your App Tracking Transparency choice in Settings → Privacy & Security → Tracking; on any device you can reset your advertising ID and manage ad-related settings.
• Manage your public profile — you can edit your nickname, avatar, wall, and showcased cards in the App at any time.
• Delete your account in-app — use Settings → Delete Account.
• Contact us — email alexeyg2006@gmail.com to request access, correction, export, or deletion of your data.

We aim to respond to privacy requests within 7 business days.

8. California Residents (CCPA)

9. Brazilian Users (LGPD)

10. Children's Privacy

Seed is intended for users aged 13 and above. We do not knowingly collect personal information from children under 13. Our app's target audience on Google Play is set to ages 13 and above, and the App's App Store age rating is set accordingly. If you believe a child under 13 has provided personal data to us, please contact us and we will work to delete it promptly.

11. International Data Transfers

Your information may be processed on servers located outside your country of residence, including in the United States or other countries where our service providers operate. When required, we rely on the safeguards offered by those providers under their applicable terms, including Google's and Firebase's data processing terms.

12. Security

We use reasonable technical and organizational measures to protect your information, including:

• Encrypted connections: HTTPS/TLS for network traffic.
• Provider-managed security features such as Firebase security controls and encryption at rest.
• Access controls intended to limit data access to the correct user account.
• Firebase App Check and related integrity checks to reduce abuse of our backend services.

However, no method of electronic transmission or storage is 100% secure, and we cannot guarantee absolute security.

13. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. If changes are material, we may also provide notice inside the App.

14. Contact Us

For any questions, requests, or concerns about this Privacy Policy or your data, please contact:

Email: alexeyg2006@gmail.com

We aim to respond within 7 business days.

This policy was last updated on June 22, 2026.