AIBBLE

https://aibble.com

ENTERPRISE PRIVACY POLICY

Version 2.0  |  Effective Date: May 22, 2026

Governing Jurisdiction: Wayne County, Detroit, Michigan

IMPORTANT NOTICE: This Privacy Policy constitutes a legally binding instrument governing ALL data collection, processing, and automated communications conducted by aibble — including SMS, MMS, email, outbound voice calls, ringless voicemail drops, webchat, and AI-generated conversational messages. By accessing aibble.com or interacting with any aibble touchpoint, you acknowledge full comprehension of and agreement to all terms herein, including mandatory binding arbitration and class-action waiver provisions.

1.  Preamble & Organizational Identity

aibble, LLC ("aibble," "the Company," "We," "Us," or "Our") is a high-performance B2B digital marketing and AI automation agency headquartered in Detroit, Michigan. Our full service architecture encompasses: Google Business Profile (GBP) optimization; outbound B2B lead generation; missed call text-back automation; SMS and MMS database reactivation; ringless voicemail (RVM) delivery; automated outbound voice broadcasting; two-way AI conversation engines; webchat lead capture; automated review request sequences; appointment booking automation; CAN-SPAM-compliant email marketing workflows; and custom CRM infrastructure delivered through the GoHighLevel platform and integrated enterprise-grade large language model (LLM) APIs.

This document is structured to satisfy the compliance review standards of sophisticated enterprise clients, Google profile verification teams, federal and state regulatory supervisory authorities, The Campaign Registry (TCR), mobile network carrier compliance divisions (AT&T, T-Mobile, Verizon), and legal counsel operating under any jurisdiction in which We conduct business or process personal data.

2.  Definitional Framework & Legal Scope

2.1  Core Definitional Architecture

• Data Controller: The legal entity determining the purposes and means of processing personal data. aibble operates as a Data Controller with respect to (i) visitors of aibble.com, (ii) prospective B2B clients identified through public data indexing, and (iii) all data voluntarily submitted via our digital properties.

• Data Processor: An entity processing personal data on behalf of a Data Controller pursuant to documented instruction. aibble operates as a Data Processor exclusively when executing automated fulfillment sequences, CRM workflows, or communication campaigns within GoHighLevel sub-account architectures on behalf of its Business Clients.

• Business Client ("Client"): Any business entity, sole proprietor, or professional engaging aibble's services. For all data residing within a Client's GoHighLevel sub-account, the Client retains sole and exclusive status as the Data Controller.

• Data Subject ("You," "Your"): Any natural person accessing our Service, interacting with our digital interfaces, communicating via our automated systems, or receiving communications generated by our platform infrastructure.

• Personal Data: Any structured or unstructured information relating to an identified or identifiable natural person, including identifiers, behavioral data, geolocation signals, device telemetry, communication records, and call transcripts.

• Sensitive Personal Data: A discrete classification including financial account credentials, government-issued identification numbers, health information, protected class characteristics, and precise geolocation. aibble does not intentionally collect Sensitive Personal Data through its public-facing Service.

• Automated Communication Modalities: The full suite of communication channels supported by aibble's infrastructure, including SMS, MMS, email, outbound automated voice calls, ringless voicemail drops, webchat, and AI-generated conversational messages — collectively subject to TCPA, CAN-SPAM, and applicable state communication statutes.

• Sub-Processor: A third party engaged by aibble (as a Data Processor) to carry out specific processing activities on behalf of a Client. All Sub-Processors are bound to equivalent data protection standards.

3.  Granular Data Collection & Technical Tracking Architecture

3.1  Voluntarily Submitted Data

We collect explicitly provided information through web forms, scheduling widgets, webchat interfaces, onboarding portals, and direct written, telephonic, or digital communications, including: full legal names, corporate titles, business entity names; electronic mail addresses, direct telephone and mobile numbers; physical business addresses, postal codes, and country; social media profile structures, business page identifiers, and SSO authentication tokens (Google Workspace, Meta Business Suite, LinkedIn); payment and billing information processed through PCI-DSS-compliant third-party processors (aibble does not store raw payment card data on its own servers); and textual communications, support requests, intake questionnaire responses, and webchat session transcripts.

