This website

The site serves static pages and a public read-only content API through Cloudflare Workers. Requests are processed by the hosting provider, including network information needed for delivery and abuse prevention. API rate limiting uses the request IP at the edge. This site does not install advertising trackers or third-party analytics scripts.

A manual theme choice is stored in your browser under cybermaps-theme. Fonts and the documentation search index are served from this site. Search queries stay in your browser when using the documentation search field.

Public agent tools

The REST, MCP, and optional browser tools read the same published website content. They do not read private WordPress data or give access to an installed plugin. API queries are sent to the hosting service; do not include secrets or personal information in a query.

The WordPress plugin

Plugin crawler analytics and request logging have their own settings and retention controls. Observations are limited to requests reaching WordPress. Review analytics and privacy controls before enabling them.

Optional integrations, including Cloudflare authorization and publishing services, operate only under their relevant configuration and permissions. Review the plugin’s integration reference for the chosen service. This website does not activate those integrations.

Cloudflare OAuth relay

The optional Connect Cloudflare & optimize action in the WordPress plugin uses https://connect.cybermaps.dev to receive Cloudflare’s OAuth callback. The service is operated by CYBERMAPS on Cloudflare Workers. It receives a random transaction state, PKCE challenge, and short-lived authorization code. Transaction state expires within five minutes; code retrieval is one-time. The PKCE verifier remains on WordPress. The relay does not receive the access token, WordPress identity, site URL, or optimization rules.

Cloudflare processes network metadata needed to serve and protect the relay. The relay uses salted hashes of request IP addresses for rate limiting and records aggregate operational and rate-limit events. It does not store IP addresses in transaction state. Hosting-provider processing is covered by Cloudflare’s privacy policy.

WordPress exchanges the authorization code directly with Cloudflare, performs the optimization authorized by the administrator, and revokes its token. Cloudflare receives the credentials and the zone, hostname, and rule information needed for those operations. Cloudflare’s terms apply to use of its services. Manual tokens and self-managed OAuth do not use the CYBERMAPS relay. Ordinary plugin publication and analytics do not contact it.

The relay is provided for administrator-initiated Cybermaps Cloudflare connections. Requests are subject to short expiry periods and abuse-prevention limits; an unavailable or rate-limited relay does not disable local plugin features. Use the plugin’s manual-token or self-managed authorization options when you need an independently controlled connection.