CatalogPilot™

Technical Architecture & Due Diligence

For IT, Platform Support, and Agency Review

Purpose of This Document

This document explains how CatalogPilot works, what risks it deliberately avoids, and why its architecture is safe, reversible, and enterprise-grade.

It is intended for:

• Internal IT and security teams
• Platform support engineers (Lightspeed, Shopify, WooCommerce, BigCommerce)
• Third-party agencies and technical consultants
• Architecture and compliance reviewers

This document avoids marketing language.

All statements describe engineering behavior, not promotional claims.

1. What CatalogPilot Is — and Is Not

What CatalogPilot Is

CatalogPilot is an external catalog intelligence layer that:

• Reads catalog data via official, read-only platform

How is CatalogPilot different from SEO apps or optimization tools?

Most SEO tools modify content inside your platform or apply rules that directly change your pages.

CatalogPilot operates as a separate catalog intelligence layer. It enriches, structures, and validates your product data independently, then delivers that intelligence back to your storefront in real time, without altering your original catalog.

This separation is what allows CatalogPilot to be safer, more reversible, and more resilient than traditional tools.

Why does CatalogPilot take a staged, review-first approach?

CatalogPilot is designed to prioritize accuracy and control, not speed at all costs.

Every enrichment goes

Most tools generate content in isolation.

CatalogPilot treats your catalog as a living system, structured, accessible, multilingual, and continuously aligned, and delivers that intelligence back to your storefront without disrupting your workflow.

It’s not a plugin.

It’s infrastructure.

(GDPR-compliant, CCPA-ready, SaaS-appropriate)

Effective Date: January 1st. 2026

Parties:

This Data Processing Addendum (“Addendum”) forms part of the Terms & Conditions (“Agreement”) between:

AdVision eCommerce Inc., a Delaware corporation (“Processor”, “AdVision”, “we”, “us”, “our”),

and

Merchant (“Controller”, “you”, “your”).

This Addendum governs the processing of personal data relating to individuals located in the European Union (EU), European Economic Area (EEA), United Kingdom (UK), or jurisdictions with similar data-protection requirements.

1. Definitions

Terms used but not defined in this Addendum have the meaning set out in the Agreement.

1.1 “Controller” means the Merchant, determining the purposes and means of processing Personal

Effective Date: January 1st. 2026

At AdVision eCommerce Inc., we understand that merchants depend on reliable and secure systems to operate their businesses. This page describes the security practices we use to help protect CatalogPilot, merchant accounts, and the data processed within the Service.

This Security Practices page is informational only and does not create contractual obligations, warranties, or guarantees. It complements our Privacy Policy and Terms & Conditions.

1. Security Principles

We follow a framework built around four core pillars:

1. Confidentiality – preventing unauthorized access
2. Integrity – maintaining accuracy and reliability
3. Availability – ensuring systems operate as intended
4. Accountability