We ask every OrionX user once whether they are happy to share anonymous usage data. Nothing is sent until you say yes — and you can turn it off any time from Appearance → OrionX, no questions asked.
Understanding how people actually use OrionX helps us make smarter decisions: which features to improve, which PHP versions to support, which plugins to integrate with, and where to focus bug fixes. Your trust matters more than any data, which is why collection is strictly opt-in and limited to technical environment details only.
When you opt in, a small JSON payload is sent to our servers once a week. Here is every field in that payload:
| Field | What it contains | Why we need it |
|---|---|---|
| site_id | One-way SHA-256 hash of your home URL | Deduplicate reports — the original URL cannot be recovered |
| theme_version | OrionX version number (e.g. 1.3.3) | Track adoption of new releases |
| wp_version | WordPress version | Know which WP versions to test and support |
| php_version | PHP version (e.g. 8.2.10) | Decide minimum PHP requirements |
| mysql_version | MySQL / MariaDB version | Ensure database queries stay compatible |
| server_software | Web server string (e.g. Apache/2.4, nginx/1.24) | Identify server-specific issues |
| php_memory_limit php_max_execution_time php_max_input_vars php_upload_max_filesize php_post_max_size |
PHP configuration values | Set sensible default recommendations in documentation |
| wp_memory_limit wp_max_memory_limit wp_max_upload_size |
WordPress memory and upload limits | Identify sites with constrained environments |
| wp_language | Site locale (e.g. en_US, de_DE) | Prioritise translation efforts |
| wp_debug | Whether WP_DEBUG is on (true/false) | Understand developer vs. production split |
| wp_multisite | Whether the site is a multisite (true/false) | Ensure multisite compatibility |
| wp_permalink_structure | "custom" or "plain" — nothing more | Verify URL-dependent features work in both modes |
| active_plugins | List of active plugin folder names (e.g. "elementor", "woocommerce") | Know which integrations matter most |
| active_plugin_count | Total number of active plugins | Understand typical site complexity |
| has_elementor has_woocommerce has_orionx_core |
true / false flags for key companion tools | Prioritise compatibility work |
| customizer | Which OrionX Customizer options are turned on (true/false only — no colour values, no text) | Understand which features are actually used so we can improve or deprecate them |
| timestamp | UTC date and time of the report | Detect trends over time |
Opt out any time — no forms, no waiting, no questions asked:
That's it. The weekly background job is cancelled immediately and no further data is sent. Your previous reports are retained in aggregate (we cannot delete individual submissions because they are stored without any identifying information — we have no way to know which rows came from your site).
Telemetry data is received by a server at troeon.com, stored in an aggregated database, and used exclusively for product analytics. Data is not sold, rented, or shared with any third party. Aggregate statistics (e.g. "60 % of users run PHP 8.2") may be referenced in blog posts or changelogs.
Last updated: June 2026 · Questions? info@troeon.com