Cookie Policy
This Cookie Policy explains how Adgrowth.io uses cookies, local storage, session storage, scripts, and similar storage/access technologies on https://adgrowth.io, public marketing pages, and the Adgrowth.io product app.
Last updated: April 27, 2026 • Effective date: April 27, 20261. Summary
- Essential storage keeps login, security, workspace routing, and product continuity working.
- Functional storage remembers user choices such as selected workspace, setup progress, and chat continuity.
- First-party analytics storage is used on public pages only after you choose Accept analytics.
- Lead form follow-up uses separate email or WhatsApp consent and does not depend on analytics consent.
- No advertising pixels are loaded by the public cookie banner.
2. Consent Choices
On public pages where tracking is loaded, the banner offers Essential only and Accept analytics. Essential-only mode still allows storage needed for security, routing, saved consent, and requested product features. Analytics mode lets us create a first-party anonymous visitor ID and record public page views.
You can change your choice from the footer Cookie settings control. If your browser sends Global Privacy Control or Do Not Track, Adgrowth.io keeps first-party analytics off and the banner explains that only essential storage is used.
3. Public Website Storage We Control
| Name | Technology | Category | Purpose | When Set | Retention |
|---|---|---|---|---|---|
| ag_tracking_consent | Local storage | Essential / consent record | Stores your analytics choice, consent version, source, and timestamp so we do not ask on every page view. | When you select Essential only, Accept analytics, or acknowledge a browser privacy signal. | Until you change the setting, clear browser storage, or we require a fresh consent version. |
| ag_visitor_id | Local storage | First-party analytics | Creates an anonymous visitor label for public page-view analytics and source attribution. | Only after you select Accept analytics. | Until browser storage is cleared or analytics consent is reset. Server-side analytics records are normally retained for up to 13 months unless a shorter operational period applies. |
4. Product App Storage We Control
| Name or Pattern | Technology | Category | Purpose | Retention |
|---|---|---|---|---|
| gp_access_token | Local storage | Essential authentication | Stores the current authenticated API access token so app pages can call protected endpoints. | Until sign-out, session replacement, expiration handling, or browser storage clearing. |
| gp_user_id | Local storage | Essential account continuity | Identifies the signed-in or placeholder user for campaign ownership, conversations, and protected routes. | Until sign-out or browser storage clearing. |
| gp_organization_id, gp_workspace_id | Local storage | Functional workspace continuity | Remembers the selected organization and workspace for dashboards, campaigns, SEO, settings, and integrations. | Until sign-out, workspace change, or browser storage clearing. |
| gp_bootstrap_done_* | Local storage | Functional onboarding continuity | Prevents repeating first-login organization/workspace setup for the same user. | Until browser storage is cleared or account setup is reset. |
| gp_conv_id | Local storage | Functional chat continuity | Lets the campaign chat resume the current conversation after refresh or navigation. | Until the conversation is cleared, replaced, or browser storage is cleared. |
| adgrowth_ui_preferences and similar product guidance keys | Local storage | Functional UI preference | Remembers non-essential interface preferences such as dismissed setup prompts or guidance panels. | Until browser storage is cleared or the interface preference version changes. |
| sb-*-auth-token or similar provider-managed keys | Local storage / provider storage | Essential authentication | Used by the Supabase browser auth SDK to maintain secure login state and OAuth sessions. | Controlled by Supabase session settings, logout, token expiry, or browser storage clearing. |
5. What We Do Not Use the Public Banner For
- The public cookie banner does not load Meta Pixel.
- The public cookie banner does not load Google remarketing tags.
- The public cookie banner does not load LinkedIn Insight Tag.
- The public cookie banner does not upload visitor lists, customer lists, or lead-form data to ad platforms.
- Ad platform publishing and account connections are separate product workflows that require user action inside the app.
6. Third-Party Technologies
Some product features rely on third-party services. These providers may use their own cookies or storage when you log in, connect accounts, visit their domains, or use an embedded provider workflow. Their policies apply to those provider-controlled technologies.
| Provider / Platform | Where It Applies | Purpose | When Used |
|---|---|---|---|
| Supabase | Product login, signup, OAuth, and session handling. | Authentication, session management, account security, and workspace access. | When you use the product app or sign in. |
| Meta, Google, LinkedIn | Ad account connection, platform authorization, draft publishing, and platform handoff workflows. | Account linking, ad account discovery, campaign draft creation, and platform review. | Only when you explicitly connect or use the relevant platform workflow. |
| WordPress, Shopify, webhooks | Publishing connectors for SEO blogs, pSEO drafts, and SEO recommendations. | Destination setup, connector testing, and publishing content to selected sites. | Only when you configure or publish through a connector. |
| AI, hosting, monitoring, and email delivery providers | Backend product services rather than public website tracking pixels. | AI generation, infrastructure, diagnostics, support, and lead notification delivery. | When required to deliver requested product or support workflows. |
7. Analytics, Leads, and Consent Boundaries
Analytics consent and contact consent are separate. Accepting analytics lets us measure public page visits with first-party analytics. Submitting a lead form requires a separate email or WhatsApp opt-in and may include your name, company, email, phone, message, selected channel, source URL, and proof of consent.
If you choose Essential only, you can still submit a lead form, log in, use product workflows, and manage connected accounts. We do not deny the public website because analytics is rejected.
8. Retention and Deletion
- Local browser storage remains on your device until it expires, is replaced, or you clear it.
- Authentication storage is removed or replaced during logout/session changes where the app controls it.
- Server-side public analytics records are normally retained for up to 13 months unless a shorter operational period applies.
- Security, consent, billing, support, and audit records may be retained where legally or operationally required.
9. How to Manage Preferences
- Use Cookie settings in the footer to reopen the Adgrowth.io consent banner.
- Use your browser settings to block, inspect, or delete cookies and local storage for adgrowth.io.
- Use logout to clear app-controlled auth context on shared devices.
- Use browser privacy controls such as Global Privacy Control or Do Not Track where supported.
- Blocking all essential storage may prevent login, workspace routing, campaign chat, and connected-account workflows from working correctly.
10. Changes to this Policy
We update this policy when product features, storage behavior, providers, or legal requirements change. If analytics or advertising tracking materially changes, we may request a fresh consent choice.
11. Contact
For cookie and privacy questions: privacy@adgrowth.io
Website: https://adgrowth.io