3.2  Webchat & Live Chat Widget Data Collection

aibble deploys GoHighLevel-powered webchat widgets on aibble.com and, where applicable, on client-facing digital properties managed under our service agreements. When a visitor initiates a webchat session or is engaged by our automated chatbot workflow, the following data is collected:

• Name and contact information voluntarily provided during the chat session, including mobile number and email address, which may trigger TCPA-governed automated follow-up sequences upon submission with disclosed consent.

• Full verbatim transcript of the chat conversation, stored within our CRM and subject to the retention schedule defined in Section 7.

• Device type, browser type, operating system, IP address (truncated to subnet level within 30 days), and referring URL.

• Session timestamp, session duration, and page-context indicators identifying which page of our site initiated the chat.

3.3  Call Recording Disclosure — All-Party Consent Notice

IMPORTANT: aibble's telephone infrastructure, including inbound and outbound call routing powered by GoHighLevel and Twilio, may automatically record telephone calls for quality assurance, training, compliance verification, and dispute resolution purposes.

By calling any aibble-affiliated telephone number, or by receiving an inbound or outbound telephone call from our systems, you consent to the recording of that call. This disclosure satisfies the all-party call recording consent requirements of California Penal Code § 632, Illinois Eavesdropping Act (720 ILCS 5/14), Pennsylvania Wiretapping and Electronic Surveillance Control Act (18 Pa. C.S. § 5703), Florida Security of Communications Act (Fla. Stat. § 934.03), and all analogous all-party consent statutes enacted by other U.S. jurisdictions.

Call recordings are stored securely within our GoHighLevel and Twilio infrastructure for a maximum of thirty-six (36) months from the date of the recorded call, after which they are permanently deleted. Clients who utilize aibble's GHL sub-account telephone features are solely responsible for issuing appropriate call recording disclosures to their own customers prior to call initiation.

3.4  Automated Telemetry & Pixel Implementation Architecture

We deploy a structured suite of tracking technologies including: Google Analytics 4 / Google Tag Manager for behavioral flow mapping and conversion event tracking; Google Invisible reCAPTCHA v3 for continuous background bot risk analysis; Meta Pixel and Meta Conversion API (CAPI) for cross-platform audience construction and attribution; LinkedIn Insight Tag for B2B retargeting; and anonymized session replay and heatmap telemetry for UX optimization. All pixel and telemetry deployments are governed by our Cookie Consent Management Architecture described in Section 3.5.

3.5  Cookie Consent Management Architecture

Upon first access to aibble.com, Data Subjects in regulated jurisdictions are presented with a granular consent interface permitting acceptance, rejection, or category-level customization of non-essential cookies. Global Privacy Control (GPC) browser signals are automatically honored as an opt-out from cross-context behavioral advertising without requiring separate affirmative action. Cookie preferences may be modified at any time via the persistent Cookie Preference Center in our site footer.

3.6  Meta Lead Ads & Third-Party Platform Integrations

aibble integrates with Meta Lead Ads (Facebook and Instagram), Google Lead Form Extensions, and other third-party lead capture platforms via native API connections and GoHighLevel's integration layer. Data received through these integrations is governed by both the originating platform's terms of service and this Privacy Policy. The originating platform's consent documentation serves as the consent artifact for the initial data collection event. aibble does not augment, re-sell, or independently license data received through third-party lead form integrations.

4.  Legal Bases for Processing & Purpose Limitation

All processing of Personal Data by aibble is anchored to at least one lawful basis. We do not process data beyond the specific purpose for which it was collected without re-establishing a compatible legal basis or obtaining fresh consent.

• Consent (GDPR Art. 6(1)(a); CCPA/CPRA opt-in mechanisms): Applied to all Automated Communication Modalities, non-essential cookie deployment, retargeting pixel activations, and email marketing campaigns.

