AIBBLE

https://aibble.com


ENTERPRISE COOKIES & TRACKING TECHNOLOGIES POLICY

Effective Date: May 22, 2026  |  Last Updated: May 22, 2026

Governing Jurisdiction: Wayne County, Detroit, Michigan

This Cookies Policy is a legally operative component of aibble's Enterprise Privacy Policy and Terms & Conditions. It governs ALL tracking technologies and data storage mechanisms deployed across aibble.com and all associated GoHighLevel-powered sub-account funnels, calendars, order forms, webchat widgets, membership portals, and affiliated digital properties. By continuing to use our website after reviewing this Policy, or by clicking "Accept" on our consent banner, you consent to the deployment practices described herein, subject to your full control rights in Section 7.

1.  Scope, Applicability & Relationship to Other Policies

This Cookies & Tracking Technologies Policy ("Cookies Policy") is published by aibble, LLC ("aibble," "We," "Us," or "Our"), a Michigan limited liability company operating at https://aibble.com. This Policy covers the full spectrum of cookies, web beacons, tracking pixels, session replay scripts, LocalStorage entries, SessionStorage entries, device fingerprinting technologies, and server-side tracking mechanisms deployed across our digital properties — including all GoHighLevel-powered funnel pages, scheduling widgets, order forms, webchat interfaces, membership portals, eCommerce checkouts, and survey tools hosted on or connected to our infrastructure.

This Cookies Policy supplements and is incorporated by reference into aibble's Enterprise Privacy Policy. All data collected through tracking technologies described herein is processed per the legal bases, retention schedules, and Data Subject rights in the Privacy Policy. In the event of conflict, the Privacy Policy controls.

2.  What Are Cookies & Tracking Technologies?

2.1  Cookies

Cookies are small text files deposited into your web browser's storage when you load a webpage. Each cookie contains a name, a value, a domain scope, an expiry date, and security transmission flags. They enable platforms to recognize returning users, preserve session state, maintain authentication, and deliver personalized experiences across page loads.

2.2  Browser Cookies vs. LocalStorage vs. SessionStorage

  • Browser Cookies: Traditional cookies transmitted with every HTTP request to the issuing domain. Readable by both server and client. Subject to expiry dates set at creation.

  • LocalStorage: Browser-based key-value storage that persists indefinitely until manually cleared by the user or programmatically deleted. Not transmitted with HTTP requests. Used for preserving form state, cart data, session history, and platform configuration across visits.

  • SessionStorage: Temporary key-value storage that is automatically purged when the browser tab or window is closed. Used for transient data like order responses, redirect URLs, and active form submission state.

All three storage mechanisms are employed within aibble's GoHighLevel-powered infrastructure and are disclosed in full in the cookie inventory in Section 4.

2.3  First-Party vs. Third-Party Technologies

  • First-Party: Set directly by aibble or GoHighLevel under the aibble.com domain. Used for platform functionality, session management, attribution, and eCommerce operations.

  • Third-Party: Set by external providers (Google, Meta, LinkedIn, Stripe, Twilio) through embedded scripts. These providers may aggregate your data across their broader network of publisher sites independently of your interaction with aibble.

2.4  Web Beacons, Tracking Pixels & Email Pixels

Web beacons (tracking pixels) are microscopic, invisible graphic elements embedded in web pages or HTML email messages. Unlike cookies, they transmit data to a remote server at the moment the page or email renders. aibble deploys email open-tracking pixels in commercial email communications — these record email render timestamp, approximate geographic region (IP-derived), and device category for campaign performance measurement. You may disable email pixel tracking by disabling automatic image loading in your email client settings.

2.5  Session Replay & Behavioral Heatmap Scripts

aibble deploys session replay and heatmap tools that record anonymized behavioral interactions — mouse movement, click events, scroll depth, and form interaction patterns — to optimize conversion pathways. All personal identifiers (names, emails, payment data) are masked before recording. Session replay is classified as Analytics (non-essential) and requires your consent.

