Legal

    Privacy Policy

    Effective Date: November 11, 2026

    This Privacy Policy describes how Nimbus AI collects, uses, and protects your personal information when you use our services, visit our website at nimbusai.biz, or interact with the Nimbus Marlowe platform.

    By using our services, you agree to the collection and use of information in accordance with this Privacy Policy.

    1. Information We Collect

    We collect information you provide directly to us, such as:

    • Name and email address when you sign up for our newsletters or automation workflows
    • Business information when you request consultations or demos
    • Communication preferences and interaction data

    2. Nimbus Marlowe Platform Data

    If you use the Nimbus Marlowe platform, we also process: (a) account information — your name, email, role, and firm details; (b) client and case data that your firm uploads or creates in the platform ("Client Data") — your firm owns this data, and we process it solely to provide the platform services as described in our Terms of Service; (c) payment information, which is processed and stored exclusively by our payment processor (Stripe) and never stored on our servers; and (d) usage and audit log data for security and support. We never use Client Data to train AI or machine learning models. Client Data is encrypted in transit and at rest, isolated per firm, and processed by a limited set of service providers under confidentiality and data protection obligations — a current list of subprocessor categories appears in our Terms of Service, and identities are available under an executed Data Processing Agreement. Data retention and deletion upon termination are governed by the Terms of Service. For privacy requests relating to platform data, contact [email protected].

    2A. ChatGPT Connection

    Authorization and purpose

    The Nimbus Marlowe ChatGPT connection lets authorized firm members request permitted operational records and prepare intake workflows from ChatGPT. A connection is associated with a Marlowe user, the firm selected during authorization and the permissions granted to that connection. Available records and actions also depend on the user's role, firm settings and applicable client or matter consent controls. Connecting does not grant access to other firms.

    Information exchanged

    Marlowe receives inputs sent to its tools to perform the requested task, such as search terms, record identifiers, date ranges, filters, workflow specifications and synthetic test inputs. Depending on the requested tool and permissions, Marlowe returns contact and case metadata, intake and follow-up information, contract and document metadata, recorded deadlines and appointments, operational reports, or workflow definitions and test results. Contact details such as email addresses and telephone numbers are included only where the firm's settings and the user's access permit them.

    The release described here does not provide medical-record or full document-body retrieval, message sending, workflow activation, appointment booking, signature collection or payment charging. Do not include medical records, payment-card data, government identifiers, passwords or other authentication secrets in tool inputs. These limits describe this ChatGPT connection, not every feature of the broader Marlowe platform.

    OpenAI and service providers

    Information returned by Marlowe is sent to OpenAI's ChatGPT to answer the user's request. Information sent to Marlowe is processed to provide the requested connection functions, together with the hosting, database and authentication services described in our platform disclosures and Terms of Service.

    Our commitment not to use Client Data to train models continues to apply to Nimbus's own processing. OpenAI's handling of information in ChatGPT, including retention and model-improvement use, is governed by the applicable ChatGPT terms, privacy policy, user settings and workspace arrangements. A ChatGPT connection does not establish zero-data-retention treatment for the user's ChatGPT account. For more about connected apps, see OpenAI's Connected apps in ChatGPT help article.

    Stored workflows and operational records

    When a permitted user saves an inactive workflow draft, its definition and associated validation information are stored in Marlowe for later review. Saving an inactive draft does not activate it or send messages.

    We also process connection and activity metadata, including firm and user identifiers, granted permissions, connection status, tool names, execution times, result status, related record identifiers and result counts. These records support access control, security, troubleshooting and service-operation reporting. Operational reporting may include tool-use counts, success rates and response times; it is distinct from the contents of client records.

    Revocation, retention and privacy requests

    You can disconnect an individual connection in Marlowe's ChatGPT integration settings. Authorized firm administrators can manage connections within their firm. Revocation stops further access through that connection; it does not by itself delete underlying Marlowe records, saved workflow drafts, audit records or information previously returned to ChatGPT. Other separately authorized connections remain subject to their own permissions.

    The existing retention and deletion commitments in our Terms of Service continue to apply to Marlowe platform data, including applicable audit-log retention periods. Disconnecting the ChatGPT connection is not the same as terminating the firm's Marlowe account or requesting deletion. Information already held in ChatGPT is subject to OpenAI's applicable controls and arrangements.

    For requests about access, correction or deletion of Marlowe data, contact [email protected]. You may also need to contact your firm administrator for records controlled by your firm.

    2B. Claude Connection

    Authorization and purpose

    The Nimbus Marlowe connection for Anthropic's Claude, including claude.ai, Claude Desktop and Claude Code, lets authorized firm members request permitted operational records and prepare intake workflows from Claude. A connection is associated with a Marlowe user, the firm selected during authorization and the permissions granted to that connection. Available records and actions also depend on the user's role, firm settings and applicable client or matter consent controls. Connecting does not grant access to other firms.

    Information exchanged

    Marlowe receives inputs sent to its tools to perform the requested task, such as search terms, record identifiers, date ranges, filters, workflow specifications and synthetic test inputs. Depending on the requested tool and permissions, Marlowe returns contact and case metadata, intake and follow-up information, contract and document metadata, recorded deadlines and appointments, operational reports, or workflow definitions and test results. Contact details such as email addresses and telephone numbers are included only where the firm's settings and the user's access permit them.

    Some information is available only if a firm administrator turns it on. Those settings are off by default. They include bounded pages of stored document, contract and saved-draft text; treating-provider names, stated lien amounts and records-request status; and message, call-summary, transcript or case-note content. Documents marked as containing health information are not returned through this connection.

    By default, this connection does not send messages to clients or anyone else. A firm administrator can turn on sending. When it is on, Claude can only prepare a client email, text or letter. The message goes out only after a person with permission approves the exact text in Marlowe, and only if each recipient is opted in and not suppressed on that channel at the time of approval. A missing opt-in, a suppression or a failed check sends nothing. This connection does not turn on workflows, book appointments, collect signatures or charge payments. A workflow can only be saved as an inactive draft, and a person with permission must approve activation in Marlowe. If a firm enables internal updates such as tasks or notes, each one is prepared as a proposal that a person confirms in Marlowe. Dates shown are the dates the firm recorded. Marlowe does not calculate legal deadlines through this connection.

    Do not include medical records, payment-card data, government identifiers, passwords or other authentication secrets in tool inputs. These limits describe this Claude connection, not every feature of the broader Marlowe platform.

    Anthropic and service providers

    Information returned by Marlowe is sent to Anthropic's Claude to answer the user's request. Information sent to Marlowe is processed to provide the requested connection functions, together with the hosting, database and authentication services described in our platform disclosures and Terms of Service. Our commitment not to use Client Data to train models continues to apply to Nimbus's own processing.

    Anthropic's handling of information in Claude, including retention and any model-improvement use, is governed by the applicable Anthropic terms, privacy policy, user settings and workspace arrangements. A Claude connection does not establish zero-data-retention treatment for the user's Claude account. For more about connectors, see Anthropic's help article on connectors and Anthropic's privacy policy.

    Stored workflows and operational records

    When a permitted user saves an inactive workflow draft, its definition and associated validation information are stored in Marlowe for later review. Saving an inactive draft does not activate it or send messages.

    We also process connection and activity metadata, including firm and user identifiers, granted permissions, connection status, tool names, execution times, result status, related record identifiers and result counts. These records support access control, security, troubleshooting and service-operation reporting. Operational reporting may include tool-use counts, success rates and response times; it is distinct from the contents of client records.

    Revocation, retention and privacy requests

    You can disconnect from Claude's connector settings or from Marlowe's connector settings at /settings/connector. Authorized firm administrators can manage connections within their firm. Revocation stops further access through that connection; it does not by itself delete underlying Marlowe records, saved workflow drafts, audit records or information previously returned to Claude. Other separately authorized connections remain subject to their own permissions.

    The existing retention and deletion commitments in our Terms of Service continue to apply to Marlowe platform data, including applicable audit-log retention periods. Disconnecting the Claude connection is not the same as terminating the firm's Marlowe account or requesting deletion. Information already held in Claude is subject to Anthropic's applicable controls and arrangements.

    For requests about access, correction or deletion of Marlowe data, contact [email protected]. You may also need to contact your firm administrator for records controlled by your firm.

    3. Google User Data

    Nimbus Marlowe allows users to connect a Google account to enable calendar features. This section describes exactly what we access and why.

    What we access. With your permission, Nimbus Marlowe requests the following Google API scopes:

    • .../auth/userinfo.email — identifies which Google account is connected.
    • .../auth/calendar — lists your calendars so you can choose which to sync, and reads availability for scheduling.
    • .../auth/calendar.events — creates, updates and deletes the appointments you manage through Nimbus Marlowe, and reads events so your schedule is visible in-app and double-booking is prevented.

    How we use it. Google Calendar data and your Google account email address are used solely to provide calendar synchronization and scheduling features within Nimbus Marlowe.

    How long we keep it. Google Calendar data is retained only while your Google account is connected, and is deleted within 30 days of disconnection or account closure.

    What we never do. We do not sell Google user data. We do not use it for advertising. We do not use it to develop, improve, or train generalized artificial intelligence or machine learning models. We do not transfer it to third parties except as necessary to provide these features, to comply with applicable law, or in connection with a merger or acquisition with notice to you.

    How to revoke access. You can disconnect your Google account at any time from Settings → Integrations within the product, which revokes our access. You can also revoke access from your Google Account permissions page at https://myaccount.google.com/permissions.

    Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

    4. How We Use Your Information

    We use the information we collect to:

    • Send you automation workflows and business tips you've requested
    • Provide customer support and respond to your inquiries
    • Improve our services and develop new features
    • Send periodic newsletters and updates (you can unsubscribe anytime)

    5. Information Sharing

    We do not sell, trade, or rent your personal information to third parties. We may share your information only in these limited circumstances:

    • With your explicit consent
    • To comply with legal obligations
    • To protect our rights and safety

    6. SMS / Text Messaging

    Some of our products, including Nimbus Marlowe, allow end users to receive text messages — for example, when a caller to a law firm's intake line requests a scheduling or intake form link by text.

    Consent

    End users opt in to receive text messages by requesting them, such as by asking for a link during a phone call to a participating firm's intake line or by texting the firm's number. Messages are sent in response to the end user's request.

    No third-party sharing

    Mobile phone numbers and SMS opt-in/consent data will not be shared with or sold to third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties.

    Message frequency

    Message frequency varies based on your requests and interactions.

    Fees

    Message and data rates may apply. Check with your mobile carrier for details.

    Opting out

    You can opt out of text messages at any time by replying STOP to any message. Reply HELP for help. After you opt out, you will receive one final message confirming your opt-out.

    7. Data Security

    We implement appropriate security measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.

    8. Your Rights

    You have the right to:

    • Access the personal information we have about you
    • Request correction of inaccurate information
    • Request deletion of your information
    • Unsubscribe from our communications at any time

    9. Contact Us

    If you have questions about this Privacy Policy, please contact us at:

    General inquiries: [email protected]
    Privacy requests: [email protected]

    10. Changes to This Policy

    We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the effective date.

    November 11, 2026: Added Section 2B (Claude Connection) and updated the effective date.

    July 7, 2026: Added Section 6 (SMS / Text Messaging) and updated the effective date.

    By using our services, you agree to the collection and use of information in accordance with this Privacy Policy.

    Contact us

    Tell us what you are trying to automate and we will get back to you.