Customers’ personal data: Federal Law 152-FZ for a brand and a retailer. Grounds and consents, storage, localization, loyalty, mailings, liability
A map of the duties of a brand and a retailer when working with buyers’ personal data: on what basis to collect data, when consent is needed, how and where to store it, what to do with a loyalty program, mailings and contractors, which notifications to file and what follows a violation. The document decides which data the business needs for its purposes and which is better not to collect, and how to check the CRM before the regulator does.
Why this document
Buyer data is needed by everyone: without it there is no CRM, loyalty, mailings or analytics. But every field in the base creates a duty: a basis, a purpose, a retention period, protection, liability. The owner, the lawyer, the head of CRM and the IT director read this document when launching a loyalty program, changing a CRM or a contractor and before an inspection. It puts the duties into one order and shows with an example how an audit of the base turns “all records” into a permitted mailing. Without it the base is piled up for years out of habit, and then it turns out that most records have no basis.
At a glance
- What is this document and why is it needed?
- A map of the duties of a brand and a retailer when working with buyers’ personal data: on what basis to collect data, when consent is needed, how and where to store it, what to do with a loyalty program, mailings and contractors, which notifications to file and what follows a violation. The document decides which data the business needs for its purposes and which is better not to collect, and how to check the CRM before the regulator does.
- Who owns the document and how often is it rebuilt?
- The lawyer and the head of CRM lead, the IT director is responsible for protection and storage, the owner approves the policy; reviewed when a new process starts, when a contractor changes and once a year; norms are checked in the current edition.
- What mistakes are the most common?
- Brand: one general tick “I agree to everything” → the advertising consent is invalid → separate the advertising consent from the consent to service. Retail: the cashier records a phone “for the receipt” and adds it to the mailing → advertising without consent → fix the purpose in the process and in the till settings. Brand: a mailing or analytics contractor without an instruction and a check of the storage place → the operator is liable for the contractor and a localization breach → conclude an instruction and check.
For whom
- Brand
- A brand collects data in the online store, subscriptions, loyalty programs, events and on marketplaces (part of the data belongs to the marketplace and not to the brand). The main things: the basis and the purpose for each channel of collection, a separate consent to advertising, contractors for mailings and analytics, the retention period.
- Retail
- A retailer collects data at the till, in the app, in the loyalty card and on delivery; video surveillance and electronic receipts are added. The main things: what the cashier asks for and records, how the loyalty program works, where the base is stored and which employees have access.
What it consists of
What personal data is and who is the operator
- Personal data: any information relating to an identified or identifiable person (name, phone, address, e-mail, purchase history, device identifiers linked to a person); the operator: the one who determines the purposes and the composition of processing (a brand, a retailer); a contractor processes on the instruction of the operator.
Grounds and consent
- Processing is permitted when there is a basis: consent, performance of a contract (purchase, delivery), a requirement of the law and other cases under the law; advertising and profiling need a separate consent; the consent must be specific, informed and conscious, the form and the composition of the requirements are checked in the current edition of the law.
- Brand: for every collection channel write down the purpose, the basis and the composition of the fields; do not collect what is not needed for the purpose (a date of birth “just in case”); collect advertising consent by a separate action and not by a general tick.
- Retail: at the till do not demand a phone number as a condition of sale; a loyalty program needs consent and clear rules; for an electronic receipt the buyer’s address or phone is needed for sending and cannot be used for advertising without consent.
Policy, notification, storage and localization
- The processing policy is published on the website; the notification to Roskomnadzor on processing is filed as a general rule before processing begins (check the exceptions); the databases of Russian citizens are collected, recorded and stored using databases on the territory of Russia; data is stored no longer than the purpose requires, then deleted or anonymized.
- Retail: determine the retention period for each type (receipts and accounting by accounting rules; marketing data by purpose and activity) and set up automatic deletion; do not leave databases in personal spreadsheets and messengers.
Contractors and cross-border transfer
- Brand: mailing services, CRM, call centers, analytics and delivery process data on instruction: a contract or an instruction with a list of actions and protection measures is needed; the operator is liable to the person for the contractor.
- Cross-border transfer (a cloud service, a foreign contractor) requires as a general rule a notification to the regulator before the transfer and an assessment of protection at the recipient; for Russian citizens the primary recording and storage remain in Russia: check the current requirements.
Mailings, loyalty, access, leaks and liability
- Advertising mailings over telecommunication networks (SMS, e-mail, messengers) are permitted only with the addressee’s prior consent (the Advertising Law, Art. 18); unsubscribing must work; advertising on the internet carries a marking, which is another regime.
- Retail: a loyalty program has public rules and its own processing basis; employee access is given by roles, actions in the base are logged; the operator notifies the regulator of leaks in short terms (a guide: a first notification within a day), check the requirements.
- Liability: administrative fines under the Code of Administrative Offenses (Article 13.11 and related), for repeated leaks the amounts with turnover have grown; in serious cases criminal liability: the amounts are not named in Lab, check in the current edition.
Where the data comes from
| Data source | Fields |
|---|---|
| Collection channels and forms | website, app, till, loyalty, events, marketplaces; fields, purpose, basis |
| CRM and contractors | where the base is stored, who processes it, contracts and instructions, places of storage, access |
| Consents and logs | the date and form of consent, the text version, unsubscribes, the access log, incidents |
How to build it step by step
- Step 1: Brand: draw up a register of processing processes: channel, purpose, fields, basis, retention period, place of storage, contractor.
- Step 2: Remove the fields not needed for the purpose and separate the consent to service from the consent to advertising.
- Step 3: Retail: check the process at the till and in the app: what the employee asks for and records, how consent and loyalty are formalized.
- Step 4: Publish the processing policy and check the notification to the regulator on processing.
- Step 5: Brand: conclude contracts or instructions with contractors and check where the databases are physically stored; for a foreign cloud assess the transfer requirements.
- Step 6: Audit the base by basis and term (see the example): mark what can be mailed, what only service messages, what to block, what to delete.
- Step 7: Retail: set up access roles and the log, the rules for working with exports and the procedure for responding to a leak.
- Step 8: Appoint a responsible person, carry out the check once a year and when a new process starts; keep the evidence of consents.
Formulas
| Measure | Formulas | Note |
|---|---|---|
| Permitted mailing | Mailing = Records × share with advertising consent and active | The other records receive only service messages or are blocked. |
| Volume of deletion | Delete = Records × share with an expired retention period and without a basis | The terms by type of data are set by the operator in the policy, check the accounting rules and the purposes. |
Formulas in notation
- Permitted base
M = N·s_a, Σ s_i = 1
N: records in the base; s_a: the share of the segment with advertising consent and active; Σ s_i = 1: every record falls into one segment.
Worked example
A conditional audit of a base of 120,000 records and 4 advertising messages a month per recipient
| Segment | Records | Share, % | What to do | Advertising messages a month |
|---|---|---|---|---|
| Advertising consent given, client active | 38,400 | 32 | mailing allowed; keep the proof of consent and its date | 153,600 |
| Only the “performance of a contract” basis (purchase, delivery) | 30,000 | 25 | service messages only; advertising after a separate consent | 0 |
| No confirmed basis (import from old systems) | 21,600 | 18 | block for mailings; request consent or delete | 0 |
| Purpose achieved, retention period expired | 30,000 | 25 | delete or anonymize; do not keep “just in case” | 0 |
The shares are conditional. The general conclusion: mailing is possible only for the segment with consent, the rest must either be requested again or deleted; the size of the “permitted” base is usually noticeably smaller than the “whole” one and more accurate.
Figures
The path of a client’s personal data in a brand or a retailer. Every step has a duty: a basis, consent, protection, an instruction to a contractor, a retention period and deletion.
- Collection: website, till, loyalty → Basis and consent
- Basis and consent → CRM and storage in Russia
- CRM and storage in Russia → Contractors by instruction
- Contractors by instruction → Mailings and loyalty
- Mailings and loyalty → Retention period and deletion
- Retention period and deletion
Data as a table
| Measure | Records |
|---|---|
| Advertising consent | 38.4k |
| Contract only | 30k |
| No basis | 21.6k |
| Term expired | 30k |
Segments of the base by basis and term (a conditional audit). Mailing is possible only for the segment with consent; the other records need a decision: request again, restrict, delete.
Specifics by category
- Apparel
- Apparel: data is needed for sizes, delivery and returns; body measurements and the client’s sizes remain ordinary personal data, but do not collect more than needed and store size preferences only with consent.
- Footwear
- Footwear: foot size and size returns; foot measurements on a 3D scanner or in an app, if they allow identifying a person, need a separate assessment and consent: check with a lawyer.
- Accessories
- Accessories: often gifts; the recipient’s data (address, phone) belongs to another person, so collect the minimum and explain to the buyer that he is entering someone else’s data.
- Kids
- Kids: data about a child (age, sizes) is entered by a parent; special rules apply to the data of minors, consent is given by a legal representative and advertising may not be sent directly to a child: check with a lawyer.
- Men
- No difference in rules; collection channels differ: the male audience more often buys through an app and a subscription, so collect consents to notifications and to advertising separately.
- Women
- No difference in rules; there are more loyalty programs, mailings and personal recommendations, so profiling and the consent to it need more attention and unsubscribing must be simple.
Common mistakes
- Brand: one general tick “I agree to everything” → the advertising consent is invalid → separate the advertising consent from the consent to service.
- Retail: the cashier records a phone “for the receipt” and adds it to the mailing → advertising without consent → fix the purpose in the process and in the till settings.
- Brand: a mailing or analytics contractor without an instruction and a check of the storage place → the operator is liable for the contractor and a localization breach → conclude an instruction and check.
- Retail: the base is kept in spreadsheets by employees and in messengers → a leak without a log → keep it in a system with roles and a log.
- Data is not deleted after the purpose is achieved → the risk and the volume of liability grow → set a retention period and automatic deletion.
Russian specifics
- Federal Law of 27.07.2006 No. 152-FZ on personal data: grounds, consent, policy, notification, localization, cross-border transfer, leaks; check the edition on the date of application. Rule: Law 152-FZ of 27.07.2006: Federal Law of 27.07.2006 No. 152-FZ on personal data.
- Brand: advertising over telecommunication networks only with the addressee’s prior consent: the Advertising Law, 38-FZ, Art. 18; identification of internet advertising: Roskomnadzor Order No. 68 of 25.03.2025. Rule: Law 38-FZ of 13.03.2006: Federal Law of 13.03.2006 No. 38-FZ on advertising.
- Retail: the form and composition of consent, the terms of notifications, the list of exceptions, the rules for processing biometrics and video surveillance, fines under the Code of Administrative Offenses have changed and keep changing: given in Lab as a guide, unverified, check with a lawyer in the current edition.
- Brand: Kazakhstan and Belarus have their own personal data laws; Russian rules do not carry over automatically: check with a local lawyer if you collect the data of buyers in these countries.