This page describes what the app does with data from your Shopify store, as built today. The app is in Shopify review and not yet in the App Store. It adds detail to the HappifyApps privacy policy.
Reviewed against the app’s code on 2026-10-08
Store Builder reads your product catalogue to plan a storefront. It keeps projects, versions and drafts, and sends text you ask it to draft or translate to Google Gemini. Reviewed actions can prepare files and translations in an unpublished theme, publish a theme, create missing content pages, or update explicitly selected fields of an existing page. New workflows remain in testing; the app listing has not been submitted.
All Happify apps run on one platform and one Postgres database (Supabase). The apps run on our own server at Hetzner. Store data is kept once per store, not once per app: if you install two Happify apps, they read the same copy of your products, inventory and orders.
| Shopify permission | Used for |
|---|---|
| read_orders | When purchase attribution is approved and explicitly enabled, verifies linked paid orders and refunds. Contact details and addresses are not retained; this does not import your order history into the shared catalogue. |
| read_customer_events | Enables the analytics-consented checkout signal used to link an experiment receipt to a purchase. No browser-supplied revenue is trusted. |
| write_pixels | Creates or updates the Store Builder analytics pixel only through explicit merchant setup. Collection remains disabled until operator approval, granted permissions and verified setup. |
| read_products | Products, variants and prices, so a project is planned around what you actually sell and AI copy can use current product facts. |
| write_products | Saves explicitly reviewed product/collection SEO metafields or title/description text, creates reviewed supplier draft products, or creates a draft native fixed bundle with an explicit price and component relationships. It never publishes these drafts or changes existing component prices or inventory quantities. |
| read_files | Verifies the exact uploaded image is ready in Shopify Files before adding it to the media library, and checks uncertain upload results without recreating a file. |
| write_files | Stages and creates an image in Shopify Files after upload and rights confirmation. A separate reviewed action can append a verified image to a native product gallery; existing images are preserved. |
| write_discounts | Creates an explicitly reviewed, scheduled percentage discount on selected variants, reads its outcome, and deactivates it on request. The app never chooses a discount or changes existing product prices automatically. |
| write_app_proxy | Enables signed first-party requests for explicitly started live homepage hero tests and consented hero views/button clicks. It does not grant customer or order access. |
| read_themes | Lists your themes and reads the files of the unpublished theme you choose, so the app can check it is safe to change. |
| write_themes | Writes generated files or explicitly reviewed manual text-file changes to the unpublished theme you choose. Publishing that theme requires a separate confirmation. Shopify requires a separate approval for theme-file writes, which is pending. |
| read_online_store_pages | Reads existing content pages to identify missing pages and compare current title/body content with your saved draft before a reviewed update. |
| write_online_store_pages | Creates missing content pages after confirmation, updates explicitly reviewed title/body fields, or saves selected search title/description metafields through the separate SEO review. Handles and publication settings are preserved. |
| read_legal_policies | Reads whether your shop has a shipping policy, a refund policy and contact information published, so the product-readiness check can flag a missing one. Read-only; the policy text is not stored. |
| read_locales | Lists languages already enabled in Shopify. Store Builder does not enable or publish languages automatically. |
| read_translations | Reads theme translation fields, source digests and existing translations so you can review exact changes. |
| write_translations | Saves explicitly mapped and reviewed translations to an unpublished theme, with a final source check. Market-specific overrides are preserved. |
Read but not stored: A complete theme backup: selective publication reads theme files to detect unrelated changes, but retained rollback snapshots cover the generated templates rather than every merchant file; Catalogue SEO audit results: these remain in the current browser tab and are cleared when the tab reloads. Selected SEO change reviews are stored separately as described above..
When an app has order access, the import copies each order with its line items, totals, tax lines, discount codes, tags, note, note attributes and Shopify’s risk recommendation. Buyer details are kept only while an app on your store needs them: the buyer’s name, email, phone and shipping and billing addresses only while Local Delivery Sheet or Invoice & Packing Slip is installed, and the customer’s name and email (on the customer record) only while Reorder Predictions, Local Delivery Sheet or Invoice & Packing Slip is installed. Otherwise orders are stored without contact details and customers as a Shopify ID only, and the import does not ask Shopify for those fields. The stored copy of what Shopify sent never keeps the buyer’s contact, browser or device details.
Purchase attribution requests order and customer-event permissions but remains disabled until approval and setup. It retains pseudonymous linkage and verified order payment/refund records, including a keyed customer-ID hash solely for erasure. Names, email addresses, phone numbers and postal addresses from order events are not retained. The shared customer-record import level is none; this does not mean that attribution data is non-personal. One thing you type can still be personal data: a testimonial’s attribution (a customer’s name, up to 120 characters) and source note (up to 300 characters). You enter both yourself; they are stored in the project, in every saved version and in the publication manifest, and the attribution is published to your storefront. Enter a name only when you have that customer’s permission to show it. Where another Happify app on your store keeps customer or order details, that app’s page describes them.
| Recipient | Purpose | Data |
|---|---|---|
| Google PageSpeed Insights and Chrome UX Report | Explicitly requested performance scans of your public homepage and available aggregate field measurements | The verified public homepage URL and selected device are sent to Google. Google retrieves the public page. No unpublished preview URL, Shopify token, password, customer record or raw visitor identifier is sent. Field reports may be unavailable when Google has insufficient page-level data. |
| Google (Gemini API) | Drafting copy, translations, hero images and reference-based product/lifestyle variations when you use AI on the Advanced or Pro plan | Copy requests send your prompt, store name, industry, any brief you entered, and the title and description of a product when you choose one. When you improve a homepage section, the existing heading and body of that section are sent too. Brand style suggestions send the current colours, typography and locks. Image requests send your prompt, store name and industry; variation requests also send the image reference you upload after confirming permission. Responsive crops are processed in your browser. Translation requests send the selected source text and language. No Shopify customer or order records are sent, but text and images you supply can contain personal data; do not include private information in AI requests. Google handles the request under its own Gemini API terms. |
Hosting is on Hetzner and Supabase, listed on our Sub-processors page. We do not sell data or use it for advertising.
Shopify sends every app these mandatory webhooks. This is what the app does with each.
| Webhook | What happens |
|---|---|
| app/uninstalled | Marks the app as uninstalled and its subscription as cancelled, and stops syncing for it. Nothing is deleted at this point: Shopify sends the shop redaction request below 48 hours later, and any other Happify app on the store keeps working meanwhile. |
| customers/data_request | Logged on receipt. We prepare the customer’s data by hand and send it to you, the merchant, within 30 days. |
| customers/redact | Removes the customer’s name and email from the customer record; their name, email, phone and addresses from their orders; their contact details from Local Delivery Sheet run stops, along with any proof of delivery photo or signature for those stops; stored webhook records about them; and their email address wherever it was logged as an email recipient. Order lines and totals stay, so your sales history still adds up. |
| shop/redact | Deletes this app’s data for your store: its installation and encrypted access token, subscription record, settings, app-specific data (such as delivery runs and proof of delivery, zones, internal order notes), audit log entries and webhook records. The shared store data (products, inventory, orders, customers) is deleted too when no other Happify app is installed on the store. If one is, the shared data stays for that app, cut down to the customer details it needs. |
To ask for a copy of your store’s data, or to have data deleted sooner, email admin@happifyapps.com. Settings in the app also has a “Download account data” button.