End User Licence Agreement

1. Who this agreement is between

1.1. This End User Licence Agreement ("Agreement") is between:

• SEMownia Szymon Sanecznik, ul. Twarda 44, 00-831 Warszawa, tax ID (NIP) 6422931698, EU VAT ID PL6422931698, registered in CEIDG (Polish Central Register of Business Activity), email hello@tellmyshop.pl, phone +48 792 250 586 ("Seller", "we", "us"); and
• the person or organisation that installs, activates or uses the TellMyShop module ("Licensee", "you").

1.2. If you accept this Agreement on behalf of a company or other organisation, you confirm that you are authorised to bind it.

1.3. This Agreement works together with the Terms of Sale, the Privacy Policy, the Data Processing Agreement and the Refund and Support Policy. If this Agreement and the Terms of Sale conflict on the licence itself, this Agreement prevails. If they conflict on purchase, payment, withdrawal or complaints, the Terms of Sale prevail.

1.4. You accept this Agreement by ticking the acceptance box at checkout, when creating an account for the Audit edition, or by installing or activating the Module, whichever happens first.

2. Definitions

3. Grant of licence

3.1. When you have paid for a Plan in full, we grant you a non-exclusive, non-transferable (except as set out in sections 8 and 9), perpetual licence to install and use the Module on the number of Production Domains included in your Plan, plus Development Domains under section 5.

3.2. "Perpetual" means that the right to use the versions of the Module you were entitled to download does not expire with time. It ends only if this Agreement is terminated under section 17. The Updates Period is separate (section 7): when it ends, the Module keeps working on the last version you downloaded.

LAWYER: Under Polish copyright law (art. 68 of the Act on Copyright and Related Rights) a licence for an indefinite period may be terminated by the licensor with one year's notice unless the agreement provides otherwise, and a licence for more than 5 years is deemed, after 5 years, to be granted for an indefinite period. Section 17.4 excludes our right to terminate without cause. Please confirm that this achieves a "perpetual" licence, or choose a long fixed term instead.

3.3. The licence covers the following uses (fields of exploitation), only to the extent needed to use the Module as intended:

a) downloading the Module and storing copies on your devices and servers; b) installing, loading, running and displaying the Module within a PrestaShop installation on a licensed domain; c) making backup copies, as many as reasonably needed for security; d) changing the Module's configuration through its settings screen; e) adapting the Module's templates through PrestaShop's normal override mechanisms in your theme.

LAWYER: fields of exploitation listed for Polish law (art. 41 ust. 2, art. 67 ust. 1, art. 74 ust. 4 PrAut). Check completeness.

3.4. One installation of PrestaShop uses one Production Domain from your Plan. Whether one licence covers several shops of a single multistore installation is not promised at this time TBC: plugin code. Until we confirm it in writing, each shop domain in a multistore installation counts as a separate Production Domain.

3.5. All rights not expressly granted remain with the Seller. You do not acquire ownership of the Module or any intellectual property in it.

4. Free Audit edition

4.1. The Audit edition is free, has no time limit and requires an Account. It covers one Production Domain and the Module in read-only mode only: for example shop information, SEO audit, 404 report, logs, shop health and product visibility checks. It cannot save changes to your store.

4.2. Sections 3.2 to 3.5, 5 and 10 to 19 apply to the Audit edition. Section 7 (Updates and support) applies as follows: we may provide Updates to the Audit edition at our discretion; support is limited to documentation and community channels.

4.3. We may change or end the Audit edition for new users at any time. For users who already have it, we will give at least 30 days' notice by email before ending it, and the version you downloaded will continue to work in read-only mode for as long as the licence server allows activation TBC: plugin code: confirm behaviour if the Audit edition is discontinued.

LAWYER: a free edition for which the user provides personal data may still be "digital content supplied for personal data" under Directive 2019/770 art. 3(1) and chapter 5b of the Polish Consumer Rights Act. Confirm whether conformity rules apply and whether section 4.3 is acceptable for consumers.

5. Development and staging domains

