AI EDITORIAL DESK for WP
Diagnostics Service — Privacy & Terms
About this service
Last updated: August 22, 2026
This page explains the privacy practices and terms of use that apply specifically to the diagnostics service provided for AI Editorial Desk for WP.
The service is operated by KAWASAKI, the developer of AI Editorial Desk for WP.
Support contact: developer@aieditorialdesk.com
The diagnostics service endpoint is:
https://diagnostics.aieditorialdesk.com/api/v1/diagnostics
1. When the diagnostics service is used
AI Editorial Desk for WP does not automatically send general product-usage telemetry to this diagnostics service.
A support diagnostics report is sent only when a WordPress administrator explicitly chooses to send it.
Consent to send a diagnostics report is separate from any consent that may apply to other optional product-usage or analytics features.
2. Registration data
Before the first diagnostics report is sent, the plugin may register the WordPress installation with the diagnostics service.
The registration request may include:
- a randomly generated installation identifier;
- the installed AI Editorial Desk version; and
- a value confirming the explicit diagnostics-send action.
Authentication after registration
The service returns a client secret that is used to authenticate later diagnostics requests.
The client secret is stored by the WordPress installation. Later diagnostics requests use signed authentication rather than sending that secret as plaintext.
3. Information included in a diagnostics report
A diagnostics report uses an allowlisted technical snapshot and may include:
- AI Editorial Desk version and build state;
- WordPress version;
- PHP version;
- plugin database-schema version;
- Free or Premium entitlement state without license keys;
- selected run-attention counts and internal run identifiers;
- AI-provider connection state without provider credentials;
- Google connection and configuration state without OAuth tokens or private keys;
- editor and provider state;
- budget-policy state without API credentials;
- pricing-catalog verification metadata;
- cover-font status or fingerprint;
- WordPress AI Client, Abilities API, and MCP compatibility information;
- UI and content-language state;
- the latest product-state error code; and
- safety-boundary state.
Additional information selected by the administrator
The administrator may also explicitly choose to include:
The plugin does not automatically capture screenshots.
- a short symptom note; and
- up to three selected PNG, JPEG, or WebP screenshots, subject to the plugin’s size limits.
4. Information excluded from the structured diagnostics snapshot
The structured diagnostics snapshot is designed not to include:
- article bodies;
- OpenAI API keys;
- Google OAuth tokens;
- Google private keys;
- email addresses;
- WordPress passwords;
- wp-config.php; or
- raw WordPress option values.
Review notes and screenshots before sending
A symptom note or screenshot is information selected or entered by the administrator and may contain information that is not part of the structured snapshot.
Screenshot contents are not automatically redacted.
Administrators should review screenshots before sending them and should not submit passwords, API keys, OAuth tokens, private keys, or personal information that is not necessary for the support request.
5. Authentication, abuse prevention, and network data
Diagnostics requests use an installation identifier together with request timing, a nonce, and a cryptographic request signature.
The service uses replay protection and rate limiting and returns a receipt identifier for accepted reports.
The diagnostics receiver application is designed not to persist raw IP addresses in its own diagnostics store or audit log.
For abuse prevention, the receiver uses a keyed value derived from the IP address rather than storing the raw IP address in those records.
The hosting and network infrastructure used to provide the service may independently process connection metadata as necessary for hosting, security, network operation, and abuse prevention.
6. How diagnostics information is used
Diagnostics information is used to:
Choosing to send a diagnostics report is not treated as consent for unrelated advertising or automatic general product-usage tracking.
- receive and identify support reports;
- investigate reported technical problems;
- check report status using receipt identifiers;
- protect the diagnostics endpoint from replay and abuse; and
- maintain the security and reliability of the diagnostics service.
7. Storage and retention
Diagnostics report payloads are stored outside the public web root in private storage.
The current diagnostics receiver design encrypts stored report payloads using AES-256-GCM.
Diagnostics reports use a default retention period of 90 days, after which expired report data is subject to cleanup.
Security, replay-prevention, and rate-limit records may use different operational retention periods where necessary to protect the service.
8. Hosting provider
The diagnostics service currently uses hosting infrastructure provided by XServer Inc. (エックスサーバー株式会社), Japan.
XServer provides infrastructure used to operate the diagnostics endpoint and may process information necessary to provide and secure its hosting services.
XServer’s own handling of personal information is governed by its current Privacy Policy and Terms of Service.
9. Your choices
Sending a diagnostics report is optional.
If you do not want to send diagnostics information to the service, do not use the diagnostics send action.
AI Editorial Desk for WP also provides technical information that can be copied and shared manually instead of using the diagnostics endpoint.
10. Questions and deletion requests
For questions about the diagnostics service, or to request deletion of a submitted diagnostics report where applicable, contact:
KAWASAKI developer@aieditorialdesk.com
If you have the diagnostics receipt identifier associated with the report, include it with your request where possible.
Do not send passwords, API keys, OAuth tokens, private keys, or other authentication secrets by email.
11. Acceptable use
You must not use the diagnostics service to:
Access to the diagnostics service may be limited or blocked when reasonably necessary to protect the service, its users, or its infrastructure.
- submit unlawful material;
- intentionally submit credentials or authentication secrets;
- submit malware or other harmful content;
- probe, attack, interfere with, or disrupt the service;
- attempt to bypass authentication, replay-protection, or rate-limit controls; or
- send automated traffic unrelated to a genuine AI Editorial Desk support report.
12. Service availability
The diagnostics service is provided as a support facility for AI Editorial Desk for WP.
Continuous, uninterrupted, or error-free availability is not guaranteed.
The service may be changed, temporarily suspended, restricted, or discontinued when reasonably required for maintenance, security, legal compliance, infrastructure changes, or changes to AI Editorial Desk for WP.
13. Changes to these Privacy & Terms
These Privacy & Terms may be updated when the diagnostics service, its infrastructure, its data handling, or applicable requirements change.
The current version will be published on this page.
14. Contact
Questions regarding these Privacy & Terms or the AI Editorial Desk diagnostics service may be sent to:
developer@aieditorialdesk.com