Bytelore Privacy Policy

Effective October 25, 2026.

This policy applies to the Bytelore Python, Bytelore JavaScript, Bytelore Java, Bytelore C#, Bytelore Rust, Bytelore Go, Bytelore Swift, Bytelore Delphi, Bytelore Clojure, Bytelore SQL, Bytelore 1С apps for iOS, macOS and Android, to the web version and to the Playground on byte-lore.online. All editions handle data identically: they share one server, one account and one set of data.

1. Data we process

• Account: email address, display name, email verification status. When you sign in with Apple or Google - the identifier the provider shares.
• Learning progress: results per topic and level, task solutions, league participation.
• Purchases: transaction confirmations from the App Store and Google Play (no payment details - we never see or store them).
• Receipt sent to support: if you bought a paid edition in a store that gives the app no way to confirm the purchase, support unlocks it from the receipt you send. We keep a copy of that receipt only as proof of the access granted, show it to no one, and delete it together with the access or with your account.
• Support message: if you write to us through the form on the support page - the email address for our answer, the text of your message, the browser or app string (version and device) and the connecting address. All of it is needed to answer and to look into the problem; we keep messages for no longer than a year, and a resolved one is deleted earlier at your request.
• Code Recipes forum: the same account can post on the forum of code-recipes.byte-lore.online. If you post there, we keep the display name, the text and code of your posts (they are public), the time of publication and editing, the connecting address, reports, hidden participants and forum suspensions; the connecting address is erased after 90 days and when the account is deleted, and attempts refused by the profanity word list are kept for 30 days. Details are in the Code Recipes privacy policy.
• Technical reports: anonymous app error reports; they contain no personal data by design.

We do not collect data for advertising, do not track you across other sites, and do not sell data to anyone.

2. Why

The data makes the service work: syncing progress between devices, confirming purchase entitlements, running the league and the Code Recipes forum, answering requests and fixing bugs. We only send transactional email - address verification and password recovery.

3. Processors involved

• Apple and Google - sign-in and payments under their own terms;
• an email delivery service - sending transactional messages to your address;
• Anthropic - a tone check of published Code Recipes forum posts (only the post text and code are sent, without the name, email or connecting address), as our service provider, under its commercial terms.

Data is stored on our servers with restricted access.

4. Retention and deletion

Data is kept while your account exists. You can delete the account in the app settings; all associated data (profile, progress, league history, sign-in links) is deleted. Code you run in the sandbox just to try it lives only for the duration of the run and is not stored; solutions to tasks that you submit for checking are stored in your account to track your progress.

Support messages are a deliberate exception: they live separately from the account and outlive its deletion, because the most common message of that kind is a request to delete the account, and the record proves the request was carried out. We keep such messages for no longer than a year.

Code Recipes forum posts are the second exception: when the account is deleted they are not deleted but anonymized (the link to the account is removed and "deleted participant" is shown instead of the name).

5. Children

The service is not intended for independent use by children under the age of data-processing consent in your jurisdiction.

6. Changes and contact

Policy changes are announced in the app. Questions and data requests: obraztsov-develop@yandex.ru. Terms of Use are here.