01Legal / Terms

Terms of service.

Last updated 16 November 2026

A. General Terms

A.1 Introduction

  1. As used in these terms and conditions (the “Terms of Service”), “we”, “us”, and “Rehive” means Rehive Inc., a Delaware corporation.

  2. Rehive offers various software products and services to help businesses create financial applications for their End Users, such as for wallets, payments and rewards. These are the Services (Section A.2). Any new features or tools that are added to the current Services shall be also subject to the Terms of Service.

  3. Rehive is a financial technology company, not a bank or licensed financial services provider. Rehive provides the technology platform; you, the Developer, build and operate your Program for your End Users; and any banking or other financial services are provided by Third-Party Financial Institutions, integrated by Rehive or directly by you, or by you where you are licensed to provide them.

  4. Rehive does not hold, or have custody of, your or your End Users’ Funds at any point. Funds are held by Third-Party Financial Institutions or by End Users themselves. The Services send your information and instructions, and those of your End Users, to Third-Party Financial Institutions and service providers on your instructions, as Section H.1.2 sets out, and those institutions and providers carry out the transactions, payments and transfers.

  5. As a condition to using the Website or any of the Services, you must read and accept these Terms of Service, including Rehive’s Privacy Policy. By signing up for a Rehive Account, using the Website, or using any of the Services, you are agreeing to these terms. Additional agreements, including the Software License Agreement, may apply depending on your Rehive Subscription and are incorporated by reference where applicable.

  6. The current Terms of Service are available at https://www.rehive.com/terms. If you do not agree, you must immediately cease using the Services. Questions about the Terms of Service should be sent to Rehive Support.

  7. “You” and “your” mean the Account Owner. The individual who accepts these Terms of Service on its behalf represents and warrants that they are authorized to bind it.

A.2 Definitions

Account Terms

  • “Account” means a Rehive account registered on the Website, or otherwise opened with Rehive, in the name of an Account Owner.
  • “Account Owner” means the organization in whose name an Account is created. It acts through an individual it designates (the “Account Representative”), who accepts these Terms of Service and signs the Commercial Agreement on its behalf and must be authorized to bind it. Rehive may rely on the Account Representative’s instructions and treat notices to them as notices to the Account Owner. The Account Owner’s details are those recorded as company details in the Admin Dashboard.
  • “Developer” means the Account Owner in its capacity as the party building, operating, and maintaining a Program on the Services, including its Program configuration and End User relationships. “Developer” and “Account Owner” are used interchangeably in these Terms of Service, and the term aligns with the terminology used by Third-Party Financial Institutions in their agreements with the Account Owner.
  • “Account Admin” means an Authorized User whose Staff Account has administrator-level access to an Account.
  • “Admin Dashboard” means the password-protected interface provided by Rehive for the administration and management of a Rehive Account, accessible only through a Staff Account or the Rehive Review Account.
  • “Staff Account” means a user account you create for a member of your team to work on the admin side of your Account, with the permissions you give it (see Section B.2.2), including those of the Account Representative, Account Admins and your support staff. A Rehive Review Account is not a Staff Account.
  • “Rehive Review Account” means a review account with administrator-level access that Rehive may keep on each Account and uses only as needed, to review configuration, review Program activity and data for the purposes in Section H.9 point 2, help resolve issues, support app store reviews, manage and reset Rehive Test User accounts without moving any Funds other than those of the Rehive Test User, and add risk signals and apply platform controls under Section D.6. Apart from Rehive Test Users and actions under Section D.6, Rehive does not use it to manage your End Users or to make day-to-day decisions about them or their transactions.
  • “Account Setup Process” means the steps required to configure your Account upon activation, including providing branding information, DNS configuration, linking third-party services, creating test users, and completing test transactions. The process may be more extensive depending on your onboarding requirements.
  • “Voluntary Account Closure” means the process initiated by the Account Owner to gracefully close its account and associated projects, including notifying Rehive, backing up data, communicating with End Users, settling outstanding fees, and requesting data deletion.
  • “Account Closure Date” means the final date on which access to the Production Project will be terminated by Rehive, as agreed upon following the Account Owner’s notification of intent to close its account.

Project Terms

  • “Project” means a Test Project or a Production Project.

  • “Base Configuration” means Rehive’s versioned template for the structure and default settings of a Production Project, as Rehive updates it from time to time (Section B.2.3 point 7).

  • “Program” means the financial product or service you operate for your End Users using the Services, including its configuration and End User relationships.

  • “Funds” means money or digital assets of actual value, as opposed to sandbox or test balances, whether held by a Third-Party Financial Institution or by End Users themselves, such as in self-custody wallets.

  • “Test Project” means a rate-limited project for training, integrations and testing. Only your and Rehive’s employees and contractors may use it. Test Users may use their own real details in it, and may use Funds where third-party sandboxes are insufficient. Rehive may reset or delete it at any time.

  • “Production Project” means a project on which a Program runs for its End Users, separate from any Test Project. Until Rehive sets it to Trial Mode, a Production Project is being set up and no End User may use it. From then on it is always in one of these modes:

    • “Trial Mode”: the stage for you to learn and test how your Program works on the Rehive Platform. Rehive sets the project to Trial Mode once you complete the initial setup steps Rehive provides. It is not yet open to real customers. Only Production Test Users may use it, within the usage limits Rehive sets.
    • “Pilot Mode”: the stage in which you run your Program with a limited group of real End Users you invite. Rehive sets the project to Pilot Mode after checking that it is set up correctly on the Rehive Platform (Section B.2.3). Only Production Test Users and Live Users you invite may use it, within the usage limits that apply (Section B.2.3).
    • “Live Mode”: the stage in which you may open your Program to the public. Rehive sets the project to Live Mode after Pilot Mode (Section B.2.3). Live Users may use it. Whether you open registration to the public or keep it to End Users you invite is your choice.

    Trial Mode, Pilot Mode and Live Mode help you learn how the Services work and help Rehive manage the risk of abuse of the Rehive Platform. Moving a project from one stage to the next is a technical and platform-risk step, not a compliance, licensing or legal approval of your Program (Section B.2.3).

    • “Restricted Mode”: Rehive has limited the Services on the project to help manage an unpaid invoice or another unresolved issue (Section B.5), a risk or another issue with your Account (Section B.4), or at your request. Rehive decides which Services stay available, which may be as little as a withdrawal-only route or self-custody key export for End Users (Sections B.8 and B.9). Fees still apply, except as Section B.4 provides.
    • “Suspended Mode”: Rehive has blocked all access to the project, for End Users and Authorized Users alike, under Section B.4 or Section B.5. Fees still apply, except as Section B.4 provides.
    • “Closed Mode”: the final mode. Your Account has been closed, by Rehive under Section B.5 or Section F or at the end of a Voluntary Account Closure (Section B.6), and the project cannot be reopened or reactivated. No one has access. No further Fees accrue, but Fees already owed and any early termination fee remain payable. Sections B.7 and B.9 apply to your data, apps and integrations.

User Terms

  • “Authorized User” means each person the Account Owner authorizes, through a Staff Account, to help manage the Program, including the Account Representative. Authorized Users act on the admin side of the Services, not as End Users.

  • “End User” means any person or business that uses your Program or a Test Project, whether through a Rehive Application or otherwise. Every End User is either a Test User or a Live User.

  • “Test User” means an End User on a Test Project.

  • “Live User” means any End User on a Production Project, including early access or beta participants and Production Test Users.

  • “Production Test User” means a Live User who tests a Production Project. There are two kinds:

    • “Developer Test User”: your employee or contractor whom you record as a Developer Test User (see Section B.2.3).
    • “Rehive Test User”: a Rehive employee or contractor testing as part of Rehive’s review or support (see Section B.2.3).

    A Production Test User always tests through their own End User account, in their own name, separate from any Staff Account or the Rehive Review Account.

  • “End User Data” means all data and information about End Users and their use of your Program that is submitted to, collected by or generated in the Services, whether it comes from End Users, from you, from a Third-Party Financial Institution or other provider, or from the Services themselves. It includes account and identity details, transactions and balances, and verification documents and results. It does not include Aggregated Statistics, de-identified or aggregated data, or risk signals Rehive keeps for its own platform controls (Section D.6.3 point 5).

  • “User Content” means content, data, and information shared, uploaded, or provided by an Authorized User through the Services.

Commercial Terms

  • “Fees” means, collectively, the Subscription Fees, Usage Fees, any Monthly Minimum Commitment, Passthrough Service Fees, Additional Fees and any other fees that apply under your Commercial Agreement.
  • “Subscription Fees” means the fees applicable to your Rehive Subscription for the Services.
  • “Usage Fees” means the variable fees for your use of the Services, calculated as set out in your Commercial Agreement (the Plan Terms for your Plan, which is your subscription level, and any signed terms that vary them).
  • “Share of Take”, “Share Rate”, “Transaction Floor”, “Monthly Minimum Commitment” (or “MMC”), “Monthly Transacting Users”, “Monthly Active Users”, “Rehive-Enabled Revenue”, “Net Revenue”, “Provider Costs”, “Revenue Streams” and “Billable Transaction” have the meanings given in your Commercial Agreement, where it uses them.
  • “Passthrough Services” means third-party services that Rehive makes available to you through an account or agreement Rehive holds with the provider, on that provider’s terms. Rehive’s role is limited to holding that account, setting up and changing the service’s configuration for your Program, maintaining the integration with it and billing you for it. Rehive shares the configuration it sets up, in its help center or on request, and that configuration is part of your Program configuration, for you to review. The provider delivers the service and makes its own decisions. Rehive does not carry out the provider’s service, and how your Program uses it is for you to decide (see Section C.2). Rehive charges for them (“Passthrough Service Fees”) as set out for each service.
  • “Revenue Statement” means a monthly statement of revenue not recorded on the Rehive Platform, provided where your Commercial Agreement requires one.
  • “Additional Fees” means fees for add-on packages, operational fees and professional services that you order separately from your Plan.
  • “Activation Date” means the date on which the first invoice under your Commercial Agreement is paid.
  • “Billing Date” means a date on which Fees are billed under your Commercial Agreement.
  • “Authorized Payment Method” means any valid payment method that you authorize Rehive to charge for Fees.
  • “Payment Processor” means Rehive’s authorized third-party payment processor used to charge Fees to your Authorized Payment Method.
  • “Taxes” means all applicable federal, provincial, state, local, or other governmental taxes, duties, fees, or charges related to your Rehive Subscription.
  • “Rehive Subscription” means an Account Owner’s subscription to the Services on its Plan.

Technical Terms

  • “Services” means the software products and services Rehive provides to you under these Terms of Service and your Commercial Agreement to help you build and run financial applications for your End Users. They include the Rehive Platform, the Rehive Extensions, the Rehive API, the Admin Dashboard, the Messaging Services, any Rehive Application Rehive provides or hosts for you, Rehive Support, and making Passthrough Services available to you. They do not include the services of Third-Party Financial Institutions or other third parties, including the Passthrough Services themselves, which those providers deliver (Section C.2).
  • “Software” means the software embedded in or related to the Website and the Services. Where your subscription includes codebase access, the Software License Agreement sets the license terms for the licensed code.
  • “Rehive Platform” means the core Rehive software comprising the User, Auth, and Ledger APIs, along with the documentation and Admin Dashboard. Available with all subscription levels or under the Software License Agreement.
  • “Rehive Extensions” means the value-added features and integrations built on the Rehive Platform and incorporated into Rehive Applications.
  • “Rehive API” means all software, including routines, data structures, object classes, protocols, programs, templates, libraries and interfaces, application programming interfaces (APIs), software development kits (SDKs), developer tools, technical documentation, Updates, and other materials related to the Rehive Platform and Rehive Extensions, whether tangible or intangible, in whatever form or medium that are made available by Rehive to you.
  • “API Credentials” means the credentials that allow you to make authenticated requests to the Rehive API.
  • “Private API Credentials” means the API Credentials generated through the Admin Dashboard.
  • “API Client” means the unique Rehive Application configuration (including API Credentials) generated through the Admin Dashboard.
  • “Rehive Application” means any app, website or interface built on the Rehive Platform or Rehive Extensions to serve your End Users, such as your web app on your own domain and your mobile apps in your own app store accounts. It includes custom applications and modified versions of Rehive-provided applications, which you may build only where your Commercial Agreement permits it. A Rehive Application is presented under your brand.
  • “Updates” means bug fixes, updates, upgrades, enhancements, modifications, and new releases or versions of the Rehive API.
  • “Beta Services” means pre-release or beta features that are in development and not yet available to the public, offered on a trial basis at Rehive’s discretion.
  • “Open Source Components” means any software component that is subject to any open source license agreement, including any software available under the MIT License (MIT), GNU Affero General Public License (AGPL), GNU General Public License (GPL), GNU Lesser General Public License (LGPL), Mozilla Public License (MPL), Apache License, BSD licenses, or any other license that is approved by the Open Source Initiative.
  • “Messaging Services” means the email and SMS messaging tools provided through the Services.

Hosting Terms

  • “Standard Hosting” means shared Rehive-managed cloud infrastructure used to host applications by default. Included in all subscription tiers at no extra cost.
  • “Dedicated Hosting” means isolated cloud infrastructure managed by Rehive, dedicated to a single client, where your Commercial Agreement includes it.
  • “Solution Pod” means a dedicated Rehive engineering team assigned to a client for custom development, integrations, and ongoing maintenance, where your Commercial Agreement includes one. Section D.5 applies to what a Solution Pod builds.

Reference Documents

  • “Plan” means the subscription tier you select for your Account (for example Standard, Premium or Enterprise). References in these Terms of Service to your subscription level or subscription tier mean your Plan.

  • “Plan Terms” means Rehive’s standard terms for each Plan, setting out its Subscription Fees, Usage Fees, included features, commitment term and related commercial terms. Plan Terms are versioned, and the version that applies to you is the one you last accepted (see Section E.2.3). The Plan Terms form part of your Commercial Agreement.

  • “Commercial Agreement” means the commercial terms agreed between you and Rehive for your Account, as in force from time to time. It is made up of:

    • the Plan Terms for your Plan, whether attached to a signed agreement (including one signed electronically, see Section A.5) or accepted when you select or change a Plan;
    • any Order Forms, and any amendments or other signed terms, that add to or vary them, such as add-ons, custom work, custom pricing, exceptions, or Enterprise terms on service levels, support or codebase access; and
    • any Enterprise Commercial Agreement, and any commercial agreement or pricing schedule you signed with Rehive before these Terms of Service took effect.

    The Commercial Agreement is incorporated by reference into these Terms of Service.

  • “Order Form” means a document Rehive issues to add an add-on, feature, custom work or other service to your Account, setting out its Fees and term, that your Account Representative signs or accepts, including in the Admin Dashboard or by email. Each Order Form forms part of your Commercial Agreement (see Section A.5).

  • “Written Agreement” has the meaning in Section H.1.

  • “Privacy Policy” means the current version of Rehive’s privacy policy located at https://rehive.com/privacy/.

  • “Software License Agreement” refers to the agreement that serves as an addendum to these Terms of Service, granting a license to access, use, and modify the frontend mobile and web application codebase. The Software License Agreement applies only to clients whose subscription includes codebase access, whether through an Enterprise Plan or a signed term in their Commercial Agreement.

  • “Full Software License” refers to the license granted under the Software License Agreement, where your Commercial Agreement includes it, providing a license to use, modify, and self-host the Rehive codebase, including both frontend and backend components.

