full report<\/strong> in your ScanBase account: developer task list, document templates, remediation services.<\/li>\n<\/ul>\n\nThe plugin works only in the admin area and outputs nothing to your site's visitors.<\/p>\n\n
How it works<\/h4>\n\n
The plugin is a thin client of the ScanBase API. All checks run on the service side; your API key is stored only on your site and is used solely for API requests. Your tier (free, scan package or subscription) is determined by your ScanBase account.<\/p>\n\n
External service (mandatory disclosure)<\/h4>\n\n
The plugin is a client of the ScanBase<\/strong> cloud service (https:\/\/scanbase.ru) and does not work without it. What is sent to scanbase.ru and when:<\/p>\n\n\n- When you start a check<\/strong> (button in wp-admin): your site URL and your API key. The service scans the site and returns the report.<\/li>\n
- During the optional one-click connect flow<\/strong>: your site URL and the admin email (used to sign in to the ScanBase account via a magic link and issue an API key).<\/li>\n
- No data about your site's visitors is collected or transmitted: the plugin runs only in the admin area.<\/li>\n<\/ul>\n\n
ScanBase service documents:<\/p>\n\n
\n- Privacy policy (personal data processing): https:\/\/scanbase.ru\/legal\/<\/li>\n
- API terms of use (tiers, limits): https:\/\/scanbase.ru\/api\/<\/li>\n<\/ul>\n\n
Tiers<\/h4>\n\n\n- Free<\/strong> - 5 checks per day, condensed report.<\/li>\n
- Scan packages<\/strong> - full report for any domain, one-time payment.<\/li>\n
- Subscription<\/strong> - full report plus server-side monitoring.<\/li>\n<\/ul>\n\n
All tiers are managed in the ScanBase account: https:\/\/scanbase.ru\/cabinet\/ The plugin code itself is not restricted - tiers only affect how much detail the API returns.<\/p>\n\n\n
\n- Install and activate the plugin.<\/li>\n
- Open the ScanBase<\/strong> menu in wp-admin.<\/li>\n
- Click \"Connect ScanBase\" (one-click connect), or get a free key in the ScanBase account (Account -> API access -> \"Create free key\") and paste it into the plugin.<\/li>\n
- Click \"Check site\".<\/li>\n<\/ol>\n\n\n
\nDo I need a ScanBase account?<\/h3><\/dt>\nYes. Signing in is done by email (magic link), no password. A free API key is issued self-service.<\/p><\/dd>\n
Does my API key leave my site?<\/h3><\/dt>\nIt is stored in your site's options and is sent only to the scanbase.ru API when a check is requested.<\/p><\/dd>\n
What is checked for free?<\/h3><\/dt>\nThe compliance score, the number of violations and the total potential fine. Some violation details are hidden on the free tier - the full list is available with a scan package or a subscription.<\/p><\/dd>\n
Does the plugin output anything to my site's visitors?<\/h3><\/dt>\nNo. The plugin works only in the admin area: no banners, links or scripts on visitor-facing pages.<\/p><\/dd>\n
What happens when I delete the plugin?<\/h3><\/dt>\nAll settings and stored check results are removed from your site. If needed, revoke the API key in your ScanBase account.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.5.3<\/h4>\n\n\n- Fixed fine amounts display: values from the API are in rubles and were mistakenly divided by 100.<\/li>\n<\/ul>\n\n
1.5.2<\/h4>\n\n\n- Contributors field fixed to the owner's WordPress.org username.<\/li>\n<\/ul>\n\n
1.5.1<\/h4>\n\n\n- readme rewritten in English (directory requirement); Plugin Check fixes.<\/li>\n<\/ul>\n\n
1.5.0<\/h4>\n\n\n- The plugin is focused on its core: site compliance check (free and paid report). The email reminders and cookie banner modules were removed; the cron schedule left by older versions is cleaned up automatically.<\/li>\n
- The plugin no longer outputs anything on visitor-facing pages - admin area only.<\/li>\n<\/ul>\n\n
1.4.1<\/h4>\n\n\n- Security: the last check's data is passed to the script as JSON with HTML-significant characters escaped (strings from the scanned site cannot break out of the script context).<\/li>\n
- The \"Verified by ScanBase\" note enabled before 1.4.0 (when it was on by default) is no longer treated as consent - it is shown only after being explicitly enabled in settings.<\/li>\n
- Admin page scripts and styles are enqueued via standard WordPress mechanisms instead of inline output.<\/li>\n
- The external redirect to scanbase.ru in the connect flow goes through wp_safe_redirect with an explicit allowlist of hosts.<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- Preparation for the wordpress.org directory: the \"Verified by ScanBase\" note in the cookie banner became strictly opt-in (off by default).<\/li>\n
- Full cleanup of settings on plugin deletion (uninstall.php).<\/li>\n
- Explicit description of transmitted data and the external service in the readme.<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Cookie banner for the site: cookie processing notice on all pages, visitor choice remembered, policy link, configurable text and buttons.<\/li>\n<\/ul>\n\n
1.2.1<\/h4>\n\n\n- Reminder frequency: \"monthly\" (recommended) and \"weekly\". Daily re-checks removed as excessive.<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Compliance traffic light in the admin bar (like the Yoast indicator) - visible on every admin page.<\/li>\n
- Full report with \"how to fix\" recommendations right in WordPress; the last check is shown on page load.<\/li>\n
- Email reminders: periodic re-check with an email when compliance degrades.<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- One-click connect (\"Connect ScanBase\"): sign in by email, the key returns to the plugin automatically - no copying from the account.<\/li>\n
- Manual key entry kept as a fallback.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release: site check from wp-admin, compliance score, violations, account status.<\/li>\n<\/ul>","raw_excerpt":"Check your website's compliance with the Russian personal data law (152-FZ) from wp-admin: compliance score, violations and potential fines.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/375331","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=375331"}],"author":[{"embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lego1995"}],"wp:attachment":[{"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=375331"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=375331"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=375331"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=375331"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=375331"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ast.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=375331"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}