Legal
Hive Subscription Terms
Version dated October 23, 2026.
1. Order Forms and These Terms
1.1 What these Terms are. These Hive Subscription Terms (the “Terms”) apply to each order form that refers to them and is signed by Provider and the customer named in it (an “Order Form”). The Order Form, these Terms (including Schedules A to D), and any SOW together are the “Agreement.” In these Terms, “Provider” and “Customer” mean the parties named in the Order Form.
1.2 What an Order Form states. Each Order Form states the date the Agreement takes effect (the “Effective Date”), the date the subscription starts (the “Start Date”), the number of Seats, the fee per Seat (together with any other fees the Order Form lists, the “Fees”), any initial fixed term (the “Initial Term”), whether and how the subscription renews (each renewal period a “Renewal Period”), the billing method, the Authorized Integrations, and the parties’ contacts. If an Order Form states no Initial Term, the subscription is month-to-month and renews for successive 30-day Renewal Periods.
1.3 Acceptance and version. Customer accepts these Terms by signing an Order Form that refers to them or by accessing or using the Services. The version of these Terms that applies is the one the Order Form identifies by date. Provider will not change that version during the Term unless the parties agree in writing, except as these Terms expressly allow, such as price changes under Section 5.7 and updates to Annexes II and III to Schedule B.
2. Definitions
Capitalized terms have these meanings. Other terms are defined where they first appear.
- “Account Data” means information about Customer and its Authorized Users that Provider uses to administer accounts, bill, and secure the Services, such as names, work email addresses, roles, seat counts, billing contacts, and usage and cost metrics.
- “AI Features” means the parts of the Services that use machine-learning models to retrieve, summarize, draft, classify, or act on content, including Hive’s assistant (Sayya) and scheduled agents.
- “Authorized Integration” means a Third-Party Service that is listed in Schedule A, is included in the Order Form, and is connected by Customer to the Services.
- “Authorized User” means an individual employee or contractor of Customer whom Customer permits to use a Seat.
- “Credentials” means usernames, passwords, multi-factor authentication factors, OAuth authorizations and tokens, API keys, session tokens, and the devices used to sign in to or authorize access to the Services or any Authorized Integration.
- “Customer-Chosen AI Client” means any AI assistant, language-model application, or agent (for example ChatGPT, Claude, or Cursor) that Customer or an Authorized User connects to the Services, including through the Hive connector (MCP) or an API key.
- “Customer Data” means (a) content and metadata that the Services retrieve from Authorized Integrations or that Customer or an Authorized User uploads or submits, including prompts, and (b) Derived Data. It excludes Account Data and Usage Data.
- “Customer-Side Compromise” means any unauthorized access to or use of an account, device, or Credential of Customer or an Authorized User, however it occurs, including through phishing, social engineering, credential reuse, malware, lost or stolen devices, sharing of Credentials, or failure to use multi-factor authentication, and any act or omission of a Customer-Chosen AI Client or other Third-Party Service.
- “Data Protection Law” means privacy and data-protection laws that apply to Provider’s processing of Personal Data under this Agreement, including the California Consumer Privacy Act as amended (“CCPA”) and, where applicable, the GDPR, the UK GDPR, and the Swiss FADP.
- “Derived Data” means data the Services generate from retrieved or submitted content, including extracted text, vector embeddings, knowledge-graph entities and relationships, summaries, extracted tasks, commitments and decisions, saved memories and context, and conversation history.
- “Output” means any content, draft, summary, answer, or action that AI Features produce in response to an input.
- “Personal Data” means information that identifies or relates to an identifiable individual and is processed as Customer Data, including “personal information” under the CCPA.
- “Security Incident” means a confirmed breach of Provider’s security that leads to unauthorized access to, or acquisition, disclosure, loss, or destruction of, Customer Data in Provider’s possession or control. It excludes unsuccessful attempts and anything that results from Customer-Side Compromise.
- “Seat” means the right for one named Authorized User to use the Services.
- “Services” means Provider’s Hive platform, including the web application, API, MCP connector, assistant, Authorized Integration connections, and scheduled agents, as made available to Customer under this Agreement. It excludes work performed under a SOW.
- “SOW” means a written statement of work signed by both parties for anything beyond the Services, such as custom development, additional integrations, implementation, training, or consulting.
- “Subprocessor” means a third party that Provider engages to process Customer Data.
- “Third-Party AI Provider” means a Subprocessor that supplies AI models or related AI services used to power AI Features.
- “Third-Party Service” means any product or service not provided by Provider, including Google Workspace, Customer-Chosen AI Clients, and Stripe.
- “Usage Data” means technical and operational data about the use and performance of the Services, such as feature usage, token counts, cost, timestamps, and error logs, excluding the content of Customer Data.
3. The Services
3.1 Access. During the Term, Provider will make the Services available to Customer for the number of Seats in the Order Form, for Customer’s internal business purposes. The Services connect Customer’s Authorized Integrations, index and organize the content they provide, and make that context available to Authorized Users through Hive’s assistant and through Customer-Chosen AI Clients that Customer connects.
3.2 Authorized Integrations. Provider will connect only the Authorized Integrations, which are the integrations in Schedule A that the Order Form includes. Customer authorizes Provider to access each one, within the access Customer grants (for example, Google OAuth scopes), to retrieve content and, where Schedule A says so, to take actions on an Authorized User’s instruction. Customer is responsible for having the authority and administrator permissions to grant that access. Provider may change how an integration works to follow a Third-Party Service’s changes, and may suspend an integration if the Third-Party Service restricts or withdraws access.
3.3 Actions in connected systems. The Services can draft and, on an Authorized User’s instruction, take actions in Authorized Integrations, such as sending email, creating calendar events, creating or updating documents, and updating tasks. In interactive chat, Provider requires the Authorized User’s explicit confirmation before sending email or creating calendar events on the user’s behalf. Some lower-impact actions, such as creating or updating documents in the user’s own Google Drive or updating the user’s Google Tasks, may run on the user’s instruction without a separate confirmation step. Scheduled agents act only within the permissions the Authorized User grants when configuring them. Customer is responsible for every action taken through the Services at an Authorized User’s instruction or within permissions an Authorized User has granted, and for reviewing drafts and previews before confirming them.
3.4 Support and availability. Provider will provide email support at sayya@objectedge.com on business days and will use commercially reasonable efforts to keep the Services available. Provider may perform maintenance at any time. Provider does not commit to any uptime level, response time, or service credit.
3.5 Anything else requires a SOW. Work outside the Services, including additional integrations, custom connectors, implementation and configuration work, training, embedded engineering, custom applications, data migration, and any export of data, is outside this Agreement and is provided only under a SOW with its own scope, schedule, and fees. Provider has no obligation to perform that work, or to build or support an integration, until a SOW is signed. A SOW is governed by this Agreement, including Schedule D. If a SOW conflicts with this Agreement, the SOW controls for its own scope only, except that a SOW cannot change Sections 7, 9, 13, or 14 or Schedule B unless it refers to them expressly.
3.6 Changes. Provider may update, improve, or discontinue features of the Services. Provider will not materially reduce the core functionality of the Services during a period Customer has paid for, except as needed for security, to comply with law, or because a Third-Party Service changes or ends access.
3.7 Third-Party Services. Customer’s use of Third-Party Services, including Google Workspace, is governed by Customer’s agreements with those providers. Provider is not responsible for Third-Party Services or for their availability, changes, security, or terms. Customer must comply with those terms when it connects them to the Services.
3.8 Usage limits and beta features. The Services are subject to reasonable usage limits that Provider configures, including AI-usage credits, request quotas, and rate limits, and Provider may throttle use to protect the Services. Features labeled beta, preview, or experimental are provided as is.
4. Customer Responsibilities
4.1 Authorized Users and Seats. Each Seat is for one named Authorized User and may not be shared. Authorized Users sign in with their Google accounts. Customer may reassign a Seat when an Authorized User leaves Customer’s organization. Customer is responsible for all activity under its Seats and for its Authorized Users’ compliance with this Agreement.
4.2 Credentials and account security. Customer and each Authorized User are solely responsible for protecting their Credentials. Customer will:
- require multi-factor authentication on the Google account of every Authorized User, because Provider relies on Customer’s Google Workspace policies for sign-in and multi-factor authentication;
- notify Provider at sayya@objectedge.com without delay, and in any event within 24 hours, after learning of any Customer-Side Compromise or suspected unauthorized use of the Services;
- promptly remove access for any Authorized User who leaves or no longer needs it, by archiving the user in Hive and revoking that user’s Google connections; and
- keep its administrator and billing contact details current.
4.3 Customer-Side Compromise. Provider is not responsible or liable for any loss, damage, unauthorized access, use, or disclosure, or any other consequence, to the extent caused by Customer-Side Compromise. Activity carried out with valid Credentials, including through a Customer-Chosen AI Client, is treated as authorized by Customer.
4.4 Customer Data and legal compliance. Customer represents and warrants that it has all rights, notices, consents, and legal bases needed to (a) connect the Authorized Integrations and allow Provider to process Customer Data, including Personal Data of Authorized Users and of third parties who appear in emails, calendar events, chats, documents, and meeting transcripts, and (b) comply with laws on employee monitoring, recording and transcription of calls and meetings, and electronic communications that apply to its content. Customer is responsible for the accuracy, quality, and legality of Customer Data.
4.5 Restrictions. Customer will not, and will not permit anyone else to: (a) reverse engineer, decompile, or try to extract source code, models, prompts, or ontologies from the Services; (b) copy, resell, sublicense, or provide the Services to third parties; (c) use the Services to build or train a competing product or AI model, or publish benchmarks of the Services; (d) circumvent Seat or usage limits; (e) probe, scan, or test the security of the Services, or access them by automated means other than Provider’s API or connector, without Provider’s written consent; (f) upload malicious code or interfere with the Services; (g) use the Services unlawfully, in breach of Schedule C, or in breach of the terms of any Third-Party Service; or (h) connect an account that Customer is not authorized to connect.
5. Fees and Payment
5.1 Fees. Customer will pay the Fees in the Order Form. Fees are charged in advance for each billing period, starting on the Start Date.
5.2 Payment through Stripe. Customer will pay by the method the Order Form states, which is a credit card or another payment method Stripe accepts. Customer authorizes Provider and Stripe to charge the payment method on file for all Fees, including recurring charges, automatic renewals, additional Seats, and taxes, until this Agreement ends. Customer will keep its payment details current. Payment card details are collected and processed by Stripe under Stripe’s terms and privacy policy. If a payment fails, Provider may retry the charge and may suspend the Services under Section 6.3.
5.3 Seats. Customer may add Seats at any time at the same Fee per Seat. Added Seats are prorated for the rest of the current period and billed with the next charge. Reductions in Seats take effect at the start of the next Renewal Period, and Fees for unused Seats are not refunded. Provider may enforce the Seat limit through technical controls.
5.4 Taxes. Fees exclude taxes, duties, and similar charges. Customer will pay all sales, use, value-added, goods and services, withholding, and similar taxes, other than taxes on Provider’s net income. Provider will add taxes to its charges where the law requires.
5.5 No refunds. Fees are non-cancellable and non-refundable, including for partial periods and unused Seats, except where the law requires otherwise.
5.6 Late and disputed payments. Overdue amounts accrue interest at 1.5% per month, or the highest rate the law allows if lower, and Customer will pay reasonable costs of collection. Customer must dispute a charge in good faith by written notice within 30 days after the charge. Undisputed amounts remain payable.
5.7 Price changes. Provider may change the Fee per Seat for any Renewal Period by giving written notice at least 30 days before that Renewal Period begins. Customer may end this Agreement under Section 6.1 before the new price takes effect.
6. Term and Termination
6.1 Term and renewal. This Agreement starts on the Effective Date, runs for the Initial Term (if the Order Form states one), and then renews automatically for successive Renewal Periods (together, the “Term”). If the Order Form states an Initial Term, either party may stop renewal by written notice (email is enough) at least 30 days before the end of the then-current Initial Term or Renewal Period. If it states no Initial Term, either party may terminate at any time by written notice (email is enough), effective at the end of the then-current Renewal Period, and to avoid a charge for the next Renewal Period, Customer’s notice must reach Provider at least 3 days before that period begins. Fees for the current period are not refunded.
6.2 Termination for cause. Either party may terminate this Agreement by written notice if the other party materially breaches it and does not cure the breach within 30 days after notice (10 days for non-payment). Provider may terminate immediately by notice if Customer breaches Section 4.5, Schedule C, or Section 10, or if Customer’s use of the Services violates law.
6.3 Suspension. Provider may suspend all or part of the Services immediately, with notice where practicable, if (a) payment is overdue; (b) Provider reasonably believes there is a security risk, Customer-Side Compromise, or misuse; (c) the law or a Third-Party Service such as Google requires it; or (d) Customer breaches Section 4.5 or Schedule C. Fees continue to accrue during a suspension caused by Customer.
6.4 Effect of termination. When this Agreement ends: (a) Customer’s right to use the Services ends and Provider will disconnect and revoke the Authorized Integrations; (b) Customer remains liable for Fees that accrued before the end date; (c) Provider will delete Customer Data under Section 7.6; and (d) sections that by their nature should survive will survive, including Sections 4.3, 4.4, 5, 7, 9, and 10 through 16.
7. Customer Data and Data Protection
7.1 Ownership and license. As between the parties, Customer owns Customer Data. Customer grants Provider a non-exclusive, worldwide license during the Term to host, copy, process, index, and transmit Customer Data to (a) provide, secure, and support the Services for Customer; (b) take actions Authorized Users request; (c) prevent abuse and fix errors; and (d) comply with law and Customer’s documented instructions.
7.2 What the Services store. Customer acknowledges that the Services retrieve content from Authorized Integrations and store copies of that content and Derived Data, including email, document, calendar, chat, and task text, vector embeddings, knowledge-graph records, summaries, and conversation history, so that the Services work. Disconnecting an Authorized Integration stops further retrieval but does not by itself delete content already stored. Deletion happens under Section 7.6. Provider applies automatic retention limits to certain logs, as described in Schedule B, and otherwise keeps Customer Data for the Term.
7.3 Roles. For Customer Data, Customer is the controller (the CCPA “business”) and Provider is the processor (the CCPA “service provider”), and Schedule B applies. For Account Data and Usage Data, Provider acts as an independent controller (or business) to administer accounts, bill, secure, support, and improve the Services.
7.4 No training on Customer Data. Provider will not use Customer Data to train or fine-tune any AI or machine-learning model. Provider’s use and transfer of information it receives from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7.5 Usage Data. Provider may collect and use Usage Data and Account Data to operate, secure, support, and improve the Services, and may use aggregated or de-identified Usage Data that does not contain the content of Customer Data for any lawful purpose.
7.6 Deletion on termination. Within five (5) days after this Agreement ends, Provider will delete Customer Data from its production systems, including the production database and file storage. Customer Data in encrypted backups and soft-deleted storage is overwritten or expires on a rolling cycle, generally within seven (7) days after the production deletion, and Provider will not restore or access it except for disaster recovery. Limited operational log entries that may contain identifiers such as email addresses or subject lines expire within thirty (30) days after the entry is created. On Customer’s written request, Provider will confirm in writing that deletion is complete. Provider may keep (a) Account Data and billing records as required for tax, accounting, and legal purposes, and (b) Customer Data it must retain to comply with law or to establish or defend legal claims, in each case subject to Section 11. Provider will instruct Subprocessors to delete Customer Data where Provider has the technical ability to do so. Otherwise a Subprocessor’s own retention terms apply to data it holds.
7.7 No export. Customer Data comes from Customer’s own systems of record, which Customer keeps. Provider does not offer export or return of Customer Data, including Derived Data, during or after the Term. Where Data Protection Law requires Provider to return Customer Data, Provider will do so if Customer asks in writing before this Agreement ends, in a commonly used format, under a SOW at Provider’s then-current rates.
7.8 Security Incidents. If Provider confirms a Security Incident, it will notify Customer’s administrator without undue delay, take reasonable steps to contain and investigate it, and give Customer information reasonably needed to meet Customer’s own legal obligations. Customer is responsible for notices to its Authorized Users, affected individuals, regulators, and others, and for the cost of those notices, subject to Section 14. Notice of, or a response to, a Security Incident is not an admission of fault or liability.
7.9 Legal requests. Provider may disclose Customer Data if the law or legal process requires. Unless the law prohibits it, Provider will give Customer notice so that Customer may seek protection at its own expense.
7.10 Requests from individuals. Provider will use commercially reasonable efforts, taking into account the nature of the processing, to help Customer respond to requests from individuals exercising rights under Data Protection Law. Customer is responsible for responding to those requests.
8. Security
8.1 Safeguards. Provider will maintain administrative, technical, and organizational safeguards designed to protect Customer Data against unauthorized access, loss, and disclosure, appropriate to the nature of the Services. The measures in effect on the Effective Date are summarized in Annex II to Schedule B. Provider may update them, provided the updates do not materially reduce the overall protection of Customer Data.
8.2 No guarantee. No system is completely secure. Transmissions over the internet, and the Third-Party Services Customer connects, are outside Provider’s control. Provider does not warrant that the Services or Customer Data will be free from unauthorized access or that any security measure will prevent every Security Incident.
8.3 Customer’s security responsibilities. Customer is responsible for the security of its own systems, devices, networks, Google Workspace configuration, and Credentials, and for the permissions it grants to Authorized Integrations and Customer-Chosen AI Clients.
8.4 Security information. Once a year, on Customer’s request, Provider will give Customer a summary of its security practices and answer a reasonable security questionnaire. That information is Provider’s Confidential Information. Provider does not offer on-site audits or customer-run security testing.
9. AI Features and Third-Party Models
9.1 How AI Features work. AI Features use machine-learning models, including models run by Third-Party AI Providers, to retrieve, summarize, draft, and act on content. To answer a request, the Services send the request and relevant excerpts of Customer Data to a Third-Party AI Provider, and may send content to a Third-Party AI Provider to create embeddings, extract information, and re-rank search results. The Third-Party AI Providers in use on the Effective Date are listed in Annex III to Schedule B. Provider may add, replace, or remove models and Third-Party AI Providers under Schedule B.
9.2 Output can be wrong. Output may be inaccurate, incomplete, out of date, or inappropriate, and may be similar to Output generated for others. Output is not legal, financial, medical, employment, or other professional advice. Customer is responsible for reviewing Output before relying or acting on it, and for decisions made using it. Provider is not responsible for Output or for Customer’s use of it.
9.3 Third-party content and prompt injection. Content that Customer connects, such as email from outside senders and shared documents, may contain instructions written to manipulate AI systems. Provider may take steps to reduce that risk but does not warrant that AI Features will resist every attempt. Customer is responsible for reviewing drafts and previews before it confirms an action.
9.4 Customer-Chosen AI Clients. When Customer connects a Customer-Chosen AI Client, the content from Customer Data that the client requests is transmitted to that client at Customer’s direction. Customer-Chosen AI Clients are not Provider’s Subprocessors. Their handling of that content, including storage, retention, and any use for training, is governed by Customer’s agreement with the client’s provider, and Provider is not responsible for it. Customer is responsible for choosing clients and plans whose data-protection terms suit its content, and for the permissions it gives them.
9.5 Ownership of Output. As between the parties, and to the extent the law allows, Customer owns the Output generated for it from Customer Data. Provider does not promise that Output is unique or that intellectual-property rights protect it.
9.6 Human oversight and restricted uses. Customer will not use the Services or Output as the sole basis for decisions that have legal or similarly significant effects on individuals, including hiring, firing, promotion, compensation, or performance evaluation of workers, and will comply with Schedule C.
10. Proprietary Rights
10.1 Provider’s rights. Provider and its licensors own the Services, including the software, models, prompts, ontologies, workflows, interfaces, and documentation, all improvements to them, and all intellectual-property rights in them. Provider grants Customer a limited, non-exclusive, non-transferable, non-sublicensable right during the Term to access and use the Services for its internal business purposes under this Agreement. Provider reserves all rights not expressly granted.
10.2 Customer’s rights. Customer keeps all rights in Customer Data, subject to the license in Section 7.1.
10.3 Feedback. If Customer or an Authorized User gives Provider suggestions or feedback about the Services, Provider may use them without restriction or payment and without any obligation to Customer. Feedback does not include Customer Data.
10.4 Third-party and open-source components. The Services include third-party and open-source components that are governed by their own license terms.
11. Confidentiality
11.1 Definition. “Confidential Information” means non-public information that one party (the “Discloser”) gives the other (the “Recipient”) that is marked confidential or that a reasonable person would understand to be confidential. Customer Data is Customer’s Confidential Information. Provider’s non-public features, pricing, and security information, including any security summary or questionnaire response, are Provider’s Confidential Information. Confidential Information excludes information that (a) is or becomes public without the Recipient’s breach, (b) the Recipient already knew, (c) the Recipient received from a third party with no duty of confidentiality, or (d) the Recipient developed independently without using the Confidential Information.
11.2 Obligations. The Recipient will use Confidential Information only to perform or exercise rights under this Agreement, protect it with at least reasonable care, and disclose it only to employees, contractors, advisers, and (in Provider’s case) Subprocessors who need to know it and are bound by confidentiality obligations at least as protective. The Recipient may disclose Confidential Information if the law requires, after giving the Discloser notice where the law allows.
11.3 Duration. These obligations last for three (3) years after this Agreement ends, and for as long as the information remains a trade secret. Provider protects Customer Data under Section 7 and Schedule B for as long as it holds it.
12. Disclaimers
12.1 As is. THE SERVICES, THE AI FEATURES, AND OUTPUT ARE PROVIDED “AS IS” AND “AS AVAILABLE.” TO THE FULLEST EXTENT THE LAW ALLOWS, PROVIDER DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, AND ACCURACY, AND ANY WARRANTY ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. PROVIDER DOES NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE, THAT OUTPUT WILL BE ACCURATE OR COMPLETE, OR THAT THE SERVICES WILL MEET CUSTOMER’S REQUIREMENTS.
12.2 Third parties. Provider makes no warranty about Third-Party Services, Customer-Chosen AI Clients, or Third-Party AI Providers, and is not responsible for their acts, omissions, outages, or changes.
12.3 Exclusive remedy. If the Services do not work as this Agreement describes, Provider will use commercially reasonable efforts to correct the problem. Subject to Section 14.3, if Provider does not correct it within a reasonable time, Customer’s sole and exclusive remedy is to terminate this Agreement.
12.4 Authority. Each party represents that it has the authority to enter into this Agreement.
13. Indemnification
13.1 By Customer. Customer will defend, indemnify, and hold harmless Provider, its affiliates, and their officers, directors, employees, contractors, and licensors (the “Provider Indemnitees”) against any claim, demand, action, investigation, or proceeding brought by a third party (including an Authorized User, an individual whose Personal Data is in Customer Data, a regulator, or a provider of a Third-Party Service), and against all resulting losses, damages, liabilities, fines, penalties, settlements, costs, and expenses, including reasonable attorneys’ fees (together, “Losses”), to the extent arising out of or relating to:
- Customer Data, including its collection, content, and lawfulness, and Customer’s rights, notices, and consents to provide it;
- use of the Services by Customer or an Authorized User in breach of this Agreement or Schedule C, or in violation of law or of a third party’s rights;
- any Customer-Side Compromise, and any action taken with Credentials issued to or used by Customer or an Authorized User;
- any action taken through the Services at an Authorized User’s instruction or within permissions an Authorized User granted, and any reliance on Output;
- Customer’s use of Customer-Chosen AI Clients and other Third-Party Services; or
- Customer’s failure to comply with laws that apply to it, including laws on employee monitoring, recording, privacy, and employment.
13.2 Exception. Customer has no obligation under Section 13.1 for Losses to the extent a court or arbitrator finally determines that a Provider Indemnitee’s gross negligence or willful misconduct caused them.
13.3 Procedure. Provider will give Customer prompt written notice of a claim, and a delay relieves Customer only to the extent it is prejudiced. Provider may elect to control the defense and settlement of the claim, with counsel of its choice, at Customer’s expense. If Provider does not so elect, Customer will control the defense with counsel reasonably acceptable to Provider and will not settle any claim in a way that admits fault by, or imposes any obligation on, a Provider Indemnitee without Provider’s written consent. Provider may take part in the defense with its own counsel at its own cost. Customer will cooperate.
13.4 Provider’s obligations. Provider gives no indemnity under this Agreement. Customer’s remedies for claims against Provider are limited as stated in Sections 12 and 14.
14. Limitation of Liability
14.1 Excluded damages. TO THE FULLEST EXTENT THE LAW ALLOWS, NEITHER PARTY WILL BE LIABLE TO THE OTHER FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, GOODWILL, OR SAVINGS, LOSS OR CORRUPTION OF DATA, BUSINESS INTERRUPTION, OR THE COST OF SUBSTITUTE SERVICES, EVEN IF ADVISED OF THEIR POSSIBILITY. THE PARTIES AGREE THAT, TO THE FULLEST EXTENT THE LAW ALLOWS, THE COSTS OF NOTIFYING INDIVIDUALS, CREDIT MONITORING, FORENSIC INVESTIGATION, REGULATORY FINES AND PENALTIES, AND THIRD-PARTY CLAIMS THAT ARISE FROM A SECURITY INCIDENT ARE CONSEQUENTIAL DAMAGES. THIS SECTION 14.1 DOES NOT LIMIT CUSTOMER’S OBLIGATIONS UNDER SECTION 13.
14.2 Cap. EXCEPT AS SCHEDULE D PROVIDES FOR CLAIMS ARISING OUT OF A SOW, PROVIDER’S TOTAL LIABILITY ARISING OUT OF OR RELATING TO THIS AGREEMENT, WHETHER IN CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, STATUTE, OR OTHERWISE, AND INCLUDING LIABILITY ARISING FROM A SECURITY INCIDENT OR FROM ANY BREACH OF SECTION 7, SECTION 8, OR SCHEDULE B, WILL NOT EXCEED THREE TIMES (3×) THE FEES FOR SEATS (NOT INCLUDING FEES UNDER ANY SOW) THAT CUSTOMER PAID TO PROVIDER IN THE TWELVE (12) MONTHS BEFORE THE FIRST EVENT GIVING RISE TO THE LIABILITY. THIS IS ONE AGGREGATE LIMIT FOR ALL CLAIMS TOGETHER, NOT A SEPARATE LIMIT FOR EACH CLAIM.
14.3 What the limits do not cover. Sections 14.1 and 14.2 do not limit or exclude liability to the extent applicable law, including California Civil Code section 1668, does not allow it to be limited or excluded, such as liability for a party’s own fraud, willful injury, gross negligence, or violation of law. They do not otherwise carve out liability arising from a Security Incident.
14.4 Customer’s liability. Customer’s liability for Fees, its obligations under Section 13, and its liability for breach of Section 4.5, Schedule C, or Section 10 are not subject to Section 14.1 or to any cap.
14.5 Allocation of risk. The Fees reflect this allocation of risk. The limits in this Section 14 are an essential basis of the bargain, apply even if a limited remedy fails of its essential purpose, and also protect Provider’s affiliates, licensors, and Subprocessors.
14.6 Time limit. To the extent the law allows, any claim arising out of or relating to this Agreement must be brought within one (1) year after the cause of action accrues, or it is barred.
15. Governing Law and Arbitration
15.1 Governing law. California law governs this Agreement and any dispute arising out of or relating to it, without regard to its conflict-of-laws rules. The Federal Arbitration Act governs Section 15.3. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
15.2 Informal resolution. Before starting an arbitration or lawsuit, a party will send the other a written notice describing the dispute, and the parties will try in good faith to resolve it within 30 days.
15.3 Binding arbitration. Except as Section 15.5 provides, any dispute arising out of or relating to this Agreement or the Services, including its formation, scope, and enforceability, will be resolved by final and binding arbitration administered by JAMS under its Comprehensive Arbitration Rules and Procedures (or its Streamlined Arbitration Rules, where they apply). One arbitrator will decide the dispute. The seat and venue of the arbitration will be Contra Costa County, California, and the language will be English. The arbitrator must apply California law and enforce this Agreement as written, including Section 14, and may not award damages that this Agreement excludes. Each party bears its own attorneys’ fees and half of the arbitration fees and costs, except as the arbitrator awards under applicable law. A court with jurisdiction may enter judgment on the award. The proceedings and the award are Confidential Information of both parties.
15.4 No class actions. The parties will arbitrate only on an individual basis. Neither party may bring or take part in a class, collective, consolidated, or representative action, and the arbitrator may not consolidate the claims of more than one person or entity. If a court finds this waiver unenforceable for a claim, that claim will proceed in court under Section 15.6 and the rest of this Section 15 continues to apply.
15.5 Exceptions. Either party may (a) bring an individual claim in small-claims court, and (b) seek temporary or injunctive relief in court to protect its intellectual property or Confidential Information or to prevent misuse of the Services, without first arbitrating.
15.6 Courts. For any matter that is not arbitrated, the state and federal courts located in Contra Costa County, California have exclusive jurisdiction, and each party submits to their jurisdiction and waives any objection to venue.
16. General
16.1 Entire agreement and order of precedence. This Agreement (the Order Form, these Terms, the Schedules, and any SOW) is the entire agreement between the parties on its subject and replaces all earlier proposals and agreements about it. If the documents conflict, the order of precedence is the Order Form, then Schedule B (for Personal Data), then these Terms and the other Schedules, then any SOW (for its own scope only). Customer’s purchase orders and other terms do not apply. This Agreement is separate from any other agreement between the parties, including any master consulting services agreement. No other agreement, and none of its confidentiality or liability terms, applies to the Services or Customer Data, and if another agreement conflicts with this Agreement on those subjects, this Agreement controls.
16.2 Changes. Except for price changes under Section 5.7, a change to this Agreement must be in writing and signed by both parties. Provider may update Annexes II and III to Schedule B as that Schedule describes.
16.3 Assignment. Customer may not assign or transfer this Agreement, by operation of law or otherwise, without Provider’s prior written consent. Provider may assign or transfer this Agreement, in whole or in part, to an affiliate or to a successor in a merger, acquisition, reorganization, or sale of all or part of its assets or of the Hive business, on notice to Customer. An assignment in breach of this Section is void.
16.4 Notices. Notices must be in writing and take effect when emailed to the notice contact in the Order Form, or to another address a party gives by notice. A notice of a claim to Provider must also be sent by courier to Provider’s address in the Order Form.
16.5 Force majeure. Neither party is liable for a delay or failure to perform, other than a failure to pay, caused by events beyond its reasonable control, including outages or changes of Third-Party Services and of cloud, telecommunications, or AI providers, internet or utility failures, labor disputes, natural disasters, war, terrorism, and government action.
16.6 Relationship and third parties. The parties are independent contractors. No one else has rights under this Agreement, except that the Provider Indemnitees, Provider’s affiliates, licensors, and Subprocessors may rely on Sections 13 and 14.
16.7 Compliance. Each party will comply with the laws that apply to its performance. Customer will not use or export the Services in violation of export-control or sanctions laws, and represents that neither it nor any Authorized User is on a restricted-party list.
16.8 Severability, waiver, and interpretation. If a provision is unenforceable, it will be enforced to the extent the law permits and the rest of this Agreement continues. A failure to enforce a right is not a waiver of it. Headings are for convenience only, and “including” means “including without limitation.”
16.9 Counterparts and electronic signature. The parties may sign any Order Form or SOW in counterparts and electronically.
Schedule A: Available Integrations
Customer may connect only the integrations in the table below that its Order Form includes. Access is limited to what Customer grants when it connects each integration, for example through Google OAuth scopes. Customer may revoke access at any time in its Google account or in Hive. Revoking access stops further retrieval but does not by itself delete content already stored (Section 7.2). Any integration the Order Form does not include requires a SOW or a signed amendment (Section 3.5). Provider’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements (Section 7.4).
| Integration | Content retrieved | Access requested | Actions on a user’s instruction |
|---|---|---|---|
| Gmail | Message bodies (very long messages are truncated), headers, and attachments including PDF text | Read, send, and compose (gmail.readonly, gmail.send, gmail.compose) | Send, reply, and create drafts |
| Google Calendar | Events and attendees | Calendar and events, read and write (calendar, calendar.events) | Create, update, and respond to events |
| Google Drive | Docs, Sheets, and Slides files, other Drive files, and Meet transcripts stored in Drive | Full Drive access, read and write (drive) | Create and update Docs, Sheets, and Slides |
| Google Docs | Documents stored in Drive (accessed through the Drive scope) | Same as Google Drive | Create and update Docs |
| Google Chat | Messages, spaces, and members | Read-only Chat scopes | None |
| Google Tasks | Tasks | Read and write (tasks) | Create and update tasks |
| Google Sheets (structured import) | Spreadsheet tabs imported as structured data | Read-only (spreadsheets.readonly) | None |
| HubSpot | Deals, contacts, and companies | CRM read scopes; write scopes only if Customer grants them | Create notes and update properties and deals, if write scopes are granted |
| Salesforce | CRM records | Read-only | None |
| Jira | Issues | API token | Comment on, transition, and assign issues |
| GitHub | Issues, pull requests, project boards, and file contents | Access token | Open pull requests |
| Google Analytics 4 and Search Console | Website analytics | Read-only | None |
| Read.ai and Granola | Meeting notes and transcripts | OAuth or token | None |
Google Drive access is full-Drive and read and write, so it covers every Docs, Sheets, and Slides file that an Authorized User can reach in Drive. The Google Docs row uses the same access.
Schedule B: Data Processing Terms
B.1 Scope. This Schedule applies to Provider’s processing of Personal Data in Customer Data on Customer’s behalf. Terms not defined here have the meanings given in the Agreement.
B.2 Roles and instructions. Customer is the controller (or CCPA business) and Provider is the processor (or CCPA service provider). The Agreement, together with Customer’s configuration and use of the Services, including instructions given by Authorized Users, are Customer’s documented instructions. Provider will tell Customer if it believes an instruction violates Data Protection Law. Provider may also process Personal Data as the law requires.
B.3 Provider’s commitments. Provider will: (a) process Personal Data only on Customer’s documented instructions, for the business purposes in Annex I, or as the law requires; (b) ensure that people authorized to process Personal Data are bound by confidentiality obligations; (c) maintain the security measures described in Section 8 and Annex II; (d) engage Subprocessors only under Section B.4; (e) taking into account the nature of the processing and the information available to it, help Customer with requests from individuals, security of processing, breach notification, and data-protection impact assessments; (f) delete Personal Data under Section 7.6; and (g) make information available to show compliance under Section B.6.
B.4 Subprocessors. Customer authorizes Provider to use the Subprocessors in Annex III. Provider will engage each Subprocessor under written terms, which may be the Subprocessor’s standard commercial terms, that require it to protect Personal Data to a standard appropriate to the services it provides. Provider will give Customer at least 30 days’ notice of a new or replacement Subprocessor, including a new AI model provider, by updating the list at www.objectedge.com/legal/hive-subprocessors or by emailing Customer’s administrator. Customer may object in writing within 15 days after notice, on reasonable grounds relating to data protection. If the parties cannot resolve the objection, Customer’s sole remedy is to terminate the affected Services by notice. Provider’s responsibility for its Subprocessors is subject to Section 14.
B.5 Security Incidents. Section 7.8 applies.
B.6 Information and audits. Provider will make available the security summary and questionnaire responses described in Section 8.4 to show compliance with this Schedule. If Data Protection Law gives Customer an audit right that cannot be waived, Customer may exercise it once a year on 30 days’ notice, during business hours, subject to Section 11, at its own cost, without access to other customers’ data, and after it has reviewed the information Provider has made available.
B.7 Requests from individuals. If Provider receives a request from an individual about Customer Data, it will promptly tell Customer and will not respond except to refer the individual to Customer, unless the law requires otherwise. Customer will tell Provider about any request that Provider must act on. Section 7.10 applies.
B.8 Return and deletion. Sections 7.6 and 7.7 apply.
B.9 International transfers. Provider hosts Customer Data primarily in the United States, and its Subprocessors may process it in the United States and other countries. If Customer tells Provider in writing that Customer Data includes Personal Data subject to the GDPR, the UK GDPR, or the Swiss FADP, the parties will sign the Standard Contractual Clauses and the UK Addendum, or another lawful transfer mechanism, which will then form part of this Schedule.
B.10 CCPA. To the extent the CCPA applies: (a) Customer discloses personal information to Provider only for the limited and specified business purposes in Annex I; (b) Provider will not sell or share personal information, and will not retain, use, or disclose it for any purpose other than those business purposes, outside the direct business relationship between the parties, or in any way the CCPA does not permit; (c) Provider will not combine personal information with personal information it receives from other sources, except as the CCPA permits; (d) Provider will comply with the CCPA obligations that apply to it, will provide the level of privacy protection the CCPA requires, and will tell Customer if it determines it can no longer do so; and (e) Customer may take reasonable and appropriate steps to ensure that Provider uses personal information consistently with Customer’s CCPA obligations and, on notice, to stop and remediate unauthorized use.
B.11 Liability. Each party’s liability under this Schedule is subject to Section 14.
Annex I: Description of processing
| Item | Description |
|---|---|
| Subject matter and duration | Providing the Services during the Term, then deletion under Section 7.6 |
| Nature and purpose (business purposes) | Retrieving, storing, indexing, and embedding content from Authorized Integrations; building and maintaining knowledge-graph records; generating summaries, tasks, drafts, and answers; taking actions an Authorized User requests; and operating, securing, and supporting the Services |
| Frequency | Continuous. Integrations sync on schedules, by push notification, and on use |
| Data subjects | Authorized Users, and people who appear in connected content, such as email correspondents, meeting participants, calendar invitees, chat participants, and contacts |
| Categories of Personal Data | Names, email addresses, job titles, employers, and contact details; the content and metadata of emails, attachments, documents, meeting transcripts, calendar events, chat messages, and tasks; Derived Data; and Account Data for Authorized Users |
| Sensitive data | Provider does not request special categories of data, but connected content may include some incidentally. Schedule C restricts its use |
| Retention | The Term, then deletion under Section 7.6. Certain logs are deleted automatically on a schedule, generally between 24 hours and 180 days depending on the log type |
| Hosting location | Google Cloud, region us-central1 (Iowa, United States) |
Annex II: Security measures (as of the Effective Date)
Provider may update these measures under Section 8.1.
- Hosting and encryption. Hosted on Google Cloud in the United States, with Google-managed encryption at rest (AES-256) and TLS on public endpoints.
- Application-layer encryption. The content of ingested email and meeting transcripts is encrypted at the application layer with AES-256-GCM, using keys wrapped by Google Cloud KMS. OAuth access and refresh tokens and other connector credentials are encrypted with envelope encryption using a separate KMS key.
- Secrets. Application secrets are held in Google Secret Manager and are not stored in code or deployment configuration.
- Tenant isolation. Customers’ data is logically separated. The database applies organization-level row-level security, with default deny when no organization is bound to a request, on the tables that hold email, document, meeting, chat, task, and knowledge-graph data. Automated tests check that isolation.
- Access control. Sign-in uses Google Sign-In, and access requires an email address on the organization’s approved list. Access is role-based, archived users are blocked, and a per-organization Seat cap applies. API keys are stored as hashed values. External AI clients connect through OAuth 2.1 with PKCE and short-lived access tokens.
- AI query limits. The assistant’s database query tool is read-only, limited to approved views, limited in time and rows returned, and subject to the same tenant isolation.
- Backups. Automated daily database backups, with point-in-time recovery for 7 days.
- Logging. Application logs are kept in Google Cloud Logging and retained for 30 days.
- Change control. Separate development, QA, and production environments with separate databases. Code changes require an approving review before they are merged, and automated tests, including tests of tenant isolation, run in the build pipeline.
Annex III: Subprocessors (as of the Effective Date)
| Subprocessor | Purpose | Customer Data processed |
|---|---|---|
| Google Cloud | Hosting, database, file storage, encryption keys, secrets, messaging, and logging | All Customer Data |
| Fireworks AI | Primary language-model hosting for the assistant | Prompts with excerpts of Customer Data and tool results |
| OpenAI | Embeddings, extraction, classification, speech-to-text, and fallback models | Ingested text (to create embeddings), transcripts, and prompts |
| Anthropic | Validation steps and fallback models | Prompts with excerpts of Customer Data |
| Voyage AI | Re-ranking of search results | Search queries and excerpts of candidate results |
| Perplexity | Deep-research tool, when used | The user’s research query |
| Tavily | Web search and web-page retrieval, when used | Search queries, which may include names |
| Stripe | Billing and payments | Organization name, billing email, and internal organization ID; card details go to Stripe directly |
| Telegram | Optional chat channel, only for users who link it | Messages and answers in that channel |
| Google Workspace | Provider’s system and billing email | Recipient addresses and message content |
Current list: www.objectedge.com/legal/hive-subprocessors.
Schedule C: Prohibited Data and Acceptable Use
C.1 Prohibited data. Customer will not connect, upload, or otherwise provide to the Services, and will configure its integrations so that the Services do not retrieve:
- protected health information or other health information regulated by HIPAA or similar laws, unless Provider has agreed in a signed business associate agreement to handle it;
- payment card numbers, card security codes, or bank account credentials;
- government-issued identification numbers, such as Social Security, passport, and driver’s license numbers, as a category of data Customer intends to process;
- biometric identifiers or genetic data;
- personal data of children; and
- data that is classified, controlled unclassified information, or subject to export controls.
C.2 Incidental sensitive data. Provider does not request special-category or other sensitive data, but connected email, documents, chats, and transcripts may contain some incidentally. Customer is responsible for deciding whether to connect content that is likely to contain it and for having a legal basis to do so. Customer will not use the Services to systematically collect, infer, or profile people by special categories of personal data, such as health, religion, ethnicity, sexual orientation, or union membership.
C.3 Prohibited uses. Customer will not use the Services:
- for automated decisions with legal or similarly significant effects, including employment decisions or evaluating workers’ performance, based solely on Output;
- for biometric identification, social scoring, or covert surveillance of individuals;
- for any purpose where a failure could lead to death, personal injury, or serious property damage;
- to send unsolicited bulk or deceptive email, or to harass, defraud, or mislead anyone;
- to create or distribute malware or to attack other systems;
- in violation of law or of the terms or policies of any Third-Party Service, including Google’s terms and API policies; or
- to develop or train competing AI models.
C.4 Enforcement. Provider may suspend or terminate under Sections 6.2 and 6.3 for breach of this Schedule. Customer’s indemnity in Section 13 applies to breach of this Schedule.
Schedule D: Services Under a SOW
This Schedule applies to services that Provider performs under a SOW. It does not apply to the Services, which are the Hive subscription.
D.1 What a SOW contains. Each SOW will describe the services, deliverables, schedule, staffing, fees, expenses, and any Background Technology involved. A SOW takes effect when both parties sign it.
D.2 Fees and expenses. Customer will pay the fees in the SOW. Unless the SOW says otherwise, Provider will invoice monthly, invoices are due within 30 days, overdue amounts bear interest under Section 5.6, and Customer will reimburse reasonable out-of-pocket expenses, including travel, lodging, and meals, with receipts on request. Section 5.4 (taxes) applies.
D.3 Independent contractor. Provider is an independent contractor. It decides the manner and means of its work and which personnel perform it, and its personnel are not Customer’s employees.
D.4 Ownership of deliverables. Subject to full payment of the fees under the SOW, Provider assigns to Customer its rights in the deliverables the SOW identifies, such as reports, documentation, and designs prepared for Customer, other than Hive Technology and Background Technology. Customer keeps ownership of its own materials and Customer Data.
D.5 Hive Technology and Background Technology. “Hive Technology” means the Services and everything built on, embedded in, or derived from them, including the Hive platform, connectors, ontologies, knowledge-graph structures, agents, prompts, workflows, models, SDKs, and all improvements to any of them, whether or not Provider develops them for Customer. “Background Technology” means other software, frameworks, tools, models, and know-how that Provider or its affiliates own or develop independently of Customer, including anything a SOW lists. Provider owns Hive Technology and Background Technology even if one is embodied in a deliverable, and no deliverable includes them.
D.6 Licenses. Customer may use Hive Technology embodied in a deliverable only through an active subscription to the Services and only during the Term. When Customer has paid the SOW fees in full, Provider grants Customer a non-exclusive, perpetual, worldwide license to use Background Technology, other than Hive Technology, that is embodied in a deliverable, solely together with that deliverable and for Customer’s internal business purposes.
D.7 Acceptance. Unless the SOW sets other acceptance criteria, Customer will review each deliverable within ten (10) business days after delivery and will either accept it or describe in writing how it materially fails to meet the SOW. Provider will correct the material failures it agrees exist. A deliverable is accepted when Provider has corrected it or, if Customer gives no written notice within that period, at the end of the period.
D.8 Warranty. Provider will perform services under a SOW in a professional and workmanlike manner, using personnel with skills suited to the work. Subject to Section 14.3, if it does not, Customer’s sole and exclusive remedy is for Provider to re-perform the non-conforming services or, if Provider cannot do so within a reasonable time, to refund the fees paid for them. This warranty does not apply to the Services, the AI Features, or Output, which Section 12 covers.
D.9 Customer responsibilities. Customer will give Provider timely access to the people, information, systems, and approvals a SOW requires. Customer is responsible for the Credentials and access it grants to Provider personnel, who will use them only for the SOW. If Customer causes a delay, Provider may adjust the schedule and fees.
D.10 Ending a SOW. Either party may terminate a SOW for any reason on thirty (30) days’ written notice, or under Section 6.2. Customer will pay for services performed and expenses incurred through the end date. Ending a SOW does not end the subscription. Ending the subscription ends any SOW that depends on the Services unless the SOW says otherwise.
D.11 Liability for SOW services. Section 14 applies to SOWs, with these changes. For claims arising out of a SOW’s services or deliverables, the cap in Section 14.2 is the fees Customer paid under that SOW, not three times that amount. Fees under a SOW do not increase the cap for claims arising out of the Services or Customer Data, and fees for Seats do not increase the cap for claims arising out of a SOW. Section 14.3 still applies.
D.12 Other terms. The rest of this Agreement applies to work under a SOW, including Customer’s indemnity in Section 13 and the confidentiality terms in Section 11. Customer Data that Provider personnel access for a SOW stays subject to Section 7 and Schedule B.