Compare Privacy Policy
Effective Date: November 16, 2026 | Last Updated: November 16, 2026
1. Who We Are
Compare is a hosted product-comparison service for online stores. It adds a Compare button to the product cards of a WooCommerce or Shopify store; when a shopper picks two products, a popup shows an AI-generated side-by-side comparison with add-to-cart buttons. Merchants manage the service in a dashboard that also shows which products are compared and which orders followed a comparison.
The company responsible for the processing described in this Privacy Policy is:
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
This Privacy Policy covers the Compare service: the WooCommerce plugin, the Shopify app, the storefront script, the Compare API, and the dashboard. The website on which this page is published is covered by the website privacy policy.
2. When Farsea Is Controller and When It Is Processor
Farsea acts as an independent Controller for personal data it uses to conclude and administer the contract with a Merchant, process billing, answer inquiries, and keep the service secure.
When a shopper uses Compare on a Merchant's store, the Merchant determines why and how the shopper data is used. The Merchant is the Controller, and Farsea acts as the Merchant's Processor under the Data Processing Agreement in the Compare Terms of Service.
3. Personal Data We Process as Controller
3.1 Connected stores
Compare has no user accounts: the connected store is the account. The service does not ask for, and does not store, the name or password of a Merchant user. For each connected store we store:
- the platform (WooCommerce or Shopify), the store's address and domain, the storefront origins, and the store currency;
- a contact email address for the store: on WooCommerce the site's administration email address, on Shopify the shop's email address. We use it for service messages about the plan, such as a notice that the plan's monthly allowance is close or reached;
- connection credentials: for WooCommerce a shared secret created on connection, for Shopify the access and refresh tokens issued by Shopify. They are stored encrypted;
- the trial end date, the chosen plan, the subscription status, the end of the paid period, and the subscription and customer references of the billing provider;
- the settings made in the dashboard, usage counters, and the result of the latest check that the buttons appear on the storefront; and
- when the store connected and when the storefront script was first seen on it.
Where a store is operated by an identifiable individual, this information can be personal data. The legal bases are contract performance and pre-contractual steps under Article 6(1)(b) GDPR and our legitimate interests in administering and securing the service under Article 6(1)(f) GDPR.
3.2 Billing
Merchants on WooCommerce subscribe and pay through Stripe. The checkout and the billing portal are hosted by Stripe, which collects the billing contact, billing address, tax information, and payment details under its own terms and privacy documentation. Compare itself stores only the Stripe customer and subscription references and the subscription status. We can see billing contacts, invoices, and payment status in our Stripe account and use them for invoicing, tax, accounting, and payment support. We do not receive complete payment-card details.
Merchants on Shopify are billed by Shopify. Compare stores the Shopify subscription reference and status. Shopify provides us with the information about the charge that it makes available to app developers.
The legal bases are Article 6(1)(b) GDPR, Article 6(1)(c) GDPR for tax and accounting obligations, and Article 6(1)(f) GDPR for fraud prevention and payment security.
3.3 Support and other inquiries
When a person contacts us, we process the name and contact details they provide, the store concerned, and the content of the communication, to answer the request and to manage the business relationship. The legal bases are Article 6(1)(b) and Article 6(1)(f) GDPR.
3.4 Dashboard access and security data
When a Merchant user opens the dashboard or a store communicates with the Compare API, we process:
- for WooCommerce, a signed session cookie that identifies the connected store and expires after 12 hours; for Shopify, the session token Shopify issues to the embedded app, which is verified and not stored;
- the IP address, request time, requested address, and response information, processed by our hosting provider to deliver the request;
- short-lived request counters keyed by IP address, used to limit request rates, which expire within 20 minutes; and
- application logs containing the store identifier, the store domain, and error information. Secrets, tokens, and signatures are not logged.
We process this information to deliver, secure, and troubleshoot the service. The legal basis is Article 6(1)(f) GDPR. The dashboard uses no analytics or advertising tools.
4. Personal Data Processed for Merchants
On a store that uses Compare, we process the following data about shoppers on the Merchant's behalf.
4.1 Visitor identifier
The storefront script creates a random identifier and keeps it in the local storage of the shopper's browser. It contains no information about the person and is not derived from the device. It is sent to the Compare API with comparison requests and usage events. So that an order can be matched to a comparison, it is also passed to the Merchant's own store: it is added to product links in the popup and attached to the shopper's cart, and the store keeps it on the resulting order.
4.2 Comparison events
Together with the visitor identifier we store:
- that a product was picked for comparison;
- that a comparison of two to four products was opened, or could not be shown;
- the text of a criterion the shopper typed into a comparison (for example "battery life"), where the Merchant has switched this feature on;
- that a product link in the popup was clicked; and
- that a product was added to the cart from the popup.
Each event records the products concerned, whether it happened on a product listing or a product page, the language, and the time. The request for a comparison also carries the language and country code of the page, which are used to read the products in the right language and currency.
A typed criterion is free text. Shoppers should not enter personal information into it. The answer to a criterion is stored without the visitor identifier and reused for later comparisons of the same products, and the name the AI gives the criterion may be offered as a suggestion to other shoppers. The text as typed is not shown to other shoppers.
4.3 Orders that followed a comparison
For an order placed by a shopper who used Compare, the Merchant's store sends us, and we store:
- the order id and order number;
- the order total and currency;
- the order status (paid, pending, cancelled, or refunded);
- the time the order was placed; and
- the visitor identifier attached to the order.
From this we record whether, and when, the shopper opened a comparison within the period set by the Merchant (1 to 30 days, 7 by default) before the order. We do not receive or store the shopper's name, email address, telephone number, billing or delivery address, customer account, payment details, or the products in the order.
On WooCommerce, the plugin sends only orders that carry a Compare visitor identifier, and only the fields listed above. On Shopify, the order notifications we subscribe to are restricted to the order id, name and number, creation time, currency, totals, payment status, cancellation time, the cart attributes, and the line items; the cart attributes and line items are read only to find the visitor identifier, and an order without one is not stored.
4.4 Technical data
Requests from the shopper's browser to the Compare API reach our hosting provider with the IP address and usual request metadata. We use the IP address to limit request rates through counters that expire within minutes. We do not store the IP address with the visitor identifier, the events, or the orders.
4.5 What the Merchant sees
The dashboard shows the Merchant totals and rankings of compared products, the criteria shoppers typed most often with their counts, and a list of the orders that followed a comparison, with order number, date, and amount. It does not show visitor identifiers.
5. AI Processing
OpenAI API
Comparisons are generated through the OpenAI API. A request contains the compared products' titles, identifiers, descriptions, and product attributes, as read from the Merchant's store, and the language in which the comparison is to be written. When a shopper types their own criterion, the request contains that text together with the same product data. Apart from the typed criterion, no shopper data is sent to OpenAI: no visitor identifier, IP address, event, or order data. Requests are sent with OpenAI's response storage switched off. OpenAI may retain API inputs and outputs for a limited period for abuse monitoring under its own terms.
A generated comparison is stored and shown again to other shoppers who compare the same two products in the same language, until the product data changes. Comparisons are therefore not personalised to the shopper. We do not use Merchant or shopper data to train machine-learning models.
AI Disclosure
The comparison popup states that the comparison was generated by AI.
AI-generated comparisons may be incomplete or inaccurate. Shoppers should verify important product, safety, compatibility, and purchasing information with the Merchant.
6. Local Storage, Cookies, and Similar Technologies
The storefront script sets no cookies. It uses the browser's local storage and session storage for the following entries:
| Key | Mechanism | Content and purpose | Lifetime |
|---|---|---|---|
| compare_vid_<store key> | localStorage | Random visitor identifier (Section 4.1) | Until the shopper clears the browser's site data |
| compare_comparePick_<store domain> | localStorage | The first product picked for comparison, 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, and a timestamp, so the identifier can be attached to the cart | Ignored after the Merchant's attribution period; 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 |
On WooCommerce, the store keeps the visitor identifier in the shopper's WooCommerce session, for which WooCommerce may set its own session cookie on the Merchant's domain. On Shopify, the identifier is written to the cart attributes. In both cases the storage is done by the Merchant's store.
Browser local storage is distinct from a traditional cookie but is covered by the terminal-equipment access rules in § 25 TDDDG and Article 5(3) of Directive 2002/58/EC. Whether an entry requires consent on a particular store is determined by the Merchant, who is responsible for obtaining it. A shopper can remove the entries at any time by clearing the site data for the store in the browser.
The dashboard uses one first-party session cookie for WooCommerce Merchants (cmp_session, 12 hours), local storage for the display state of the setup checklist, and session storage for the plan chosen before a redirect to the payment page.
7. Purposes and Legal Bases for Merchant-Controlled Processing
The Merchant determines the lawful basis for shopper-data processing through Compare. Depending on the Merchant's use case, this may include legitimate interests under Article 6(1)(f) GDPR or consent under Article 6(1)(a) GDPR.
Farsea processes the data only on the Merchant's documented instructions, including the Terms, the Data Processing Agreement, the configuration of the service, and Merchant support requests, unless Union or Member State law requires otherwise. The purposes are to show the comparison the shopper asked for, to count usage, to prevent abuse, and to report to the Merchant which products are compared and which orders followed a comparison.
8. Recipients and Service Providers
8.1 Providers of the service
| Provider | Processing purpose | Data | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosting of the Compare API, dashboard, and storefront script; database, cache, file storage, and request logs | All data described in Sections 3.1, 3.4, and 4 | Cloudflare's global network, including locations outside the EU/EEA |
| OpenAI OpCo, LLC | Generation of comparisons | Product data and language only; no shopper data | United States |
8.2 Billing providers
| Provider | Processing purpose | Data | Location |
|---|---|---|---|
| Stripe | Subscription checkout, billing portal, and payments for WooCommerce Merchants | Merchant billing contact, payment details, and subscription data; no shopper data | Ireland and United States |
| Shopify | Billing of Shopify Merchants through the Shopify Billing API | Subscription data; no shopper data from Compare | Ireland, Canada, and United States |
The Merchant's eCommerce platform (WooCommerce or Shopify) also processes store, cart, and order data, including the visitor identifier attached to carts and orders, under the Merchant's own platform relationship.
Farsea does not sell or rent personal data and uses no advertising or analytics providers for Compare.
9. International Data Transfers
Our hosting provider operates a global network, and requests are handled at a location near the person making them. Some providers or their subprocessors process or may access data outside the EU/EEA, including in the United States. A lawful Chapter V GDPR mechanism may include an adequacy decision, the EU-US Data Privacy Framework for an eligible certified recipient, the European Commission's Standard Contractual Clauses, or another lawful mechanism, together with supplementary measures where required.
10. Retention
Farsea retains personal data only for as long as necessary for the purposes for which it was collected, or for a longer period required by Union or Member State law or necessary for the establishment, exercise, or defence of legal claims.
- Events that a product was picked for comparison or that a criterion was typed, including the typed text: 90 days, then deleted automatically.
- Typed criteria kept without the visitor identifier, so that a repeated criterion can be answered from stored answers: 90 days after the criterion was last used, then deleted automatically.
- Other comparison events and order records: while the store is connected, then deleted with the store's data as described below.
- Record of received webhook and plugin deliveries: 30 days, then deleted automatically.
- Request counters keyed by IP address: no longer than 20 minutes.
- Shopify stores: when the app is uninstalled, the stored access credentials are deleted at once. When Shopify sends its shop-erasure request, ordinarily 48 hours after the uninstall, all data held for the store is deleted; at the latest, it is deleted automatically 90 days after the uninstall. When Shopify requests redaction of a customer, the order records held for that customer's orders are deleted.
- WooCommerce stores: when the plugin is deactivated or deleted, or the Merchant disconnects, the service stops and the data is kept so that the store can reconnect with its earlier settings and history. It is deleted when the Merchant requests deletion, and automatically 90 days after the store was disconnected if it has not reconnected. Deleting the plugin also cancels the subscription.
- Support inquiries: ordinarily up to 12 months after the last substantive interaction, unless a longer period is required for an active relationship or legal claim.
- Invoices and accounting records: for the applicable German statutory retention period.
Residual copies in the database provider's recovery history may remain for up to 30 days after deletion. The full schedule is Annex 2 of the Data Processing Agreement.
11. Data-Subject Rights
Subject to the GDPR's conditions and exceptions, individuals may have the right to:
- access their personal data under Article 15;
- correct inaccurate data under Article 16;
- request deletion under Article 17;
- restrict processing under Article 18;
- receive portable data under Article 20;
- object to processing under Article 21; and
- withdraw consent at any time under Article 7(3), without affecting earlier processing.
To exercise these rights:
- For store, billing, or direct-contact data: contact privacy@getshopassist.com.
- For shopper data processed through a Merchant's store: contact the Merchant first because the Merchant is the Controller. Farsea will assist the Merchant.
Compare holds no name or contact detail of a shopper. Shopper records can therefore be located only through the visitor identifier stored in the shopper's browser or through an order number supplied by the Merchant.
12. Security
Measures include TLS in transit; encryption of stored store credentials with AES-256-GCM; provider-managed encryption at rest; signed and time-limited requests between the WooCommerce plugin and the service; signature verification of Shopify and Stripe webhooks; signed dashboard sessions that expire and can be revoked; acceptance of storefront requests only from the origins registered for a store; separation of each store's data; request-rate limits; and no logging of secrets, tokens, or signatures. The full list is Annex 3 of the Data Processing Agreement.
13. AI and Children
Stores that use Compare may be accessible to people under 18. Compare does not ask shoppers for their age or for any identifying information. Merchants remain responsible for determining whether their products, store, and legal basis are appropriate for minors and for implementing any legally required age, parental-authorisation, or content controls.
14. Complaints
Individuals may complain to a data protection supervisory authority. The supervisory authority responsible for Farsea in Berlin is:
Berliner Beauftragte für Datenschutz und Informationsfreiheit
Alt-Moabit 59–61
10555 Berlin, Germany
15. Changes to This Policy
We may update this Privacy Policy when the service, our providers, our processing, or our legal obligations change. We will publish the updated version with a new effective date and provide additional notice where required.
16. Contact
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