5.1. You may use the Module free of charge, in addition to your Production Domains, on these Development Domains:

a) localhost, 127.0.0.1 and addresses in private IP ranges; b) domains ending in .local, .localhost, .test, .example or .invalid; c) subdomains of a licensed Production Domain starting with dev., staging., stage., test., demo., preprod. or beta. (for example staging.example.com when example.com is licensed); d) up to 3 additional domains that you register as development domains in your Account, for each licence.

5.2. Domains ending in .dev are public domains and are not automatically treated as Development Domains.

5.3. Development Domains may be used only for development, testing, staging, demonstration or training. They must not serve a live store open to the public for orders. If a Development Domain is used as a live store, it requires a Production Domain from your Plan.

5.4. We may update the list in section 5.1 on the licence server to reflect new standard development environments. We will not remove a category listed in 5.1 a) to c) for existing licences without 30 days' notice.

5.5. Claude.ai connects to your store from the internet. A staging store therefore needs a public address to work with Claude.ai. A store on your own computer works with Claude Desktop or Claude Code.

6. Founders licences

6.1. Founders licences are Shop licences (1 Production Domain) sold at a reduced price to the first 100 (100) buyers. They include lifetime Updates.

6.2. "Lifetime" means: for as long as the Seller (or its legal successor) develops and distributes the Module, and in any case for at least FOUNDERS_MIN_YEARS years from the date of purchase. It refers to the life of the product, not to the life of the Licensee.

6.3. If we stop developing and distributing the Module before that minimum period ends, we will either (a) refund the part of the price corresponding to the remaining minimum period, calculated pro rata, or (b) provide equivalent lifetime Updates for a successor product, at your choice. LAWYER: confirm this remedy, or replace it.

6.4. Founders licences include email support on the same terms as the Shop Plan for as long as lifetime Updates last.

6.5. We may ask Founders buyers for feedback or a short case study. Giving feedback is voluntary and is not a condition of the licence or of the price. If we publish any feedback, we will say that it comes from a Founders customer.

6.6. A Founders licence can be transferred under section 9 like any other licence. Lifetime Updates go with the licence.

7. Updates Period, support and renewal

7.1. Each paid Plan (except Founders, see section 6) includes 12 months of Updates and email support from the date of purchase.

7.2. During the Updates Period you can download every Update we publish. After it ends, the Module keeps working on the last version you downloaded. You cannot download newer versions until you renew.

7.3. Renewal is optional and gives another 12 months of Updates and support at the price shown on our website at the time of renewal (currently €69 for Shop, €199 for Freelancer, €499 for Agency, excluding VAT). If you renew before the current Updates Period ends, the new period starts when the current one ends. If you renew after it has ended, the new period starts on the date of payment. [Business decision to confirm: renewal after a lapse starting on the payment date.]

7.4. Section 7 does not affect a Consumer's statutory right to updates needed to keep the Module in conformity with the contract, including security updates, for the period the Consumer can reasonably expect (Directive 2019/770 art. 8(2) and chapter 5b of the Polish Consumer Rights Act). See section 15.

7.5. We will publish critical security fixes in a way that also reaches Licensees whose Updates Period has ended, at least by notifying them by email and describing a workaround where possible. [Business decision: whether critical security fixes are delivered free to all licensees. Recommended: yes.]

8. Domains, transfers and additional domains

8.1. The Licence Key is assigned to a Production Domain on first activation. The Module reads the domain from the PrestaShop configuration, not from a field you type in TBC: plugin code.

8.2. You may move a licence from one Production Domain to another by releasing the old domain in your Account and activating the Licence Key on the new one. You can do this yourself once in every 12 months for each Production Domain. Further transfers are possible through support, if you explain the reason (for example a domain change, a rebuilt store or a client leaving an agency). We will not refuse a reasonable request.

8.3. You can buy additional Production Domains for an existing licence at the price shown on our website (currently €99 excluding VAT). An additional domain shares the Updates Period of the licence it is added to.

8.4. You must not use any method to make one Production Domain slot serve several live stores at the same time, for example by rotating activations.