2.6  Device Fingerprinting & Google reCAPTCHA v3

aibble deploys Google's Invisible reCAPTCHA v3 as a silent background security engine across all forms, scheduling widgets, and funnels. reCAPTCHA analyzes hardware telemetry, browser environment, behavioral signals, and Google's global threat intelligence to distinguish human users from automated bots. Four reCAPTCHA storage entries are deployed (GRECAPTCHA, _grecaptcha, rc::f, rc::b) — all classified Strictly Necessary and not subject to consent opt-out. Data is governed by Google's Privacy Policy.

2.7  Server-Side Tracking (Meta Conversions API)

In addition to browser-based pixels, aibble deploys the Meta Conversions API (CAPI) for server-to-server conversion event transmission. When a conversion occurs on our properties, our server transmits SHA-256-hashed event data directly to Meta — bypassing browser-side blockers (iOS ATT, Safari ITP, ad blockers). Hashed data cannot be reverse-engineered. CAPI transmissions are suppressed for sessions where marketing cookies have been declined or a GPC signal detected, within 48 hours of opt-out processing.

2.8  Cross-Device & Attribution Tracking

aibble's GoHighLevel Attribution framework and third-party advertising partners (Google, Meta, LinkedIn) employ session and cross-device tracking to link behavioral signals across devices and sessions, analyze the full conversion journey from first touch to lead capture, and attribute campaign performance to specific traffic sources. Attribution cookies store referrer data, landing page URL, UTM parameters, and page visit history. This data is used for internal marketing optimization only and is not sold to third parties.

2.9  Affiliate Marketing Tracking

aibble's GoHighLevel infrastructure includes affiliate marketing tracking capabilities. If you arrive at aibble.com via an affiliate link, our system deploys affiliate-specific cookies (am_id, am_fingerprint) to record and attribute the click, lead, and any resulting transaction to the originating affiliate partner. This data is used exclusively for affiliate commission calculation and is not shared with advertising networks.

3.  Legal Framework for Cookie Deployment

3.1  GDPR & ePrivacy Directive (EU/UK Visitors)

Cookie deployment for EEA/UK visitors is governed by GDPR Article 6 and the EU ePrivacy Directive (Directive 2002/58/EC). Strictly Necessary cookies are deployed on the lawful basis of Legitimate Interests (GDPR Art. 6(1)(f)) as they are technically required for secure platform operation. All non-essential cookies are deployed exclusively on the basis of your freely given, specific, informed, and unambiguous Consent (GDPR Art. 6(1)(a)) via our Consent Management Platform. Consent may be withdrawn at any time without detriment.

3.2  CCPA / CPRA & U.S. State Privacy Laws

For California residents and residents of states with enacted consumer privacy legislation: deployment of cross-context behavioral advertising cookies constitutes "sharing" of Personal Data under the CPRA. You have the right to opt out at any time via our Cookie Preference Center or by transmitting a Global Privacy Control (GPC) browser signal. aibble does not sell cookie-collected data for monetary consideration.

3.3  Consent Record-Keeping

aibble records all consent events including: timestamp; policy version; cookie categories accepted or declined; consent mechanism used; and anonymized session identifier. Records are maintained for a minimum of three (3) years and are available for regulatory audit.

4.  Complete Cookie & Data Storage Inventory

The following inventory discloses every cookie, LocalStorage entry, and SessionStorage entry deployed across aibble.com and all associated GoHighLevel-powered properties. The inventory is organized by functional category and reviewed quarterly. "Persistent" entries without a stated expiry are retained until manually cleared by the user or programmatically deleted by the platform.


CATEGORY 1 — Strictly Necessary / Essential Platform Cookies

These cookies and storage entries are technically indispensable for core platform functionality. They cannot be disabled without breaking login, payment processing, form submission, and session state management. They do not track behavior for advertising purposes.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

msgsndr_id

Browser Cookie

GoHighLevel Funnels

Identifies visitor contact information and facilitates user-contact activity tracking across funnel pages.

