Terms & Conditions — NurtureCRM

These Terms and Conditions ("Terms") govern your access to and use of NurtureCRM.ai (the "Service"), operated by AiCoaches dot com LLC ("Company", "we", "us", "our") under the brand Multiplai.tech. By accessing or using the Service you agree to be bound by these Terms.

If you do not agree to these Terms, do not use the Service.

1. Acceptance and Eligibility

By creating an account or using the Service you confirm that you:

are at least 16 years of age;
have the legal authority to enter into these Terms on behalf of the organization you represent; and
will comply with these Terms and all applicable laws.

These Terms distinguish three parties, and the distinction matters throughout:

Customer — the organization that holds the subscription and contracts with us. The Customer is the party bound by these Terms.
Authorized User — an individual the Customer grants access to the Customer's instance of the Service. Authorized Users act under the Customer's authority.
End Contact — a person whose data the Customer loads into the Service, or who submits one of the Customer's public forms. End Contacts are not parties to these Terms; their relationship is with the Customer, and the Customer is responsible for having a lawful basis to process their data.

2. Description of the Service

NurtureCRM is a multi-tenant customer relationship management platform. Each Customer receives an isolated runtime: a dedicated application container, a dedicated database, and dedicated object storage. Customer data is not commingled with other Customers' data.

The Service includes:

CRM records — contacts, companies, deals, pipelines, activities and tasks.
Unified inbox — optional delegated access to Microsoft 365 and Gmail mailboxes, so email conversations appear alongside the CRM records they relate to. See section 7.
Forms and public embeds — hosted forms and pages the Customer publishes to collect End Contact submissions.
Bookings and calendar sync — scheduling surfaces and calendar integration.
AI-assisted features — drafting, summarization, insights and scoring, as described in the AI Policy.
Modules — a marketplace of first-party, official third-party and custom modules that extend the Service. See section 8.

Not every capability is available on every subscription tier. Tier eligibility is described at the point of purchase.

3. Accounts, Roles and Tenancy

The Customer is responsible for the accuracy of the information supplied at signup.
Authorized Users receive roles that determine what they may see and do. The Customer's administrators allocate those roles.
The Customer is responsible for keeping credentials secure and for all activity that occurs under its Authorized Users' accounts.
The Customer's administrators are responsible for who is granted access to each departmental inbox. Granting a user access to a shared or departmental inbox gives that user visibility of the mail in it. We do not adjudicate whether that grant is appropriate within the Customer's organization.
Notify us promptly at support@aicoaches.com of any unauthorized access.

4. Subscription, Billing and Tiers

The Service is offered on Free, Starter, Pro and Enterprise tiers.
Paid subscriptions are billed monthly or annually in advance.
Fees are non-refundable except where required by law.
We will give at least 30 days' notice of a price change.
Payment is processed by Stripe. We do not store full payment card details.

Downgrades disable tier-ineligible modules automatically. This is implemented behaviour, not a policy statement: when a subscription moves to a lower tier, any installed module that the new tier does not permit is disabled, and the Customer's runtime restarts to apply the change. Data written by a disabled module is retained but is not accessible through that module until the module is re-enabled on an eligible tier. Plan downgrades accordingly.

Non-payment may result in suspension. Suspension is described in section 13.

5. Acceptable Use

The Customer and its Authorized Users must not:

use the Service unlawfully, or to store or transmit unlawful content;
attempt to access another tenant's data, container, storage or database;
probe, scan or test the security of the Service without our written permission;
reverse engineer, resell or white-label the Service except under a separate written agreement;
upload malware, or use the Service to send unsolicited bulk messages;
connect a mailbox without the authorization of the mailbox owner, or use the unified inbox to access a mailbox the Customer is not entitled to access;
circumvent module permission scopes, or install a module in order to obtain data the installing user could not otherwise access; or
send messages from a connected mailbox that the Customer is not lawfully entitled to send, including messages that misrepresent the sender.

