Technical Architecture, Privacy & Free Pilot

Our AI Product Finder is designed to give merchants a simple way to add AI-powered product search to their online store without requiring access to their customer database or large amounts of merchant information.

The pilot is currently free and intentionally lightweight. This page explains how the Product Finder works, what information is used, how shopper questions are handled, and how merchants can remove their data.

1. Simple Merchant Setup

Getting started with the Product Finder is designed to be straightforward.

Step 1 — Create Your Account

The Merchant creates an account on our website.

We aim to keep the information required to operate the account to a minimum. Each Merchant is associated with an internal Merchant ID.

The Merchant ID is encrypted when stored and decrypted only when required for specific system operations.

Step 2 — Provide Your Store Data

The Merchant can provide product and store information in a number of simple ways, including:

• Manually uploading or updating product data
• Providing a product feed
• Providing URLs to publicly available product information
• Providing URLs to relevant store policy or information pages

This can include product information, FAQs, shipping information, returns information, store policies, and other information that helps the Product Finder answer shopper questions.

The Merchant remains in control of the information provided to the Product Finder.

Step 3 — Add Two Lines of Code

Once the Product Finder is configured, the Merchant receives two lines of JavaScript code.

These lines are normally placed immediately before the closing </body> tag on the Merchant's website.

Once installed, visitors can use the Product Finder directly from the Merchant's storefront.

2. What Happens When a Shopper Uses the Product Finder?

Visitors can ask questions about products using natural language.

For example:

"I need a waterproof jacket for hiking in cold weather."

"Which laptop is best for video editing under €1,500?"

The Product Finder interprets the question and searches the Merchant's product information to provide relevant answers and product suggestions.

The experience is designed around Q&A and semantic product search , rather than traditional keyword-only search.

3. Visitor Questions & Email Filtering

Visitors can ask natural-language questions about the products available in the merchant's catalogue.

As a basic privacy measure, our system automatically looks for email addresses in shopper questions and replaces detected email addresses before the question is sent to our AI system or stored.

For example:

"Can you recommend a jacket? You can contact me at john@example.com."

may become: "Can you recommend a jacket? You can contact me at <EMAIL_REDACTED>."

The AI system is instructed not to reconstruct, guess, or infer information that has been removed.

Our filtering is currently focused on email addresses. It is not intended to identify or remove every possible type of personal information that a visitor might enter into a free-text question. Visitors should therefore avoid entering unnecessary personal or sensitive information.

The purpose of this approach is to minimise unnecessary personal information while keeping the shopper's product question intact and useful for product search.

4. Visitor Q&A & Data Retention

After passing through the PII-filtering layer, Q&A interactions may be temporarily stored.

This allows us to understand how the Product Finder is being used, improve search quality, identify gaps in product information, and monitor the performance of the service.

Short-Term Q&A Storage

Raw Q&A interactions are currently retained for a limited period of up to 8 days.

After this period, raw Q&A data is scheduled for deletion from our active systems.

Our intention is to keep raw shopper conversations only for as long as they are useful for operating and improving the Product Finder.

Limited Usage Information

After raw Q&A is removed, we may retain limited information derived from the interaction where it is useful for operating the Product Finder.

This may include information such as:

• Number of searches
• Number of Product Finder interactions
• Usage totals by Merchant
• Product or catalogue identifiers involved in searches
• Aggregated search statistics
• Service usage periods
• Other basic usage metrics

This information helps us understand Product Finder usage, improve the service, identify product-search trends, and potentially support future usage-based pricing or billing.

We do not need to retain the full shopper conversation to calculate basic usage statistics.

No Individual Shopper Profiles

The Product Finder is not designed to build individual shopper profiles or maintain a long-term history of what a particular visitor has searched for.

Our goal is to retain useful product and service statistics rather than long-term shopper conversations.

5. No Shopper Account Required

Shoppers do not need to create an account or provide their name, email address, or other contact details to use the Product Finder.

A technically necessary session identifier is used to maintain the shopper's conversation while using the Product Finder. This identifier is used only to keep the conversation connected to the same shopping session.

The session identifier is not used for advertising, marketing, cross-site tracking, or visitor profiling.

We do not use third-party advertising or analytics cookies in the Product Finder widget.

