Platform orientation
Understand how local plugins, cloud accounts, product entitlements, support, and policy boundaries fit together.
- Plugin is the local agent
- Cloud is durable authority
- Product scope stays explicit
Documentation
Guides, policies, and operational references
Use one public resource center for platform orientation, security workflow guidance, support routing, and policy references without mixing customer and admin scopes.
Core Guides
Start fast and operate consistently
The docs page is intentionally curated for website visitors. It links to clear public guides rather than exposing internal admin concepts.
Security workflow
Use a practical operating model for prevention, monitoring, cleanup, recovery, and team handoff.
- Prepare before incidents
- Validate risk quickly
- Recover with accountable steps
Support and policy references
Find the right route for support, privacy, legal, security disclosure, SLA, DPA, and acceptable use.
- Support routing
- Privacy requests
- Security disclosure
Compliance Notes
WordPress.org-aligned product guidance
These documents keep product, support, and policy messaging aligned with plugin distribution and customer privacy expectations.
- Plugin pages should disclose local capability separately from optional cloud workflows.
- Cloud login/register flows are hosted by cloud-auth surfaces, not WordPress plugin password forms.
- Customer pages should present customer-owned data; admin-only operations belong in cloud-admin.
- Policy pages must stay visible for privacy, security, legal, cookie, DPA, SLA, and acceptable-use questions.
Trust References