We may suspend access to investigate a suspected breach of this section.

6. Customer Data, Controller and Processor Roles

The Customer retains ownership of all data it loads into, or generates within, the Service. We do not claim ownership of Customer content.

For CRM records, mail content and any other personal data the Customer brings to the Service:

the Customer is the data controller; and
NurtureCRM is the data processor, acting on the Customer's instructions.

The Customer warrants that it has a lawful basis for the End Contact data it loads and for each mailbox it connects, and that it has given any notices and obtained any consents that its own legal obligations require. Where the Service asks the Customer to record a lawful basis — for example when creating an inbox — that record is the Customer's declaration, not our determination.

We process Customer data only to provide and support the Service, as described in the Privacy Policy and the Data Policy.

7. Email and Mailbox Connections

This section governs the unified inbox and any other feature that connects a Microsoft 365 or Google Gmail mailbox to the Service.

Consent comes from the mailbox owner. A mailbox is connected only when the person who owns that mailbox completes the provider's own consent flow and grants access. An administrator can invite a user to connect a mailbox; an administrator cannot connect another person's mailbox on their behalf. Where the mailbox owner's organization requires administrator consent at the directory level, that consent is a prerequisite and is obtained separately by the organization's administrators — it does not by itself connect any individual mailbox.

Scopes requested and what each enables.

Provider	Scope	What it enables
Microsoft 365	`Mail.Read`	Reading messages from the consenting mailbox into the unified inbox
Microsoft 365	`Mail.Send`	Sending replies and composed messages as the consenting user
Microsoft 365	`offline_access`	Refreshing access without asking the user to sign in repeatedly
Microsoft 365	`User.Read`, `openid`, `profile`	Identifying the consenting mailbox owner
Google Gmail	`gmail.readonly`	Reading messages from the consenting mailbox into the unified inbox
Google Gmail	`gmail.send`	Sending replies and composed messages as the consenting user
Google Gmail	`openid`, `userinfo.email`, `userinfo.profile`	Identifying the consenting mailbox owner

We do not request permission to modify or delete messages in a connected mailbox.

Where the data goes. Message content and metadata from a connected mailbox are ingested into the Customer's own isolated database, inside the Customer's own runtime. Mail content from one Customer is never written to another Customer's database.

Credentials. OAuth tokens for connected mailboxes are stored encrypted at rest. Provider client secrets are held by the platform and are never written into a Customer's runtime container.

Revocation. The mailbox owner may disconnect at any time from within the Service or from the provider's own account settings, and a Customer administrator may revoke a connection for their organization. Revocation tears down the provider-side subscriptions and marks the stored token revoked so it can no longer be used. The token record itself is retained in a revoked state for audit purposes rather than deleted, so it remains possible to answer who connected what and when. Mail already ingested into the Customer's database is governed by section 13 and the Data Policy.

Microsoft and Google are independent controllers of their own platforms. Their terms govern the mailbox itself, and nothing in these Terms varies them. Connecting a mailbox does not change the relationship between the mailbox owner and their email provider.

8. Third-Party Integrations and Modules

The Service integrates with third-party providers including Microsoft, Google and Stripe. Those providers' own terms govern their services. Our sub-processors are listed at Sub-processors.

The module trust model. Modules come in three kinds:

First-party modules, built and maintained by us.
Official provider modules, built by a third party we have reviewed and admitted to the marketplace.
Custom modules, built by or for the Customer.

An installed module runs with the permission scopes the Customer allocated to it at install time. A module cannot silently widen its own scopes. The Customer is responsible for the modules it chooses to install, for the scopes it grants them, and — for custom modules — for their content and behaviour. Module actions are recorded in the module audit log available to the Customer's administrators.

We may remove a module from the marketplace, or disable a module for security reasons, without notice where the risk warrants it.

9. AI Features