365 Days

_mp

Browser Cookie

GoHighLevel Funnels

Stores marketplace information; tracks user purchases including recurring payment events.

365 Days

tr

Browser Cookie

Funnels / Forms

Generates a unique tracking ID for order and transaction tracking across funnel flows.

365 Days

provider

Browser Cookie

GoHighLevel Funnels

Stores the latest payment method type selected during the current user session.

Session

hl_timer_arrival

Browser Cookie

GoHighLevel Funnels

Stores arrival timestamp and timer element ID for user action tracking on timer-enabled funnel pages.

1 Day

user-email

Browser Cookie

GoHighLevel Funnels

Stores the user's email address to facilitate form pre-population and submission tracking.

365 Days

user-billing-id

Browser Cookie

GoHighLevel Funnels

Stores the unique billing identifier for the user to facilitate billing-related user actions.

365 Days

cookie-config

Browser Cookie

GoHighLevel Funnels

Stores cookie consent preferences — the record of user permission to deploy non-essential cookies.

6 Months

_ud

LocalStorage

Forms / Surveys / Cal

Stores form and survey data entered during session (credit card info is explicitly excluded).

Persistent

wl

LocalStorage

GoHighLevel Calendar

Stores the whitelabel URL used for redirect handling within calendar and booking flows.

Persistent

ln_url

LocalStorage

GoHighLevel Funnels

Stores the LeadConnector login URL for redirect navigation within funnel environments.

Persistent

storeInfo

Browser Cookie

eCommerce Store

Stores eCommerce store configuration including locationId, storeId, and store path.

No Expiry

token_[variable]

Browser Cookie

eCommerce Store

Stores the eCommerce session login token required for authenticated storefront access.

No Expiry

orderResponse

SessionStorage

GoHighLevel Funnels

Stores the order form response data required for upsell flows and order confirmation pages.

Session

contactResponse

SessionStorage

GoHighLevel Funnels

Stores contact response data for order forms, upsell sequences, and sticky contact functionality.

Session

redirect

SessionStorage

eCommerce

Stores the post-purchase redirect URL for eCommerce flows.

Session

redirectUrlOnSuccess

SessionStorage

Funnels / Forms / Cal

Stores the order form success redirect URL for IDEAL, SEPA, and BANCONTACT payment providers.

Session

redirectUrlOnFailure

SessionStorage

Funnels / Forms

Stores the order form failure redirect URL for IDEAL, SEPA, and BANCONTACT payment providers.

Session

*formData-[variable]

SessionStorage

GoHighLevel Funnels

Stores form submission data including product-related information for session duration.

Session

*submissionResponse-[variable]

SessionStorage

GoHighLevel Funnels

Stores form submission response values for session-level confirmation handling.

Session


CATEGORY 2 — GoHighLevel Attribution & Session Tracking

These entries power GoHighLevel's attribution engine, tracking visitor journeys from first landing through lead capture. They store referrer data, UTM parameters, session IDs, and full page visit history to enable accurate marketing attribution and campaign optimization.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

v3_first_session_event_[location_id]

LocalStorage / Browser

GHL Attribution

Stores first-session landing data including referrer URL, landing page, and UTM parameters.

30 Minutes

v2_contact_session_[location_id]_[session_id]

LocalStorage / Browser

GHL Attribution

Stores unique session ID used for lead identification and contact-session linking.

7 Days

v2_user_session_event_[location_id]_[session_id]

LocalStorage / Browser

GHL Attribution

Stores unique session ID for user-level lead identification across attribution events.

7 Days

v2_session_history_[location_id]

LocalStorage

GHL Attribution

Maintains a log of all session details for full-funnel attribution analysis.

Permanent

v2_history_[location_id]

LocalStorage

GHL Attribution

Records each page visited and time spent per page to track the complete user journey.

Permanent

hl_timer_[element_id]

Browser Cookie

GoHighLevel Funnels

Stores timer element data for countdown-based user action tracking on funnel pages.

1 Day

location_[variable]

Browser Cookie

GoHighLevel Funnels

Stores location identifier, user email, and billing info to facilitate form actions.

365 Days


CATEGORY 3 — GoHighLevel eCommerce, Order Forms & Cart

These entries support GoHighLevel-powered order forms, shopping cart functionality, eCommerce checkouts, and upsell flows. They are classified Essential or Functional as they are required for transaction processing and order confirmation.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

pmt_[variable]

LocalStorage

Order / Product Forms

Stores payment provider configuration for a specific contactId across order form interactions.

No Expiry

user_[variable]

LocalStorage

Calendars / Forms

Stores form submission data for the current session, excluding payment card information.

No Expiry

billingaddress

LocalStorage

Checkout Page

Stores billing address information to enable faster eCommerce checkout completion.

No Expiry

pl[funnel_id]

LocalStorage

GoHighLevel Funnels

Stores v2 order form product details for order confirmation page rendering.

Permanent

plv1_[funnel_id]

LocalStorage

GoHighLevel Funnels

Stores v1 order form product details for legacy order confirmation page rendering.

Permanent

plecom_[variable]

LocalStorage

eCommerce

Stores product details for display in the eCommerce order summary and thank-you page.

Permanent

address[funnel_id]

LocalStorage

Funnels / eCommerce

Stores the contact address for display on order form confirmation and receipt pages.

Permanent

cart_details_[funnel_id]

LocalStorage

eCommerce

Persists shopping cart contents across the user session to prevent cart data loss.

Permanent

couponSessionId_[funnel_id]

SessionStorage

Funnels / eCommerce

Stores coupon session identifier for one-time product coupon validation.

Session


CATEGORY 4 — GoHighLevel Affiliate Marketing Tracking

These cookies are deployed exclusively when you arrive at aibble.com via an affiliate referral link. They enable accurate attribution of clicks, leads, and sales to affiliate partners for commission calculation. Affiliate tracking data is not shared with advertising networks.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

am_id

Browser Cookie

GHL Affiliate Module

Stores the unique affiliate code used to attribute traffic and sales to a specific affiliate partner.

Persistent (varies)

am_fingerprint

Browser Cookie

GHL Affiliate Module

Stores a unique identifier for the affiliate-linked visit to track clicks, leads, and resulting sales.

Persistent (varies)


CATEGORY 5 — GoHighLevel Webchat Widget

These entries are deployed by the GoHighLevel-powered webchat widget embedded on aibble.com. They preserve chat session continuity, save contact details to reduce re-entry friction, and store display state preferences. Personal data entered in the chat widget is governed by the full Privacy Policy.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

lead-connecter-text-widget-input-values

LocalStorage

GHL Chat Widget

Stores the last chat session user details (name, email) so they are pre-populated on return visits.

Persistent

lead-connecter-text-widget-i18n-keys

SessionStorage

GHL Chat Widget

Stores internationalization (i18n) translation keys for widget interface language rendering.

Session

lead-connecter-text-widget-prompt-dismissed

LocalStorage

GHL Chat Widget

Records the timestamp of the last time the user clicked the chat widget prompt.

365 Days

_lead-connecter-live-widget-message-data

LocalStorage

GHL Chat Widget

Saves the user's last input in the chat widget so fields are pre-filled on next visit.

365 Days

ghl_chat_widget

Browser Cookie

GHL Chat Widget

Maintains active webchat session thread ID for conversation continuity across page navigation.

Session


CATEGORY 6 — GoHighLevel Membership, Calendar, Forms & Surveys

These entries support GoHighLevel's membership access control, appointment scheduling, form embed configurations, and survey tools. They are classified Essential or Functional as they enable core platform features.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

mf_[location_id]

Browser Cookie

GHL Membership

Stores membership access credentials once a membership is purchased via an order form.

Persistent

user_data_[calendar_id/location_id]

Browser Cookie

GHL Calendar

Stores calendar and booking form data entered during session (credit card info excluded).

Persistent

embedCode[surveyId]

