Crawrix integrations — privacy

Last updated: 12 October 2026

This page describes what the Crawrix site integrations send to the crawrix service, when they send it, what each one stores, and how to stop it. It covers the WordPress plugin, the Wix app, the Webflow app, and the Shopify app. It supplements the service’s general terms; if you never install one of them, none of this applies to you.

crawrix is owned and operated by Trontra LLC. “We” and “us” on this page mean Trontra LLC, which is responsible for the data described here.

Nothing is sent before you connect

Installing an integration sends nothing to us on its own. There is no telemetry, no tracking, and no phone-home before someone with administrative access explicitly connects the site: clicking Connect in wp-admin and approving on this site for WordPress, or completing the app install and its permission grant for Wix, Webflow, and Shopify. The WordPress plugin’s local features (the AI-crawler allow/block panel) work entirely on your server and never contact us.

What every integration sends after you connect

Once a site is connected, the integration communicates with the crawrix service over HTTPS. The data sent is:

  • Site metadata — the site URL and the platform’s own identifiers and version information. For WordPress that is the WordPress, PHP, and plugin versions, the permalink structure, and the detected SEO, cache, and page-builder plugins, re-sent by a daily WP-Cron heartbeat (which fires on site traffic and may be delayed or disabled by your host) so we can flag a stale connection. For the hosted apps it is the site or shop identifier, the published domains, and which write capabilities the platform grants your plan.
  • Audit content — the page content our audits read in order to score SEO and AI visibility and to list issues, and the specific values (titles, meta descriptions, schema, robots.txt, redirects, CMS fields, image alt text) involved in a fix you preview, approve, apply, or revert.
  • Chat messages — messages you type into the Crawrix chat, wherever it runs: wp-admin, the Wix dashboard, the Webflow Designer panel, the Shopify admin, or our own web app. The crawrix service runs the agent.

We never collect visitor analytics, visitor IP addresses, comments, or end-user accounts through any integration. The Shopify app holds no customer-data scopes, so it cannot read customers, orders, or payments, and the WordPress plugin does not read WooCommerce orders.

What we store, per integration

Every credential we hold is encrypted at rest with AES-256-GCM before it is written to our database, and no credential is ever sent to a browser. What differs is which credential each platform issues.

WordPress plugin

On our side: the site URL, an encrypted site token with its REST root, and a SHA-256 hash of the plugin token (never the token itself). On your site, in your WordPress database: an encrypted plugin token, the hash of the site token, and the WordPress user ID of the administrator who connected. Dashboard preferences such as the theme choice stay in that administrator’s browser localStorage and are not sent to us. We receive no webhooks from WordPress; the daily heartbeat is an outbound call from your site.

Wix app

We store the Wix app instance ID for your site, unencrypted, because the uninstall and billing webhooks identify your site by it. We hold no site access token: calls to Wix are authorised per request by the app itself. We also store a link between the Wix user ID of the person who opened the app and their crawrix account, and, if you buy a plan through Wix, the plan and its status. Wix sends us app-instance and paid-plan webhooks.

Webflow app

We store the OAuth access token Webflow issues at install, encrypted, plus the site ID, the site’s short name, the published domains, the results of a capability probe (whether your plan allows redirects, robots.txt, and asset alt text), and the IDs of the webhooks we registered. If you connected with a pasted site API token instead of the OAuth install, that token is stored the same way. We also store a link between the Webflow user ID of a Designer user who opens the panel and their crawrix account, which is what lets a collaborator work on a site someone else installed. The short-lived ID token the Designer panel presents is verified against Webflow and never stored. Webflow sends us site-publish, page-metadata, page-delete, and CMS-item webhooks.

Shopify app

We store the offline Admin API access token, encrypted, along with the shop domain, the granted scopes, a link between the staff account that opened the app and their crawrix account, and the subscription state Shopify reports. Shopify sends us app-uninstall, shop-redact, and subscription webhooks.

What webhooks are for

Webhooks tell us that something changed on your site so our audit results do not go stale, and that an app was uninstalled or a plan changed so we can stop acting on your behalf. We verify every webhook signature before reading the body, and an unverified request is rejected without being processed. We do not use webhooks to collect anything beyond the event itself.

How writes are controlled

The service can only change your site through an allowlisted, metadata-class write surface: titles, meta descriptions, Open Graph tags, structured data, robots.txt, llms.txt, same-host redirects, CMS item fields, image alt text, and a small number of site settings. Page body content is refused on every platform. Every change is proposed to you with the current live value beside the new one and is applied only after you approve it; if the live value changed in the meantime, the whole batch is refused rather than overwriting the newer value. Every applied change records a pre-image and can be reverted from the History screen.

Revoking access

WordPress: disconnect from Crawrix → Settings in wp-admin, or delete the plugin. Either revokes the connection tokens and wipes the plugin’s stored options, redirects, and transients from your site.

Wix and Shopify: uninstall the app from the platform. The uninstall webhook revokes the connection and clears the stored credential on our side.

Webflow: revoke the app from your Webflow workspace. Webflow sends no uninstall webhook, so we detect the revocation either on our next API call, which clears the stored token immediately, or through a daily check that clears connections idle for about a day.

On any platform you can also revoke a site’s connection from your crawrix account, which deletes the stored credential straight away.

Data retention and questions

Audit results, findings, chat history, and change history for a connected site are retained in your crawrix account until you delete them or delete the account. Deleting a connection removes its credentials at once; the audit history remains until you remove it. For privacy questions or deletion requests, contact us at privacy@crawrix.ai.