Other Terms

  • “Third-Party Financial Institution” means a bank, licensed financial institution or financial infrastructure provider (for example an on/off-ramp, card issuing, custody or payments provider) that provides financial services to you or your End Users through an integration with the Services.
  • “Rehive Contracting Party” has the meaning in Section A.4.
  • “Rehive Managed Partner” means a third party that Rehive has approved to build, configure or operate Programs on the Services for Account Owners under its own agreement with them.
  • “Rehive Support” means the support channels Rehive gives you during onboarding, such as a support email address or a shared Slack channel, and any other support channel Rehive tells you about.
  • “Official Channels” means the channels Rehive uses to communicate with you about your Account: email to your Account Representative or to another contact you give Rehive for that purpose, notices in the Admin Dashboard, and your shared Slack channel with Rehive, where you have one. You are responsible for monitoring them.
  • “Website” means https://rehive.com.
  • “Business Day” means a day other than a Saturday, Sunday, or other day on which commercial banks in New York City, USA, or Johannesburg, South Africa, are authorized or required by law to be closed for business.
  • “Content” means the content, data and information that Rehive provides through the Services (Section G.1).
  • “Materials” means the content you upload to or create on the Services for your Rehive Application and its End Users, such as branding, text and images, and the descriptions and settings of your currencies, rewards and in-app products.
  • “Aggregated Statistics” means data and information related to your use of the Services that we use in an aggregate and anonymized manner, including to compile statistical and performance information related to the provision and operation of the Services.
  • “Confidential Information” has the meaning in Section D.2.
  • “Feedback” means any feedback, suggestions, ideas, feature requests or reviews you provide to Rehive regarding the Rehive API or the Services.
  • “DMCA Notice” means a notice of alleged copyright infringement that identifies the original copyrighted work, the allegedly infringing material, and is signed by the copyright holder or agent.
  • “Security Incident” means unauthorized access to, or disclosure, loss or alteration of, your data, End User Data or credentials that Rehive holds in the Services.
  • “Sanctions Lists” means the sanctions and restricted party lists of the United States (including those of the Department of the Treasury’s Office of Foreign Assets Control and the Department of Commerce), the United Kingdom, the European Union and the United Nations.
  • “Biometric Data” means face scans, face templates, liveness captures, voiceprints, fingerprints and similar measurements of a person’s physical characteristics used to identify them, and the selfie or other image they are taken from. It does not include identity documents, the data read from them, or the results and scores a verification check returns.
  • “KYC/KYB” refers to Know Your Customer/Know Your Business processes that financial institutions and businesses must perform to verify the identity of their clients and assess potential risks.

A.3 General Conditions

  1. Changes to these Terms. Rehive may amend these Terms of Service by posting the amended version at https://www.rehive.com/terms. Changes take effect when posted, unless the amended version states a later date. Rehive will tell you about material changes through an Official Channel. A longer notice period applies only where a Written Agreement (Section H.1) gives you one. Changes apply only from the date they take effect and never to anything that happened before it. Your continued use of the Services after a change takes effect is your acceptance of it. If a material change reduces your rights or increases your obligations under these Terms of Service and you do not agree to it, you may end the affected Rehive Subscription by written notice given within 30 days after Rehive tells you about the change, and it ends on the date of your notice. Rehive will refund prepaid Fees for the period after that date, Fees for Services used before it remain payable, and this is your only remedy for a change you do not agree to. A change required by law or regulation, a change that only adds Services or features, a change to the Plan Terms (which follow Section E.2.3), and a clarification that does not reduce your rights are not material changes for this purpose. No early termination fee applies to an exit under this point, and the notice periods in Sections E.2.2 and F.2.3 and the billing period in Section F.1 point 3 do not apply to it. If you need longer to wind down your Program, you may instead use Voluntary Account Closure under Section B.6, started within the same 30 days: the change applies to you until your Account closes, Fees apply until then, and no early termination fee applies.

  2. Lawful use. You may not use the Services for any illegal or unauthorized purpose, or in breach of any law that applies to you, including copyright law, U.S. federal law and the laws of the State of Delaware. Section C.1.2 sets out your responsibility for the laws and regulation that apply to your Program.

  3. Credentials. You are solely responsible for the activity that occurs using your API Credentials and your Staff Accounts, for keeping them secure, and for the permissions you give them and any user you create. Any request made with your API Credentials or through a Staff Account is treated as authorized by you. Rehive has no obligation to monitor, question or block activity that uses them, and may, but does not have to, suspend or revoke credentials it suspects are compromised.

  4. No resale. You agree not to reproduce, duplicate, copy, sell, resell, or exploit any portion of the Services, use of the Services, or access to the Services without the express written permission by Rehive.

  5. Rehive’s name. You shall not purchase search engine or other pay per click keywords (such as Google Ads), or domain names that use Rehive or Rehive trademarks and/or variations and misspellings thereof.

  6. Support. Technical support in respect of the Services is only provided to Authorized Users and not to End Users.

  7. Messages to you. The Services will send certain communications to you by short message service (SMS) messaging and email (for example, mobile verification, email verification and SMS multi-factor-authentication) through the Messaging Services. You consent to receive applicable messages whenever you add a mobile number, email address, or multi-factor SMS authenticator to your account. To unsubscribe, modify your notification preferences in your account settings or contact Rehive Support.

  8. Messages to your customers. The Services allow you to send certain communications to your customers by short message service (SMS) messaging and email (for example, sending transaction confirmation notifications) through the Messaging Services. You will only use the Messaging Services in compliance with these Terms of Service, the acceptable use policy of the messaging provider Rehive uses, which Rehive will make available to you, and our Acceptable Use Policy, and the laws of the jurisdiction from which you send messages, and in which your messages are received. You must provide your own Messaging Services credentials for your Production Projects.

  9. Survival. The sections hereof entitled “Account Terms”, “End User Accounts”, “Account Restriction And Suspension”, “Unpaid Invoices And Other Unresolved Issues”, “Your Data When Your Account Ends”, “Notices To Your End Users”, “Your Apps, Domains And Integrations When Access Is Limited Or Ends”, “Regulatory Compliance and Responsibilities”, “Third-Party Services Disclaimer”, “Your Content”, “Acceptable Use Policy”, “Rehive Rights”, “Platform Controls and Risk Management”, “Confidentiality”, “Feedback and Reviews”, “Work Rehive Builds For You”, “Payment of Fees”, “Effect of Termination”, “Intellectual Property and Content”, “Software License”, “API Usage Terms”, “Limitation of Liability”, “Indemnification”, “Warranties and Disclaimers”, “Relationship of the Parties”, “Public Announcements”, “Notices”, “Economic Sanctions”, “No Third Party Beneficiaries”, “Privacy and Data Protection”, “Governing Law and Dispute Resolution”, “Force Majeure” and “General” will survive the termination or expiration of these Terms of Service. So will any other provision that by its nature is meant to survive.

A.4 Rehive Contracting Party

  1. “Rehive Contracting Party” means Rehive Inc., a Delaware corporation, with its principal place of business at 1 Belvedere Pl, Suite 200, Mill Valley, CA 94941, United States.

  2. In the event that the Dispute Resolution provisions below are found not to apply, the parties irrevocably and unconditionally submit to the exclusive jurisdiction of the courts of San Francisco County, California with respect to any dispute or claim arising out of or in connection with the Terms of Service.

  3. Rehive B.V., a private company with limited liability registered in Amsterdam, may act as the Rehive Contracting Party only if explicitly agreed in writing.

