Privacy Policy

This Privacy Policy applies to Cluxive LLC, a Texas limited liability company(“Cluxive,” “we,” “us,” or “our”), which operates the Cluxive website, product, and related services. Privacy roles can differ depending on the type of data involved.

• For account, billing, support, security, marketing/contact, and website operations data, Cluxive LLC generally acts as the data controller or business.
• For customer-provided service data processed through the Cluxive product on behalf of a business customer, Cluxive generally acts as a processor or service provider, and the business customer is responsible for the notices, permissions, and legal basis required for its use of that data.
• If you are a website visitor interacting with a Cluxive-powered widget on a customer's website or a caller speaking with a customer's AI Front Desk, that business is usually the primary party responsible for the content, call handling configuration, lead flow, booking configuration, follow-up activity, recording notices when recordings are enabled, and visitor- or caller-facing data practices.

Depending on how you use Cluxive, we may collect the following categories of information:

• Account and identity data: name, email address, sign-in activity, membership details, workspace role, authentication/session information, and legal acceptance records.
• Business and onboarding data: business name, website URL, business contact information, welcome messages, lead prompts, approved summaries, knowledge content, uploaded materials, detected PDF links, scanned page summaries, and onboarding drafts.
• Widget, chat, phone-call, and lead data: visitor questions, caller statements, assistant replies, conversation content, chat sessions, call sessions, message and call timestamps, call transcripts, call recordings when recording is enabled, lead forms, lead names, caller ID, phone numbers, email addresses, notes, priority labels, source page URLs, and call-routing metadata. This may include contact details voluntarily typed or spoken in a normal conversation, not only details submitted through a dedicated form.
• Booking and calendar data: structured business-hours settings, appointment rules, connected Google Calendar metadata such as calendar identifier and time zone, encrypted calendar OAuth tokens, synced busy blocks and availability cache records, free/busy availability windows, booked appointment records, cancellation and reschedule records, confirmation-delivery status, and visitor or caller scheduling details such as requested times, name, email address, phone number, or notes submitted during or related to booking.
• Usage, analytics, telephony, and install data: widget launch, message, click, call, and submission events; page paths; widget and voice session keys; phone numbers assigned to a customer; call duration and usage-metering records; install signals; allowed domains; operational telemetry; and anti-abuse, spam, or rate-limit signals.
• Billing and transaction metadata: pricing plan, subscription status, trial status, Stripe customer and subscription identifiers, checkout metadata, and related account state. Payment card information is handled by the payment processor rather than stored directly by Cluxive.
• Communications and notification data: email delivery status, phone-call delivery metadata, optional SMS configuration and sender setup status, consent or opt-out records where applicable, notification logs, and related troubleshooting information.
• Support, admin, and audit data: support-side changes, admin audit records, reasons for support actions, knowledge revision history, and legal acceptance records.
• Website and contact data: contact form details, setup-help inquiries, and security-verification data such as bot-check results.
• Technical and network data: IP address, approximate location inferred from IP, user agent, device/browser data, request origin, referrer, and logs needed for security, fraud prevention, troubleshooting, and abuse detection.

• directly from you when you create an account, complete onboarding, edit settings, request support, book a demo, or contact us;
• from your website or connected public sources when onboarding tools scan public pages and linked PDF documents that you direct us to review or that our product discovers from your website during setup;
• automatically when users interact with the dashboard, billing flows, widget, AI Front Desk, contact forms, APIs, calendar integrations, telephony systems, notification systems, and security systems;
• from service providers that help us with authentication, email delivery, telephony, optional SMS or messaging, payments, anti-abuse, hosting, analytics, infrastructure, and AI or model-serving operations;
• from workspace owners, admins, or authorized support personnel acting on behalf of a customer account.

