Privacy · Free Shipping Bar
Free Shipping Bar — Privacy Policy
Last updated: July 4, 2026
This policy applies specifically to the Free Shipping Bar Shopify app. For the general Boost Apps website policy, see the main privacy page.
Scope of this policy
This page describes how the Free Shipping Bar Shopify app (the “App”) processes data. It covers the embedded admin interface, the storefront widget delivered through Shopify’s Theme App Extension, and the checkout attribution logic delivered through Shopify’s Web Pixel Extension. It does not cover the Boost Apps marketing website itself; see the main Boost Apps privacy page for that.
Data the App receives from merchants
When a merchant installs the App through Shopify, Shopify’s OAuth flow provides the App with the shop’s .myshopify.com domain, an OAuth access token, and the granted API scopes. Shopify also returns session metadata about the installing user, including that user’s Shopify user ID, first and last name, email address, locale, account owner or collaborator flag, and email verification status. This information is stored so the App can authenticate subsequent admin requests. The App additionally stores the merchant’s subscription and billing state (Shopify charge identifier, plan name, status, current billing period end) and the campaign settings the merchant enters in the admin (bar name, threshold amount and currency, message templates, colors, mobile behavior, page targeting, priority, and scheduling).
Permissions the App requests and why
The App requests three Shopify access scopes. read_themes is used to read the merchant’s theme information in order to detect whether the App’s theme app embed has been enabled, so the admin can show an accurate activation status. write_pixels and read_customer_events are used to register and run the Web Pixel that reports the checkout conversion described below. The App does not request access to products, orders, or customer records.
Data the App receives from storefront visitors
The storefront widget records three anonymous event types: “impression” when the bar is first shown to a shopper, “goal reached” when the shopper’s cart subtotal crosses the bar’s threshold, and “conversion” when a checkout is completed for a session that saw the bar. Each event stores a randomly generated session identifier and, where applicable, the cart subtotal at the time of the event. Conversion events additionally store the Shopify order or checkout token supplied by Shopify’s Web Pixel runtime, which the App uses only to deduplicate retried events and to attribute revenue to the correct bar in aggregate reporting. The App does not collect shopper names, email addresses, phone numbers, postal addresses, or payment details, and does not link the random session identifier to any Shopify customer profile.
Cookies and browser storage
On storefronts where the App is active, two first-party cookies are set with a 24-hour lifetime and SameSite=Lax attribute: “fs_seen” records that the bar was shown in the current session, and “fs_app_url” stores the event endpoint the Shopify Web Pixel should post the conversion event to. The widget also writes short deduplication keys to the browser’s sessionStorage (fs:sid and per-event keys) so an event fires at most once per session. Those sessionStorage keys stay in the browser and are not transmitted back to the App.
IP addresses
Requests to the App’s public event endpoint are rate-limited per IP address. IP addresses are held in an in-memory bucket for at most one minute for that purpose and are not written to the App’s database. IP addresses may appear transiently in the App’s hosting provider platform logs (see “Sub-processors” below) subject to that provider’s log retention.
How data is used
Merchant data is used only to authenticate the merchant with Shopify, render the App’s admin interface, sync the merchant’s bar configuration to a public Shopify shop metafield so the storefront widget can render it, bill the merchant through Shopify App Pricing, compute the aggregate performance metrics shown to the merchant in their own admin dashboard, and prevent abuse of the public event endpoint. Data is never sold, rented, or shared for advertising or profiling purposes.
Sub-processors
The App is hosted on Fly.io in the Frankfurt (fra) region and uses Neon as its managed PostgreSQL database provider in an EU region (eu-central-1). Merchant OAuth, Admin GraphQL, Web Pixel runtime, and App Store billing are provided by Shopify. No other sub-processors are used; no data is sent to advertising networks, social platforms, or third-party analytics services.
Data location and security
Both the App and its database are hosted in the European Union. Data in transit is encrypted with HTTPS/TLS. OAuth access tokens and database credentials are stored as encrypted secrets in the hosting provider and are not committed to source control. Access to the production environment is restricted to Boost Apps engineers using two-factor authentication.
Retention and deletion
While the App is installed, campaign configuration and analytics events are retained so historical metrics remain available to the merchant in the admin dashboard. When a store uninstalls the App, Shopify fires the app/uninstalled webhook and the App immediately deletes the merchant’s OAuth session records and marks any active subscription as cancelled; campaign configuration and analytics events are retained temporarily so a reinstall within 48 hours can recover the previous setup. 48 hours after uninstall Shopify fires the shop/redact webhook and the App permanently deletes all remaining data for the shop: analytics events, campaigns, subscription records, and any residual session data.
GDPR / privacy compliance webhooks
The App implements the three Shopify-mandated privacy webhooks. customers/data_request is acknowledged with no data action because the App does not store any Shopify customer’s personal data. customers/redact is acknowledged with no data action for the same reason. shop/redact triggers the full-purge behavior described above.
Children
The App is a merchant-facing Shopify tool and is not directed at children. It does not knowingly collect data from children.
International transfers
The App infrastructure is located in the European Union. Shopify, as the platform, operates globally; data passing between the App and Shopify’s systems is transferred under Shopify’s own data transfer terms.
Merchant rights
Merchants can uninstall the App from their Shopify admin at any time, which triggers the deletion flow described above. Merchants can also request an export or deletion of the data described in this policy by contacting Boost Apps at the address below.
Changes to this policy
Material changes to this policy will be reflected on this page with an updated revision date. The current version is always available at this URL.
Contact
Questions, data requests, or concerns about this policy can be sent to hello@boostapps.co.