FEI Checkout Upsell

FEI Checkout Upsell

Privacy Policy

Effective date: June 10, 2026

FEI Checkout Upsell is a Shopify app for merchant-defined add-on services. This policy explains what information the app processes, which Shopify permissions it uses, and how that information supports the service.

Information we process

  • Shop information such as shop domain, installation state, approved app scopes, app settings, and language preference.
  • Authentication and session records needed to connect the embedded app to Shopify.
  • Merchant-configured service data, including categories, groups, options, prices, terms, display settings, and matching rules.
  • Product, variant, collection, and tag identifiers needed to match service offers to storefront products.
  • Online Store publication and sales channel identifiers needed to make FEI service products available where shoppers can buy them.
  • Order and service line item identifiers, FEI line item properties, service amounts, order status, currency, quantities, and timestamps needed for merchant service-order reporting.

Shopify permissions used by the app

  • read_products: used to read product, variant, collection, and tag information so merchants can target service offers to the correct products.
  • write_products: used to create and update the merchant's hidden FEI service product and service variants, including price and active state, so selected services can be sold as Shopify line items.
  • read_publications: used to read Online Store publication and sales channel data so the app can identify where the hidden FEI service product should be available.
  • write_publications: used to publish the hidden FEI service product to the Online Store publication so selected services can be added to cart and purchased.
  • read_orders: used to receive and process order webhooks so merchants can see which Shopify orders include purchased FEI add-on services, paid service revenue, and basic attach-rate reporting.
  • write_app_proxy: used to operate the Shopify App Proxy endpoint that securely provides storefront service configuration to theme app blocks.

How we use information

  • To operate the embedded Shopify app, merchant settings, and App Proxy endpoints.
  • To show merchant-defined add-on service options on product and cart surfaces.
  • To sync merchant-defined service options with Shopify product variants.
  • To publish FEI service products to the Online Store publication when merchants sync service variants.
  • To attach service identifiers to cart and order line items for merchant reporting and fulfillment workflows.
  • To record service order status and paid service amounts from Shopify order webhooks.
  • To maintain security, debug errors, comply with Shopify requirements, and respond to support requests.

Buyer and customer data

  • The app is designed to avoid unnecessary customer data access and does not sell buyer personal information.
  • The app uses order webhook data only to show merchant-facing service order records and basic service sales metrics.
  • The app does not store customer name, email, phone, or address for the service-order reporting feature.

Merchant responsibilities

  • Merchants define their own service content, pricing, terms, fulfillment process, and customer support obligations.
  • Merchants are responsible for making their service terms accurate, lawful, and visible to buyers where required.

Data sharing and processors

  • The app may use hosting, database, logging, and deployment providers to operate the service.
  • Information is shared with Shopify APIs only as needed for app functionality and according to permissions approved by the merchant.

Retention and deletion

  • Installation sessions and shop settings are retained while the app is installed.
  • When the app receives Shopify uninstall, scope update, customer data request, customer redact, or shop redact webhooks, it processes those requests according to Shopify requirements.

Security

  • The production website and app use HTTPS.
  • Secrets, private keys, access tokens, and environment files are not committed to source control or exposed publicly.

Contact