Privacy Policy

Last updated: October 12, 2026

This document explains, in plain language, what data Individual Entrepreneur Albert Akhmadiev (the "Operator", "we") processes when you use the ByteFit service: the Telegram bot, the Telegram Mini App, the iOS app, and the bytefit.ru website. We explain why we need this data, where it is stored, who receives it and how much of it, how to delete your account, and what rights you have.

The Operator is an individual entrepreneur (a natural person) and acts as the personal-data operator (and, where EU/EEA or UK data-protection law applies, as the data controller). This Policy has been prepared in accordance with Federal Law No. 152-FZ "On Personal Data", the data-localization requirement (242-FZ), other laws of the Russian Federation, and, where applicable, the EU General Data Protection Regulation (GDPR) and the UK GDPR. The most important thing to know up front: we do not sell your data and we do not use it for third-party ad targeting. By using the service, you agree to the terms of this Policy.

1. The personal-data operator

The operator that determines the purposes and the scope of the processed data is:

For any questions about personal-data processing, and to exercise your rights, write to bytefit.ai@gmail.com. This is the main channel for such requests. We also accept and review requests received through our other official channels (in-bot support and the Support page).

The Operator processes personal data in accordance with Federal Law No. 152-FZ "On Personal Data" and takes the measures required by law, including those relating to notifying Roskomnadzor about the processing of personal data and about the cross-border transfers described in Sections 2.7 and 5.

2. What data we process

We collect only the data needed to run the service and to comply with the law. The exact set of data depends on which channel you use (the bot and Mini App, the iOS app, or the website).

2.1. Data you provide yourself

• Profile details: optional name, height, weight, age, gender, activity level, nutrition goal, interface language.
• Personalized targets: calorie and macro targets calculated for you and, in the iOS app, water, steps and sleep targets as well. In iOS, targets are kept only on your device.
• Food diary: meal entries and their nutritional value computed by AI; generated meal plans, saved recipes, and weekly recaps.
• E-mail and/or phone for sending the fiscal receipt and for support contact.
• Support requests: the text of your message and a contact for our reply.

2.2. Data collected automatically

• Technical and log data: IP address, request time, error logs.
• Feature-usage counters (for example, how many messages you sent to the AI coach in a day).
• In the iOS app, usage events for product analytics, if it is on (see Section 2.7).

2.3. Data from integrations

• Telegram: your user id, username, and first name.
• Subscription and payment status: plan, status, dates, masked card number, transaction ids.

2.4. Website data

• Anonymized analytics and cookies (the site shows a consent banner, see Section 11).

2.5. Technical data for iOS subscriptions and response recovery

For iOS AI features, the server stores a random installation identifier, hashed session secrets, the free-analysis state, and technical counters. Subscription checks process Apple product and transaction identifiers, the purchase environment, and access status and dates. This does not require registration, a name, or an email address. ByteFit does not receive Apple Account credentials or payment-card details.

To recover a response after a network interruption without a new AI request, the food-analysis result (meal name, ingredients, grams, calories and macros, and assessment notes) is temporarily stored on the server. This is a technical response copy, not diary synchronization. The original photo and request text are not stored in this operation log.

Body measurements, food intake, calorie and macro targets, and activity level are health and fitness data used to estimate nutrition and personalize recommendations. In iOS, sending a coach message transmits the completed profile details, current targets, recent food entries, conversation history, language, and time zone. The service is not a medical service and is not intended for diagnosis. Do not submit examination results, medical documents, or other information that is unnecessary for discussing nutrition.

2.6. Apple Health in the iOS app

Starting with version 1.5, the ByteFit iOS app can show steps, water and sleep from the Apple Health app on its Home screen. Access is requested only after you tap "Connect" on the Home screen or an Apple Health button in a tracker sheet: iOS then shows its own screen where you choose what to allow. Without access, you can log water and sleep by hand, and you can remove any tracker from the Home screen.

What the app reads from Apple Health. Only what you allow, and only for recent days:

• steps: today, by hour and for the last 7 days;
• water: today, including water logged by other apps;
• sleep: the last 7 nights, with duration, bedtime, wake-up time and sleep stages if your watch or sleep app records them.

What the app writes to Apple Health. Only what you log yourself, and only if writing is allowed: water you add in ByteFit and sleep you log by hand. These entries are marked as entered by you. If you delete a water entry in ByteFit, the app also deletes its copy in Apple Health. ByteFit never changes or deletes entries made by other apps.

Apple Health data stays on your device.

• It is not sent to the ByteFit server, to AI providers (OpenAI, Google) or to any other third party. The Operator never receives it.
• It is not used for advertising or marketing, and it is not sold.
• ByteFit's own copies are not included in your iCloud backup: the app keeps the latest values and your water and sleep entries in a separate folder on your device that is excluded from backups. Water and sleep entries are kept there for at most 35 days.
• Only you see it: on the Home screen and in tracker sheets, in the ByteFit widget on your device's screen, in Bite's lines and in the water and sleep reminders. The app works all of this out on your device. Notification texts do not contain your steps, water or sleep values. The system may hide step and sleep numbers in the widget while your device is locked.

Water, steps and sleep targets. These are not Apple Health data. A target is calculated on your device from your profile, entered by you, or suggested by AI from your questionnaire answers (see Section 5.4). Apple Health data plays no part in target setup.

How to turn it off. Access is managed only in the Apple Health app: Profile → Apps → ByteFit. There you can turn off reading and writing of steps, sleep and water. You can remove trackers from the Home screen in ByteFit: Profile → Home. After you turn access off, the app stops receiving new data. Entries that ByteFit saved to Apple Health stay there until you delete them in the Apple Health app. Deleting ByteFit removes its data from your device.

2.7. Product analytics in the iOS app

To understand how many people use the ByteFit iOS app, which features they need and where something goes wrong, the app can send short records of actions, called events, to the product analytics service PostHog. An event only says that an action happened, not what it contained: for example, "app opened", "meal saved" or "subscription screen shown".

What is sent.

• the event name and neutral parameters: the source (camera, photo library, text or voice), the onboarding step, where the subscription screen was shown, the error category (for example, "no network"), the number of photos in an analysis, and whether you have a subscription or a trial;
• for the subscription screen and purchases: the plan and its billing period, the plan's App Store list price and currency (not the amount charged), whether it was a trial or Bite's gift offer and, when a gift is redeemed, whether it had been opened. Transaction and account identifiers are not sent;
• the event time, plus a random analytics ID and a session ID that the app generates itself. The analytics ID is not linked to your name, your account, the installation ID on the ByteFit server or Apple's device identifiers (the advertising identifier IDFA and the vendor identifier IDFV);
• app and device details: app version and build, iOS version, device model, the app and device language, screen size, network type (Wi-Fi or cellular), how the app was installed (App Store or TestFlight) and the App Store storefront country.

What is never sent. Your IP address is not stored: PostHog discards it on receipt, IP-based location lookup is turned off, and the app does not request your location. Events never contain your name, e-mail, food diary, dish, product or venue names, barcodes, photos, any text you type or dictate, coach messages, calories or macros, targets, weight, height, age, sex, Apple Health data (including events that would depend on that data), or purchase and installation identifiers.

Who receives it. The app sends events directly to PostHog (PostHog Inc., USA) over a secure connection; the ByteFit server does not receive them. We use PostHog Cloud EU, so events are stored in the EU, in Germany (Frankfurt). PostHog processes them on our behalf and may access them from the USA under its data processing agreement (DPA), which includes the EU Standard Contractual Clauses, and under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework. Events are not used for advertising, are not sold and are not used to track you across other companies' apps and websites. We do not treat this data as anonymous: the analytics ID links the events from one device until you turn statistics off and on again.

By country. The country is taken from the App Store storefront, that is, the country of your Apple Account, not from your location.

• the App Store storefronts of Russia, Kazakhstan and Uzbekistan: analytics is not used. The app sends no events, and there is no switch in Profile;
• the European Union and the European Economic Area, the UK and Switzerland, and cases where the storefront country cannot be determined: analytics stays off until you turn it on yourself, and nothing recorded before that is sent. While the country cannot be determined, the switch is not shown in Profile; it appears once the country is known;
• all other countries: analytics is on by default, and you can turn it off at any time.

How to turn it off. Profile → Usage statistics. Once it is off, the app makes no further requests to PostHog: events recorded before that and not yet delivered are deleted from the device, not sent. The only exception is a batch of events that was already being sent at that moment. If you turn statistics back on, the app creates a new random analytics ID, so new events are not linked to the earlier ones. The technical request the app then makes to PostHog also carries a random technical ID that the PostHog library keeps on the device; that ID is never part of an event. This switch is separate from the permissions in Profile → AI data sharing: neither turns the other on or off. It does not affect how the app works.

How long data is kept. PostHog keeps events for 1 year from receipt, after which they are deleted. If this period changes, we will update this Policy in advance. Events are not linked to your name, e-mail or account, so we cannot find and delete them using such details; they are deleted when the retention period ends.

Legal basis. In the EU, the EEA, the UK and Switzerland, and wherever the storefront country cannot be determined: your consent, which you give by turning the switch on and withdraw by turning it off (GDPR Art. 6(1)(a)). This consent also covers storing the analytics ID on your device. In the other countries where analytics is used: the Operator's legitimate interest in improving the service (GDPR Art. 6(1)(f); clause 7 of Part 1 of Article 6 of 152-FZ). You can object to this processing at any time by turning the switch off.

3. What we do NOT keep

We deliberately limit the storage of sensitive content. The following are not stored on our servers:

• Food photos. A photo is processed to recognize the dish and estimate its calories, and is then discarded and not kept by us.
• Voice recordings. Your voice is processed to convert it to text and estimate nutrition, and is then discarded.
• AI-coach conversation text. The content of your messages to the coach is not stored. We keep only a usage counter (how many messages were sent in a day).
• Menu page photos and delivery cart screenshots. They are sent for reading and are not kept by us, and neither is the hint. Only the scan result is kept temporarily, for at most 7 days (see Section 5.2).
• "Ask Bite" questions and replies. They are not stored. We keep only the daily limit counters.
• Apple Health data. Steps, water and sleep from the Apple Health app are never sent to the ByteFit server and are not kept by us (see Section 2.6).

Only the result stays in your diary, for example the dish name and the calculated calorie and macro values that you see in your history.

4. Purposes and legal bases for processing

We process data only for specific, clear purposes:

Where the legal basis is consent, you can withdraw it at any time (see Section 10). Withdrawing consent does not affect processing that is necessary to perform the contract or that is required by law, and it does not affect the lawfulness of processing carried out before the withdrawal.

5. AI processing and cross-border transfer

To recognize your food and answer your nutrition questions, part of your data is sent to third-party AI providers, OpenAI and, for iOS food analysis and menu reading, Google (Gemini), with processing outside the Russian Federation (in particular, in the USA). This is a cross-border transfer of data to a foreign country that may not provide an equivalent level of personal-data protection. The coach, target setup and "Ask Bite" in iOS use OpenAI; photos, descriptions, ingredients, portions, nutrition values and refinements for iOS food analysis go to Google (Gemini).

Only what is needed to produce an answer is sent to the AI provider:

• the food content: the dish description, the text of the request, the voice transcript, and the AI-coach prompt;
• the necessary profile and nutrition context, without which the feature could not give a meaningful answer.

In iOS, a coach request includes your profile name if provided, along with the necessary nutrition context. E-mail, phone, and Telegram id are not added as separate fields to this iOS request. Text you submit may itself contain personal information; we do not treat such requests as anonymous. iOS voice input uses the system Apple Speech service, which may use Apple servers; ByteFit and the AI provider receive the resulting text, not the audio recording.

5.1. Several photos in one food analysis

In the iOS app, one analysis can include up to four photos, for example a dish from different sides or several dishes from one meal. All the photos you choose are sent together with your description in the same way as a single photo: to the ByteFit server and from there to Google (Gemini). The app downsizes each photo before sending. It is one analysis: the free first analysis can also include several photos. Only the first photo is kept with the diary entry on your device, as its cover; the others are not kept once the entry is saved. The ByteFit server does not store photos.

5.2. Reading menus and delivery carts

The ByteFit iOS app can use AI to read a venue's menu or a screenshot of a delivery cart and estimate the calories, protein, fat and carbs of each item. This happens only if you have a subscription or trial and tap "Allow and read the menu" yourself. Before anything is sent, the app shows which data is shared and with whom.

What is sent.

• photos of menu pages or cart screenshots, one to six at a time;
• an optional hint of up to 300 characters, usually the venue's name;
• the interface language and the type you chose: menu or cart.

Your name, food diary, food photos and coach chat are not sent. A cart screenshot may show a delivery address, phone number and recipient name. Hide them before sending; the app lets you crop a page. On your device, the app also looks for lines that resemble an address or a phone number on screenshots from your photo library and covers them before sending; you see how many lines were hidden and can undo any of them.

