Privacy Policy — Scrome

1. Who we are

Scrome is developed and published by Emre Space (emrespace.com). This policy applies only to the Scrome app and the backend services we operate for that product (production API: scrome.emrespace.com).

This policy does not cover third-party websites, stores, or services that we do not control, including Google, Apple, Google Play, or the App Store outside the app. The emrespace.com marketing website is separate from the Scrome app.

2. Privacy summary

In short:

• You create a Scrome account with Google Sign-in (and, on iOS, Sign in with Apple when that option is available).
• We store your profile, learning progress, Daily Routine completion, word-card knowledge, and — if you use classroom features — class membership, assignments, submissions, and grades.
• A study partner sees only the summary you share after both of you accept (username, display name, avatar, streak, known-word count). There is no messaging.
• Avatar photos you choose are stored on our servers. Grammar notes ship in the app. Word catalogs and progress sync through our API.
• We use Firebase for analytics, crash reporting, performance monitoring, Remote Config (including force-update), and App Distribution. We do not use Firebase Auth or Firestore as the user database.
• We do not sell your personal information. Scrome does not currently include ads or in-app purchases.

3. Information we collect and process

Depending on how you use Scrome, we may process the following categories of information.

• Account information: email address, name, and profile picture from Google Sign-in (or Apple identity on iOS when used), plus session tokens we issue (access JWT and refresh).
• Profile: display name, unique username, avatar, CEFR level, learning intent (learn / join a class / teach), selected skills, daily-goal preference, theme and language stored on the device, and the in-app notifications switch.
• Learning progress: word-card knowledge (known / not known), Daily Routine slot completion and streak, grammar-topic marks, and related practice answers needed to continue the session.
• Classroom data (if you join or teach): institution and class membership, class invite codes you enter, assigned quizzes / exams / lessons, your answers (including writing text and speaking recordings when those tasks are submitted), scores, teacher feedback, and grading drafts the teacher saves.
• Study partnership: partner search by unique username, pending requests, and at most one accepted partnership, plus the summary fields listed above.
• In-app notifications we generate for partnership events (request, accepted, declined, ended).
• Local app state: card progress and similar data in an on-device database (SQLDelight) until synced; session tokens in platform secure storage.
• Diagnostics and usage data (via Firebase): product events (for example login method and tab selection), performance traces, crash logs, device / OS information, and app version. We do not include email addresses, writing answers, or speaking recordings in those events.
• Remote configuration: non-personal values such as minimum supported version and force-update messages from Firebase Remote Config.

4. Sign-in and your account

Scrome requires an account. On Android and iOS you sign in with Google. On iOS, Sign in with Apple may also be available. We receive the identity token and basic profile fields the provider shares (email, name, and — for Google — a photo when one exists). We do not receive your Google or Apple account password.

After sign-in you complete a profile (avatar, display name, username, CEFR, and intent). You can edit profile fields later in Settings. Email comes from the identity provider and is not changed in the app.

You can sign out on this device, or permanently delete the Scrome account from Settings. Deleting the account revokes sessions and deletes the user record and associated data we store (including the avatar file we hold). Uninstalling the app without deleting the account leaves server-side data in place until you delete the account.

5. Learning progress and content

Word lists and practice items are loaded from our API. Fixed grammar notes are bundled in the app and read offline. Card knowledge is written locally first and synced in batches (for example after splash restore or when you leave the Cards tab if you swiped cards).

Daily Routine completion (including streak) is stored so the home screen and partner summary can show progress. We do not keep a history of individual wrong answers as a lasting archive.

A daily-goal change you make in Settings applies from the next day, not the current day.

6. Classroom, institutions, and assessments

If you join as a student (class code) or as a teacher (institution code), we process class membership and assigned work so the product can function.

Teachers in your class can see membership, assigned work status, submissions, scores they publish, and — for speaking/writing tasks — the answers you submitted so they can grade them. Other students do not receive your private answers.

Institution codes are issued by us; teachers do not create institutions in the app. Leaving or deleting your account removes the membership records we store; it does not delete the institution itself or other people’s work.

7. Study partner

You may search for another user only by their unique username and send a partnership request. A user may have at most one active partnership. There is no in-app messaging or motivational push campaign between partners.

After both sides accept, each partner can see the agreed summary: username, display name, avatar, streak, and known-word count. Email, tokens, classroom submissions, and other account details are not shared with a partner.

8. Photos and avatar