AI features are assistive. AI output may be inaccurate, incomplete or unsuitable, and must be reviewed by a human before it is relied upon or sent. Nothing produced by an AI feature is professional, legal, financial, medical or tax advice.

The AI Policy is part of these Terms and describes which providers are used, what data is sent to them, how long they retain it, and the commitments that apply. In particular, mail content from connected mailboxes is not used to train or improve any model, by us or by any AI provider. Google user data is additionally subject to the Google Limited Use disclosure.

Customers may disable AI features as described in the AI Policy.

10. Availability and Changes

We do not offer a service level agreement on the standard tiers, and these Terms should not be read as implying one. We aim for high availability and operate monitoring and backups, but we do not commit to a specific uptime percentage, and we do not offer service credits on Free, Starter or Pro tiers. Any SLA for an Enterprise Customer is set by separate written agreement and, where one exists, that agreement prevails over this section.

We may modify, add or remove features. Where a change materially reduces functionality the Customer relies on, we will give reasonable notice.

Planned maintenance may cause brief interruptions. Provisioning, module changes and tier changes restart the Customer's runtime container, which is a short interruption by design.

11. Limitation of Liability

To the maximum extent permitted by law:

the Service is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement;
we are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill; and
our total aggregate liability arising out of or relating to the Service is limited to the fees paid by the Customer in the twelve months preceding the event giving rise to the claim.

Some jurisdictions do not allow certain limitations, in which case the limitations apply to the fullest extent permitted.

12. Indemnification

The Customer will indemnify and hold us harmless from claims, damages and costs arising from:

the Customer's breach of these Terms or of applicable law;
content the Customer or its Authorized Users load into the Service;
End Contact data the Customer loaded without a lawful basis;
a mailbox connected without the authorization of its owner; and
custom modules the Customer builds, commissions or installs.

13. Term and Termination

These Terms apply for as long as the Customer uses the Service.

Either party may terminate: the Customer by cancelling its subscription; us for material breach, non-payment, or where required by law.

On termination the sequence is:

the Customer's instance is suspended — the Service stops serving requests for that tenant;
the Customer's database is dropped from active service and archived;
a 90-day export window runs from termination, during which the Customer may request an export of its data; and
after the export window, the archived data is permanently deleted.

Suspension for non-payment is reversible on payment. Deletion at step 4 is not reversible.

14. Dispute Resolution

These Terms are governed by the laws of the State of Florida, USA, without regard to conflict-of-laws rules.

Any dispute arising out of or relating to these Terms or the Service will be resolved by binding arbitration administered by the American Arbitration Association in Miami, Florida, under its Commercial Arbitration Rules.

Class-action waiver. Disputes will be arbitrated on an individual basis only. Neither party may bring a claim as a plaintiff or class member in a class, consolidated or representative action.

Either party may seek injunctive relief in a court of competent jurisdiction to protect intellectual property or confidential information.

15. General Provisions

Entire agreement. These Terms, together with the Privacy Policy, Data Policy, AI Policy, Sub-processors and Google Limited Use disclosure, are the entire agreement between the parties.
Severability. If any provision is unenforceable, the rest remain in effect.
No waiver. Failure to enforce a provision is not a waiver of it.
Assignment. The Customer may not assign these Terms without our written consent. We may assign them in connection with a merger, acquisition or sale of assets, on notice.
Force majeure. Neither party is liable for delays caused by events beyond its reasonable control.

16. Changes to These Terms

We may update these Terms. Material changes take effect 30 days after notice, given by email to the Customer's registered address or in-product.

Each document in this suite carries a version and an effective date, both shown at the top of the page. The version is bumped on every material change. The version accepted at signup is recorded against the Customer's account, so it is always answerable which text a Customer agreed to. Continued use of the Service after a material change takes effect constitutes acceptance of the updated Terms.

17. Contact

AiCoaches dot com LLC 111 NE 1ST ST, 8TH FLOOR 89145, Miami, Florida, USA 33132 Legal and support enquiries: support@aicoaches.com