PDN152 COMPLIANCE
PDN152 Compliance compatibility with REEID Translate
PDN152 Compliance compatibility with REEID Translate is being evaluated from available plugin evidence. Cookie banner with cookie categories and storage of user choices No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for PDN152 Compliance.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
PDN152 Compliance is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How PDN152 Compliance compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Cookie banner with cookie categories and storage of user choices
- Consent and compliance document generation/publishing on the site (e.g., personal data policy, cookie policy, consent text, mailing consent, public offer)
- Admin consent logging including date, IP address, and source, with configurable retention
- Optional consent-related workflow for account deletion / personal-data destruction (disabled until enabled in settings)
- Integrations with WordPress registration, WooCommerce, Elementor, Contact Form 7, and WPForms (configured via the plugin settings)
- Policy wizard and Roskomnadzor-oriented export helpers plus site readiness checks
- Optional external network checks during compliance scans (opt-in required) including GeoIP via ip-api.com and operator registry lookup via pd.rkn.gov.ru; whois.com is only used as a manual link (no automatic requests)
CONTENT BOUNDARY
PDN152 Compliance capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
PDN152 Compliance and REEID Translate FAQ.
What does PDN152 Compliance do according to the available plugin evidence?
PDN152 Compliance has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for PDN152 Compliance?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for PDN152 Compliance?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate PDN152 Compliance in a multilingual WordPress workflow.
REEID documents PDN152 Compliance functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.