Privacy policy

Last updated July 14, 2026

What FeedWarden accesses

From Shopify, FeedWarden reads product and order data needed for monitoring: product titles, prices, stock, identifiers, URLs, and order-line data that is aggregated into 30-day revenue and units sold per product variant. From Google Merchant Center, FeedWarden reads the Merchant Center account ID, submitted product attributes, product statuses and issue details, and data-source identifiers, names, and types. FeedWarden also stores the Google OAuth refresh token required to run the scheduled scans you authorize.

FeedWarden stores the settings you choose, including alert recipients and any Slack, Discord, or generic webhook URLs you configure. Shopify supplies the session information needed to authenticate store administrators inside the embedded app.

What we do not collect

FeedWarden does not retrieve or store your customers' names, addresses, email addresses, or payment information. Order data is reduced to 30-day revenue and units sold per product variant during ingestion; customer details never leave Shopify. App billing runs through Shopify.

How Google data is used

FeedWarden uses Google Merchant Center data only to provide the monitoring features visible in the app: scheduled and manual scans, Shopify-to-Merchant-Center comparisons, product-health dashboards, mismatch detections, incidents, root-cause guidance, evidence packets, and alerts sent to destinations you configure.

From that raw data, FeedWarden creates normalized catalog snapshots, detections, incidents, evidence, health counts, and alert content for your store. FeedWarden does not create cross-merchant aggregated or anonymized datasets from Google API data.

Where data is processed and shared

FeedWarden uses service providers only to operate the user-facing features described above:

• Vercel processes application traffic and runs the FeedWarden application.
• Supabase stores application data in FeedWarden's production database.
• Resend receives alert recipients and derived alert content when you configure email alerts.
• Slack, Discord, or a generic webhook receives derived alert content only when you configure that destination.

FeedWarden does not sell Google user data or transfer it to advertisers, data brokers, lenders, or unrelated third parties. FeedWarden personnel do not inspect Google user data unless you affirmatively ask us to examine specific data for support, access is necessary to investigate a security or abuse incident, or access is required by law.

How data is protected

FeedWarden uses HTTPS/TLS for data in transit. Google OAuth refresh tokens and stored webhook URLs are encrypted by the application with AES-256-GCM. Production database access is restricted to FeedWarden's application infrastructure and authorized operators, and production credentials are kept in restricted environment configuration rather than application source code.

Retention and deletion

Current Shopify and Merchant Center catalog snapshots are replaced on each completed scan and otherwise remain while FeedWarden is installed. Scan and detection history, product-page checks, status events, alerts and delivery records, and resolved incidents are retained for 30 days on Monitor, 60 days on Protect, or 90 days on Command. Open incidents remain until they resolve or your store's data is deleted.

Disconnecting Google in FeedWarden Settings immediately removes that Shopify store's stored OAuth credential and Merchant Center account ID. It does not revoke access for another FeedWarden store connected with the same Google account. To revoke FeedWarden's access for the Google account itself, remove FeedWarden from your Google Account connections. Existing catalog snapshots and monitoring history remain under the retention rules above. Uninstalling FeedWarden deletes the store's credentials, settings, catalog snapshots, scans, detections, incidents, evidence, crawl results, alerts, and sessions. Shopify's later shop-redaction webhook repeats that deletion safely. You can request earlier deletion at any time by emailing hello@feedwarden.com.

Google API Limited Use

FeedWarden's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. This applies to raw Google data and anything derived from it. FeedWarden's production user-facing service only makes read requests for Merchant Center products, statuses, issues, and data sources and does not modify your Merchant Center account. Google's Merchant Center content scope technically permits writes because Google provides no narrower read-only scope for these Merchant API requests.

Raw or derived Google user data is not used for advertising, retargeting, lending, credit-worthiness decisions, surveillance, sale, data-broker services, or generalized or personalized AI/ML model training. It is not transferred to an AI provider for model training. You can remove a store's connection in FeedWarden Settings or revoke FeedWarden's account-wide access from your Google Account at any time.

Public website analytics

This public website uses Vercel Web Analytics to understand aggregate page use. Vercel processes privacy-preserving page-view information such as the visited page, referrer, approximate location, and general browser, operating-system, and device details. This analytics integration does not use cookies or collect data from inside the authenticated app.

Contact

Questions or deletion requests: hello@feedwarden.com.