Feast privacy policy

When a store installs Feast, the app stores:

• Store identity and authentication: the store's myshopify domain, the OAuth scopes granted, and the access token needed to call Shopify's APIs. Session records created by Shopify's sign-in may include the admin user's ID, name, email address and locale; these are used only for authentication, never for marketing.
• Recipe content and settings: the recipes, ingredients, steps, timings and related settings the merchant creates in the app. Published recipes are also written to app-owned Shopify metaobjects so the storefront can render them.
• Linked products: Shopify product and variant IDs, plus cached titles and images, only where the merchant links a product to an ingredient.
• Uploaded recipe images: stored under a per-store prefix and served publicly only through a validated Feast image route while the store's installation is active.
• Billing state: the store's plan, Shopify subscription reference and trial state, used to enforce Free and Pro entitlements. Billing is handled by Shopify; Feast never receives card or payment details.
• Operational logs: error and diagnostic context restricted to safe identifiers such as the store domain, route path, request method, recipe ID and status. Request bodies, access tokens and secrets are excluded.

• No storefront customer accounts, names, email addresses, shipping addresses, payment details or order records are stored in Feast's database.
• No raw shopper IP addresses are stored by the application. Our infrastructure providers process network metadata as a normal part of delivering the service, as described in their terms.
• A shopper's ingredient check-offs on a recipe are kept only in that shopper's own browser storage and are never transmitted to Feast.
• Feast does not run behavioral analytics, ratings collection or AI processing at this time. The corresponding features are disabled, their endpoints are inactive, and no such data is collected.

We use the data above solely to:

• operate the service — authenticating the store, publishing recipes to the storefront, serving images and enforcing plan entitlements;
• provide merchant support when the merchant contacts us;
• keep the service secure, prevent abuse and diagnose faults; and
• comply with legal obligations.

We do not sell or rent this data, and we do not use merchant store data for advertising or marketing.

Feast runs on the following providers:

• Shopify — authentication, billing, product data, app-owned metaobjects and theme extension delivery.
• Cloudflare — application hosting, network delivery, operational logs and image storage (R2).
• Neon — PostgreSQL database hosting.
• Rollbar — error monitoring, limited to the safe operational context described above.

Each provider processes data under its own terms and data-processing agreement. All data is transferred over HTTPS and stored with industry-standard encryption.

• Uninstall: the store is immediately marked inactive, its stored access token is cleared and its sessions are deleted. Uploaded images are queued for deletion after 48 hours, so a reinstall inside that window restores them.
• Store redaction: when Shopify sends the mandatory shop/redact request after uninstall, Feast deletes the store's relational data and queues its image storage for complete erasure, retried until it converges.
• Customer requests: Shopify's customers/data_request and customers/redact webhooks are received and acknowledged. Feast holds no customer-linked records, so there is nothing to export or erase.
• Caches: publicly served recipe images revalidate within five minutes, so removal takes effect promptly.

Merchants and individuals have the rights described in our general privacy policy, including access, correction and deletion, under GDPR and the UK Data Protection Act. To exercise them for Feast data, contact us at the address below and we will respond promptly.

We may update this policy as Feast evolves; changes will be posted on this page with a new date. Questions and requests: