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. Who is responsible for your data
1.1. The controller of your personal data is SEMownia Szymon Sanecznik, ul. Twarda 44, 00-831 Warszawa, tax ID (NIP) 6422931698 ("we", "us").
1.2. Contact for privacy matters: privacy@tellmyshop.pl 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.
1.3. This policy covers the website tellmyshop.pl, the customer account, purchases, the free Audit edition, the licence check performed by the TellMyShop module, support and the newsletter. Section 4 explains separately what happens to the data in your store when you use the module with Claude.
2. Summary
- We collect what we need to sell you a licence, run your account, check the licence and answer your emails.
- In normal operation we do not receive your store's product, order or customer data. When Claude uses the module, that data goes from your store to your own Claude account (section 4).
- Payments are handled by Stripe. We never see your full card number.
- Marketing emails only with your separate consent.
- You can access, correct, delete or export your data and object to some uses (section 9).
3. What we process, why, 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 requested, time, referrer (server and security logs) | running the website, security, preventing abuse | our legitimate interest (art. 6(1)(f) GDPR) |
| Cookie consent choice | remembering your choice | legal obligation and legitimate interest (art. 6(1)(c) and (f)) |
| Usage statistics through ANALYTICS_PROVIDER | understanding which pages help visitors and improving the website | your consent (art. 6(1)(a)) if the tool uses cookies or similar identifiers; otherwise our legitimate interest TBC: website, depends on the tool chosen |
| Advertising pixels (AD_PIXELS, if used) | measuring ads | your consent (art. 6(1)(a)) |
See section 11 for cookies.
3.2. Account
| Data | Purpose | Legal basis |
|---|---|---|
| email, password (hashed), name, language, login history | creating and running your 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 |
|---|---|---|
| name, company name, billing address, country, tax ID / VAT ID, 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)) |
| the same data, invoices | issuing invoices (including through KSeF for Polish businesses), accounting and tax records, VAT OSS | legal obligation (art. 6(1)(c)) under tax and accounting law |
| consent to immediate delivery and acknowledgement of loss of the right of withdrawal, with timestamp | proving 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 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, such as fraud prevention and meeting financial regulations. See Stripe's privacy policy.
3.4. Audit edition
| Data | Purpose | Legal basis |
|---|---|---|
| email, account data, activated domain, PrestaShop, PHP and module versions | providing the free edition | performance of the contract (art. 6(1)(b)) |
| aggregated statistics on PrestaShop and PHP versions | deciding which versions to support (for example PrestaShop 1.7) | our legitimate interest (art. 6(1)(f)) |
Creating an account for the Audit edition does not sign you up for marketing. The newsletter needs a separate consent (section 3.7).
3.5. Licence verification
When the module checks the licence (about once a day and on activation) it sends:
- the Licence Key or the signed token derived from it;
- the domain and the shop URL;
- a random instance identifier generated when the module was installed;
- the versions of the module, PrestaShop and PHP;
- and, as with any internet request, the IP address of your server.
TBC: plugin code: confirm the exact payload, including whether the domain verification callback is implemented.
| Purpose | Legal basis |
|---|---|
| checking that the licence is valid, counting domains, delivering Updates | performance of the contract (art. 6(1)(b)) |
| detecting misuse of licences (for example one key on many stores) | our legitimate interest (art. 6(1)(f)) |
This data mostly concerns your business and your server. It becomes personal data when it can be linked to you, for example if 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 store review was completed (
first_job_run_at); - the number of items in the latest fix plan (
audit_findings_count); - the number of saved changes and undos since installation (
writes_count,reverts_count).
The statistics contain no Claude conversation content, no product names or descriptions, no orders and no data about your store's customers. You can switch them off in the module ("Technical details" card, "Send setup statistics" switch); the licence check keeps working, and the help emails described in section 3.7 then rely on activation data only. TBC: plugin code: field names and switch as in plugin/onboarding-w-module.md.
| Purpose | Legal basis |
|---|---|
| showing setup progress in your 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 | our legitimate interest (art. 6(1)(f)); you can object by switching it off |
LAWYER: does sending statistics from a module running on the customer's server require consent under art. 5(3) of the ePrivacy Directive (PL: art. 399 Electronic Communications Law), or is a default-on switch with this notice enough?
3.6. Support and contact
| Data | Purpose | Legal basis |
|---|---|---|
| email, name, content of messages, attachments, technical details you send (versions, logs, screenshots) | answering questions, fixing problems, handling complaints | performance of the contract (art. 6(1)(b)) and our 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. Please send only what we need, masked where possible.
3.7. Newsletter and marketing
| Data | Purpose | Legal basis |
|---|---|---|
| email, name (optional), language, consent date and source, opens and clicks TBC: website | sending product news and offers | your consent (art. 6(1)(a) GDPR, and the consent required by electronic communications law for marketing emails) |
You can withdraw consent at any time with the link in each email or by writing to privacy@tellmyshop.pl. Withdrawal does not affect earlier processing.
Service emails (order confirmation, licence key, security notices, changes to terms, expiry of the Updates Period) are part of the contract and are not marketing. We treat single setup help emails 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 only cover getting what you already have working, contain no prices or offers, and you can opt out of further ones with the link in the footer (performance of the contract, art. 6(1)(b); for reminders, our legitimate interest, art. 6(1)(f)).
3.8. Legal claims
We may process the data described above to establish, exercise or defend legal claims, on the basis of our legitimate interest (art. 6(1)(f)).
4. Data from your store
4.1. The module runs on your server. When you ask Claude to do something 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. That data goes from your store to your own Claude account at Anthropic, and nowhere else. CONFIRM against module code.
4.2. We do not receive your store's data in normal operation. 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 model. The only data the module sends to us is the licence check data and the setup statistics (dates and numbers only) in section 3.5. Claude connects directly to the module on your server using an access token generated in the module, so the connection does not pass through our servers. CONFIRM before each release.
4.3. 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 do not control what Anthropic does with the data. If the data includes personal data of your customers, you as the store owner are the controller of that data. The Data Processing Agreement and GDPR guide explains the roles and gives a checklist.
4.4. Customer data is masked before it is passed to Claude. The module masks your customers' personal data (for example names, email addresses, phone numbers and addresses) before returning results to Claude, unless you switch masking off in the module settings. In Service mode, customer tables are excluded from SQL queries by default. CONFIRM against module code: which fields and tools are masked and how the exclusion works. LAWYER: review wording.
4.5. Exceptions where store data may reach us:
a) support: when you send us logs, screenshots, database dumps or give us temporary access to your store; the Data Processing Agreement then applies; b) licence check: domain, shop URL and versions, plus setup statistics (dates and numbers only), as described in section 3.5.
5. Who receives your data
We use these service 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 for accounts, orders and licences | EU (Frankfurt, Germany) (EU region preferred) |
| Cloudflare R2 | storage of module files for download | STORAGE_REGION |
| Resend | transactional emails (licence key, receipts) | 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) processes payments and calculates tax. It acts as our processor for some processing and as an independent controller for other processing (for example fraud prevention).
We may also disclose data to public authorities, such as tax authorities or courts, when the law requires it, and to our legal advisers.
We do not sell your personal data.
6. Transfers 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 with a European Commission adequacy decision, including US companies certified under the EU-US Data Privacy Framework; or
- under Standard Contractual Clauses approved by the European Commission, with additional safeguards where needed.
You can ask us for a copy of the safeguards at privacy@tellmyshop.pl. TBC: website: list the actual safeguard for each provider.
7. How long we keep data
| Data | Retention |
|---|---|
| Account | while the account exists; after deletion, only what is needed for the purposes below |
| Orders, invoices, payment records | 5 years from the end of the calendar year in which the tax payment deadline passed (Polish Tax Ordinance art. 86, Accounting Act art. 74) |
| Licence and activation records | for as long as the licence exists, then until claims are time-barred |
| Licence check logs with IP address | LICENCE_LOG_RETENTION (proposal: 12 months) |
| Setup statistics | for the life of the licence; in aggregate statistics without a link to the account |
| Server and security logs | SERVER_LOG_RETENTION (proposal: 30 days) |
| Consent to immediate delivery, withdrawal and refund records, complaints | until claims under the contract are time-barred (generally up to 6 years, end of calendar year, art. 118 Polish Civil Code) |
| Support emails | SUPPORT_RETENTION after the case is closed (proposal: 3 years) |
| Store data received in support (logs, dumps, screenshots) | deleted no later than 30 days after the case is closed, see the Data Processing Agreement |
| Newsletter | until you withdraw consent; proof of consent until claims are time-barred |
| Analytics | ANALYTICS_RETENTION |
LAWYER: confirm retention periods.
8. Is providing data required
Providing data for the account and purchase is voluntary but necessary to conclude the contract. Billing data is required by tax law. Without it we cannot sell you a licence. The newsletter is entirely optional.
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 contract or consent;
- object to processing based on our legitimate interest, and at any time to direct marketing;
- withdraw consent at any time, without affecting earlier processing;
- lodge a complaint with a supervisory authority: in Poland the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa,
uodo.gov.pl), or the authority in your country of residence or work.
Write to privacy@tellmyshop.pl. We respond within one month, which can be extended by two months for complex requests. We may ask you to confirm your identity.
10. Automated decisions
We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. Stripe may use automated fraud screening when you pay, under its own terms. The licence server automatically classifies domains as production or development under published rules (EULA, section 5); you can ask support to review a classification.
11. Cookies
11.1. Cookies are small files stored by your browser. We use:
| Type | Examples | Basis |
|---|---|---|
| Strictly necessary | login session, security token (CSRF), cookie consent choice, language; Stripe cookies on the checkout page for fraud prevention | no consent needed; necessary to provide the service you requested |
| Analytics | ANALYTICS_PROVIDER | consent, unless the tool works without cookies or similar identifiers |
| Marketing | AD_PIXELS (if used) | consent |
11.2. When you first visit the website, 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 legal basis in Poland is art. 399 of the Electronic Communications Law (Prawo komunikacji elektronicznej) implementing art. 5(3) of the ePrivacy Directive. Confirm the banner design and the list of cookies once the website is built. TBC: website: full cookie list with names, providers and lifetimes.
12. Security
We protect data with encryption in transit (HTTPS), access control and two-factor authentication on administrative accounts, hashed passwords, encrypted storage of Licence Keys, minimal access for people working with us, and regular backups. Licence Keys are stored as a hash plus an encrypted copy so that you can see your key in the account.
13. Changes
We will publish any change to this policy on this page and, if the change is significant, inform account holders by email. The date at the top shows the current version.
PrestaShop is a registered trademark of PrestaShop SA. Claude is a trademark of Anthropic. TellMyShop is not affiliated with either.