Privacy policy

1. Data controller

The data controller is Individual entrepreneur Zolotarev Mikhail Igorevich (INN 773319471109) — for the data of the business owners who use the service. Data-protection contact: support@get5stars.ru.

For guest data left in the «Prize for a review» mechanic, the controller is the owner of the location that displayed the QR code: they determine the purposes of processing and obtain the guest’s consent. get5stars processes such data solely on that owner’s instruction (part 3 art. 6 of 152-FZ) on the terms of section 8 of the public offer, and does not use it for its own purposes. The location owner is liable to the guest as a data subject; a guest with a question about their data should contact them. When the phone number is requested and in the promo rules, the guest is shown the owner details as the owner supplied them: the location’s name, plus the owner’s legal name and INN where those fields have been filled in. Supplying accurate details is the location owner’s obligation; get5stars does not verify them.

2. What data is processed

• Business-owner data: name, email, phone, Telegram id — for sign-up, login and notifications.
• Location and subscription data: map-listing links, settings, payment history, plus page opens and outbound map clicks from the last 30 days for Free and Pro locations.
• Auto-renewal data: the bank’s token for repeat charges; for a card payment, the card’s last 4 digits and expiry; for an SBP payment, where available in the account area, the bank’s name, its Faster Payments System member id and the service identifier of the account-binding request assigned by the bank; plus the date and time consent to auto-renewal was given, the IP address it was given from, and the offer edition in force at that moment.
• Guest data in «Prize for a review» (processed on the location owner’s instruction, see 1): phone and name if the guest provides them and consents; the rating and text of the review; details of the prize issued; the date and time of participation.
• Technical data: session cookies and service logs needed for the site and account area; once the visitor consents, analytics cookies and marketing cookies — see section 9.
• The necessary g5s_referral cookie: an opaque invitation value that the server links to a partner-programme participant. The cookie itself contains no name, phone number, email address, personal code or link.
• First-touch attribution: campaign labels, the shortened address of the referring page and the moment of first visit — this record falls under the «Necessary» category and is not gated by the cookie banner, see section 9.

3. Purposes and legal basis

Data is processed to provide the service (performance of the agreement — para. 5 part 1 art. 6 of 152-FZ), send notifications, take payment and issue fiscal receipts (54-FZ), and support users. The bank’s service token, the card’s last 4 digits and expiry, or the bank’s name and its SBP member id, are processed to make the automatic recurring subscription charges and to show the owner which payment method they are taken from. The date and time consent to auto-renewal was given, the IP address it was given from, and the offer edition in force at that moment are processed to evidence the fact and the terms of that consent — when handling requests, complaints and payment disputes, and to meet the requirements of the bank and the payment systems (pursuit of the controller’s rights and legitimate interests — para. 7 part 1 art. 6 of 152-FZ). Data is not sold to third parties and is not used for third-party advertising.

4. Sharing with third parties

To provide the service, data may be shared with infrastructure providers: the acquiring bank JSC «TBank» (payments, receipts; tbank.ru) and Telegram (notification delivery). Where paying via SBP is available in the account area, the transfer and the account binding take place in the Faster Payments System: the account data is processed by the payer’s bank and the SBP operator JSC «NSPK» — independently, under the payment system’s rules and the national payment system law; get5stars does not pass the account data to them and never receives the full account number. Sharing is limited to the data needed for that operation.

For visit statistics and advertising-performance measurement — only once the visitor has consented — data is shared with the enabled web analytics and advertising services; for session recording in the owner account area and staff console — with the enabled web analytics service (see section 9).

To fix failures of the site and the owner account area, error reports are sent to the technical error-tracking service Sentry (servers in the European Union). Such a report contains technical information only: the error message and its location in the program code, the address of the open page with key parameters removed, the site version and the browser type. Names, phone numbers, e-mail addresses, cookies and form contents are not included.

5. Storage and deletion

