Shopping List Privacy and Personal Data Processing Policy
Edition of November 18, 2026. Effective date: October 1, 2026.
1 General provisions and controller
This policy describes how Shopping List user information is processed, stored in the account, synchronized, and cached on devices. It also describes how requests and individual rights are handled.
The app owner and data controller is Individual Entrepreneur Nikolay Anatolyevich Akshentsev, tax identification number (INN) 023201000305, individual entrepreneur registration number (OGRNIP) 323366800109254.
Mailing address: 69 Leninska St., Korshevo, Bobrovsky District, Voronezh Region, 397731, Russia. Privacy and support email: hello@gomvp.dev.
This policy takes account of Russian Federal Law No. 152-FZ of July 27, 2006, On Personal Data. Groceries, recipes, and shopping-list details are considered together with their association with an account. A product name that cannot identify anyone on its own does not automatically exclude associated information from personal data processing.
2 People and information covered
This policy covers account holders, app users, and people who contact the controller. Information is collected during registration, use of features, and communications.
The app processes the following information:
- Account and profile information, including email and account ID. Standard registration requires an email address and a password. Sign-in through VK or Google also works without separately entering an email address or creating an app password. The app receives and stores the provider's user ID and the profile picture or its link when the provider supplies it. Standard VK and Google sign-in does not give the app the user's provider password. Name, phone number, an uploaded picture, and a VK profile link are optional. Name and photo are used for the profile. Name and provided contacts are used to respond to app-related issues. They are not automatically used for marketing.
- Kitchen information, including food names, amounts, units, expiration dates when that feature is used, record IDs, and association with the account.
- Shopping-list information, including list names, items, quantities, purchase marks, record IDs, and association with the account.
- Recipe titles, ingredients, user content, and favorites when those features are synchronized.
- Preferences and settings saved to and synchronized with the account.
- AI Chef prompts and history when the feature is available and stores that information.
- Support messages, including sender email, name if provided, correspondence, and necessary attachments.
When photo upload, voice entry, or family sharing is used, the provided photos, voice data, and information needed for the sharing selected by the user are processed for the relevant feature. Profile pictures are used to display the profile.
Allergies and medical conditions may constitute health data. This policy does not itself authorize their processing. The special requirements of Article 10 of Law No. 152-FZ apply. Do not include unnecessary health information, passport details, or information about other people in free text or enquiries.
Users supply accurate information about themselves and correct it when it changes. Users choose text entered in lists and recipes. They should omit information unnecessary for the app's purpose. Unrequested information is not automatically used for new purposes.
Users may submit another person's personal data only with a lawful basis. Uploading it alone does not prove that person's consent. When such information is received, the controller evaluates its own lawful basis and, when necessary, restricts access, blocks, or deletes the data in accordance with law. This does not shift the controller's duties to the user.
3 Purposes and legal bases
Account creation, sign-in, and recovery
Data used: account and required authentication information.
Legal basis: Article 6(1)(5) of Law No. 152-FZ, to the extent necessary to enter into the app agreement at the user's request and perform it.
Storing and synchronizing kitchen data, lists, and recipes across devices
Data used: account content and necessary record identifiers.
Legal basis: the same basis if the agreement covers the features and processing is necessary to provide them.
Profile display and app-related communication
Data used: name and photo to display the profile, and name, telephone number, and VK link for contact if supplied.
Legal basis: Article 6(1)(5) of Law No. 152-FZ, to the extent necessary for features selected under the app agreement. This does not cover marketing messages.
Optional settings, AI, and other optional features
Data used: only what is necessary for the enabled feature.
Legal basis: Article 6(1)(5) of Law No. 152-FZ when processing is necessary to deliver the feature selected under the app agreement. If processing extends beyond that scope and requires consent, Article 6(1)(1) applies and separate consent is obtained before processing starts.
Technical support
Data used: email, message, and necessary attachments.
Legal basis: Article 6(1)(5) of Law No. 152-FZ for support related to the agreement. For enquiries outside the agreement, Article 6(1)(7) applies if processing is needed to respond and does not infringe the individual's rights and freedoms. Data rights requests are handled under the controller's legal duties.
Handling personal data requests
Data used: content of the request and necessary contact and identity details.
Legal basis: Article 6(1)(2), to fulfill duties under Law No. 152-FZ.
The policy provides information. It is not general consent. When consent is needed, it is requested separately and confirmed by an action that can be demonstrated. Processing required for the agreement is distinct from optional processing. Reading or accepting this policy does not authorize marketing.
Withholding information genuinely necessary to register or perform the agreement may prevent use of the affected feature. Declining optional processing does not block independent features. Standard registration requires email and a password. VK and Google sign-in are available without separately entering email or creating an app password. Name, phone, photo, and VK link remain optional.
4 Server storage and the device cache
The app sends account information to the server for storage and synchronization. A device may keep a local copy for its interface and to access previously loaded information. Routine sign-out leaves the device cache in place.
The app server and primary account database are hosted in Moscow, Russia, on Timeweb infrastructure. Provider website: https://timeweb.ru/. Account information stored on the server is synchronized with the local app cache.
Timeweb's website lists JSC Timeweb, tax identification number (INN) 7810353960 and registration number (OGRN) 1247800127112, at 22 Zastavskaya St., building 2, lit. A, Saint Petersburg, 196006, Russia. Source: https://timeweb.com/ru/contacts/. This edition records the owner's statement that database backups were not created and the primary database and technical logs were on the Moscow server.
When collecting Russian citizens' personal data, the controller follows the applicable requirements of Article 18(5) of Law No. 152-FZ for using databases in Russia.
Processing includes collecting, recording, organizing, accumulating, storing, updating, retrieving, using, transferring for synchronization or lawful processing on the controller's behalf, blocking, deleting, and destroying information. Core processing is automated. Handling enquiries may involve manual steps.
5 Recipients and external services
Access is provided only on a lawful basis and to the extent needed for the stated purposes. Timeweb provides server infrastructure for account information. VK and Google are optional sign-in providers. Gmail is used to receive support email. Processing on the controller's behalf is subject to the required terms under Article 6(3) of Law No. 152-FZ.
The controller limits access to what the app needs and protects confidentiality. Infrastructure providers and external services process data as described here.
Messages to hello@gomvp.dev go through Gmail. Gmail's processing is subject to its own terms and privacy policy. Hosting the main app database in Russia does not mean external services process data solely in Russia.
If you choose VK or Google sign-in, the selected service is used for authentication. The app receives and stores the provider's user identifier and profile picture or its link if provided. The optional profile link is a separate field from information collected at VK sign-in.
The primary account database is in Russia. Google states that it uses servers in multiple countries in its privacy policy. External services may process data outside Russia. Cross-border transfers organized by the controller must meet Article 12 of Law No. 152-FZ. Data may be supplied to competent authorities when a legal basis exists.
Timeweb hosting does not change the individual entrepreneur's status or duties as controller. Providers acting on instructions are bound by the purposes and requirements in their agreements. A service that the user engages independently and outside the controller's instructions is responsible for its own processing under its own rules. The controller remains responsible for transfers it organizes.
When family sharing is enabled, information is shown only to the participants the user chose and within their permissions. Sharing a list does not authorize disclosure of the entire profile or account history.
6 Retention and deletion
Account, groceries, lists, and recipes
Information is kept while the account exists, until the user deletes it or the relevant purpose or applicable lawful basis ends. Inactivity alone does not cause automatic deletion. Deletion follows the procedures and time limits of Russian law.
Device cache
Data stays until updated or cleared under the app's rules. Account deletion clears local account data on the device where the request is made. Routine sign-out leaves the cache in place.
Server database backups made by the controller
This edition records no database backup retention period.
Support email
After resolution, correspondence may remain in the mailbox for repeat enquiries and to document the handling of complaints. It is retained only as long as needed for those purposes and with a lawful basis. Correspondence, attachments, and copies are deleted or anonymized when those purposes and legal bases end, unless the law requires further retention.
Personal data requests and records of their resolution
Information is kept as needed to consider the request, meet legal requirements, and show compliance. Any mandatory legal retention period applies. When lawful retention is no longer necessary, data, copies, and attachments are deleted or anonymized.
Clearing the cache, uninstalling the app, or signing out does not delete the server account.
Users can delete the account under Profile, Legal Information, Delete Account. Account data is deleted from the server, and the account cache is cleared on the device where deletion is requested. This includes saved profile data, groceries, lists, recipes, preferences, and AI chat history associated with the account. See Account and Data Deletion for handling of shared family records. If you cannot use the button, email hello@gomvp.dev. The controller verifies account ownership and handles the request on the applicable lawful basis.
Account deletion does not automatically erase support correspondence or records held on an independent legal basis. They are kept only for the purposes and lawful duration covered by this policy. They cannot be used to restore the account.
When the purpose is achieved or consent is withdrawn and there is no basis for continued processing, data is destroyed under Article 21 of Law No. 152-FZ. The general limit in those cases is 30 days, subject to the conditions and exceptions in law. Requests to stop processing are handled under Article 21(5.1). Withdrawal of consent does not end processing that has a separate legal basis.
Mandatory grounds and periods for retaining particular information are stated separately. If database backups are introduced, retention and deletion rules are determined before their use and the policy is updated.
After account deletion, particular information may remain only to the extent necessary on a separate legal basis, for example to comply with a specific statutory duty or handle a particular dispute. For each such situation the purpose, scope, basis, and period are determined. Potential future complaints do not by themselves justify retaining the entire account indefinitely. Information retained for a restricted purpose is not used for advertising or routine personalization.
7 Rights and requests
Users may obtain information about processing, request correction, blocking, or destruction in cases provided by law, withdraw consent, and complain to Roskomnadzor or a court.
Send requests to hello@gomvp.dev. Proof of identity and account association should be proportionate. Do not send a scanned passport in routine technical email unless needed. Article 14 of Law No. 152-FZ applies to formal requests.
The controller does not disclose information to someone merely because they know the account holder's name or email. Appropriate verification is required to prevent unauthorized disclosure or deletion. If the requester or subject cannot be determined, the controller explains what clarification is needed within applicable deadlines and requirements. A refusal must be based on and state a ground provided by law.
Information is supplied within 10 working days of a properly made request. An extension of up to five working days is possible with a reasoned notice. Confirmed inaccuracies are corrected within seven working days. Other requests are handled under Articles 20 and 21 of Law No. 152-FZ.
8 Security and access to the policy
The controller takes necessary legal, organizational, and technical data protection measures under Russian law, including protection of authentication data and limits on access. This policy does not specify particular password algorithms or transport protocols.
Users keep their credentials confidential, protect the device, and report suspected unauthorized access to hello@gomvp.dev. Do not send passwords, one-time codes, or session tokens to support. Failure to follow this advice does not automatically release the controller from liability. Circumstances and consequences are assessed under law.
This policy does not add a contractual guarantee of absolute security, instantaneous sync, or indefinite recovery of deleted data. It does not limit legal protections or change express guarantees in the agreement. If an incident occurs the controller complies with applicable response and notification duties. A hosting outage alone does not release the controller from liability.
The policy is available before registration and under Legal Information. App website: https://spisook.ru/. Before a new form of processing starts, the policy is updated if features, purposes, recipients, or data categories change. Additional required consent is obtained separately.
Changes cannot retroactively expand the purposes for which previously collected data is used. The controller notifies Shopping List users in the app about important changes and makes the new text available. Policy versions and evidence of consent are kept to the extent and for the duration required by the applicable legal basis.
9 Scope and liability
This policy governs data processing. The Terms of Use and any applicable agreements govern payments, subscriptions, refunds, use of recipes and AI recommendations, rights in user content, and permitted limits on contractual liability.
Liability is governed by Russian law. This policy does not waive mandatory rights, exempt the controller from liability for breaches, or require users to prove matters the controller must prove. If a provision conflicts with mandatory law, that law applies.
Sign in with Apple, iOS notifications, and purchase records
When you choose Sign in with Apple, Apple verifies its account identifier, your chosen regular or private relay email, and your name if you allow it. The app does not receive your Apple Account password. Linking to an existing account requires proof of ownership. Matching email addresses alone do not merge accounts. Credentials used to revoke Apple access are encrypted on the server and used when unlinking or deleting the account.
Remote iOS notifications are optional. Apple Push Notification service (APNs) is used after you enable notifications and grant system permission. Delivery uses a push token, installation and app identifiers, platform, and association with the account or session. Apple processes technical information and notification contents to deliver messages. Notifications may appear on the lock screen according to your settings. Turning notifications off or signing out removes server registration. It does not imply that Apple deletes technical records kept independently. Notification permission does not authorize marketing or purchase a subscription.
When an active App Store offer is available, the server processes transaction and original purchase IDs, product, access term and expiry, refunds or cancellations, and an account-linked random appAccountToken to verify and restore access. The app receives neither card information nor the Apple account password. Purchase records may be kept to the minimum necessary for restoration, preventing duplicate claims, and applicable requirements. This section does not enable purchases or grant an entitlement.
Apple privacy information: https://www.apple.com/legal/privacy/.
Separate permission to send data to OpenAI
An explanation of the OpenAI transfer and a request for explicit permission appear before the first AI request. Depending on the feature, the app sends your text, selected photos or audio, and the product, recipe, or nutrition profile context needed for the result. Do not send other people's information or unnecessary personal data. You can decline and keep using manual features.
Your choice is stored locally for this app, account, and regional server. Signing in to another account or choosing another server does not automatically grant permission. AI and Your Data in the account or documents section lets you withdraw it. Withdrawal stops future transfers via new requests. It does not cancel submitted jobs or erase past history. OpenAI privacy information: https://openai.com/policies/privacy-policy/.
Google Play purchase data
Supplement dated November 16, 2026. Google Play handles Android payments under its own rules. We do not receive the full card number or the Google password. The server processes app, product, and subscription option identifiers, purchase dates, term and status, an indirect ID for our account, and the purchase token to verify, restore, and grant access. The token is encrypted and sent to the Google Play Developer API for verification and acknowledgement. Periodic checks update access after cancellation, expiry, or refund. Test and regular purchases are distinguished. Purchase records are kept to verify access and handle disputed purchases. After account deletion only the records necessary for those purposes and any legally required records are retained.
Nutrition, prepared meals, and receipts across apps
Supplement dated November 18, 2026. Shopping List, goCalories, and Family Budget have a shared account and household on the selected regional server. For nutrition features, we process age, height, weight, sex used for the calculation, activity, goal, calculated or manual calorie and macronutrient targets, food names, meal times, portions and grams, calories and macronutrients, water, and selected photos. These can be health data. The questionnaire and calculation provide an estimate of nutrition needs. You can review and change the targets. They do not diagnose or provide medical advice. This description does not substitute for separate consent or another required lawful basis.
Prepared meal history stores a snapshot of the recipe, its ingredients and nutritional values, the quantity prepared, and remaining portions. Current household members with relevant permissions can access it. Editing the original recipe does not alter the saved snapshot. After you explicitly mark a portion as eaten, that portion is written to an authorized nutrition profile. Adults log their own food. Managing a dependent profile requires separate server permissions. Family subscription coverage alone does not give access to other adults' private diaries.
A nutrition card in your private chat displays targets, consumption, and what remains that day, based on your diary. An ordinary message to the chef does not log food automatically. Only using Share What You Ate sends selected text, comments or photos, and necessary profile context to the regional server and OpenAI for estimation. The separate AI permission described above applies. You can review and adjust the result, assumptions, and values. The diary record is created after confirmation. The saved notice and card belong to the author's private chat, not a household chat.
Selecting Add Receipt lets us process receipt photos, optional comments, store, date, items, quantities, prices, discounts, taxes, currency, and total, plus the chosen budget, category, and rate. After AI permission, selected photos and comments are sent to OpenAI for recognition. Check the amount and currency. Keep full card numbers and unnecessary personal information out of the image. Recognition does not record expenses by itself. Once reviewed and confirmed, the total becomes a single expense in the chosen budget. A shopping list can be linked for context.
The recognition draft and photos are accessible to the uploader with current permissions. The saved transaction and its receipt details are available to users who can read the selected budget. Creating an expense requires write access. Household membership alone does not grant budget access. Images remain restricted to the uploader. The uploader's private chat receives a short summary and budget link. The link does not replace sign-in and authorization. Manual financial entries and viewing the budget are not automatically sent to OpenAI.
By default food logging notifications do not include calories or diary details. Enabling detailed notifications separately allows a known calorie total to appear. Food names, weight, questionnaire responses, and daily targets are not included in push text. Receipt notifications stay general without the amount or line items. Delivery uses registered Shopping List installations and your notification settings. A notification can appear on a lock screen. Opening details requires sign-in and current access.
Saved entries, meal snapshots, and photos attached to confirmed entries are retained for their feature. Deleting the original recipe does not delete prepared meal snapshots. Drafts and temporary materials are subject to background cleanup. Closing the screen does not promise instant removal of all copies. Entries and the shared account follow applicable deletion procedures. Shared family information may remain with other household members. Russian accounts use the Russian server and international accounts use the international server. A region selection or link to another app does not transfer the account between databases. A selected AI feature can transfer data to OpenAI through an international service as described above. These materials are not sent for recognition unless those features are used.
Importing PDF receipts and confirming a record
Share allows one selected PDF receipt to be sent to the app. When recognition is requested and AI processing authorized, the regional server receives the file and sends it to OpenAI to read the store, date, total, currency, and line items. The app does not access other files on the device. Avoid sending statements or documents with unnecessary personal data. The original and draft are restricted to the sender with current access. A confirmed expense is available to authorized members of the selected budget. Cancellation before confirmation does not create an expense. Existing receipt storage and deletion rules apply to PDFs.
If a message describes a meal or an expense, the chef may propose a diary or budget record. Recognized data is saved to the diary or budget only after confirmation. A private nutrition reply can keep a snapshot of the result when the record was saved.