AI for store owners
Is it safe to give AI your store data? 8 questions to ask first
It can be safe, if you know what the tool sends and keeps. Before connecting any AI tool, find out what leaves your store, whether it includes customer personal data, how long it's stored, whether it trains models, and whether the tool can change anything. A tool that can't answer these in writing isn't ready for your store.
Below is a checklist that works for any AI tool, whether it's a general AI chat you upload exports to, a plugin, or something a developer built on the WooCommerce REST API. After each question, you'll find what a good answer looks like and how Askshelf answers it, using the same wording as its readme and privacy policy.
1. What data leaves the store?
There's a big difference between a tool that sends "net sales for October: $8,200" and one that sends every order row. Ask for a specific list, not "we only use what we need".
- Good answer: a named list of fields or a description of the queries, and the point at which data first leaves (installing, connecting, or asking).
- Warning sign: "your store data" with no detail, or a full database sync for a tool that only answers questions.
Askshelf: nothing leaves the store until a store manager clicks Connect Askshelf. Connecting sends the store's home URL and its WordPress, WooCommerce and Askshelf version numbers. When you ask a question, your browser sends your question, the earlier questions and answers in that conversation, the results of the read-only lookups the AI asked for (such as totals, product names and order numbers), your store's date, time zone, currency and locale, and a short-lived token signed by your store.
2. Does it include customer personal data?
Names, emails, phone numbers, addresses and IP addresses are personal data. Sending them to a third party brings in your own privacy policy and, depending on where you and your customers are, data protection law. Most sales and stock questions don't need any of it.
- Good answer: personal data is never read, or is removed before anything is sent, and the tool refuses questions about individual people.
- Warning sign: a CSV upload of the Customers report, which includes names and emails. That's the most common way personal data ends up in an AI chat.
Askshelf: customer names, emails, phone numbers, addresses and IP addresses are never read or sent. Its lapsed customer and customer retention lookups return counts only, with no names. Questions that contain an email address or phone number are refused in your browser and never sent, and the service checks again.
3. Where does the data go?
An AI tool is often a chain: the tool's own service, then one or more AI model providers. Each link should be named.
- Good answer: a list of processors (hosting, AI routing, model providers) in the privacy policy.
- Warning sign: "trusted partners" with no names.
Askshelf: the Askshelf service is hosted on Supabase and forwards questions to an AI model through OpenRouter, restricted to model providers that don't store or train on the data. The privacy policy notes that providers may process data outside your country, including in the United States.
4. Is it stored, and for how long?
Ask separately about the tool's own servers, the AI provider, and your own site. "We don't store your data" sometimes means "we don't store it for long".
- Good answer: a retention period for each kind of data, and a way to delete it.
- Warning sign: no retention period, or logs kept "as long as needed".
Askshelf: the service doesn't store questions, answers or store data. Once an answer is shown, the question, answer and lookup results aren't kept. It keeps, for each connected store, the site ID, secret, home URL and version numbers; for your account, your email address, plan and, on a paid plan, billing customer and subscription IDs; and counts of questions and AI tokens used. Its hosting provider keeps short-lived request logs, including IP addresses, for security. Conversations are saved in your own WordPress database, per user, and uninstalling the plugin deletes them.
5. Is it used to train AI models?
This is separate from storage. Some AI services let you control whether your conversations are used to improve their models, and the setting can differ by plan. If you upload exports to a general AI chat, check that tool's data controls and your plan's terms before you do.
- Good answer: a clear "no", in the terms or privacy policy, covering both the tool and the model providers it uses.
- Warning sign: silence on the subject, or an opt-out buried in settings.
Askshelf: questions go only to model providers that don't store or train on the data.
6. Can it read only, or also write?
For analysis, a tool should only need to read. Write access means a bug, a misunderstood request or a compromised account can change prices, stock or orders.
- Good answer: read-only by design, and stated as such.
- Warning sign: a request for a REST API key with Read/Write permission for a reporting tool. WooCommerce lets you choose Read, Write or Read/Write when you create keys under
WooCommerce › Settings › Advanced › REST API, so you can always give less. See the WooCommerce REST API documentation.
Askshelf: every lookup is read-only, and there's no code in the plugin that writes store data. The only things it saves are its own settings and your chat history.
7. Who in your team can use it, and where do conversations live?
Questions and answers about your store are business information. Know who can see them.
- Good answer: access tied to WordPress roles, conversations kept on your own site or deletable on request.
- Warning sign: a shared login, or conversations kept on someone else's servers with no way to delete them.
Askshelf: conversations are stored in your WordPress database, per user. The Askshelf service can't see them.
8. What happens when you stop using it?
- Good answer: uninstalling removes local data, and you can ask the vendor to delete your account.
- Warning sign: no mention of deletion at all.
Askshelf: uninstalling the plugin deletes its settings, the connection and all saved conversations. You can ask for your account to be deleted.
The checklist on one page
| Question | Ask for | Askshelf's answer |
|---|---|---|
| What leaves the store? | A specific list | Question, conversation, lookup results, store date and locale settings |
| Customer personal data? | None, or removed before sending | Never read or sent |
| Where does it go? | Named processors | Supabase, OpenRouter, no-storage model providers |
| Stored, how long? | A period for each kind | Questions, answers and store data not kept |
| Trains models? | A written "no" | No |
| Read or write? | Read-only for analysis | Read-only |
| Where do chats live? | Your site, per user | Your WordPress database |
| On uninstall? | Local data deleted | Settings, connection and conversations deleted |
What about uploading exports to a general AI chat?
The checklist applies there too, but the answers depend on the tool and your plan, and you control the biggest risk yourself: what's in the file. Before uploading:
- Remove personal data. Delete name, email, phone and address columns. The Customers report export contains names and emails.
- Send totals, not rows, when totals answer the question.
- Check the tool's settings for conversation history and model training, on the plan you actually use.
The wider trade-off is in ChatGPT vs a built-in store analyst.
Safe doesn't mean correct
A tool can handle your data perfectly and still give you a wrong number, because of a date range, an excluded status or a sum. Privacy and accuracy are separate checks. For the second, see how to check an AI's answers about your store.
Askshelf shows the lookups behind every answer, so you can check them:
How many customers with 3 or more orders haven't ordered since June?
For the bigger picture of where AI fits in your reporting, read using AI to analyze your WooCommerce store. Askshelf is free for 10 questions a month; plans are on the pricing page.
Common questions
Is it against GDPR to use AI on my store data?
Not in itself. The questions are whether personal data is sent, to whom, and on what basis. Tools that answer sales and stock questions without customer names or contact details avoid most of the issue; for anything else, check with your own adviser.
Should I give an AI tool a REST API key with write access?
Only if it genuinely needs to change things and you trust the code behind it. For analysis, a Read permission key is enough, and you can revoke it under WooCommerce › Settings › Advanced › REST API.
Does Askshelf see my customers' names or emails?
No. Its lookups never read or send customer names, emails, phone numbers or addresses, it declines questions about individual people, and questions containing an email address or phone number are refused in your browser before they're sent.