Data is stored on servers in the Russian Federation for the term of the agreement and for the periods required by law (including accounting and tax records). On the owner’s request, access to the account stops immediately, and the owner’s profile, settings, contacts, guests’ private reviews and uploaded files are deleted no later than 30 calendar days. Payment records the controller must keep for accounting and tax purposes are retained for 5 years, in the minimum scope and without payment credentials. Auto-renewal data (the service token, the card’s last 4 digits and expiry, or the bank’s name and its SBP member id) is kept while auto-renewal is in force, and is deleted no later than one business day after the owner has refused the use of those credentials, the bank has stopped accepting them, or the subscription for the location has ended and auto-renewal is off. The date and time of consent to auto-renewal, the IP address and the offer edition are kept for 3 years from the last charge made under that consent — to handle possible complaints and payment disputes. Backups are kept no longer than 35 days; when data is restored from a backup, the deletion is applied again.

6. Your rights

You may request access to your data, its correction, blocking or deletion, and withdraw consent to processing. To do so, email support@get5stars.ru.

7. Information security

The controller applies organisational and technical safeguards: role-based access control, storing passwords and PINs only as irreversible hashes (Argon2), access over secure channels, regular backups and software updates. Only authorised staff can access personal data, and only as needed for the work.

8. Secure transmission of payer data

All data exchange between the user’s device and the service is encrypted via HTTPS/TLS. Card details are entered on the acquiring bank’s secure payment page and processed on its side under the PCI DSS security standard. Where paying via SBP is available in the account area, the account binding is confirmed in the bank’s app, and the account’s details are processed by the payer’s bank and JSC «NSPK» under the SBP rules. get5stars does not receive, see or store the full card number, the CVV, or the full bank account number. The service data get5stars does receive from the bank and store for auto-renewal is listed in section 2.

9. Statistics, advertising and traffic attribution

The site uses web analytics and advertising services — for visit statistics and to measure how well advertising performs. These scripts are not loaded into the browser until the visitor consents in the cookie banner to «Analytics» and/or «Marketing». Consent can be withdrawn at any time — the «Cookie settings» control is in the site footer and on the account settings screen — and withdrawal turns those scripts off.

The owner account area and the staff console also use session recording provided by the enabled web analytics service — to understand where the interface is hard to use. Session recording is not run on the public «Prize for a review» page or on this marketing site; payment screens in the account area are excluded from it.

The necessary g5s_referral cookie may be retained for up to 60 days to operate a partner link. The first valid visit takes priority and later visits do not renew the period. Approximate partner statistics count only browsers that consented to analytics and made a qualifying visit during the last 30 days; one browser is counted by a pseudonymous browser identifier and its digest, without a name or contact details. The estimate can be incomplete because of browser settings, multiple devices or withdrawn consent.

When an account owner consents to analytics, actions related to the partner programme may be sent to enabled browser analytics and marketing systems according to the selected cookie categories. Successful invitation application, the first qualifying payment, bonus earning, use and reversal may be sent by the server to the enabled analytics services with a pseudonymous account identifier and without a name, contact details, personal code or link. Trial access and bonuses do not depend on analytics consent. Withdrawing consent deletes optional queued deliveries and delivery receipts and stops future queued attempts; a delivery already in progress may still complete, and data transmitted to a provider cannot be recalled.

When a visitor arrives via an advertising or referral link, we store that campaign's labels (utm_source, utm_medium, utm_campaign, utm_content), the address of the referring page — shortened to its host and path, with its query string and fragment discarded before storage — the path of the first page of our own site the visitor landed on (without its query string), and the moment of the first visit. We add no name, phone number, email address or other contact detail to that record; the parameters of the referring address are discarded, and the record itself is used only to understand which channel a registration came from — not to identify the visitor. This record falls under the "Necessary" category and is not gated by the cookie banner: without it we could never learn the traffic source for visitors who decline analytics. If the visitor has granted the "Analytics" category, a copy of the fields listed above is passed to the enabled product analytics service — and to it alone — so that the acquisition source is visible alongside the statistics; query strings are never passed there. Without that consent the record stays with us alone. Alongside it, a pseudonymous browser identifier (a random UUID, stored for up to 400 days) is kept in the g5s_vid cookie: it lets us connect a first visit to a later registration and payment, carries no name, contact detail or other information about the visitor, and falls under the same "Necessary" category.