Your privacy obligations

Your app ships under your own developer accounts, so you are the one responsible for its privacy compliance. When you turn on analytics or push, your app collects data from shoppers, and both Apple and Google require you to disclose that and to publish a privacy policy. This guide covers what to declare and one current gap to work around.

What your app collects depends on what you enable

A Vunda app only collects what its enabled integrations collect:

• Analytics: when you Enable Google Analytics on the Integrations page, your app reports events (screen views, product views, add to cart, checkout and, when your app has those screens, video views, opens of stories, articles and routines, shares, likes, saves and follows) to your GA4 property. The Google Analytics card lists every one under Events your app sends.
• Push: when you Enable Klaviyo or Enable OneSignal, your app asks the shopper for notification permission, registers a device push token, and identifies the signed-in shopper to your push provider.

If you leave these off, the app does not send that data. Declare whatever you do enable in your App Store privacy details and your Google Play Data safety form, and reflect it in your privacy policy. (Sources: Apple - App privacy details, and Google Play - Data safety.)

Google Analytics in your privacy forms

If you connect GA4, declare its events as analytics in both stores:

• App Store privacy details: Usage Data > Product Interaction, for the Analytics purpose. Apple's definition of product interaction includes app launches, taps, clicks, scrolling, music listening, video views and saved place in a game, so video views and the other events in the list belong here. (Source: Apple - App privacy details.)
• Google Play Data safety: App activity > App interactions, collected, for the Analytics purpose. (Source: Google Play - Data safety.)

When a shopper allows usage analytics, the app grants Google only analytics_storage and keeps ad_personalization and the other advertising signals denied. Keep it that way in Google Analytics too: do not turn on Google signals or ads personalisation for the property or link it to Google Ads for personalised advertising. Apple treats data that is linked with other companies' data for targeted advertising as tracking, which needs its own prompt and declaration. (Source: Apple - App privacy details.) Firebase collects some data of its own through its SDK, so also check Google's disclosure for the Firebase SDK against your forms.

Sign-up forms

If you add a sign-up form in App builder > Signup forms, your app collects the email address (and first name and mobile number, if the form asks) of shoppers who sign up, with their marketing consent, and sends them to your Shopify store or your Klaviyo list. Declare them in your privacy details and privacy policy. Collect sign-ups with forms covers what to declare and what Vunda keeps.

Vunda push: what is collected today

When you Use Vunda push, your app:

• Registers the push token of each shopper who allows notifications, with the phone's platform, language, time zone and app version. When the shopper is signed in, Vunda also stores a pseudonym of their customer id, never the id itself.
• Keeps, against the phone's push token, the drop reminders and restock requests the shopper sets and the notification types they turn off, so it can send exactly the alerts they asked for and none they turned off. When you connect Klaviyo, a shopper can also ask for a restock email: the app sends the address straight to your Klaviyo back in stock flow, and Vunda never receives or keeps it.
• Records when a shopper opens one of your notifications, so Push can show how many were opened. Once the shopper turns notifications off, the app records and sends nothing, not even opens.
• When a shopper opened one of your notifications in the last 24 hours and then checks out, adds that notification's id to the cart as _vunda_push_message, so the order can be credited to the push. It is only the notification's id, never shopper data.

When a shopper turns notifications off in your app, Vunda deletes that phone's push token and its push history. It keeps only a pseudonymous marker that the phone already received your welcome flow, for up to 400 days, so turning notifications off and on again cannot start the welcome a second time. When Shopify asks Vunda to erase a shopper's data, the marker of every phone still registered to that shopper is deleted too.

In-app activity tracking: off today, and what changes when it is on

Automations that start from what shoppers do in your app (abandoned checkout, browse abandonment, back in stock, price drop and post-purchase), and counting orders placed in the app after a push, need in-app activity. Vunda does not collect this activity today. The app drops it on the phone and Vunda's servers store none of it, and those flows show Needs activity tracking in Push and cannot be turned on.

Collection is one platform switch (VUNDA_PUSH_EVENTS_ENABLED) that Vunda turns on for every store on Vunda push at once, not a setting in your admin. If you plan to use these automations, update your privacy policy, your App Store privacy details and your Google Play Data safety form (below) before it is switched on. When in-app activity tracking is turned on for your store:

