Legal
Cookie Policy
Effective date: 4 August 2026 - Last updated: 4 August 2026
Three cookies, and only one of them is set before you say yes. This page lists all of them. It covers the website at primemoq.app; the Prime MOQ app inside your Shopify admin is a different surface, described in the privacy policy.
2. The four categories
Two of the four are empty today. We have kept them in the preference centre so your choice is already recorded if that ever changes, and so we are not describing a category that does not match the toggles you are shown.
Strictly necessary (always on)
These are set without asking, because the site cannot do what you asked without them. The only one we set is the cookie that records your cookie choice, which is a cookie we would have to set even to remember that you refused everything else. Under the ePrivacy Directive and the CNIL guidance on consent, a cookie strictly necessary to provide a service the user requested is exempt from consent.
Cookies in this category today: pmq_cookie_consent.
Analytics
Aggregate measurement: page views, referrers, approximate country, device type. We use it to work out which pages answer a merchant's question and which waste their time. Nothing is loaded and no analytics cookie is set until you accept this category. If you refuse, the Google Analytics script is never requested at all.
Cookies in this category today: _ga, _ga_PLL34CRS31.
Marketing
We run no advertising, retargeting or personalisation tags on primemoq.app. The toggle exists so that your choice is already on record if that ever changes, and so that Google Consent Mode receives an explicit signal for the advertising parameters rather than a silent default. Turning it on today sets nothing.
Cookies in this category today: none.
Preferences
This category would cover cookies that remember a display choice such as a language or a dismissed banner. The site sets none today. As with marketing, the toggle records your position in advance.
Cookies in this category today: none.
4. How consent works here
On your first visit, before anything else runs, the page tells Google Consent Mode that analytics storage, advertising storage, advertising user data and advertising personalisation are all denied. That default is the first script in the document, ahead of everything.
Then the Google Analytics tag is not loaded. Not loaded and denied: not loaded and waiting. Until you accept analytics, your browser makes no request to googletagmanager.com or google-analytics.com at all.
When you choose, we write pmq_cookie_consent, send a consent update matching your choice, and load the analytics tag only if you accepted analytics. Refusing is one click on the banner, in the same place and at the same size as accepting. No box is ticked in advance, and closing the banner without choosing is not treated as consent.
We record which version of this cookie list you were shown. If we add a cookie, that version changes and we ask again rather than assuming a choice you made about a shorter list still covers the longer one.
5. Changing your choice
Open the preference centre at any time, from this button, from the link in the site footer, or from the same button on the privacy policy. Withdrawing consent is exactly as easy as giving it, which is what Article 7(3) of the GDPR requires.
Withdrawing analytics consent stops any further data being collected. It does not delete what Google already holds; for that, ask us and we will pass on a deletion request, or use Google's own controls below.
6. Browser level controls
Your browser can block or delete cookies independently of anything we do, usually under privacy or site settings. Blocking the strictly necessary cookie will not break the site, but it will mean the consent banner reappears on every visit, because the record of your choice is the thing you blocked.
Google publishes a browser add-on that opts you out of Google Analytics on every site at once, at tools.google.com/dlpage/gaoptout.
We honour Global Privacy Control where a browser sends it: a GPC signal is treated as a refusal of analytics and marketing, and you will not be asked to override it.
7. Google Consent Mode v2
Consent Mode is the mechanism Google provides for telling its tags what a visitor allowed. We implement version 2, which covers four consent parameters plus two storage parameters:
| Parameter | Default | Controlled by |
|---|---|---|
| analytics_storage | denied | The Analytics toggle |
| ad_storage | denied | The Marketing toggle |
| ad_user_data | denied | The Marketing toggle |
| ad_personalization | denied | The Marketing toggle |
| functionality_storage | granted | The Preferences toggle |
| security_storage | granted | Always granted. It covers security and fraud prevention, which is strictly necessary |
Because we do not load the tag at all before consent, Consent Mode here is a second line of defence rather than the only one. If a Google tag ever arrives on this site through some route we did not intend, it will still find every advertising and analytics parameter denied.
8. Changes to this policy
When the cookie list changes, this page changes with it and the consent version is bumped, so everyone is asked again about the list that now applies. The effective date at the top is the date of the current version.
9. Contact
Aspedan Inc.
325 Front St West, Suite 300, Toronto, ON M5V 2Y1, Canada
support@primemoq.app
Questions
A person reads every message, on any plan. If something on this page is unclear, or you want to exercise a right described in it, write to us and say so plainly.