9. Agencies and freelancers

9.1. Freelancer and Agency Plans include a pool of Production Domains. You may install the Module on stores you build or maintain for your clients, within the number of domains in your pool.

9.2. The licence stays with you, the agency or freelancer, and not with your client. You are responsible towards us for every installation in your pool, including how your client uses it.

9.3. You may release a domain from your pool and assign it to another client store under section 8.

9.4. If a client wants to hold the licence for their own store (for example when they stop working with you), you may ask support to transfer that domain to the client. We will issue a separate Shop licence in the client's name, remove the domain from your pool, and carry over the remaining Updates Period. The pool size of your Plan then decreases by one. The client must accept this Agreement. [Business decision to confirm: whether the agency gets a slot back at a fee, or the pool simply shrinks.]

9.5. You must give your clients the information they need about the Module, in particular sections 12 to 14 (Blocks, Claude and backups), and you must not give them rights wider than those in this Agreement.

9.6. Apart from sections 6.6, 9.4 and transfers we approve in writing, you may not assign or transfer this licence. A transfer of the whole licence to a new owner of the business that uses it is allowed if you notify support and the new owner accepts this Agreement.

10. Restrictions

10.1. You must not, and must not allow anyone else to:

a) sell, rent, lend, sublicense, distribute or publish the Module or the Licence Key, except as allowed for agencies in section 9; b) remove, bypass, disable or tamper with the licence check, the Licence Key, the read-only fallback or any other technical protection in the Module; c) change the Module's code to unlock functions or domains you have not paid for; d) use the Module on more Production Domains than your Plan allows; e) remove copyright, trademark or licence notices from the Module; f) use the Module to build a competing product, or publish its code or parts of it; g) decompile, disassemble or reverse engineer the Module, except to the extent that applicable law allows this and does not allow it to be excluded by contract.

10.2. Source code is visible. The Module is written in PHP, so its source code can be read on your server. Being able to read it does not make it open source. The Module is licensed under this proprietary licence with source code visible. You may read the code to review its security, to understand how it works with your store, to make it interoperable with other software and to fix errors for your own use, within the limits of the law (in the EU: Directive 2009/24/EC art. 5 and 6; in Poland: art. 75 of the Act on Copyright and Related Rights). Section 10.1 g) does not limit these rights.

10.3. Third-party and open-source components. The Module may include components owned by third parties and licensed under their own licences (for example open-source libraries). These are listed in the LICENSES / THIRD_PARTY_NOTICES file in the Module package: THIRD_PARTY_COMPONENTS_LIST. Those licences govern those components, and nothing in this Agreement restricts the rights they give you. [Option, if we decide to release parts of the Module as open source: "The following parts of the Module are licensed under OPEN_SOURCE_LICENCE: OPEN_SOURCE_PARTS."]

LAWYER: PrestaShop core is licensed under OSL-3.0 and many modules under AFL-3.0. Please confirm that distributing the Module under a proprietary licence is compatible with the PrestaShop licences and with the licences of any bundled libraries.

10.4. You may not use the Module in breach of law, of the terms of your Claude plan, or of the rights of third parties.

11. Licence verification

11.1. The Module checks the licence online, normally about once a day and when you activate it. It needs an outgoing HTTPS connection to LICENCE_SERVER_URL.

11.2. Each check sends only:

• the Licence Key (or the signed token derived from it);
• the domain and the shop URL;
• a random instance identifier generated when the Module is installed;
• the versions of the Module, PrestaShop and PHP.

As with any internet request, our server also receives the IP address of your server. The licence check does not send product, order or customer data from your store. TBC: plugin code: confirm the exact payload.

11.3. To confirm that a Production Domain is real, our server may make a request to a verification address of the Module on your domain TBC: plugin code. This request carries only a random one-time code.

11.4. If our licence server cannot be reached, the Module keeps working during a grace period of 14 days (currently 14) TBC: plugin code. If the licence is invalid, refunded or cannot be confirmed after the grace period, the Module switches to read-only mode (the same as the Audit edition). It never disables your store front or back office.