• provide, host, configure, secure, and maintain the Cluxive service;
• authenticate users and manage accounts, memberships, sessions, preferences, and legal acceptance records;
• scan and summarize public website information during onboarding, create knowledge drafts, and help customers configure a live assistant;
• deliver widget and AI Front Desk functionality, respond to visitor or caller prompts, maintain conversation history, route inbound calls, transcribe or record calls when enabled, and present configured lead-capture, booking, or follow-up flows;
• create, enrich, or update lead records when visitors voluntarily submit contact details through a lead form or provide identifiable contact details in an ordinary chat message;
• send customer-designated notifications, such as lead alerts, follow-up routing, appointment-related emails, call notifications, or optional text-message communications requested and enabled by the customer;
• power scheduling workflows, including syncing availability from a connected calendar, storing local availability and busy-block cache data, validating appointment requests against business-hours settings, creating, canceling, and rescheduling confirmed appointments, sending confirmations, and using AI or model-serving providers to extract booking intent and visitor or caller contact details when the customer has enabled those features;
• process billing, trials, subscriptions, and account lifecycle events;
• monitor product usage, measure performance, improve reliability, and understand feature adoption;
• detect, investigate, and prevent abuse, fraud, security incidents, unauthorized access, and misuse;
• provide customer support, maintain admin audit trails, and troubleshoot operational issues;
• comply with legal obligations, protect rights and safety, and enforce our agreements.

Cluxive uses Google Workspace APIs, including Google Calendar APIs, only to provide customer-facing scheduling functionality that customers choose to connect and configure in the product. Calendar-related data is used to read and sync availability, retrieve the calendar metadata needed to route bookings, maintain local busy-block and availability cache records, create confirmed appointment events, update or cancel events for reschedules and cancellations, and verify availability before a booking is finalized.

The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Cluxive does not use Google Workspace API data for advertising, does not sell Google Workspace API data, and does not use Google Workspace API data to train generalized or non-personalized AI or machine-learning models.

Cluxive uses cookies and similar technologies for authentication, session continuity, security, legal acceptance flow, product preferences, and analytics or operational measurement. Some of these technologies are strictly necessary for the service to function properly.

We may also use browser storage such as localStorage or sessionStorage to help preserve widget conversation state, session continuity, invite-bubble or launcher state, and other product preferences on the device or browser where the widget is used. We may use session cookies or similar identifiers to distinguish browser sessions and support safe widget operation.

Browser settings may allow you to block or remove certain cookies or local browser storage, but doing so can break sign-in, dashboard behavior, billing flows, remembered widget conversations, or other core product functions.

We may share information in the following circumstances:

• Service providers and subprocessors: including providers that support hosting, infrastructure, authentication, email delivery, telephony, optional SMS or messaging, payments, anti-abuse, logging, analytics, and AI or model-serving operations.
• Within a customer workspace: where account owners, admins, and authorized users can access workspace data based on the roles and permissions configured in the product.
• With customer-designated recipients: such as lead notification email addresses or other recipients configured by the customer for operational follow-up.
• With connected workspace providers:such as Google, when a customer connects Google Calendar so Cluxive can sync availability, retrieve calendar metadata, create, update, or cancel calendar events, and support booking, cancellation, and rescheduling on the customer's behalf.
• With professional advisers and counterparties: such as lawyers, auditors, insurers, acquirers, financing sources, or other advisers where reasonably necessary for legal, security, corporate, or transaction-related purposes.
• For legal and safety reasons: when reasonably necessary to comply with law, protect rights, investigate abuse, respond to lawful requests, or prevent harm.
• Business transactions: in connection with a merger, acquisition, financing, reorganization, asset sale, or similar transaction, subject to applicable confidentiality and legal requirements.

Cluxive does not describe itself here as selling personal information for cross-context behavioral advertising. If that changes, we will update this policy and any required notices.

Cluxive uses AI, speech, transcription, and model-serving providers to support certain product workflows, such as generating assistant responses, understanding inbound phone calls, structuring business knowledge, extracting lead or booking intent from messages, and supporting preview or setup experiences. Depending on feature and availability, Cluxive may use third-party AI providers, real-time voice providers, or self-hosted models as subprocessors for service continuity and performance.