• Contractual Necessity (GDPR Art. 6(1)(b)): Applied to processing required to deliver agreed-upon services to Business Clients.

• Legitimate Interest (GDPR Art. 6(1)(f)): Applied to B2B outbound prospecting from publicly indexed data, platform security, fraud prevention, and product analytics. Legitimate Interest Assessments are documented internally.

• Legal Obligation (GDPR Art. 6(1)(c)): Applied to tax, accounting, anti-money laundering, and regulatory reporting obligations.

5.  Comprehensive Automated Communications Compliance (TCPA, A2P 10DLC, CAN-SPAM)

5.1  Universal Automated Communications Consent — All Modalities

MANDATORY WRITTEN CONSENT DISCLOSURE: By submitting your contact information through any aibble touchpoint, you provide TCPA-compliant written consent to receive ALL of the following automated communication types. Read each category carefully.

By submitting your mobile telephone number, email address, or other contact information through any digital interface, contact form, lead magnet, landing page, webchat session, scheduling widget, or any other touchpoint operated by or on behalf of aibble, you provide your explicit, knowing, voluntary, and irrevocable written consent — constituting a legally operative written signature for TCPA purposes under 47 U.S.C. § 227 — to receive from aibble and its authorized agents all of the following:

5.2  SMS & MMS Text Messaging

You consent to receive automated SMS and MMS text messages including: appointment confirmations, scheduling reminders, service delivery updates, account notifications, promotional marketing content, database reactivation messages, and missed call text-back notifications. Messages may be generated via automated telephone dialing systems (ATDS), AI-powered messaging engines, or programmatic workflows integrated within GoHighLevel's A2P 10DLC-registered infrastructure.

Message frequency varies based on account activity and campaign schedules, estimated at 2–6 messages per week during active engagement. Message and data rates may apply. All commercial SMS messaging is registered under The Campaign Registry (TCR) A2P 10DLC framework with compliant use case categorization.

Opt-Out: Reply STOP, END, QUIT, CANCEL, or UNSUBSCRIBE to any message. Our automated opt-out system executes immediately and issues a carrier-compliant confirmation message within one (1) business day.

5.3  Missed Call Text-Back Automation

You consent to receive an automated SMS message triggered by our missed call text-back system whenever an inbound call to any aibble-affiliated telephone number goes unanswered. This automated response is generated programmatically without live agent review and is delivered within seconds of the missed call event. This consent applies regardless of whether you have otherwise opted out of general marketing SMS, as missed call text-back constitutes a transactional communication directly related to your initiated telephone contact.

5.4  Ringless Voicemail (RVM) Drops

You consent to receive ringless voicemail messages delivered directly to your mobile or landline voicemail inbox without an audible ring event. Ringless voicemail delivery is a component of our database reactivation and outbound B2B prospecting workflows. RVM messages are pre-recorded audio files delivered via server-to-voicemail technology integrated within our GoHighLevel automation architecture. Each RVM delivery includes a verbal opt-out instruction directing recipients to reply via text or call to be removed from future voicemail sequences. This consent is required separately from SMS consent given the distinct technical delivery mechanism.

5.5  Automated Outbound Voice Broadcasting

You consent to receive automated outbound voice calls generated by our telephony infrastructure, including calls featuring pre-recorded messages or AI-voiced conversational agents. Outbound voice calls may be used for appointment reminders, service notifications, and, where permitted by applicable law, promotional outreach. Automated voice calls to residential telephone numbers require separate express written consent distinct from SMS consent. You may opt out of automated voice calls at any time by pressing the designated opt-out key during any automated call, by replying to any associated SMS, or by contacting us at [email protected].

5.6  AI Conversation Engine Communications

You consent to receive and engage with AI-generated conversational messages delivered through our two-way AI conversation engine, which may operate across SMS, webchat, and email channels. AI conversation responses are generated by large language model APIs integrated within our GoHighLevel infrastructure. At any point during an AI conversation, you may request escalation to a human agent by sending the word HUMAN to any SMS thread or clicking the escalation prompt within any webchat session.

5.7  Email Marketing (CAN-SPAM Act Compliance)

You consent to receive commercial email communications from aibble, including newsletters, service announcements, promotional offers, case studies, and educational content. All commercial email communications comply with the CAN-SPAM Act of 2003 (15 U.S.C. § 7701 et seq.) as follows:

• Sender Identification: All commercial emails clearly identify aibble as the sending entity and display our valid physical postal address in the email footer.

• Subject Line Accuracy: Subject lines accurately reflect the content of each message and are not deceptive or misleading.

• Opt-Out Mechanism: Every commercial email includes a clear, conspicuous, and functional unsubscribe link. Opt-out requests are processed within ten (10) business days of receipt and honored permanently.

• No Deceptive Headers: We do not use false or misleading routing information, forged headers, or deceptive reply-to addresses.

• Transactional Email Exemption: Service notifications, billing confirmations, onboarding instructions, and other purely transactional emails are exempt from CAN-SPAM opt-out requirements but remain subject to our general data practices.

5.8  Review Request Automation & FTC Compliance

aibble deploys automated review request sequences on behalf of Business Clients, soliciting customer feedback and review submissions via SMS and email. These sequences comply with the Federal Trade Commission's guidelines on endorsements and testimonials (16 C.F.R. Part 255) and applicable platform terms of service (Google, Yelp, Facebook). Specifically:

• Review request messages are delivered exclusively to verified customers of the Business Client who have completed a service transaction and provided documented consent to receive post-service communications.

• Review request messages do not offer compensation, incentives, or rewards contingent upon the submission of a positive review.

• Review request messages do not direct recipients to any review filtering, gating, or screening mechanism designed to suppress negative reviews in violation of the Consumer Review Fairness Act (15 U.S.C. § 45b).

• Business Clients bear sole compliance responsibility for ensuring that their customer databases used in review request sequences contain only verifiable transaction-based contacts with appropriate consent documentation.

5.9  Non-Contingency, Consent Records & Double Opt-In

Your consent to receive any automated promotional communication is entirely voluntary and is not — directly or indirectly — a condition of purchasing any property, goods, or services from aibble. Where technically feasible and campaign-appropriate, aibble employs SMS double opt-in confirmation workflows to generate a second-layer consent record that satisfies enhanced carrier compliance requirements. All consent records — including timestamp, channel identifier, IP address, opt-in source, and opt-in confirmation — are stored within our CRM for a minimum of five (5) years as required for TCPA statute of limitations defense.

5.10  Mobile Data Segregation Assurance

Mobile telephone numbers collected for SMS consent purposes are strictly isolated within a dedicated, access-controlled database segment. This information is never shared, leased, sold, syndicated, or distributed to any third-party entity, affiliate, downstream partner, or data broker for independent marketing or promotional purposes.

6.  AI Processing, LLM Data Security & Zero-Training Guarantee

6.1  Private API Execution Architecture

aibble integrates enterprise-grade LLM APIs within our service delivery infrastructure to automate lead capture, generate GBP optimization content, execute database reactivation communications, power two-way AI conversation workflows, and generate appointment booking sequences. The following safeguards are operative for all AI-mediated data processing:

• Private Enterprise-Tier Endpoints: All customer, lead, visitor, and client business data processed through our AI applications is routed exclusively through private, enterprise-tier API configurations contractually isolated from shared inference environments.

• Zero-Training Guarantee: aibble explicitly and contractually prohibits all third-party AI infrastructure providers from utilizing any data flowing through our systems — including prompts, completions, CRM data, chat transcripts, or call summaries — to train, fine-tune, optimize, benchmark, or iterate any public, commercial, or research-facing AI model. This prohibition is a material, non-negotiable term in all vendor agreements. Your proprietary operational data remains permanently isolated from model training pipelines.

• Data Minimization: Only the minimum data necessary to complete a specific AI-assisted task is transmitted to LLM endpoints. PII is pseudonymized or tokenized where technically feasible before processing.

• Audit Trail: All AI-mediated processing events are logged with timestamp, processing purpose, data category, and output disposition. Logs are retained for twenty-four (24) months and available to Business Clients upon written request.

6.2  Automated Decision-Making & Profiling

aibble does not employ fully automated decision-making processes producing legal or similarly significant effects upon Data Subjects without human review. Where AI-assisted lead scoring, audience segmentation, or campaign optimization produces outputs informing service delivery decisions, a qualified aibble team member reviews and approves the outcome prior to client-facing implementation.

6.3  B2B Legitimate Interest Data Processing (Public Index Prospecting)

The Company programmatically processes publicly available business directory data, Google Maps listings, municipal business licensing records, and corporate registry information to identify prospective B2B clients. Processing is conducted under Legitimate Interest (GDPR Art. 6(1)(f)) and applicable B2B commercial prospecting exemptions. Data categories processed are limited to: business name, registered address, publicly listed telephone number, publicly available email address, GBP URL, and publicly indexed ratings. We do not process personal residential data or individual consumer records through this mechanism. Any business owner may request immediate removal by emailing [email protected] with subject line "Opt-Out: B2B Prospecting Database." Removal executes within five (5) business days.

7.  Data Retention, Deletion & Automated Purification Architecture

7.1  Retention Schedule by Data Category

• Web Form Submissions & Lead Records: Retained 24 months from last meaningful engagement. Automated anonymization executes at 18 months of inactivity.

• Webchat Session Transcripts: Retained 24 months from session date. Anonymized at 18 months of inactivity using k-anonymity (k≥5).

• Call Recordings: Retained 36 months from call date, then permanently deleted with zero-retention parameters.

• SMS & Voicemail Consent Records (TCPA Documentation): Retained minimum 5 years from consent or last communication to satisfy TCPA statute of limitations defense and A2P 10DLC documentation standards.

• Business Client CRM & Operational Data: Retained for the duration of active engagement plus 36 months following contract termination for audit, dispute resolution, and statutory compliance purposes.

• Web Analytics & Behavioral Telemetry: Aggregated analytics retained 24 months. Raw session-level data anonymized within 90 days. IP addresses truncated to subnet level within 30 days.

• Email Marketing Consent & CAN-SPAM Records: Retained 5 years from consent date or last commercial email delivery, whichever is later.

• Payment Transaction Records: Retained 7 years for IRS record-keeping and applicable state tax statute compliance.

• Support & Communication Records: Retained 36 months from last exchange. Automated quarterly purge executes on records exceeding threshold.

• AI Processing Logs: Retained 24 months with automated hash-based anonymization at retention period conclusion.

• Security Incident & Access Logs: Retained minimum 36 months to support forensic investigation, regulatory reporting, and litigation hold obligations.

7.2  Automated Data Purification Protocols

aibble operates an automated data lifecycle management system executing quarterly purification operations including: k-anonymity anonymization (k≥5) of records exceeding active retention windows; permanent suppression list maintenance preventing re-collection of previously removed individuals; orphaned record identification and deletion within 30 days; and backup purge synchronization propagating all deletion events to disaster recovery environments within 15 days of primary purge.

8.  Sub-Account Architecture, Client Liability Firewall & Data Processor Obligations

8.1  The Controller–Processor Boundary

The Business Client is the sole and exclusive Data Controller for all data residing within their GoHighLevel sub-account. aibble functions as a Data Processor under the Client's documented instruction and assumes no independent Data Controller liability for data the Client introduces, uploads, or causes to be collected within their sub-account environment.

• Non-Compliant List Uploads: All legal liability arising from deployment of lists acquired without proper consent — including TCPA violations, state consumer protection claims, CAN-SPAM violations, and carrier penalties — rests exclusively with the Client as Data Controller. aibble disclaims all vicarious, secondary, and derivative liability for non-compliant data imports initiated by clients.

• Campaign Configuration Compliance: Clients are solely responsible for ensuring all message content, opt-in language, and call-to-action disclosures deployed through their sub-account sequences comply with applicable law. aibble's technical execution of a configured campaign does not constitute legal endorsement of its compliance posture.

• Client Data Subject Rights Fulfillment: When a Data Subject requests access, deletion, correction, or portability of data held in a Client's sub-account, aibble forwards the request to the Client for fulfillment within 5 business days. Technical execution of the operation occurs upon Client instruction; the Client bears primary legal responsibility for timely fulfillment.

• Call Recording Client Obligations: Clients using GHL sub-account telephony features are solely responsible for issuing legally compliant call recording disclosures to their own customers in all applicable jurisdictions prior to call initiation.

8.2  Data Processing Addendum (DPA)

All Business Clients engaging aibble's automation and CRM services must execute a Data Processing Addendum as a binding supplement to the primary service agreement. The DPA specifies processing purposes, data categories, security measures, Sub-Processor disclosure, audit rights, and data return or deletion obligations. Clients who upload Personal Data to their sub-account without executing a DPA assume all associated compliance risk without recourse against aibble.

8.3  Google Business Profile Third-Party Policy Alignment

aibble operates strictly within Google's Third-Party Policy and Terms of Service. aibble does not own, claim ownership of, or assert unauthorized control over any Client's Google Business Profile. All API-level actions are performed under manager-level authorization tokens explicitly granted by the verified profile owner. Clients retain the right to revoke manager access at any time without penalty.

9.  Multi-Jurisdictional Privacy Compliance Framework

9.1  Omnibus U.S. State Privacy Rights

aibble's compliance architecture satisfies the operative requirements of all enacted U.S. state consumer privacy statutes as of the effective date of this Policy, including the CCPA/CPRA, VCDPA, Colorado CPA, CTDPA, UCPA, Texas TDPSA, Oregon OCPA, Montana MCDPA, and all subsequently enacted state frameworks. The following universal rights schedule applies to all residents of states with enacted consumer privacy legislation:

• Right to Know / Access: Request a copy of the categories and specific pieces of Personal Data we have collected about you. We respond within 45 days (one 30-day extension permissible upon notice).

• Right to Deletion: Request deletion of your Personal Data. Deletion requests are propagated to Sub-Processors within 30 days, subject to legally recognized exceptions.

• Right to Correct: Request correction of inaccurate Personal Data within 45 days of verification.

• Right to Portability: Receive a portable, machine-readable copy of Personal Data you have provided to us, where technically feasible.

• Right to Opt-Out of Sale or Sharing / Targeted Advertising: Opt out via the Cookie Preference Center on aibble.com, a GPC browser signal, or a written request to [email protected]. Honored within 15 days.

• Right Against Discrimination: Exercise of any privacy right will not result in denial of services, price differentiation, or quality degradation.

To exercise any right, submit a verified request at https://aibble.com/privacy-requests or email [email protected]. Authorized agents may submit requests with documented authorization.

9.2  California-Specific Supplemental Disclosures (CCPA / CPRA & CalOPPA)

For California residents: We collect Identifiers, Commercial Information, Internet and Network Activity, Geolocation Data (city-level IP inference), call recordings, and Inferences. We do not sell Personal Data for monetary consideration. Cross-context behavioral advertising pixel deployment constitutes "sharing" under California law. Sensitive Personal Information is not processed beyond strict service delivery and security necessity. We honor Do Not Track (DNT) signals for site analytics under CalOPPA.

9.3  European Union & United Kingdom GDPR