Browser Cookie

GHL Forms

Maintains embed code configuration settings for embedded form and survey deployments.

Permanent

survey_temp_slides_[surveyId]

Browser Cookie

GHL Surveys

Retains survey slide configuration settings between sessions for multi-step surveys.

Permanent


CATEGORY 7 — Security & Anti-Fraud (Google reCAPTCHA v3)

Google reCAPTCHA v3 operates as a silent, continuous background security engine deployed across all aibble.com forms, funnels, scheduling widgets, and checkout pages. It uses device fingerprinting and behavioral analysis to distinguish human users from automated bots without requiring user interaction. These entries are classified Strictly Necessary and cannot be disabled without disrupting form security. Processing is governed by Google's Privacy Policy.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

GRECAPTCHA

Browser Cookie

Google reCAPTCHA v3

Primary device fingerprint and bot risk score storage. Analyzes hardware telemetry, browser env, and behavioral signals.

6 Months

_grecaptcha

LocalStorage

Google reCAPTCHA v3

Stores reCAPTCHA verification data for form security validation across funnel and website interactions.

Persistent

rc::f

LocalStorage

Google reCAPTCHA v3

Internal reCAPTCHA session data used for challenge processing and bot verification logic.

No stated expiry

rc::b

SessionStorage

Google reCAPTCHA v3

Internal reCAPTCHA challenge response data used for session-level bot verification.

Session


CATEGORY 8 — Analytics & Performance (Google Analytics / Tag Manager)

Analytics cookies enable aibble to understand how visitors navigate our platform, which content drives engagement, and where conversion friction occurs. Data is processed in aggregated, anonymized form and is not shared with advertising networks for behavioral targeting. These cookies require your consent and can be declined via our consent banner.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

_ga

Browser Cookie

Google Analytics 4

Distinguishes unique visitors via an anonymized client ID. Core GA4 user identification mechanism.

2 Years

ga[ID]

Browser Cookie

Google Analytics 4

Persists GA4 measurement session state and engagement data across page loads.

2 Years

_gid

Browser Cookie

Google Analytics 4

Differentiates individual users across a 24-hour measurement window.

24 Hours

gatgtag

Browser Cookie

Google Tag Manager

Rate-limits the frequency of analytics data requests to prevent API throttling.

1 Minute

mf_[session_id]

Browser Cookie

Session Replay Tool

Anonymized session identifier for heatmap recording and scroll depth tracking. All PII masked.

90 Days


CATEGORY 9 — Marketing, Retargeting & Conversion Pixels

Marketing cookies enable aibble to serve relevant promotional content to visitors across third-party advertising networks after they leave our website. They also facilitate conversion attribution — connecting advertising spend to lead and sales outcomes. These cookies constitute "sharing" of Personal Data under CCPA/CPRA and are subject to your opt-out rights. They are deployed only upon your affirmative consent.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

gclau

Browser Cookie

Google Ads / GTM

Measures conversion events between Google Ads campaigns and on-site actions.

90 Days

_fbp

Browser Cookie

Meta Pixel (Facebook)

Identifies browsers across sites for ad attribution and retargeting via Meta's advertising network.

90 Days

_fbc

Browser Cookie

Meta Pixel (Facebook)

Stores the Facebook Click ID from inbound Meta ad clicks for conversion attribution.

90 Days

fr

Browser Cookie

Meta Platforms

Powers cross-site interest-based advertising delivery on Facebook and Instagram.

90 Days

li_fat_id

Browser Cookie

LinkedIn Insight Tag

Member indirect identifier for LinkedIn conversion tracking and B2B retargeting.

30 Days

AnalyticsSyncHistory

Browser Cookie

LinkedIn Insight Tag

Stores information about sync timing between aibble.com and LinkedIn's advertising systems.

30 Days

UserMatchHistory

Browser Cookie

LinkedIn Insight Tag

Synchronizes LinkedIn's advertising user identifier across partner site visits.

30 Days


CATEGORY 10 — Payment Processing Infrastructure (Stripe)