A profile photo is required to finish registration. You may use the photo Google provides or pick one from the device (Android Photo Picker; iOS PHPicker / Photo Library access as declared in the system prompt). We upload the image you choose to Vercel Blob and store a public avatar URL on your profile. We do not access your full photo library for any other purpose.

When you delete the account we delete the avatar object we store.

9. Microphone and speaking

Speaking practice (Daily Routine skill) and classroom speaking tasks record audio on your device when you start a recording. Daily Routine speaking is used to complete that step on the device; we store completion/progress, not a long-term archive of those practice takes.

If you submit a classroom speaking answer, the recording (or a URL to it) may be stored with the submission so your teacher can play it back and grade it. We do not use speaking audio to train general AI models or to serve ads.

10. Notifications

Where the operating system requires it (Android 13+ notifications permission; iOS notification permission), we may ask for permission so the app can show operational alerts. In Settings you can turn the in-app notifications preference off.

We generate in-app notifications for partnership events. We do not send marketing push campaigns. Platform push delivery (FCM / APNs) may be used for the same operational events when it is enabled in a given build.

11. Analytics and diagnostics

Scrome uses Google Firebase services to operate and improve the app:

• Firebase Analytics — product events with non-personal parameters (for example login method and selected tab). Advertising-identifier collection for Analytics is not used to personalize ads; Scrome has no ads.
• Firebase Crashlytics — crash stacks and related diagnostics.
• Firebase Performance Monitoring — traces for startup and key flows.
• Firebase Remote Config — minimum supported version and force-update messaging.
• Firebase App Distribution — used by us to distribute debug / preview builds, not as your learning database.

12. How we share information

We do not sell your personal information. We share or disclose information only in these limited ways:

• Vercel — to host the Scrome API.
• Neon — to store accounts, progress, classroom, partnership, and related data.
• Vercel Blob — to store avatar files (and speaking or other media files when a feature uploads them).
• Google Sign-in and, on iOS, Sign in with Apple — to verify your identity.
• Firebase Analytics, Crashlytics, Performance, Remote Config, and App Distribution — as described above.
• Your study partner — only the summary fields after mutual acceptance.
• Your teacher / class (if you joined a class) — membership, assignments, submissions, and published grades as needed to run the class.
• Legal requirements: we may disclose information if required by law, legal process, or to protect rights, safety, and integrity.
• Business changes: if Emre Space or Scrome is involved in a merger, acquisition, or asset transfer, information may be transferred as part of that transaction, subject to appropriate privacy protections.

13. Storage, security, and retention

Communications with our API use HTTPS/TLS. Session tokens are stored in platform secure storage. Local card progress uses an on-device database.

We keep account and learning data while your Scrome account exists and as needed to operate the service. When you permanently delete the account we revoke sessions, delete the user row (and cascaded records we store), and remove the avatar file we hold.

Uninstalling the app without deleting the account leaves server-side data in place until you delete the account. Firebase analytics, crash, and performance data are retained according to Google Firebase retention settings and our operational needs.

14. Children’s privacy

Scrome is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children. Classroom features are intended for users who meet that age requirement and are authorized to join the institution or class. If you believe a child has provided personal information through the app, contact us and we will take appropriate steps.

15. Your choices and rights

If the EU General Data Protection Regulation (GDPR), the Turkish Personal Data Protection Law (KVKK), or similar laws apply to you, you may have rights to access, correct, delete, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority (in Türkiye, the Kişisel Verileri Koruma Kurumu). To exercise these rights for data we hold, contact [email protected].

• Edit profile, CEFR, daily goal, theme, language, and the notifications switch in Settings
• Sign out of this device, or permanently delete your Scrome account from Settings
• Revoke Scrome access at myaccount.google.com/permissions (Google) or in Apple ID settings (Sign in with Apple)
• Revoke photo, microphone, or notification permissions in system settings
• End a study partnership from the app when that action is available
• Clear app storage / cache or uninstall the app

16. International processing

Our processors (including Vercel, Neon, Google, Apple, and Firebase) may process data in the United States or other countries where they operate infrastructure. If you use Scrome from another country, information may be transferred internationally subject to those providers’ safeguards and applicable law, including KVKK and GDPR where they apply.

17. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date on this page. For material changes, we may provide additional notice in the app or on emrespace.com.

18. App stores and platform permissions

When you download Scrome from Google Play or the Apple App Store, that store’s own privacy practices also apply to download, billing, reviews, and account management. Platform permission dialogs are controlled by the operating system vendor.

Contact us

If you have questions about this Privacy Policy, your data, or privacy rights related to Scrome (including KVKK and GDPR requests), contact us at: