Revision dated October 23, 2026.
This revision takes effect upon publication as the current revision on October 27, 2026 (UTC).
Website analytics rules have applied since September 16, 2026. This revision adds no new website analytics purposes and does not reset your choice; website and app settings are independent.
1. Who processes data
Developer and personal data controller: Individual Entrepreneur Lopatka Aleksandr Fedorovich.
Legal address: Uzbekistan, Tashkent, Unusobod Markaz 6 Mavzesi, 90-UV 85-Xonadom.
Privacy, support and deletion: head.stat@gmail.com
This Policy covers Shopping List STAT and its services, the shoppingliststat.com website and the shoppingliststat.app mirror. It explains actual data processing rather than authorizing any purpose. Features depend on app version, platform, service availability and the selected plan. Sections about shared lists, price-label recognition and purchases apply to versions supporting them from 1.3.0 onward. Including a section does not mean those features operate or collect data in version 1.2.0. Notes, item photos and audio attachments are unavailable in version 1.3.0 shared lists. Optional telemetry is controlled separately from acceptance of the Terms. Email invitations and remote push notifications are disabled in the Android 1.3.0 release; local reminders remain a separate feature.
2. Use without an account and local data
Lists, items, prices, quantities, currencies and exchange rates you enter, categories, recipes, personal text notes, selected photos, personal audio notes and settings may be stored on your device. Core local features do not require an account. Personal-note photo and audio files are not uploaded by personal synchronization; personal note text may be synchronized under section 4. Using the app without an account does not mean there are no network requests: system speech recognition, device services, update checks, technical settings and separately permitted telemetry may use the internet. Image recognition processing and SDK technical requests are explained separately below.
You can edit and delete app content. Trash, recoverable personal notes and deletion records may retain content for restoration and synchronization. Stopping sharing is not the same as deleting the account or every copy: supported data may remain for the list owner’s personal recovery. For permanent deletion, use the applicable app action or submit a data deletion request. Clearing local storage and system backups depends on the OS. The app cannot remotely erase independent copies or exported files held by recipients.
3. Account and sign-in
On registration or sign-in, Google/Firebase processes the email address, account identifier, sign-in provider, session data and technical information including the IP address and client information. The app profile may store a name, email, avatar color, and the date and version of Terms acceptance. Google or Apple sign-in supplies profile information authorized by that provider, including a photo if provided. Loading that photo contacts its provider’s server.
To confirm which Terms were accepted and when, Cloud Firestore stores a separate record: account and acceptance identifiers, the versions and publication dates of the Terms and Privacy Policy, acceptance and server-confirmation times, language, sign-in provider, an app-generated installation identifier, platform, device model, OS version, app version and build number. When the sign-in screen offers a synchronization choice, the record also contains the selected switch position and the synchronization disclosure version. These details support the account and evidence Terms acceptance: they are stored independently of permission for analytics, diagnostics and list synchronization, retained as account data, and deleted with the account. A local acceptance record is stored on the device.
Email and password sign-in is provided by Firebase Authentication. We do not receive your Google or Apple account password and do not ask you to send passwords or verification codes to support. An Apple private relay address may be used as the account email.
4. Personal synchronization and shared lists
When you explicitly sign in with email, Google or Apple, the Terms screen includes a synchronization switch that is initially on for that sign-in attempt. You can turn it off before accepting the Terms. Acceptance records the selected position; exchange begins after successful sign-in, server confirmation of acceptance, and satisfaction of service-availability and local-data ownership requirements. Cancelling or failing sign-in does not change the saved setting. You can also manage synchronization in Settings. Cloud Firestore receives supported lists, items, prices, quantities, custom categories, note text, and synchronization metadata: record and installation identifiers, timestamps, protocol versions and deletion records. The profile and Terms acceptance records are stored in the cloud independently of list synchronization.
Personal synchronization between devices using one account and a list shared by different accounts are separate modes. In personal synchronization in version 1.2.0 and the 1.3.0 implementation described here, note photo and audio files, recipes and system reminders are not uploaded by that feature. All notes, including text, photo and audio notes, and item photos are disabled in version 1.3.0 shared lists. When a personal list becomes shared, those notes and files are not sent to members or uploaded as shared content. Turning off personal synchronization stops new personal synchronization, but does not delete an existing cloud copy or by itself end shared-list membership.
When you enable sharing or accept an invitation, the server processes the list and owner identifiers, member identifiers, members’ selected display names and available profile photos, list and item names, supported item fields (quantity, price, currency, status and category), participant action attribution and technical change revisions. Members can access these data according to their roles. Shared text, photo and audio notes and item photos are disabled in version 1.3.0; personal note files are not sent into shared lists. Disabling a feature does not automatically prove deletion of files from earlier testing or builds: any such data must be addressed when verifying account deletion and stored remnants.
Leaving a list, removing a member and stopping sharing affect future access but cannot guarantee immediate erasure on an offline device. Revoking an invitation or link prevents new joins but does not itself remove members who have already joined. The app may retain the last available copy for offline use; after receiving confirmed revocation it restricts access to the shared list and clears the related managed copies. A local list lock does not control other authorized members’ actions and does not provide end-to-end encryption.
In the Android 1.3.0 release, invitations use a link: you choose the recipient and the app used to share it. Server email invitations are disabled; the app does not offer an email address field for sending invitations or promise email delivery. Accepting a link does not automatically create an account or membership. Earlier addressed invitations and emails, if any, are handled separately when checking deletion and retention. Their addresses are used only for the original invitation, access checks, abuse prevention and related support requests. Opting out of further emails is available through the original email link or head.stat@gmail.com after address ownership verification. A minimal technically protected opt-out key may be kept separately from an account; it is not anonymous data. Enabling email in the future must not send accumulated invitations.
If, after sign-in, the device contains shopping data from another account, the app requires a choice: transfer it to the current account as separate copies, or delete the local shopping data. This choice is required even when synchronization is off. Transfer creates new identifiers; similar lists are not combined by name and duplicates may remain. Photos, audio notes and reminders are retained locally. Transfer does not itself enable synchronization, but if synchronization is already allowed, supported copies may be uploaded to the current account’s cloud storage. Local deletion requires confirmation and does not delete the previous account’s cloud data. Recipes, their ingredients, the catalog, settings and files needed by retained records remain on the device; links to deleted custom categories may be reset.
5. Speech recognition and audio notes
Speech recognition starts at your request after a disclosure and the required system permissions. Audio is processed by the device’s system speech provider, such as Google, Apple or another installed service. Depending on the device, language and settings, the provider may send audio and technical information to its servers. The app receives recognized text; we do not save a separate audio recording for this feature. Saved text may be synchronized if synchronization is allowed.
Personal audio notes are a separate feature: at your request, the app records an audio file and saves it on the device. That file is not included in personal synchronization. Personal-note photos are also not uploaded by that synchronization. Notes and audio attachments are unavailable in version 1.3.0 shared lists. Turning off microphone permission does not delete existing personal recordings; use the applicable app action to delete them. Voice input through system speech recognition and sending files yourself through Share are separate actions described separately.
You can use manual entry, stop recording or recognition, and revoke permissions in system settings. Revoking a permission does not delete text or audio notes already saved. The app is not designed for covert continuous listening.
6. Other device features
Camera access supports price-label recognition and available local photo features; the microphone supports voice input and personal audio notes; photo selection supports personal local attachments; notifications support local reminders. Remote push notifications are disabled in the Android 1.3.0 release. These permissions do not enable disabled notes, item photos or audio attachments in shared lists. System biometrics unlock locally protected lists: the app receives an authentication result, not fingerprints or face templates. Import through Share processes the text you provide; export transfers selected data to your chosen app. Permissions are requested for the relevant actions; available manual and local features remain usable without them.
Price-label recognition runs on the device. In the current recognition flow, camera frames are not sent to our server for analysis or to a cloud artificial-intelligence model. Check recognized values before using them. Recognized text and prices you save become data in the selected list and may take part in its personal synchronization or sharing. A scanner frame does not become an item photo or shared attachment; item photos and notes are unavailable in version 1.3.0 shared lists. Separate scanner diagnostic recording is described below. Recognition availability and quality depend on the camera, device, OS, supported recognition mechanisms, language and image.
Local image processing does not mean there are no technical requests. Android uses Google ML Kit: its SDK documentation describes Google receiving app and device information, installation identifiers and technical performance information, including processing duration, configuration and errors, for SDK diagnostics and usage analytics. This is separate from optional Google Analytics for Firebase and Crashlytics; those switches do not themselves control ML Kit. An explanation is shown before first starting the relevant recognition feature, and any consent required by applicable law is obtained before processing. iOS uses the system Vision framework; Apple also governs its system services.
Google ML Kit technical data processing
Opening the scanner normally does not enable diagnostic recording. If you separately enable it in the scanner menu, the app saves technical measurements and diagnostic session settings on your device. An additional choice, initially off, allows the recording to include individual camera frames or crops and recognized text. The recording may contain information from price labels and the surrounding scene and is not considered anonymous. Recording stops automatically after 30 seconds, but stopping does not delete files already created. A diagnostic archive is not sent automatically: at your request, it is passed to the system share menu, where you choose a recipient or another app. Before sending it, consider that the archive may include saved images and text. Exported copies exist separately from the app’s local recording.
In version 1.3.0, additional-currency amounts use an exchange rate you enter manually. The app does not obtain an automatic bank or market rate for this feature. Rate values are stored locally; amounts and currency labels saved in a synchronized or shared list are processed as that list’s content. Conversion is informational and may differ from a store price, bank rate or actual charge.
Remote push notifications are disabled in the Android 1.3.0 release, and delivery through Firebase Cloud Messaging is not offered. Local reminders are generated on the device and do not require remote push delivery. The app code handles notification preferences, disabling and revoking previous device registration; previously created tokens and technical records, if any, are considered separately when verifying deletion. Disabled delivery does not confirm erasure of data previously sent to a provider. Declining notification display is not an account deletion request.
For purchases, Google Play or the App Store and RevenueCat process product and transaction information, access status and duration, renewals, cancellations, restores and refunds, and technical client information. RevenueCat receives an identifier linked to the app account; it may initialize after sign-in, before a purchase, to check access and retrieve offers. Our server stores the necessary verified access state. These records support fulfillment and verification of purchases, restoration and protection against incorrect access grants; RevenueCat also provides purchase statistics. We do not receive your bank card number from the store or use these records for cross-service advertising tracking.
If you report a violation in a shared list, we process your identifier, the relevant list or member identifier, the selected reason, an optional explanation, only necessary excerpts of disputed text, the technical time and the operator’s decision. Entire lists are not automatically uploaded as part of reports. Access is restricted to authorized operators and service processes. A separate block record links the blocker and blocked account to prevent future invitations and direct interactions; it is not used for advertising. You may contact support about a decision. Retention periods are stated in section 11.
Clipboard import suggestions are enabled by default if no different choice has been saved. On launch and return to the app, when the main screen is ready, the app reads clipboard text before import confirmation and may offer to import it. Adding it to lists requires your confirmation. Before import, the app does not persist the text or send it to a server as part of this check. After showing a suggestion, it stores only a hash of the text locally to avoid suggesting it again. A newly shown suggestion replaces the previous hash; detecting an empty clipboard while checks are enabled, or clearing app data, removes it. Dismissing a suggestion, restarting or disabling suggestions does not itself remove the hash. You can turn suggestions off in Settings; a saved refusal is respected. iOS may also request system permission to paste. After a confirmed import, the text becomes list content and may be included in allowed synchronization.
We do not use location, contacts, SMS or call-history access for app features, collect payment card details, or use advertising identifiers for advertising. Do not add passwords or information unnecessary for the purpose of lists or recordings. Sensitive information you choose to add will be processed as part of that content.
7. Analytics, diagnostics and service settings
Google Analytics for Firebase is enabled only after your separate choice. It processes app usage events, app and operating system versions, device information and an installation identifier; the provider uses the technical IP address, including to derive general geography. List, note and recording content is not intended to be sent to analytics. We do not use this analytics for personalized advertising.
Firebase Crashlytics is enabled separately for error diagnosis. It processes crash reports, stack traces, event times, device and app technical information, and installation identifiers. We limit error messages to technical information and do not add list content, passwords, emails or account identifiers to custom report fields.
Google Analytics for Firebase and Firebase Crashlytics report transmission are off until you confirm your choice. Without a saved choice, the app offers to permit both or configure them separately. Transmission of these data to Firebase starts only after confirmation; declining does not restrict core features. With transmission disabled, native Crashlytics may create local unsent reports. The choice, notice version, time, language and source are stored on the device and are not changed by sign-in, sign-out or acceptance of new Terms. Saved refusals do not trigger repeated automatic requests. Settings stop new transmission of the relevant telemetry; unsent Crashlytics reports are deleted on disablement and before first enablement. Previously transmitted data follows providers’ retention and deletion procedures. These two switches specifically control Firebase Analytics and Crashlytics; processing for accounts, purchases, security, delivery and the recognition SDK is explained separately.
Firebase Remote Config receives an installation identifier and technical information to deliver feature availability and security settings. This exchange is separate from optional analytics. Update checks may contact Google Play or Apple services. Remote Config does not replace your choice to enable synchronization or telemetry.
8. Purposes and legal bases
- Providing requested accounts, personal synchronization, shared lists, invitations, purchases and support: performance of a contract or requested pre-contractual steps where that basis applies. When email invitations are available, for an invitation recipient without an account, our legitimate interest is delivering the specific invitation requested by its sender, where applicable law permits this basis and the recipient’s rights do not override it. Where the law requires the recipient’s prior consent, the sender’s request alone is insufficient. Recipients can stop further invitation emails.
- Optional analytics, diagnostics and processing requiring consent: separate consent. Operating system permissions and Terms acceptance do not replace required separate consents.
- Service security, abuse prevention and delivery of technical settings: legitimate interests in secure service operation, where permitted by applicable law and not overridden by your rights.
- Responding to binding lawful requests and fulfilling controller obligations: applicable legal obligations.
9. Recipients
Recipients, to the extent necessary, are Google/Firebase and Google Cloud for accounts, Firestore, server functions, Remote Config, App Check, FCM and selected telemetry, and for processing and deleting previously stored Cloud Storage files if any exist; Apple for selected system services, sign-in, APNs and the App Store; Google for Google Play and ML Kit technical data; RevenueCat for purchases; Resend for processing previously sent invitation emails, if any; the selected system speech-recognition provider; and the support email provider. Listing Cloud Storage does not mean that new photo or audio uploads are available in 1.3.0 shared lists. Other shared-list members receive its permitted content and member information within their access rights. Yandex Cloud serves shoppingliststat.com and Cloudflare serves shoppingliststat.app; YANDEX LLC receives separately permitted website analytics. We provide necessary access for the stated purposes and apply appropriate processing terms. Stores’ and system providers’ independent processing is also governed by their policies. New email invitations and remote push delivery are disabled in the Android 1.3.0 release.
Recipients processing data on our behalf are subject to confidentiality obligations, purpose and access restrictions, and safeguards consistent with this Policy and applicable law. We verify these terms before granting access. Stores’ and system providers’ independent obligations do not remove our own data protection and deletion duties.
Resend delivery service privacy policy
We do not sell personal data or share it for cross-context behavioral advertising. When you export content, the apps or people you select become recipients. We may disclose the minimum necessary information in response to a binding lawful request or to protect legal rights.
Firebase privacy and processing periods
10. International processing
The controller’s legal correspondence address is given in section 1. Providers may process data in other countries, including the United States; actual locations depend on the service and configuration. We do not promise that all data stays in your country. International transfers take place only with an applicable legal basis and required safeguards; choosing a feature does not override localization or international-transfer requirements. You may email us for information about specific recipients, countries, the applicable transfer mechanism and how to obtain a copy of safeguards relevant to you.
11. Retention and deletion periods
- Local data: until deleted in the app, app data is cleared or the app is uninstalled, subject to trash and system backup behavior. The app cannot remotely erase offline devices or copies made outside the app.
- Accounts and cloud content are retained to provide the requested features. Deleting an account and associated data requires ownership verification, handling related shared records and separate actions with external providers. An accepted request is distinct from completed erasure; completion is confirmed after verification, not merely after sign-out or deletion of a sign-in account. Independent copies held by other users, data on offline devices and specific lawful exceptions are considered separately. Applicable mandatory request-handling deadlines remain in effect. Previously shared photos, audio and notes are not automatically erased merely because these features are disabled. Retained private originals are available only to their rightful owner through protected mechanisms; an erasure request requires ownership and dependency checks without deleting other people’s data.
- An invitation is valid for 7 days after creation. Expiry or revocation prevents its use but does not confirm deletion of every invitation and delivery record. Cleanup periods for verified categories are given below. An invitation-email opt-out is stored separately: a minimal derived address key remains while the opt-out is valid. It is not used for mailing and is not arbitrarily removed when an account is deleted. Support can remove the opt-out after verifying ownership of the address; removal does not restore previous list access.
- Closed abuse reports become eligible for scheduled cleanup 90 days after closure; action-audit records do so 180 days after creation. An active block remains while it is in force; after unblocking, a minimal record is retained for 30 days after unblocking completes. A temporary shared-access conflict barrier remains until the conflict is resolved, independently of any continuing block. Open reports and justified dispute holds are excluded from ordinary cleanup. A hold must have a specific basis and a review date; it does not authorize indefinite retention without a basis. A derived opt-out key or technical identifier can remain personal data if it can be linked to a person.
- Pro entitlement information is needed to fulfill, restore and verify a purchase. Erasure of the associated RevenueCat profile and data in our systems is checked separately from Google Play’s or Apple’s payment records. Deleting an app or RevenueCat profile does not itself cancel a store subscription. Any information that must be retained is limited to a specific applicable lawful basis; the exception and retention duration or criterion must be explained when handling the request.
- Support contact details and correspondence are retained until confirmed closure of the case, then for no more than 90 calendar days. For an account-deletion request, closure means completion of the necessary actions and checks, not receipt of the request. Cleanup covers working emails, attachments and controlled copies. A justified dispute or mandatory legal retention may require a specific exception with a recorded basis and review date; the data must be deleted when that basis ends. A prepared email or technical receipt alone does not prove completed erasure.
Server-side installation safeguard records are retained until confirmed completion of account deletion and verification that old tokens, sessions and deferred operations cannot be reused. After safety is confirmed, they become eligible for cleanup after 30 days. Cleanup must not allow deleted data to be restored; a verifiable safeguard and specific review are required until that risk is resolved. Hashed identifiers and operation versions are not automatically anonymous. Deletion of the Firebase Installation ID is checked separately from deletion of the FCM token; Firebase services may create a new identifier on subsequent use. A separate temporary UID write block is retained while the deletion request exists and until its technical expiry, one day after the block is set; a justified hold prevents cleanup. The 30-day period after safety confirmation applies to installation safeguard records.
- Provider periods differ from our request-handling deadline. Firebase Authentication states that associated data is removed from live and backup systems within 180 days after user deletion is initiated. For a Firebase installation identifier used by Cloud Messaging, Google states the same period after a separate call to delete that identifier; deleting a push token does not confirm that this call was made. Crashlytics retains traces and associated identifiers for 90 days before starting removal from live and backup systems. These terms are not a universal retention period for all app data.
Successfully completed safety operations become eligible for scheduled cleanup 30 days after completion. Completed text-check jobs, including jobs superseded by a newer version, and successfully processed notification jobs become eligible for cleanup 7 days after completion. For an email, this period starts when the provider accepts it, not when it is read. Pending, retrying and failed operations are retained while safe completion, a retry or error investigation is needed. After 7 days of unsuccessful processing, operator review is required; after 30 days with an unresolved error, the operator must decide to retry, cancel, complete with verifiable confirmation, or document a justified hold with a basis and review date. Unfinished account deletion, critical protective blocks and justified holds are not deleted using the period for successfully completed operations. An error alone does not justify indefinite retention. Codes and addressed invitations are valid for 7 days. Invitation records, shared-link pointers and addressed projections become eligible for cleanup 30 days after expiry, normally 37 days after creation. Minimal receipts for successfully processed billing events and notification-preference changes are retained for 30 days after confirmed processing or receipt creation, respectively. Unfinished billing events are not deleted using the period for successful receipts. Daily anti-spam counters for new emails expire at the end of the next daily window; the repeat-send restriction for the same pair expires 2 days after its record is written. Expiry of an invitation, opt-out token or delivery permission does not mean all associated data has been physically erased. Cleanup uses background workers; TTL is asynchronous and does not guarantee deletion at the exact instant. Technical reminder-processing records are retained for 30 days after confirmed notification preparation, cancellation or expiry processing. Unprocessed scheduled work is not deleted using the period for completed operations; error-review rules apply after the scheduled time. In the verified primary Cloud Logging stores, server logs have a 30-day retention setting, while mandatory administrative and system audit logs have a 400-day setting that cannot be changed. Extended point-in-time recovery is disabled for the live Firestore database; its standard previous-version window is 1 hour. No backup schedules or backups for that database in its region were found during verification. This does not establish that no exports, copies outside the verified scope or provider-internal copies exist. In the verified private file store, a deleted object can remain recoverable for 7 days after deletion. This period does not automatically delete an active file and is not a retention period for files that have not been deleted. Resend’s public documentation separately describes email and log retention for standard plans and deletion after contract termination; these do not replace our delivery-queue retention period and must match the actual agreement. Deleting a customer profile through RevenueCat’s API or dashboard is a separate procedure; it does not cancel a Google Play subscription. A universal backup or archive retention period for our RevenueCat account has not been verified. You can send a data-deletion request to support at head.stat@gmail.com. Acknowledging a request, expiring a technical token or deleting a live database record does not confirm erasure by every provider.
- Google Analytics for Firebase event and identifier retention is set to 14 months. New activity does not reset the configured retention period for the user identifier. This setting does not automatically describe all aggregated reports, technical logs or provider backups; those follow retention necessary for their respective purpose and providers’ deletion procedures. We limit further use to the stated purposes and handle deletion requests within applicable legal deadlines. Turning collection off is not immediate deletion of previously transmitted data.
If a binding legal obligation requires retention of specific information, we limit its scope, access and use to that purpose and delete it when the basis ends. We explain the applicable exception and period when handling the request unless notice is prohibited by law. A technical error does not in itself justify indefinite delay.
12. Account deletion
In the app, open Menu → Account → Delete account. After confirmation and session verification, the server must acknowledge the request; while offline it has not yet been accepted. The app attempts immediate deletion and distinguishes completed deletion from an accepted unfinished request. An accepted request continues even if you close the app; proportionate identity re-verification may be requested when needed. An operator handles unfinished requests within the stated period. After a request is accepted, the deleted account’s local shared data and related managed files are cleared; a separate choice deletes its personal local data on the current device. Shared-list deletion covers your content and associated personal information as explained on the deletion page; another person’s entire list is not deleted merely because you leave it. Deleting the app account does not by itself cancel a store subscription: subscription management is separate and is not a condition for deletion.
13. Security
Transfers use secure connections, and cloud data uses authentication and account-based access rules. Administrative request processing is separate from the user app. A local list lock does not promise separate database encryption or end-to-end cloud encryption. Protect your device with a system lock. Absolute security cannot be guaranteed.
14. Your rights
Depending on applicable law, you may request access and a copy of your data, correction, deletion, restriction or portability, object to processing based on legitimate interests, and withdraw consent. Send requests to head.stat@gmail.com. We verify identity proportionately and respond within the deadlines required by applicable law. Contacting us does not limit your right to complain to a competent data protection authority or seek a judicial remedy.
Where California privacy laws apply, their applicable rights to information, correction, deletion and non-discrimination are provided within the scope of those laws. We do not claim that the CCPA applies to every user and do not engage in sale of data or cross-context behavioral advertising.
15. Age
The service is intended for users aged 16 and above and is not directed at children under 16. Any applicable requirement for a legal representative’s involvement in entering a contract still applies. We do not collect a date of birth for ordinary use. If we learn that a child’s data has been processed contrary to applicable requirements, we will investigate and take necessary action, including deletion.
16. Website and policy changes
The website is available at shoppingliststat.com and the shoppingliststat.app mirror. Theme and language preferences are stored in localStorage. Technical requests to the primary address are processed by Yandex Cloud, and requests to the mirror by Cloudflare. On shoppingliststat.com, Yandex Metrica starts only after separate website consent to measure visits, advertising sources and clicks on Google Play links. The recipient is YANDEX LLC. Transmitted data includes visited page addresses and campaign tags, referral sources, events, browser and device technical information, IP address and cookie identifiers; these data are not considered fully anonymous. We do not send shopping list contents or app account data to Metrica. Session replay, click maps and form tracking are disabled. This counter does not run on the mirror. Declining does not restrict the website or store links. Withdraw consent using “Analytics settings” in the footer: new transmission stops and Metrica records accessible to the site are removed. Withdrawal does not automatically erase previously transmitted provider data. Website choices are independent of app settings; see the cookie policy for details and retention.
We use Yandex Metrica data while they are used for website analytics and remain necessary for that purpose. When we stop using them, we initiate deletion of the collected data in accordance with Yandex’s available procedures and terms. Cookie expiry and visitor-parameter retention are not the overall retention period for statistics. Stopping collection does not itself erase previously transmitted data; provider-side deletion follows the provider’s procedures and terms. You can send a deletion request to our support team. Yandex’s terms separately provide for its use of anonymized or aggregated data for its own purposes; our criterion does not set a fixed retention period for that processing.
Website cookies and local storage policy
The current revision is published at this page’s stable address; previous revisions are available in the archive. A new revision describes features available in the relevant versions and does not convert an old receipt into acceptance of new Terms. Material changes are communicated in the app or by another appropriate method before the relevant new use of data. Where consent is required, processing does not begin before your choice. Continued use or opening this page is not consent to new optional purposes. Refusals of optional telemetry remain effective.