Depending on the workflow a customer uses, these providers may process prompts and related business context needed to return a result. That can include public website content surfaced during setup, approved business summaries, widget conversation content, call transcripts or excerpts, and lead or booking-related message context that a customer asks Cluxive to interpret or structure.

Cluxive currently uses Google Gemini as a primary AI provider for certain text, reasoning, setup, and assistant workflows; OpenAI for certain model and realtime voice workflows; and a self-hosted Qwen3:14B model as a fallback for certain tasks and service continuity.

We use these services as subprocessors or service providers in support of the Cluxive product. The AI provider or model used may vary by feature, availability, and system performance. If we add or materially change the AI services we rely on for customer-facing product workflows, we will update this Privacy Policy or related disclosures accordingly.

Billing and subscription management in Cluxive rely on third-party payment infrastructure. For example, checkout and subscription records may be handled through Stripe. Cluxive stores billing metadata needed to manage subscriptions and account state, but payment card details are collected and processed by the payment provider rather than stored directly by Cluxive.

We retain information for as long as reasonably necessary to provide the service, maintain account history, support customers, improve platform reliability, investigate incidents, comply with law, resolve disputes, and enforce our agreements.

• deleted-account records are typically retained for up to 120 days to handle billing disputes, fraud review, audit questions, and operational recovery before they are purged from active systems;
• chat, lead, onboarding, booking, calendar, and knowledge records may be retained while the customer account remains active and for a reasonable period afterward;
• logs and security telemetry may be retained for shorter periods or as needed for abuse prevention and incident response;
• information stored in a browser's local or session storage may remain on that device until the browser clears it, the session ends, or the user removes it.

Cluxive and its service providers may process information in the United States or other countries where we or our providers operate. Those countries may have data protection rules that differ from the rules in your jurisdiction. Where required, we will use legally recognized transfer mechanisms or comparable safeguards.

Cluxive uses administrative, technical, and organizational measures designed to protect information against unauthorized access, misuse, loss, or alteration. These measures include role-based access controls, authentication controls, rate limiting, audit logging, encrypted storage for sensitive integration secrets, and other product and infrastructure safeguards.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Customers are responsible for choosing appropriate use cases, limiting sensitive data, maintaining the security of their own systems and users, and configuring connected services such as calendars or email routing responsibly.

Depending on your location and the context in which we process your information, you may have rights to access, correct, delete, export, or object to certain processing, or to limit certain uses of your information. Rights may be subject to verification, legal exceptions, and role distinctions.

If Cluxive processes your information solely on behalf of one of our business customers, we may direct your request to that customer because it controls the relevant data and relationship. Where required, we will assist our customers with these requests. If you interacted with a Cluxive-powered widget on another business's site, contacting that business is often the fastest way to address the content of the conversation, follow-up, or booking record.

If you are covered by a U.S. state privacy law, you may have rights to know, access, delete, correct, or receive a copy of certain personal information, and to appeal a denied request where applicable. Any such rights are subject to verification and the limits permitted by law.

We disclose in this Privacy Policy the categories of personal information we collect, the sources of that information, the purposes for which it is used, and the categories of parties with whom it may be shared.

Cluxive is not directed to children under 13, and we do not knowingly collect personal information directly from children for our own services. If you believe a child has provided information to us improperly, contact us so we can review and address the issue.

Unless we expressly support it in writing for a particular service, please do not submit medical records, government identification numbers, payment card numbers, precise financial account credentials, or other highly sensitive personal data through onboarding materials, chat inputs, booking requests, or the widget.

We may update this Privacy Policy from time to time to reflect product, legal, security, or operational changes. When we do, we will post the updated version here, update the effective version above, and may require renewed acceptance before continued access to some parts of the service.

For privacy questions or requests for Cluxive LLC, a Texas limited liability company acting as a controller or business, contact us at contact@cluxive.com. If you are writing about data processed through a specific Cluxive customer workspace or widget, please identify the relevant business or website so we can route the request correctly.