Scan a CMS site for common Roskomnadzor and Russian personal-data requirements.
RKN / 152-FZ
CMS Site → RKN / 152-FZ scans the landing page and CMS legal slots against common 152-FZ / Roskomnadzor expectations (privacy policy, consents, cookies/trackers, forms, localization, operator registry).
Output: score, risk level, and findings with where/how/acceptance steps and law references. Advisory only — not legal advice.
What is checked
| Area | Examples |
|---|---|
| CMS documents | Privacy policy, PD consent, terms/offer, marketing consent |
| Policy quality | Operator contacts, subject rights, cookies if analytics present |
| Live site | HTTPS, privacy link, cookie banner vs trackers, form checkboxes |
| Process | Reminders for RKN operator registry (art. 22) and localization (art. 18(5)) |
The Check RKN button on Legal documents analyzes each saved document (purposes, consents, cookies, publish state, etc.) and stores a report; Result opens the full finding list.
API (admin JWT)
Prefix YOUR_API_URL/v1/cms/sites/{siteId}/rkn
POST /scans— run scanGET /scans— historyGET /scans/{scanId}— scan + issuesGET /latest— latest done scan + open issuesPATCH /issues/{issueId}—{ "status": "open" \| "resolved" \| "ignored" }
Per legal document (Legal documents section):
POST /v1/legal/owners/cms_site/{siteId}/{kind}/rkn-checkGET /v1/legal/owners/cms_site/{siteId}/{kind}/rkn-check/latest