1. Scope and operator
ИП Родин Дмитрий Евгеньевич is responsible for sanvimo.com. Public registration and contact details are on the seller page. For data enquiries, email support@sanvimo.com.
This document covers the informational website. The account, browser and Telegram diary, and the Android app belong to the Sanvimo app. Its single policy is linked below. Section 15 of the app policy covers YooKassa purchases and receipts, and section 17 covers RuStore Pay; this text does not replace it.
2. Demo, questionnaires and calculators
Demo diary entries, questionnaire answers and calculator results are processed in your browser. This website does not save them to your account or transfer them when you open the app. These exercises do not require a name, email or password.
Values stay in the open page’s memory and reset when it reloads. Do not enter secrets or information you do not wish to share in free-text fields. Questionnaire answers, portions, recipe contents and plan text are not included in the website’s own analytics events.
Opening the app takes you to a separate service. Sign-in details are entered on app.sanvimo.com; the marketing website does not receive your password or read your diary.
3. Technical data and remembering your choice
When you visit, your browser sends the server information needed to connect and deliver the page, including an IP address and request details. These may be used to operate and protect the website and investigate technical errors.
Your cookie choice is stored in browser local storage for 180 days to remember consent or refusal. If storage is unavailable, your choice applies only to the current page. Saving this choice does not create an account.
4. Yandex Metrica is optional
If you arrive from Yandex Direct, after you allow analytics Metrica also receives the advertising click identifier, yclid. It helps match the visit to an ad. The website carries this tag between its public pages in the URL without separately storing it. The website does not add it to sign-in, APK or Telegram links.
After analytics is allowed, the website may request a public registry of campaign tags from the app. The request sends no account cookies or referring page address. Our analytics events use only tags from the allowed registry; unknown values are discarded. This choice does not enable additional account analytics: the app’s single privacy policy explains its terms and settings.
Yandex Metrica loads after you allow analytics. It does not load before a choice or following refusal. Declining does not restrict demos, questionnaires, calculators or reading pages.
When allowed, Metrica uses cookies, technical browser data and information about views and actions. Our events describe clicks, section views and the start or completion of activities. Session Replay and click maps are disabled. Roadmap search text and arbitrary link parameters are not added to our events.
Change your choice through “Cookie settings” at the bottom of the page. Withdrawal prevents further Metrica loading and reloads the page, resetting current answers and the demo. Previously sent data are not automatically deleted; Yandex’s terms govern their processing and retention.
5. Support and external links
If you email support@sanvimo.com, your sender address, message and chosen attachments are used to respond. Include only what is needed to resolve the question. A support request is not consent to marketing email.
Links to Telegram, the app and payment services lead to separate platforms with their own data practices. Do not send full card numbers, security codes, passwords or one-time codes to support.
6. Website chat and consent to processing your request
The operator is ИП Родин Дмитрий Евгеньевич. By selecting the chat consent checkbox, you agree to your name, phone and conversation being processed to answer and follow up on your request, including sharing them with our support team in Telegram. Consent version: sanvimo.site-support.contact.2026-10-29. This is not marketing consent. Email requests, including refunds and data enquiries, do not require a phone number or CAPTCHA.
Before composing a message, chat asks for your name, phone and consent. “Continue” checks these fields in your browser; your contact details reach the server only with your first message after CAPTCHA verification. The phone is checked for format, without SMS, and does not verify your identity or account ownership. A request does not create an account or automatically link your contact details to purchases.
After consent, chat loads Cloudflare Turnstile to protect against automated submissions. Your browser connects to Cloudflare and sends technical connection data needed for verification. Our server checks the CAPTCHA result before creating a conversation. You can email us if verification is unavailable.
A secure chat session cookie lets you return to your conversation for up to seven days. It contains no name, phone or message text and cannot be read by page scripts. Contact details and drafts are not saved in localStorage, page URLs or the website’s own analytics events. Unsent text stays only in the open page’s memory and disappears when you reload it.
On this website, your name, phone, messages, consent and delivery records are available for seven days from the start of the conversation. They then become unavailable and are deleted during the next automatic cleanup. New messages and ending a chat do not extend this period. Copies already shared with the team in Telegram are not automatically deleted on this schedule; requests to delete them are handled separately, subject to legal duties.
To withdraw consent, ask about processing or request deletion, email support@sanvimo.com. Include details that help us find your request; passwords and sign-in codes are not needed. Replies arrive in the website chat while its history is available. Checking for replies pauses when the chat is closed or the tab is hidden; no notifications are sent when the browser is closed.
7. Purchases and receipts
A plan link opens the purchase section in a Sanvimo account and passes the selected plan and language. If the current page address contains a valid source tag, it is also carried between website pages and into sign-in or purchase links. The tag identifies the source of a visit; carrying it does not itself enable account analytics or replace the user’s separate choice.
The website carries this tag from the current page address without saving it in cookies or local storage. This mechanism does not copy other parameters from the current address, such as an email or arbitrary advertising parameters, into the app. It does not add the tag to APK, Telegram or payment-provider links. Viewing plans or following a link does not create an order or transmit card details. The final amount, payment availability and purchase confirmation are shown in the account.
A RUB purchase through YooKassa uses order details, amount and currency, a receipt email and confirmation of payment, refund and access. Receipts from YooKassa sends the prepayment receipt and later settlement receipts without another charge. Diaries, weight, questionnaire answers and private recipes are not shared for payment.
After account deletion, the email for outstanding receipts and refunds is held separately until those obligations are complete, then deleted automatically. Financial records remain for required record keeping. CloudPayments and foreign cards are being discussed separately; mentioning a future provider does not mean data are sent to it.
8. Data used for RuStore Pay purchases
On Android you can select RuStore Pay when available. Technical order and product identifiers and a pseudonymous buyer identifier link the payment to the purchase. Sanvimo receives payment and refund confirmations, the amount, currency and transaction identifiers to provide Pro to the correct account and handle support requests.
Account email, diaries, photos, messages and workouts are not passed in RuStore purchase fields. The payment service or bank handles bank details; Sanvimo does not receive or store them. Section 17 of the app policy and the RuStore policy describe technical data handled by its payment module.
The YooKassa receipt process does not automatically apply to RuStore. Payment confirmations may remain for required record keeping after account deletion. The app privacy policy describes the processing purposes and data in detail.
The RuStore badge loads from our website. Only clicking it opens the external store listing; no RuStore scripts or widgets are embedded here. The badge link contains no visitor parameters and does not send the referring page address.
9. Android, RuStore and updates
The Android app uses a Sanvimo account. The APK can be downloaded directly from this website; the app is also available on RuStore. New versions arrive on the website and Telegram first, then on RuStore after review. An alternative download and news are available through the external Telegram channel https://t.me/sanvimoapk. Downloading an APK does not itself install the app or create an account. Reading this page does not connect your phone or grant camera, file or notification access.
Device permissions belong to the installed app. Notifications, health-data and wearable integrations remain separate areas of development. New integrations will require a description of actual data processing and appropriate user actions before launch.
10. Data requests and document updates
Email support@sanvimo.com to ask about processing, correction or deletion of support data. We may request details needed to verify ownership, but not passwords or sign-in codes. Requests are handled within the timeframes required by applicable law.
Data are used to the extent and for the time needed for their stated purpose and legal duties. Deleting a request or account does not automatically remove records that must be kept by law. The app’s single policy describes the purposes and retention periods for app and payment data.
Edition dated 29 October 2026. We update this document and its date when website practices change. Preparing a future integration does not itself change your cookie choice.