6. Minimal Merchant Data

We aim to keep the amount of Merchant information stored by our system as small as reasonably possible.

The core Merchant information may include:

• Account information required to operate the Merchant account
• An encrypted internal Merchant ID
• Product catalogue information
• Store and policy information provided by the Merchant
• Product Finder configuration
• Usage information required to operate and analyse the service

Merchant identifiers are encrypted when stored and decrypted only when required by the system.

We do not need access to the Merchant's customer database to operate the Product Finder.

Merchants do not need to provide customer lists, customer accounts, order histories, or payment information.

7. Your Product Data

The Product Finder needs information about your products in order to answer shopper questions.

You can provide this information manually or provide URLs to relevant pages or feeds on your store.

Examples include:

• Product catalogue data
• Product descriptions
• Product specifications
• Categories
• Pricing information
• Availability information
• Shipping information
• Returns information
• Frequently Asked Questions
• Other publicly available store information

This information is used to create and operate your Product Finder.

The Merchant remains responsible for ensuring that the information provided to the Product Finder is suitable for use.

8. Our AI Infrastructure

The Product Finder operates using our own hosted AI environment.

Merchant product data and Product Finder processing are handled within our controlled infrastructure.

We do not send your product catalogue to public AI services such as OpenAI or Anthropic to generate your Product Finder responses.

Your product catalogue is not used to train public AI models.

Our goal is to keep the Product Finder workflow as contained and controlled as possible.

9. European Hosting

The Product Finder infrastructure is hosted within the European Union.

Merchant data, product information, configuration data, and Product Finder information are maintained within the infrastructure used to operate the service.

10. Designed to Be Lightweight

The Product Finder is designed to have minimal impact on your storefront.

We provide a small two-line JavaScript integration that can normally be placed immediately before the closing </body> tag.

The widget loads asynchronously and is designed not to block your website's initial page rendering.

We aim to keep the Product Finder lightweight and independent from the rest of your storefront.

Actual website performance depends on your theme, hosting environment, third-party applications, network conditions, and other factors. Therefore, we do not guarantee a particular Lighthouse, PageSpeed, or Core Web Vitals score.

Our goal is simple:

Add useful AI search without making your store slower.

11. Free Pilot

The Product Finder is currently available as a free pilot.

There is:

• No setup fee
• No subscription required
• No long-term commitment
• No requirement to continue using the service

The purpose of the pilot is to allow merchants to use the Product Finder on real stores while we continue developing and improving the product.

Because this is an early-stage product, features and functionality may change over time.

12. Provided As-Is

The free pilot is provided "as-is" and "as-available."

We aim to provide useful and reliable product search, but we cannot guarantee:

• 100% uptime
• Perfect search results
• Perfect AI-generated answers
• A specific conversion rate
• A specific increase in sales
• A particular PageSpeed or Lighthouse score
• Compatibility with every website, theme, browser, or third-party application

AI-generated answers may occasionally be incomplete, unexpected, or incorrect.

Merchants should continue to maintain their normal product information, store policies, and customer-support processes.

13. No Customer Database Required

The Product Finder does not require access to your customer database.

You do not need to provide:

• Customer names
• Customer email lists
• Customer addresses
• Customer order histories
• Customer account information
• Payment information

The Product Finder works from your product and store information.

This is an important part of our approach to keeping the integration simple.

14. Account Deletion

You are always in control of your account.

If you decide to stop using the Product Finder, you do not need to contact us.

Simply:

1. Log in to your account.
2. Select Delete Account.
3. Confirm the deletion.

Once confirmed, the account and associated Merchant data will be deleted from our active systems.

This includes Merchant-specific information such as:

• Merchant account information
• Product catalogue data
• Product Finder configuration
• Store information
• API credentials
• Other Merchant-specific data held by the Product Finder

The Product Finder integration will no longer operate for the account.

The Merchant should then remove the two-line Product Finder widget from its website.

Some limited technical information may remain temporarily in system backups or security records where necessary for normal system operation. Such information is not intended to remain part of the active Product Finder service.

15. No Lock-In

There is no lock-in during the free pilot.

You can stop using the Product Finder whenever you want.

If you delete your account, your Merchant data is removed from the active Product Finder environment and the associated service is disabled.

