FIRSTLY · B2

Your practice. Your choices.

Privacy Policy

How Firstly handles your answers, progress and account information.

Updated 19 October 2026

1. Who is responsible

This policy covers the Firstly B2 app, its web version and related support. The individual operator is Alexander Zyulikov ("we"). For privacy questions and requests, contact support@codeveya.ru.

Firstly is an independent English exam preparation service. It is not affiliated with or endorsed by Cambridge University Press & Assessment.

2. Data we handle

  • Guest access and accounts. The app assigns a guest identifier and session so you can practise without signing in. If you choose email sign-in, we process your address, verification requests, code hashes, session records and a backup of your progress. If you choose Sign in with Apple or Sign in with Google, we receive from that provider an account identifier issued for our app and, when the provider shares it and confirms it, your email address. With Apple this may be a private relay address if you chose to hide your email. Google’s sign-in token can also include your name and profile photo; we do not store or use them. For Apple we also store a refresh token, encrypted, only so that we can ask Apple to revoke the app’s access when you delete your account. We never receive your Apple or Google password. Each sign-in method is a separate account: an Apple or Google sign-in is never linked to an email account because the addresses match. Guest identifiers and provider account identifiers are pseudonymous; records linked to them are not necessarily anonymous.
  • Practice. Your answers, scores, mistakes, vocabulary, study plans and mock-exam results are stored on your device. Synced answers and submitted AI attempts are also stored on our server. Signing in with Apple, Google or email allows a progress backup to be restored on another device.
  • AI feedback. We store submitted writing and sentence-transformation answers, speaking transcripts, feedback, estimated scores, request status and usage counts. For speaking, the app processes microphone recordings or an audio file you select. Firstly does not persistently store the audio recording on its server.
  • Device storage. Drafts, settings, AI permissions, cached exercises and results can remain on your device. Unfinished drafts, audio recordings and AI permissions are not part of the account progress backup.
  • Technical and support data. Infrastructure and application logs may include IP addresses, request paths, timestamps, response codes, timing and errors. We also process security rate-limit records and any email, attachments or device information you choose to send to support.
  • In-app support. If you contact the author, report a bug or send feedback, we store the message, its type, your optional reply email, app version/build when available, platform and interface language, linked to your account. Practice answers, recordings and clipboard contents are not attached automatically. These messages follow your account when you sign in and are erased when it is deleted; otherwise they remain until account deletion. Independent backups follow the schedule below. Drafts stay in memory on your device and are cleared on account cleanup.
  • Subscriptions. Apple and RevenueCat process purchase history, product and transaction identifiers, subscription status and dates, and an opaque app user identifier issued by our server. That identifier can be linked to your guest or signed-in account; it is pseudonymous, not anonymous. We do not receive your payment card details.

3. Why we use it

We use this information to provide exercises and feedback, save and restore progress, authenticate requests, enforce feature allowances, prevent abuse, diagnose failures and respond to support requests. Where a legal basis is required, these purposes rely on providing the service you request, our legitimate interests in operating and securing it, or consent where required. We ask for your permission before sending content for each AI feature.

Firstly does not sell personal information or use it for targeted advertising. The app does not include advertising or cross-app tracking SDKs.

4. AI and other providers

OpenAI: after you allow an AI feature, your content goes through our server to OpenAI. Writing and transformation reviews include your answer and the task. Speaking sends audio for transcription, then the transcript and task for feedback. Your email address is not intentionally included in these AI requests. Any personal information you put inside an answer or recording is part of the submitted content.

OpenAI states that API content is not used for model training by default. We request that text responses are not stored as retrievable responses; this does not disable provider security retention. OpenAI describes default abuse-monitoring retention of up to 30 days, with exceptions, and different rules for audio transcription. See OpenAI API data controls and the OpenAI Privacy Policy.

AdminVPS: provides our application hosting and email infrastructure. Our application server is in Finland; email infrastructure and AI processing can operate in other countries. The mail service handles your address and sign-in messages when delivering codes, and support correspondence.

Apple and Google (sign-in): if you choose Sign in with Apple or Sign in with Google, the sign-in itself takes place in Apple’s or Google’s own screen, and their privacy policies apply to it. We send them only a one-time random value that ties the result to your request, and receive the identity information described in section 2. The app signs out of Google immediately after the sign-in and does not use Apple or Google services for anything else. See the Apple Privacy Policy and the Google Privacy Policy.

Providers receive data needed for their role. We may also disclose information where required by applicable law or necessary to protect rights and the service. These pages use no analytics cookies or third-party advertising. Our providers may process information outside your country.

Apple and RevenueCat: Apple processes App Store payments; RevenueCat validates purchases and supports restoration, subscription access and purchase analytics in its dashboard. We send the server-issued user identifier, not your email address as a customer attribute. Purchase history and user identifiers can be linked to your account for app functionality and subscription analytics. We do not use these data for advertising or cross-app tracking. See the RevenueCat Privacy Policy and Apple Privacy Policy.

