You connected AI to your store. Did your customers consent?

This article is for informational purposes. It does not constitute legal advice. Every store is different. Consider consulting a privacy professional for your specific situation.

Do you know what your AI tools can access?

AI tools are connecting to merchant infrastructure from two directions at once.

OpenAI, Anthropic, Google, and xAI have built integrations that connect to email, cloud storage, calendars, CRM systems, and support platforms. Merchants can give an AI access to Gmail threads, Google Drive files, PayPal data, Klaviyo records, and Zendesk tickets. Often in a few clicks.

At the same time, WordPress is adding its own AI integration layer to Core. The Connectors API and AI Client ship to your WooCommerce store in WordPress 7.0, providing every installed plugin with a standard way to connect store data to any configured AI provider.

This is a new feature of the WordPress platform. Hence, most of us are not yet aware of how far these connections reach.

How does your customer data end up in AI?

Customer data reaches AI systems through three different paths.

Path 1: The plugin path. A WordPress or WooCommerce plugin uses the AI Client to send store data to a configured AI provider. Order details, support tickets, product information. The merchant may not know what each plugin includes in its prompts.

Path 2: The staff path. Someone on the team copies a customer email or order summary into ChatGPT, Claude, Gemini, or Grok. This could happen outside any WordPress integration or organizational contract, and maybe even on a personal ChatGPT account.

Path 3: The platform connector path. The AI platform integrates with connected business tools such as Gmail, Google Drive, a CRM, or payment processors. It pulls context into its responses on its own. The data does not need to be given to it. The AI goes and gets it.

Each path requires its own governance answer.

What have you connected your AI to?

Most merchants underestimate how broad these connections have become.

OpenAI (ChatGPT) calls its integrations apps. Google Drive, Slack, Asana, and other services are accessible inside ChatGPT conversations. Third-party apps can pull from additional systems. OpenAI’s documentation notes that custom apps are not verified and may allow users to share sensitive data with third parties.

Anthropic (Claude) offers workspace connectors for Gmail, HubSpot, Intercom, Square, PayPal, and others. Actions require explicit user approval by default. But some write-capable connectors can be configured to always allow actions without per-request confirmation. That setting alone is a reason to review connector permissions carefully.

Google (Gemini) integrates natively with the Google Workspace ecosystem. Gmail, Drive, Calendar, and Docs data can be accessed within Gemini conversations for Workspace subscribers. For merchants already living inside Workspace, this feels like a built-in feature rather than a separate integration. Easy to use. Also easy to overlook when auditing data flows.

xAI (Grok) connects to Google Drive on its business and enterprise tiers. Connected content is indexed, and Grok checks for changes every hour (some recent updates may take up to an hour to appear). Grok can cite documents back to users in conversation, meaning stored files are actively referenced.

Once a merchant or team member enables these connectors, the AI platform can access customer data that lives outside the store: email threads, support inboxes, shared drives, CRM records.

Have you looked at your WooCommerce store’s Connectors yet?

Once you update to WordPress 7.0, your WooCommerce store will get access to the Connectors API and the AI Client.

The Connectors API manages credentials centrally. A site owner configures an API key once at Settings > Connectors, and every plugin on the site can use it. OpenAI, Anthropic, and Google are supported in Core. Others register through provider plugins.

The AI Client gives plugins a standard way to talk to any configured AI provider. A plugin can send a prompt and receive a response without building its own integration. Credentials are site-wide, with no per-plugin scoping.

Your plugins are sending data. But which data?

Between the three paths, the data categories that can reach AI systems include: customer names, email addresses, billing and shipping addresses, order history, order values, support ticket content, refund requests, CRM records, full email threads, calendar entries, cloud documents, and internal notes.

The WordPress Abilities API (extended by the MCP Adapter) takes the plugin path further. WooCommerce can register capabilities like “retrieve order data” or “export customer records” that AI agents discover and call automatically. A single request can chain multiple capabilities across several systems.

When Claude reads a Gmail thread, the AI sees everything in those messages.

The drafted reply the merchant sees may look simple. The prompt that produced it can contain a stitched-together customer profile built from multiple systems at once.

The prompt is gone. Is the data?

Most privacy commentary stops at the moment data is sent. That is only half the picture. Four questions matter after the prompt leaves your site.

Was the data sent? In most setups, yes. But the merchant may not know which plugin sent what.