Who receives it. The data goes to the ByteFit server, which passes each page, the hint and the language to Google (Gemini), the provider of the AI model. Your data may be processed outside your country, including in the United States.

Why. To produce a list of dishes with estimated nutrition, portion and price. These are estimates from the menu text, not exact data; for allergens the app suggests asking the staff.

A separate permission. Permission for menu reading is separate from the permissions for food analysis, the coach and target setup: none of them allows menu reading, and it allows none of them. You can withdraw it in the app: Profile → AI data sharing → Menu reading. Withdrawing stops future requests. It does not recall data that was already sent. Saved venues, searching them, picking dishes on your device and logging them work without this permission and without a subscription.

How long data is kept.

• On your device. A venue is saved only when you tap "Save venue": its dishes and compressed photos of its pages ("Original menu"). They stay on your device only and are deleted with the venue. Until a scan result is saved or discarded, the app keeps the pages and the result temporarily, for at most 7 days, so that a retry after a lost connection does not scan the menu again.
• On the ByteFit server. The scan result (the venue's name and type, the currency and the list of dishes with descriptions, prices and nutrition) is kept under the request key for at most 7 days. That way, sending the same request again returns the same answer without a new scan and without being counted again. The server does not keep the page photos or the hint: to recognise a retry, it keeps only a checksum of the request. Phone numbers, e-mail addresses and lines that look like an address are removed from the result before it is kept.
• Server logs contain only a technical request ID, the status, the duration, the access-check outcome and the number of pages and dishes. Photos, the hint and the model's reply are never written to logs.

5.3. "Ask Bite" at a venue

At a venue you can ask Bite to suggest a set of dishes with AI, for example "something warm, under $20". This happens only if you have a subscription or trial and the coach permission, and you send the question yourself. Picking dishes without AI works on your device and sends nothing.

What is sent. This venue's dishes (up to 150): name, type of dish, calories, protein, fat, carbs, price, tags and up to three words of ingredients, under temporary numbers; the meal; how many calories you have left today and, if your protein, fat and carbs targets are confirmed, how much of those; an optional budget and an optional wish of up to 200 characters. The venue's name, photos, your name and diary entries are not sent.

Who receives it. The data goes to the ByteFit server, which passes it to OpenAI (United States), the provider of the AI model. It is the same model the coach uses. The server checks your wish for explicit mentions of an illness: such a wish is not passed to OpenAI, and the app suggests discussing the topic with a doctor and shows its own suggestions without AI.

Why. To suggest up to three sets of dishes that fit what is left of your day, your budget and your wish. The server itself checks that every set uses dishes from this menu and stays within your budget. Bite cannot know allergens for sure, so please check with the staff.

Permission. The same as for the coach: Profile → AI data sharing → Coach and recipes. Withdrawing stops future requests and does not recall data that was already sent.

How long data is kept. The ByteFit server keeps neither the request nor the reply; only the daily limit counters remain. Logs contain only a request ID, the status, the duration and the access-check outcome. Your chosen dishes and budget are kept only on your device, with the venue.

5.4. Nutrition and daily targets setup

The ByteFit iOS app can use AI to suggest daily targets for calories, protein, fat and carbs and, starting with version 1.5, water, steps and sleep targets in the same setup. This happens only if you choose AI setup yourself, when you first open the app or later from the Home screen, Profile or the Daily targets screen, and give permission with "Allow and find targets". Before anything is sent, the app shows which data is shared and with whom.

What is sent. Your answers for the target setup:

• weight goal: lose, maintain or gain;
• sex, or "not specified";
• age, height and weight;
• activity level;
• an optional note of up to 200 characters and the tags you choose: "I work out", "No meat", "Sweet tooth".

Along with your answers, the app sends the ByteFit server the interface language and your device's date and time zone. Your name, food diary, photos, coach chat and Apple Health data (steps, water, sleep) are not sent: water, steps and sleep targets are based only on your questionnaire answers.

Who receives it. The data goes to the ByteFit server. The server passes your answers, language and tags, together with the calorie needs and allowed target ranges it calculates from your answers, to OpenAI (United States), which provides the AI model. The server does not pass the date or time zone to OpenAI.

The ByteFit server checks your note for explicit mentions of health: pregnancy, breastfeeding, diabetes, an eating disorder, medication or another condition. Such a note is neither passed to OpenAI nor stored. Your targets are then calculated without a calorie deficit, with a suggestion to discuss them with a doctor, and no water, steps or sleep targets are suggested. The check relies on explicit wording: if the server does not recognise a health topic, the note goes to OpenAI together with your other answers.

Why. To calculate your daily targets and explain them. The targets are a guide, not medical advice, and you can change them in the app at any time.

A separate permission. Permission for target setup is separate from the permissions for food analysis, the coach and menu reading: it does not allow sending your diary or photos, and those permissions do not allow target setup. You can withdraw it in the app: Profile → AI data sharing → Target setup. Withdrawing stops future requests and deletes the temporary request record on your device. It does not recall data that was already sent.

Without this permission you can enter your own targets or calculate them with a formula on your device, with no AI and nothing sent.

How long data is kept.

• On your device. The request (your answers, note and the result received) is kept temporarily so that a retry after a lost connection does not use the free setup again. It is kept for at most 24 hours and is deleted sooner once your targets are saved or the permission is withdrawn. Saved targets (calories, protein, fat, carbs, the date and the explanation, plus water, steps and sleep targets) stay only on your device, in the app's profile.
• On the ByteFit server. The result (calories, protein, fat, carbs, the explanation and tips, plus water, steps and sleep targets) is kept under the request key for at most 24 hours. That way, sending the same request again returns the same answer without a new calculation and without using the free setup again. The server does not keep your answers or note: to recognise a retry, it keeps only a checksum of the request. A mark that the free setup has been used on this installation is kept with the installation's access data.
• Server logs contain only a technical request ID, the status, the duration and the access-check outcome. The request body, your note, the targets and the model's reply are never written to logs.

5.5. Separate consent for cross-border transfer (Art. 12 of 152-FZ)

In accordance with Article 12 of Federal Law No. 152-FZ, the cross-border transfer of data to such a country is carried out on the basis of your separate, informed consent. You can withdraw this consent at any time (see Section 10), and it covers:

• recipients: Google (Gemini) for iOS food analysis and for reading menus and delivery carts; OpenAI for the coach, target setup, "Ask Bite" and the service's other AI features;
• countries: the USA (outside the Russian Federation); Google may also temporarily store or cache data in other countries where Google or its agents maintain facilities;
• purpose: food recognition, reading menus and delivery carts, dish suggestions at a venue, setting daily nutrition, water, steps and sleep targets, and AI-coach answers to nutrition questions;
• data categories: food content and nutrition context; in iOS, also completed profile details and an optional name, conversation history, and recent food entries; for target setup, questionnaire answers (weight goal, sex, age, height, weight, activity level), an optional note and tags; for menu reading, menu page photos or cart screenshots and the hint; for "Ask Bite", the venue's dishes, what is left of your day's nutrition, the budget and the wish. Apple Health data is never transferred (see Section 2.6).

In the iOS app, each feature asks for its own permission before it first sends data. Food analysis (including AI refinements) is allowed only after you tap "Allow and start analysis", the coach and recipes after "Allow and send", target setup after "Allow and find targets" (see Section 5.4), and menu and delivery cart reading after "Allow and read the menu" (see Section 5.2). "Ask Bite" at a venue uses the coach permission (see Section 5.3). Using the app, purchasing a subscription or restoring purchases does not grant these permissions automatically. You can withdraw any permission in "Profile → AI data sharing"; this stops future AI requests for that feature but does not recall data already sent. Manual entry, your local diary, saved food, history, and targets you enter yourself or calculate with the formula remain available without these permissions.

The cross-border transfer is carried out in compliance with Article 12 of 152-FZ, including the Operator's duty to notify Roskomnadzor about the cross-border transfer of personal data. If you do not give this consent, the features that require AI processing stay unavailable, while the rest of the service keeps working. You can withdraw your consent at any time (see Section 10); once withdrawn, the transfer stops.

5.6. International transfers and GDPR safeguards

If you are in the EU, the EEA, or the UK, this transfer to the USA is an international transfer under the GDPR and the UK GDPR. We rely on your explicit consent for it and, where applicable, on appropriate safeguards such as Standard Contractual Clauses or equivalent contractual measures, to the extent these are in place with the relevant provider. You can ask us for more information about these safeguards by writing to bytefit.ai@gmail.com.

Product analytics events from the iOS app (Section 2.7) are stored in the EU, in Germany. Where PostHog Inc. accesses them from the USA, it relies on the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, and on the Standard Contractual Clauses in its data processing agreement.

6. Payment data

Purchases are made inside the Telegram bot. Payments in rubles are accepted through T-Bank internet acquiring (JSC "TBank"). Card payment happens on the bank's secure payment page: you enter your card details there, not with us.

• The Operator never receives or stores your full card number or CVV.
• For display only, we store the masked card number and the card brand, plus transaction ids and a token for recurring charges (RebillId).
• Payment notifications reach our server through a cryptographically signed request (verified with SHA-256); forged callbacks are rejected.

Purchases in the iOS app are handled by the App Store (Apple) under Apple's rules; Telegram Stars payments go through Telegram. In these cases, the payment data is processed by the relevant platform.

7. Who we share data with

We use trusted service providers (processors) strictly to the extent needed to run the service. We do not sell personal data and we do not pass it to ad brokers for targeting.

In addition to the above, data may be disclosed to authorized government bodies where the law requires it.

When you explicitly look up a barcode, the iOS app sends the product code directly to Open Food Facts. That service also receives the IP address and app User-Agent; the request does not include your profile, diary, or photos. Open Food Facts keeps technical request logs containing the IP address, the URL with the product code, User-Agent, and response metadata for diagnostics and API usage statistics. This processing follows the Open Food Facts privacy policy; ByteFit does not set the retention period for those API logs. Open Food Facts privacy.

8. Where data is stored and how it is protected

The core data of bot and Mini App users is stored in our database on secure cloud infrastructure located in the Russian Federation. This ensures compliance with the requirement to localize the personal data of Russian citizens (242-FZ).

An important difference between channels: in the iOS app, diary entries are stored on the device itself; in the bot and Mini App, entries are stored on the Operator's secure servers.

Product analytics events from the iOS app (Section 2.7) are stored by PostHog in the EU, in Germany (Frankfurt). They are not collected for the App Store storefronts of Russia, Kazakhstan and Uzbekistan.

• Data is transmitted over secure, encrypted channels (TLS/HTTPS).
• We apply organizational and technical protection measures, and access to data is restricted.
• For recurring charges we use a bank token (RebillId), not the card number.

We do everything reasonably possible to protect data; however, no method of transmitting or storing information can guarantee absolute security. If, despite our measures, a personal-data breach occurs, we will take steps to mitigate the consequences and will notify Roskomnadzor and the affected users (and, where the GDPR applies, the competent supervisory authority) in the cases and within the time limits set by law.

9. Retention periods

We keep personal data no longer than necessary for the purposes of processing or to comply with the law. The specific periods are:

• Profile and food diary: while your account is active. After a request to delete your account (see Section 10) or after a long period of inactivity (as a rule, after 12 months), this data is deleted or anonymized.
• Food photos, voice recordings, and AI-coach message text: not stored (see Section 3).
• The technical copy of an iOS AI-analysis result is available for redelivery for 7 days from the start of the operation; background maintenance then removes its content. A compact record of the operation identifier, request hash, and outcome remains to prevent duplicate execution.
• A menu or delivery cart scan result is kept on the server under the request key for at most 7 days; page photos and the hint are not stored (see Section 5.2). On your device, an unsaved scan is kept for at most 7 days, and a saved venue stays until you delete it.
• "Ask Bite" requests and replies are not stored on the server. Only the daily limit counters remain (see Section 5.3).
• A target setup result is kept on the server under the request key for at most 24 hours; questionnaire answers and the note are not kept (see Section 5.4).
• Apple Health data never reaches the server. On your device, the water and sleep entries you log in ByteFit are kept for at most 35 days, and the latest values until the next update (see Section 2.6).
• Product analytics events from the iOS app are kept by PostHog for 1 year from receipt and then deleted. Once "Usage statistics" is off, nothing more is sent and events not yet delivered are deleted from the device; turning it back on creates a new analytics ID (see Section 2.7).
• An iOS access secret is valid for 15 minutes; its server-side hash is removed on revocation or by background maintenance after expiry. The refresh-secret hash and installation record remain to continue the same session. Verified purchase, installation-binding, and Apple notification metadata remain after a subscription ends for restoration and duplicate protection; these technical records currently have no automatic age-based deletion. Deletion requests are handled as described in Section 10.
• Temporary iOS rate counters and the IP-address hashes used in them are removed by background maintenance once their counter window is more than two days old. This does not change the technical-log retention periods below.
• Payment and accounting records (including data for fiscal receipts): for the periods set by accounting and tax laws (as a rule, at least 5 years). The basis is a legal requirement.
• Technical logs (IP, request time, error logs): as a rule, up to 12 months, to the extent needed for security and diagnostics. The basis is the Operator's legitimate interest.

The absence of photo and conversation-text storage described above applies to ByteFit servers. Processing by the AI provider is subject to its retention rules: standard OpenAI API abuse-monitoring logs may contain requests and responses and may be retained for up to 30 days, with exceptions for legal and safety requirements. This is separate from the seven-day technical result copy in ByteFit. OpenAI API data controls.

For paid Gemini API services, Google provides for limited retention of requests and responses to detect violations, maintain security and meet required legal disclosures. Data may be temporarily stored or cached in countries where Google or its agents maintain facilities. These rules are separate from technical-result storage in ByteFit. Gemini API terms.

Once the processing purposes are met, or upon your request, data is deleted or anonymized, except for information we are required to keep by law (for example, accounting and fiscal records).

10. Your rights and account deletion

Under 152-FZ you have the right to:

• obtain information about the processing of your personal data;
• request that inaccurate or incomplete data be clarified (corrected);
• request deletion or blocking of data if it is processed in breach of the law or is no longer needed for the purposes of processing;
• withdraw consent you previously gave, including consent to cross-border transfer (Section 5);
• object to product analytics in the iOS app, or withdraw your consent to it, by turning off "Profile → Usage statistics" (Section 2.7);
• appeal our actions to Roskomnadzor or in court.

10.1. Additional rights for EU/EEA/UK users (GDPR)

If the GDPR or the UK GDPR applies to you, you also have the right to: access your data and receive a copy of it; have inaccurate data rectified; have data erased ("right to be forgotten"); restrict or object to processing; data portability (receive your data in a structured, commonly used, machine-readable format); and to withdraw consent at any time without affecting processing carried out before the withdrawal. You also have the right to lodge a complaint with your local data-protection supervisory authority. We do not use your data for automated decision-making that produces legal or similarly significant effects on you.

You can object to product analytics in the iOS app (Section 2.7), or withdraw your consent to it, at any time by turning off Profile → Usage statistics. After that, the app sends nothing more to PostHog; if you turn it back on, a new analytics ID is created.

10.2. How to delete your account and data

To fully delete your account, send a request to bytefit.ai@gmail.com from the contact linked to your account, or via in-bot support. After we confirm that the account is yours, we delete your profile, personalized targets, diary entries, plans, recipes, recaps, and the saved payment details for recurring charges. This is normally done within 30 days.

Deleting your account ends access to the paid features. We do not delete information that we are required to keep by law, first of all the accounting and fiscal records of completed payments (for the periods set by law). Such records are stored separately and are not used for any other purpose.

To exercise any of these rights, send a request to bytefit.ai@gmail.com. We will review the request and respond within the period set by law (as a rule, within 30 days). For your own safety, we may ask you to confirm your identity or your ownership of the account.

11. Cookies on the website

The bytefit.ru website uses cookies:

• necessary cookies, for the site to work correctly;
• analytics cookies, for anonymized visit statistics that help us improve the site.

On your first visit, a consent banner is shown. You can manage cookies through your browser settings; disabling some cookies may affect how certain site features work.

12. Minors

The service is intended for users aged 14 and over. For users under 18, we recommend using the service with the involvement of a parent or legal guardian. We do not knowingly collect data from people under 14. If you believe we have processed a child's data below the permitted age, please write to us and we will take action.

13. The service is not a medical service

ByteFit is informational and reference in nature and is not a medical service. It does not diagnose, prescribe treatment, or replace a consultation with a doctor or dietitian. The calorie and macro estimates are calculated by AI and are approximate, so they may contain errors. Please check them and adjust them if needed. If you have any illness, are pregnant, have allergies, or have other health considerations, be sure to consult a specialist.

14. Changes to this Policy

We may update this Policy. The current version is always published openly at /en/privacy.html, with the update date shown at the top of the page. We will try to announce material changes in advance. Continuing to use the service after a new version is published means you have reviewed it. Related documents: Public Offer, Terms of Use, Refund Policy, Support.

15. Contacts