Stripe payment cookies are deployed during checkout and payment processing flows. They enable fraud detection, payment session continuity, and secure token management. aibble does not store raw payment card data on its own servers. All payment data is processed exclusively within Stripe's PCI-DSS-compliant infrastructure.


Cookie / Key Name

Storage Type

Service / Provider

Purpose

Lifespan

stripe_mid

Browser Cookie

Stripe, Inc.

Fraud detection and payment session continuity for Stripe-powered checkout flows.

1 Year

stripe_sid

Browser Cookie

Stripe, Inc.

Secure payment session identifier and tokenization management during active checkout.

Session


5.  Category Classification Reference

Each cookie and storage entry in this Policy is classified under one of the following categories. These classifications govern consent requirements and opt-out applicability:

  • Strictly Necessary / Essential: Required for core platform security, authentication, payment processing, form submission, and session state. Deployed automatically. Cannot be disabled without breaking platform functionality. No consent required under applicable law.

  • Functional: Enhance the user experience by preserving preferences, chat session data, and platform configuration. Non-essential but improve usability. Subject to consent in EU/UK jurisdictions.

  • Analytics: Enable measurement of visitor behavior, conversion performance, and UX optimization. Aggregated and anonymized. Subject to consent and fully opt-outable.

  • Marketing: Power retargeting advertising and conversion attribution across third-party advertising networks. Constitute 'sharing' under CCPA/CPRA. Subject to consent and opt-out rights.

6.  Third-Party Provider Privacy Policies

Third-party cookies are governed by the independent privacy policies of their respective providers. aibble is not responsible for third-party data practices. Review each provider's policy:

7.  Your Consent Rights & Complete Control Architecture

7.1  On-Site Consent Management Platform (CMP)

Upon your first visit to aibble.com, our Consent Management Platform presents a granular consent interface offering: Accept All (all categories authorized); Essential Only / Reject All Non-Essential (blocks Analytics, Marketing, and Social/SSO — only Strictly Necessary cookies deploy); and Manage Preferences (category-level independent accept/reject). Your selection is recorded with a timestamp and policy version identifier. Preferences can be modified anytime via the "Cookie Preferences" link in the footer of any aibble.com page.

7.2  Global Privacy Control (GPC) Signal

aibble automatically detects and honors GPC browser signals in compliance with CPRA § 1798.135. A GPC signal is treated as equivalent to selecting Essential Only on our consent banner and also suppresses Meta CAPI event transmission within 48 hours. GPC-compatible browsers include Firefox (with Privacy Badger), Brave (native), DuckDuckGo (native), and Chrome (with GPC extension). Verify GPC support at https://globalprivacycontrol.org.

7.3  Do Not Track (DNT)

aibble acknowledges DNT signals for Google Analytics suppression in compliance with CalOPPA. DNT scope is narrower than GPC — we recommend GPC for the broadest opt-out coverage.

7.4  Browser-Level Controls

  • Google Chrome: Settings > Privacy and Security > Cookies and Other Site Data

  • Apple Safari: Preferences > Privacy > Manage Website Data

  • Mozilla Firefox: Settings > Privacy & Security > Cookies and Site Data

  • Microsoft Edge: Settings > Cookies and Site Permissions

  • Brave Browser: Settings > Privacy and Security > Cookies

Note: Blocking Strictly Necessary cookies at the browser level will impair core features including login, payment processing, form submission, and cart functionality.

7.5  LocalStorage & SessionStorage Clearing

Browser-level cookie controls do not automatically clear LocalStorage or SessionStorage entries. To clear these: Chrome: Developer Tools > Application > Storage > Clear Site Data; Firefox: Developer Tools > Storage > Local Storage > Right-click > Delete All; Safari: Develop menu > Empty Caches (enable Develop menu in Advanced Preferences). Clearing LocalStorage will remove all GHL-attributed session history, cart data, form pre-fill data, and chat widget memory.

7.6  Industry Opt-Out Registries

