Data and permissions: what Commander reads and what it can change
Commander reads data from your Shopify store and from the sources you connect. This page lists the Shopify permissions Commander holds, what each source adds and what reaches AI providers.
Shopify permissions
You approve these permissions when you install Commander. They stay in place until you uninstall the app.
Warning: Commander holds some permissions that let it change data in your store. Check the Can change data column.
To see the permissions in the app, open Settings > Integrations and click the Shopify card. While the store is connected, the dialog shows the connected store and a Granted permissions list. The list names each permission your store granted, with the name the table below uses. A permission that can change data also shows Can change data. While the status loads, or when Commander cannot read the permissions, the dialog shows the status without the list. The table below lists every permission Commander can hold and what each one allows.
| Permission | What it allows | Can change data |
|---|---|---|
| Read products | Syncs your catalog: products, variants, collections and inventory. | No |
| Read orders | Reads your recent orders to build product and customer insights. | No |
| Read all orders | Reads your full order history. Without it, Shopify limits how far back Commander can read. | No |
| Read customers | Reads customer profiles to build segments and RFM scores. | No |
| Write customers | Adds RFM tags and metafields to customer records in Shopify. | Yes |
| Read analytics | Reads your store analytics data. | No |
| Read reports | Reads your sales report. The setup wizard uses it to pick your first products. | No |
| Read themes | Reads your theme so Commander can check that its app blocks are installed. | No |
| Write content | Lets Commander create and edit pages in your online store. | Yes |
| Write online store navigation | Lets Commander create URL redirects. | Yes |
| Write files | Lets Commander upload images to your store's Files library. | Yes |
| Read customer events | Lets an app-owned tracking pixel read storefront events, such as page views. | No |
| Write pixels | Lets Commander create and manage an app-owned tracking pixel in your store. Commander does not create one today. | Yes |
A permission sets the most the app may do. It does not mean every feature uses it today. To change what Commander can do, uninstall the app from Shopify Admin.
What other sources add
Each integration you connect adds its own data. Commander reads only from sources you connect. Blueshift is the exception: it receives data from Commander.
| Source | What it adds |
|---|---|
| Meta Ads and Google Ads | Performance and creative data for your own ad accounts. |
| Google Analytics 4 | Product views, add-to-cart events and purchases from your property. |
| Triple Whale | Attribution and profit analytics from your Triple Whale account. |
| Klar | Channel attribution, marketing and profit figures from your Klar account. |
| Review apps and CSV import | Product reviews from your review app or from a file you upload. |
| Blueshift | Nothing is read from it. Commander sends customer attributes, such as RFM segments, and the audiences you sync to your Blueshift account. |
Each integration page lists exactly what it needs. Start from Integrations.
AI providers and your data
Commander uses AI providers to write text, analyse ads and generate creative.
- Omniconvert's privacy notice states that Commander leaves individual user identifiers out of AI prompts. Prompts carry aggregated figures, ad copy and creative briefs.
- The notice states that your data is not used to train AI models.
- The notice states that AI insights are recommendations for your review and action.
For the legal terms, the full provider list and retention periods, read Omniconvert's privacy notice for Commander. This page is a summary, not the notice.
The notice also lists the sub-processors Omniconvert uses, including the session-recording tool. Read its section on sub-processors for the current list.
Tracking and cookies
Commander uses Microsoft Clarity, PostHog and Google Analytics to understand how people use the app. Warning: if you decline, Commander still measures usage with Clarity and PostHog, but without cookies and without your email. In your browser, Google Analytics receives nothing until you accept. Usage events that Commander records on its own servers go to Google Analytics only when your consent is granted: by Accept, or automatically where no banner is required. Events that belong to no person, such as system events of a store, still go to Google Analytics without personal identifiers.
The consent banner
If the time zone of your browser is in Europe, Commander shows a banner at the top of the page before it uses cookies. This covers the EEA, the UK and Switzerland. The banner names the tools and has a Privacy notice link. It has two buttons of equal weight: Accept and Decline. Elsewhere the banner does not appear and tracking is on by default, so Google Analytics runs there without a question. Commander treats that as granted consent and keeps it with your account when you are signed in. You can still turn it off, as shown below. Google Analytics then stops at once, in your browser and on Commander servers. If you travel into a region with a banner, Commander shows the banner again and sends nothing to Google Analytics until you answer.
| Your choice | What happens |
|---|---|
| Accept | Cookies and browser storage are allowed. PostHog links your usage to your email. Google Analytics starts and receives your usage events, from your browser and from Commander servers, under an internal ID, never your email. |
| Decline | Clarity runs without cookies. PostHog keeps nothing in your browser and knows you by an internal ID, not your email. Google Analytics does not load in your browser, and Commander servers send it none of your usage events. |
| No answer yet | Same as Decline, until you answer: Google Analytics does not load in your browser, and Commander servers send it none of your usage events. |
Commander saves your choice in your browser and, when you are signed in, with your user account. A decline takes effect at once in your browser, and within a minute on Commander servers. An accept reaches PostHog fully on your next page load.
Your choice is saved for your user account. If someone else signs in on the same browser, they see the banner until they answer. Your own answer comes back when you sign in again.
Change your choice
- Open Settings > Profile.
- Click Privacy & tracking.
- Turn the Allow cookies and link usage to my email switch on or off.
On the sign-in and sign-up pages, click Privacy & tracking under the form to change the same switch.
The Privacy notice link opens Omniconvert's privacy notice for Commander in a new tab.
Who can see your data
Your data is kept apart per brand. A team member sees only the brands they belong to. The Team tab shows each person's role. See Team and roles.
Disconnect a source
Disconnect removes the access that Commander stored. For Meta Ads and Google Ads, the Commander app stays in the list of connected apps in your Meta or Google account until you remove it there.
- Open Settings > Integrations.
- Click the card of the source.
- Click Disconnect. Triple Whale, Klar and Blueshift name the button Disconnect Triple Whale, Disconnect Klar and Disconnect Blueshift.
Meta Ads, Google Ads, GA4, Triple Whale, Klar and Blueshift offer this button. Each guide under Integrations explains what it does. To remove the Shopify connection, uninstall Commander in Shopify Admin.
For a question about your data, see Contact support.