Claude works in your store. You decide what gets saved.
Claude gets access to your store the way a new employee would: at first it can only look, and later it does what you allow. The same rules apply in PrestaShop and WordPress.
Sofas category description
Sofas at the best prices. Happy shopping!
Two- and three-seater, sofa beds and corner sofas, delivered in 5 days.
Claude has 12 new descriptions. Have a look before I save.
Saved. I'm keeping the old versions.
Undone. Your store is back to yesterday.
1.A preview before every save
Claude can look around your store as much as it needs. When it wants to change something, it shows the current version and the new one. It saves only after your "yes".
- If someone on your team edits the same product after Claude showed you the preview, Claude won't save its change. It shows you a new preview first.
- Your "yes" covers exactly the change you see in the preview.
2.History and undo
Every change Claude makes goes into a history together with the previous version.
- Ask "What did you change this week?" and you get a list of changes with the old and new versions.
- "Undo Monday's changes in Sofas" brings back the old texts, even for 40 products at once.
- Before a theme file changes, Claude makes a backup copy, so you can restore the previous look from that copy.
- A few things can't be undone from the history, such as database structure changes or installing and removing modules and plugins. Claude says so in the preview.
3.At first, Claude can only read
After installation Claude can only look at your store. You switch on everything else separately, when you want to.
| What | After installation |
|---|---|
| Store review, finding problems | on |
| Texts and Google | off until you allow changes |
| Prices, promotions, discount codes, stock | separate switch, with a risk confirmation |
| Store design, other modules and plugins | separate switch |
| Server files and the database | only in service mode, for a few hours, for a technical person |
Claude works on its own account that nobody can log in to. It has only the permissions you give it.
4.Customer data stays private
After installation Claude doesn't see your customers' personal data at all: names, e-mails, phone numbers, addresses.
- Three access levels. No access (the default after installation). Hidden data: Claude sees orders and amounts, but a pseudonym instead of the customer. Full access only for a few hours, for example to handle a complaint, then it switches itself off.
- A reason in the log. When you switch on full access, you type why. The entry stays in the log.
- Files Claude won't open. Passwords and keys, database backups, server logs and files from customers are always blocked.
- Encrypted customer data. History entries with customer data and all file backups are encrypted with a key kept outside the database. By default TellMyShop deletes history older than 180 days.
5.You know what's happening
- The connection log shows when Claude connected and what it did, without the content of your chats.
- One button switches the connection to Claude off completely.
6.How it works in WordPress
WordPress with WooCommerce follows the same rules. The plugin adds a few things site owners ask about:
- A separate "Claude (TellMyShop)" account. Claude works as its own WordPress user that can't log in to wp-admin. In the free Audit that account can only read.
- A private connector address. You create it in the plugin. You can switch it off or generate a new one at any time, and the old one stops working at once.
- Customer data off by default. Personal data from WooCommerce orders, user accounts and forms stays hidden until you switch it on. Then Claude sees initials and pseudonyms instead of names and e-mails. E-mails and IP addresses in logs and comments are always masked.
- Limits and an IP allow-list. At most 120 calls and 60 saves an hour. You can also allow only chosen IP addresses and get an e-mail about failed connection attempts.
- Connection log and audit log. Every call goes to the connection log (30 days by default). Every change to the protection settings, such as switching on customer data or the Commerce block, goes to an audit log you can't clear from the panel. You can download it as CSV.
- Text for your privacy policy. The "Customer data (GDPR)" tab has ready text for your privacy policy and record of processing. Adapt it with your lawyer.
7.GDPR
TellMyShop helps you meet GDPR requirements: it hides customer data by default, encrypts history entries that contain it and deletes old entries itself. Exporting or erasing a customer's data also covers those entries: in PrestaShop through the GDPR module (psgdpr), in WordPress through the privacy tools (Tools → Export and Erase Personal Data).
For your developer
Preview and a single-use change token bound to that preview, HTTPS only, hourly limits on calls and saves, an IP allow-list, a separate account without login, encryption of history entries with customer data and of file backups, file integrity checks. In WordPress: a separate user without login, WordPress capabilities instead of an administrator account, and an audit log you can export as CSV.
Try it on your own store before you pay
The free TellMyShop Audit only reads your store and shows a plan of fixes.