For Data Subjects in the EEA or UK: Processing relies on Consent, Contractual Necessity, Legal Obligation, and Legitimate Interests as enumerated in Section 4. International data transfers from the EEA or UK to the U.S. are protected by Standard Contractual Clauses (EU Commission Decision 2021/914) and the UK IDTA, supplemented by technical safeguards addressing residual transfer risks. EEA Data Subjects retain the right to lodge complaints with the competent supervisory authority in their Member State of habitual residence.

9.4  Children's Privacy (COPPA)

aibble's services are directed exclusively toward business entities and professional adults aged 18 and older. We do not knowingly collect Personal Data from individuals under age 13. If such data is discovered, it is deleted within 48 hours with zero-retention confirmation. Parents or guardians may contact [email protected] immediately upon discovery.

10. Third-Party Disclosure, Data Sharing & Vendor Governance

aibble discloses Personal Data to third parties only in the following defined circumstances: (i) Service Delivery Partners bound by equivalent data protection agreements; (ii) Advertising Platform Partners (Google, Meta, LinkedIn) for attribution and audience optimization through standard integrations; (iii) Legal Compliance and Enforcement in response to valid legal process; (iv) Business Transfers to a successor entity with advance notice and applicable opt-out rights; and (v) Professional Advisors under enforceable confidentiality obligations. aibble does not sell Personal Data to data brokers, list aggregators, or marketing networks.

11. Information Security, Incident Response & Breach Notification

aibble implements TLS 1.2+ encryption in transit, AES-256 encryption at rest, role-based access control with MFA enforcement, periodic penetration testing, documented vulnerability remediation, and mandatory annual privacy and security training for all team members with data access. In the event of a reportable security breach, aibble will notify affected Business Clients within 72 hours, notify affected individual Data Subjects as required by applicable law, file regulatory notifications within statutory timeframes, and maintain a breach register for regulatory audit.

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

READ CAREFULLY: THIS SECTION REQUIRES BINDING INDIVIDUAL ARBITRATION AND WAIVES YOUR RIGHT TO CLASS-ACTION PARTICIPATION.

Any dispute arising out of or relating to this Privacy Policy, your data privacy rights, our data processing practices, or any automated communications you receive shall be resolved exclusively through final, binding, individual arbitration administered by the American Arbitration Association (AAA). Prior to filing any arbitration demand, the complaining party must deliver written notice to [email protected] and allow 30 days for good-faith informal resolution.

YOU AND AIBBLE EXPRESSLY WAIVE ANY RIGHT TO INITIATE OR PARTICIPATE IN: (I) ANY CLASS-ACTION LAWSUIT; (II) ANY CONSOLIDATED OR MULTI-PLAINTIFF PROCEEDING; (III) ANY COLLECTIVE ARBITRATION; OR (IV) ANY REPRESENTATIVE ACTION UNDER STATE PRIVATE ATTORNEY GENERAL STATUTES, TO THE MAXIMUM EXTENT PERMITTED BY LAW. THIS WAIVER IS MATERIAL AND NON-SEVERABLE.

All proceedings shall be governed by the laws of the State of Michigan, without regard to conflict of law principles. The exclusive venue and seat for all arbitration proceedings or any permitted court actions shall be Wayne County, Detroit, Michigan. If any provision of this Section (other than the class-action waiver) is found unenforceable, it shall be modified to the minimum extent necessary while all remaining provisions continue in full force.

13. Policy Amendments, Versioning & Contact Protocol

Material amendments are communicated via email and/or site notice not less than 14 days prior to the effective date. Non-material corrections may be implemented upon publication. Prior policy versions are archived and available upon written request. Continued use of the Service following the effective date of any amendment constitutes acceptance of the revised Policy.

Compliance Email: [email protected]  |  Privacy 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

© 2026 aibble, LLC. All Rights Reserved. Detroit, Michigan.

Enterprise Privacy Policy v2.0 — Last Reviewed & Approved by Compliance Office: May 22, 2026

• Designated Compliance Email: [email protected]

• Authorized Agency Telephone: 313- 889-7656

• Official Statutory Mail Address: 2785 E Grand Blvd Unit 169 Detroit MI 48211