AI EDITORIAL DESK for WP
Optional improvement aggregation and data handling
This page explains optional usage aggregation and product-improvement sharing from the WordPress site where AI Editorial Desk is installed. Email enquiry information and manually submitted support diagnostics have separate policies.
Optional local aggregation, off by default
On-site usage aggregation is optional, is off by default and requires administrator consent. It aggregates requests for feature operations and predefined errors in up to eight categories for up to 30 days on a UTC basis. Expired records are deleted the next time the plugin runs. You can use local aggregation alone, prepare or copy reports, and stop or delete the aggregation.
Sharing with COMDECIS requires separate consent
Sharing with COMDECIS is also optional and off by default. It is enabled only after you review the destination, fields, retention period and what happens when sharing stops in the administration screen, then consent using a separate checkbox. Consent to local aggregation, manual copying, support diagnostics or Freemius does not start this sharing. The destination is the COMDECIS product-improvement contact at aieditorialdesk.com. Received aggregates are materials for human review of possible improvements; receipt alone does not automatically run AI, change product code or publish anything.
Information shared and excluded
The shared JSON report is limited to counts in up to eight categories; the product, version and Free or Pro edition; WordPress and PHP major version numbers; the covered UTC period; random identifiers for the purpose and each transmission unit; and prescribed format, aggregation-definition, destination and consent information. It does not include article bodies, URLs, email addresses, IP addresses, user IDs, license information, credentials, cookies or free-text descriptions of operations. The plugin creates random credentials for sharing and keeps them within the site. It does not reuse existing WordPress, support, Freemius or other credentials. This registration is not used to verify the identity of a purchaser.
Sharing intervals and unknown results
New aggregates are normally shared through WordPress scheduled execution at intervals of at least six hours. This depends on site activity, so transmission times are not guaranteed. If the result is unknown, the same report is rechecked a limited number of times only while consent remains valid, after which sharing is paused. This does not rerun article processing or paid generation.
Stopping sharing and confirming deletion
When you stop sharing, new sharing and rechecks of sharing are switched off first, and deletion of aggregates already received is requested. Communications authorized before sharing stopped may still complete. Until deletion is confirmed, the dedicated key is retained only for the deletion request. Data is not displayed as deleted without confirmation from the recipient. Local aggregation can be stopped and deleted separately.
Recipient retention and records that remain
The recipient stores up to 30 days of raw aggregate data on a UTC basis. Expired data is deleted during the next receipt or maintenance process. Maintenance depends on daily WordPress scheduled execution; immediate erasure while the recipient is not operating is not guaranteed. Minimal hashes and similar data needed to prevent reacceptance are retained beyond the storage period within capacity limits. Hashes of the dedicated key and purpose remain without a set expiry even after a deletion request. Connection information such as the source IP address reaches servers and may be recorded in ordinary access logs. Deletion by this feature does not include ordinary server logs or manually exported copies.
Freshness and storage of improvement-review materials
Improvement reviews use aggregated materials created within the previous seven days; older materials are not treated as current results. Materials collected periodically do not include information identifying individuals or sites, article bodies or input contents. Files used for transfer and storage are configured to expire after seven days, separately from retention of usage records at the recipient. Ordinary server logs and storage backups are managed separately; deleting usage records alone does not guarantee physical deletion of all of those copies.