A.5 Agreement Structure And Signing

  1. Agreement structure. The Terms of Service, including the documents it incorporates by reference, constitute the entire agreement between you and Rehive and govern your use of the Services and your Account, superseding any prior agreements between you and Rehive. The agreement structure is as follows: These Terms of Service provide the base terms for all users. The Privacy Policy governs how Rehive handles personal information and prevails on that subject. The Software License Agreement extends these Terms of Service as an addendum for customers whose subscription includes codebase access. The Commercial Agreement sets out the commercial terms for your Account: the Plan Terms for your Plan and any signed terms that vary them. In the event of a conflict between documents, the following order of precedence applies (highest to lowest):

    1. these Terms of Service
    2. Privacy Policy, on the handling of personal information
    3. Software License Agreement
    4. Commercial Agreement

    Notwithstanding this order:

    • (a) Commercial matters. The Commercial Agreement governs pricing, Fees, billing, Plans and commitment terms, and prevails over these Terms of Service on those matters. The Software License Agreement does not set commercial terms.
    • (b) Specific changes. Signed terms in a Commercial Agreement may vary a provision of these Terms of Service, or add to or amend a term of the Software License Agreement, only where they expressly identify that provision or term and state the change.
    • (c) Within the Commercial Agreement. Signed terms prevail over the Plan Terms only for the terms they expressly vary.
    • (d) Adding to the Commercial Agreement. An Order Form or amendment adds to your Commercial Agreement without replacing it, and prevails only for the items it covers. Unless it states otherwise, an Order Form runs to the end of your current commitment term and renews with it. Rehive does not need a new Commercial Agreement to add an add-on, feature or service.

    Guidelines, documentation and schedules referred to in these documents apply only where consistent with them and do not override them.

  2. Signing. You may sign your Commercial Agreement and other documents with Rehive electronically, including in the Admin Dashboard with a typed signature, under Rehive’s E-SIGN Consent (https://rehive.com/esign-consent/). An electronic signature has the same effect as a handwritten one. Rehive keeps a record of each signature, including who signed, when, and the signed document.

B. Account Management

B.1 Account Terms

  1. To access and use the Services, you must register for an Account by providing your full legal name, current address, phone number, valid email address, and any other information indicated as required. Rehive may reject your application for an Account for any reason, in its sole discretion. Rehive may restrict, suspend, terminate or close an existing Account, or stop offering the Services, only as these Terms of Service set out, in particular Sections B.4, B.5 and F.

  2. The Account Representative and every Authorized User must be at least 18 years old, or the age of majority where they live if that is higher.

  3. You confirm that you are receiving any Services provided by Rehive for the purposes of carrying on a business activity and not for any personal, household, or family purpose.

  4. You acknowledge that Rehive will use the email address you provide on opening an Account or as updated by you from time to time as the primary method for communication with you, together with the other Official Channels.

  5. You are responsible for keeping your password secure. Rehive cannot and will not be liable for any loss or damage from your failure to maintain the security of your Account and password.

B.2 Account Activation

B.2.1 Account Owner

  1. The Account Owner is the contracting party under these Terms of Service. The Account Representative must open the Account in the Account Owner’s name and represents and warrants that they are authorized to bind it to these Terms of Service and the Commercial Agreement. Rehive may ask for evidence of that authority. The Account Owner may change its Account Representative by telling Rehive in writing. A change does not affect any acceptance, agreement or instruction given by a previous Account Representative. Unless Rehive agrees otherwise in writing, the Account Owner must be the same legal entity that contracts with its Third-Party Financial Institutions, holds its app store accounts and domains, and is named as the provider of its Program to End Users. You must tell Rehive promptly if the Account Owner, the Account Representative or any of these arrangements change.

  2. The Account Representative must use an email address issued by the Account Owner. If the Account Representative is a contractor, a Rehive Managed Partner or otherwise not the Account Owner’s director, officer or employee, Rehive may accept an email address from another organization. For that, a director or officer of the Account Owner, or another person authorized to bind it (but not the Account Representative themselves), must authorize the Account Representative in a signed letter sent from an email address issued by the Account Owner.

  3. Your Account can only be associated with one Account Owner.

  4. An Account Owner may have multiple Accounts.

  5. Rehive may check the Account Owner, its owners and its representatives, including through third-party screening, and ask for updated documents. These checks are for Rehive’s own purposes, not a review of your Program. If you don’t provide what Rehive asks for, it may restrict your Account (Section B.4).

B.2.2 Staff Accounts

  1. Depending on your Rehive Subscription, you may be able to create one or more Staff Accounts allowing other people to access the Account. With Staff Accounts, the Account Owner can set permissions and let other people work in its Account while determining the level of access by Staff Accounts to specific business information (for example, you can limit Staff Account access to customer verification on the user page or prevent Staff Accounts from making any configuration changes).

  2. The Account Owner is responsible and liable for the acts, omissions, and defaults arising from use of Staff Accounts in the performance of obligations under these Terms of Service as if they were the Account Owner’s own acts, omissions, or defaults.

B.2.3 Activation And Onboarding

  1. Activation. Rehive starts delivering the Services once you have accepted your Commercial Agreement, whether by selecting a Plan and accepting its Plan Terms in the Admin Dashboard or by signing an agreement with Rehive, and paid its first invoice, which activates your Account (the Activation Date). If your Account is not activated and that invoice is unpaid 30 days after you accept the Commercial Agreement (or after the invoice is issued, if later), Rehive may end the Commercial Agreement by notice and cancel the invoice. Neither party then owes the other anything under it, except accrued rights and obligations that by their nature survive, such as confidentiality. Your Account and these Terms of Service continue.

  2. Start of the term. The term of your Rehive Subscription, including any commitment term under your Commercial Agreement, begins on the Activation Date, even if delivery for your Account is still in progress or your Rehive Application is not yet available.

  3. Project stages. Activation of your Account gives access to a Production Project and, where one is provided, a Test Project. The Production Project moves through Trial Mode, Pilot Mode and Live Mode (Section A.2). You must follow the onboarding steps and requirements Rehive provides for each stage in the Admin Dashboard and its help center, as Rehive updates them. Before Live Mode, only the End Users that the mode allows may use the project, within the usage limits in your Commercial Agreement or, where it sets none, those Rehive sets in the Admin Dashboard (for example on the number of End Users or the number, type and volume of transactions). Fees apply in Pilot Mode as in Live Mode. Rehive decides whether and when to set a Production Project to each mode, may require you to release a major new capability of your Program first to End Users you invite, and may later restrict or suspend the project under Sections B.4, B.5 and D.6.

  4. Your decisions and sign-off. You make the decisions that define your Program, such as its branding, audience, regions, End User verification, how Funds move, features and limits, and you review and confirm the configuration Rehive sets up from them. These decisions are yours and may affect your Plan and Fees. Before Pilot Mode, you must confirm to Rehive that your Program is ready for the End Users you invite. Asking Rehive to set your Production Project to Pilot Mode or to Live Mode is that confirmation, and so is serving Live Users. You alone are responsible for that readiness, including compliance, your Financial Crimes Program (Section C.1.5), licensing, regulatory approvals, End User terms, third-party arrangements and testing.

  5. What Rehive’s reviews mean. Rehive’s reviews, including its Pilot Mode review, check only that your Program is set up correctly on the Rehive Platform, that it fits your Plan, and that you have provided what Rehive requires. They do not assess your Program’s compliance, licensing, legal or commercial readiness, and they are not advice. Setting a Production Project to any mode does not approve, endorse or certify your Program or replace your sign-off, and Rehive makes no statement to anyone, including you, End Users, regulators and Third-Party Financial Institutions, that your Program is compliant or ready. Rehive’s reviews do not cover integrations you build or contract yourself. For those, Rehive may adapt or skip steps, and testing them and deciding when they are ready is yours alone.

  6. Projects already live. Where your Production Project was serving Live Users before Rehive introduced these stages, the onboarding Rehive carried out with you at the time stands in place of them. Rehive may ask you to complete any current step, or to confirm your decisions and your sign-off again, within the time Rehive reasonably sets. Points 4 and 5 apply to that earlier onboarding too.

  7. Your configuration. Rehive sets up your Production Project from the Base Configuration. It is a starting point for you to test and review, not advice and not a recommendation that it suits your Program. You may change settings within it, yourself in the Admin Dashboard or by asking Rehive Support. Changes to its structure (a “Custom Configuration”) are available only where your Plan or Commercial Agreement includes them. Rehive updates the Base Configuration over time, tells you through an Official Channel and records the updates in its help center. Some updates are optional. Others are mandatory: Rehive applies them, with or without your prior approval, and you may not override them (Sections C.2 point 9, D.6.1 and D.6.10). The Base Configuration as applied, your settings and every update are part of your Program configuration and are yours to review. Continuing to run your Program after an update confirms your sign-off for it. Adding a service, feature, provider, region or other capability is a change to your Program: points 4 and 5 apply to it, and your Fees may change.

  8. Apps, domains and app stores. Where your Plan includes a Branded Web App or App Store Management (as named in your Plan Terms), you must complete the Account Setup Process, providing the branding, domain (DNS) configuration, app store access, approvals and test account that Rehive’s onboarding steps require. Your domains and your Apple App Store and Google Play accounts must be in the Account Owner’s name, and you must keep those accounts active and secured with multi-factor authentication. Rehive prepares app store submissions from your Program and the information you give, you confirm them, and Rehive submits them on your behalf. A submission is not a review of your Program, publication depends on the app stores’ review, and you are responsible for what your apps and listings say.

  9. Test users. You must keep an accurate record of which End Users are your Developer Test Users and give it to Rehive on request. Rehive Test Users test with small transactions only, and their testing does not replace yours.

  10. Delivery timeframes. Timeframes for access, app store submissions and codebase access, and any remedy for delay, are set in your Commercial Agreement.

  11. Compliance Contact. You must keep a compliance contact, a person responsible for your Program’s compliance and risk decisions (your “Compliance Contact”), and their available hours, up to date in the Admin Dashboard. You must acknowledge a compliance matter Rehive raises within one Business Day, even if the full answer takes longer. For an urgent matter, Rehive may call your Compliance Contact, including outside their available hours. Section D.6.3 point 6 sets the time to decide manual actions and respond to risk notices.

B.3 End User Accounts

  1. Who may be an End User. Your End Users must accept your own terms before they use your Program (Section C.1.3). An End User who is an individual must be at least 18 years old, or the age of majority where they live if that is higher. A business End User must be validly formed and able to enter into contracts. End Users may not use the Services in or for a sanctioned country or region (Section H.7).

  2. Your responsibility. You are responsible for your End Users: for their Funds, for supporting them, for the accuracy of the content in your Program, and for their use of the Services, including keeping their accounts secure and following the laws that apply to them.

  3. No liability to End Users. Rehive has no agreement with your End Users and no liability to them. Subject to Section H, Rehive is not liable to you or to End Users for errors, unauthorized access, interruptions, viruses or content-related issues in your Program.

  4. Rehive’s marks. End Users may not use Rehive’s trademarks or intellectual property without Rehive’s prior written permission.

  5. Breach by an End User. If an End User does not meet the requirements of this section, you must act on it, and Rehive may restrict or end that End User’s access under Sections B.4 and D.6.

B.4 Account Restriction And Suspension

  1. When Rehive may act. Rehive may restrict or suspend your, your Authorized Users’ and your End Users’ access to the Services at any time, with immediate effect, with or without notice and without giving a reason. A restriction limits access to some of the Services so that the issue can be managed, for example by pausing new registrations or deposits or by leaving only a withdrawal-only route, and puts the affected Production Projects in Restricted Mode. A suspension blocks all access and puts them in Suspended Mode. Rehive decides which applies and may move from one to the other. Examples of when Rehive may restrict or suspend include where:

    • there is a threat to, or an attack on, Rehive’s systems, or your use of them poses a security risk to Rehive, its other customers or its vendors;
    • Rehive knows or suspects that you, an Authorized User or an End User are using the Services for fraudulent or illegal activity;
    • you fail to pay the Fees you owe;
    • you or an Authorized User breach these Terms of Service or any other terms or policies that are part of your agreement with Rehive;
    • the law, a regulator, a law enforcement authority, a Third-Party Financial Institution or another provider requires or requests it, or a vendor has suspended or ended a service Rehive needs to provide the Services to you;
    • you stop carrying on business in the ordinary course or become subject to insolvency or similar proceedings, subject to applicable law; or
    • Rehive otherwise considers it necessary to protect the security, integrity or availability of the Services, its business or reputation, or other users.
  2. Steps and Fees. A restriction or suspension under this Section B.4 does not need to follow the steps in Section B.5. Fees continue to apply during a restriction or suspension caused by you, such as for unpaid Fees, a breach of these Terms of Service, a risk arising from your Program or its users, or a requirement of a Third-Party Financial Institution or other provider, a regulator or a law enforcement authority. For any other restriction or suspension, Fees for the Services you cannot use pause while it lasts.

  3. Notice. Rehive may, but is not required to, notify you of a restriction or suspension and of any steps you can take to resolve it.

  4. Restoring access. Rehive may restore access once it is satisfied that the reason for the restriction or suspension has been resolved.

  5. No liability. Subject to Section H.1, Rehive has no liability for any damage, liabilities, losses (including any loss of data or profits), or any other consequences that you, your End Users or any Authorized User may incur as a result of a suspension, restriction or account closure under Sections B.4 to B.6.

  6. If it is not resolved. If the issue behind a restriction or suspension is not resolved within a reasonable period, as Rehive determines, Rehive may close your Account under Section B.5 or terminate under Section F.2.1.

  7. Serious cases. Where Rehive acts because of suspected fraud, illegal activity, sanctions or a similar serious risk, it may suspend your Account at once, without notice to you or your End Users and without first restricting it or keeping a withdrawal-only route under Section B.8, and may act on the instructions of the relevant Third-Party Financial Institution, regulator or law enforcement.

B.5 Unpaid Invoices And Other Unresolved Issues

  1. What Rehive may do. Where an invoice is overdue, or Rehive has told you to fix something else, such as a breach of these Terms of Service, a requirement you have not met or a risk Rehive has asked you to address, Rehive may move your Production Projects into Restricted Mode, Suspended Mode and Closed Mode. Rehive decides which mode fits the situation, in what order and when, and may tell your End Users to withdraw their balances and export any self-custody keys (Sections B.8 and B.9).

  2. Notice and discretion. Unless it acts at once under Section B.4, Rehive normally tells you by email which steps it intends to take and when, so that you have time to put things right before access is blocked. The steps and dates it gives are not a commitment or a grace period: Rehive may change, skip, shorten or reorder them, and may restrict or suspend at once under Section B.4, for example for fraud, a security risk, a legal or regulatory requirement, a Third-Party Financial Institution requirement or a breach of these Terms of Service. Fees continue to apply until your Account is closed.

  3. Putting it right. At any time before your Account is closed, Rehive returns your Production Projects to their previous mode once all overdue invoices are paid and any other issue is resolved to its satisfaction. If you would rather close your Account, tell Rehive Support: once you and Rehive agree how the overdue Fees, and the Fees for the Voluntary Account Closure period (Section B.6), will be paid, Rehive pauses its steps and follows Voluntary Account Closure instead.

  4. Closure is permanent. When Rehive closes your Account under this Section B.5, your Production Projects are in Closed Mode. They and your Test Projects cannot be retrieved or reactivated. Section B.7 applies to exporting and deleting your data, Section B.9 to your apps, domains and integrations, and Section F.2.3 to any early termination fee. To use Rehive again, you must create a new Account and follow the standard onboarding process.

  5. Your End Users. You remain responsible for your End Users and their Funds throughout. To help End Users reach their Funds, Rehive may, but does not have to, send them notices under Section B.8, keep a project in Restricted Mode for longer with a withdrawal-only route or key export (Sections B.8 and B.9), move a suspended project back to Restricted Mode for a period, by agreement with you or on its own decision, so that End Users can withdraw or export their keys, and share information and coordinate with the relevant Third-Party Financial Institution. You authorize Rehive to take these steps. Rehive takes them for you and at your cost, and they do not make Rehive responsible for your End Users, their Funds or your Program.

  6. Not a wind-down plan. You should not rely on the steps Rehive takes or announces as a wind-down plan for your Program or your End Users. If you want an orderly wind-down, use the Voluntary Account Closure process in Section B.6. Rehive’s help center describes the steps Rehive typically takes; it is guidance, and Rehive may update it.

B.6 Voluntary Account Closure

If you want to close your Account, Rehive will work with you in good faith on an orderly wind-down for your End Users.

  1. Notice. Your Account Representative must tell Rehive Support in writing at least 90 days before the date you want to close, to allow an orderly wind-down for your End Users. Fees apply until the Account Closure Date, and any remaining commitment term is handled as Section F sets out.

  2. Timeline. Rehive confirms your request and agrees with you a timeline for the closure, including the Account Closure Date and how your End Users will be informed.

  3. Your part. Before the Account Closure Date, you must tell your End Users about the closure and give them the instructions and support they need, back up the data you need (Section B.7), and pay all outstanding Fees.

  4. Closure. On the Account Closure Date, Rehive ends access to your Account and sets your Production Projects to Closed Mode. Section B.7 applies to your data, including deletion at your request, and Section B.9 to your apps, domains and integrations.

B.7 Your Data When Your Account Ends

  1. Your records. You must keep the data and records you need, including any that laws, regulators or your Third-Party Financial Institutions require, in your own systems for as long as required. Rehive does not keep data for you for these purposes, and you should not rely on Rehive holding any data after the period in point 3.

  2. Exporting your data. While you still have access, you can export your Production Project data through the Admin Dashboard or the Rehive API. If you ask before, or within 30 days after, your Account closes or the Services end for any reason, Rehive will also provide your full Production Project data in a standard format within a reasonable time (normally 30 days), with reasonable support to complete the export. If your Account closes or the Services end because of unpaid Fees, Rehive may first require you to pay the overdue Fees. Further help is transition assistance under Section F.2.3.

  3. Deletion. Rehive keeps your Production Project and Test Project data for at least 90 days after your Account closes or the Services end, or 60 days where Rehive closes your Account under Section B.5. After that, Rehive may delete it without further notice. If your Account Representative asks Rehive to delete it, Rehive does so within 30 days of the request, or once your export is complete if later. Deleted data cannot be recovered.

  4. Data Rehive still holds. Data Rehive still holds after that period, including any the law requires it to keep or that it needs to establish, exercise or defend legal claims, is not available to you as a service. It remains confidential under Section D.2, and Rehive keeps personal data only as data protection law allows.

B.8 Notices To Your End Users

  1. Notices you approve now. You agree in advance that Rehive may send notices to your End Users about:

    • planned maintenance, outages and incidents affecting the Services;
    • migrations and other changes to the Services, your Rehive Applications or your integrations;
    • changes and actions that a Third-Party Financial Institution, app store or other provider requires, such as accepting new terms, completing verification or updating an app; and
    • the restriction, suspension or closure of your Production Project, or the end of the Services, where you have not completed a Voluntary Account Closure under Section B.6, for example because you did not meet your obligations on payment, usage limits or acceptable use, including how End Users can withdraw their Funds and export the private keys of any self-custody wallets.
  2. How. Rehive may send notices by email, SMS, push or in-app message, or as a notice in your Rehive Application, in your branding and through the Services’ notification tools, using the End User contact details held in the Services. Notices say they are sent on your behalf. Rehive normally tells you before it sends a notice, unless the law, a regulator or a Third-Party Financial Institution requires otherwise or an urgent risk does not allow it. You may not disable these notices. Where you host your own Rehive Application, you will show equivalent notices when Rehive asks.

  3. What notices say. Notices are factual: what is changing or closing, what End Users need to do, and who to contact, which is you or the relevant Third-Party Financial Institution. They make no statement about the amount of any End User balance or the safety of Funds, and give no advice.

  4. Providers first. Rehive may share information with the relevant Third-Party Financial Institution or other provider and follow its instructions about notices, and may hold back a notice where that provider objects or runs its own process.

  5. Withdrawal-only route and key export. Rehive may limit a Production Project in Restricted Mode to a withdrawal-only route for End Users, to self-custody key export, or to both, for a period it decides, but only where the relevant Third-Party Financial Institution or wallet provider allows it. Platform controls, including Mandatory Controls, continue to apply, and Rehive may close the route or end key export at any time. Neither is available once the project is in Suspended Mode or your Account is closed. Section B.9 point 6 says more about key export.

  6. An option, not an obligation. Rehive decides whether, when and how to send any notice or keep any route or key export open, and has no obligation to do any of them. Notices are sent on your behalf and at your cost.

  7. Your responsibility stays with you. These notices are not End User support and do not make Rehive responsible for your End Users, their Funds, your Program or its compliance. You remain responsible for your End Users, including answering them, giving any notice your Third-Party Financial Institutions or the law require, and returning their Funds. Rehive is not liable for the content or timing of a notice, or for not sending one.

  8. After the Services end. This section continues to apply after your Account closes or these Terms of Service end.

B.9 Your Apps, Domains And Integrations When Access Is Limited Or Ends

  1. While your project is restricted or suspended. Restricted Mode and Suspended Mode cover more than access to the Admin Dashboard and the Rehive API. Rehive may also, as it decides:

    • limit or switch off your Rehive Applications, including the web app on your custom domain and your mobile apps, or show only a notice in them or, in Restricted Mode, a withdrawal-only route;
    • stop submitting app updates and managing your app store listings;
    • pause custom extensions, custom applications and integrations that Rehive builds, hosts or runs for you; and
    • pause the use of the credentials you have linked to the Services for Third-Party Financial Institutions and other providers, and any Passthrough Service.

    Rehive restores what it paused when your Production Project returns to its previous mode.

  2. When the Services end. When your Account closes or the Services end for any reason, Rehive may, but is not required to unless you ask under point 3:

    • take your Rehive Applications offline and stop serving your custom domain;
    • remove your mobile apps from sale on your app store accounts, or publish a final version that shows only a closure or withdrawal notice, and then remove its own access to those accounts;
    • stop running custom extensions, custom applications and integrations that Rehive builds, hosts or runs for you. Their ownership follows Section D.5 and your Commercial Agreement, and Rehive does not have to hand over their code unless your Commercial Agreement or the Software License Agreement provides for it;
    • delete or disable the credentials you linked to the Services, and close any Passthrough Service account Rehive holds for your Program, as that provider’s terms allow; and
    • stop sending email, SMS and push messages for your Program.
  3. Your responsibility to request a wind-down. It is your responsibility to ask Rehive formally to wind down your apps, domain, credentials and data when the Services end. Rehive is not expected to remove anything for you unless you ask, and until you do, anything left in place, such as apps still listed, a domain still pointing to Rehive or credentials still linked, remains your responsibility. If your Account Representative asks in writing, through Rehive Support or by legal notice under Section H.6, Rehive will, within a reasonable time after the Services end: remove your mobile apps from sale and remove its own access to your app store accounts; stop serving your custom domain; delete the credentials you linked to the Services; and delete your data as Section B.7 sets out. Anything else you ask for is transition assistance under Section F.2.3.

  4. No obligation to keep anything live. Apart from any notices, withdrawal-only route or key export Rehive chooses to provide under Section B.8, Rehive has no obligation to keep your Rehive Applications, app store listings, custom domains, custom extensions, custom applications or integrations live, updated, or in line with app store or provider requirements while your Production Project is restricted or suspended, or after the Services end. Any action an app store or provider takes as a result is your responsibility, and, subject to Section H.1, Rehive is not liable for the steps in this section.

  5. Your part. Your app store accounts, domains and provider accounts remain yours and your responsibility. When the Services end, you must remove the DNS records that point your domains to Rehive, revoke at your providers the credentials and API keys you linked to the Services, and take any other steps your app stores, providers and End Users require. Rehive is not responsible for anyone’s use of a domain or DNS record you leave pointing to Rehive’s infrastructure after the Services end.

  6. Self-custody key export. This point applies where your End Users hold Funds in self-custody wallets through a Passthrough Service that runs on Rehive’s account with the wallet provider. In Restricted Mode, Rehive may limit those End Users to withdrawals, to exporting their private keys, or to both, in each case after they sign in to your Rehive Application. Suspended Mode blocks key export along with everything else, unless Rehive moves the project back to Restricted Mode for a period under Section B.5 point 5, and key export is not available through Rehive after your Account closes. Before it suspends such a Production Project under Section B.5, Rehive normally keeps key export available in Restricted Mode for a period, and its notice to End Users under Section B.5 tells them to export their keys. This does not apply to an End User whose withdrawals you or Rehive have paused or disabled (Section D.6.10 point 5), in the cases in Section B.4 point 7, or where the law, a regulator, a sanctions requirement or the wallet provider prevents it. Making sure your End Users export their keys in time is your responsibility. Where the wallet provider account is your own, key export after suspension or closure is between you and that provider.

C. Your Responsibilities And Conduct

C.1 Regulatory Compliance And Responsibilities

C.1.1 Rehive’s Role

  1. Software only. Section A.1 sets out Rehive’s role. Rehive provides software only: it is not a bank or licensed financial institution, and it does not hold, or have custody of, your or your End Users’ Funds.

  2. Integrations. Rehive provides out-of-the-box integrations with third-party providers for identity verification, custody and on/off ramps. These integrations let you connect your own accounts with these providers, or use a provider’s service that Rehive makes available as a Passthrough Service.

  3. Failed instructions. Rehive’s software may resubmit an instruction unchanged where the Third-Party Financial Institution reports that it failed or was not received. Rehive Support may also resubmit one manually, but only with your written consent for that instruction, for example in your shared Slack channel or a support ticket. A resubmitted instruction remains your or your End User’s original instruction. Rehive does not approve transactions and does not initiate or change them, except as Section H.1.2 point 2 sets out. A platform control under Section D.6 limits, pauses or blocks activity. It does not initiate or change a transaction. Resubmitting does not make Rehive responsible for the outcome.

  4. Reconciliation.

    • The record. Rehive’s records reflect the instructions sent through the Services and the results the Third-Party Financial Institution reports back. The institution’s records are the record of the Funds it holds, and for self-custody wallets the blockchain is the record.
    • Mismatches. If Rehive’s records don’t match them, Rehive helps you investigate as part of its standard support and, with your agreement, updates its records to match. A mismatch is not itself a loss and does not by itself show an error by Rehive. Mismatches caused by activity outside the Services, whether carried out directly with the provider or on the blockchain, or by the provider’s own systems, are your responsibility or the provider’s.
    • Your part. You must reconcile your records with your providers’ regularly. Raise any mismatch with Rehive within 10 Business Days of the statement, receipt or record showing it; Rehive can investigate a mismatch raised later only where the records are still available.
    • Liability. Rehive is liable for a loss connected to a mismatch only where Section H.1.2 point 4 applies, and a late report counts as contributing to that loss.

C.1.2 Your Responsibilities

You, the Account Owner, are responsible for the following, whether you use Rehive’s out-of-the-box integrations or your own integrations with other providers. Your Authorized Users act for you.

  • Laws and regulation. Complying with every law and regulatory requirement that applies to your Program: for the products you offer, the End Users you serve, and each country or region where you operate or where your End Users are. This includes working out which requirements apply to you. Rehive does not do this for you.
  • Licensing. Holding any license, registration or approval your activities need, or making sure your arrangements with your Third-Party Financial Institutions cover them.
  • Provider requirements. Meeting the requirements of your Third-Party Financial Institutions and other providers, as they change, including their terms and policies, the uses they permit and prohibit, their onboarding and verification requirements, their approval of your marketing, and their requests for information (Section C.2).
  • Third-Party Accounts. Setting up and maintaining your own accounts with Third-Party Financial Institutions, except for services Rehive makes available as Passthrough Services. Rehive provides integrations to connect these accounts, but does not manage those accounts or your relationship with those providers.
  • Provider fit. Confirming that the providers you choose meet the regulatory requirements for your use case and jurisdiction, even where they have built-in compliance features.
  • Guidelines. Making sure your team is familiar with, and follows, the integration and platform usage guidelines Rehive publishes from time to time (such as in its help center).

Summary. Rehive provides the technology and integrations. You are responsible for your Program’s legal and regulatory compliance, for your accounts with third-party providers, and for meeting their requirements.

C.1.3 Your End User Terms

  1. Minimum content. Your terms with End Users must, at least:

    • identify you as the provider of your Program;
    • say which Third-Party Financial Institution holds End User Funds, or that End Users hold them themselves, and require End Users to accept that institution’s terms where it requires this;
    • say that your third-party software and technology providers do not hold End User Funds, are not party to your relationship with End Users and have no liability to them;
    • set out End Users’ responsibility for their own credentials, devices and wallet keys;
    • allow access to your Program, or to an End User’s account, to be restricted, suspended or ended, and transactions to be paused or blocked, without liability of your third-party software and technology providers to End Users;
    • say that End Users with self-custody wallets are responsible for exporting and safeguarding their private keys, and that key export through your Program may be limited or may stop;
    • allow your third-party software and technology providers to send End Users notices about your Program on your behalf, including about maintenance, changes and withdrawing Funds if your Program closes; and
    • tell End Users that your third-party software and technology providers process their data to operate, secure and improve their services, prevent fraud and develop new features, including in de-identified or aggregated form, and give any other notice and obtain any consent the law requires for that.
  2. No misrepresenting Rehive. Your End User terms, marketing, app store listings and support content must not present Rehive as a party to your relationship with End Users, as a holder of End User Funds, or as a provider of financial services to End Users.

  3. Rehive’s check. Rehive may check that your End User terms are in place and linked from your Rehive Application, but does not review their content, and these minimums are not legal advice. You remain responsible for your End User terms (Section B.2.3).

C.1.4 Identity Verification (KYC/KYB)

  1. Three separate roles. Identity verification on your Program involves three separate parties:

    • Rehive’s software collects the information and documents your End Users submit, stores them in the Services, sends them to your verification provider and Third-Party Financial Institutions as their APIs or hosted verification flows require, and records the results and the verification status of each End User. Rehive does not verify identities or make KYC/KYB or other compliance decisions.
    • Your verification provider, a KYC/KYB provider you contract directly or that Rehive makes available as a Passthrough Service, carries out the checks and returns its results, based on the configuration set for your Program.
    • Your Third-Party Financial Institutions carry out their own KYC/KYB as their regulation and agreements require, and decide for themselves whether to onboard or keep serving an End User.
  2. Your configuration and decisions. The verification levels, checks, rules and workflows used for your Program, including any set-up or defaults Rehive configures as part of an integration, are your Program configuration (Sections B.2.3 and D.6.1). Within the workflows the Services provide, you can manage End User verification statuses in the Admin Dashboard, for example to approve, reject, request more information or override a result where the workflow allows it. Each of these decisions, and whether to accept an End User, is yours. You are responsible for your KYC/KYB obligations and for any override you make.

  3. Statuses are not approvals. A verification status in the Services records your provider’s results and your decisions. It is not a determination by Rehive, does not mean that a Third-Party Financial Institution accepts the End User, and does not replace that institution’s own checks. Where an institution requires its own verification or rejects an End User, its decision governs, and you must not use the Services to get around it.

  4. Verification data.

    • Storage and sharing. Rehive stores verification information and documents in the Services on your behalf, shares them with your verification provider and Third-Party Financial Institutions as needed to operate your Program, protects them under Section H.9 and handles them under Section B.7 when your Account ends. Some verification flows use Biometric Data.
    • Rehive’s use. Verification documents and results, including identity documents, the data read from them, liveness and match results and the signals a check returns, are End User Data, and Rehive may use them for the purposes in Section H.9 point 2, including to detect and prevent fraud and to build risk models and features. Rehive uses Biometric Data only to operate verification for your Program, to detect and prevent fraud and other risks, including by building and training risk models, and to test and improve the verification and risk features of the Services, and only where the law allows it. This includes review by Rehive’s staff. Rehive may keep and use statistics derived from verification, such as pass rates and liveness outcomes, that do not identify any person and contain no Biometric Data (Section D.1).
    • Your notices and consents. You must give End Users any notice, and obtain any consent, that the law requires for collecting, storing, sharing and using their verification data, including Biometric Data, in these ways, and you keep the verification records the law requires you to keep.
  5. Platform controls. Rehive’s platform controls under Section D.6 are measures Rehive takes to manage risk on its own platform. This includes Mandatory Controls, such as blocking sanctioned wallet addresses, risk signals, and a pause or other manual action on a single End User (Section D.6.3). They are not KYC/KYB or other compliance decisions about your End Users, and not applying one is not an approval.

C.1.5 Your Financial Crimes Program

  1. Your program. You must have, follow and keep up to date written policies and procedures to prevent money laundering, terrorist financing, sanctions breaches and fraud on your Program (your “Financial Crimes Program”), as the laws that apply to you and your Third-Party Financial Institutions require, and as fits your Program. It normally covers anti-money laundering and sanctions, onboarding and ongoing checks on End Users, transaction and account monitoring, fraud and identity theft, reporting suspicious activity, and staff training. These are examples, not a standard Rehive sets.

  2. Confirmation and copies. Your sign-off under Section B.2.3 point 4 confirms that your Financial Crimes Program is in place. You must give Rehive a copy when it asks, and give it to your Third-Party Financial Institutions and regulators as they require. Rehive asks for it for its own risk management and to answer its providers and any authority that asks. Rehive does not review it for adequacy, and receiving it is not advice or an approval.

  3. If it is missing. If you do not have a Financial Crimes Program, or do not give Rehive a copy when asked, Rehive may decline to set your Production Project to Pilot Mode or Live Mode and may restrict or suspend your Account under Section B.4. Section D.6.5 applies: nothing in this section makes Rehive responsible for your Financial Crimes Program or your obligations.

C.2 Third-Party Services Disclaimer

  1. Third-party services. The Services integrate with third-party services not owned or controlled by Rehive, including payment processors, banking providers, KYC/KYB providers, and other financial infrastructure.

  2. No responsibility. Subject to Section H.1, Rehive assumes no responsibility for the content, privacy policies, availability or practices of any third-party services, and you use them through the Services at your own risk. Section H.1.2 applies to Funds held by Third-Party Financial Institutions.

  3. No endorsement. Rehive does not endorse or guarantee third-party services.

    • Providers you contract directly. Your relationship with the provider, including its service, its fees and your obligations to it, is between you and the provider. Rehive supports its own integration with the provider’s service, not the service itself.
    • Passthrough Services. Rehive holds the account with the provider, but the provider delivers the service on its own terms. Points 4, 5 and 10 set out what this means for you.
  4. Third-party terms. You agree to comply with any terms and conditions set forth by third-party services you use, including the third-party terms that apply to a Passthrough Service, which Rehive will make available to you. You must give your End Users any notice, and get any consent, that those third-party terms require. If you breach them, Rehive may suspend that Passthrough Service.

  5. Third-party fees. Fees charged by third-party providers are your responsibility. Where you contract a provider directly, you pay that provider. Where Rehive makes a third-party service available to you as a Passthrough Service, you pay Rehive the Passthrough Service Fees. These are set for each Passthrough Service, in your Commercial Agreement or in a price list Rehive gives you before you start using it, and may differ from the third party’s own charges. Rehive tells you of any change to them in advance where it can, and otherwise as soon as reasonably possible.

  6. If a provider cuts you off. If a Third-Party Financial Institution or other third-party provider suspends, restricts or terminates your account, Program or access to its services (including through Rehive’s integration or a Passthrough Service), for any reason other than Rehive discontinuing that integration under point 7 and even where this materially affects your ability to use the Services:

    • this is not a breach by Rehive and does not entitle you to terminate for cause under Section F.2.2;
    • your Fees, commitment term and any early termination fee under Section F.2.3 continue to apply;
    • you are not entitled to any refund, credit or reduction of Fees; and
    • where an alternative provider is available, Rehive may help you integrate it on request, charged as Additional Fees.
  7. Discontinuing an integration. Rehive may discontinue an extension or integration for all clients, or for all clients in a country or region:

    • Notice. Rehive will give you reasonable notice, unless the discontinuation is outside its control, for example because the third party shuts down or ends its service.
    • Alternatives. Rehive will make reasonable efforts to source or integrate an alternative, but cannot guarantee that one will be available or equivalent. Using an alternative may require you to contract with the new provider.
    • Fees. Your Fees and commitment term continue, unless your Commercial Agreement provides otherwise.

    This point sets out your only remedies for a discontinuation.

  8. Your arrangement with the institution. How your Program works with a Third-Party Financial Institution, in every respect, is for you to decide and agree with that institution. This applies even where Rehive makes the institution’s service available as a Passthrough Service, and to any features you use to meet the institution’s requirements.

    Rehive provides the software and configuration options. Where Rehive sets up or configures an integration for you, it does so on your instructions, and the setup remains your responsibility. Neither this nor any configuration requirement Rehive sets under Section D.6 transfers any of your obligations to that institution, your End Users or any regulator to Rehive. You remain responsible for choosing a setup that meets those obligations and for meeting them, including presenting the institution’s current terms as it specifies and sharing any records it asks for.

  9. Changes required by providers. Third-Party Financial Institutions, app stores and other providers may require changes to how their services are integrated or used, such as new data, verification steps, disclosures, terms acceptance, app updates or a move to a new version of their service. Rehive may make these changes in the Services, your integrations, your configuration and your Rehive Applications, and roll them out to your Program without your prior approval, telling you where practical. Rehive has no obligation to make any such change, or to make it by a particular date, unless your Commercial Agreement provides otherwise. A change Rehive makes does not mean your Program meets the provider’s requirements: point 8 applies, and you remain responsible for any action the provider requires of you and for your obligations to it. Your Fees and commitment term continue.

  10. Ending a Passthrough Service for your Program. Rehive may suspend or end a Passthrough Service for your Program where the provider requires or requests it, or where Rehive considers that your Program puts Rehive’s account or standing with that provider at risk, for example because of its level of fraud, disputes or other risk. Rehive tells you in advance where it can. The consequences listed in point 6 apply in the same way. Where the provider allows it, you may contract that provider or another provider directly.

C.3 Your Content

  1. Providing content. You and your Authorized Users may upload, share or provide User Content through the Services. By doing so, you represent that you are legally allowed to and that it does not infringe any law or third-party right.

  2. License to Rehive. You grant Rehive a non-exclusive, fully paid-up and royalty-free license to process, analyze and use User Content solely for the purposes set out in Section H.9 point 2. To the extent the law permits, you waive, and will make sure your Authorized Users waive, any moral rights in it. User Content may be transmitted across networks and adapted to the technical requirements of connecting networks or devices.

  3. Your responsibility. You are solely liable for User Content. Rehive does not filter or moderate it and disclaims all liability for its accuracy, completeness or propriety.

  4. Removal. Rehive may remove, delete, block or rectify User Content at its discretion and without notice, and deny the Authorized User who provided it access to the Services, where:

    • Rehive receives a complaint about it;
    • Rehive receives a notice that it infringes a third party’s intellectual property rights;
    • a public authority orders it; or
    • Rehive is made aware that it may represent a risk for Authorized Users, third parties or the availability of the Services.

    This does not entitle you or your Authorized Users to any compensation, damages or reimbursement.

  5. Deletion requests. Rehive deletes User Content on your written request, subject to Section B.7 and the law. Rehive refers any request it receives from an End User to you, and acts on it directly only where the law requires that of Rehive. Please see our Privacy Policy for more information regarding each party’s right to retain, access, delete, and correct certain User Content.

  6. Claims. You agree to hold Rehive harmless from any claim or damage arising from User Content, or from its removal, deletion or modification by Rehive in accordance with these Terms of Service.

C.4 Acceptable Use Policy

  1. The Website and the Services may only be used within the scope of their purposes, subject to these Terms of Service and applicable law. You are responsible for making sure that your Authorized Users and End Users use them in the same way.

  2. You must not, and must not let your Authorized Users or End Users:

    • use the Services for illegal or fraudulent activity, or for an activity that your Third-Party Financial Institutions or other providers prohibit or do not support;
    • let another business operate its own financial product or service for its own customers through your Project, or resell or sublicense the Services, without Rehive’s prior written agreement;
    • get around usage limits, platform controls under Section D.6, or a restriction, suspension or closure, including by opening another Account or Project;
    • misrepresent Rehive’s role, for example by presenting Rehive as a bank, a holder of Funds or a provider of financial services, or as having approved your Program (Sections C.1.3 and H.5);
    • probe, scan or test the security of the Services without Rehive’s prior written agreement, access them without authorization, introduce malware or place an excessive load on them (Section G.3.3 also applies);
    • infringe the rights of a third party; or
    • abuse, threaten or harass any Authorized User, End User, or Rehive employee or contractor.
  3. Where Rehive knows or suspects, in its sole discretion, that this section has been breached, it may take any appropriate measure, including restricting or suspending access under Section B.4, terminating under Section F.2.1, removing content, and reporting the conduct to the appropriate judicial or administrative authorities.

D. Rehive’s Rights And Responsibilities

D.1 Rehive Rights

  1. Changes to the Services. Rehive may modify the Services at any time, and may suspend or discontinue the Services or any part of them as Sections B.4, C.2 point 7 and F set out. Subject to Section H.1, Rehive is not liable to you or any third party for a modification, suspension or discontinuation made under those sections. Not all Services and features are available in every jurisdiction, and Rehive is under no obligation to make any Services or features available in any jurisdiction.

  2. Price changes. Prices for using the Services are subject to change upon 60 days’ notice from Rehive. Such notice may be provided at any time by posting the changes to the Website or through an Official Channel. Where your Commercial Agreement includes versioned Plan Terms, Section E.2.3 applies instead.

  3. Maintenance and migrations. Rehive may carry out maintenance and upgrades, and migrate your projects, data, Rehive Applications and integrations to new infrastructure or versions. This may cause downtime or require action from you. Rehive tells you in advance where practical, and Section B.8 applies to notices to your End Users. Unless your Commercial Agreement includes a service level commitment, Rehive does not guarantee availability during maintenance or a migration, and has no obligation to carry out any particular maintenance or migration.

  4. Support and service levels. Support response times for each Plan are set in your Commercial Agreement (for Standard and Premium, in the Plan Terms). Any other service level commitments, including uptime guarantees and SLA credits, are governed exclusively by the Commercial Agreement and apply only to Enterprise clients whose Commercial Agreement includes such commitments.

  5. Access. Rehive may refuse access to the Services, for any reason, to anyone whose Account is not yet activated. For an activated Account, Sections B.4, B.5, C.4 and F set out when Rehive may restrict, suspend or terminate, including for a breach of the Acceptable Use Policy or suspected fraud, and Rehive has no obligation to do so. Rehive may also throttle or temporarily limit your use of the Services where it significantly exceeds normal usage or may affect the performance of the Services for other customers (Section G.3.4), and tells you where practical.

  6. Investigating and reporting. Rehive may, but has no obligation to, investigate any suspected violation of these Terms of Service or any misuse of the Services or the Website. Where Rehive suspects that you, an Authorized User or an End User has violated these Terms of Service or any law, rule or regulation, it may report any activity, data or persons to, and cooperate with: (i) law enforcement authorities; (ii) financial regulators and other government authorities; (iii) Third-Party Financial Institutions and other providers and vendors; and (iv) system administrators at Internet service providers, networks or computing facilities. This may include providing information about you, your End Users and your and their use of the Services, including IP addresses and other identifying information. Rehive may also disclose any information it thinks necessary to comply with applicable law, regulation, subpoena or other legal process or a governmental or regulatory request. Rehive does not have to tell you before or after it reports or discloses, and the law may prevent it from doing so. This right does not create a duty for Rehive to monitor, investigate or report, and does not replace any report you are required to make.

  7. Statistics and de-identified data. Rehive may monitor how you use the Services and collect Aggregated Statistics, which it may compile from your data. Rehive owns the Aggregated Statistics and any related intellectual property, and may share them publicly and use them as the law and the Privacy Policy allow. Rehive may also create de-identified or aggregated data from your data and End User Data that does not identify you, any End User or any other person, and may use it for any purpose, during and after your Rehive Subscription. Rehive owns that data. Section C.1.4 applies to Biometric Data.

  8. No exclusivity. Rehive makes no promise of exclusivity in any market segment. It may provide the Services to your competitors and launch products that compete with products you developed using the Services.

  9. Account ownership disputes. If the ownership of an Account is disputed, Rehive may ask for documents to confirm it, such as a business license, a government-issued photo ID, the last four digits of the card on file or proof of a person’s role at the Account Owner. Rehive may decide, in its sole judgment, who the rightful Account Owner and Account Representative are and transfer the Account accordingly. If it cannot reasonably decide, it may disable the Account until the parties resolve the dispute, without prejudice to its other rights and remedies.

D.2 Confidentiality

  1. What it covers. Each party (the “Receiving Party”) may receive Confidential Information of the other (the “Disclosing Party”) under these Terms of Service. Confidential Information is any non-public information about a party’s business, whether or not it is marked as confidential, including business and financial information, technical processes, software, documentation, product designs, pricing and costs, business plans, and information about customers, Authorized Users and End Users. Rehive’s Confidential Information includes non-public information about Rehive and the Services, including its security program and practices.

  2. Use and protection. The Receiving Party must:

    • use Confidential Information only as necessary to exercise its rights and perform its obligations under these Terms of Service;
    • disclose it only to its employees, agents, subcontractors and other representatives who need it for that purpose and are bound by confidentiality obligations at least as protective, and be responsible for their compliance;
    • protect it with at least the care it uses for its own sensitive information, and no less than reasonable care; and
    • tell the Disclosing Party promptly of any unauthorized use or disclosure, and take all reasonable steps to stop it.
  3. What is excluded. Confidential Information does not include information that the Receiving Party can show from its records:

    • it rightfully knew, without restriction on use or disclosure, before receiving it under these Terms of Service;
    • is or becomes public other than through a breach of these Terms of Service by the Receiving Party or its representatives;
    • it received on a non-confidential basis from a third party that, to its knowledge, was not bound to keep it confidential; or
    • it developed independently, without using the Confidential Information.
  4. Compelled disclosure. If the law compels the Receiving Party or its representatives to disclose Confidential Information, then, to the extent the law permits, it will promptly tell the Disclosing Party in writing, so that the Disclosing Party can seek a protective order or waive its rights, and give reasonable help in opposing or limiting the disclosure. If disclosure is still required, the Receiving Party discloses only the part it is legally required to disclose.

  5. Trade secrets. Notwithstanding anything else in these Terms of Service, the Receiving Party’s obligations for Confidential Information that is a trade secret continue for as long as it remains a trade secret under applicable law, other than through an act or omission of the Receiving Party or its representatives.

  6. Data use, providers and reporting. Nothing in this Section D.2 limits Rehive’s rights under Section D.1 points 6 and 7, Section D.6 or Section H.9 point 2. End User Data and other personal information are handled under Section H.9 and the Privacy Policy, which prevail over this Section D.2 on that subject. Rehive may share your Confidential Information with Third-Party Financial Institutions and other providers as needed to operate your Program and as Sections B.5, B.8 and D.6 provide.

D.3 Feedback And Reviews

You assign to Rehive all right, title and interest in any Feedback you give, and waive any rights in it that you cannot assign. Rehive may use, disclose and otherwise exploit Feedback for any purpose, as given or as modified, without attribution, payment, restriction or any obligation of confidentiality, and without needing permission or a license from you or any third party.

D.4 DMCA Notice And Takedown Procedure

Rehive responds promptly to valid DMCA takedown notices. To report alleged copyright infringement, email [email protected] with: (i) identification of the original work, (ii) identification of allegedly infringing material, and (iii) signature of copyright holder or agent. Upon receiving a valid notice, Rehive will notify the relevant party and may remove or disable access to the materials. Counter-notifications are handled per standard DMCA procedures, and materials are restored within 10 to 14 business days unless the complainant seeks a court order.

D.5 Work Rehive Builds For You

All extensions, components, applications, integrations and other deliverables that Rehive builds, maintains or delivers for you, including through a Rehive Solution Pod, remain Rehive intellectual property unless otherwise agreed in writing. You may use them as part of the Services during your Rehive Subscription.

D.6 Platform Controls And Risk Management

This section sets out what Rehive may do to manage risk on the Rehive Platform. Rehive does these things for its own risk management and at its sole discretion, and Section D.6.5 applies to all of them.

D.6.1 Platform Configuration Requirements

  1. Rehive may set and enforce minimum configuration requirements on all Programs and the Projects they run on, including through the Base Configuration (Section B.2.3 point 7). They are software-level defaults that reduce business risk for Rehive and for you.

  2. Any configuration Rehive applies under this Section D.6 becomes part of your Program configuration when it is deployed, and you are responsible for reviewing and approving it. You remain responsible for your Program’s configuration, compliance and operational decisions.

D.6.2 Platform Data Analysis

  1. Rehive may analyze platform data across all Programs, including transaction patterns and user activity, to identify anomalies, develop its understanding of fraud, improve rule templates and train automated detection models.

  2. Rehive does not have to disclose its methods or findings, and makes no representation that any pattern, anomaly or risk will be identified.

  3. Unless expressly agreed otherwise in writing, Rehive does not carry out transaction monitoring for you, and this analysis is not a substitute for your own.

D.6.3 Automated Rules And Platform-Initiated Actions

  1. Rules. Rehive may deploy automated rule templates on Projects that take preconfigured actions in response to platform events, such as adjusting transaction controls, limits and user access. The automated rules that run on your Project, whether from a rule template or configured for your Program, are its “Rules”.

  2. Changing Rules and manual actions. Rehive may enable, disable or change Rules on a Project at any time. Rehive may also take a manual action on a Project, an End User or a transaction whenever it considers it appropriate to manage a risk, whether or not a Rule exists for it. It may act on any signal, however small, and does not have to meet any standard of proof before it acts.

  3. How actions work and who decides. Automated and manual actions follow the same process: the action is applied and an alert is created for you. Rehive also tells you of a manual action through an Official Channel. A manual action may apply to a single End User or transaction, for example pausing an End User’s debits, or all of their transactions, so that you can review them. Manual actions are occasional spot checks. The final decision about your End Users is yours, and you make it by keeping or reversing the Reversible Control. The exceptions are a Mandatory Control and an action that the law, a regulator, a Third-Party Financial Institution or another provider requires of Rehive. You must review and decide each alert, and each case where cases are enabled on your Project, within a reasonable time, or within the time in point 6 where it applies. An alert or case you have not reviewed remains your responsibility.

  4. Not a determination. An action, whether automated or manual, is not a determination by Rehive about any End User’s compliance status, fraud risk or account standing. Rehive records actions, alerts and reversals in logs, and does not guarantee the timeliness, completeness or accuracy of any action. You handle any communication with the End User about an action, and must not present it as a decision or finding by Rehive.

  5. Risk signals. Rehive may add risk signals, such as a risk tag, to an End User’s record or to a transaction, automatically or by hand. A risk signal records something Rehive observed and is not a determination under point 4. The risk signals you can see are an input to the risk scoring and Rules on your Program, which you review and approve, and what they lead to is decided by those Rules and by you. Rehive may also keep risk signals that are not shown to you. Those feed only Rehive’s own platform controls, not your Rules. Rehive may use what it learns on one Program to add risk signals on another, without disclosing another client’s Confidential Information or identifying its End Users to you. Rehive is not obliged to add risk signals, to add them consistently, or to keep them up to date.

  6. Response time. You must make sure Rehive’s risk notices reach your Compliance Contact (Section B.2.3 point 11). You must review and decide each manual action, and respond to each risk notice from Rehive, within two Business Days. Until you decide, the control stays in place. A control does not lapse, and Rehive does not decide for you, because time has passed. If you do not respond in time, Rehive may restrict your Account under Section B.4.

D.6.4 Workflow Templates And Operational Guidance

  1. Rehive may give you workflow templates, operational guides and configuration recommendations. They are starting points only.

  2. You are responsible for reviewing, adapting and approving any process before you use it. Rehive is not liable for the outcome of your use of, or reliance on, these materials.

D.6.5 No Assumption Of Your Obligations

  1. What this section is not. Everything Rehive does or provides under this Section D.6, including configuration requirements, data analysis, Rules, manual actions, risk signals, templates, guidance, provider communications, use of linked credentials and information sharing, it does for its own risk management and at its sole discretion. None of it is a monitoring, compliance or fraud-prevention service provided to you, or legal, compliance or regulatory advice. None of it creates a duty of care, an obligation to continue, or a guarantee that any risk will be detected or prevented.

  2. Your obligations stay yours. Nothing in these Terms of Service, or in any platform feature, configuration, notification, template or communication from Rehive, means that Rehive assumes any of your obligations under the law, to any regulator, to your End Users or under your agreement with any third-party provider. This includes obligations for transaction monitoring, suspicious activity reporting, AML/CTF compliance, sanctions screening, KYC/KYB verification and regulatory reporting. You remain solely responsible for them, whatever platform features or controls Rehive provides.

D.6.6 Third-Party Provider Communication

  1. Contacting your providers. By linking credentials or API keys for a Third-Party Financial Institution or other provider to the Services, you authorize Rehive to contact that provider on your behalf whenever Rehive considers it useful, and to share with it the data about your Program, your End Users and their transactions that it needs, in order to debug an issue or to implement, maintain or support the integration. Rehive may also do so at your request, for example to compile and present platform configuration data or to help answer a provider’s inquiries. This is limited to technical and product matters. Rehive does not agree to anything, accept terms or make commitments for you, and what it shares is platform data, not Rehive’s assessment, endorsement or guarantee of your compliance, fraud controls or regulatory standing. Rehive has no obligation to contact a provider. Your relationship with the provider, and your obligations to it, remain yours (Section C.2 point 8), and you remain responsible for what is communicated on your behalf. You confirm that your agreement with the provider allows you to give this authorization.

  2. Rehive’s own communications. Rehive may also communicate with providers on its own account about aggregate, anonymized platform data and product-level matters. These communications do not reference specific clients’ Programs, except for a Passthrough Service your Program uses, as Sections B.5, B.8 and D.1 point 6 provide, or where Rehive shares information to prevent fraud or other risks under Section H.9 point 2.

  3. Telling Rehive about provider action. Unless the law prevents it, you must tell Rehive promptly, through an Official Channel, if a Third-Party Financial Institution or other provider warns you about your Program, restricts it, places conditions on it, or tells you it may end its services to you. Rehive uses this to manage risk to the Rehive Platform and its integrations. It does not make Rehive responsible for resolving the matter with the provider, which remains yours (Section C.2 point 8).

D.6.7 Limitation Of Liability For Platform Controls

  1. Rehive is not liable for any loss, damage or disruption arising from the enforcement of platform configuration requirements or the exercise of any right under this Section D.6, such as transaction limits, verification requirements or user group restrictions. In particular, Rehive is not liable for:

    • false positives, including legitimate transactions or End Users that are blocked, restricted or deactivated;
    • the timing, accuracy, scope or completeness of any fraud prevention measure, including anything Rehive does not detect or act on; or
    • any misconfiguration introduced by Rehive in the deployment of a platform control or rule template.
  2. Platform controls may affect End User access and transactions. They are there to reduce shared business risk, not to guarantee against fraud, compliance failures or provider action.

D.6.8 Investigative Use Of Linked Provider Credentials

  1. You link credentials and API keys for Third-Party Financial Institutions and other providers to the Services so that the integrations work. Rehive may use them to run manual, read-only queries to investigate potential fraud, risk or platform-integrity concerns, and you authorize this as a condition of linking them.

  2. This use is limited to retrieving and viewing information. Rehive does not initiate, authorize, modify or complete any transaction, payment or transfer with those credentials for this purpose.

D.6.9 Provider Support Channel Access

  1. Rehive may ask for, and you may give, access to the channels you share with your Third-Party Financial Institutions and other providers, including shared support channels, so that Rehive can follow risk and fraud information relevant to your Program and the platform.

  2. Rehive takes part for information only. It does not act as your agent, and you remain responsible for your own communications and obligations with the provider.

D.6.10 Mandatory And Reversible Controls

  1. Two types. Platform controls under this Section D.6 are of two types:

    • Reversible Controls are applied with an alert to you. You may reverse them, and you make the final decision and bear its outcome. For example, Rehive may pause an End User’s debits, or all of their transactions, for you to review, and you decide whether to lift the pause.
    • Mandatory Controls are controls Rehive designates as necessary to address legal, sanctions, fraud or platform-integrity risks, including suspected crime or misuse of the Services. Rehive applies them at its sole discretion, and you may not disable, reverse or override them. For example, Rehive may permanently block on-chain transactions to wallet addresses it identifies as sanctioned or high-risk, or keep a pause on an End User or a transaction in place.
  2. Rehive decides the type. Rehive decides, in its sole discretion, whether a control is a Reversible Control or a Mandatory Control. It may change a Reversible Control into a Mandatory Control, and may apply a control again after you have reversed it. A Mandatory Control does not transfer any of your obligations to Rehive (Section D.6.5).

  3. A condition of the Services. Mandatory Controls are a condition of using the Services, and you accept their consequences, including any effect on End User access or transactions. If you object to a Mandatory Control, your only remedy is to terminate the Services under Section F.

  4. Not a finding. A control, whether a Reversible Control or a Mandatory Control, is Rehive declining to process activity on the Rehive Platform. It is not a finding about any End User, and the absence of a control is not an approval of any End User, transaction or Program.

  5. Access to Funds. A control limits what Rehive processes. It does not hold or move Funds. It does not affect Funds held at a Third-Party Financial Institution: whether and how an End User can reach them is between you and that institution, and you may work with it directly. For self-custody wallets, disabling an End User’s withdrawals also disables the export of that End User’s private key, so that you can block unauthorized use. Under a Reversible Control, you decide whether to lift the control, including to let the End User export their key before you end your relationship with them.

D.6.11 Cross-Platform Risk Information Sharing

  1. Rehive may share with you and other clients generalized information, risk indicators and recommended configurations drawn from patterns across the platform.

  2. It is shared in generalized, aggregated and anonymized form and does not identify, or reveal the Confidential Information of, any other client or End User. You are responsible for evaluating and acting on it.

  3. Section D.2 (Confidentiality) continues to apply to your Confidential Information.

E. Payments And Fees

This section sets out how Fees are billed and paid. Your Commercial Agreement sets out which Fees apply to you, their amounts and when they are billed.

E.1 Payment Of Fees

E.1.1 Fees

You will pay the Fees set out in your Commercial Agreement. New versions of the Plan Terms apply to you as set out in Section E.2.3.

Where you accept the Plan Terms electronically and sign nothing else, those Plan Terms are your Commercial Agreement, and your Fees under them are due, payable and enforceable under these Terms of Service (including Sections E.1.2 to E.1.7, B.5 and F.2) in the same way as Fees under a signed agreement.

If you use the Services without a signed or accepted Commercial Agreement, the current Plan Terms for your Plan apply to you, whether or not you review or accept them, with your Subscription Fees and features as shown in the Admin Dashboard. Rehive will make the Plan Terms available, for example in the Admin Dashboard or by email. Usage Fees under them, and any newer version, apply from the first billing month that starts at least 30 days after they are made available. Your subscription runs month to month until you sign or accept a Commercial Agreement.

E.1.2 Payment Method

Unless you and Rehive have otherwise agreed in writing, you must keep an Authorized Payment Method on file to pay for all incurred and recurring Fees. Rehive charges applicable Fees to it until the Services are terminated and all outstanding Fees have been paid in full. Unless otherwise indicated, all Fees and other charges are in U.S. dollars, and all payments shall be in U.S. currency.

E.1.3 Payment Processor

You authorize Rehive and the Payment Processor to charge the Authorized Payment Method for all Fees, and you represent and warrant that you are authorized to use it and to have Fees charged to it. You also agree to comply with the Payment Processor’s service agreement, if any. If Rehive receives notice that you have violated that agreement, Rehive may take action to comply with it, including by restricting or suspending your Account under Section B.4 or using any other remedy in these Terms of Service.

E.1.4 Billing Date

Fees are billed when and as often as your Commercial Agreement, or the price list for a Passthrough Service, sets out. Amounts billed in advance are not refundable, except as these Terms of Service provide.

You will be charged on each Billing Date for all outstanding Fees that have not previously been charged. Invoices are sent to you by email and appear in the Admin Dashboard. You must raise any billing dispute within 14 days of the invoice date.

E.1.5 Payment Attempts

If a payment fails, Rehive may try again. Unpaid invoices are handled under Section B.5 (Unpaid Invoices And Other Unresolved Issues).

E.1.6 Late Payments

If you fail to make any payment when due, then, in addition to all other remedies that may be available to Rehive:

  • Rehive may charge interest on the past due amount at the rate of 1% per month calculated daily and compounded monthly or, if lower, the highest rate permitted under applicable law; and
  • you shall reimburse Rehive for all reasonable costs incurred by Rehive in collecting any late payment of amounts due or related interest, including attorneys’ fees, court costs, and collection agency fees.

E.1.7 Revenue Reporting And Verification

Rehive measures your usage from Rehive Platform records. You give Rehive the information and records it needs to calculate and check your Fees, as set out in your Commercial Agreement. Where your Commercial Agreement does not set this out, the reporting and verification terms of the current Plan Terms for your Plan apply.

E.2 Initial Term And Renewal

E.2.1 Initial Term

Your Rehive Subscription starts on the Activation Date and runs for the commitment term in your Commercial Agreement or, if there is none, month to month.

E.2.2 Renewal Term

  1. At the end of a commitment term, your Rehive Subscription renews automatically for a term of the same length (each a “Renewal Term”). A month-to-month subscription renews each month.

  2. Either party may prevent renewal by written notice at least 90 days before the end of the current term, or 10 days for a month-to-month subscription. You may also end it under Section E.2.3 or Section A.3 point 1.

  3. Your Commercial Agreement may set different renewal terms or notice periods, and billing frequency (for example monthly or annual) is separate from the commitment term.

E.2.3 Plan Versions

  1. When you select or change a Plan, you accept the current version of its Plan Terms, either by signing a Commercial Agreement that attaches them or by accepting them electronically. Rehive records your Plan, the Plan Terms version, and the date, time and user of each signature or acceptance, and that record is evidence of the terms that apply to you. Rehive will make the version of the Plan Terms that applies to you available to you on request.

  2. The Plan Terms version you accepted applies for your current commitment term.

  3. Rehive may publish new versions of the Plan Terms. Rehive will notify you at least 60 days before the end of your current commitment term of any new version that will apply to you, and it applies from the start of your next Renewal Term. During a commitment term, the Plan Terms that apply to you stay the same. The only exceptions are:

    • changes required by law or regulation;
    • changes to Passthrough Service Fees, or to the third-party terms that apply to a Passthrough Service, when the third party changes its charges or terms; and
    • where your Commercial Agreement provides for them, new Revenue Streams added by rate card, and changes to the supported services or custody model.

    Rehive will tell you about these in advance where it can, and otherwise as soon as reasonably possible.

  4. You may accept a newer version of the Plan Terms at any time before your next Renewal Term, for example where it is more favorable to you. It then applies from the date you accept it, and a new commitment term starts on that date.

  5. If you do not wish to continue under a new version notified under point 3, you may end your subscription at the end of your current commitment term by written notice before that date. The 90 day notice period in Section E.2.2 does not apply to that notice.

  6. Signed terms in your Commercial Agreement may fix pricing or a Plan Terms version for a longer period (a “Pricing Lock”), or set their own change process. Where they do, those terms apply.

E.2.4 Plan Changes

How you move between Plans, including upgrades, downgrades and what happens when you reach a Plan limit, is set out in your Commercial Agreement. Moving to or from Enterprise requires an Enterprise Commercial Agreement.

E.3 Refunds

Fees are not refundable once charged, including for partial periods, downgrades and unused services, unless these Terms of Service or your Commercial Agreement provide otherwise or the law requires a refund. If you think a charge is wrong, raise it under Section E.1.4.

E.4 Taxes

  1. All Fees are exclusive of Taxes, whether now in force or enacted in the future.

  2. You are responsible for all applicable Taxes that arise from or as a result of your Rehive Subscription or purchase of Rehive’s services. To the extent that Rehive charges these Taxes, they are calculated using the tax rates that apply based on the billing address associated with your Account that you provide to Rehive. Such amounts are in addition to the Fees for such services and will be billed to your Authorized Payment Method. If you are exempt from payment of such Taxes, you must provide Rehive with evidence of your exemption, which in some jurisdictions includes an original certificate that satisfies applicable legal requirements attesting to tax-exempt status. Tax exemption will only apply from and after the date Rehive receives evidence of your exemption that is satisfactory to it. If you are not charged Taxes by Rehive, you are responsible for determining if Taxes are payable, and if so, self-remitting Taxes to the appropriate tax authorities in your jurisdiction.

  3. For the avoidance of doubt, all sums payable by you to Rehive under these Terms of Service shall be paid free and clear of any deductions or withholdings whatsoever. Other than any Taxes charged by Rehive to you and remitted to the appropriate tax authorities on your behalf, any deductions or withholdings that are required by law shall be borne by you and paid separately to the relevant taxation authority. Rehive shall be entitled to charge the full amount of Fees stipulated under these Terms of Service to your Authorized Payment Method ignoring any such deduction or withholding that may be required.

  4. You must maintain an accurate jurisdiction of incorporation in the Admin Dashboard, and update it promptly if it changes.

F. Cancellation And Termination

F.1 Cancellation By Account Owner

  1. You may cancel your Account at any time by written notice to Rehive Support, following the instructions it gives you.

  2. Cancelling during a commitment term ends automatic renewal and is a termination for convenience under Section F.2.3, so the early termination fee in point 2 of that section applies, unless Section A.3 point 1 applies or your Commercial Agreement provides otherwise.

  3. If you have a Production Project in Pilot Mode or Live Mode, your Account closes through Voluntary Account Closure (Section B.6), and billing continues for the 90 days that process needs.

F.2 Termination Conditions

F.2.1 By Rehive

Rehive may terminate your Rehive Subscription and these Terms of Service, effective immediately and without notice, in the cases in points 1 to 4, and on notice under point 5.

  1. Unpaid Fees. You fail to pay any amount due within 30 days of its due date.

  2. Repeated late payment. Three or more late payments occur within 12 months.

  3. Unresolved restriction or suspension. The issue behind a restriction or suspension is not resolved (Sections B.4 and B.5).

  4. Breach or risk. Rehive determines, in its sole discretion, that you have breached these Terms of Service or that continuing to provide the Services would expose Rehive to legal, regulatory, security or reputational risk. Where Rehive terminates under this point for a risk that does not arise from your breach of these Terms of Service, it refunds any prepaid Fees for the period after termination and no early termination fee applies. Rehive may otherwise terminate for convenience only under point 5 or Section F.2.3, and then refunds any prepaid Fees for the period after termination.

  5. Discontinuing the Services. If Rehive decides to stop offering the Services altogether, it may terminate on at least 90 days’ written notice, given at any time, including during a commitment term or a renewal period. No early termination fee applies, and Sections B.7 and B.9 apply to your data, apps and integrations.

F.2.2 By Either Party

Either party may terminate, effective on written notice, where the other party:

  1. materially breaches these Terms of Service or the Commercial Agreement and fails to cure the breach within 30 days of receiving notice of it; or

  2. becomes insolvent or bankrupt, or is subject to similar proceedings.

This does not limit Rehive’s rights under Section F.2.1.

F.2.3 General Termination

  1. During a commitment term. Either party may terminate with at least 90 days’ prior written notice.

  2. Early termination fee. If you terminate for convenience during an active commitment term (as specified in the Commercial Agreement), you shall pay the remaining Subscription Fees and any Monthly Minimum Commitment under your Commercial Agreement for the balance of the commitment term as an early termination fee. This amount becomes due within 14 days of the termination notice. Usage Fees are not part of the early termination fee; Usage Fees and Passthrough Service Fees incurred up to the termination date remain payable. The same early termination fee applies, and is due within 14 days after termination, where Rehive terminates, or closes your Account under Section B.5, during an active commitment term because of your unpaid Fees or your breach of these Terms of Service (Section F.2.1).

  3. Refunds. No refund of prepaid Fees, except as Section A.3 point 1 or Section F.2.1 points 4 and 5 provide or where Rehive terminates for convenience under point 1.

  4. After a commitment term. Either party may terminate with at least 90 days’ prior written notice before the end of the current renewal period, or 10 days for a month-to-month subscription (Section E.2.2). Section F.1 point 3 applies where you have a Production Project in Pilot Mode or Live Mode. No early termination fee applies during renewal periods.

  5. For cause. Section F.2.2 sets out termination for cause. No early termination fee applies where you terminate for cause. Point 2 sets out when one applies where Rehive terminates.

  6. After termination. Section B.7 applies to exporting and deleting your data. Transition assistance is available at Rehive’s then-current hourly rates.

F.3 Effect Of Termination

When your Rehive Subscription or these Terms of Service end for any reason:

  1. Rights and licenses. All rights and licenses granted to you under these Terms of Service, including under Section G, end immediately, and your access to the Software, including Updates and support, ends.

  2. Software and Confidential Information. You must stop using the Software and the Rehive API, and destroy all copies of the Software and of Rehive’s Confidential Information within 10 days, certifying this in writing on request. Where the Software License Agreement applies, its terms on termination also apply.

  3. Fees. All outstanding Fees become due and must be paid within 14 days after termination, and Section F.2.3 point 2 applies to any early termination fee. Rehive sends you a final invoice by email. Once it is paid in full, you will not be charged again.

  4. Access. Rehive stops providing the Services, your Production Projects are in Closed Mode (Section A.2), and you can no longer access your Account or your Rehive Applications.

  5. Data, apps and integrations. Section B.7 applies to your data, and Section B.9 to your Rehive Applications, app store listings, custom domains, custom extensions, custom applications and integrations.

  6. Refunds. Unless these Terms of Service provide otherwise, you are not entitled to any refund of Fees, pro rata or otherwise.

  7. Accrued rights. Termination does not affect any right or obligation that arose before it, and the provisions listed in Section A.3 point 9 survive.

G. Intellectual Property And Customer Content

G.1 Intellectual Property And Content

  1. Ownership. Rehive does not claim any intellectual property rights over your Materials. They remain yours. You can remove Materials in the Admin Dashboard, and Section B.7 applies to your data when your Account ends.

  2. Permissions. By uploading Materials, you allow:

    • the people who use your Rehive Application to view the Materials you provide on it;
    • Rehive to store your Materials and, for Materials you post publicly, to display and use them on the Services; and
    • Rehive to review and delete, at any time, Materials that do not comply with these Terms of Service or the Software License Agreement, as Rehive determines in its sole discretion.
  3. Your responsibility. You are responsible for making sure your Materials comply with applicable laws and regulations. Materials your Authorized Users provide are also User Content, and Section C.3 applies to them.

  4. Your name and marks. By using the Services, you grant Rehive a non-exclusive right and license to use the names, trademarks, service marks and logos associated with your Account to identify you as a current or former customer, as Section H.5 permits.

  5. Rehive’s Content. Unless otherwise specified or clearly recognizable, the Content is owned by Rehive or its licensors, which hold all intellectual property rights in it. You and your Authorized Users may use the Content only as necessary for proper use of the Services, and may not copy, modify, distribute or create derivative works of it except as expressly permitted.

  6. Reporting infringement. If you suspect that the Services or the Content infringe the rights of a third party, contact Rehive Support.

  7. Templates. Rehive may provide templates for landing pages, terms of service, privacy policies, and business documentation. These templates are provided as starting points only and do not constitute legal or business advice. You are solely responsible for reviewing, customizing, and ensuring these templates meet your specific legal, regulatory, and business requirements.

G.2 Software License

  1. Rehive licenses the Software to you as part of the Services. It is not sold, and Rehive reserves all rights that these Terms of Service or the Software License Agreement do not expressly grant.

  2. The Software License Agreement applies only to clients whose Rehive Subscription includes codebase access. If your subscription tier does not include codebase access, the Software License Agreement does not apply to you. Codebase access is granted only where your Commercial Agreement includes it, and you must also sign the Software License Agreement. The Software License Agreement grants a Software License (frontend codebase access) or, where your Commercial Agreement includes it, a Full Software License (full codebase access including self-hosting rights). Access to the backend codebase is only available under a Full Software License, with a delivery period agreed in your Commercial Agreement.

  3. Where applicable, the Software License Agreement grants certain rights, including but not limited to the rights to use, execute, copy, or distribute the Software, to the extent determined by such license and your Rehive Subscription.

  4. The Software License Agreement serves as an addendum to these Terms of Service and provides additional terms specific to codebase access. Where both documents address the same topic, the Software License Agreement provides the more specific terms for codebase access, but does not override the base protections in these Terms of Service or the Privacy Policy.

  5. You may find further information regarding the license terms in the Software License Agreement, available at https://rehive.com/software-license or upon request for qualifying clients.

G.3 API Usage Terms

G.3.1 Access To The Rehive API

  1. You may not use the Rehive API where Section H.7 (Economic Sanctions) or any other applicable law prohibits it.

  2. Private API Credentials may be used only by you and by the service providers you authorize under point 4, and only for your Rehive Applications and your Program.

  3. Except as permitted herein, you must keep the API Credentials and all login information for your Account secure, you may not share the API Credentials with any third party, and you will not access the Rehive API by any means other than the API Credentials you receive in accordance with the terms in this section. API Credentials are the exclusive property of Rehive, and your access to and use of API Credentials is at Rehive’s sole discretion.

  4. You are not permitted to use a service provider in connection with providing your Rehive Application’s service unless they sign an agreement with you to:

    • protect any End User Data received from Rehive (at least as well as Rehive’s terms and policies require), and limit their use of End User Data solely to providing their services to your Rehive Application (and not for their own purpose or any other purpose); and
    • keep the End User Data secure and confidential.

    You must ensure that any service provider complies with these Terms of Service and any other applicable Rehive terms and policies, and you acknowledge and agree that any act or omission by a service provider amounting to a breach of these Terms of Service will be deemed to be a breach by you. If requested, you will provide a list of your service providers to Rehive.

  5. Access to certain APIs or SDKs may require a separate written agreement between you and Rehive.

G.3.2 API License

Subject to these Terms of Service and your applicable subscription level, Rehive grants you a worldwide, non-exclusive, royalty-free, non-transferable, non-sublicensable, revocable, and limited license to use and make calls to the Rehive API solely in connection with developing, implementing, and distributing your Rehive Application that interoperates or integrates with the Services (for a custom application or a modified version of a Rehive-provided application, only where your Commercial Agreement permits it), and solely in the manner described in these Terms of Service and in the technical documentation contained in the Rehive API. See the Commercial Agreement for API access included with each subscription tier.

G.3.3 API Restrictions

When using the Rehive API, you will (and will ensure that your employees, agents, and service providers will):

  • only use the Rehive API (including SDKs) to develop and distribute Rehive Applications or content for your use or an End User’s use with the Services;
  • restrict disclosure of the API Credentials, or any part thereof, to your agents, employees, or service providers, who must require access to use, maintain, implement, correct, or update your Rehive Application in accordance with the Terms of Service, and who are subject to confidentiality obligations the same as or greater than those contained herein;
  • not distribute, sell, lease, rent, lend, transfer, assign, or sublicense any rights granted by the Terms of Service or the Software License Agreement to any third party;
  • not use or access the Rehive API or the Services in order to monitor the availability, performance, or functionality of the Rehive API, the Services, or any portion thereof or for any similar benchmarking purposes;
  • not remove or destroy any copyright notices, proprietary markings, or confidentiality notices placed upon, contained within, or associated with the Rehive API;
  • not engage in any activity that interferes with, disrupts, harms, damages, or accesses in an unauthorized manner the servers, security, networks, data, applications, or other properties or services of Rehive or any third party;
  • not circumvent technological measures intended to prevent direct database access, or manufacture tools or products to that effect;
  • not modify, translate, reverse engineer, disassemble, reconstruct, decompile, copy, or create derivative works of the Rehive API, End User Data, any Account, the Services, or any aspect or portion thereof, except to the extent that this restriction is expressly prohibited by applicable law and except to the extent expressly permitted by the Software License Agreement;
  • not bypass Rehive API restrictions for any reason, including automating administrative functions of the Admin Dashboard;
  • not, except as authorized by Rehive in writing or as expressly permitted by the Software License Agreement, substantially replicate products or services offered by Rehive, including the Rehive API. Subject to the preceding sentence and the parties’ other rights and obligations under the Terms of Service (including confidentiality obligations and any restrictions on use of End User Data), each party agrees that the other party may develop and publish Rehive Applications that are similar to or otherwise compete with such party’s Rehive Applications;
  • not develop applications or integrations that excessively burden the Rehive system, or distribute spyware, adware, or other commonly objectionable programs;
  • not develop a Rehive Application whose primary purpose is to migrate Authorized Users or End Users from the Services;
  • not access or use the Rehive API to develop or distribute the Rehive Application in any way in furtherance of criminal, fraudulent, or other unlawful activity, or otherwise violate the Terms of Service;
  • not request more than the minimum amount of data from a Rehive API needed by your Rehive Application to provide the End User the intended Rehive Application functionality, or any data outside any permissions granted by the End User;
  • not falsify or alter any unique identifier in, or assigned to your Rehive Application, or otherwise obscure or alter the source of queries coming from a Rehive Application; and
  • not include code in any Rehive Application that performs any operations not related to the services provided by the Rehive Application, whether or not you have obtained End User consent to do so. For the avoidance of doubt, this prohibited activity includes embedding or incorporating code into any Rehive Application which utilizes the resources (including CPU resources) of another computer, including for the purposes of cryptocurrency mining.

G.3.4 API Limits

  1. Rehive may set and enforce limits on your use of the Rehive API (limiting the number of requests that you may make or the number of End Users you may serve), in its sole discretion.

  2. You agree to, and will not attempt to circumvent such limitations, including those documented at https://docs.rehive.com/platform/general-usage/throttling/. If you would like to use any Rehive API beyond these limits, you must obtain Rehive’s express written consent (and Rehive may decline such request or condition acceptance on your agreement to additional terms and/or charges for that use). To seek such approval, contact Rehive Support.

G.3.5 Open Source Software

Some of the software packages, libraries, or components required by or included in the Rehive API are or may become Open Source Components. To the limited extent that the license for Open Source Components expressly supersedes the Terms of Service, your use, reproduction, and distribution of any such Open Source Components is governed by the terms of the applicable open source software license and not these Terms of Service.

G.3.6 Updates

Rehive may require you to install or update software to continue using the Rehive API and the Services, and may make Updates to the Rehive API from time to time, at its sole discretion. You must implement and use the most current version of the Rehive API and make any changes to your Rehive Application that an Update requires, at your sole cost and expense. Updates may adversely affect how your Rehive Application accesses or communicates with the Rehive API. Your continued access or use of the Rehive API following an Update constitutes binding acceptance of it.

G.3.7 Access And Use

Subject to Sections C.2 point 7, D.1 and E.2.3, Rehive may change or discontinue the availability of some or all of the Rehive API. Such changes may include the removal of features or the requirements of fees for previously free features. Rehive may also impose limits on certain features and services or restrict your access to some or all of the Rehive API. Your continued use of the Rehive API following a subsequent release will be deemed your acceptance of modifications.

G.4 Beta Services

From time to time, Rehive may, in its sole discretion, invite you to use Beta Services. Beta Services may be subject to additional terms and conditions, which Rehive will provide to you before you use them. Beta Services, and all conversations and materials relating to them, are Rehive’s Confidential Information under Section D.2. Rehive makes no representations or warranties that Beta Services will function, and they may not work in the same way as a final version. Rehive may discontinue Beta Services at any time, and may change or not release a final or commercial version, in its sole discretion. Rehive will have no liability for any harm or damage arising out of or in connection with Beta Services.

H. Legal Provisions

H.1 Limitation Of Liability

This section excludes and limits Rehive’s liability to you. Please read it carefully. The exclusions and limits in this Section H.1 apply whatever the form of the claim, whether in contract, tort (including negligence), under statute or otherwise. They do not limit your liability to Rehive. They apply even if a limited remedy fails of its essential purpose, and the Fees reflect them.

In these Terms of Service, a “Written Agreement” means your Commercial Agreement or any other written agreement between you and Rehive, whatever it is called, that both of you have signed or accepted, including electronically. These Terms of Service, the Privacy Policy, documentation, proposals, quotes, marketing material, emails and statements by Rehive staff are not a Written Agreement.

H.1.1 Limits

  1. No liability unless agreed otherwise. To the extent the law allows, Rehive has no liability to you for any loss or damage of any kind, whether direct or indirect, arising out of or relating to these Terms of Service or the Services, unless a Written Agreement expressly provides otherwise. Where one does, Rehive is liable only as and to the extent it provides, and this Section H.1 applies except where that Written Agreement expressly replaces it. This Section H.1 does not limit a refund or credit these Terms of Service expressly give you, such as under Sections A.3, F.2, H.3.4 or H.3.5. A Written Agreement made before this version of these Terms of Service took effect that sets a limit on Rehive’s liability is treated as expressly accepting Rehive’s liability to you for direct loss, including a loss of Funds under Section H.1.2 point 4, up to that limit.

  2. Excluded losses. Whenever Rehive is liable to you, whether under a Written Agreement or because point 1 does not apply, Rehive is never liable for any indirect, incidental, special, consequential, punitive or exemplary loss, or for any loss of profits, revenue, business, goodwill or anticipated savings, business interruption, or loss or corruption of data, even if it was foreseeable, unless a Written Agreement expressly accepts liability for that kind of loss.

  3. Fallback limit. If Rehive is liable to you despite point 1, or a Written Agreement accepts liability for Rehive without setting a limit, Rehive’s total liability to you, for all claims together, is limited to the lesser of US$1,000 and the Subscription Fees you paid Rehive for the one month before the event giving rise to the first claim, less any of them refunded to you. If you have paid none, the limit is zero. This is one limit in total, not a limit per End User, transaction or claim. Point 1 does not apply to Rehive’s breach of Section D.2, other than a Security Incident; this point limits that liability.

  4. How Rehive pays. Rehive meets any liability to you by crediting the amount against your future Fees, and may set credits off against any amount you owe Rehive. Any credit still unused when the Services end is paid to you within six months after they end. Credits count towards the limit that applies under the Written Agreement or point 3. This point does not apply to liability under point 5, or where the law requires payment in another form.

  5. What is not limited. Nothing in these Terms of Service excludes or limits Rehive’s liability for its own fraud, willful misconduct or gross negligence, or anything the law does not allow to be excluded or limited.

  6. Third-party services, authorities and instructions. Rehive is not liable for the acts, failures or availability of third-party services, including those Rehive makes available as Passthrough Services. Rehive is also not liable for acting in good faith on an instruction, request or requirement of a court, regulator, law enforcement authority, Third-Party Financial Institution or other provider, or for reporting or disclosing under Section D.1 point 6. Losses of or relating to Funds or transactions are dealt with only in Section H.1.2.

  7. Who these limits protect. These exclusions and limits also protect Rehive’s affiliates, directors, officers, employees and contractors, who may rely on this Section H.1 despite Section H.8.

  8. Time limits for claims. To the extent the law allows, you must start arbitration under Section H.10 (or, where that section allows a court claim, file it) within three months after you became aware, or should reasonably have become aware, of the facts giving rise to the claim. A claim started later is waived. Separately, and whether or not that three-month limit applies or is enforceable, no claim may be started more than 12 months after the event giving rise to it, and a claim started later is waived. This point does not apply to liability under point 5.

H.1.2 Funds And Transactions

  1. Rehive does not hold Funds. Funds are held by a Third-Party Financial Institution or, in self-custody wallets, by End Users. Rehive does not hold the private keys of those wallets. Rehive stores the API keys and other credentials that connect your Program to Third-Party Financial Institutions and other providers, uses them only to operate the Services for you, including carrying out instructions under point 2, and protects them under Section H.9.

  2. Rehive acts on your instructions. The Services carry out activity on your Program automatically: when you, your Staff Accounts or your End Users create a transaction, a new End User account or another event on the Rehive Platform, Rehive’s integration sends the matching instruction to the relevant Third-Party Financial Institution or other provider using the credentials connected to your Program. By enabling an integration, and through the automations you configure, you instruct Rehive to do this. Rehive’s staff have access to the Services, including through the Rehive Review Account, but do not use it to start or authorize transactions on your or your End Users’ accounts, except from the accounts of Rehive Test Users when testing your Program (Section B.2.3) and to resubmit failed instructions (Section C.1.1). That access is limited and logged, and its misuse by Rehive is a breach by Rehive under point 4 and, where intentional, willful misconduct under Section H.1.1 point 5. You are responsible for the credentials you provide, for how credentials Rehive holds for a Passthrough Service are used on your instructions, and for the permissions, limits and automations you set.

  3. No liability for Funds. Except as point 4 sets out, Rehive is not liable for any loss of, or relating to, Funds or transactions, including losses from:

    • unauthorized, failed, delayed, duplicated or misdirected transactions;
    • instructions sent through the Services by you, your Staff Accounts, your End Users, or anyone using your or their credentials or API keys;
    • compromised credentials, API keys, wallet keys or devices;
    • fraud by End Users or third parties, returns, reversals and chargebacks;
    • the acts, failures or insolvency of any Third-Party Financial Institution, wallet provider, stablecoin issuer or blockchain network;
    • the nature of digital assets, including irreversible or mistaken transfers, transfers to a wrong address or network, network fees and congestion, forks, smart-contract failures, and changes in the value or availability of a stablecoin or other digital asset;
    • the restriction, suspension or closure of your Account or a Production Project, the ending of a Passthrough Service, or a withdrawal route or key export not being available (Sections B.4 to B.9 and C.2); and
    • platform controls under Section D.6.

    This does not limit liability under Section H.1.1 point 5, or where a Written Agreement states otherwise.

  4. Rehive’s own errors. Rehive is liable for a loss of Funds directly caused by its breach of these Terms of Service or an error in its software only where a Written Agreement expressly accepts that liability. Unless it says otherwise, that liability is within the limits in Section H.1.1, is paid as set out there, and includes an amount you must pay a Third-Party Financial Institution for that loss under your agreement with it. This liability is reduced to the extent you, your Staff Accounts, your End Users or a third party contributed to the loss. It does not cover losses caused by a Third-Party Financial Institution or other third party, by fraud of End Users or third parties, by instructions given by you, your Staff Accounts or your End Users, by credentials compromised outside the Services, or by your own integrations, custom code, modified Rehive Applications or self-hosted deployments. It also does not cover a loss that the settings available to you in the Services, such as which transaction flows a user may use and the limits that apply to them, would have prevented had you used them. A loss of Funds resulting from a Security Incident is covered only as Section H.9 point 5 provides. Section D.6.7 applies to platform controls.

  5. Your provider agreements. Your agreements with Third-Party Financial Institutions govern your liability to them. If such an agreement makes you liable for losses caused by your service providers, including Rehive, that liability stays with you, and you will not seek to recover it from Rehive except for the amounts point 4 covers, within the limits in Section H.1.1. Where Rehive makes a provider’s service available as a Passthrough Service, Section H.2 applies to any liability Rehive has to that provider for your Program.

  6. Using the Services as a ledger only. Where you use the Services to record balances or transactions for a Program whose Funds Rehive does not connect to a Third-Party Financial Institution, for example because you hold or move the Funds yourself or through your own integrations, the records in the Services are records you keep on your own instructions. You are responsible for what you and your End Users do in reliance on them, for reconciling them with the Funds, and for any licence or approval your model needs. Rehive is not liable for any loss of or relating to those Funds, point 4 does not apply, and your remedy for a defect in the Services is Section H.3.

H.2 Indemnification

  1. Your breach. You will indemnify and hold harmless Rehive and (as applicable) its parent, subsidiaries, affiliates, officers, directors, agents, employees, contractors and providers from all third-party claims and demands, and the resulting losses, damages, fines, penalties, costs and expenses, including reasonable attorneys’ fees, arising out of your breach of these Terms of Service or the documents it incorporates by reference (including without limitation the Privacy Policy and the Software License Agreement), or your violation of any applicable law or the rights of a third party in your use of the Services.

  2. Your Program, End Users and Funds. You also indemnify them against any third-party claim, including by an End User, a Third-Party Financial Institution or other provider, or a regulator, arising out of or relating to your Program, your End Users, or Funds or transactions in your Program, including where Rehive’s negligence or an error in Rehive’s software contributed to it. This includes any penalty, fine or loss a provider imposes on or claims from Rehive because of your Program or your use of a Passthrough Service, and Rehive’s reasonable costs of responding to a subpoena, investigation or regulatory request about your Program.

  3. Exceptions. This Section H.2 does not apply to the extent the claim arises from Rehive’s fraud, willful misconduct or gross negligence, or from a loss for which Rehive is liable to you under Section H.1.2 point 4, up to the limit that applies to that liability.

  4. Procedure. Rehive will tell you promptly of a claim it seeks indemnity for and may control its defense and settlement at your cost, with your reasonable cooperation. You may not settle a claim on Rehive’s behalf, or in a way that binds or admits fault for Rehive, without Rehive’s written consent.

H.3 Warranties And Disclaimers

H.3.1 Limited Warranty

Rehive warrants that the Services will perform substantially as described in Rehive’s then-current documentation, under normal use, during your Rehive Subscription. This warranty does not apply to Beta Services, Passthrough Services or Open Source Components, or to issues caused by your own integrations, custom code, modified Rehive Applications or self-hosted deployments, or by use contrary to these Terms of Service or the documentation.

H.3.2 Disclaimer Of Warranties

  1. Except as expressly provided in these Terms of Service, the Services are provided “as is” and “as available” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement.

  2. Rehive does not warrant that the Services will be uninterrupted, error-free or completely secure, or make any warranty as to the results obtained from the Services or the accuracy, reliability or content of any information provided through them.

  3. Rehive does not warrant that the Services, the Base Configuration, any template or any platform control meets a legal or regulatory requirement that applies to you, or will detect or prevent fraud. Rehive gives no warranty about any blockchain network, stablecoin or other digital asset.

H.3.3 No Warranty For Third-Party Services

Rehive gives no warranty for third-party services or products that you access or use in connection with the Services, including Passthrough Services.

H.3.4 Exclusive Remedy

Provided you tell Rehive in writing of a non-conformity within 30 days of discovering it, your exclusive remedy for breach of the limited warranty is the correction of the non-conforming Services or, if correction is not feasible, termination of the affected Services and a refund of the pre-paid but unused Fees for them. Section H.1 applies. A refund under this section is paid as a refund, not as a credit under Section H.1.1 point 4.

H.3.5 Infringement Claims

If you receive a claim that the Services infringe a third party’s intellectual property rights, tell Rehive promptly and do not settle it in a way that concerns the Services without Rehive’s written consent. Rehive may then modify or replace the affected part, obtain the right for you to keep using it, or end the affected Services and refund the pre-paid but unused Fees for them. That is your only remedy for such a claim, Section H.1 applies, and it does not cover claims arising from your own content, integrations or custom code, Open Source Components or third-party services. Where you have signed a Software License Agreement, its terms on infringement claims apply instead to the Software licensed under it, subject to Section H.1.

H.4 Relationship Of The Parties

The relationship between the parties is that of independent contractors. Nothing in these Terms of Service creates any agency, partnership, joint venture or other form of joint enterprise, employment or fiduciary relationship between the parties, and neither party has authority to contract for or bind the other in any manner. Where these Terms of Service let Rehive act or communicate on your behalf, such as under Sections B.2.3, B.8 and D.6.6, Rehive does so only within those limits and is not your agent for any other purpose.

H.5 Public Announcements

Neither party may issue or release any announcement, statement, press release or other publicity or marketing material relating to these Terms of Service or, unless these Terms of Service expressly permit it, otherwise use the other party’s trademarks, service marks, trade names, logos, domain names or other indicia of source, association or sponsorship, in each case without the other party’s prior written consent, which may not be unreasonably delayed or withheld. However, Rehive may, without your consent, include your name and other indicia in its lists of current or former customers in promotional and marketing materials. You must not state or imply that Rehive endorses, approves or has reviewed your Program.

H.6 Notices

  1. Legal notices, such as a notice of a claim, a termination for breach or a dispute, must be in writing. A cancellation under Section F.1 or a request under Section B.6 is not a legal notice and goes to Rehive Support. Legal notices to Rehive go to the email address Rehive gives you for legal notices, for example in your Commercial Agreement or your shared Slack channel, or by post to the Rehive Contracting Party at the address in Section A.4. Legal notices to you go to your Account Representative’s email address in the Admin Dashboard. An email notice takes effect two Business Days after it is sent, and a posted notice when it is received.

  2. Operational notices, including under Sections B, D.6, E and H.9, may be given through any Official Channel and take effect when sent. Operational notices to Rehive may be sent to Rehive Support.

H.7 Economic Sanctions

  1. Your warranty. You represent and warrant that neither you, nor any person who owns or controls you, nor any Authorized User is named on a Sanctions List, owned or controlled by a person named on one, or located, organized or ordinarily resident in a country or region subject to comprehensive sanctions under the laws behind the Sanctions Lists.

  2. Your use. You must not use the Website or the Services, or let any End User use them, for the benefit of such a person, in such a country or region, or otherwise contrary to the sanctions laws of the United States, the United Kingdom, the European Union or the United Nations that apply to you, to Rehive or to your Third-Party Financial Institutions. You must screen your End Users against the Sanctions Lists, yourself or through a provider.

  3. Rehive’s rights. Rehive may restrict, suspend or terminate access to the Services and the Accounts of anyone it suspects of breaching this section, in its sole discretion, and may apply Mandatory Controls under Section D.6.10 to enforce it.

H.8 No Third Party Beneficiaries

These Terms of Service are for the sole benefit of you and Rehive and your respective successors and permitted assigns. Nothing in them, express or implied, confers on any other person any legal or equitable right, benefit or remedy, except as Section H.1.1 point 7 and Section H.2 provide for the persons they name.

H.9 Privacy And Data Protection

  1. Privacy Policy. Rehive collects, uses and discloses personal information, yours and your End Users’, as set out in its Privacy Policy.

  2. Access and use. Rehive’s employees, contractors and vendors may access and use your data and End User Data, without asking you each time, to:

    • provide, support and maintain the Services, including answering your support requests and working with your providers under Section D.6.6;
    • measure your usage and calculate and check your Fees;
    • investigate and fix bugs, incidents and security issues, and test new releases;
    • detect and prevent fraud and other risks, including by building and training risk models, by sharing information about specific transactions or users with Third-Party Financial Institutions and fraud-prevention services, and by exercising Rehive’s rights under Section D.6;
    • improve the Services and develop new features and services, including features that use artificial intelligence, and analyze usage, costs and pricing;
    • send your Authorized Users service and product updates and offers;
    • comply with the law, report and cooperate under Section D.1 point 6, enforce these Terms of Service, and establish, exercise or defend legal claims; and
    • share it under confidentiality obligations in an audit, financing or due diligence, and transfer it in a merger, acquisition or sale of all or part of Rehive’s business.

    For these purposes Rehive’s staff may review individual End User records, activity and verification data. That review is not a compliance review of your End Users, and Rehive makes no decisions about them for you (Section D.6). Rehive uses de-identified or aggregated data for analysis, model training and testing where practical. Rehive’s vendors, including hosting and artificial intelligence providers, process data only for Rehive’s purposes and under confidentiality and security obligations. Rehive does not sell your data or End User Data, does not market to your End Users, does not share your identifiable data with its other clients, and does not provide support to your End Users.

  3. Vendors and the CCPA. Rehive uses third-party vendors and hosting partners to provide the necessary hardware, software, networking, storage, and related technology required to run the Services. Where the California Consumer Privacy Act (“CCPA”) applies to End User Data that Rehive processes on your behalf to operate your Program, Rehive is your “service provider”. It processes that data only for the purposes in point 2, Sections D.1 and D.6 and the Privacy Policy, does not sell or share it as the CCPA defines those terms, and will tell you if it can no longer meet its obligations as a service provider. For the purposes the Privacy Policy lists as Rehive’s own, Rehive uses that data only as the CCPA allows a service provider to, or in de-identified or aggregated form. You must meet your own obligations under the CCPA and must not use the Services in a way that breaches it.

  4. Security measures. Rehive maintains reasonable administrative, technical and physical security measures, appropriate to the nature of the data, to protect your data and End User Data in the Services, including credentials and API keys for Third-Party Financial Institutions and other providers. These include backups, encryption of data in transit and at rest, and access limited to authorized people and services.

  5. Security Incidents. Rehive tells you of a Security Incident without undue delay, and in any case no later than the time set in a Written Agreement or, if none sets one, within two Business Days after Rehive becomes aware of it. Rehive gives you the information it reasonably can, takes reasonable steps to contain the incident, and cooperates so that you can meet your notice obligations to Third-Party Financial Institutions and regulators. You are responsible for securing your Staff Accounts (including two-factor authentication), any credentials you hold outside the Services, and the permissions, limits and approvals you configure. Rehive is not responsible for a Security Incident to the extent it arises from these. Rehive is not liable for a Security Incident or any loss resulting from it, except as Section H.1.1 point 5 provides or where a Written Agreement expressly accepts that liability, and then within Section H.1.

H.10 Governing Law And Dispute Resolution

  1. These Terms of Service (and any other terms or agreements referenced herein, including but not limited to the Privacy Policy and Software License Agreement), and any and all claims, disputes or other legal proceedings by or between you and Rehive, including but not limited to any claims or disputes that are in any way related to or arising out of these Terms of Service or your use of or access to the Website or the Services, shall be governed by and construed per U.S. federal law and the laws of the state of Delaware, without regard to any principles of conflicts of law.

  2. Except as otherwise required by a non-waivable provision of applicable law, any dispute, claim, or controversy arising out of or relating to these Terms of Service or the breach, termination, enforcement, interpretation, or validity thereof, including the determination of the scope or applicability of this agreement to arbitrate, shall be determined by arbitration in San Francisco, California, United States before one arbitrator. Claims may be brought only individually, not as a class, consolidated or representative proceeding. The arbitration shall be administered by JAMS according to its Comprehensive Arbitration Rules and Procedures. Judgment on the award may be entered in any court having jurisdiction. This clause shall not preclude parties from seeking provisional remedies in aid of arbitration from a court of appropriate jurisdiction in San Francisco County, California, or if such proceeding cannot be lawfully held in such location, as near thereto as applicable law permits.

  3. The arbitration is confidential and conducted in English. Either party may seek an injunction or other equitable relief in any court with jurisdiction for an actual or threatened breach of Confidentiality (Section D.2), the Acceptable Use Policy (Section C.4) or its intellectual property rights, and Rehive may bring a claim for unpaid Fees in any court with jurisdiction.

  4. To the extent the law allows, each party waives any right to a jury trial in any court proceeding arising out of or relating to these Terms of Service.

H.11 Force Majeure

Neither party is liable for a failure or delay in performing its obligations under these Terms of Service, other than an obligation to pay, where it results from a cause beyond that party’s reasonable control. Such causes include mechanical, electronic or communications failure or degradation; the failure of a Third-Party Financial Institution, blockchain network or other third-party service that the party does not control; cyberattacks; acts of God, flood, fire, earthquake or explosion; war, terrorism, invasion, riot or other civil unrest; embargoes or blockades; national or regional emergency; strikes, labor stoppages or slowdowns or other industrial disturbances; passage of law or any action taken by a governmental or public authority; and national or regional shortage of adequate power, telecommunications or transportation. The affected party will tell the other and use reasonable efforts to resume performance.

H.12 General

  1. Waiver. The failure of Rehive to exercise or enforce any right or provision of the Terms of Service shall not constitute a waiver of such right or provision.

  2. Severability. If any provision of the Terms of Service, including all terms and conditions and other documents it incorporates by reference (including without limitation the Privacy Policy and the Software License Agreement), is held by a court of competent jurisdiction to be contrary to law, such provision shall be changed and interpreted so as to best accomplish the objectives of the original provision to the fullest extent allowed by law, and the remaining provision of the Terms of Service shall remain in full force and effect.

  3. Remedies. The remedies available to Rehive in these Terms of Service are cumulative and in addition to any others available to Rehive. Rehive may seek all remedies available to it at law and in equity for any violation of these Terms of Service.

  4. Assignment. These Terms of Service, and any rights and licenses granted under them, may not be transferred or assigned by you without Rehive’s prior written consent, which Rehive may give or withhold in its sole discretion, but may be assigned by Rehive without restriction, including to an affiliate or a successor to its business. Any attempted transfer or assignment by you in breach of this point is void. These Terms of Service bind and benefit the parties and their respective successors and permitted assigns.