Personal Data in Russian Franchise Networks: Who Qualifies as Data Operator Under 152-FZ
In Russian franchise networks, customer personal data is routinely processed through a single information system: collection occurs at the franchisee outlet, storage takes place on the franchisor’s servers, and further use supports a common loyalty program and brand-wide communications.
The distribution of legal roles between the parties is rarely formalized in contracts, yet the issue becomes critical when a data subject submits a request, a regulator intervenes, or a security incident occurs.
Legal Definition of Operator
Under paragraph 2 of Article 3 of Federal Law No. 152-FZ “On Personal Data”, an operator is any person that organizes and/or carries out processing and determines the purposes, the scope of data, and the operations performed. The decisive criterion is the determination of processing purposes; this distinguishes an operator from a processor acting on another party’s instructions. Multiple operators may exist for the same dataset, and the law does not prescribe how responsibility is shared.
Processing on Behalf of an Operator
Article 6(3)–(5) of 152-FZ permits an operator to instruct another party to process data, provided the data subject has consented and a written agreement exists. The processor does not need separate consent from the subject; the instructing operator remains liable to the subject, while the processor is liable only to the operator.
Default Model: Franchisee as Operator
When a franchisee concludes a contract with a customer, receives payment, and fulfills obligations, the legal basis is Article 6(1)(5) — processing necessary for performance of a contract. The franchisee therefore determines the purpose and qualifies as operator. The franchisor supplying the IT system acts solely on the franchisee’s instructions and is a processor.
When the Franchisor Becomes an Operator
The franchisor acquires independent operator status once it pursues its own processing purposes. Typical triggers include:
- Operating a loyalty program where the franchisor is the obligated party and issues points redeemable across the network.
- Conducting advertising campaigns in its own name, requiring prior consent under the Advertising Law No. 38-FZ.
- Collecting data through a central website, mobile app, or call center when the specific franchisee is not yet identified at the moment of collection.
In the last scenario, the franchisor processes data for its own purpose of routing leads and must therefore be treated as operator at the collection stage; subsequent transfer to the chosen franchisee constitutes a transfer between two operators.
Documenting Processing Instructions
Instructions must be included in the commercial concession agreement or an annex and must explicitly list the categories of data, permitted actions, purposes, confidentiality and security obligations, data-localization requirements, and breach-notification deadlines that allow the operator to meet the 24-hour Roskomnadzor reporting window.
Liability and Practical Recommendations
Transferring data without a valid instruction constitutes processing without a legal basis and may result in fines of 150,000–300,000 RUB, rising to 300,000–500,000 RUB for repeat violations under Article 13.11 of the Code of Administrative Offenses. The operator remains liable to data subjects and should therefore secure contractual recourse against the processor.
Experts recommend mapping every processing purpose within the network, identifying the operator for each purpose, and formalizing instructions between franchisor and franchisees before operations begin.
Related articles
Dynamic Sites on Yandex Cloud Storage Enable Communication Under White-List Restrictions
A developer facing mobile internet white lists explored ways to exchange encrypted messages without relying on blocked infrastructure. Initial attempts with a national messenger bot failed due to poor API documentation and account hijacking. The team then modeled the problem as three neighboring plots where Alice and Bob route messages through Eve while a slow postman handles delivery. Yandex Disk was tested as a message store accessible via direct GET and POST requests, though it required accounts and suffered from 15-25 second latency. The final approach used Yandex Cloud object storage, whose domains remained whitelisted, allowing HTML files to load and function even when only government services and select platforms were reachable.
Rawline Aggregates VK, MAX, DNS and Other Tunnels into One Multi-Platform VPN Client
Rawline is a new multi-platform client that combines various VPN protocols and non-standard transports into a single application for Android, Windows, Linux and macOS. The project is built on Throne using sing-box and Xray network cores and supports both conventional protocols and unusual transports such as VK and MAX calls, WebRTC, DNS and S3. Users can import profiles via links or QR codes, test latency, chain connections and apply per-app or per-domain routing rules. The developer paid special attention to security issues, removing unnecessary local proxy endpoints, protecting internal connections with random passwords and adding traffic ownership verification that is enabled by default on Android 10 and newer. Additional fixes were implemented after discovering that some transport bridges could be hijacked by external applications sending the first UDP packet. Source code and builds are available on GitHub.
Russia Freezes Entire Hosting Networks to Block VPN Traffic, Investigation Finds
An independent test of 435 endpoints across 154 hosting providers revealed that Russian internet providers are throttling connections to entire autonomous systems rather than individual IP addresses. Networks belonging to Hetzner, OVH, DigitalOcean, M247 and HostPapa are frozen after roughly 25 TCP packets, causing downloads to stall at around 16 KB while UDP-based WireGuard tunnels remain unaffected. The blocking is applied uniformly by multiple Russian operators including Beeline, MTS and home broadband providers, indicating a centrally distributed rule from Roskomnadzor via the TSPU filtering system. Smaller providers that rent IP space from the affected autonomous systems are also impacted, regardless of their own brand or location. Cloudflare-hosted resources currently pass the test, but the list of blocked networks has remained stable since mid-2025. The researcher published an open-source script that allows anyone to reproduce the measurements in under a minute.
macOS Builds Undocumented Personal Knowledge Graph Since Version 13, Inferring Family Ties via On-Device ML
Since macOS 13 in 2022, two daemons named knowledgeconstructiond and intelligenceplatformd have been constructing a comprehensive personal knowledge graph on every Mac. The system aggregates data from Contacts, Calendar, Photos, Messages, Mail, Family Sharing, Health emergency contacts, Screen Time, and behavioral signals to map users, their relationships, locations, and activities. Results are stored in ~/Library/IntelligencePlatform as SQLite databases, including graph.db containing 181 entity classes and 278 predicates. Two CoreML models, EntityTagging_Family.mlmodelc and EntityTagging_FamilyAndFriends.mlmodelc, use 144 behavioral and photographic features to classify family and friend relationships with daily updates in entityTagging.db. An embedded LLM and embedding models further label unnamed faces and infer relationships from message text when Apple Intelligence is enabled. The graph remains queryable locally and is designed to feed personalized AI features while operating entirely on-device under Full Disk Access protections.