Privacy Policy

Effective date: July 21, 2026 · Last updated: July 21, 2026

ElementsBoost (“ElementsBoost”, “we”, “us”, or “our”) operates elementsboost.com and distributes the ElementsBoost WordPress plugin. This policy explains how information is handled when you browse our website, contact us, purchase or manage a product, or enable an optional connected feature in the plugin.

1. Information we collect

Information you provide

• Contact and support: your name, email address, message, attachments, site details, and any diagnostic information you choose to share.
• Orders and licenses: contact and billing details, the product purchased, order history, license status, and related support records. Payment details are processed by the payment provider displayed at checkout; we do not intentionally store complete card numbers.
• Accounts and comments: if these features are available and you use them, WordPress may store the information you submit, associated metadata, and account preferences.

Website and device information

Our hosting, security, caching, and analytics tools may process IP address, browser and device type, operating system, referring page, pages viewed, approximate location derived from IP address, timestamps, cookie or similar identifiers, and error or security-event data. We use this information to deliver the site, prevent abuse, understand aggregate usage, and diagnose reliability problems.

2. Cookies and analytics on elementsboost.com

WordPress, our checkout system, security tools, and caching infrastructure may use cookies or local storage that are necessary for sign-in, checkout, fraud prevention, preferences, and basic site operation. If analytics is enabled, Google services configured through Site Kit and Automattic/Jetpack may also process usage information. Your browser settings and any consent controls presented on the site can limit non-essential cookies, although blocking essential storage may affect checkout or account features.

Learn more in the Google Privacy Policy and Automattic Privacy Policy.

3. Data handled by the ElementsBoost plugin

The plugin’s ordinary settings, scans, page evidence, asset map, history snapshots, and supported undo records are stored on the WordPress installation where the plugin runs. ElementsBoost does not need a central copy of page content to provide those local features.

Optional Diagnostics

Diagnostics is disabled by default and can be enabled or disabled by a WordPress administrator. When enabled, the plugin sends one report when the setting is turned on and then sends a limited technical report approximately weekly. The report can include WordPress, Elementor, PHP and plugin versions; theme name; locale and multisite status; counts for active plugins, Elementor content, disabled widgets, scans, issues, images, conflicts and dequeue rules; installation age; the on/off state of documented ElementsBoost controls; delivery status; and a persistent random installation UUID generated locally.

The Diagnostics payload is designed not to include the site URL, individual page URLs, page content, plugin names, WordPress usernames, or email addresses. Turning Diagnostics off stops future scheduled reports. Uninstalling the plugin removes its locally generated installation UUID.

Other optional connections

• Compatibility Intelligence: when compatibility alerts are enabled, the plugin downloads a curated feed from ElementsBoost. The feed request has no site or user data in its query string or request body.
• Aggregated benchmarks: the dashboard can retrieve benchmark data from ElementsBoost without sending site or user data in the request.
• Self-host Google Fonts: when an administrator enables this feature, the plugin requests font CSS and files from Google and stores eligible files on the WordPress site. Google receives the server request used for that download.
• Google PageSpeed Insights: Free includes administrator-initiated, on-demand tests. Pro can add benchmark history, comparisons, scheduling, and API-key support. When an administrator runs a test, the selected public page URL is sent to Google PageSpeed Insights and the returned result is stored on the WordPress site.
• Optional local real-user monitoring (RUM): if an administrator enables RUM, ElementsBoost samples 25% of eligible public page views and sends the page’s post ID, browser-observed LCP, CLS, INP, and viewport width to that site’s own WordPress REST endpoint. Samples are stored locally as post metadata for a rolling maximum of 60 samples per post and up to 28 days. No IP address is stored; a salted hash is used transiently for rate limiting. RUM does not send these samples to ElementsBoost or an external monitoring provider, and disabling RUM stops collection.
• License activation and updates: activating or checking a commercial license requires communication with the licensing service so the key, status, site activation, and eligible updates can be validated.

4. How we use information

• Deliver the website, downloads, purchases, licenses, updates, and support.
• Authenticate accounts, process transactions, prevent fraud, and maintain security.
• Respond to questions and diagnose product or compatibility problems.
• Measure aggregate website and optional product usage so we can improve documentation, reliability, and feature priorities.
• Maintain business, tax, accounting, and legal records and enforce our terms.

5. When information is shared

We share information only as reasonably necessary with service providers that help us host, secure, cache, analyze, email, support, license, and process payments for the service; when you direct us to connect a feature; to investigate abuse or protect rights and safety; to comply with law or a valid legal request; or as part of a business reorganization where appropriate safeguards apply. Providers process information under their own terms and privacy notices. We do not sell personal information.

6. Retention

We retain information only for as long as it is reasonably needed for the purposes described above. Order, license, and accounting records may be kept for the period required by tax, fraud-prevention, and legal obligations. Support communications and security logs are retained as needed to resolve issues and protect the service. Optional diagnostic records may be retained in identifiable or aggregated form for product reliability and trend analysis. Backup copies may persist for a limited period after deletion from active systems.

7. Your choices and rights

• Disable optional plugin Diagnostics at any time in ElementsBoost settings.
• Choose whether to run features that contact Google or the ElementsBoost licensing and intelligence services.
• Manage cookies through your browser and any consent controls available on the site.
• Request access, correction, export, or deletion of personal information we control, subject to identity verification and legal retention requirements.
• Object to or restrict certain processing where applicable under local law.

8. Security, international processing, and children

We use reasonable technical and organizational safeguards, but no internet service can guarantee absolute security. Our service providers may process information in countries other than your own; where required, transfers are handled under applicable contractual or legal safeguards. ElementsBoost is intended for website owners and professionals and is not directed to children under 13. If you believe a child has provided personal information, please contact us.

9. External links and embedded content

Our site and articles may link to or embed content from WordPress.org, Google, video platforms, documentation sites, and other third parties. Their services may collect information independently under their own privacy policies. A link does not make us responsible for a third party’s privacy practices.

10. Contact us

For a privacy request or question, use the ElementsBoost contact page. Please do not send passwords, full payment-card details, or other unnecessary sensitive information.

11. Changes to this policy

We may update this policy when our services, connected features, or legal requirements change. We will post the revised version here and update the date at the top. Material changes may also be communicated through the website or product interface when appropriate.