Compare Terms of Service and Data Processing Agreement
Effective Date: November 16, 2026 | Last Updated: November 16, 2026
Part I — Terms of Service
1. Scope and Parties
1.1 These Terms of Service (the "Terms") govern access to and use of Compare, a hosted product-comparison service for online stores, together with its WooCommerce plugin, its Shopify app, its storefront script, and its dashboard (together, the "Service"). The Service is provided by Farsea GmbH ("Farsea," "Provider," "we," or "us") to the contracting customer ("Customer" or "Merchant"). "Shopper" means an individual who visits the Merchant's online store, whether or not the individual completes a purchase.
1.2 The Service is offered exclusively to entrepreneurs within the meaning of § 14 German Civil Code (BGB), legal entities under public law, and special funds under public law. Consumers may not contract for the Service.
1.3 These Terms, the plan selected by the Merchant, and the Data Processing Agreement in Part II form the "Agreement." If provisions conflict, the following order of precedence applies: (a) an individually negotiated and signed agreement; (b) Part II for data-protection matters; (c) the remaining provisions of these Terms; and (d) the service description shown in the dashboard, the plugin listing, or the app listing.
1.4 Customer terms do not apply unless Farsea expressly accepts them in text form.
2. The Service
2.1 Service description
Compare adds a Compare button to the product cards of the Merchant's store and, where the Merchant enables it, to product pages. When a Shopper picks two products, a popup shows a side-by-side comparison of the two products generated by artificial intelligence from the Merchant's product data, with add-to-cart buttons for both products. A hosted dashboard lets the Merchant set where the buttons appear and how they look, shows which products are compared, and lists the orders that followed a comparison.
2.2 Supported platforms and components
The Service is available for WooCommerce, through the Compare plugin, and for Shopify, through the Compare app and its theme app extension. On both platforms a storefront script loaded in the Shopper's browser draws the buttons and the popup and communicates with the Compare API. The plugin and the app are connectors to the hosted Service and do not work without it. Farsea may add or discontinue platform support in accordance with Section 12.
2.3 Platform dependencies
The Service depends on the Merchant's eCommerce platform, theme, product catalogue, and third-party services. To build a comparison, the Service reads the two products from the Merchant's store: on WooCommerce through the store's public WooCommerce Store API, and on Shopify through the Shopify Admin API with the read permissions the Merchant granted on installation. Farsea is not responsible for failures caused by a platform provider, revoked permissions, a store that cannot be reached, Merchant modifications, unsupported themes or customisations, or third-party changes outside Farsea's reasonable control.
2.4 AI and infrastructure providers
The Service runs on Cloudflare (Workers, D1 database, KV storage, and R2 object storage). Comparisons are generated through the OpenAI API. A generation request contains the titles, identifiers, descriptions, and product attributes of the compared products and the language of the comparison. Where a Shopper types their own criterion, the request contains that text and the same product data. It contains no other Shopper data. Requests are sent with OpenAI's response storage switched off. Farsea may change a provider where reasonably necessary to maintain, secure, or improve the Service, subject to Section 12 and the subprocessor requirements in the DPA.
2.5 AI limitations
Comparisons are generated automatically from the product information in the Merchant's store. AI outputs are probabilistic and may be incomplete, inaccurate, or unsuitable for a particular decision, including the recommendation of one product over the other. The Service does not guarantee that a comparison is error-free, current, or legally compliant. A generated comparison is stored and shown again for the same pair of products until the product data of either product changes. The Merchant remains responsible for the product information it publishes and must keep that information accurate and complete.
2.6 Availability
Farsea provides the Service with reasonable care but does not guarantee a particular availability. Availability may be affected by announced or emergency maintenance, failures caused by the Merchant or third parties, force majeure, internet or platform outages, and suspension permitted under this Agreement.
2.7 AI Act roles
For Regulation (EU) 2024/1689 (the "AI Act"), Farsea is the provider of the AI system underlying the Service and the Merchant is the deployer. The comparison popup states that the comparison was generated by AI, and the Merchant may not remove or obscure that statement. Farsea will make available the information a deployer reasonably requires.
2.8 Terminal equipment and browser storage
The storefront script stores information in, and reads information from, the local storage of the Shopper's browser, as listed in Annex 4. It sets no cookies. Where § 25 TDDDG, Article 5(3) of Directive 2002/58/EC, or an equivalent national implementation applies, the Merchant is responsible for assessing each entry in Annex 4 and for obtaining any consent that is required before the storefront script is loaded. The Service does not collect consent itself.
3. Contract Formation, Accounts, and Connecting a Store
3.1 The Agreement is concluded when the Merchant connects a store to the Service. No separate user account, password, or API key is created: the connected store is the account.
3.2 WooCommerce. The store connects when the Merchant clicks Connect or Reconnect in the Compare plugin. The plugin sends the store address and the site's administration email address to the Compare API, the API calls the store back to confirm that the request came from that store, and the store receives a public key and a secret that the plugin keeps in the store's database. The store must be publicly reachable over HTTPS; a store on a local or private network, or behind a password, cannot connect. The Merchant opens the dashboard from the WordPress administration area through a signed link.
3.3 Shopify. The store connects when the Merchant installs the Compare app from the Shopify App Store and opens it. The dashboard runs inside the Shopify administration area. The Merchant switches the storefront script on through the app embed in the theme editor. Shopify's own terms apply to the installation and to the Merchant's use of Shopify.
3.4 The Merchant is responsible for everyone who can reach the dashboard through its WordPress or Shopify administration accounts, and must protect those accounts and the store secret against unauthorised access.
4. Merchant Responsibilities and Acceptable Use
4.1 Source information
The Merchant is responsible for the legality, completeness, accuracy, and currency of the product titles, descriptions, attributes, prices, availability, images, warnings, and other content that the Service reads from its store.
4.2 Seller relationship
The Merchant, not Farsea, is the seller of record and the contractual counterparty of its Shoppers. The Merchant is responsible for products, fulfilment, taxes, product safety, consumer information, warranties, returns, refunds, and decisions Shoppers make on the basis of a comparison.
4.3 Privacy and instructions
The Merchant is responsible for an appropriate legal basis, Shopper notices, consent where required, and lawful instructions for its use of the Service. The Merchant must describe the Service in its own privacy notice to the extent required by law. The Merchant must not instruct Farsea to process data in violation of applicable law or the DPA.
4.4 Prohibited use
The Merchant must not, and must not permit others to:
- use the Service for unlawful, fraudulent, deceptive, discriminatory, or harmful activity;
- offer illegal goods or use the Service in a manner that infringes third-party rights;
- place personal data, payment data, or other confidential information in product content, button texts, or custom styles supplied to the Service;
- bypass security or usage limits, access another customer's data, introduce malicious code, overload the Service, or probe for vulnerabilities without written authorisation;
- connect a store the Merchant does not operate or is not authorised to connect;
- reverse engineer, copy, resell, or create derivative works from the hosted Service except where mandatory law or an open-source licence permits; or
- remove the statement that a comparison was generated by AI.
4.5 Minors and regulated products
The Merchant is responsible for ensuring that its store and its use of the Service comply with applicable age restrictions, product-safety rules, advertising restrictions, and other requirements concerning regulated products, including alcohol, tobacco and vaping products, medicines, weapons, and other age-restricted or legally controlled goods. Automatically generated comparisons may not be appropriate for such products. The Merchant must assess this before enabling the Service for them, and Farsea may restrict or refuse an unsupported use case.
5. Trial, Plans, Fees, and Payment
5.1 Trial
A free trial starts when a store connects for the first time. No payment details are required. The trial ends after 14 days or after 500 generated comparisons, whichever comes first. Nothing is charged when the trial ends. Unless the Merchant has subscribed to a plan, the Service then stops serving the store: the Compare buttons are no longer shown and no comparisons are generated. The connection, the settings, and the stored data are kept, and the Service resumes when a subscription becomes active. Reconnecting a store whose data is still held does not start a new trial.
5.2 Plans and usage allowance
Paid plans are monthly subscriptions. The plans, their prices, and the allowance of each plan are those shown in the dashboard and, for Shopify, in the app listing at the time of subscription. A plan's allowance is an amount of revenue from shoppers who compared per calendar month (UTC). That revenue is the total of the store's orders placed by a shopper within 7 days after that shopper opened a comparison, excluding cancelled and refunded orders, converted to US dollars at a daily reference exchange rate. It is measured by the Service and shown in the dashboard; the attribution period a Merchant sets for its reports does not change it. It records that an order followed a comparison and is not a statement that the comparison caused the order.
Each plan also includes a fair-use number of newly generated comparisons per calendar month, shown in the dashboard. A comparison shown again for the same set of products and language does not count towards it; a comparison generated again because product data changed does. A plan offered without a revenue limit is subject to fair use: Farsea may require a separate agreement where a store's revenue from shoppers who compared exceeds USD 1,000,000 in a calendar month.
When the revenue allowance or the fair-use number of comparisons of a month is reached, the Compare buttons are no longer shown until the next calendar month begins or the Merchant moves to a larger plan. Farsea sends a notice to the store's contact email address before and when the revenue allowance is reached. No charges arise beyond the plan fee.
On Shopify development stores the Service is free of charge and no plan is required. Once the store is on a paid Shopify plan, the trial and plan terms of this section apply.
5.3 Payment
Merchants on WooCommerce subscribe and pay through Stripe. The checkout and the billing portal, where the Merchant changes plan, updates payment details, and cancels, are hosted by Stripe and opened from the dashboard. Merchants on Shopify subscribe by approving a recurring application charge in Shopify; the fee is billed by Shopify on the Merchant's Shopify invoice under Shopify's billing terms. Subscription fees are payable in advance for each billing period.
A Merchant who subscribes while the trial is running is not charged for the remaining days of the trial.
5.4 Taxes
All advertised prices and fees are net amounts exclusive of VAT and any other applicable taxes unless expressly stated otherwise. The tax treatment depends on the locations and tax status of Farsea and the Merchant and on applicable law. VAT is added where legally required, or reverse-charge treatment is applied where its conditions are met. The Merchant must provide complete and accurate billing, location, and tax information at checkout.
5.5 Renewal
A subscription renews automatically for successive billing periods until it is cancelled under Section 10.2.
5.6 No partial-period refunds
Except where mandatory law requires otherwise or Farsea expressly agrees in text form, paid fees are non-refundable and no refunds or credits are given for an unused portion of a billing period or an unused allowance.
5.7 Late or failed payment
If a payment fails or a subscription becomes unpaid, the Service stops serving the store until the outstanding amount is paid. Statutory default interest and recovery costs apply to overdue amounts.
5.8 Price changes
Farsea may change prices or plan allowances for a future billing period by giving at least 30 days' notice. The Merchant may cancel under Section 10.2 before the change takes effect.
6. Intellectual Property and Data
6.1 Farsea rights
Farsea and its licensors retain all rights in the Service, software, interface, documentation, prompts, models, configurations, and improvements, excluding Customer Data. The Merchant receives a limited, non-exclusive, non-transferable, non-sublicensable right to use the Service for its connected store during the Agreement. Software that Farsea distributes under an open-source licence, such as the WooCommerce plugin, is governed by that licence.
6.2 Customer Data
"Customer Data" means information, content, and personal data that the Service reads from the Merchant's store under its instructions, that the Merchant enters in the dashboard, or that is generated from its Shoppers' use of the Service, including the comparisons generated for the Merchant's products. As between the parties, the Merchant retains its rights in Customer Data. Personal data is not property, and this clause does not limit data-subject rights.
6.3 Processing permission
The Merchant instructs and authorises Farsea to host, copy, transmit, analyse, display, and otherwise process Customer Data only as necessary to provide, secure, support, and maintain the Service and as further described in the DPA.
6.4 No model training
Farsea does not use Customer Data to train machine-learning models.
7. Data Protection and Confidentiality
7.1 Compliance
Each party must comply with applicable data-protection law. For Customer Personal Data processed by Farsea on the Merchant's behalf, the DPA in Part II applies and is incorporated into the Agreement.
7.2 Privacy Policy
The Compare Privacy Policy explains processing for which Farsea is a controller and provides information about Farsea's processing on behalf of Merchants.
7.3 Confidentiality
Each party must protect the other party's non-public business, technical, security, and commercial information, use it only for the Agreement, and disclose it only to personnel and providers who need it and are bound by confidentiality. This does not cover information that is public without breach, already lawfully known, independently developed, or lawfully received from a third party.
8. Warranties, Defects, and Liability
8.1 Service warranty
Farsea will provide the Service with reasonable care and skill and materially in accordance with the applicable service description. The Merchant must report reproducible defects promptly and provide reasonable information needed to investigate.
8.2 Unlimited liability
Nothing in this Agreement excludes or limits Farsea's liability for intent, gross negligence, injury to life, body or health, fraudulent concealment, an expressly assumed guarantee, or any liability that cannot lawfully be excluded or limited.
8.3 Limited liability
For slight negligence, Farsea is liable only for breach of a material contractual obligation whose performance is necessary for the Agreement and on which the Merchant may reasonably rely. Liability is limited to foreseeable damage typical for this type of Agreement. To the extent legally permitted, Farsea's total liability under this Section 8.3 for all events occurring in a contract year is capped at the fees paid or payable by the Merchant under the Agreement during the 12 months preceding the first event giving rise to liability in that contract year. If that event occurs during the first 12 months of the subscription, the cap is the fees paid or payable for the first 12 months of the subscription. Claims arising from the same or related events count as one claim. This cap does not apply to Section 8.2.
8.4 Strict liability exclusion
Strict liability for defects existing when the Service was made available under § 536a(1), first alternative, BGB is excluded, except where Section 8.2 applies.
8.5 Excluded liability
Subject to Sections 8.2–8.4, Farsea is not responsible for inaccurate Merchant product information, Merchant instructions, unsupported modifications, eCommerce-platform failures, or a Shopper's purchasing decision based on a generated comparison. This does not exclude Farsea's liability for its own breach of duty.
8.6 Extension to representatives
The limitations in this Section also apply to Farsea's legal representatives, employees, and agents.
9. Third-Party Claims
9.1 Merchant indemnity
The Merchant will indemnify Farsea against a third-party claim to the extent it results from unlawful Customer Data, illegal or defective products, inaccurate product information or warnings, the Merchant's material breach of Sections 4 or 7, or an instruction that infringes law or third-party rights.
9.2 Indemnity procedure
Farsea must notify the Merchant promptly, permit the Merchant to control the defence and settlement, and provide reasonable cooperation at the Merchant's cost. The Merchant may not settle a claim in a manner that admits fault by Farsea, imposes non-monetary obligations on Farsea, or fails to release Farsea without Farsea's prior consent. The indemnity does not apply to the extent Farsea caused the claim through its own breach or unlawful conduct.
10. Term, Cancellation, Suspension, and Termination
10.1 Term
The Agreement begins when the store connects and runs for an indefinite period. Trial, billing, and renewal periods are governed by Section 5.
10.2 Cancelling a subscription
WooCommerce. The Merchant cancels in the Stripe billing portal opened from the dashboard. The cancellation takes effect at the end of the paid billing period; the Service continues until then and stops serving the store once Stripe reports the subscription as cancelled. Deleting the plugin stops the Service for the store at once and cancels a running subscription immediately; fees already paid for the current billing period are not refunded. Deactivating the plugin or clicking Disconnect stops the Service for the store at once but does not cancel a running subscription, so that the store can be switched back on; the Merchant must cancel the subscription in the billing portal, or ask Farsea in text form to cancel it.
Shopify. The Merchant cancels by uninstalling the Compare app. Shopify then ends the subscription, and the Service stops serving the store when the app is uninstalled.
A cancelled subscription can be replaced by a new one at any time while the store is connected.
10.3 Termination for cause
Either party may terminate for good cause without notice. Where the cause is remediable, termination normally requires a warning in text form and a reasonable cure period. Good cause may include a serious or repeated security breach, unlawful use, material uncured breach, or insolvency-related grounds to the extent permitted by law.
10.4 Suspension
Farsea may suspend the Service for a store to address a material security risk, unlawful use, a binding legal requirement, abuse of usage limits, or overdue fees. Where feasible, Farsea will give advance notice and limit suspension to what is reasonably necessary.
10.5 Deletion and return of Customer Data
Shopify. When the app is uninstalled, the stored Shopify access credentials are deleted at once. Shopify then sends a shop-erasure request, ordinarily 48 hours after the uninstall, and on receipt Farsea deletes all data held for the store: settings, generated comparisons, product display data, Shopper events, order records, usage counters, and the store record itself.
WooCommerce. When the store disconnects, the Service stops and dashboard sessions are revoked. The stored data is kept so that the store can reconnect with its earlier settings and history. Farsea deletes all data held for the store when the Merchant requests deletion in text form at the contact address in Section 13.
On request made before deletion, Farsea will provide the Merchant with the Customer Data it holds in a structured, commonly used, machine-readable format. Data that Union or Member State law requires Farsea to retain is isolated, used only for that legal purpose, and deleted when the requirement ends. Residual copies in database recovery history are overwritten according to the provider's recovery cycle and are not used for another purpose. The DPA supplements this Section.
10.6 Switching and data export
Where Chapter VI of Regulation (EU) 2023/2854 (the "EU Data Act") applies, the Merchant may request an export of its exportable data for transfer to another provider, or its erasure. Farsea will provide the export in a structured, commonly used, machine-readable format and the assistance required by mandatory law. An export does not include Farsea or third-party source code, models, prompts, trade secrets, or security-sensitive information, except to the extent mandatory law requires.
11. Force Majeure
Neither party is liable for delay or failure caused by events beyond its reasonable control, including widespread internet or cloud outages, failures of eCommerce platforms or AI providers, natural disasters, war, labour disputes, epidemics, government action, or cyberattacks that could not reasonably have been prevented. Payment obligations already accrued remain due. If the event continues for more than 90 days, either party may terminate without penalty.
12. Changes to the Service and Agreement
12.1 Service changes
Farsea may make reasonable Service changes for security, legal compliance, provider changes, technical development, or improvement, provided the core contracted functionality is not materially reduced during a paid period without an appropriate remedy.
12.2 Agreement amendments
Farsea may amend these Terms for future use or where reasonably required by law, security, or Service development. Farsea will give at least 30 days' advance notice of material adverse changes unless urgent legal or security reasons require a shorter period.
12.3 Consent and objection
Silence does not constitute acceptance unless the legal requirements for an agreed amendment mechanism are satisfied and the notice clearly explains the effect of silence and the Merchant's right to object. If a material amendment requires consent and the Merchant does not consent, either party may end the Service at the end of the current paid period. Individually negotiated terms may be changed only by agreement.
13. Final Provisions and Provider Information
13.1 Notices
Notices under the Agreement may be sent in text form, including email, unless law or an individually negotiated provision requires a stricter form. Farsea may also give notices to the Merchant in the dashboard.
13.2 Applicable law
German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. Mandatory conflict-of-law rules remain unaffected.
13.3 Jurisdiction
To the extent a jurisdiction agreement is legally permitted, Berlin is the exclusive place of jurisdiction. In all other cases, the statutory rules apply.
13.4 Severability
If part of the Agreement is invalid or unenforceable, the remaining provisions remain effective. The invalid provision is replaced by the applicable statutory rule; § 139 BGB is excluded to the extent legally permitted.
13.5 Provider
Farsea GmbH
Liselotte-Herrmann-Straße 12, 10407 Berlin, Germany
Managing Director: Bartosz Krol, Tim Kremič
Commercial Register: HRB 291598, Amtsgericht Berlin-Charlottenburg
Privacy requests: privacy@getshopassist.com
Support: support@getshopassist.com
Part II — Data Processing Agreement
1. Scope, Definitions, and Roles
1.1 This Data Processing Agreement ("DPA") applies when Farsea processes Personal Data on behalf of the Merchant in connection with the Service. It forms part of the Agreement and is intended to satisfy Article 28 GDPR.
1.2 Definitions. "Data Protection Law" means the GDPR and applicable Union or Member State laws implementing or supplementing it. The terms Controller, Processor, Data Subject, Personal Data, Personal Data Breach, Process, Processing, and Supervisory Authority have the meanings given to them in applicable Data Protection Law. "Customer Personal Data" means any Personal Data contained in or derived from Customer Data that Farsea processes on behalf of the Merchant as Processor in connection with the Service. It includes pseudonymised data and online identifiers where the information relates to an identifiable individual. It does not include Personal Data that Farsea processes as an independent Controller for contracting, billing, direct business communications, security, or legal compliance, as described in the Privacy Policy.
1.3 The Merchant is Controller and Farsea is Processor for Customer Personal Data. Each party remains independently responsible for processing for which it determines its own purposes and means.
1.4 If the Merchant acts as a Processor for another Controller, the Merchant appoints Farsea as a subprocessor and confirms that it has authority to give the instructions in this DPA. References to Controller include that other Controller where required by Article 28 GDPR.
2. Processing Details and Documented Instructions
2.1 Subject matter and duration
Farsea processes Customer Personal Data to show the Compare buttons and comparisons on the Merchant's store, to count usage, to prevent abuse, to report to the Merchant which products are compared and which orders followed a comparison, and to support and secure the Service, during the Agreement and for the deletion and recovery periods specified in Section 7 and Annex 2.
2.2 Nature and purpose
Processing may include collection, transmission, storage, retrieval, matching, aggregation, display, support access, restriction, export, and deletion. Purposes are limited to providing, securing, troubleshooting, maintaining, and supporting the Service under the Merchant's instructions.
2.3 Data Subjects
Data Subjects are Shoppers and visitors of the Merchant's store and the Merchant's authorised users who open the dashboard.
2.4 Categories of Customer Personal Data
- a random visitor identifier that the storefront script creates and keeps in the local storage of the Shopper's browser;
- usage events linked to that identifier: a product picked for comparison, a comparison opened or failed, a criterion typed into a comparison (including its text), a product link clicked in the popup, and a product added to the cart from the popup, each with the products concerned, whether it happened on a listing or a product page, the language, and the time;
- for an order placed by a Shopper who used Compare: the platform order id, the order number, the order total, the currency, the order status, the time the order was placed, and the visitor identifier, together with whether and when a comparison preceded the order;
- the language and country code of the page from which a comparison is requested; and
- IP addresses and request metadata processed by the infrastructure to deliver requests, limit request rates, and keep security and application logs.
The Service does not read or store a Shopper's name, email address, telephone number, postal address, customer account identifier, payment details, or the products contained in an order. On WooCommerce the plugin sends only orders that carry a Compare visitor identifier. On Shopify the order notifications the Service subscribes to are limited to the fields it reads, and an order without a Compare visitor identifier is not stored.
2.5 Special data
The Service is not intended to process payment-card data, passwords, government identifiers, Article 9 special-category data, or criminal-conviction data, and offers Shoppers no free-text input. The Merchant must not place such data in product content or settings.
2.6 Instructions
The Agreement, the supported configuration of the Service, and documented Merchant support requests are the Merchant's instructions. Farsea will process Customer Personal Data only on those instructions unless Union or Member State law requires otherwise, in which case Farsea will inform the Merchant before processing unless legally prohibited.
2.7 Unlawful instructions
Farsea will promptly inform the Merchant if, in its opinion, an instruction infringes the GDPR or other applicable Data Protection Law. Farsea may suspend the affected processing until the parties resolve the issue.
2.8 AI use
The AI provider receives product data and the language of the comparison only. No visitor identifier, event, order data, IP address, or other Customer Personal Data is sent to the AI provider. Farsea will not use Customer Personal Data to train machine-learning models.
3. Processor Obligations
3.1 Confidentiality and access. Farsea will ensure that persons authorised to process Customer Personal Data are bound by confidentiality and access data only as required for their role. Access is limited to authorised Farsea personnel and to the users of the relevant Merchant's dashboard.
3.2 Security. Farsea will implement and maintain appropriate technical and organisational measures under Article 32 GDPR, taking into account the state of the art, costs, nature and context of processing, and risks to Data Subjects. The measures are described in Annex 3.
3.3 Data-subject requests. Taking account of the nature of processing, Farsea will assist the Merchant through appropriate technical and organisational measures with requests under GDPR Chapter III. If Farsea receives a request relating to Customer Personal Data, it will forward it to the Merchant and will not respond substantively unless instructed or legally required. Because the Service holds no name or contact detail of a Shopper, records can be located only through the visitor identifier stored in the Shopper's browser or through an order number. Farsea may ask the Merchant for those identifiers. For Shopify stores, Farsea also acts on the customer data-request and customer-redaction notifications that Shopify sends, as described in Annex 2.
3.4 Security and compliance assistance. Taking account of the nature of processing and information available, Farsea will reasonably assist the Merchant with Articles 32–36 GDPR, including security assessments, breach notification, data-protection impact assessments, and prior consultation.
3.5 Personal Data Breach. Farsea will notify the Merchant without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data. As information becomes available, the notice will describe the nature of the breach, affected data and Data Subjects, likely consequences, measures taken or proposed, and a contact point. Farsea's notice is not an admission of fault.
3.6 Compliance information and audits. Farsea will make available information reasonably necessary to demonstrate compliance with Article 28 GDPR and allow audits, including inspections, by the Merchant or an independent auditor bound by confidentiality. Except following a material incident, a regulator request, or reasonable evidence of non-compliance, audits are limited to once per year, during business hours, on reasonable notice, and in a way that protects other customers and avoids unnecessary disruption. The parties will first use written responses and available third-party reports where these reasonably address the request. Each party bears its own costs; the Merchant bears exceptional external costs unless an audit identifies a material breach by Farsea.
3.7 Records and authorities. Farsea will maintain records required of it under Article 30(2) GDPR and cooperate with competent Supervisory Authorities as required by law.
4. Merchant Obligations
4.1 Legal compliance
The Merchant is responsible for the lawfulness, fairness, and transparency of its processing; an appropriate Article 6 legal basis; the information it gives Shoppers; and any consent required under § 25 TDDDG or an equivalent implementation of Article 5(3) of Directive 2002/58/EC for the entries listed in Annex 4, obtained before the storefront script is loaded.
4.2 Appropriateness assessment
The Merchant must assess whether the Service is appropriate for its store, products, audience, and use case, including access by minors and regulated products.
4.3 Security measures
The Merchant must use reasonable security, limit access to its store administration, protect the store secret and platform credentials, and promptly notify Farsea of suspected unauthorised access or unlawful instructions.
5. Subprocessors
5.1 General authorisation
The Merchant generally authorises Farsea to appoint the subprocessors listed in Annex 1 to process Customer Personal Data for the specified purposes.
5.2 Changes
Farsea will give advance notice of an intended addition or replacement of a subprocessor. The Merchant may object within 14 days on reasonable data-protection grounds. The parties will work in good faith on a commercially reasonable solution. If none is available, either party may terminate the Service without penalty and Farsea will refund prepaid fees for the unused period.
5.3 Subprocessor obligations and responsibility
Farsea will engage each subprocessor under a written contract or other binding legal arrangement that imposes the same data-protection obligations as this DPA insofar as they apply to the subprocessor's services. Where a subprocessor fails to fulfil its data-protection obligations, Farsea remains responsible to the Merchant as required by Article 28(4) GDPR.
5.4 Platform roles
WooCommerce, WordPress, and Shopify are not Farsea subprocessors merely because the Service integrates with them. They process store data under the Merchant's own relationship with them, including the visitor identifier that the Service writes to the Merchant's cart and order records.
6. International Transfers
6.1 To the extent applicable Data Protection Law restricts international transfers, Farsea will not transfer Customer Personal Data to, store it in, or make it remotely accessible from a country outside the European Economic Area unless the transfer complies with Chapter V GDPR. Farsea may use an applicable adequacy decision, the EU-US Data Privacy Framework where the recipient and processing are covered, the European Commission's Standard Contractual Clauses, or another lawful transfer mechanism.
6.2 Farsea will ensure that international transfers to or through its subprocessors are covered by an appropriate transfer mechanism and any supplementary measures required by applicable Data Protection Law.
6.3 If the Standard Contractual Clauses are required for a transfer from the Merchant to Farsea, the 2021 controller-to-processor module applies, or the processor-to-processor module where the Merchant is itself a processor. The docking clause applies; the optional independent-dispute-resolution clause does not. Annexes 1–3 of this DPA supply the relevant processing, subprocessor, and security information.
7. Retention, Return, and Deletion
7.1 Retention. Farsea retains Customer Personal Data for the periods specified in Annex 2. Data that Union or Member State law requires Farsea to retain is isolated, used only for that legal purpose, and deleted when the requirement ends.
7.2 Deletion at the end of the Agreement. Customer Personal Data is deleted as described in Section 10.5 of the Terms and in Annex 2. On request, Farsea will confirm in text form that deletion has been completed.
7.3 Return. On request made before deletion, Farsea will provide the Customer Personal Data it holds in a structured, commonly used, machine-readable format.
7.4 Deletion requests. Farsea will locate and delete Customer Personal Data on the Merchant's instruction using the identifiers reasonably available to it, namely the store, a visitor identifier, or an order number.
8. Liability, Precedence, and Term
8.1 Liability. Liability relating to this DPA is governed by Section 8 of the Terms, subject to mandatory Data Protection Law and Data Subjects' statutory rights.
8.2 Precedence. If this DPA conflicts with another part of the Agreement on processing Customer Personal Data, this DPA controls. The European Commission's Standard Contractual Clauses control over inconsistent contractual terms for a transfer governed by them.
8.3 Term. This DPA takes effect with the Agreement and continues while Farsea processes Customer Personal Data.
Annex 1 — Authorised Subprocessors
| Provider | Processing purpose | Customer Personal Data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the Compare API, dashboard, and storefront script (Workers); database (D1); cache and rate-limit counters (KV); file storage for the storefront script and plugin releases (R2); request logs | All categories in DPA Section 2.4 | Cloudflare's global network, including locations outside the European Economic Area |
| OpenAI OpCo, LLC | Generation of comparisons from product data | None. Receives product data and the comparison language only | United States |
Stripe processes the payments of WooCommerce Merchants, and Shopify bills Shopify Merchants, under their own payment relationships; neither receives Shopper data from the Service. WooCommerce, WordPress, and Shopify process store data under the Merchant's platform relationship. None of them is a Service subprocessor under this DPA.
Annex 2 — Retention and Deletion Schedule
1. Storage periods
| Data | Retention | Treatment at expiry |
|---|---|---|
| Events recording that a product was picked for comparison or that a criterion was typed, including the typed text | 90 days | Deleted automatically by a daily job |
| Typed criteria kept without the visitor identifier, for answering a repeated criterion from stored answers | 90 days after last use | Deleted automatically by a daily job |
| Other usage events (comparison opened or failed, product link clicked, added to cart) with the visitor identifier | While the store is connected | Deleted with the store's data, see sections 2 and 3 |
| Order records (order id, number, total, currency, status, times, visitor identifier, attribution result) | While the store is connected; on Shopify, earlier when Shopify requests redaction of the customer's orders | Deleted with the store's data, see sections 2 and 3 |
| Generated comparisons, product display data (title, handle, image address), settings, and monthly usage counters. These contain no Shopper data | While the store is connected | Deleted with the store's data, see sections 2 and 3 |
| Record of received webhook and plugin deliveries, kept to ignore repeated deliveries | 30 days | Deleted automatically by a daily job |
| Cached product data read from the store | 1 hour | Expires automatically |
| Rate-limit counters keyed by IP address | No longer than 20 minutes | Expire automatically |
| Request and application logs at the hosting provider | The provider's standard log retention period | Deleted automatically by the provider |
| Product data sent to the AI provider | Not stored by Farsea beyond the generated comparison; sent with the provider's response storage switched off. The provider may keep API inputs and outputs for a limited period for abuse monitoring under its own terms | Deleted by the provider under its terms |
2. Shopify stores
When the app is uninstalled, the Service stops for the store, the stored access credentials are deleted, and dashboard sessions are revoked. When Shopify sends its shop-erasure request, ordinarily 48 hours after the uninstall, all rows held for the store in every table and its cache entries are deleted. When Shopify sends a customer-redaction request, the order records held for the orders named in the request are deleted; the visitor identifier on the remaining usage events is then no longer linked to any order. When Shopify sends a customer data request, Farsea identifies the order records it holds for the orders named in the request and provides them to the Merchant within the period Shopify sets.
3. WooCommerce stores
When the plugin is deactivated or deleted, or the Merchant clicks Disconnect, the Service stops for the store and dashboard sessions are revoked. The data held for the store is kept so that the store can reconnect with its earlier settings and history, and is deleted when the Merchant requests deletion in text form. The visitor identifier that the plugin wrote to the store's own order records stays in the Merchant's WooCommerce database and is under the Merchant's control.
4. Recovery copies
The database provider's point-in-time recovery history may retain residual copies for up to 30 days after deletion from the active database. Recovery copies are not used for ordinary processing. If a recovery copy is restored, outstanding deletions are reapplied.
Annex 3 — Technical and Organisational Measures
Farsea maintains the following measures and may replace a measure with one that provides materially equivalent or better protection.
1. Encryption and secrets
- TLS for all traffic between browsers, stores, platforms, and the Service, with HTTP Strict Transport Security on API responses;
- store credentials (the WooCommerce shared secret and Shopify access and refresh tokens) are encrypted with AES-256-GCM before they are written to the database, with the key held as a separate secret outside the database;
- provider-managed encryption at rest for the database, cache, and file storage; and
- secrets, tokens, and signatures are kept out of application logs.
2. Authentication of requests
- a WooCommerce store is connected only after the Service has called the store back and received a cryptographic proof that the request came from that store;
- requests from the WooCommerce plugin, including order notifications and dashboard launch links, are signed with HMAC-SHA256 using the store secret and carry a timestamp that is accepted for five minutes only; repeated deliveries are ignored;
- Shopify webhooks and Stripe webhooks are accepted only with a valid signature, and Shopify dashboard requests only with a valid Shopify session token;
- WooCommerce dashboard sessions are signed, expire after 12 hours, are held in an HttpOnly cookie, and are revoked when the store secret is rotated or the store disconnects; state-changing dashboard requests from another origin are refused; and
- storefront requests are accepted only with the store's publishable key and from an origin registered for that store.
3. Tenant separation and abuse prevention
- every stored record carries the store it belongs to, and every dashboard and storefront query is scoped to the authenticated store;
- the storefront API accepts product identifiers only, never product content, validates every request against a strict schema, and limits request size;
- request-rate limits per client and per store, and a usage allowance per store; and
- addresses supplied for a store are validated before the Service calls them, to prevent requests to internal or private networks.
4. Data minimisation
- no Shopper name, contact detail, address, customer account identifier, or payment detail is read or stored;
- Shopify order notifications are restricted to the fields the Service reads, and orders without a Compare visitor identifier are not stored;
- the WooCommerce plugin sends only orders that carry a Compare visitor identifier, and only the fields listed in DPA Section 2.4;
- no Customer Personal Data is sent to the AI provider, and requests to it are sent with response storage switched off; and
- automated daily deletion of the records with a fixed period in Annex 2.
5. Organisation
- persons authorised to process Customer Personal Data are subject to confidentiality obligations;
- access to production systems is limited to authorised personnel and granted only for an operational purpose;
- a process for identifying, assessing, containing, and remediating security incidents and for notifying the Merchant under DPA Section 3.5; and
- review of these measures after a material architectural, provider, or risk change.
Annex 4 — Browser Storage Inventory
This Annex lists each entry the Service stores on, or reads from, the Shopper's terminal equipment. It supports the Merchant's obligations under § 25 TDDDG and Article 5(3) of Directive 2002/58/EC and may be reproduced in the Merchant's own cookie or storage notice. The storefront script sets no cookies.
1. Storefront (Shoppers)
| Key | Mechanism | Content and purpose | Lifetime |
|---|---|---|---|
| compare_vid_<store key> | localStorage | Random visitor identifier. Sent with comparison requests and usage events; used to limit request rates and to recognise that an order followed a comparison | Until the Shopper clears the browser's site data |
| compare_comparePick_<store domain> | localStorage | The first product the Shopper picked for comparison (product data only), so the choice survives a page change | Until the second product is picked or the choice is undone |
| compare_wcAttribution (WooCommerce only) | localStorage | The visitor identifier, how the Shopper reached the cart (popup or product link), and a timestamp, so the identifier can be attached to the Shopper's cart | Ignored after the Merchant's attribution window (1 to 30 days, 7 by default); removed on the order confirmation page |
| compare_wcAttributionSent (WooCommerce only) | sessionStorage | Flag that the identifier was already sent to the store in this tab | Tab session |
Where local storage is unavailable, the visitor identifier is kept in memory for the page view only.
2. Identifier passed to the store
So that an order can be matched to a comparison, the visitor identifier is passed to the Merchant's own store. Product links in the popup carry it as the query parameter cmp. On Shopify it is written to the cart as the cart attributes _compare, _compare_vid, and _compare_method, and to products added from the popup as the line-item properties _compare and _compare_vid, which Shopify keeps on the resulting order. On WooCommerce the plugin keeps it in the Shopper's WooCommerce session and writes it to the order as the order meta field _compare_vid. WooCommerce may set its own session cookie on the Merchant's domain for this purpose, as it does when a Shopper adds a product to the cart. That cookie is set by the Merchant's store, not by the Service.
3. Dashboard (Merchant users)
| Key | Mechanism | Content and purpose | Lifetime |
|---|---|---|---|
| cmp_session (WooCommerce Merchants) | Cookie, HttpOnly | Signed dashboard session for the connected store. Strictly necessary for sign-in | 12 hours |
| cmp_checklist_collapsed, cmp_check_url | localStorage | Display state of the setup checklist | Until cleared |
| cmp_checkout | sessionStorage | The plan chosen before the redirect to the payment page, to show the result on return | Tab session |
4. Exclusions
No name, contact detail, order content, or authentication secret is written to the Shopper's terminal equipment. The classification of an entry as requiring consent or not is for the Merchant to make for its store and jurisdiction and does not bind a Supervisory Authority.