How FeedOps handles privacy, cookies, and platform data.

What we collect

FeedOps may collect information you provide directly, information created when you use our website, and information needed to provide FeedOps products and services.

We collect personal information only where it is reasonably needed for the way you interact with FeedOps, such as requesting a demo, downloading resources, joining a webinar, using the platform, or asking for support.

How we use information

We use information to operate FeedOps, respond to requests, improve our website and services, and support ecommerce teams with product feed and channel work.

• To respond to enquiries, demo requests, support requests, and account questions.
• To provide access to FeedOps tools, reports, audits, guides, webinars, and platform features.
• To maintain, secure, troubleshoot, and improve the FeedOps website and platform.
• To understand which website content and product information is useful.
• To send relevant product, service, or marketing communications where permitted.
• To meet legal, security, marketplace, platform, and compliance obligations.

Platform and marketplace data

FeedOps may process product, catalogue, feed, channel, marketplace, and diagnostic information so that we can provide feed management, product data optimisation, approval support, enrichment, reporting, and related services.

Google advertising, analytics, and Merchant Center data

Where a customer connects FeedOps to Google services, FeedOps may access, use, and store Google Ads, Google Analytics, Google Merchant Center, product feed, campaign, and reporting data needed to manage advertising, diagnose product data issues, optimise product feeds, and report on performance.

• Google data is used only for authorised FeedOps services, including campaign management, product data analysis, reporting, support, troubleshooting, and platform improvement.
• FeedOps does not sell Google user data and does not share Google user data with third-party tools, including AI models, except where required to provide the service, comply with law, enforce agreements, prevent fraud or abuse, or protect FeedOps, its customers, or others.
• Aggregated or anonymised statistics may be used to understand product performance, website behaviour, platform quality, or service trends, but these statistics do not identify an individual customer or user.
• Google advertising, analytics, conversion tracking, and similar website tools may use cookies or related technologies for measurement, diagnostics, and service improvement.

Amazon and marketplace data

Where FeedOps processes Amazon or other marketplace data, including data obtained through Amazon Marketplace Web Service (MWS), Selling Partner API (SP-API), or related marketplace APIs, we use physical, administrative, and technical safeguards designed to protect that information. Data in transit is protected using HTTPS, and sensitive information is handled with access controls and retention controls appropriate to the service being provided.

• Marketplace data is accessed only for authorised service, support, diagnostic, or operational purposes.
• Access is limited to people and systems that need it to perform the work.
• Personally identifiable information is not downloaded onto external devices.
• Suspicious activity, such as repeated failed login attempts or unusual access patterns, may be flagged and access may be revoked where needed to protect marketplace data.
• FeedOps does not intentionally retain Amazon or marketplace personal information beyond transient processing needs or the operational need for the service.
• Where Amazon data is used only for transient processing, accessed data is purged after use and FeedOps can confirm deletion where required by Amazon or applicable platform requirements.
• FeedOps does not use Amazon data for third-party AI model training and does not sell Amazon user data.
• Amazon data is not logged beyond what is necessary for security, error handling, support, audit, or compliance purposes.
• Security incidents involving marketplace data are escalated and handled through our incident response process.
• FeedOps cooperates with reasonable marketplace audit, compliance, and security review requests where required by applicable platform policies or agreements.

Meta catalogue and business access

Where a user connects Meta to FeedOps, we may request permissions needed to support product feed and catalogue workflows. These can include catalogue management permissions, business management permissions to read Business Manager names and IDs, and the email address of the person authenticating the app.

FeedOps uses this Meta access only to connect the relevant business, identify the correct catalogue or business assets, support authorised product feed work, and provide related diagnostics or support. FeedOps does not request these permissions to sell personal information or to add Meta, advertising, or analytics scripts directly to the website.

For Meta app terms and data deletion requests, see the Meta Integration Terms and Meta data deletion instructions.

When information may be shared

FeedOps does not sell personal information. We may share information where needed to operate the website, provide services, support customers, work with trusted service providers, comply with law, or protect FeedOps, our users, or others.

• With service providers that help us run hosting, forms, CRM, analytics, communication, security, support, or platform operations.
• With channel, marketplace, or platform providers where needed to connect, diagnose, optimise, or support product feeds.
• With professional advisers, regulators, courts, or law enforcement where required or appropriate.
• In connection with a business transaction, such as restructuring, merger, sale, or acquisition.

Security, retention, and deletion

FeedOps uses reasonable technical, administrative, and organisational safeguards to protect information from unauthorised access, misuse, loss, interference, disclosure, or alteration.

We keep information only for as long as needed for the purpose it was collected, to provide services, to meet legal or accounting obligations, to resolve disputes, to protect security, or to maintain business records. When information is no longer needed, we take reasonable steps to delete, de-identify, or securely dispose of it.

Your privacy rights

Depending on where you are located, you may have rights to access, correct, delete, restrict, object to, or request a copy of personal information we hold about you.

• You can ask us what personal information we hold about you.
• You can ask us to correct information you believe is inaccurate or incomplete.
• You can ask us to delete or restrict certain personal information, subject to legal and operational limits.
• You can unsubscribe from marketing communications using the unsubscribe link or by contacting us.

We will respond to privacy requests within a reasonable period and may need to verify your identity before acting on a request.

Privacy questions, answered plainly

These short answers summarise the most common privacy questions about FeedOps, cookies, analytics, and data requests.

Contact FeedOps about privacy

If you have questions about this FeedOps privacy policy, how FeedOps handles information, or a privacy request, contact us using the details below.

If you are looking for app-specific privacy and data handling terms, see:

• Amazon MFN
• BigCommerce App Terms of Service

This policy may be updated from time to time. The latest version will be published on this page.

Last updated: 16 June 2026.