• Only shoppers who allowed both notifications and usage analytics in your app are tracked, and only while both stand. A shopper who declined either, or later turned either off in Account, sends nothing, and anything not yet sent is discarded. In Vunda push apps the usage analytics prompt tells shoppers it is also used to personalise their notifications.
• The app reports five kinds of activity: a product viewed, a product added to the wishlist, items added to the cart, checkout started, and an order completed.
• Each record holds the time, the Shopify product ids involved, a pseudonym for the phone and, when the shopper is signed in, the pseudonym of their customer id. Checkout and order records also hold a pseudonym of the cart or order id, and an order record holds the order total and currency and, if the shopper opened one of your notifications in the 24 hours before, which one.
• No name, email address, phone number, postal address or product title is stored. Product names in your notifications come from your store, never from the app.
• In Push you see totals (for example orders after a push), never one shopper's activity.
• The activity records (the push_events data) are kept for 90 days, and the products a phone is waiting on for back-in-stock or price-drop pushes for 30 days after the shopper last viewed them. Both are deleted sooner when the shopper turns notifications off in your app, or when Shopify asks Vunda to erase that shopper's data.

What to tell shoppers

Add to your privacy policy that, for shoppers who allow notifications and usage analytics, your app records the products they view and wishlist, what they add to their cart, when they start checkout and the orders they place in the app, and that you use this to send them notifications about those products and orders (for example a reminder about a product they looked at, a back-in-stock alert or a thank-you after an order) and to measure how well your notifications work. Say that turning notifications or usage analytics off in the app stops it, and that turning notifications off also deletes what was recorded for that phone, and name Vunda as the service that stores it for you.

App Store privacy details

In App Store Connect, under App Privacy, Apple asks which data types your app collects, whether each is linked to the user, whether it is used for tracking, and for which purposes. When in-app activity tracking is on, these apply to the Vunda push data (Source: Apple - App privacy details):

• Usage Data > Product Interaction (product views, wishlist, add to cart, checkout started). Linked to the user: yes, because it is tied to the shopper's phone and, when signed in, their account. Purposes: App Functionality, Developer's Advertising or Marketing (your automated pushes are marketing sent to your own shoppers) and Analytics (measuring your pushes).
• Purchases > Purchase History (orders completed in the app). Linked to the user: yes. Same three purposes.
• Used for tracking: no. Vunda does not combine this data with other companies' data for advertising, and does not share it with data brokers, which is what Apple means by tracking.

Apple lets you skip a data type only when it meets all of its optional-disclosure criteria, and data used for Developer's Advertising or Marketing does not, so declare both. Keep the entries you already need for Vunda push itself, such as the push token.

Google Play Data safety

In Play Console, the Data safety form asks which data types your app collects or shares and why. When in-app activity tracking is on (Source: Google Play - Data safety):

• App activity > App interactions: collected. Purposes: App functionality, Analytics and Advertising or marketing.
• Financial info > Purchase history: collected, with the same purposes.
• Shared: no. Google does not count a service provider that processes data on your behalf, as Vunda does, as sharing.
• Processed ephemerally: no, the records are stored.
• Required or optional: optional, because shoppers can use the app without allowing notifications or usage analytics.
• Encrypted in transit: yes. Shoppers can have it deleted by turning notifications off in the app, or by asking you, since Shopify's customer data erasure also reaches Vunda.

These are the entries that match what Vunda collects. Your app may collect more through other integrations you enable, so check the whole form against your setup.

Customer and order data is not used yet

Features that read your Shopify customers or orders, or that create discount codes, need Shopify permissions Vunda does not ask for today: campaign audiences from customer segments or tags, win-back, starting abandoned checkout or post-purchase from your Shopify orders, crediting orders from your Shopify order records, and a unique discount code for each shopper. They stay off until Vunda asks for those permissions and you approve them. Until then, win-back shows Needs order access in Push and the customer audience options cannot be chosen.

You must publish a privacy policy

Both stores require a privacy policy URL for an app that collects data, and Apple reviews every submission against its App Store Review Guidelines, which treat privacy as a review area in its own right. Publish one regardless of which integrations you enable - it is the safest default, and both store listings have a field for it. Put a privacy policy that reflects your data use at a stable URL, and set that URL in both your App Store and Google Play listings (see Complete your store listings). (Sources: Apple - App Review Guidelines, Privacy, and Google Play - User Data policy.)

A current gap: the in-app privacy link is not wired yet

Your app can show a privacy policy link on its onboarding screens. In App builder, choose Welcome flow in the workspace picker, then open Look & feel, switch on Show a privacy policy link and enter your privacy policy URL. Saved changes reach shoppers opening the app for the first time once your App Store and Google Play version includes onboarding updates. Your store listings still need their own privacy policy URL, so make sure it is set on both.

What to do

• Write a privacy policy that matches the integrations you enable.
• Add its URL to both your App Store and Google Play listings.
• Complete Apple's privacy details and Google Play's Data safety form to match.
• Update all of the above whenever you change which integrations are on.