11.5. Details of how we process this data are in the Privacy Policy.

12. Blocks, switches and your responsibility

12.1. The Module divides its functions into Blocks, each with its own switch. After installation the whole Module is in read-only mode, so no tool can change the store until you turn read-only mode off. The Module offers two connections to Claude: a daily connection (Blocks 1 and 2) and a service connection (additionally Blocks 3 to 5), which works only from IP addresses on an allowlist.

A separate switch, independent of the Blocks, controls customers' personal data, which is masked before it is passed to Claude TBC: plugin code. Further controls: read-only mode for the whole store, acting as a separate employee with that employee's permissions, limits of 120 calls and 60 writes per hour, a limit of 20 theme file writes per hour, and a main switch that turns the Module's connection off.

12.2. You decide which Blocks and switches are enabled, and you are responsible for that decision. We recommend enabling only what you need.

12.3. Block 2 (Commerce), Block 3 (Appearance and deployments), Block 4 (Modules) and Block 5 (Service mode) carry higher risk. A wrong price, stock level or discount code can cause financial loss within minutes, and a theme change can break the look of the store. Switching off, updating or uninstalling a module can stop payments or shipping, and uninstalling deletes the module's data irreversibly. Service mode can change or delete any files and data and make the store unavailable. All of these Blocks are off by default. Turn them on only if you understand the consequences, ideally on a staging copy first. Not every change in Blocks 4 and 5 can be undone, in particular uninstalling a module, database changes made by a module update, and changes to the database structure (for example ALTER, CREATE, DROP, TRUNCATE). The preview says so before saving. Support does not cover repairing changes made in Service mode (see the Refund and Support Policy).

12.4. Every write requires your confirmation. Each tool that changes the store first returns a preview and a one-time confirmation token valid for 30 minutes. The change is saved only when the token is used. Claude is instructed to show you the preview and wait for your approval. You are responsible for reviewing each preview before approving it. Approving a change, including when you let Claude approve on your behalf or configure Claude to run tools without asking, is your decision.

12.5. Changes in Blocks 1 and 2 go through PrestaShop's own back-office logic, as if an employee clicked "Save". They are recorded in a change history and can usually be undone. Theme files are backed up before each write. A URL change is not reverted by undo; it is corrected by a new URL change with a 301 redirect. Undo cannot reverse effects outside the store, such as emails already sent, data already indexed by search engines or orders placed at a wrong price.

13. Claude and AI output

13.1. Claude is a third-party service. Claude is provided by Anthropic under your own agreement with Anthropic (for example the Anthropic consumer or commercial terms for your Claude plan). We are not a party to that agreement, do not resell Claude and are not responsible for its availability, pricing, features, terms or data handling. You need a Claude account; a free account is enough.

13.2. When Claude uses the Module, data from your store is sent to your Claude account. How Anthropic processes that data is governed by your agreement with Anthropic. See the Privacy Policy and the Data Processing Agreement and GDPR guide.

13.3. AI output can be wrong. Claude may misunderstand an instruction, invent facts, write inaccurate product information, choose the wrong product or propose a change with unintended effects. The Module shows a preview so you can check every change. You are responsible for reviewing previews, for the content published in your store (including product descriptions, claims and prices) and for its compliance with the law.

13.4. We do not guarantee any result from using Claude, such as traffic, rankings or sales.

14. Backups

14.1. Before installing the Module and before enabling Blocks 2, 3, 4 or 5, make a full backup of your store's files and database, and keep regular backups afterwards.

14.2. The Module's change history, undo and theme file backups help you reverse changes. They do not replace a full backup of your store.

15. Warranty

15.1. Consumers. If you are a Consumer, you have the statutory rights for digital content that does not conform with the contract, under Directive (EU) 2019/770 and chapter 5b of the Polish Consumer Rights Act (or the equivalent law of your country of residence where it applies). Nothing in this Agreement limits or excludes those rights. How to make a complaint is described in the Terms of Sale.