7.7  Email Pixel Opt-Out

To prevent email open-tracking pixels from firing: disable automatic image loading in your email client settings, or click the unsubscribe link in any commercial email to opt out of future marketing email delivery and eliminate future pixel exposure.

7.8  Consent Withdrawal & Previously Collected Data

Consent withdrawal is prospective — it prevents future cookie deployment but does not automatically delete previously collected data. To request deletion of cookie-derived historical data, submit a formal request via our Privacy Request Portal. Certain Strictly Necessary data may be retained for fraud prevention and legal compliance per the retention schedule in the Privacy Policy.

8.  Policy Updates & Inventory Versioning

This Cookies Policy and cookie inventory are reviewed quarterly and updated whenever our marketing technology stack changes materially. Material changes are communicated via site notice at least seven (7) days prior to the effective date. Upon any material update, previously recorded consent preferences are reset and a fresh consent prompt is presented on your next visit. The "Last Updated" timestamp at the top of this Policy reflects the most recent revision. Prior versions are available upon written request to [email protected].

9.  Dispute Resolution, Binding Arbitration & Class-Action Waiver

READ CAREFULLY: This Section requires binding individual arbitration and waives class-action rights for all cookie and tracking-related disputes.

Any legal dispute or controversy arising out of this Cookies Policy, our web tracking technologies, pixel installations, LocalStorage practices, server-side tracking, or cookie-derived data processing shall be resolved as follows:

  • Pre-Dispute Notice Requirement: The complaining party must deliver written notice to aibble at [email protected] describing the dispute in reasonable detail and allow thirty (30) calendar days for good-faith informal resolution before initiating any formal proceeding.

  • Binding Individual Arbitration: Disputes not resolved within 30 days are submitted to final, binding, individual arbitration administered by the American Arbitration Association (AAA) under its Commercial Arbitration Rules. Hearings shall be conducted in Wayne County, Detroit, Michigan.

CLASS-ACTION WAIVER: YOU EXPLICITLY AND IRREVOCABLY WAIVE ANY RIGHT TO INITIATE, JOIN, OR PARTICIPATE IN ANY CLASS-ACTION LAWSUIT, COLLECTIVE ARBITRATION, OR REPRESENTATIVE ACTION REGARDING OUR COOKIE, TRACKING, OR DATA STORAGE PRACTICES. ALL CLAIMS MUST BE BROUGHT SOLELY IN AN INDIVIDUAL CAPACITY. THIS WAIVER IS A MATERIAL, NON-SEVERABLE CONDITION OF THIS POLICY.

  • Governing Law & Venue: This Policy is governed exclusively by the laws of the State of Michigan. The exclusive venue for all arbitration and any permitted court actions is Wayne County, Detroit, Michigan.

10. Compliance Contact & Data Request Channels

For all questions regarding this Cookies Policy, consent withdrawal, cookie inventory inquiries, or cookie-derived data deletion requests, contact our Compliance Office:

  • Compliance Email: [email protected]  |  Subject: "Cookie Policy Inquiry — [Topic]"

  • Privacy Request Portal: https://aibble.com/privacy-requests

  • Business Telephone: 313-889-7656

  • Registered Mail: aibble, LLC, Attn: Compliance Office, 2785 E Grand Blvd, Unit 169, Detroit, MI 48211


All consent withdrawal and data deletion requests are acknowledged within five (5) business days and processed within the timeframes mandated by applicable law.


© 2026 aibble, LLC. All Rights Reserved.  |  2785 E Grand Blvd, Unit 169, Detroit, MI 48211

Enterprise Cookies Policy — Effective May 22, 2026 — Governing Law: State of Michigan

Wayne County, Detroit, Michigan — Exclusive Arbitration Venue


Image

Innovation

Fresh, creative solutions.

Image

Integrity

Honesty and transparency.

Excellence

Excellence

Top-notch services.

FOLLOW US

COMPANY

CUSTOMER CARE

Copyright 2026. Aibble. All Rights Reserved.