Privacy policy

1. What we collect from merchants

When you create an account and connect a store we collect:

• Your name, email address and password (stored as a hash), and the workspace and app names you choose.
• Store credentials your platform issues to us: a Shopify access token after you install our app, or WooCommerce REST keys after you approve us from your WordPress admin. These are encrypted with a key held separately from the database before they are stored, and are used only to read your catalogue, register webhooks and, where you ask us to, create charges.
• Your app design: templates, sections, colours, images and text you upload or write. Images are stored in our object storage.
• Optional integration credentials you paste in, such as a Judge.me token, an Apple App Store Connect API key or a Google Play service account. These are encrypted the same way as store credentials and used only for the integration you connected them for.
• Billing status from the payment provider you pay through (plan, status, renewal date). We never see card numbers.
• Technical logs of dashboard requests (IP address, browser, timestamps) kept for security and debugging.

2. What we collect from shoppers through merchant apps

A merchant app built with AppFromShop sends us only what is needed for it to work:

• An install id generated on the device, the platform (iOS or Android), app version, locale and, if the shopper allows notifications, a push token. This lets the merchant send push notifications and lets the app receive design updates.
• Cart state (the store's cart id, number of lines, subtotal) so the merchant's abandoned-cart reminder can run. No payment details pass through us: checkout happens on the store's own checkout (Shopify's checkout or the WooCommerce order page).
• Whether a shopper is signed in. On Shopify, sign-in uses Shopify's Customer Account API; the access token stays on the device and is sent to Shopify, not to us. We do not store shopper names, emails or order histories.
• Anonymous counts such as "app opened" used for the merchant's install and active-user figures. We do not run third-party advertising or analytics SDKs inside merchant apps.

Product, collection, price and stock data is read by the app directly from the merchant's store platform. Reviews are fetched through our servers from the merchant's reviews provider and cached briefly.

3. The AppFromShop app for merchants

The AppFromShop app on Google Play and the App Store lets merchants and their teams see an app's draft on a phone. It needs no account and collects very little:

• Camera: used only to read the QR code shown in the dashboard. The image is processed on the device; no photos or video are stored or sent to us.
• Your apps list: the preview links you open, with each app's name and icon, are kept on the phone only. Long-press an app to remove it.
• Device presence: while a preview is open, the app sends an install id generated on the device and the device type, so the merchant's dashboard can show which phones are previewing. It does not register as an install of the merchant's app, report usage, or ask for notifications.
• The sample store and any store you preview load product data straight from that store. Checkout happens on the store's own checkout; no payment details pass through us.

4. Why we process it

• To provide the service: build, preview, publish and update the merchant's app.
• To send push notifications a merchant composes or schedules.
• To bill merchants for their plan through the provider they chose.
• To keep the service secure and to investigate abuse or failures.
• To meet legal obligations, including store-platform compliance requests.

5. Who we share it with

We share data only with providers needed to run the service, under their own terms:

• Shopify and WooCommerce (the merchant's own store), for catalogue, checkout, accounts and, for Shopify merchants, billing.
• Expo push services, and through them Apple Push Notification service and Firebase Cloud Messaging, to deliver notifications.
• Apple App Store Connect and Google Play Console, when a merchant launches their app, using the merchant's own developer accounts.
• Razorpay and Paddle, when a non-Shopify merchant pays for a plan.
• Judge.me or Yotpo, when a merchant connects a reviews provider.
• Our hosting and infrastructure providers (servers, object storage, content delivery and DNS).

We do not sell personal data and do not share it for advertising.

6. Shopify protected customer data

Where a Shopify merchant enables shopper sign-in, their app reads customer data under Shopify's protected customer data requirements. We request only the scopes the feature needs (customer and order read access), do not store that data on our servers, and keep it on the shopper's device for the session. Merchants remain responsible for their own privacy notices to shoppers.

7. How long we keep it

• Merchant accounts, designs and published versions: for as long as the workspace exists, and 30 days after it is deleted so an accidental deletion can be reversed.
• Store and integration credentials: until the connection is removed or the store uninstalls us, then deleted within 48 hours (Shopify uninstall webhooks trigger this automatically).
• Shopper install ids, push tokens and cart state: until the app is uninstalled or the token becomes invalid, or 12 months after the last activity.
• Request logs: 30 days.

8. Your rights

Depending on where you live, you may have rights to access, correct, export, restrict or delete your personal data, and to object to some processing. Merchants can delete their workspace from the dashboard; shoppers can uninstall the app, which removes the install id and push token from active use, or ask the merchant to request deletion on their behalf.

To exercise a right, email [email protected]. We answer within 30 days. If you are in the UK or EU you may also complain to your supervisory authority; if you are in India, the Digital Personal Data Protection Act applies and you may approach the Data Protection Board.

9. Security

Credentials are envelope-encrypted at rest, traffic is encrypted in transit, access to production is limited to named staff, and published app configurations are cryptographically signed so an app only accepts what we published. No system is perfectly secure; if we learn of a breach affecting you we will notify you and, where required, the relevant authorities without undue delay.

10. International transfers

Our servers and providers may be located outside your country. Where data leaves the UK, EU or India we rely on the providers' standard contractual terms and equivalent safeguards.

11. Children

The dashboard is for businesses and not directed at children. Merchant apps follow the age rating the merchant declares to Apple and Google; we do not knowingly collect data from children under 13 (or the applicable age in your country) through them.

12. Changes and contact

We will post changes to this policy here and update the date above; material changes are announced in the dashboard. Contact: [email protected].