Privacy

Effective date

This privacy policy is effective June 9, 2026. It explains how FeedRescue AI handles data for its public checker, Shopify embedded app, Google Merchant Center connection, diagnostics, monitoring, reporting, and support workflows.

Data accessed

FeedRescue may access, collect, or process the following categories of data depending on how you use it:

• Shopify store and catalog data, including shop domain, shop identifiers, product and variant identifiers, product titles, handles, status, publication state, prices, inventory and availability signals, product attributes, images, product page URLs, public storefront-visible signals, and scan/evaluation results.
• Shopify billing and app operation data, including plan status, entitlement checks, usage events, audit logs, webhook events, API call logs, job status, error state, and support context.
• Public checker data, including storefront or product URLs submitted for a scan, scan IDs, issue examples, and optional report email metadata. Public checker report emails are handled with minimization controls, including hashed report-email metadata in scan records where applicable.
• Google OAuth identity data when you connect Google Merchant Center: your connected Google account email address and email verification status through the openid and email scopes. FeedRescue uses this only to show which Google account is connected and to support account-selection and troubleshooting workflows.
• Google OAuth authorization data: granted scopes, access tokens, refresh tokens, token expiration metadata, and connection status. Tokens are stored encrypted or secrets-managed so FeedRescue can maintain the merchant-authorized Merchant Center connection.
• Google Merchant Center data through the https://www.googleapis.com/auth/content scope and Merchant API, including accessible Merchant Center account list, selected merchant account ID, account name, account type, developer/user access state, product and offer identifiers, product status and approval signals, pending or disapproved item state, product-level diagnostics, account-level diagnostics, policy issue details, data-source/feed information, product input metadata, aggregate approval counts, and import or publish status.
• Merchant-approved repair data, including fix suggestions, write destination, supplemental feed rows, app metafield payloads, Merchant Center product input records, idempotency keys, provider responses, rollback payloads, and related audit records.

FeedRescue does not request access to Gmail, Google Drive, Google Ads, YouTube, Google Workspace documents, or unrelated Google account content.

How data is used

• To authenticate Shopify shops and merchant-authorized Google Merchant Center connections.
• To sync Shopify catalog data and show real product-level issue proof before payment.
• To import Merchant Center statuses and diagnostics, compare them with Shopify catalog facts, and explain approval, pending, disapproval, account, policy, or product-level signals.
• To generate deterministic issue findings, constrained AI-assisted drafts, safe fix plans, and merchant review workflows.
• To publish or remove merchant-approved supplemental feed, Merchant Center product input, app metafield, or explicit direct catalog edits when the merchant has enabled and confirmed that workflow.
• To provide monitoring, weekly reports, alerts, support, troubleshooting, security, and abuse prevention.
• To maintain audit history, idempotency, rollback evidence, compliance records, and operational reliability.

FeedRescue does not sell Google user data, Shopify catalog data, or public checker data. FeedRescue does not use Google user data for advertising, retargeting, credit, lending, eligibility, or unrelated product profiling.

Google API limited use

FeedRescue's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide and improve user-facing Merchant Center diagnostics, monitoring, safe repair workflows, support, security, compliance, and account-management features requested by the merchant.

• Google user data is not sold, rented, or transferred for advertising purposes.
• Google user data is not used to train, improve, or develop generalized AI or machine-learning models.
• Human access to Google user data is limited to cases where the merchant asks for support, access is required for security or abuse investigation, access is required by law, or access is necessary for internal operations such as debugging a merchant-reported issue.
• Transfers to service providers are limited to what is necessary for FeedRescue to operate the app, and those providers are bound to process the data only for FeedRescue's app functions.

AI and merchant facts

FeedRescue treats AI as constrained enrichment only. AI may help draft explanations, category suggestions, copy improvements, or repair candidates from available product and diagnostic context, but deterministic rules and merchant-confirmed facts remain authoritative. FeedRescue does not use AI to invent GTINs, manufacturer part numbers, weights, dimensions, certifications, compliance facts, shipping facts, or other factual commerce claims.

When AI features are used, FeedRescue sends only the limited product and issue context needed to perform the requested app function. Google user data is not used to train generalized AI models.

How data is stored and protected

• Data is transmitted over encrypted HTTPS connections.
• OAuth tokens and sensitive contact values are encrypted or stored as references to encrypted secrets.
• Operational records use hashes, fingerprints, and minimized fields where full raw values are not needed.
• Access is limited by role and need, with audit logging for scans, suggestions, external writes, and cleanup.
• External writes use idempotency and audit records so a merchant can understand what was attempted.
• Provider calls are rate-limited, timeout-bounded, and monitored to reduce abuse and operational risk.

Sharing and subprocessors

FeedRescue shares data only as needed to provide, secure, monitor, support, and improve the app. This may include hosting, managed database, queue, object storage, email delivery, observability, analytics, and AI service providers. FeedRescue may also disclose data if required to comply with law, protect users, investigate abuse, or enforce terms.

Subprocessors may process Google user data only for the FeedRescue app functions described in this policy and not for their own advertising or unrelated purposes.

Retention and deletion

FeedRescue retains shop, scan, issue, fix, billing, support, and integration records for as long as needed to provide the app, maintain audit history, support rollback and troubleshooting, meet legal obligations, prevent abuse, and resolve disputes. Retention is minimized where possible by storing hashes, fingerprints, and references instead of raw data.

You can disconnect Google Merchant Center in the app, revoke FeedRescue access in your Google Account, or contact FeedRescue to request deletion of Google connection data. Shopify uninstall and privacy webhooks trigger the app's redaction and cleanup process for shop, customer, support, and integration data according to the app's retention process.

Merchant controls

• Google Merchant Center connection is optional and happens only after merchant OAuth authorization.
• Catalog repairs are non-destructive by default through supplemental feeds or app-owned metafields.
• Direct Shopify catalog edits require an explicit merchant setting before they can be used.
• Merchant-input issues stay merchant-input issues; FeedRescue should not invent missing factual values.
• You can review suggested values, write destination, evidence, and fix method before applying a fix.

Your choices and contact

To request access, correction, deletion, privacy support, or Google Merchant Center disconnection help, email feedrescue.api@gmail.com. You can also revoke Google access from your Google Account's third-party access settings.