Cookie Policy
This policy explains the small number of identifiers Argus Grape relies on. The short version: we set no third-party advertising or retargeting cookies. We use strictly-necessary browser storage to keep you signed in and remember your preferences. Everything else — anonymous analytics (our funnel pixel and a self-hosted, cookieless analytics tool) and the support chat widget — is non-essential and consent-gated: none of it loads until you accept the cookie banner.
Effective June 17, 2026 · v2026.06.1
What we mean by cookies and storage
“Cookies” is the common name for several browser mechanisms a website can use to remember information between requests: HTTP cookies, and the related localStorage and sessionStorage APIs. This policy covers all of them, plus the one tracking identifier our edge service appends to links. It should be read together with our Privacy Policy, which explains what personal data we process and the rights you have over it.
We set no advertising cookies; analytics is optional
The Argus Grape marketing website and customer dashboard set no third-party advertising, retargeting, or social-media tracking cookies, and we load no advertising pixels. We do use three non-essential, consent-gated items, all off by default and loaded only after you choose Accept in the cookie banner shown on your first visit:
(1) an anonymous intention pixel for our own conversion funnel (aggregate page views — no advertising identifier, no cross-site profile); (2) a self-hosted, cookieless analytics tool; and (3) the support chat widget (which sends the text you type to a third-party AI provider to generate replies — see the Privacy Policy). If you decline — or simply ignore the banner, or send a Global Privacy Control signal — none of these load and the site works identically. You can change your mind any time by clearing this site’s storage (see below), which makes the banner appear again.
Everything else we rely on is strictly-necessary browser storage: a small amount of localStorage and sessionStorage in your browser (including the record of your cookie-banner choice), plus the session needed to keep you authenticated. These are essential to operate the service — without them you could not sign in or stay signed in — so they do not require consent under applicable law.
The argus_cid tracking identifier
Argus Grape is a server-side affiliate-tracking platform, so the identifier that does the actual attribution work is argus_cid — and it is worth explaining clearly because it is not a cookie we set on your device. When someone clicks an affiliate link, our edge tracker handles GET {edge}/r/:affiliate_id, generates a cryptographic 128-bit click identifier, and issues an HTTP 302 redirect to the campaign destination with the click id appended as ?argus_cid=<32-hex>.
From that point the identifier lives in the destination URL on the merchant’s own website. A merchant’s site may choose to read argus_cid from the URL and persist it client-side — for example in sessionStorage — so that it can attach the identifier to a later purchase and have that conversion credited to the right affiliate. That storage happens on the merchant’s domain, under the merchant’s control, and is governed by the merchant’s own cookie and privacy notices, not this one. Argus Grape never stores a plaintext IP address at the click layer; the click record holds only salted hashes (a device fingerprint and an ip_hash) and the redirect itself.
Identifiers at a glance
The table below lists every identifier involved in using Argus Grape, what kind it is, what it does, and who sets it.
| Identifier | Type | Purpose | Set by |
|---|---|---|---|
app-state | localStorage (browser) | Strictly-necessary: keeps you signed in and remembers dashboard preferences such as layout and theme. | Argus Grape dashboard |
argus_cid | URL parameter / sessionStorage | Affiliate attribution: links a click to a later conversion. May be persisted by the merchant site to credit the conversion. | Merchant site (on its own domain) |
| Intention pixel | Third-party script + localStorage (optional, consent-gated) | Anonymous funnel analytics — aggregate page views and engagement. No advertising identifier, no cross-site profile. | Zylior (loaded by Argus Grape only on consent) |
| Self-hosted analytics | Self-hosted script, cookieless (optional, consent-gated) | Aggregate, cookieless traffic analytics on our own infrastructure. Loaded only after you accept; production only. | Argus Grape |
| Support chat widget | Third-party script + storage (optional, consent-gated) | Loads the on-site support/feedback chat; messages you type are sent to a third-party AI provider to generate replies. Loaded only after you accept. | Support chat widget |
argus_cookie_consent_v2 | localStorage (browser) | Strictly-necessary: remembers your Accept/Decline choice for the optional trackers above so the banner isn't shown again. | Argus Grape marketing site |
| Payment processor | Third-party (checkout only) | Payment processing and fraud prevention when you purchase or manage a paid plan; set only on the processor's hosted checkout. | Payment processor |
The payment-processor entries appear only during checkout on the processor’s own hosted pages, where they are necessary to take payment securely. They are not set while you simply browse the marketing site or use the dashboard.
How to control or clear browser storage
Because we rely only on strictly-necessary storage, there is no setting inside Argus Grape to turn it off — disabling it would prevent you from signing in. You remain in full control through your browser, however. You can clear localStorage, sessionStorage, and cookies for any site at any time from your browser’s privacy or site-data settings, and you can configure your browser to block or delete storage when you close it.
Clearing storage for argusgrape.com will sign you out and reset your saved dashboard preferences. To remove an argus_cid value that a merchant’s site has persisted, clear the storage for that merchant’s domain rather than ours, since that data lives there.
Global Privacy Control & Do Not Track
We honor Global Privacy Control (GPC) signals where required by applicable law, and we respect comparable browser-level privacy preferences such as Do Not Track. Because we set no advertising, retargeting, or cross-site tracking cookies, and we do not sell or share your personal information, there is no ad-targeting opt-out for us to perform on your behalf.
In other words, the privacy outcome a GPC signal is meant to achieve already applies to everyone who uses Argus Grape by default — but we still respect GPC and similar signals when your browser sends them. For more on how we handle personal information and the choices available to you, see our Privacy Policy.
Changes and contact
We may update this policy as the product evolves — for example if we ever introduce a new strictly-necessary identifier. When we do, we will revise the effective date and version shown at the top of this page. For any question about how we use cookies or browser storage, contact us at legal@argusgrape.com.