15.2. Businesses. If you are a Business, the Module is provided "as is". We will make reasonable efforts to fix reproducible errors during the Updates Period. To the extent permitted by law, all other warranties, including statutory warranty for defects (rękojmia) under the Polish Civil Code, are excluded. LAWYER: confirm exclusion of rękojmia (art. 558 Civil Code) for a licence agreement, and whether a short "fit for purpose" commitment should replace it.

15.3. We do not warrant that the Module will work with every theme, module, server configuration or PrestaShop version. Supported versions are PrestaShop 8.1 and newer, including 9, with PHP 8.1 or newer, as listed in the documentation. PrestaShop 8.0, 1.7 and older are not supported.

16. Liability

16.1. Consumers. If you are a Consumer, we are liable under the applicable law. Nothing in this section limits liability that cannot be limited towards Consumers.

16.2. Businesses. If you are a Business:

a) our total liability under or in connection with this Agreement is limited to the price you paid for the Plan (plus additional domains and renewals) in the 12 months before the event giving rise to the claim; for the Audit edition, it is limited to EUR 0 to the extent the law permits LAWYER: check enforceability of a zero cap; consider a nominal amount; b) we are not liable for lost profits, lost revenue, lost data, business interruption or indirect damage; c) we are not liable for damage resulting from enabling Blocks 2, 3 or 5, from changes you approved, from Claude's output, from Anthropic's services, from third-party modules or themes, or from missing backups.

16.3. The limits in 16.2 do not apply to damage caused intentionally (art. 473 § 2 of the Polish Civil Code), to liability for personal injury, or to other liability that cannot be limited by law.

17. Term and termination

17.1. This Agreement starts when you accept it (section 1.4) and continues for as long as you hold the licence.

17.2. You may stop using the Module and terminate this Agreement at any time by uninstalling it and, if you wish, deleting your Account. Uninstalling releases the domain. Termination by you does not give a right to a refund, except under the 30-day money-back guarantee or your statutory rights.

17.3. We may terminate this Agreement, or suspend the licence, by notice by email if you materially breach sections 8.4, 9.6 or 10 and do not stop the breach within 14 days of our notice, or immediately if the breach cannot be remedied (for example resale of Licence Keys or circumvention of the licence check).

17.4. Apart from section 17.3 and section 17.5, we waive our right to terminate the licence without cause, including the right under art. 68 of the Polish Act on Copyright and Related Rights. LAWYER: confirm.

17.5. A refund (including under the money-back guarantee or a statutory withdrawal) ends the paid licence. A chargeback suspends it while the dispute is open; if the dispute is decided against us, the licence ends. In both cases the Module falls back to read-only mode.

17.6. After termination you must stop using the paid functions of the Module. Sections 10, 13, 15, 16 and 19 survive termination.

18. Changes to this Agreement

18.1. We may change this Agreement for valid reasons: changes in law, in Anthropic's or PrestaShop's services, in the Module's functions, or to fix unclear wording. We will notify you by email and on our website at least 30 days before the change takes effect.

18.2. Changes do not reduce the rights you have already paid for (number of domains, perpetual licence, Updates Period, Founders lifetime Updates). If you do not accept a change that affects you, you may terminate this Agreement before it takes effect; if you are within the 30-day guarantee, you also get a refund.

19. Governing law and disputes

19.1. This Agreement is governed by Polish law. If you are a Consumer, this choice does not deprive you of the protection of mandatory provisions of the law of your country of residence.

19.2. Disputes with Businesses are decided by the common court competent for the Seller's registered address. Consumers may bring proceedings in the courts that have jurisdiction under the applicable law, including the courts of their country of residence.

19.3. Out-of-court dispute resolution options for Consumers are described in the Terms of Sale.

20. Language and contact

20.1. This Agreement is available in English and Polish. LAWYER: decide which version prevails. Proposal: the version in the language in which the contract was concluded.

20.2. Contact: support@tellmyshop.pl. Security issues: security@tellmyshop.pl.

---

PrestaShop is a registered trademark of PrestaShop SA. Claude is a trademark of Anthropic. TellMyShop is not affiliated with either.