Privacy policy

Last updated 3 October 2026

AlliDesk App Builder (“App Builder”, “we”) is a Shopify app that turns a Shopify store into an Android app its customers install. A merchant installs App Builder on their store and we process data on the merchant’s behalf: the merchant decides what their app does, and the shoppers who use it are the merchant’s customers. This page says what App Builder keeps, why, who else sees it and when it is deleted.

• What we keep about the merchant
• What we keep about shoppers
• How we use it
• Tools the merchant connects
• Who else processes it
• How long we keep it
• Security
• Your rights and contact

What we keep about the merchant

• The app itself: its name, icon, colours, pages, themes, schedules, A/B tests, smart links, discounts and push notifications, and the images uploaded for them.
• Previews: pictures of the online store’s pages, taken by our server for the Design tab.
• The store’s password, if the online store is password-protected, so the app and the previews can open it.
• Keys for connected tools, such as a Meta access token, a Google Analytics API secret or Firebase files. Secrets are stored encrypted.
• Builds and the signing key: each build of the app, and the key it is signed with, whose password is stored encrypted. The signing key is what lets the merchant update an app that is already on phones.
• Support chat: the messages and pictures the merchant sends us from the chat button in the app, and our answers.
• Billing: the plan, its price and any promo code used, as Shopify reports them, and the usage charged through Shopify (commission on orders placed in the app, extra builds).

We keep Shopify’s access token for the store so the app can work. We do not keep the names or email addresses of the store’s staff.

What we keep about shoppers

The app makes a random install id the first time it opens on a phone. It is not the phone’s advertising id and it does not name anyone. Against that id we keep:

• the phone’s platform and app version, when the app was first and last opened, and how many times;
• whether someone is signed in (yes or no) and how many items are in the cart, so the merchant can send a push to, say, shoppers with something in their cart;
• what was done in the app: opens, screens, products and collections viewed, add to cart, checkout started, push notifications received and opened, reels watched, liked or shopped, wishlist adds, searches (the words searched) and smart links opened;
• a push token from Firebase, when the merchant has connected Firebase, so a notification reaches the phone at once.

From Shopify’s order webhooks we keep, for each order the store takes: its number, where it came from (the app, the website, point of sale or another channel), its total and currency, its items (title, quantity, price and product), the discount codes used, and any cancellation or refund. For an order placed in the app we also keep the install id, the push notification and the app theme that led to it. We do not keep the customer’s name, email, phone number or address.

Signed-in shoppers see their orders, addresses and profile in the app. These are read from Shopify when the screen opens, through Shopify’s own signed app proxy, and are not stored by us. “Delete my account” in the app asks Shopify to erase that customer’s data for the merchant.

We never see payment details: checkout is Shopify’s.

How we use it

To build and update the merchant’s app; to show it the store’s live products, prices and stock; to deliver the push notifications the merchant sends; to show the merchant their analytics (app and website sales, push revenue, A/B test results); and to bill the plan and its usage through Shopify. We do not sell data, we do not use it for advertising of our own, and we do not combine one store’s shoppers with another’s.

Tools the merchant connects

Only when the merchant connects them, and always under the merchant’s own account with each provider:

• Google Analytics 4 and Meta. App Builder sends the merchant’s property and pixel the app’s product views, add to carts, checkouts and orders placed in the app, with the items, value and currency and the install id hashed; Meta also receives the phone’s IP address and user agent. For an order, Meta receives the customer’s email, phone number, name, city, state, postcode and country, each hashed with SHA-256 as Meta requires.
• Firebase Cloud Messaging, in the merchant’s own Firebase project, to deliver push notifications.
• Other tools: analytics, attribution and engagement services (such as Microsoft Clarity, AppsFlyer, Adjust, Branch, CleverTap, MoEngage, WebEngage, Klaviyo and Netcore) and review, loyalty, wishlist, search, delivery and chat services (such as Judge.me, Smile, Swym, Algolia, Shiprocket, WhatsApp, Tidio, Gorgias, Freshchat and Zendesk). Some run inside the app as the provider’s own code and collect data under that provider’s terms, so the merchant’s own privacy policy should name the ones they use.
• AlliDesk. If the store also uses AlliDesk, the app signs shoppers in through it, and AlliDesk’s privacy policy covers that.

Who else processes it

• Shopify, which App Builder runs on and bills through.
• Our hosting provider, whose server runs App Builder and holds its database and files.
• Cloudflare R2, which stores older builds of each app and our encrypted backups.

How long we keep it

• While the store has App Builder installed, its app, designs, uploads and analytics are kept, because they are the app and its history. The merchant can erase all analytics (installs, events and orders) at any time from Settings.
• Builds: the newest build of an app stays on our server; the 20 before it are kept in Cloudflare R2 so they can still be downloaded, and older ones are deleted.
• Push tokens are deleted as soon as Firebase says the phone no longer accepts them.
• Server logs, which record the IP address of each request, are deleted after 15 days.
• When a store uninstalls, its plan ends at once. Two days later Shopify asks us to erase the store’s data, and everything above is deleted: the app’s settings, designs, uploads and previews, its builds (in R2 too), its signing key, the keys for connected tools, its support chat, and its installs, events and orders. Once the signing key is gone, the app already on phones can no longer be updated. If the store installs App Builder again before then, nothing is erased. A record of the plan the store had and any promo code it used is kept for our accounts.
• When a shopper asks a merchant to erase their data, Shopify tells us which orders were theirs and we remove the install id from those orders, so nothing ties them to a phone. For a shopper’s request to see their data there is nothing to send, because nothing we keep names them.
• Backups are encrypted with AES-256 and kept for 14 days on our server, with an encrypted copy in Cloudflare R2. Data erased from the app can remain inside those encrypted backups until they are deleted.

Security

Everything travels over HTTPS. Keys for connected tools and the passwords of signing keys are encrypted with AES-256-GCM, under a key that is not stored in the database. The database has no network port: only App Builder itself reads it. Backups are encrypted before they leave the server, and only the people who run App Builder can reach it.

Your rights and contact

Shoppers: the store you use controls your data. Ask the store, and it can have your data exported or erased through Shopify; we act on that request as described above.

Merchants, and anyone else: for a question or a request about data, write to hello@allidesk.com. When this policy changes, the date at the top changes with it.