Was it stored? OpenAI’s API monitoring can retain request content for up to 30 days by default (zero-retention options available on enterprise plans).

Was it indexed? xAI documents that Drive content connected to Grok is indexed, synced hourly, and cited back in responses.

Was it remembered? Anthropic documents memory features and past chat search in Claude. Enterprise retention controls exist, but even incognito chats are subject to retention policies.

The consumer vs. business gap matters here. Google makes it very visible. In consumer Gemini, activity is auto-deleted after 18 months, and chats reviewed by human reviewers can be retained for up to three years. Google warns users not to enter confidential information. In Workspace Gemini, content is not used for training, and prompts and outputs are not stored or used for training without explicit Workspace admin permission (subject to Google’s Workspace data protection terms). A similar differentiation exists across all major AI platforms. Business and enterprise accounts offer explicit controls and zero-retention options. Consumer accounts do not. Your subscription tier and contract with the provider determine what happens to data after the interaction ends.

Two requirements. Do you meet both?

The merchant is the data controller. The AI provider is the data processor.

In GDPR, under Article 28, the controller must have a binding contract (data processing agreement, DPA – find a template here) with the processor covering subject matter, duration, nature, purpose, data types, and assistance duties. Without those processor terms, the merchant is missing a required GDPR control. A DPA and a lawful basis are two separate requirements. You need both.

AI-assisted support and internal operations can often fall under existing lawful bases. GDPR still requires transparency in every case: the purpose, lawful basis, categories of recipients, retention periods, and transfer safeguards must be disclosed.

If legitimate interest is the basis, Article 21 gives customers the right to object. For higher-risk uses like automated customer scoring or behavioral segmentation, Article 35 can require a Data Protection Impact Assessment.

In short, the two requirements are: a processor contract (DPA) with every AI provider that touches your customers’ data, and a lawful basis for the processing itself. They are separate. You need both.

Companies that have data privacy officers who stopped their marketing teams from implementing Google Tag Manager are now loading their entire customer data and employee data into AI tools.

All for the sake of convenience. Without informing anyone or asking for opt-in.… https://t.co/K1BmKRL0OA

— Matthias Reinholz (@MattReinholz) April 11, 2026

Are you on the right AI plan?

Consumer AI plans are the wrong default for working with customer data in a commercial context. Consumer services may use content for model training unless the user opts out, and generally lack the organizational controls businesses need.

The picture across providers is consistent:

• OpenAI business and API offerings do not train on inputs by default. DPA included.
• Anthropic incorporates its DPA into commercial terms for Claude for Work and the API. No training on commercial inputs by default.
• Google offers DPA terms and EU data residency for Workspace business tiers.
• xAI enterprise terms include a DPA and automatic 30-day deletion. No training by default.

Business-tier accounts also add admin controls, usage logging, retention configuration, and subprocessor lists. If real customer data is involved, a commercial plan with the right contract is where you need to start.

Can you control what you just enabled?

The WordPress Connectors API makes it easier to build AI integrations than to govern them.

Credentials are site-wide. A plugin installed after initial configuration can use the shared API keys immediately. API keys configured via Settings > Connectors are stored in the WordPress database and are not encrypted at rest by default (they are masked in the admin UI). Encryption is being explored for a future Core update. For production sites, use environment variables or server-level secrets management where possible. The wp_ai_client_prevent_prompt filter exists for blocking prompts, but it is a developer hook, not a merchant-facing permission layer yet.

WooCommerce’s Abilities API compounds this. Order data, stock data, and customer records are registered as discoverable capabilities for AI agents by design. The tools for building are ahead of the tools for controlling.

Where do you start?

Update your privacy policy. Name each AI provider that processes customer data, describe the data categories and purposes, identify the lawful basis, and document transfer safeguards for non-EU providers.

Handle data subject requests. WordPress manages export and erasure through Tools > Export Personal Data and Tools > Erase Personal Data. WooCommerce adds order data to those exports and exposes retention settings under WooCommerce > Settings > Accounts & Privacy. These tools cover the WordPress side. They do not erase data already sent to an external AI provider.

Set internal rules. Staff need a clear answer to four questions. Which AI tools are approved? Which data can be used? Which account tier is required? Who decides when a new AI workflow is acceptable? Write those answers down. That document will do more for compliance than a vague internal promise to be careful with AI.