<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>FAQ Policies: Published Ordered Knowledge Base: : | AdVision eCommerce Support</title>
    <description>Published Ordered Knowledge Base: FAQ Policies</description>
    <generator>Helprace RSS</generator>
    <link>https://support.advision-ecommerce.com/s1-general/knowledgebase/top/c20-faq-policies?format=rss</link>
    <item>
      <title>Trust &amp; Security</title>
      <description><![CDATA[<p>Effective Date: January 1st. 2026</p>
<p>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.</p>
<p>This Security Practices page is informational only and does not create contractual obligations, warranties, or guarantees. It complements our Privacy Policy and Terms &amp; Conditions.</p>
<p>1. Security Principles</p>
<p>We follow a framework built around four core pillars:</p>
<ol>
<li>Confidentiality – preventing unauthorized access</li>
<li>Integrity – maintaining accuracy and reliability</li>
<li>Availability – ensuring systems operate as intended</li>
<li>Accountability[_cuted_]</li></ol>]]></description>
      <pubDate>Mon, 19 Jan 2026 14:46:43 +0000</pubDate>
      <link>https://support.advision-ecommerce.com/i265-trust-security</link>
      <guid>https://support.advision-ecommerce.com/i265-trust-security</guid>
      <author>Diego Cassio</author>
      <dc:creator>Diego Cassio</dc:creator>
      <content:encoded><![CDATA[<p><b>Effective Date:</b> <span style="font-weight: 400;">January 1st. 2026</span></p>
<p><span style="font-weight: 400;">At</span> <b>AdVision eCommerce Inc.</b><span style="font-weight: 400;">, 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.</span></p>
<p><span style="font-weight: 400;">This Security Practices page is</span> <b>informational only</b> <span style="font-weight: 400;">and does</span> <b>not</b> <span style="font-weight: 400;">create contractual obligations, warranties, or guarantees. It complements our Privacy Policy and Terms &amp; Conditions.</span></p>
<h1><b>1. Security Principles</b></h1>
<p><span style="font-weight: 400;">We follow a framework built around four core pillars:</span></p>
<ol>
<li style="font-weight: 400;"><b>Confidentiality</b> <span style="font-weight: 400;">– preventing unauthorized access</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><b>Integrity</b> <span style="font-weight: 400;">– maintaining accuracy and reliability</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><b>Availability</b> <span style="font-weight: 400;">– ensuring systems operate as intended</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><b>Accountability</b> <span style="font-weight: 400;">– maintaining auditable controls and responsible governance</span><span style="font-weight: 400;"><br></span></li>
</ol>
<h1><b>2. Data Security</b></h1>
<h3><b>2.1 Encryption in Transit</b></h3>
<p><span style="font-weight: 400;">Data transmitted between your browser, APIs, and our servers is protected with industry-standard encryption (HTTPS/TLS).</span></p>
<h3><b>2.2 Encryption at Rest</b></h3>
<p><span style="font-weight: 400;">Where supported by our hosting infrastructure, stored data may also be encrypted at rest.</span></p>
<h3><b>2.3 Data Isolation</b></h3>
<p><span style="font-weight: 400;">Each merchant’s environment is logically separated to prevent unauthorized access across accounts.</span></p>
<h3><b>2.4 Access Restrictions</b></h3>
<p><span style="font-weight: 400;">Only authorized personnel with a legitimate operational requirement are granted access to production systems.</span></p>
<p><span style="font-weight: 400;">Access requires:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">unique credentials</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">role-based permissions</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">authentication layers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">audit logging</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>3. Infrastructure Security</b></h1>
<h3><b>3.1 Hosting &amp; Cloud Providers</b></h3>
<p><span style="font-weight: 400;">We use reputable, industry-standard hosting providers for infrastructure. These providers maintain:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">physical datacenter security</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">environmental controls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">redundant power and networking</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">certification frameworks such as SOC 2, ISO 27001 (provider-specific)</span></li>
</ul>
<h3><b>3.2 Network Protections</b></h3>
<p><span style="font-weight: 400;">Network policies may include:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">firewalls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">IP restrictions</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">rate limiting</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">DDoS mitigation (provider-dependent)</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>3.3 Monitoring &amp; Logging</b></h3>
<p><span style="font-weight: 400;">We use monitoring tools to track key aspects of system health, including:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">uptime</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">load</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">ingestion processes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">API requests</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">unusual patterns</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Logging helps with debugging, performance analysis, and security investigations.</span></p>
<h1><b>4. Application Security</b></h1>
<h3><b>4.1 Secure Development Practices</b></h3>
<p><span style="font-weight: 400;">Our development workflows incorporate:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">code reviews</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">environment separation</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">CI/CD pipelines</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">dependency scanning</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">vulnerability patching</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">version control</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>4.2 Password &amp; Account Security</b></h3>
<p><span style="font-weight: 400;">Users are responsible for safeguarding login credentials.</span></p>
<p><span style="font-weight: 400;">We encourage:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">strong passwords</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">unique account logins</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">administrator permission control within merchant accounts</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>4.3 Session Management</b></h3>
<p><span style="font-weight: 400;">Session timeouts and authentication rules help reduce risks associated with unauthorized access.</span></p>
<h1><b>5. Third-Party Integrations &amp; Api Security</b></h1>
<h3><b>5.1 Integration Controls</b></h3>
<p><span style="font-weight: 400;">CatalogPilot integrates with platforms such as:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Lightspeed</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Shopify</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">WooCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">BigCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Ecwid</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Google Merchant Center</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Other APIs and marketplaces</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We authenticate via API keys or platform-specific authorization methods.</span></p>
<h3><b>5.2 Dependency Awareness</b></h3>
<p><span style="font-weight: 400;">Because third-party platforms control their API availability, changes, and performance, we cannot guarantee:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">uptime</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">correctness of returned data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">compatibility</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">stability of integrations</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>5.3 Restricted Access</b></h3>
<p><span style="font-weight: 400;">Merchant API credentials are stored securely and only used to perform tasks required to deliver the Service.</span></p>
<h1><b>6. Data Backups &amp; Continuity</b></h1>
<h3><b>6.1 Regular Backups</b></h3>
<p><span style="font-weight: 400;">We maintain regular backups of key system components where appropriate.</span></p>
<p><span style="font-weight: 400;">Backups help mitigate the risk of accidental data loss.</span></p>
<h3><b>6.2 Recovery &amp; Incident Handling</b></h3>
<p><span style="font-weight: 400;">In the event of:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">service interruption</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">infrastructure failure</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">catastrophic hosting event</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We may restore data from backups as reasonably possible.</span></p>
<p><span style="font-weight: 400;">However,</span> <b>we do not guarantee recovery times or data restoration</b><span style="font-weight: 400;">, and merchants should maintain independent backups of critical data.</span></p>
<h1><b>7. Incident Response</b></h1>
<h3><b>7.1 Detection &amp; Investigation</b></h3>
<p><span style="font-weight: 400;">We investigate potential security events and take steps to reduce risks.</span></p>
<h3><b>7.2 Communication</b></h3>
<p><span style="font-weight: 400;">If a data breach affects personal information, we will notify the Merchant in accordance with applicable laws.</span></p>
<h3><b>7.3 Remediation</b></h3>
<p><span style="font-weight: 400;">Post-incident steps may include:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">patching vulnerabilities</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">modifying configurations</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">infrastructure updates</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>8. Employee Access &amp; Training</b></h1>
<p><span style="font-weight: 400;">We restrict production-level access to select personnel trained in:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">operational security</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">data handling</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">privacy controls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">system maintenance</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Employees must adhere to internal confidentiality and usage policies.</span></p>
<h1><b>9. Merchant Responsibilities</b></h1>
<p><span style="font-weight: 400;">Merchants are responsible for:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">ensuring catalog accuracy</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">securing their own systems, devices, and networks</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">maintaining backup copies of their data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">controlling internal user access</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">reviewing AI-generated metadata before publishing</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">complying with third-party platform policies</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">The security of your environment affects the security of your data.</span></p>
<h1><b>10. Limitations</b></h1>
<p><span style="font-weight: 400;">While we apply industry-standard practices,</span> <b>no system is completely secure</b><span style="font-weight: 400;">.</span></p>
<p><span style="font-weight: 400;">We cannot guarantee:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">uninterrupted service</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">absolute protection</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">compatibility with all platforms</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">immunity from attacks</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">loss prevention in all scenarios</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<p><span style="font-weight: 400;">Our Terms &amp; Conditions govern all limitations of liability.</span></p>
<h1><b>11. Contact</b></h1>
<p><span style="font-weight: 400;">If you believe you have discovered a security issue or vulnerability, please notify us at:</span></p>
<p><b>info@advision-ecommerce.com</b></p>]]></content:encoded>
    </item>
    <item>
      <title>Service Availability Statement</title>
      <description><![CDATA[<p>Effective Date: January 1st. 2026</p>
<p>This Service Availability Statement (“Statement”) describes how CatalogPilot (“Service”) operated by AdVision eCommerce Inc. (“AdVision,” “we,” “us,” “our”) generally manages availability, maintenance, and updates.</p>
<p>This Statement is informational only and does not constitute a service-level agreement (SLA), warranty, or guarantee of uptime.</p>
<p>1. General Availability</p>
<p>CatalogPilot is designed to operate continuously, 24 hours a day, 7 days a week, except during planned or unplanned maintenance events.</p>
<p>While we strive to ensure high availability, we do not guarantee any specific uptime percentage.</p>
<p>2. Planned Maintenance</p>
<p>We may perform maintenance activities to:</p>
<ul>
<li>upgrade infrastructure</li>
<li>improve performance</li>
<li>deploy[_cuted_]</li></ul>]]></description>
      <pubDate>Mon, 19 Jan 2026 12:57:06 +0000</pubDate>
      <link>https://support.advision-ecommerce.com/i264-service-availability-statement</link>
      <guid>https://support.advision-ecommerce.com/i264-service-availability-statement</guid>
      <author>Diego Cassio</author>
      <dc:creator>Diego Cassio</dc:creator>
      <content:encoded><![CDATA[<p><b>Effective Date:</b> <span style="font-weight: 400;">January 1st. 2026</span></p>
<p><span style="font-weight: 400;">This Service Availability Statement (“Statement”) describes how</span> <b>CatalogPilot</b> <span style="font-weight: 400;">(“Service”) operated by</span> <b>AdVision eCommerce Inc.</b> <span style="font-weight: 400;">(“AdVision,” “we,” “us,” “our”) generally manages availability, maintenance, and updates.</span></p>
<p><span style="font-weight: 400;">This Statement is</span> <b>informational only</b> <span style="font-weight: 400;">and does</span> <b>not</b> <span style="font-weight: 400;">constitute a service-level agreement (SLA), warranty, or guarantee of uptime.</span></p>
<h1><b>1. General Availability</b></h1>
<p><span style="font-weight: 400;">CatalogPilot is designed to operate continuously, 24 hours a day, 7 days a week, except during planned or unplanned maintenance events.</span></p>
<p><span style="font-weight: 400;">While we strive to ensure high availability,</span> <b>we do not guarantee any specific uptime percentage</b><span style="font-weight: 400;">.</span></p>
<h1><b>2. Planned Maintenance</b></h1>
<p><span style="font-weight: 400;">We may perform maintenance activities to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">upgrade infrastructure</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">improve performance</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">deploy new features</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">resolve known issues</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">apply security patches</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">update integrations</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>Planned maintenance may be performed:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">with or without notice</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">during non-peak hours (when feasible)</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">outside of your local timezone</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">During maintenance, the Service may be temporarily unavailable or experience reduced performance.</span></p>
<h1><b>3. Unplanned Downtime</b></h1>
<p><span style="font-weight: 400;">Unplanned downtime may occur due to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">hosting provider issues</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">network failures</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">third-party API outages</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">data center conditions</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">software defects</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">external attacks</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">emergency patching</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<p><span style="font-weight: 400;">We respond to unplanned downtime as quickly as reasonably possible, but</span> <b>make no guarantee of response time or resolution time.</b></p>
<h1><b>4. Dependencies On Third-Party Platforms</b></h1>
<p><span style="font-weight: 400;">The Service relies on integrations with third-party platforms, including but not limited to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Shopify</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Lightspeed</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">WooCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">BigCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Ecwid</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Google Merchant Center</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Cloud infrastructure providers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">CDN providers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Payment processors</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>We are not responsible for:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">failures or outages of these services</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">API limitations</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">rate limits</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">platform policy changes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">deprecations or breaking updates</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">data being unavailable from these platforms</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Any such issues may impact Service availability or functionality.</span></p>
<h1><b>5. Performance Considerations</b></h1>
<p><span style="font-weight: 400;">Service performance may vary based on:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">data volume</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">catalog size</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">processing capacity</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">concurrent load</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">usage spikes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">network conditions</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We optimize for reliability but</span> <b>do not guarantee minimum performance metrics.</b></p>
<h1><b>6. Support Availability</b></h1>
<p><span style="font-weight: 400;">Support channels operate during the hours listed on our website or documentation.</span></p>
<p><span style="font-weight: 400;">Response times are influenced by:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">issue severity</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">staff availability</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">timezone differences</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">volume of requests</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p>Support response times are not guaranteed.</p>
<h1><b>7. Updates &amp; Deployments</b></h1>
<p><span style="font-weight: 400;">We regularly release updates that may include:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">improvements</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">new features</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">fixes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">backend changes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">infrastructure modifications</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>These updates may:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">occur without notice</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">require temporary downtime</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">modify or remove features</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Your continued use of the Service constitutes acceptance of these updates.</span></p>
<h1><b>8. Data Access During Outages</b></h1>
<p><span style="font-weight: 400;">During outages or maintenance events:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">you may lose temporary access to your CatalogPilot dashboard</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">ingestion, enrichment, and syncing may pause temporarily</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">queued processes may resume once availability returns</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<p><span style="font-weight: 400;">We do</span> <b>not</b> <span style="font-weight: 400;">guarantee access to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">historical logs</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">real-time metrics</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">processing queues</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">pending tasks</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">during unavailability events.</span></p>
<h1><b>9. Business Continuity</b></h1>
<p><span style="font-weight: 400;">We maintain operational procedures designed to promote continuity and recovery, including:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">redundant hosting components (where applicable)</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">routine backups</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">monitoring tools</span><span style="font-weight: 400;"><br></span> <span style="font-weight: 400;">incident response workflows</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">However, we do</span> <b>not</b> <span style="font-weight: 400;">guarantee continuity, disaster recovery times, RTO/RPO metrics, or failover availability.</span></p>
<h1><b>10. No SLA Or Warranty</b></h1>
<p><span style="font-weight: 400;">This Statement does</span> <b>not</b> <span style="font-weight: 400;">constitute:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">a warranty</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">a service-level agreement</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">an uptime guarantee</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">a promise of uninterrupted service</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Availability is provided</span> <b>“as-is” and “as-available”</b> <span style="font-weight: 400;">in accordance with the Terms &amp; Conditions.</span></p>
<h1><b>11. Changes To This Statement</b></h1>
<p><span style="font-weight: 400;">We may update this Statement at any time.</span></p>
<p><span style="font-weight: 400;">Updates are effective upon posting.</span></p>
<p><span style="font-weight: 400;">Continued use of the Service constitutes acceptance.</span></p>]]></content:encoded>
    </item>
    <item>
      <title>Data Processing Addendum (DPA)</title>
      <description><![CDATA[<p>(GDPR-compliant, CCPA-ready, SaaS-appropriate)</p>
<p>Effective Date: January 1st. 2026</p>
<p>Parties:</p>
<p>This Data Processing Addendum (“Addendum”) forms part of the Terms &amp; Conditions (“Agreement”) between:</p>
<p>AdVision eCommerce Inc., a Delaware corporation (“Processor”, “AdVision”, “we”, “us”, “our”),</p>
<p>and</p>
<p>Merchant (“Controller”, “you”, “your”).</p>
<p>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.</p>
<p>1. Definitions</p>
<p>Terms used but not defined in this Addendum have the meaning set out in the Agreement.</p>
<p>1.1 “Controller” means the Merchant, determining the purposes and means of processing Personal[_cuted_]</p>]]></description>
      <pubDate>Mon, 19 Jan 2026 14:46:47 +0000</pubDate>
      <link>https://support.advision-ecommerce.com/i263-data-processing-addendum-dpa</link>
      <guid>https://support.advision-ecommerce.com/i263-data-processing-addendum-dpa</guid>
      <author>Diego Cassio</author>
      <dc:creator>Diego Cassio</dc:creator>
      <content:encoded><![CDATA[<p><i><span style="font-weight: 400;">(GDPR-compliant, CCPA-ready, SaaS-appropriate)</span></i></p>
<p><b>Effective Date:</b> <span style="font-weight: 400;">January 1st. 2026</span></p>
<p><b>Parties:</b></p>
<p><span style="font-weight: 400;">This Data Processing Addendum (“Addendum”) forms part of the Terms &amp; Conditions (“Agreement”) between:</span></p>
<p><b>AdVision eCommerce Inc.</b><span style="font-weight: 400;">, a Delaware corporation (“Processor”, “AdVision”, “we”, “us”, “our”),</span></p>
<p><span style="font-weight: 400;">and</span></p>
<p><b>Merchant</b> <span style="font-weight: 400;">(“Controller”, “you”, “your”).</span></p>
<p><span style="font-weight: 400;">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.</span></p>
<h1><b>1. Definitions</b></h1>
<p><span style="font-weight: 400;">Terms used but not defined in this Addendum have the meaning set out in the Agreement.</span></p>
<p><span style="font-weight: 400;">1.1</span> <b>“Controller”</b> <span style="font-weight: 400;">means the Merchant, determining the purposes and means of processing Personal Data.</span></p>
<p><span style="font-weight: 400;">1.2</span> <b>“Processor”</b> <span style="font-weight: 400;">means AdVision, processing Personal Data on behalf of the Controller.</span></p>
<p><span style="font-weight: 400;">1.3</span> <b>“Personal Data”</b> <span style="font-weight: 400;">means any information relating to an identified or identifiable natural person.</span></p>
<p><span style="font-weight: 400;">1.4</span> <b>“Sub-processor”</b> <span style="font-weight: 400;">means any third party engaged by AdVision to process Personal Data.</span></p>
<p><span style="font-weight: 400;">1.5</span> <b>“Applicable Data Protection Laws”</b> <span style="font-weight: 400;">includes GDPR, UK GDPR, ePrivacy laws, CCPA/CPRA (to the extent applicable).</span></p>
<p><span style="font-weight: 400;">1.6</span> <b>“Services”</b> <span style="font-weight: 400;">means CatalogPilot and related applications, hosting, APIs, metadata generation, and integrations.</span></p>
<h1><b>2. Subject Matter, Duration &amp; Nature Of Processing</b></h1>
<p><span style="font-weight: 400;">2.1</span> <b>Subject Matter:</b> <span style="font-weight: 400;">The Processor will process Personal Data solely to provide the Services.</span></p>
<p><span style="font-weight: 400;">2.2</span> <b>Duration:</b> <span style="font-weight: 400;">For the duration of the Merchant’s subscription and for the retention period defined in the Privacy Policy.</span></p>
<p><span style="font-weight: 400;">2.3</span> <b>Nature &amp; Purpose:</b></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Catalog ingestion</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Metadata generation</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Product enrichment</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">API sync</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Hosting</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Logging, analytics, AI workflows</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Support services</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">2.4</span> <b>Type of Personal Data:</b></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Customer names, emails, phone numbers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Shipping and billing data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Catalog content (if it contains personal information)</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Analytics/usage logs</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">2.5</span> <b>Categories of Data Subjects:</b></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Merchant’s customers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Merchant’s staff</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">End-users of the Merchant’s website</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Merchant account holders</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>3. Merchant Responsibilities (Controller Obligations)</b></h1>
<p><span style="font-weight: 400;">Controller agrees that it:</span></p>
<p><span style="font-weight: 400;">3.1 Has a lawful basis for all Personal Data processed.</span></p>
<p><span style="font-weight: 400;">3.2 Has provided appropriate privacy notices to Data Subjects.</span></p>
<p><span style="font-weight: 400;">3.3 Will not instruct the Processor to process data in violation of law.</span></p>
<p><span style="font-weight: 400;">3.4 Is solely responsible for determining if the Services meet its legal obligations.</span></p>
<p><span style="font-weight: 400;">3.5 Is responsible for accuracy, quality, and legality of all Personal Data.</span></p>
<h1><b>4. Processor Obligations</b></h1>
<p><span style="font-weight: 400;">AdVision shall:</span></p>
<p><span style="font-weight: 400;">4.1 Process Personal Data only on documented instructions from Controller.</span></p>
<p><span style="font-weight: 400;">4.2 Maintain appropriate technical and organizational security measures.</span></p>
<p><span style="font-weight: 400;">4.3 Ensure staff with access are bound by confidentiality.</span></p>
<p><span style="font-weight: 400;">4.4 Assist with GDPR rights (access, rectification, deletion, portability).</span></p>
<p><span style="font-weight: 400;">4.5 Notify Controller of data breaches without undue delay.</span></p>
<p><span style="font-weight: 400;">4.6 Maintain logs and records to demonstrate compliance.</span></p>
<h1><b>5. Sub-Processors</b></h1>
<p><span style="font-weight: 400;">5.1 Controller authorizes AdVision to use Sub-processors necessary for providing the Service.</span></p>
<p><span style="font-weight: 400;">5.2 AdVision will ensure equivalent data-protection obligations are in place.</span></p>
<p><span style="font-weight: 400;">5.3 A current list may include:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Hosting providers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">AI processing engines</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Database/infrastructure providers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Monitoring tools</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Payment processors</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Email/SMS services</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">5.4 AdVision may update this list; continued use constitutes approval.</span></p>
<h1><b>6. International Transfers</b></h1>
<p><span style="font-weight: 400;">6.1 AdVision may transfer Personal Data internationally for service provision.</span></p>
<p><span style="font-weight: 400;">6.2 Transfers to the US or other countries rely on:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Standard Contractual Clauses (SCCs)</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Processor agreements</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Equivalent safeguards</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>7. Data Security</b></h1>
<p><span style="font-weight: 400;">AdVision will implement security measures including:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Encryption in transit</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Access controls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Role-based permissions</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Secure hosting</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Audit logging</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Incident response procedures</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">(More details in the “Security Practices” page linked from the Privacy Policy.)</span></p>
<h1><b>8. Data Breach Notification</b></h1>
<p><span style="font-weight: 400;">If AdVision becomes aware of a breach affecting Personal Data, AdVision will:</span></p>
<p><span style="font-weight: 400;">8.1 Notify the Merchant without undue delay.</span></p>
<p><span style="font-weight: 400;">8.2 Provide relevant details.</span></p>
<p><span style="font-weight: 400;">8.3 Assist in required notifications to authorities or individuals.</span></p>
<h1><b>9. Data Subject Rights</b></h1>
<p><span style="font-weight: 400;">AdVision will assist the Merchant with responding to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Access requests</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Deletion requests</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Rectification requests</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Objections and restrictions</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Portability requests</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">AdVision will not respond directly to Data Subjects unless required by law.</span></p>
<h1><b>10. Return Or Deletion Of Data</b></h1>
<p><span style="font-weight: 400;">Upon termination:</span></p>
<p><span style="font-weight: 400;">10.1 Merchant Data remains accessible for 30 days.</span></p>
<p><span style="font-weight: 400;">10.2 After 30 days, Personal Data may be deleted.</span></p>
<p><span style="font-weight: 400;">10.3 Anonymized data may be retained indefinitely.</span></p>
<h1><b>11. Audit Rights</b></h1>
<p><span style="font-weight: 400;">11.1 Controller may request information to verify compliance.</span></p>
<p><span style="font-weight: 400;">11.2 On-site audits are only permitted if required by law and with 60 days’ notice.</span></p>
<p><span style="font-weight: 400;">11.3 Merchant pays any audit-related costs.</span></p>
<h1><b>12. Liability</b></h1>
<p><span style="font-weight: 400;">Liability is governed by the Agreement.</span></p>
<p><span style="font-weight: 400;">Nothing in this Addendum expands AdVision’s liability beyond the Agreement’s limits.</span></p>
<h1><b>13. Conflict Of Terms</b></h1>
<p><span style="font-weight: 400;">If this Addendum conflicts with the Agreement, this Addendum controls solely for data-processing matters.</span></p>]]></content:encoded>
    </item>
    <item>
      <title>Cookie Policy</title>
      <description><![CDATA[<p>Effective Date: January 1st. 2026</p>
<p>This Cookie Policy explains how AdVision eCommerce Inc. (“AdVision,” “we,” “us,” “our”) uses cookies and similar tracking technologies in connection with CatalogPilot and any websites or web-based interfaces we operate (“Sites”).</p>
<p>This Cookie Policy should be read together with our Privacy Policy, which describes how we handle personal information.</p>
<p>1. What Are Cookies?</p>
<p>Cookies are small text files stored on your device when you visit a website or use a web application. Cookies allow us to:</p>
<ul>
<li>improve user experience</li>
<li>understand how visitors use our Sites</li>
<li>secure your account</li>
<li>remember preferences</li>
<li>analyze performance</li>
</ul>
<p>Cookies may be[_cuted_]</p>]]></description>
      <pubDate>Mon, 19 Jan 2026 12:57:59 +0000</pubDate>
      <link>https://support.advision-ecommerce.com/i262-cookie-policy</link>
      <guid>https://support.advision-ecommerce.com/i262-cookie-policy</guid>
      <author>Diego Cassio</author>
      <dc:creator>Diego Cassio</dc:creator>
      <content:encoded><![CDATA[<p><b>Effective Date:</b> <span style="font-weight: 400;">January 1st. 2026</span></p>
<p><span style="font-weight: 400;">This Cookie Policy explains how</span> <b>AdVision eCommerce Inc.</b> <span style="font-weight: 400;">(“AdVision,” “we,” “us,” “our”) uses cookies and similar tracking technologies in connection with</span> <b>CatalogPilot</b> <span style="font-weight: 400;">and any websites or web-based interfaces we operate (“Sites”).</span></p>
<p><span style="font-weight: 400;">This Cookie Policy should be read together with our Privacy Policy, which describes how we handle personal information.</span></p>
<h1><b>1. What Are Cookies?</b></h1>
<p><span style="font-weight: 400;">Cookies are small text files stored on your device when you visit a website or use a web application. Cookies allow us to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">improve user experience</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">understand how visitors use our Sites</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">secure your account</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">remember preferences</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">analyze performance</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Cookies may be set by us (“first-party cookies”) or by third parties (“third-party cookies”).</span></p>
<h1><b>2. Types Of Cookies We Use</b></h1>
<h3><b>2.1 Strictly Necessary Cookies</b></h3>
<p><span style="font-weight: 400;">These cookies are essential for the Sites and Service to function.</span></p>
<p><span style="font-weight: 400;">They enable:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">login and authentication</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">session management</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">security protections</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">basic navigation</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><b>These cookies cannot be disabled.</b></p>
<h3><b>2.2 Functional Cookies</b></h3>
<p><span style="font-weight: 400;">These support features such as:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">saving user preferences</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">remembering interface selections</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">customizing the dashboard experience</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">You may disable these, but parts of the Service may not function properly.</span></p>
<h3><b>2.3 Analytics &amp; Performance Cookies</b></h3>
<p><span style="font-weight: 400;">These cookies help us understand:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">which features are used</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">how users interact with the Sites</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">technical performance</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">error rates and load times</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">This may include tools such as:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">first-party analytics</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">hosting provider analytics</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">anonymized performance metrics</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We do</span> <b>not</b> <span style="font-weight: 400;">use analytics cookies to track individuals across websites.</span></p>
<h3><b>2.4 Third-Party Cookies</b></h3>
<p><span style="font-weight: 400;">Certain third-party services used by AdVision may place cookies, including:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">payment processors (e.g., Stripe)</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">hosting/CDN providers</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">operational monitoring tools</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">customer support widgets (if enabled)</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">Third-party cookies are governed by the respective providers’ policies.</span></p>
<h1><b>3. Do We Use Cookies For Advertising?</b></h1>
<p><span style="font-weight: 400;">No.</span></p>
<p><span style="font-weight: 400;">We do</span> <b>not</b> <span style="font-weight: 400;">use:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">advertising cookies</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">retargeting cookies</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">cross-site tracking cookies</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">behavioral advertising cookies</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">CatalogPilot is a B2B service and does not rely on advertising technologies.</span></p>
<h1><b>4. How Long Do Cookies Last?</b></h1>
<p><span style="font-weight: 400;">Cookies may be:</span></p>
<ul>
<li style="font-weight: 400;"><b>Session cookies:</b> <span style="font-weight: 400;">deleted when your browser closes</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><b>Persistent cookies:</b> <span style="font-weight: 400;">remain for a defined period or until deleted manually</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We use a mixture based on functional need.</span></p>
<h1><b>5. Cookie Management &amp; Your Choices</b></h1>
<p><span style="font-weight: 400;">You may control or delete cookies through:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">your browser settings</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">privacy tools or built-in browser controls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">clearing site data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">disabling cookies entirely</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">If you block necessary cookies, the Service may not function correctly.</span></p>
<h1><b>6. Similar Technologies</b></h1>
<p><span style="font-weight: 400;">We may also use:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">local storage</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">session storage</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">API tokens</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">pixel tags</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">server-generated identifiers</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">These are used for authentication, performance, and functionality.</span></p>
<h1><b>7. Changes To This Cookie Policy</b></h1>
<p><span style="font-weight: 400;">We may update this Cookie Policy periodically.</span></p>
<p><span style="font-weight: 400;">Changes are effective upon posting.</span></p>
<p><span style="font-weight: 400;">Your continued use constitutes acceptance.</span></p>
<h1><b>8. Contact</b></h1>
<p><span style="font-weight: 400;">For questions about this Cookie Policy, contact:</span></p>
<p><b>info@advision-ecommerce.com</b></p>]]></content:encoded>
    </item>
    <item>
      <title>Acceptable Use Policy (AUP)</title>
      <description><![CDATA[<p>Effective Date: January 1st. 2026</p>
<p>This Acceptable Use Policy (“AUP”) governs how Merchants and their Authorized Users (“you,” “your”) may access and use CatalogPilot, all related applications, APIs, metadata engines, services, and integrations (collectively, the “Service”) operated by AdVision eCommerce Inc. (“AdVision,” “we,” “us,” “our”).</p>
<p>By using the Service, you agree to comply with this AUP.</p>
<p>Violations may result in suspension or termination of your account without notice.</p>
<p>1. General Principle</p>
<p>The Service must only be used for lawful, legitimate business purposes.</p>
<p>You may not use it in any way that:</p>
<ul>
<li>violates laws;</li>
<li>harms individuals or businesses;</li>
<li>compromises security;</li>
<li>disrupts[_cuted_]</li></ul>]]></description>
      <pubDate>Sun, 08 Feb 2026 16:47:04 +0000</pubDate>
      <link>https://support.advision-ecommerce.com/i261-acceptable-use-policy-aup</link>
      <guid>https://support.advision-ecommerce.com/i261-acceptable-use-policy-aup</guid>
      <author>Diego Cassio</author>
      <dc:creator>Diego Cassio</dc:creator>
      <content:encoded><![CDATA[<p><b>Effective Date:</b> <span style="font-weight: 400;">January 1st. 2026</span></p>
<p><span style="font-weight: 400;">This Acceptable Use Policy (“AUP”) governs how Merchants and their Authorized Users (“you,” “your”) may access and use</span> <b>CatalogPilot</b><span style="font-weight: 400;">, all related applications, APIs, metadata engines, services, and integrations (collectively, the “Service”) operated by</span> <b>AdVision eCommerce Inc.</b> <span style="font-weight: 400;">(“AdVision,” “we,” “us,” “our”).</span></p>
<p><span style="font-weight: 400;">By using the Service, you agree to comply with this AUP.</span></p>
<p><span style="font-weight: 400;">Violations may result in suspension or termination of your account without notice.</span></p>
<h1><b>1. General Principle</b></h1>
<p><span style="font-weight: 400;">The Service must only be used for lawful, legitimate business purposes.</span></p>
<p><span style="font-weight: 400;">You may not use it in any way that:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">violates laws;</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">harms individuals or businesses;</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">compromises security;</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">disrupts service integrity;</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">abuses the platform;</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">misuses AI output or metadata.</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">AdVision reserves the right to determine, at its sole discretion, whether conduct violates this AUP.</span></p>
<h1><b>2. Prohibited Content</b></h1>
<p><span style="font-weight: 400;">You may NOT upload, process, transmit, or generate through the Service:</span></p>
<h3><b>2.1 Illegal or harmful content:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">illegal goods or services</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">controlled substances not lawfully permitted</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">content that violates export control regulations</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">malware, ransomware, spyware</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">violent or graphic images inappropriate for commerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">hateful, discriminatory, or extremist materials</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>2.2 Infringing materials:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">copyright-infringing text or images</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">stolen product images</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">pirated digital goods</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">counterfeit products</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">trademark violations</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>2.3 Fraudulent or misleading content:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">deceptive product listings</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">false advertising</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">manipulated metadata meant to game search engines</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">fake testimonials or reviews</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>2.4 Sensitive personal data:</b></h3>
<p><span style="font-weight: 400;">Unless legally required and explicitly permitted, you may NOT submit:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">government IDs</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">credit card data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">medical information</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">biometric data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">authentication secrets</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">minors’ personal data</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>3. Prohibited Conduct</b></h1>
<p><span style="font-weight: 400;">You may NOT, in connection with the Service:</span></p>
<h3><b>3.1 Interfere with integrity or security</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">attempt to bypass security controls</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">attempt to gain unauthorized access</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">probe, scan, or test systems without written consent</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">introduce malware or harmful code</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<h3><b>3.2 Abuse APIs or system resources</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">excessive or automated scraping</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">attempting DDoS or stress testing</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">overwhelming the system with unrealistic loads</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">using automated tools to artificially inflate processing volumes</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<h3><b>3.3 Reverse engineering or copying</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">reverse engineer, decompile, or disassemble the Service</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">replicate UI, metadata logic, or AI models</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">train competitive models using our outputs</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">attempt to build competing services using our intellectual property</span><span style="font-weight: 400;"><br>
<br></span></li>
</ul>
<h3><b>3.4 Platform policy evasion</b></h3>
<p><span style="font-weight: 400;">You may not use CatalogPilot to:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">circumvent restrictions imposed by Shopify, Lightspeed, WooCommerce, Ecwid, Google, or any other platform</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">exploit API limitations</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">republish restricted or banned content</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">intentionally mislead algorithms</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>4. Misuse Of AI Output</b></h1>
<p><span style="font-weight: 400;">You may NOT use AI-generated metadata, descriptions, insights, or recommendations for:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">unlawful claims or false representations</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">dangerous or harmful products</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">SEO manipulation contrary to platform rules</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">automated mass-generation of prohibited content</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">deceptive practices</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">You are responsible for</span> <b>reviewing all AI-generated content</b> <span style="font-weight: 400;">before publishing.</span></p>
<h1><b>5. Unauthorized Use Of Accounts</b></h1>
<p><span style="font-weight: 400;">You may NOT:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">share login credentials with unauthorized individuals</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">resell, sublicense, or transfer your account</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">access the Service on behalf of others without written permission</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">impersonate another person or entity</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>6. Spam &amp; Unsolicited Activity</b></h1>
<p><span style="font-weight: 400;">You may NOT use the Service for:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">unsolicited email campaigns</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">mass-messaging</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">spam metadata generation</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">AI-created “keyword stuffing”</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">black-hat SEO activities</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">scraping other merchants’ stores</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h1><b>7. Third-Party Platform Compliance</b></h1>
<p><span style="font-weight: 400;">Your use of the Service must comply with all terms, policies, and rules of the platforms you integrate with, including:</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Shopify</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Lightspeed</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">WooCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">BigCommerce</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Ecwid</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Google Merchant Center</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Social commerce channels</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Marketplace APIs</span><span style="font-weight: 400;"><br></span></li>
</ul>
<p><span style="font-weight: 400;">We are</span> <b>not responsible</b> <span style="font-weight: 400;">for any penalties, suspensions, or account actions resulting from your choices or publications.</span></p>
<h1><b>8. Enforcement &amp; Consequences</b></h1>
<p><span style="font-weight: 400;">If we determine that you violated this AUP:</span></p>
<h3><b>8.1 We may take any of the following actions:</b></h3>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">immediate account suspension</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">restricted access to certain features</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">permanent termination</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">deletion of specific data</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">refusal to onboard or reinstate</span><span style="font-weight: 400;"><br></span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">legal referral if required by law</span><span style="font-weight: 400;"><br></span></li>
</ul>
<h3><b>8.2 No refunds</b></h3>
<p><span style="font-weight: 400;">Violations resulting in suspension or termination do</span> <b>not</b> <span style="font-weight: 400;">qualify for refunds.</span></p>
<h1><b>9. Reporting Violations</b></h1>
<p><span style="font-weight: 400;">To report abuse or violations of this AUP:</span></p>
<p><b>info@advision-ecommerce.com</b></p>
<h1><b>10. Changes To This Policy</b></h1>
<p><span style="font-weight: 400;">We may update this AUP at any time. The updated version becomes effective upon posting.</span></p>
<p><span style="font-weight: 400;">Continued use constitutes acceptance.</span></p>]]></content:encoded>
    </item>
  </channel>
</rss>
