Draft. This document is a template under legal review and is not yet in force. Highlighted fields are still to be filled in.
Privacy Policy
1. Data controller
- The controller of your personal data is SEMownia Szymon Sanecznik, ul. Twarda 44, 00-831 Warszawa, tax ID (NIP) 6422931698 ("we", "Controller").
- For data protection matters, write to [email protected] or by post to the address above. We have not appointed a Data Protection Officer because the law does not require it for our activities. LAWYER: confirm.
- This policy covers the website
tellmyshop.com, the customer account, purchases, the free TellMyShop Free version, the licence check performed by the TellMyShop module, support and the newsletter. Section 4 explains separately what happens to the data from your store when you use the module together with Claude.
2. Summary
- We process only the data needed to sell licences, run the account, check licences and answer messages.
- In normal operation we do not receive your store's product, order or customer data. When Claude uses the module, the data goes from your store to your own Claude account (section 4).
- Payments are handled by Stripe. We do not see your full card number.
- We send marketing messages only with your separate consent.
- You can access your data, correct it, delete it, port it and object to some ways of processing it (section 9).
3. What data, for what purpose and on what legal basis
GDPR means Regulation (EU) 2016/679.
3.1. Website visitors
| Data | Purpose | Legal basis |
|---|---|---|
| IP address, browser and device information, pages visited, time, referring page (server and security logs) | running the website, security, preventing abuse | legitimate interest (art. 6(1)(f) GDPR) |
| cookie choice | remembering the choice | legal obligation and legitimate interest (art. 6(1)(c) and (f)) |
| usage statistics through ANALYTICS_PROVIDER | understanding which pages help visitors, improving the website | consent (art. 6(1)(a)) if the tool uses cookies or similar identifiers; otherwise legitimate interest TBC: website, depends on the tool chosen LAWYER/B3: (1) aggregate sales statistics sent from the server to Google Analytics without a personal identifier (random identifier, no IP and no email), also without consent; with an identifier only after analytics consent; (2) Meta Conversions API (hashed email, purchase) only after marketing consent; add Google and Meta to the recipients (section 5) and to the transfer to the USA (section 6); WNIOSKI (findings) 2026-10-06 |
| advertising pixels (AD_PIXELS, if used) | measuring the effectiveness of ads | consent (art. 6(1)(a)) |
Cookies are described in section 11.
3.2. Account
| Data | Purpose | Legal basis |
|---|---|---|
| email, password (hashed), full name, language, login history | creating and running the account | performance of the contract (art. 6(1)(b)) |
| licences, domains, development domains, downloads | managing licences and downloads | performance of the contract (art. 6(1)(b)) |
3.3. Purchases, invoices and refunds
| Data | Purpose | Legal basis |
|---|---|---|
| full name, company name, billing address, country, tax ID (NIP) / EU VAT number, email, order details, amount, currency, VAT, Stripe customer and payment identifiers (not full card numbers) | concluding and performing the contract, delivering the licence key | performance of the contract (art. 6(1)(b)) |
| tax ID (NIP) or EU VAT number (required field when ordering) and the result of the EU VAT number check in the VIES system, with a timestamp | confirming that the order is placed by a business, and correct VAT accounting | legal obligation (art. 6(1)(c)) under the law on value added tax, and performance of the contract (art. 6(1)(b)) |
| the same data, invoices | issuing invoices (including through KSeF for Polish businesses), accounting, tax records, VAT OSS settlement | legal obligation (art. 6(1)(c)) under tax and accounting law |
| consent to immediate delivery and acknowledgement of the loss of the right of withdrawal (required box on the order page), with a timestamp | demonstrating that the statutory conditions were met | legal obligation and legitimate interest (art. 6(1)(c) and (f)) |
| withdrawal statements, refund requests, complaints, chargebacks | handling them and defending against claims | legal obligation (art. 6(1)(c)) and legitimate interest (art. 6(1)(f)) |
Stripe also processes payment data as an independent controller for its own purposes, for example fraud prevention and meeting regulatory obligations. Details are in Stripe's privacy policy.
3.4. TellMyShop Free version
| Data | Purpose | Legal basis |
|---|---|---|
| email, account data, activated domain, versions of PrestaShop or WordPress (and WooCommerce), PHP and the module | providing the free version | performance of the contract (art. 6(1)(b)) |
| aggregate statistics on PrestaShop, WordPress, WooCommerce and PHP versions | decisions on supported versions (for example PrestaShop 1.7) | legitimate interest (art. 6(1)(f)) |
Creating an account for the TellMyShop Free version does not mean subscribing to the newsletter. The newsletter requires separate consent (section 3.7).
3.5. Licence verification
During licence verification (about once a day and on activation), the PrestaShop module or the WordPress plugin sends:
- the licence key (on activation) or the signed licence token (on refresh);
- the domain and URL of the store or website (for WordPress also the WordPress installation address, if different);
- a random installation identifier generated at installation;
- the versions of the module or plugin, of PrestaShop or WordPress (and WooCommerce, if installed), and of PHP;
- and, as with any internet connection, the IP address of the server of the store or website (for WordPress also the standard User-Agent header with the WordPress version and the website address).
(WordPress plugin: checked in the code src/License/LicenseManager.php, 2026-10-06.)
TBC: plugin code: confirm the exact scope of the data and whether domain verification by callback has been implemented.
| Purpose | Legal basis |
|---|---|
| checking the validity of the licence, counting domains, delivering updates | performance of the contract (art. 6(1)(b)) |
| detecting licence misuse (for example one key in many stores) | legitimate interest (art. 6(1)(f)) |
This data mainly concerns your business and your server. It becomes personal data when it can be linked to you, for example when you are a sole trader.
Setup statistics. Together with the licence check (once a day), and once right after Claude first connects to the module, the module sends dates and numbers only:
- the date Claude first called the module (
first_tool_call_at); - the date the first Ready Job was run (
first_job_run_at); - the number of items in the latest fix plan (
audit_findings_count; in version 2.6.0 the field is empty); - the number of saved changes and the number of undos since installation (
writes_count,reverts_count) and the date of the first undo (first_revert_at); - how many times each Ready Job has been run (
jobs_runs); - the number of calls in each area of the module, blocks 0–5 (
block_calls).
The statistics contain no content of conversations with Claude, no product names or descriptions, no orders and no data about your store's customers. Only the paid PrestaShop version of the module sends statistics; the free TellMyShop Free version does not connect to the licence server. The WordPress plugin does not send setup statistics. If we ever add them, they will be switched off by default, and we will change this policy beforehand. Sending statistics is switched off by default, including after every module update. The module sends them only if you switch them on in the admin panel with the "Send setup statistics (numbers only)" switch, and you can switch them off at any time. The licence check works independently of this switch, and the help messages described in section 3.7 then rely on activation data only. Basis: your consent given by switching the switch on (art. 6(1)(a) GDPR); switching it off withdraws consent. (Code: module 2.6.5, DECYZJE (decisions) 1.41, PR #67, 2026-10-06. TBC: 2.6.5 released before this policy is published.)
| Purpose | Legal basis |
|---|---|
| showing setup progress in the customer account and in the module; sending help only to people who got stuck (section 3.7) | performance of the contract (art. 6(1)(b)) |
| aggregate statistics that help us improve installation and instructions | consent (art. 6(1)(a)); you withdraw it by switching the switch off |
LAWYER: from 2.6.5, statistics are sent only after the owner switches them on (opt-in), which is intended to satisfy Article 399 of the Polish Electronic Communications Law (PKE). Please confirm that switching on the switch in the panel with this information is sufficient as consent.
3.6. Support and contact
| Data | Purpose | Legal basis |
|---|---|---|
| email, full name, content of the message, attachments, technical information sent (versions, logs, screenshots) | answering questions, fixing problems, handling complaints | performance of the contract (art. 6(1)(b)) and legitimate interest in answering enquiries (art. 6(1)(f)) |
If you send us data about your store's customers (for example in logs, screenshots or a database dump), we process it on your behalf under the Data Processing Agreement. Send only what is necessary, masked where possible.
3.7. Newsletter and marketing
| Data | Purpose | Legal basis |
|---|---|---|
email, first name (optional), language, date and source of consent, opens and clicks TBC: website LAWYER/B3: on sign-up to the list, the website also records utm_content and the entry path (where the person came from); add "source of entry to the website (e.g. campaign)" and the purpose "assessing which channels bring sign-ups", basis art. 6(1)(f); WNIOSKI (findings) 2026-10-06 | sending information about the product and offers | consent (art. 6(1)(a) GDPR and the consent to marketing communication required by the Polish Electronic Communications Law) |
LAWYER/B3: add a row "downloadable materials (e.g. PDF checklist from the blog)": email, sending the material, art. 6(1)(b); without marketing consent the address is deleted after 30 days; marketing consent in a separate field with email confirmation; E10 → E5 2026-10-06
You can withdraw consent at any time using the link in the message or by writing to [email protected]. Withdrawal of consent does not affect the lawfulness of earlier processing.
Service messages (order confirmation, licence key, security notices, changes to terms, end of the updates period) are part of performing the contract and are not marketing. We treat single setup help messages the same way, for example when a key is still not active after a few days or Claude has not yet connected to the module. They concern only getting what you already have working, contain no prices or offers, and you can opt out of further ones using the link in the message footer (performance of the contract, art. 6(1)(b); for reminders, legitimate interest, art. 6(1)(f)).
3.8. Claims
We may process the data described above to establish, pursue or defend claims, on the basis of legitimate interest (art. 6(1)(f)).
4. Data from your store or website
This section applies equally to the PrestaShop module and the WordPress plugin (with or without WooCommerce); "store" here also means a WordPress website.
- The module runs on your server. When you ask Claude to do a task in your store, Claude calls a tool of the module. The module reads or changes data in your store and returns the result to Claude. The data goes from your store to your own Claude account at Anthropic and nowhere else. [TO BE CONFIRMED in the module code.]
- In normal operation we do not receive your store's data. TellMyShop servers do not receive product, order, customer or content data from your store when you use the module. We do not store it and do not use it to train any models. The only data the module sends to us is the licence verification data and, if you switch them on, the setup statistics (dates and numbers only) in section 3.5. Claude connects directly to the module on your server using a token generated in the module, so the connection does not pass through our servers. CONFIRM before each release.
- Anthropic is your provider, not ours. Anthropic processes the data that reaches your Claude account under your own agreement with Anthropic and Anthropic's privacy terms for your Claude plan. We are not a party to that relationship and have no influence over what Anthropic does with the data. If the data includes personal data of your customers, you as the store owner are its controller. The roles and a checklist are described in the Data Processing Agreement and GDPR guide.
- Claude gets no customer data until you allow it. By default, the module gives Claude no access to your customers' personal data. In WordPress this also covers WooCommerce customers and orders, user accounts, form entries, and the emails and IP addresses of comment authors. You can choose access with pseudonymisation (full names, email addresses, phone numbers and addresses are masked before results are returned to Claude) or, for 1 to 24 hours and with a stated purpose, full access, after which the module automatically returns to the previous level. The module's change history is deleted after 180 days by default. LAWYER: check the wording.
- Exceptions in which store data may reach us:
- support: when you send us logs, screenshots, database dumps or give us temporary access to your store; the Data Processing Agreement then applies;
- licence verification: domain, store URL and versions and, if you switch them on, setup statistics (dates and numbers only), as in section 3.5.
5. Recipients of data
We use the following providers (processors), who process data only on our instructions:
| Provider | Service | Location / transfer safeguard |
|---|---|---|
| Vercel Inc. (e.g. Vercel Inc.) | website and API hosting | EU (Frankfurt, Germany) / SAFEGUARD |
| Neon (Databricks, Inc.) | database of accounts, orders and licences | EU (Frankfurt, Germany) (EU region preferred) |
| Cloudflare R2 | storage of module files for download | STORAGE_REGION |
| Resend | transactional messages (licence key, confirmations) | EMAIL_LOCATION / SAFEGUARD |
| MAILBOX_PROVIDER | support mailbox | MAILBOX_LOCATION / SAFEGUARD |
| NEWSLETTER_PROVIDER | newsletter | NEWSLETTER_LOCATION / SAFEGUARD |
| INVOICING_TOOL (e.g. Fakturownia, inFakt or wFirma) | invoicing and KSeF | Poland / EU |
| ACCOUNTING_FIRM | accounting and tax | Poland |
| ANALYTICS_PROVIDER | website statistics | ANALYTICS_LOCATION / SAFEGUARD |
Stripe (Stripe Payments Europe, Ltd., Ireland, and Stripe, Inc., USA) handles payments and calculates taxes. For some operations it acts as our processor, and for others as an independent controller (for example in fraud prevention).
We may also disclose data to public authorities, for example tax authorities or courts, when the law requires it, and to our legal advisers.
We do not sell personal data.
6. Transfers of data outside the European Economic Area
Some providers (for example Stripe, Inc. or a US hosting provider) may process data in the United States or other countries outside the EEA. We transfer data only:
- to countries covered by a European Commission decision finding an adequate level of protection, including to US companies certified under the EU-US Data Privacy Framework; or
- on the basis of Standard Contractual Clauses approved by the European Commission, with additional safeguards where needed.
You can receive a copy of the safeguards by writing to [email protected]. TBC: website: enter the actual safeguard for each provider.
7. How long we keep data
| Data | Retention period |
|---|---|
| Account | until the account is deleted; after deletion only to the extent needed for the purposes below |
| Orders, invoices, payment data | 5 years from the end of the calendar year in which the tax payment deadline passed (Article 86 of the Polish Tax Ordinance, Article 74 of the Polish Accounting Act) |
| Licences and activations | for as long as the licence exists, and then until the limitation period for claims expires |
| Licence verification logs with IP address | LICENCE_LOG_RETENTION (proposal: 12 months) |
| Setup statistics | for as long as the licence exists; in aggregate statistics without a link to the account |
| Server and security logs | SERVER_LOG_RETENTION (proposal: 30 days) |
| Consent to immediate delivery, records of withdrawals, refunds and complaints | until the limitation period for contractual claims expires (as a rule up to 6 years, at the end of the calendar year, Article 118 of the Polish Civil Code) |
| Support correspondence | SUPPORT_RETENTION from the closing of the case (proposal: 3 years) |
| Store data received in support (logs, database dumps, screenshots) | deleted no later than 30 days after the case is closed, see the Data Processing Agreement |
| Newsletter | until consent is withdrawn; proof of consent until the limitation period for claims expires |
| Statistics | ANALYTICS_RETENTION |
LAWYER: confirm the retention periods.
8. Is providing data required
Providing data for the account and the purchase is voluntary but necessary to conclude the contract. Invoice data is required by tax law. A tax ID (NIP) or EU VAT number is required because we sell licences only to businesses. Without them we cannot sell a licence. Subscribing to the newsletter is entirely voluntary.
9. Your rights
You have the right to:
- access your data and receive a copy;
- rectify inaccurate data;
- erase data ("right to be forgotten"), unless we must keep it, for example for tax purposes;
- restrict processing;
- data portability for data you gave us on the basis of a contract or consent;
- object to processing based on legitimate interest, and at any time to direct marketing;
- withdraw consent at any time, without affecting earlier processing;
- lodge a complaint with the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa,
uodo.gov.pl) or with the supervisory authority in your country of residence or work.
Write to [email protected]. We respond within one month; in complex cases the period may be extended by two months. We may ask you to confirm your identity.
10. Automated decisions
We do not make decisions about you based solely on automated processing that produce legal effects or similarly significantly affect you. Stripe may use automated fraud risk assessment during payment under its own rules. The licence server automatically classifies domains as production or development under published rules (§ 5 of the EULA); you can ask support for a re-assessment.
11. Cookies
- Cookies are small files stored by the browser. We use:
| Type | Examples | Basis |
|---|---|---|
| Strictly necessary | login session, security token (CSRF), cookie choice, language; Stripe cookies on the payment page used for fraud prevention | no consent; necessary to provide the service you request |
| Analytics | ANALYTICS_PROVIDER; tms_hero (TellMyShop): remembers which version of the home page you see in an A/B test, so that you see the same one on later visits (contains only the letter a or b, no identifier), kept for 30 days and deleted when consent is withdrawn | consent, unless the tool works without cookies and similar identifiers |
| Marketing | AD_PIXELS (if used) | consent |
- On your first visit, the banner lets you accept or reject non-essential cookies with equal ease. You can change your choice at any time via the "Cookie settings" link in the footer and in your browser settings.
LAWYER: the basis in Poland is Article 399 of the Polish Electronic Communications Law (Prawo komunikacji elektronicznej), implementing Article 5(3) of the ePrivacy Directive. Verify the banner and the cookie list once the website is built. TBC: website: full cookie list with names, providers and lifetimes.
12. Security
We protect data by, among other things, encryption in transit (HTTPS), access control and two-factor authentication on administrative accounts, storing passwords as hashes, encrypted storage of licence keys, minimal access for people working with us, and regular backups. We store licence keys as a hash and an encrypted copy, so that the key can be displayed in the account.
13. Changes to the policy
We publish changes on this page and inform account holders of significant changes by email. The date at the top indicates the current version.
PrestaShop is a registered trademark of PrestaShop SA. WordPress is a trademark of the WordPress Foundation. WooCommerce is a trademark of Automattic Inc. Claude is a trademark of Anthropic. TellMyShop is not affiliated with any of these entities.