5. Storage and retention

Account data — for email, Apple or Google sign-in — and practice data remain until deletion. Guests become eligible for automatic removal after 180 days without authenticated server activity. Accounts with a valid session, active paid access or an ongoing AI request are protected from this cleanup. The inactivity clock for existing guests starts when this rule is deployed. Local data remain until cleared by the app, device, browser or you; offline activity alone does not refresh the server clock.

Sign-in codes are valid for 10 minutes and sessions for up to 30 days. A daily cleanup removes code records 24 hours after expiry, session records 7 days after expiry or revocation, and hashed authentication rate-limit events after 24 hours. One-time Apple and Google sign-in challenges are valid for 10 minutes; daily cleanup removes them 24 hours after expiry. These are cleanup thresholds; a daily run can add up to 24 hours.

Confirmed account deletion removes associated study data from the active database and the current device. It does not remotely erase offline copies on other devices or cancel Apple subscriptions. Infrastructure backups expire after 30 days and are removed by daily cleanup, which can add up to 24 hours. A separate deletion journal keeps only random current/former account identifiers and deletion time for 37 days, plus the daily cleanup window. It is checked before a restored database serves users so deleted accounts do not reappear. Only backups within the supported retention period may be restored.

When you delete an account created with Sign in with Apple, we ask Apple to revoke Firstly’s access to your Apple ID. If Apple cannot be reached, we keep only the Apple account identifier and the encrypted token for this purpose and retry daily; the record is removed after successful revocation or after 30 days at most. Deleting an account created with Google removes our link to your Google account; you can also remove Firstly from your Google Account’s third-party connections.

Application and Firstly web access logs rotate daily with 14 archives. Support email correspondence is handled separately and is not erased by the app’s automatic cleanup; contact us to request review or removal, subject to applicable legal obligations. OpenAI handles any retained provider records under its own data controls.

We use HTTPS, restricted access, private backup storage and hashed server session credentials. No storage or transmission system can promise absolute security.

Deleting an account removes our billing identity links. To prevent allowance resets after restoration, minimal purchase-period metadata, hashed transaction lineage and Writing/Speaking usage counts remain until the actual paid period expires plus 31 days; daily transformation usage remains until the next UTC midnight. These contain no answer, recording or email, but hashed identifiers are not a guarantee of anonymity. Daily cleanup can add up to 24 hours. Hashed webhook event identifiers remain for seven days. Independent backups follow the retention schedule above.

The device also stores a pending purchase marker with the account identifier and expected plan to prevent accidental repeat checkout after restarting. On logout or account deletion, the account identifier is removed; a pending plan marker may remain until verification, explicit restoration or device storage clearing. No receipt or practice content is stored in this marker.

Deleting your Firstly account does not cancel an App Store subscription and does not delete purchase/customer records held by Apple or RevenueCat. Provider records follow their own retention policies; contact us for help with privacy requests. Manage or cancel subscriptions separately in Apple subscriptions.

6. Your choices and requests

  • You can practise as a guest and never sign in.
  • You can decline AI processing. In Profile → AI data sharing, revoke permissions for future requests. This does not erase results or information already sent.
  • You can withdraw microphone permission in your device settings and choose whether to upload audio.
  • Open Profile → Delete account, or Delete guest data when using the app without email. Guests confirm deletion without adding an email address. For an email account, verify your email again if requested; for an Apple or Google account, sign in again with the same Apple ID or Google account. If the existing session or sign-in is unavailable, contact support@codeveya.ru. We may need information sufficient to identify the records and confirm that the request is yours; do not send passwords or sign-in codes.
  • You can stop using Sign in with Apple for Firstly in your Apple ID settings, or remove Firstly from your Google Account’s third-party connections. This blocks future sign-ins with that account but does not delete your Firstly data; use Profile → Delete account for that.
  • Depending on applicable law, you may request access, correction, a copy, deletion, restriction or objection to processing, withdraw consent, and complain to the relevant data protection authority. Contact us to exercise these rights.

Deleting the app or clearing browser storage alone does not delete server records. Deleting an account does not cancel an Apple subscription; manage it separately in Apple account settings.

7. Younger learners

Use the service only when you can lawfully consent to the relevant processing, or with any permission and supervision required from a parent or guardian. Do not include unnecessary personal or sensitive information in practice answers. A parent or guardian who believes a child has provided data without the necessary permission can contact support@codeveya.ru.

8. Changes

We will publish updates on this page with a new date. Material changes to AI sharing that require new permission will be presented in the app before the relevant processing. This policy describes the current service; changes to purchasing or additional providers require an updated disclosure.