If we eventually introduce a paid version of the Product Finder, any new pricing or commercial terms will be presented separately.

16. Keeping the Pilot Simple

The free pilot is designed to be standardised so that we can focus on building and improving the product.

The standard pilot does not include:

• Custom enterprise integrations
• Custom security assessments
• Bespoke technical questionnaires
• Custom reporting systems
• Dedicated enterprise support arrangements
• Individually negotiated technical configurations

As the product develops and merchant demand grows, we may introduce additional options for businesses that need more advanced capabilities.

17. Confidentiality

We treat non-public information shared with us during the pilot as confidential.

This can include:

• Private technical configurations
• API credentials
• Product-feed configurations
• Non-public performance information
• Private discussions about the Product Finder

We expect both parties to use reasonable care when handling information that is clearly private or confidential.

Neither party should knowingly publish false or misleading statements about the other's business, technology, or participation in the pilot.

18. Frequently Asked Questions

Do I need to provide my customer database?

No.

The Product Finder does not need your customer database, customer list, order history, or customer accounts.

It works from your product and store information.

What does the shopper see?

The shopper sees an AI-powered product search experience on your website.

They can ask questions in natural language and receive answers and product recommendations based on the information available in your Product Finder.

Are shopper questions stored?

Yes, for a limited period.

After passing through our PII-filtering layer, Q&A interactions may be temporarily stored so that we can analyse usage, improve search quality, and identify gaps in product information.

Raw Q&A is currently retained for up to 8 days and is then scheduled for deletion from our active systems.

We may retain limited usage statistics after that period, such as search counts, interaction totals, product identifiers, and other aggregated information that helps us operate the service and potentially support future usage-based billing.

We do not intend to maintain long-term individual shopper search histories or build individual shopper profiles.

What happens if a shopper enters an email address?

The query passes through our automated PII-filtering layer before being stored.

The system is designed to detect and remove common patterns such as email addresses and telephone numbers.

The search box should nevertheless be used for product-related questions rather than personal or sensitive information.

Is our product data sent to OpenAI or other public AI services?

No.

The Product Finder uses our own hosted AI environment.

Your product catalogue is not sent to public AI services such as OpenAI or Anthropic to generate Product Finder responses.

Do you train public AI models using our catalogue?

No.

Your product data is used to power your Product Finder. It is not used to train a public AI model.

Where is our data hosted?

The Product Finder infrastructure is hosted within the European Union.

Do you store our Merchant ID?

Yes.

An internal Merchant ID is required to connect your account, catalogue, configuration, and Product Finder environment.

The Merchant ID is encrypted when stored and decrypted only when required for system operations.

Can we delete everything?

Yes.

Log in to your account, select Delete Account, and confirm.

Your Merchant-specific data and Product Finder configuration will be deleted from our active systems.

You can then remove the two-line widget from your website.

Will the Product Finder slow down our website?

The widget is designed to load asynchronously and minimise its impact on your storefront.

Actual performance depends on the individual website and its existing applications, so we cannot guarantee a particular PageSpeed, Lighthouse, or Core Web Vitals score.

Is the pilot really free?

Yes.

The Product Finder is currently provided free of charge during the pilot.

There is no obligation to continue using it.

Can we remove it whenever we want?

Yes.

There is no lock-in. Simply log in to your account, select Delete Account, and confirm.

What happens if the Product Finder becomes a paid product?

If we introduce a paid version in the future, we will provide separate pricing and commercial terms before any paid service begins.

19. Our Approach

The Product Finder is an early-stage product and this pilot is designed to keep things simple.

Our approach is:

• Minimal merchant data.
• No customer database required.
• No public AI APIs for your catalogue.
• PII filtering before Q&A storage.
• Short-term raw Q&A retention.
• Limited usage statistics for longer-term analysis.
• EU-hosted infrastructure.
• Two lines of code.
• No lock-in.
• Self-service account deletion.

We are building the Product Finder with privacy, security, performance, and simplicity in mind from the beginning.

As the product gains traction and merchants begin asking for additional enterprise capabilities, we expect to expand the technical and commercial framework accordingly.

For now, our focus is simple:

Build a genuinely useful AI product search experience that merchants can try without cost, complexity, or lock-in.