Effective October 23, 2026 · Last updated November 3, 2026
Realizse Platform Terms and Conditions
Welcome, and thank you for your interest in the Realizse Platform ("Realizse," "we," or "us") and our websites at www.realizse.com and www.179Dregistry.com ("Public Websites"), along with any of our other related websites, platform ("Platform"), API, and other services provided by us (collectively, the "Service"). These Terms and Conditions are a legally binding contract between you and Realizse regarding your use of the Service.
PLEASE READ THE FOLLOWING TERMS CAREFULLY:
BY CLICKING "I ACCEPT," OR BY DOWNLOADING, INSTALLING, OR OTHERWISE ACCESSING OR USING THE SERVICE, YOU AGREE THAT YOU HAVE READ AND UNDERSTOOD, AND, AS A CONDITION TO YOUR USE OF THE SERVICE, YOU AGREE TO BE BOUND BY, THE FOLLOWING TERMS AND CONDITIONS, INCLUDING THE REALIZSE PRIVACY POLICY AVAILABLE AT https://app.realizse.com/privacy ("PRIVACY POLICY") (TOGETHER, THESE "TERMS"); PROVIDED, THAT TO THE EXTENT THESE TERMS DIRECTLY CONFLICT WITH ANY SEPARATE AGREEMENT THAT YOU HAVE PREVIOUSLY MADE WITH REALIZSE RELATED TO THE SERVICE AND THE PLATFORM OUTSIDE OF THE STANDARD VERSION OF THESE TERMS (INCLUDING VIA AN ADDENDUM TO THESE TERMS, A CLOUD SERVICES AGREEMENT, OR A PLATFORM SERVICES AGREEMENT), SUCH SEPARATE AGREEMENT WILL CONTINUE TO GOVERN AND CONTROL ANY SUCH CONFLICT OTHER THAN AS NECESSARY TO COMPLY WITH LAW. IF YOU ARE NOT ELIGIBLE, OR DO NOT AGREE TO THE TERMS, THEN YOU DO NOT HAVE OUR PERMISSION TO USE THE SERVICE. YOUR USE OF THE SERVICE, AND REALIZSE'S PROVISION OF THE SERVICE TO YOU, CONSTITUTES AN AGREEMENT BY REALIZSE AND BY YOU TO BE BOUND BY THESE TERMS.
ARBITRATION NOTICE. Except for certain kinds of disputes described in Section 21 (Dispute Resolution and Arbitration), you agree that disputes arising under these Terms will be resolved by binding, individual arbitration, and BY ACCEPTING THESE TERMS, YOU AND REALIZSE ARE EACH WAIVING THE RIGHT TO A TRIAL BY JURY OR TO PARTICIPATE IN ANY CLASS ACTION OR REPRESENTATIVE PROCEEDING. Where Section 26.11 (Public Entities) applies, this Arbitration Notice and Section 21 do not apply.
1. Definitions
In these Terms, the following terms have the meanings set out below:
"Account" means the user account created through the Platform's identity provider that enables an individual to access the Service.
"Admin" means a User assigned the administrator role within an Organization, with permissions to manage users, resources, and organization settings.
"Aggregated Data" means User Content that has been aggregated with other data such that the resulting data no longer reasonably identifies the Client, any specific Project, or any individual.
"Allocator" means an owner, or its delegate, that allocates Tax Deductions in a Transaction.
"API" means the Realizse application programming interface, accessible at the designated API endpoint, through which Clients may interact with the Service programmatically.
"Asset Passport" means a persistent digital identity assigned to a real-world asset (such as a building or land parcel), backed by a Decentralized Identifier (DID) and containing Verifiable Credentials that describe the asset's attributes, history, and compliance status.
"Client" means the organization that enters into a subscription agreement with Realizse and is registered as an Organization on the Platform.
"Confidential Information" has the meaning set forth in Section 20.1.
"Content-Addressed Storage" means the file storage system in which each file is identified by its SHA-256 cryptographic hash, ensuring that file content cannot be altered without detection.
"Customer" has the same meaning as "Client" and the two terms are used interchangeably throughout these Terms.
"Customer-Uploaded Content" means any data, documents, files, records, certifications, engineering studies, energy models, tax forms, compliance records, or other materials submitted, uploaded, transmitted, or otherwise made available to the Platform by or on behalf of the Customer, including materials uploaded by Customer's employees, contractors, agents, authorized Users, certifiers, auditors, designers, or other affiliated parties acting under Customer's direction or authority. Customer-Uploaded Content is a subset of Client Data.
"Covered Period" means a two (2)-year period beginning and running from the date on which you (or any person for which you are serving as an Intermediary on the Platform) (i) meet an Introduced Party (in the case of Section 8.2) or (ii) discover an Introduced Transaction (in the case of Section 8.3). In any case where both (i) and (ii) are applicable, the Covered Period shall begin and run from the later of the two.
"Decentralized Identifier (DID)" means a globally unique, persistent identifier created in accordance with the W3C DID standard, assigned to Assets, Products, and Projects on the Platform.
"Digital Passport" means a Realizse Passport. The terms are used interchangeably throughout these Terms.
"Document" means a legal agreement generated from a Platform template, populated with Project-specific data, and sent for electronic signature through the e-signature provider.
"Editor" means a User assigned the editor role within an Organization, with permissions to create and modify resources but not manage users.
"Effective Date" means the date the Client first accepts these Terms or signs its subscription agreement, whichever is earlier.
"File" means any binary content (PDFs, spreadsheets, images, signed agreements) uploaded to or generated by the Platform and stored in Content-Addressed Storage.
"Intermediary" means any person or entity that uses the Service on behalf of, as agent for, or as representative of an Allocator, a Qualified Off-taker, or any other party to a Transaction, including brokers, advisors, consultants, accountants, and attorneys.
"Introduced Party" means any third party that you (or any person for which you are serving as an Intermediary on the Platform) first meet on the Platform or through the Service, including any introduction by the Platform or Realizse. Introduced Party expressly excludes any third party that you invite to the Service or with whom you (or any person for which you are serving as an Intermediary on the Platform) had a bona fide pre-existing commercial relationship whereby you (or such other person) and the third party have entered into transactions for the allocation of tax deductions or other capital markets, development, or other significant commercial transactions related to Projects, or that you (or such other person) and such third party have engaged in communications or activities that are reasonably likely to lead to entering into one or more of such transactions. Realizse may request reasonable documentation and other backup information to substantiate any such pre-existing commercial relationship.
"Introduced Transaction" means (i) in the case of a Qualified Off-taker (or any person when acting as Intermediary on behalf of a Qualified Off-taker), any Transaction that such Qualified Off-taker is first made aware of through use of the Platform or through an introduction by Realizse, or (ii) in the case of an Allocator (or any person when acting as agent on behalf of an Allocator), any Transaction for which a Qualified Off-taker has first been made aware of through use of the Platform or through introduction by Realizse, but only with respect to such Qualified Off-taker. A Qualified Off-taker will not be deemed to be previously aware of a Transaction if such awareness is based solely on publicly available information or information that is widely available in the industry.
"Materials" means the visual interfaces, graphics, design, compilation, information, data, computer code (including source code or object code), products, software, services, and all other elements of the Service provided by Realizse.
"Non-Platform Transaction" means any direct or indirect investment, purchase and sale, or other transaction to monetize Tax Deductions (including through an allocation of Tax Deductions, or pursuant to a tax equity partnership, inverted lease, or sale leaseback structure) by you or any of your affiliates, subsidiaries, or clients (if you are an Intermediary) that does not take place on the Platform.
"Organization" means a registered tenant on the Platform representing a business entity, which serves as the primary unit of data isolation.
"Participating Organization" means an Organization registered on the Platform that has no subscription agreement with Realizse and whose Users access the Service by invitation of a Client, such as a counterparty, designer, certifier, auditor, or consultant. Participating Organization is a status on the Platform; Contributing Organization (as defined in Section 11.3(a)(ii)) is a role on a Realizse Passport, which a Client can also hold.
"Platform" means the Realizse web application, including all associated services, features, and functionality accessible through the web interface.
"Product Passport" means a Digital Product Passport containing manufacturer specifications, compliance attestations, and supporting documentation for equipment or components.
"Project" means a time-bounded engagement on the Platform that orchestrates multi-party workflows, data collection, document generation, and credential issuance in connection with an eligible facility in the United States.
"Project Passport" means a persistent digital identity assigned to a real-world project (such as an in-progress energy project or process), backed by a Decentralized Identifier (DID) and containing Verifiable Credentials that describe the project's attributes, history, and compliance status.
"Qualified Off-taker" means a designer or other person eligible to receive an allocation of Tax Deductions in a Transaction.
"Realizse Passport" means any individual or combination if plural of Asset Passport, Project Passport, and/or Product Passport associated with a Client on the Platform.
"Service" means, collectively, the Platform and the API.
"Service Logs" means the CDN access logs, API access logs, and application execution logs generated through the operation of the Service. Personal information in Service Logs is protected in the same way as other personal information and is used only to operate, secure, and support the Service.
"Tax Deductions" means energy efficient commercial tax deductions pursuant to Section 179D of the United States Internal Revenue Code (the "Code").
"Term" means the period from the Effective Date until the Client's subscription agreement, including any renewals, ends or these Terms are terminated, whichever occurs first. The ninety (90)-day transition period under Section 25.11(c) is not part of the Term.
"Transaction" or "Allocation" means any certification and allocation of Tax Deductions facilitated on or through the Platform.
"Usage Data" means information generated from the use of the Service that does not identify any individual, such as data and learnings about your use of the Service.
"User" means an individual person who accesses the Service through an Account. Each User belongs to exactly one Organization.
"User Content" means any content submitted, uploaded, published, broadcast, or otherwise transmitted ("Posted") to the Service by a User, including messages, photos, video or audio, images, folders, documents, data, text, and any other works of authorship or other works.
"Verifiable Credential (VC)" means a cryptographically signed, tamper-evident digital attestation issued through the Platform in accordance with the W3C Verifiable Credentials Data Model standard.
"Viewer" means a User assigned the viewer role within an Organization, with read-only access to organization resources.
2. Service Description
2.1 Overview
Realizse provides a cloud-hosted Software-as-a-Service platform and API that enables organizations to manage digital passports, verifiable credentials, and document workflows for physical assets and energy infrastructure projects, and that facilitates the registration, allocation, and organization of Tax Deductions originating from eligible Projects. Realizse is not a party to Transactions between any asset owner, developer, designer, and/or other third parties transacted on the Platform, though Realizse may be a third-party beneficiary of such Transactions for purposes of paying certain fees or as otherwise stated in the definitive transaction agreements.
2.2 Service Components
The Service includes:
(a) The Platform — a web-based application for managing organizations, assets, products, projects, documents, and verifiable credentials, and for facilitating Transactions.
(b) The API — a REST application programming interface for programmatic access to Platform functionality, subject to the API-specific terms set out in Section 27.
2.3 Current Scope
The Service encompasses both the Platform and the API as a combined offering. API-specific terms and conditions are set forth in Section 27. In the event of a conflict between the general provisions of these Terms and the API-specific terms in Section 27, the API-specific terms shall control with respect to the Client's use of the API.
2.4 Allocator Use
If you are an Allocator, then you can use our Platform to, among other uses: create and manage your profile and account; upload and structure Project-related information relevant to the potential allocation of Tax Deductions; distribute Project-related information to potential Qualified Off-takers; facilitate the negotiation and execution of allocation agreements and definitive transaction documents; and streamline the sharing or receiving of Project and tax information before or after the completion of a Transaction, including for purposes of due diligence and tax filings.
2.5 Qualified Off-taker Use
If you are a Qualified Off-taker, then you can use our Platform to, among other uses: create and manage your profile and account; source potential Projects that could offer Tax Deductions for allocation; facilitate the negotiation and execution of term sheets, definitive transaction documents, and other related transaction documents; and streamline the sharing or receiving of Project and tax information before or after the completion of a Transaction, including for purposes of due diligence and tax filings.
2.6 Asynchronous Processing
Certain operations on the Platform — including document signing, verifiable credential issuance, and file archival — are processed asynchronously. These operations may complete after the initial request is acknowledged. The Platform uses message queuing with retry mechanisms to ensure processing reliability. Realizse does not guarantee specific completion times for asynchronous operations.
3. Eligibility
You must be at least 18 years old to use the Service. By agreeing to these Terms, you represent and warrant to us that: (a) you are at least 18 years old; (b) you have not previously been suspended or removed from the Service; and (c) your registration and your use of the Service is in compliance with any and all applicable laws and regulations. If you are an entity, organization, or company, the individual accepting these Terms on your behalf represents and warrants that they have authority to bind you to these Terms and you agree to be bound by these Terms.
4. Accounts and Registration
4.1 Account Creation
To access the Platform, you must register for an Account. When you register for an Account, you may be required to provide us with information about yourself, such as your name, company email address, and information about the Allocator, Qualified Off-taker, or other party, as applicable. You agree that the information you provide to us is accurate, complete, and not misleading, and that you will keep it accurate and up to date at all times.
4.2 Authentication
Access to non-public Platform features and user API endpoints requires authentication through Realizse's identity provider. Users authenticate using email-based passwordless authentication and receive a JSON Web Token (JWT) that must accompany every user API request. Realizse does not store user passwords.
4.3 Organization Membership
Each User belongs to exactly one Organization. Data access is scoped to the User's Organization, except for cross-Organization access authorized under these Terms and enforced by the Platform's access controls. Participating Organizations can access only the data of their own Organization and the project records, files and credentials of the Client projects to which they have been invited, including other participants' contributions, plus any further access the Client grants through the Platform's access controls.
4.4 Roles and Permissions
Users are assigned one of three roles by their Organization's administrator or, during Organization creation, by Realizse:
- Admin — Access to organization resources subject to project-specific permissions, including user management (invite, edit roles, disable accounts).
- Editor — Can create and modify resources (assets, products, projects, files) but cannot manage users.
- Viewer — Read-only access to organization resources.
Permissions are enforced at the API level on every user API request.
Each Organization must designate at least one (1) User with the Admin role at all times during the term of the subscription. If an Organization has no active Admin (due to account disablement, departure, or other circumstances), Realizse may, at its discretion, restrict the Organization's ability to create or modify resources until a new Admin is designated. Realizse may contact the Organization's primary billing contact or other authorized representative to facilitate the designation of a replacement Admin.
4.5 Account Responsibility
You are solely responsible for maintaining the confidentiality of your Account, and you accept responsibility for all activities that occur under your Account. The Client is responsible for: (a) ensuring that only authorized individuals receive Accounts within the Client's Organization; (b) maintaining the accuracy of User information (names, email addresses, roles); (c) promptly disabling the Accounts of individuals who are no longer authorized to access the Service (e.g., former employees); and (d) all activity that occurs under Accounts within the Client's Organization. If you believe that your Account is no longer secure, please immediately notify us at support@realizse.com.
4.6 Fees
You are not required to pay any fees to Realizse solely as a result of your agreement to these Terms. However, Realizse may charge fees in connection with Allocations and subscriptions, as set out in an Order Form or other signed agreement, and you may be required to agree to separate fee documentation (including an Order Form) in order to continue to use the Platform. We will not charge you any out-of-pocket fees that are not explicitly agreed to by you. However, we reserve the right to discontinue the Service to any user, including by removing a Transaction from the Platform, if such fee arrangements are not entered into at the appropriate time. The signed-agreement requirements in Sections 4.6 and 25.1 do not apply to amounts expressly payable under Sections 8.2 and 8.3.
4.7 Participating Organizations
In addition to the provisions of these Terms that apply to all users of the Service, the following apply to a Participating Organization: Sections 4.5, 15.4(d), 15.6(f), 16.7, 20, 22-A (as to content the Participating Organization uploads), 23, 24.2(a)–(c) and (e)–(f), and 26.10. The following do not apply to a Participating Organization: the ownership rights in Section 11.1; Sections 13.4(b), 14.6, 24.2(d), and 25.1 through 25.10; and the DPA.
5. Licenses
5.1 Limited License
Subject to your complete and ongoing compliance with these Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Service on behalf of the Allocator, Qualified Off-taker, or other party that you work for or otherwise represent.
5.2 License Restrictions
Except and solely to the extent such a restriction is impermissible under applicable law, you may not: (a) reproduce, duplicate, distribute, publicly display, or create derivative works of the Service or any components thereof (including, without limitation, form transaction documents developed by or on behalf of Realizse such as the Tax Deduction Allocation Agreement); (b) make modifications to the Service; (c) interfere with or circumvent any feature of the Service, including any security or access control mechanism; or (d) reverse engineer, decompile, or attempt to derive the source code of the Service. If you are prohibited under applicable law from using the Service, then you may not use it.
5.3 Feedback
If you choose to provide input and suggestions regarding existing functionalities, or problems with or proposed modifications or improvements to the Service ("Feedback"), then you hereby grant us an unrestricted, perpetual, irrevocable, non-exclusive, fully paid, royalty-free right and license to exploit the Feedback in any manner and for any purpose, including to improve the Service and create other products and services, without any requirement of attribution. For the avoidance of doubt, "Feedback" does not include Client Data or User Content; the rights granted to Realizse with respect to Client Data and User Content are solely as set forth in Section 11.
6. Ownership; Proprietary Rights
6.1 Realizse IP
The Service is owned and operated by Realizse, Inc. The Materials are protected by intellectual property and other laws. All Materials included in the Service are the property of Realizse or its third-party licensors. There are no implied licenses in these Terms, and Realizse reserves all rights to the Materials not granted expressly in these Terms. Nothing in these Terms transfers any Realizse intellectual property to the Client.
6.2 Client Data IP
As set out in Section 11, the Client retains all right, title, and interest in and to Client Data.
7. Acceptable Use
7.1 Permitted Use
The Client may use the Service solely for its intended business purposes related to managing digital passports, verifiable credentials, document workflows, energy infrastructure compliance projects, and the registration, allocation, and organization of Tax Deductions.
7.2 Prohibited Conduct
BY USING THE SERVICE, YOU AGREE NOT TO, AND SHALL ENSURE THAT YOUR USERS DO NOT:
(a) Use the Service for any illegal purpose or in violation of any local, state, national, or international law.
(b) Harass, threaten, demean, embarrass, bully, or otherwise harm any other user of the Service.
(c) Violate, encourage others to violate, or provide instructions on how to violate, any right of a third party, including by infringing or misappropriating any third-party intellectual property right, or by violating any third-party contract, including any contract that prohibits you from engaging in a Transaction on the Platform.
(d) Attempt to bypass, circumvent, or disable any authentication, authorization, or security controls implemented by the Service.
(e) Exceed or attempt to circumvent the rate limits imposed by the API (currently 50 requests per second sustained, 100 concurrent burst).
(f) Submit malformed, deceptive, or malicious payloads intended to exploit vulnerabilities or evade input validation.
(g) Attempt to access data belonging to other Organizations or Users beyond the scope of the Client's authorized access.
(h) Use automated tools to scrape, crawl, or extract data from the Service beyond the scope of the API, including through the use of any engine, software, tool, agent, device, or mechanism (including spiders, robots, crawlers, and data mining tools) other than the software or search agents provided by Realizse and the Platform.
(i) Interfere with the operation of the Service or any user's enjoyment of the Service, including by uploading or otherwise disseminating any virus, adware, spyware, worm, or other malicious code.
(j) Perform any fraudulent activity including impersonating any person or entity, claiming a false affiliation or identity, accessing any other Account without permission, or falsifying your age or date of birth.
(k) Sell or otherwise transfer the access granted under these Terms or any Materials, or any right or ability to view, access, or use any Materials.
(l) When engaging in bidding activities on the Platform, submit bids, respond to bids, or otherwise communicate in respect of a Transaction in a manner that does not reflect your good faith intention to enter into a Transaction based on such communicated terms and conditions.
(m) Submit bids or respond to bids for informational purposes only or in any other manner if you do not have a good faith intent to enter into a Transaction consistent with the terms of any bid or response to any bid.
(n) Take any effort to manipulate terms, conditions, pricing, or other elements of the Platform, whether in respect of a particular Transaction or multiple Transactions.
(o) Attempt to do any of the acts described in this Section 7.2 or assist or permit any person in engaging in any of the acts described in this Section 7.2.
7.3 Enforcement
Realizse enforces acceptable use through technical controls including authentication scope checks, role-based access controls, web application firewall rules, rate limiting, and input validation. Violation of these Terms may result in suspension or termination of access.
8. Referrals; Non-Circumvention
8.1 Definitions
Capitalized terms used in this Section 8 (Covered Period, Introduced Party, Introduced Transaction, Non-Platform Transaction) have the meanings set forth in Section 1.
8.2 Introduced Party Referral Fee
During the Covered Period, if you (or any person for which you are serving as an Intermediary on the Platform) participate in a Non-Platform Transaction with an Introduced Party, you will be required to pay to Realizse 1.00% of the notional value of tax deductions being allocated (or equivalent amount as part of any tax equity partnership, inverted lease, or sale leaseback transaction) in such Non-Platform Transaction. The amounts payable to Realizse under this Section 8.2 with respect to a particular Non-Platform Transaction shall constitute the total amount payable to Realizse from all parties collectively, including Allocator and Qualified Off-taker, for any amounts due under this Section 8.2 with respect to such Non-Platform Transaction. In addition, if any Non-Platform Transaction under this Section 8.2 would also be covered by Section 8.3, it shall be addressed exclusively by Section 8.3.
8.3 Transaction Non-Circumvention
During the Covered Period, you (or any person for which you are serving as an Intermediary on the Platform) shall not participate in any Non-Platform Transaction that is the same as, or substantially similar to, some or all of any Introduced Transaction (including where there is overlap on some or all of the tax deductions or Projects included in such Introduced Transaction and such Non-Platform Transaction). If you (or such person) complete any such Non-Platform Transaction, you will be required to pay to Realizse the greater of (x) 1.00% of the notional value of tax deductions allocated (or equivalent amount as part of any tax equity partnership, inverted lease, or sale leaseback transaction) and (y) the fees that Realizse would have received in connection with such Transaction(s) if completed on the Platform pursuant to any fee documentation agreed to between Realizse and any transacting party, including Order Forms. The amounts payable to Realizse under this Section 8.3 with respect to a particular transaction shall constitute Realizse's maximum recovery from all parties collectively, including Allocator and Qualified Off-taker, for a breach of Section 8.3 with respect to such transaction.
9. Your Warranties
You represent, warrant, and covenant to Realizse that:
9.1. You are acting on your own behalf or on behalf of the organization or other party you represent (including as an Intermediary), and you have authority to bind that organization or party. The party on whose behalf you act, as the party to any Transaction, is legally formed and domiciled in the United States and is a "United States person" within the meaning of Code section 7701(a)(30). These requirements apply to that party, not to each individual User.
9.2. As applicable to you under applicable laws, you have established anti-money laundering policies and procedures as required by the Bank Secrecy Act, as amended by the USA PATRIOT Act (the "Patriot Act") and are in full compliance with the Financial Crimes Enforcement Network of the U.S. Department of Treasury regulations or, as applicable, the regulations of your federal functional regulator.
9.3. As applicable to you under applicable laws, you are in compliance with the Patriot Act and do not provide services to any U.S. Treasury Department's Office of Foreign Assets Control ("OFAC") named targets or entities, countries sanctioned under Section 311 of the Patriot Act, or foreign shell banks.
9.4. You are not and shall not be prohibited from transacting business of the type contemplated by these Terms, pursuant to any federal regulations and executive orders and lists administered or published by OFAC.
9.5. The information you provide to Realizse in connection with your use of the Platform and/or in connection with any Project and/or proposed Transaction is accurate and complete; to the extent you subsequently learn or discover that any information previously submitted is inaccurate or incomplete, you will promptly inform us of the same and update such information to make it accurate and complete.
9.6. While you are using the Service and/or in the performance of any allocation agreement or other transaction document in connection with a Transaction, you will not violate any applicable laws or third-party rights.
10. Third-Party Services and Linked Websites
Realizse may provide tools through the Service that enable you to export information, including User Content, to third-party services, including through features that allow you to link your Account on the Service with an account on a third-party service. By using one of these tools, you hereby authorize Realizse to transfer that information to the applicable third-party service. Third-party services are not under the control of Realizse, and, to the fullest extent permitted by law, we are not responsible for any third-party service's use of your exported information. The Service may also contain links to third-party websites. Linked websites are not under Realizse's control, and we are not responsible for their content. Please be sure to review the terms of use and privacy policy of any third-party services before you share any User Content or information with such third-party services. Once sharing occurs, Realizse will have no control over the information that has been shared.
11. Data Ownership and Licensing
11.1 Client Data Ownership
The Client retains all right, title, and interest in and to the data it submits to the Service, and owns all other data associated with its Projects, including data contributed by Participating Organizations (together, "Client Data"). Client Data includes organization information, asset and product data, project data, and uploaded files, subject to the licenses granted in these Terms. Each Participating Organization assigns to the Client all of its rights in the data it contributes to the Client's Projects; to the extent any such assignment is not effective, the Participating Organization grants the Client a perpetual, irrevocable license to use that data for the applicable Project and related tax and compliance purposes. Client Data does not include the account details of Users or the contact details of Organizations, which Realizse handles for itself under the Privacy Policy.
11.2 Processing License
By Posting User Content to or via the Service, you grant Realizse a worldwide, non-exclusive, revocable, royalty-free, fully paid, and transferable right to use, copy, store, disclose, transmit, transfer, publicly display, modify, and create derivative works from Client Data only as necessary to: (a) provide the Service and fulfill its obligations under these Terms; (b) derive, generate, create, or compile Usage Data or Aggregated Data and to use such data as set forth in Section 11.4; and (c) as otherwise required by law or as agreed to in writing between the parties. This license terminates upon termination of the agreement, subject to any data retention obligations set out in Section 15.
11.3 Realizse Passport and Verifiable Credential Ownership
(a) Definitions. For purposes of this Section 11.3:
(i) "Passport Owner" means the Organization that is designated as the owner of an Asset, Project, or Product Passport on the Platform (a “Realizse Passport”), which shall be the Organization that holds the subscription under which the Realizse Passport was created and that pays the applicable fees for such Realizse Passport, or any successor Organization to which ownership of the Realizse Passport has been transferred in accordance with Section 11.3(f).
(ii) "Contributing Organization" means any Organization other than the Passport Owner that submits data, documents, certifications, or other content to the Platform that is associated with or incorporated into a Realizse Passport as a Verifiable Credential, including without limitation certifiers, designers, auditors, insurers, and other project participants.
(b) Ownership Principle. The Passport Owner shall have sole ownership of, and sole authority and control over, the Realizse Passport and all Verifiable Credentials, data, documents, files, and other content associated with such Realizse Passport (collectively, the "Passport Data"), regardless of which Organization or individual originally contributed any element of such Passport Data to the Platform.
(c) Contributing Organization Rights. A Contributing Organization acknowledges and agrees that, upon submitting data or content to the Platform that is associated with a Realizse Passport:
(i) such data and content become part of the Passport Data under the control of the Passport Owner;
(ii) the Contributing Organization does not retain any ownership interest in, or independent right to control, delete, modify, or demand removal of, any data or content it has contributed to the Passport Data;
(iii) the Contributing Organization's submission of data to the Platform constitutes a transfer of control over such data to the Passport Owner for the purposes contemplated by these Terms; and
(iv) the Contributing Organization may retain read access to Passport Data associated with projects in which it has participated, subject to the Platform's access controls, the Passport Owner's continued participation on the Platform and the terms of Section 11.3(e).
(d) Passport Owner Authority. The Passport Owner shall have the exclusive right to:
(i) request deletion or removal of Passport Data from the Platform, subject to the deletion limitations set forth in Section 15.3 and the compliance record retention obligations set forth in Section 15.1;
(ii) request export of Passport Data in accordance with Section 15.6;
(iii) authorize or restrict third-party access to Passport Data through the Platform's access controls, which apply to a whole Project, Asset or Product and do not permit removing a party while a document is out for signature, during or after certification, after a Project is locked, or where that party is the claimant; and
(iv) transfer ownership of the Realizse Passport to another Organization in accordance with Section 11.3(f).
No Contributing Organization or other third party may exercise any of the foregoing rights with respect to a Realizse Passport except with the Passport Owner's express written authorization.
(e) Effect of Passport Owner Departure. If the Passport Owner elects to terminate its use of the Service or requests deletion of its account:
(i) Realizse shall provide the Passport Owner with a data export in accordance with Section 15.6 during the transition period set forth in Section 25.11(c);
(ii) Realizse shall notify all Contributing Organizations that have participated in projects associated with the departing Passport Owner's Realizse Passports, informing them that the Passport Owner has elected to leave the Platform and that associated Passport Data will be subject to deletion following the transition period;
(iii) Contributing Organizations shall have a period of thirty (30) days following receipt of such notice (or the remainder of the transition period under Section 25.11(c), whichever is longer) to export any Passport Data to which they had access prior to the Passport Owner's departure; and
(iv) Following expiration of the applicable transition and notice periods, Realizse shall proceed with deletion of Passport Data to the extent permitted under these Terms, subject to the compliance record retention obligations in Section 15.1 and the deletion limitations in Section 15.3.
(f) Passport Transferability. Ownership of a Realizse Passport may be transferred from one Organization to another, including in connection with a sale or transfer of the underlying asset. A transfer of ownership shall be effected by written request to Realizse, and shall require the consent of both the transferring and receiving Organizations. Upon transfer, the receiving Organization shall assume all rights and obligations of the Passport Owner under these Terms with respect to the transferred Realizse Passport.
(g) Realizse's Role. Realizse issues Verifiable Credentials as the cryptographic issuer based on data provided by or on behalf of the Client. Realizse's role as issuer does not confer upon Realizse any ownership interest in the Passport Data or the underlying asset. Realizse's liability with respect to the accuracy of Verifiable Credential content is limited as set forth in Section 17.4 (Credential Content) and Section 22 (Disclaimers).
(h) Warranty Reliance. The ownership model set forth in this Section 11.3 is predicated on the representations and warranties made by the Client in Section 22-A (Customer Representations and Warranties Regarding Customer-Uploaded Content). Realizse is entitled to treat the Passport Owner as having full authority over all Passport Data without independent verification, and shall have no liability for any dispute between the Passport Owner and any Contributing Organization regarding rights to data contributed to a Realizse Passport.
11.4 Usage Data; Aggregated Data
We may collect, access, use, disclose, transfer, transmit, store, host, or otherwise process your Usage Data and Aggregated Data for lawful business purposes, such as to: (a) track use of the Service; (b) provide support for the Service; (c) monitor the performance and stability of the Service; (d) prevent or address technical issues with the Service; (e) improve the Service, our other products and services, and to develop new products and services; and (f) for all other lawful business practices, such as analytics, benchmarking, and reports. You will not interfere with the foregoing processing of Usage Data and Aggregated Data. To the extent we share Aggregated Data or Usage Data publicly, it shall have been de-identified or aggregated such that the resulting data no longer reasonably identifies you, any specific Project, or other identifying information. Realizse shall take reasonable technical measures to ensure that Usage Data and Aggregated Data cannot be associated with any individual, shall not attempt to re-identify any individual from such data, and shall contractually require anyone with whom it shares such data to do the same, consistent with Cal. Civ. Code §1798.140(m). Realizse's rights regarding Usage Data and Aggregated Data hereunder shall survive the termination of these Terms.
11.5 User Content Representations and Warranties
You must not Post User Content if you are not the owner of or are not fully authorized to grant rights in all of the elements of that User Content. Realizse disclaims any and all liability in connection with User Content. You are solely responsible for your User Content and the consequences of providing User Content via the Service. By providing User Content via the Service, you affirm, represent, and warrant to us that:
(a) You are the creator and owner of the User Content, or have the necessary licenses, rights, consents, and permissions to authorize Realizse and users of the Service to use and distribute your User Content as necessary to exercise the licenses granted by you in this Section, in the manner contemplated by Realizse, the Service, and these Terms.
(b) Your User Content, and the Posting or other use of your User Content as contemplated by these Terms, does not and will not: (i) infringe, violate, misappropriate, or otherwise breach any third-party right, including any copyright, trademark, patent, trade secret, moral right, privacy right, right of publicity, or any other intellectual property, contract, or proprietary right; (ii) slander, defame, libel, or invade the right of privacy, publicity, or other property rights of any other person; or (iii) cause Realizse to violate any law or regulation.
11.6 Monitoring Content
Realizse does not have any obligation to monitor: (a) User Content; (b) any content made available by third parties; or (c) the use of the Service by its users. Any monitoring by Realizse of information transmitted or received through the Service is subject to Section 26.10 and is limited to the automated platform monitoring described in Section 26.10(d) and access for the purposes permitted under Section 26.10(b). Realizse may revise marketplace listings and bids shown to other users only to remove identifying information or to correct obvious errors, and will notify the User who Posted the listing or bid of any such revision. Realizse never alters uploaded files, signed documents, Verifiable Credentials, or compliance records; this does not restrict the removal of personal details under Sections 15 and 17 when the applicable retention period ends or on a valid erasure request. Realizse may remove from view or disable access to any User Content, including any listing, for legal reasons, where Realizse believes that any party is prohibited, or may be prohibited, from entering into a Transaction on the Platform due to violation of law or any third-party right or contract, or for breach of these Terms, with notice to the Client where lawful, and without any liability to the user who Posted such User Content or to any other users of the Service. Removing User Content from view or disabling access to it is not deletion, and retention under Section 15.1 continues to apply.
12. Privacy and Data Protection
12.1 PII Collected
The Service collects and processes the following categories of personally identifiable information:
- User PII: Email addresses, first and last names, phone numbers, job titles, optional departments, and account and Organization-membership information.
- Organization contact PII: Contact person names, job titles, email addresses, phone numbers, and physical addresses.
- Project participant PII: Signer names, email addresses, job titles, company names, and (for final allocation agreements) physical addresses and phone numbers; qualified individuals' names, employers, and business addresses used in certification and tax records.
- Incidental PII in logs: User identifiers, email addresses, IP addresses, and other personal information in execution logs (retained for 365 days).
12.2 Purpose of Processing
PII is processed for the following purposes: (a) user authentication and access control; (b) organization account management and communication; (c) document generation and electronic signature; and (d) platform operation, security monitoring, and incident investigation.
12.3 Third-Party Data Sharing
PII is shared with the service providers listed in Section 13.1 solely for the purposes described there. No PII is sold, rented, or shared for marketing purposes.
12.4 Privacy Policy
(a) Incorporation. Realizse maintains a Privacy Policy, available at https://app.realizse.com/privacy (the "Privacy Policy"), and a Data Processing Addendum, available at https://app.realizse.com/dpa (the "DPA"), which describe Realizse's collection, use, storage, and disclosure of personal information in connection with the Service. The Privacy Policy is incorporated into and made a part of these Terms as provided in Section 26.2.
(b) Scope of the Privacy Policy. The Privacy Policy governs Realizse's processing of personal information in its capacity as a controller, including personal information relating to Users, Organization contacts, visitors to the Public Websites, and business contacts. The Privacy Policy describes the categories of personal information set forth in Section 12.1, the processing purposes set forth in Section 12.2, and the disclosures set forth in Section 12.3, and provides additional detail regarding retention, individual rights, cookies, and security.
(c) Scope of the DPA. Realizse's processing of personal information contained in Client Data on behalf of and at the direction of the Client is governed by the DPA, under which the Client (or, where applicable, the Passport Owner) acts as controller and Realizse acts as processor or service provider, as further described in Section 12.5(c). The Client is responsible for providing any privacy notices required under applicable law to individuals whose personal information is contained in Client Data.
(d) Order of Precedence. In the event of a conflict between the Privacy Policy, the Data Processing Addendum, and these Terms, these Terms shall govern with respect to the parties' contractual rights and obligations. In the event of a conflict between the DPA and either these Terms or the Privacy Policy with respect to the processing of personal information contained in Client Data, the DPA shall govern.
(e) Changes. Realizse may update the Privacy Policy from time to time. Material changes to the Privacy Policy are subject to the notice requirements of Section 25.14.
12.5 State Privacy Laws
(a) Applicability. The Service is designed for use by business organizations in a business-to-business context. The Platform does not collect personal information directly from consumers, and Client Data processed through the Platform is submitted by or on behalf of business organizations in their professional capacity.
(b) Compliance Commitment. To the extent that any U.S. state consumer privacy law — including the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA), the Virginia Consumer Data Protection Act (VCDPA), the Colorado Privacy Act (CPA), the Connecticut Data Privacy Act (CTDPA), or any successor or equivalent legislation in any U.S. state (collectively, "State Privacy Laws") — applies to Realizse's processing of personal information in connection with the Service, Realizse shall comply with the applicable requirements of such State Privacy Laws.
(c) Controller/Processor Designation. Where State Privacy Laws apply, the parties acknowledge that: (i) the Client is the "business" or "controller" (as those terms are defined in applicable State Privacy Laws) with respect to personal information contained in Client Data; and (ii) Realizse is the "service provider" or "processor" (as applicable) processing such personal information on behalf of the Client for the purposes set forth in Section 12.2 and in accordance with these Terms and the DPA.
(d) No Sale of Personal Information. Realizse does not sell, share (as defined in the CCPA/CPRA), or otherwise make available personal information contained in Client Data for cross-context behavioral advertising or for any purpose other than providing the Service as described in these Terms.
(e) Consumer Rights Requests. If Realizse receives a verifiable consumer request from an individual seeking to exercise rights under applicable State Privacy Laws with respect to personal information contained in Client Data, Realizse shall promptly notify the Client and shall cooperate with the Client in responding to such request. Realizse shall not independently respond to such requests except as directed by the Client or required by applicable law.
13. Service Providers and Sub-Processors
13.1 Service Providers
Realizse uses the following third-party service providers to deliver the Service and operate the Public Websites. The service providers that handle data for the Client are Realizse's sub-processors ("Sub-Processors"), and Sections 13.2 through 13.4 apply to them only.
| Service Provider | Role | Handles Data For | Data Location | Key Data Processed | DPA Status |
|---|---|---|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure | The Client and Realizse | United States | All Platform data, including personal information, in encrypted storage | Covered via AWS Data Processing Addendum (incorporated into AWS Customer Agreement) |
| Auth0 (Okta, Inc.) | Identity and access management | Realizse | United States | User email, name, role, organization membership | Covered via Okta Data Processing Addendum (incorporated into Okta subscription terms) |
| Spherity GmbH | Decentralized identity and verifiable credentials | The Client | European Union (Germany) | Organization identities, DIDs, verifiable credential content | Under review — general terms include customer data provisions (Section 5); standalone DPA and Standard Contractual Clauses to be confirmed |
| PandaDoc, Inc. | Document generation and electronic signature | The Client | United States | Signer details, document content, project and building data, and the audit trail | Covered by PandaDoc's Data Processing Agreement, incorporated into its Master Services Agreement |
| Google LLC | Google Workspace email; Apps Script, which receives the www.realizse.com contact form; Google Maps for address search and maps in the Platform | Realizse | — | Email and contact form messages; addresses and map coordinates entered in the Platform | — |
| Cloudflare, Inc. | Cloudflare Web Analytics for www.realizse.com (cookieless) | Realizse | — | Website usage information | — |
13.2 Data Processing
Each Sub-Processor processes Client Data solely for the purpose of performing its designated function in delivering the Service. Realizse maintains data processing agreements (or contractual provisions with equivalent data protection obligations) with each Sub-Processor. The current DPA status of each Sub-Processor is shown in Section 13.1. Realizse shall update Section 13.1 and notify affected Clients within thirty (30) days of any material change to the DPA status of any Sub-Processor.
13.3 Cross-Border Data Transfer
(a) EU Processing. Spherity GmbH processes and stores verifiable credential data in the European Union (Germany). All other Sub-Processors process data within the United States.
(b) Transfer Mechanism. To the extent that any transfer of Personal Data to Spherity GmbH constitutes a cross-border data transfer subject to applicable data protection law, Realizse shall ensure that such transfer is covered by an appropriate legal transfer mechanism, which may include: (i) the European Commission's Standard Contractual Clauses (Module Two: Controller to Processor, or Module Three: Processor to Processor, as applicable), as set out in Commission Implementing Decision (EU) 2021/914; (ii) the EU-U.S. Data Privacy Framework or any successor adequacy mechanism, where applicable; or (iii) such other transfer mechanism as is recognized under applicable law.
(c) Data Localization. If a Client requires that no Personal Data be transferred outside the United States, the Client shall notify Realizse in writing prior to onboarding. Realizse shall work with the Client in good faith to assess whether an alternative architecture (including potential US-hosted deployment of Spherity's infrastructure) is available. Any additional costs associated with a data localization request shall be borne by the Client.
(d) Status. As of the date these Terms were last updated, the applicable transfer mechanism between Realizse and Spherity GmbH is being established. Realizse shall notify the Client promptly if the applicable transfer mechanism changes or is invalidated by a court or regulatory authority.
13.4 Sub-Processor Changes
(a) Notification. Realizse shall provide Client with at least thirty (30) days' prior written notice before engaging any new Sub-Processor or materially changing the role of an existing Sub-Processor in a manner that affects the processing of Client Data. Such notice may be provided via email to the address associated with the Client's Account or through a notification within the Platform.
(b) Objection Right. If Client has a reasonable, good-faith objection to a new or changed Sub-Processor based on data protection or security concerns, Client shall notify Realizse in writing within fifteen (15) days of receiving the notice described in Section 13.4(a), specifying the grounds for the objection. Realizse shall use commercially reasonable efforts to address Client's concerns, which may include offering an alternative Sub-Processor or modifying the scope of data processed. If Realizse is unable to address Client's objection within thirty (30) days, Client may terminate these Terms upon written notice, and Realizse shall refund a pro-rata portion of any prepaid fees for the unexpired subscription term.
(c) Emergency Sub-Processor Changes. Notwithstanding Section 13.4(a), Realizse may engage a new Sub-Processor without prior notice where necessary to address a security incident, maintain Service availability, or comply with a legal obligation, provided that Realizse notifies Client as soon as reasonably practicable and in no event later than five (5) business days after the engagement.
14. Security Measures
14.1 Authentication and Access Control
Realizse implements the following authentication and access controls: (a) all user authentication is managed through a SOC 2-certified identity provider using OAuth 2.0 with JSON Web Tokens; (b) role-based access control with defined permission scopes enforced on every user API request; (c) organization-scoped data isolation ensuring that each Client's data is accessible only to its authorized Users, Users with authorized cross-Organization access, and Realizse personnel as permitted under Section 26.10; and (d) JWT token validation (signature, expiration, audience, issuer) at the API gateway before any user API request reaches application logic.
14.2 Encryption
(a) At rest: All data stored in the Service is encrypted at rest using industry-standard encryption.
(b) In transit: All data transmitted to and from the Service is encrypted using TLS 1.2 or higher.
14.3 Network Security
Realizse maintains a web application firewall that inspects API traffic routed through the content delivery network for known attack patterns and blocks requests from known malicious sources. Rate limiting enforcement is present and takes place at the API gateway.
14.4 Data Integrity
(a) Files are stored using content-addressable storage with SHA-256 cryptographic hashing, enabling independent verification that file content has not been altered.
(b) Files are stored using content-addressed storage, and their content cannot be modified through the Service after upload.
(c) Signed documents are stored with SHA-256 hashes that enable verification of file integrity.
(d) Verifiable credentials include cryptographic proofs that make any tampering detectable.
14.5 Monitoring
Realizse maintains logging and monitoring of API access and application execution. Logs are encrypted at rest and retained in accordance with the retention periods set out in Section 15.
14.6 Security Commitment
(a) Standard of Care. Realizse implements and maintains commercially reasonable administrative, technical, and organizational security measures designed to protect Client Data against unauthorized access, use, alteration, disclosure, or destruction, taking into account the nature, scope, and purposes of the processing, the state of the art of available security technology, and the costs of implementation.
(b) No Absolute Guarantee. Client acknowledges that no method of electronic storage or transmission over the Internet is completely secure. Realizse does not warrant that the Service is impervious to all security threats, and Realizse's obligation under this Section 14.6 is limited to the exercise of commercially reasonable efforts as described in Section 14.6(a).
(c) Security Maturity Roadmap. Realizse is committed to pursuing independent security certifications, including SOC 2 Type 1, as organizational resources permit. Realizse will notify Client in writing upon achieving any such certification and will make the applicable audit report or certification available to Client upon reasonable request, subject to applicable confidentiality obligations.
(d) Incident Notification. In the event Realizse becomes aware of a confirmed unauthorized access to, or unauthorized acquisition, disclosure, or use of, Client Data, or a confirmed breach of security leading to the accidental or unlawful destruction, loss, or alteration of Client Data (each, a "Security Incident"), Realizse shall: (i) notify Client in writing, by email to the Client's account administrator at the email address on file, without unreasonable delay and in no event later than seventy-two (72) hours after confirmation of the Security Incident; (ii) provide Client with a description of the nature of the incident, the categories and approximate volume of data affected, and the measures taken or proposed to be taken to address the incident; and (iii) cooperate with Client in good faith to investigate and remediate the incident. For the avoidance of doubt, unsuccessful security events — such as blocked intrusion attempts, port scans, denial-of-service attacks that do not result in unauthorized access to, or the destruction, loss, or alteration of, Client Data, or failed login attempts — do not constitute Security Incidents.
15. Data Retention and Deletion
15.1 Compliance Record Retention
Realizse keeps compliance records — the signed documents, Verifiable Credentials, building data, certification records, and supporting files associated with a Project — for seven (7) years from the date the certification package for the Project is issued, because Project participants may need them to support a Section 179D deduction. For compliance records with no certification package, the seven (7) years run from the end of the Client's subscription. At the end of that period, Realizse removes the personal details from the compliance records unless the Client asks Realizse to keep the records longer. Clients should export and keep their own copies of compliance records, as they may need them for longer.
15.2 Platform Retention
The Service retains data as follows:
| Data Type | Retention Period | Deletable through the Service |
|---|---|---|
| Files and signed documents | Seven (7) years (Section 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No |
| Verifiable credentials | Seven (7) years (Section 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No |
| Organization records | Duration of service agreement | No |
| User accounts | Duration of service agreement (can be disabled) | Disable only |
| Project records | Seven (7) years (Section 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No |
| Asset and product passport records | Seven (7) years (Section 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No |
| API access logs | 365 days | Automatic |
| CDN access logs | 90 days | Automatic |
| Application execution logs | 365 days | Automatic |
15.3 Deletion Limitations
The Client acknowledges that due to the nature of the Service:
(a) Files stored in Content-Addressed Storage cannot be deleted through the Service. The content-addressed storage model is designed to preserve compliance evidence and ensure data integrity.
(b) Verifiable Credentials cannot be modified without invalidating their cryptographic proofs and cannot be deleted through the Service after issuance. Realizse removes personal details from its copy of a Verifiable Credential as described in Section 17.2.
(c) User accounts can be disabled (preventing further access) but cannot be permanently deleted through the Service. References to the user in project records, file metadata, and activity logs are preserved.
(d) Organization records, project records, and passport records do not have deletion mechanisms in the current version of the Service.
(e) Backups. Erased data can remain in backups for up to ninety (90) days before it is automatically deleted. Backups are used only for disaster recovery, and erasures are applied again after any restore.
15.4 Right to Erasure
(a) Erasure Requests. The Passport Owner (as defined in Section 11.3) may request deletion of Passport Data associated with its Realizse Passports by submitting a written request to Realizse at support@realizse.com.
(b) Scope of Erasure. Upon receipt of a valid erasure request, Realizse shall delete or render inaccessible the Passport Data identified in such request, subject to the following limitations:
(i) Retention Override. Where Passport Data consists of compliance records, Realizse shall retain such data for the compliance record retention period set forth in Section 15.1 notwithstanding any erasure request. Realizse shall inform the Passport Owner of any data that cannot be deleted due to compliance record retention;
(ii) Technical Deletion Limitations. Erasure is subject to the deletion limitations set forth in Section 15.3, including the immutability of Verifiable Credentials, the limitations on file deletion through the Service, and the persistence of data at Sub-Processors. Where full deletion is not technically feasible, Realizse shall render the data inaccessible through the Service (including by revoking all access permissions and removing the data from active query results);
(iii) Sub-Processor Data. Erasure of data stored at Sub-Processors is subject to each Sub-Processor's technical capabilities and retention policies as described in Section 15.5. Realizse shall use commercially reasonable efforts to cause Sub-Processors to delete or render inaccessible the relevant data; and
(iv) Contributing Organization Notice. Prior to executing an erasure request that affects Passport Data to which Contributing Organizations had access, Realizse shall provide notice to such Contributing Organizations in accordance with Section 11.3(e) and shall allow the applicable notice and transition periods to expire before proceeding with deletion.
(c) Erasure Timeline. Subject to the notice and transition periods applicable under Section 11.3(e) and Section 25.11(c), Realizse shall complete the erasure of eligible data within thirty (30) days following the expiration of all applicable notice and transition periods.
(d) Non-Owner Erasure Requests. A Contributing Organization may request that Realizse delete the Contributing Organization's own organizational account and profile data from the Platform. Such request shall not extend to any Passport Data that the Contributing Organization contributed to Realizse Passports owned by other Organizations, which shall remain under the control of the applicable Passport Owner in accordance with Section 11.3.
(e) Account Disabling. Where full deletion of a User account is not technically feasible (as described in Section 15.3(c)), Realizse shall disable the account to prevent further access and shall remove the User's identity provider record. References to the User in project records, file metadata, activity logs, and Verifiable Credentials shall be preserved to the extent required for compliance record retention and platform integrity.
15.5 Third-Party Retention
Data shared with Sub-Processors and other service providers listed in Section 13.1 is subject to each provider's own retention policies. In particular:
(a) Verifiable credentials stored at Spherity are immutable and persist indefinitely.
(b) Signed documents stored at PandaDoc are retained per PandaDoc's retention policy. Realizse maintains independent copies of all signed documents.
(c) A User's identity record at the identity provider is removed when Realizse disables the User's Account under Section 15.4(e).
15.6 Data Portability
(a) Export Right. The Client has the right to request export of all Client Data, and the Passport Owner has the right to request export of all Passport Data associated with its Realizse Passports, at any time during the term of the subscription and during any applicable post-termination transition period.
(b) Export Format. Upon receipt of a valid export request, Realizse shall provide the requested data in the following format:
(i) Verifiable Credentials and Records: JSON files, with Verifiable Credentials conforming to the W3C Verifiable Credentials Data Model and each Realizse Passport represented as a structured JSON object containing all associated Verifiable Credentials; and
(ii) Supporting Documentation: All files associated with the exported data (including PDFs, signed documents, images, and other uploaded files) aggregated in a compressed archive (ZIP format), organized by Realizse Passport and project or asset.
(c) Delivery. Realizse shall make the export available for download through a secure, authenticated link. Export requests shall be fulfilled within thirty (30) business days of receipt of the request, or, in the case of post-termination exports, within the transition period set forth in Section 25.11(c).
(d) Export Fees. One (1) data export per twelve-month subscription period shall be provided at no additional charge. Realizse reserves the right to charge a reasonable administrative fee for additional export requests, as set forth in the applicable Order Form.
(e) API Access. Nothing in this Section 15.6 limits the Client's ability to access and retrieve its data on a per-resource basis through the API during the term of the subscription, subject to the API terms set forth in Section 27.
(f) Participating and Contributing Organization Exports. A Participating or Contributing Organization may request export of data it is authorized to access under Section 4.3 or Section 11.3(c)(iv), in the format specified in Section 15.6(b). Export rights after the Passport Owner's departure are governed by Section 11.3(e).
16. Electronic Signatures
16.1 Consent to Electronic Signatures
By using the document signing features of the Service, Client and its Users consent to the use of electronic signatures for all legally binding agreements, certifications, authorizations, and documents generated through or in connection with the Platform, including but not limited to Digital Passport issuances, compliance certifications, tax credit and deduction representations (including for Section 179D), transaction authorizations, and any amendments or addenda thereto. Electronic signatures executed through the Platform are governed by and comply with the Electronic Signatures in Global and National Commerce Act (15 U.S.C. § 7001 et seq.) (ESIGN Act) and the Uniform Electronic Transactions Act (UETA) as adopted in the applicable jurisdiction. This consent constitutes a valid and binding agreement to transact electronically and no party shall challenge the legal enforceability of an electronically executed document on the basis that it was not executed in handwritten form, provided the electronic signature was completed through the Platform's designated signing infrastructure.
16.2 E-Signature Provider
Electronic signatures are provided by PandaDoc, Inc., a SOC 2-certified e-signature provider. The signing process is managed by PandaDoc's platform, and signers interact directly with PandaDoc's signing interface. Realizse may designate an alternative electronic signature provider from time to time upon reasonable notice to Client, provided any successor provider maintains equivalent SOC 2 certification or comparable security standards.
16.3 Signing Process
Documents generated through the Service are sent to designated signers via email in a defined sequence. Each signer must complete their signature before the next signer is invited. The default signing order for 179D projects is: (1) Auditor, (2) Designer, (3) Owner. Project participants may or may not have Platform Accounts; document signers receive signing invitations via email from PandaDoc and interact with PandaDoc's signing interface directly.
16.4 Signer Data
The following personal information is shared with PandaDoc for document generation and signing: signer name, email address, job title, and company name. For final allocation agreements, street address, city, state, postal code, and phone number are also shared with PandaDoc. All signers receive and may review the full document content prior to execution. PandaDoc's collection and processing of signer data is governed by PandaDoc's privacy policy and terms of service, and Client acknowledges that signers interact directly with PandaDoc's platform.
16.5 Signed Document Validity
Completed signed documents are finalized as PDF files containing embedded signature metadata, including timestamps, content hashes, device information, and cryptographic signatures. Realizse stores signed documents in its Content-Addressed Storage system with SHA-256 integrity verification. Each executed document shall have the same legal force and effect as a document executed with a handwritten signature.
16.6 Audit Trail and Evidentiary Sufficiency
(a) Prima Facie Evidence. The PandaDoc-generated audit trail associated with each executed document — including the signatory's verified email address, IP address, geolocation data, timestamp of execution (in UTC), device fingerprint, and document hash — shall constitute prima facie evidence of: (i) the identity of the signatory; (ii) the time and place of execution; and (iii) the signatory's affirmative intent to execute the document.
(b) Document Integrity. The tamper-evident certificate of completion generated by the e-signature provider upon execution, incorporating a cryptographic hash of the executed document, creates a rebuttable presumption that the document was not altered after execution.
(c) Business Records. Client agrees and acknowledges that the audit trail generated by PandaDoc and the signed document records maintained by Realizse are business records maintained in the ordinary course of Realizse's operations and may be introduced as evidence in any legal, regulatory, arbitral, or administrative proceeding pursuant to Federal Rule of Evidence 803(6) or applicable state equivalent. Client waives any objection to the admissibility of such records solely on the basis of hearsay, provided the records are accompanied by a custodian certification or equivalent attestation.
(d) Burden of Proof in Disputes. In the event of any dispute regarding the authenticity, integrity, or authorship of a document executed through the Platform, the audit trail and embedded signature metadata shall serve as the primary evidentiary reference. The burden of demonstrating invalidity shall rest with the party challenging the signature, and such party must produce clear and convincing evidence sufficient to overcome the prima facie record established by the audit trail.
(e) Dispute Process. A party wishing to dispute the validity of an electronic signature executed through the Platform must: (i) provide written notice to Realizse at legal@realizse.com within ninety (90) days of the date the completed document was delivered to the disputing party; (ii) specify with particularity the basis for the dispute; and (iii) preserve and make available to Realizse all relevant device, account, and access records in the disputing party's possession or control. Realizse will provide the relevant audit trail and certificate of completion, to the extent available from the e-signature provider, to the disputing party within ten (10) business days of receiving such notice. Failure to provide timely written notice of a signature dispute shall constitute a waiver of any such dispute.
(f) Documents Signed Outside the Platform. The audit-trail and certificate provisions of this Section 16.6 apply only to documents signed through the Platform. Documents signed elsewhere and uploaded to the Platform are stored with a hash from the date of upload.
16.7 Signatory Authority
(a) Representation of Authority. Client represents, warrants, and covenants — on a continuing basis for so long as any individual executes documents through the Platform on Client's behalf — that each individual who executes any document, certification, authorization, or agreement through the Platform using credentials associated with Client's account (each, an "Authorized Signatory") has been duly authorized by Client to execute such document and to legally bind Client to the obligations, representations, and covenants contained therein. Client represents that it has adopted, and maintains in effect, such internal policies, resolutions, delegations of authority, or other governance mechanisms as are necessary to confer actual authority upon each Authorized Signatory for the types of transactions and documents executed through the Platform.
(b) Inherent and Apparent Authority. For purposes of any document executed through the Platform, any individual who accesses the Platform using Client's account credentials and completes the applicable signing workflow shall be deemed to have been granted actual, apparent, and inherent authority to execute such document on Client's behalf, and Client shall be estopped from denying such authority as against Realizse or any third party who relies on the executed document in good faith. The grant of Platform access credentials to any individual by Client constitutes an affirmative representation to Realizse and to all counterparties that such individual is authorized to execute documents of the type available for signature through the Platform.
(c) Credential Management. Client shall be solely responsible for managing, restricting, and revoking access credentials and signing permissions within the Platform. Any failure to do so shall not affect the binding nature of documents executed prior to such restriction or revocation being communicated to Realizse in writing pursuant to Section 16.7(d).
(d) Revocation of Authority. Client may prospectively revoke an individual's signing authority by providing written notice to Realizse at legal@realizse.com and disabling such individual's Platform access. Such revocation shall be effective upon Realizse's written acknowledgment and shall not affect the validity of any document executed prior to the effective date of revocation.
(e) Indemnification. Client's indemnification obligations with respect to claims arising from unauthorized signing, access credential mismanagement, or internal authority disputes are set forth in Section 24 (Indemnification).
16.8 Survival
The representations, warranties, acknowledgments, and waivers set forth in this Section 16 shall survive the termination or expiration of this Agreement and shall remain in full force and effect with respect to any document executed through the Platform during the term hereof.
17. Verifiable Credentials
17.1 Issuance
The Service issues verifiable credentials at designated milestones in project workflows and upon asset or product passport publication. Credentials are issued in accordance with the W3C Verifiable Credentials Data Model standard using Decentralized Identifiers (DIDs).
17.2 Immutability
The Client acknowledges that verifiable credentials, once issued, cannot be modified without invalidating their cryptographic proofs and cannot be deleted through the Service. Verifiable Credentials carry as few personal details as possible. When the applicable retention period ends, or on a valid erasure request, Realizse removes the personal details from its copy of a Verifiable Credential and keeps a record of the Verifiable Credential's identifier, issuer, issuance date, and hash.
17.3 Credential Correction
(a) Immutability Disclosure. Verifiable Credentials issued through the Service are designed to be tamper-evident. Once issued, the content of a Credential cannot be altered without invalidating its cryptographic signature. The Client acknowledges this design characteristic and accepts that corrections to Credential content require the issuance of a new Credential rather than modification of an existing one. Realizse issues a corrected Credential at the Passport Owner's request.
(b) Accuracy Responsibility. Realizse does not independently verify the accuracy of Client-supplied data used to generate Credential content. The Client is solely responsible for the accuracy and completeness of data submitted to the Service that becomes part of a Verifiable Credential. Subject to Section 23 (Limitation of Liability), Realizse shall not be liable for losses arising from Credentials that accurately reflect inaccurate Client-supplied data.
(c) Revocation Capabilities. Realizse shall disclose the current state of Credential revocation capabilities to the Client upon request. As additional revocation mechanisms become available through the Service or its Sub-Processors (including Spherity GmbH), Realizse shall make such capabilities available to the Passport Owner at no additional charge.
(d) Correction Fee. The first correction of a Credential per calendar quarter shall be provided at no additional charge. Subsequent corrections within the same quarter may be subject to a reasonable administrative fee as set forth in the applicable Order Form.
17.4 Credential Content
Verifiable credentials contain data supplied by the Client (directly or through project workflows) and are signed by Realizse as the issuer. Verifiable credentials carry as few personal details as possible. The Client is responsible for the accuracy of data submitted to the Service that becomes part of a verifiable credential.
17.5 Credential Storage
Verifiable credentials are stored in two locations: (a) locally within Realizse's infrastructure (United States) for operational access; and (b) at Spherity GmbH (European Union, Germany) as the authoritative issuance record.
17.6 Future Issuer Model
The Service currently uses a single-issuer model where Realizse issues all credentials. In future versions, organizations with appropriate authority may issue credentials under their own DIDs. The transition to a multi-issuer model will be communicated to Clients in advance.
18. File Storage and Integrity
18.1 Storage Model
Files uploaded to or generated by the Service are stored using Content-Addressed Storage. Each file is identified by its SHA-256 cryptographic hash — a mathematical fingerprint of the file's content. This enables independent verification that file content has not been altered.
18.2 Stored File Content
Clients cannot modify or delete stored file content through the Service after upload. If a file with identical content is uploaded again for the same owning organization, it may create an additional stored version.
18.3 Encryption
All files are encrypted at rest using AWS Key Management Service (KMS) with a dedicated encryption key per environment and automatic key rotation.
18.4 File Content Responsibility
The Platform stores files as opaque binary objects and does not inspect, index, or validate the content of uploaded files. The Client is solely responsible for ensuring that files uploaded to the Service do not contain unlawful, harmful, or rights-infringing content.
18.5 File Size and Format Limits
Files are subject to: maximum size of 100 MB, maximum filename length of 200 characters, and must have a valid content type.
19. Service Levels
19.1 Availability
Realizse shall use commercially reasonable efforts to make the Service available twenty-four (24) hours a day, seven (7) days a week, excluding:
(a) Scheduled maintenance windows, which Realizse may schedule from time to time and for which Realizse shall provide at least twenty-four (24) hours' prior notice via the Platform dashboard or email to the Client's account administrator;
(b) Emergency maintenance required to address security vulnerabilities or data integrity risks, for which Realizse shall provide notice as soon as reasonably practicable;
(c) Force Majeure Events as defined in Section 23.4; and
(d) Outages or performance degradation caused by factors outside Realizse's reasonable control, including failures of third-party infrastructure providers (AWS, Auth0/Okta, Spherity GmbH), Internet service providers, or Sub-Processors identified in Section 13.
Uptime Target. Realizse targets a monthly platform availability of ninety-nine percent (99.0%) for the Service, measured as the percentage of total minutes in a calendar month during which the Service's core API endpoints are responsive, excluding the periods described in subsections (a)–(d) above. This target reflects Realizse's operational objective and does not constitute a guarantee or service level agreement with financial remedies.
SLA Evolution. As Realizse matures its operational infrastructure, the parties may negotiate a Service Level Agreement with defined uptime commitments and service credits as part of an Order Form or enterprise subscription agreement. Any such SLA shall supplement, and to the extent of any conflict, supersede, the general availability provisions of this Section 19.
Incident Notification. In the event of a material service disruption (defined as an unplanned outage affecting core Platform functionality for more than sixty (60) minutes), Realizse shall: (i) notify the Client's account administrator via email within four (4) business hours of becoming aware of the disruption; (ii) provide periodic status updates at least every four (4) business hours until service is restored; and (iii) deliver a written incident summary within five (5) business days of resolution, including root cause (to the extent determinable), duration, affected services, and remediation steps taken. For purposes of this paragraph, "business hours" means the regular business hours described in Section 19.2(a).
19.2 Support
(a) Standard Support. Realizse provides standard technical support to all Clients via email at support@realizse.com during regular business hours (Monday through Friday, 9:00 AM to 6:00 PM Eastern Time, excluding U.S. federal holidays).
(b) Response Targets. Realizse shall use commercially reasonable efforts to respond to support requests within the following timeframes:
(i) Critical (Service is unavailable or Client Data is at risk): initial response within four (4) business hours;
(ii) High (material feature is impaired but Service is operational): initial response within one (1) business day;
(iii) Normal (non-critical questions, feature requests, general inquiries): initial response within two (2) business days.
(c) No Guaranteed Resolution Time. The response targets in Section 19.2(b) are targets, not guarantees. Realizse shall use commercially reasonable efforts to resolve issues promptly but does not commit to specific resolution timeframes.
(d) Enhanced Support. Enhanced support tiers with dedicated support contacts, faster response targets, and extended hours may be made available pursuant to a separate agreement or Order Form.
20. Confidentiality
20.1 Confidential Information
"Confidential Information" means information disclosed to or by you under these Terms or through the use of the Platform that is designated by the party disclosing the information as proprietary or confidential or that should be reasonably understood to be proprietary or confidential due to its nature and the circumstances of its disclosure. Confidential Information includes: any technical or performance information about the Service; presentations describing Realizse's offerings; the identity of any customers, users, or prospective customers or users shared by either party; information relating to any planned or completed Projects, including the location, nature, ownership, or expected operating dates of such Projects; pricing information and transaction terms and conditions (whether final or indicative) relating to Tax Deductions or the use of any Service; any draft, final, form, or template documents shared in connection with a proposed Transaction; Client Data; technical specifications; business plans; and proprietary information relating to the market for allocations of Section 179D deductions.
20.2 Obligations
Each party shall: (a) use Confidential Information solely for the purposes of these Terms; (b) protect Confidential Information using at least the same degree of care it uses for its own confidential information, but no less than reasonable care; and (c) not disclose Confidential Information to third parties except as permitted under these Terms (including to Sub-Processors as set out in Section 13). Each party may disclose Confidential Information to its employees, agents, contractors, attorneys, advisors, accountants, and other representatives having a legitimate need to know (including, for Realizse, its subcontractors and intermediary partners), provided it remains responsible for their compliance with this Section 20 and they are bound to confidentiality obligations no less protective than this Section 20. Realizse may make Confidential Information about a Project available to that Project's participants, but only within the access each participant has under these Terms.
20.3 Exclusions
These confidentiality obligations do not apply to information that the receiving party can document: (a) is or becomes publicly available through no fault of the receiving party; (b) was known to the receiving party prior to disclosure; (c) was rightfully received from a third party without breach of confidentiality obligations; (d) was independently developed by the receiving party without use of the Confidential Information; (e) is shared by the disclosing party with another participant through its use of the Platform, including the posting of any listing, bid activities in connection with any listing, or exchanging information through a data room, a shared Project, or any other part of the Platform, but only to the extent of that participant's use or disclosure expressly authorized by the party entitled to authorize it; Realizse continues to protect such information as Confidential Information under this Section 20; or (f) is used or disclosed by Realizse as expressly permitted under these Terms, but only to the extent of that permitted use or disclosure; all other confidentiality obligations continue to apply.
20.4 Public Announcements
You acknowledge and agree that Realizse shall be permitted to make public announcements regarding your activity on the Platform, including the closing of a Transaction, but that any such announcements shall not include your name, the name of any Project, or any other identifying information without your consent, which shall not be unreasonably withheld, conditioned, or delayed. You agree to reasonably cooperate with Realizse on any such announcements, and that upon your approval of any public announcement, Realizse shall be entitled to use the information contained in such public announcement for other public purposes, including speaking engagements, reports, or otherwise.
20.5 Compelled Disclosure
A party may disclose Confidential Information to the extent required by law, regulation, or court order, provided that it gives the other party prompt written notice (where legally permitted) and cooperates with efforts to obtain protective treatment.
20.6 Remedies
Unauthorized use or disclosure of Confidential Information may cause substantial harm for which damages alone are an insufficient remedy. The disclosing party may seek appropriate equitable relief, in addition to other available remedies, for breach or threatened breach of this Section 20.
21. Dispute Resolution and Arbitration
21.1 Generally
Except as described in Section 21.2 and 21.3, you and Realizse agree that every dispute arising in connection with these Terms, the Service, or communications from us will be resolved through binding arbitration. Arbitration uses a neutral arbitrator instead of a judge or jury, is less formal than a court proceeding, may allow for more limited discovery than in court, and is subject to very limited review by courts. This agreement to arbitrate disputes includes all claims whether based in contract, tort, statute, fraud, misrepresentation, or any other legal theory, and regardless of whether a claim arises during or after the termination of these Terms. Any dispute relating to the interpretation, applicability, or enforceability of this binding arbitration agreement will be resolved by the arbitrator.
YOU UNDERSTAND AND AGREE THAT, BY ENTERING INTO THESE TERMS, YOU AND REALIZSE ARE EACH WAIVING THE RIGHT TO A TRIAL BY JURY OR TO PARTICIPATE IN A CLASS ACTION.
21.2 Exceptions
Nothing in these Terms will be deemed to waive, preclude, or otherwise limit the right of either party to: (a) bring an individual action in small claims court; (b) pursue an enforcement action through the applicable federal, state, or local agency if that action is available; (c) seek injunctive relief in a court of law in aid of arbitration; or (d) file suit in a court of law to address an intellectual property infringement claim.
21.3 Opt-Out
If you do not wish to resolve disputes by binding arbitration, you may opt out of the provisions of this Section 21 within 30 days after the date that you agree to these Terms by sending an email to support@realizse.com that specifies: your full legal name, the email address associated with your Account on the Service, and a statement that you wish to opt out of arbitration ("Opt-Out Notice"). Once Realizse receives your Opt-Out Notice, this Section 21 will be void and any action arising out of these Terms will be resolved as set forth in Section 26.1 (Governing Law).
21.4 Arbitrator
This arbitration agreement, and any arbitration between us, is subject to the Federal Arbitration Act and will be administered by the American Arbitration Association ("AAA") under its Commercial Arbitration Rules and Mediation Procedures, including, where applicable, the Procedures for Large, Complex Commercial Disputes (collectively, the "AAA Rules"), as modified by these Terms. Notwithstanding the foregoing, if you are an individual using the Service in a personal capacity rather than on behalf of an Allocator, Qualified Off-taker, Client, or other entity, the AAA Consumer Arbitration Rules shall apply in lieu of the Commercial Arbitration Rules. The arbitration shall be conducted by a single arbitrator. The AAA Rules and filing forms are available online at www.adr.org, by calling the AAA at +1-800-778-7879, or by contacting Realizse.
21.5 No Class Actions
YOU AND REALIZSE AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN YOUR OR ITS INDIVIDUAL CAPACITY AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE PROCEEDING. Further, unless both you and Realizse agree otherwise, the arbitrator may not consolidate more than one person's claims, and may not otherwise preside over any form of a representative or class proceeding.
21.6 Modifications to this Arbitration Provision
If Realizse makes any substantive change to this arbitration provision, you may reject the change by sending us written notice within 30 days of the change, in which case your account with Realizse will be immediately terminated and this arbitration provision, as in effect immediately prior to the changes you rejected, will survive.
21.7 Enforceability
If Section 21.5 or the entirety of this Section 21 is found to be unenforceable, or if Realizse receives an Opt-Out Notice from you, then the entirety of this Section 21 will be null and void and, in that case, the exclusive jurisdiction and venue described in Section 26.1 (Governing Law) will govern any action arising out of or related to these Terms.
22. Disclaimers; No Warranties
22.1. THE SERVICE AND ALL MATERIALS AND CONTENT AVAILABLE THROUGH THE SERVICE ARE PROVIDED "AS IS" AND ON AN "AS AVAILABLE" BASIS. WE DO NOT GUARANTEE THE EXISTENCE, QUALITY, OR SAFETY OF ITEMS ADVERTISED ON THE PLATFORM, INCLUDING TAX DEDUCTIONS; THE TRUTH OR ACCURACY OF USERS' CLAIMS OR REPRESENTATIONS REGARDING TAX DEDUCTIONS (INCLUDING WITHOUT LIMITATION, THE VALUE OF ANY TAX DEDUCTION, CREDIT, OR OTHER TAX BENEFIT) OR ANY PROJECT LISTING THAT APPEARS ON THE PLATFORM ("LISTING"); THE ABILITY OF ALLOCATORS TO ALLOCATE TAX DEDUCTIONS; THE ABILITY OF QUALIFIED OFF-TAKERS TO PAY FOR TAX DEDUCTION ALLOCATION AND RELATED FEES; THAT A QUALIFIED OFF-TAKER OR ALLOCATOR WILL ACTUALLY COMPLETE A TRANSACTION; THE ABILITY OF QUALIFIED OFF-TAKERS TO OFFSET THEIR FEDERAL INCOME TAX LIABILITY THROUGH THE ALLOCATION OF TAX DEDUCTIONS (OR THAT ANY SUCH ACTIVITY WILL NOT BE SUBSEQUENTLY CHALLENGED BY THE INTERNAL REVENUE SERVICE).
22.2. YOU ACKNOWLEDGE, AGREE, AND UNDERSTAND THAT THE MARKET FOR ALLOCATED TAX DEDUCTIONS IS AFFECTED BY REGULATORY AND LEGISLATIVE CHANGES, AND THAT RISKS RELATED TO TRANSACTIONS FOR ALLOCATED TAX BENEFITS ARE STILL BEING DISCOVERED AND UNDERSTOOD, INCLUDING THE CIRCUMSTANCES IN WHICH THE INTERNAL REVENUE SERVICE MAY AUDIT, DISPUTE, QUESTION, OR OTHERWISE CHALLENGE ANY SUCH TRANSACTION, EACH OF WHICH COULD HAVE A MATERIALLY ADVERSE FINANCIAL IMPACT ON ANY PARTICIPANT TO SUCH A TRANSACTION, INCLUDING YOU. YOU ACKNOWLEDGE THAT YOU ARE ACCEPTING SUCH RISKS, AND AGREE THAT REALIZSE WILL NOT BE RESPONSIBLE FOR ANY SUCH RISKS OR HAVE ANY LIABILITY TO YOU IN CONNECTION WITH THE FOREGOING. TO THE EXTENT REALIZSE PROVIDES ANY MATERIALS OR OTHER INFORMATION IN THE COURSE OF A TRANSACTION, YOU ACKNOWLEDGE AND AGREE THAT IT HAS BEEN PREPARED FOR GENERAL INFORMATIONAL PURPOSES ONLY AND IS NOT INTENDED TO BE RELIED UPON AS ACCOUNTING, TAX, LEGAL, BUSINESS, OR OTHER PROFESSIONAL ADVICE. WE STRONGLY ENCOURAGE YOU TO CONSULT WITH YOUR ADVISORS, INCLUDING LEGAL COUNSEL, FOR SPECIFIC ADVICE, INCLUDING PRIOR TO PARTICIPATING IN ANY TRANSACTION.
22.3. REALIZSE DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, RELATING TO THE SERVICE AND ALL MATERIALS AND CONTENT AVAILABLE THROUGH THE SERVICE, INCLUDING: (a) ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, QUIET ENJOYMENT, OR NON-INFRINGEMENT; AND (b) ANY WARRANTY ARISING OUT OF COURSE OF DEALING, USAGE, OR TRADE. REALIZSE DOES NOT WARRANT THAT THE SERVICE OR ANY PORTION OF THE SERVICE, OR ANY MATERIALS OR CONTENT OFFERED THROUGH THE SERVICE, WILL BE UNINTERRUPTED, SECURE, OR FREE OF ERRORS, VIRUSES, OR OTHER HARMFUL COMPONENTS, AND REALIZSE DOES NOT WARRANT THAT ANY OF THOSE ISSUES WILL BE CORRECTED.
22.4. REALIZSE DOES NOT, EITHER THROUGH THESE TERMS, OR IN ANY OTHER FORUM OR BY ANY OTHER MEANS, PURPORT TO: (A) MAKE A COMMITMENT TO EXTEND CREDIT OR MAKE A LOAN OR OTHERWISE FUND THE ALLOCATION OF TAX DEDUCTIONS; (B) PROVIDE LEGAL OPINIONS OR LEGAL ADVICE, INCLUDING WITH RESPECT TO TAX DEDUCTIONS OR OTHER TAX BENEFITS THAT MAY BE AVAILABLE IN CONNECTION WITH ANY PROJECT; OR (C) PROVIDE ESCROW SERVICES FOR DOCUMENTS OR FUNDS. REALIZSE MAY FROM TIME TO TIME MAKE REFERRALS TO USERS ON THE PLATFORM FOR PROVIDERS OF PROFESSIONAL SERVICES IN CONNECTION WITH TRANSACTIONS. REALIZSE SHALL ACT IN GOOD FAITH WHEN MAKING ANY SUCH REFERRALS BUT SHALL OTHERWISE HAVE NO LIABILITY OR OBLIGATIONS RELATED TO ANY SUCH REFERRAL, INCLUDING FOR THE PERFORMANCE OF SERVICES BY ANY SUCH REFERRED PARTY.
22.5. THE RELATIONSHIP BETWEEN YOU AND REALIZSE SHALL BE ONE OF INDEPENDENT CONTRACTORS, NOT AGENTS, PARTNERS, OR JOINT VENTURERS, AND YOU AGREE THAT THE SERVICES TO BE PERFORMED HEREUNDER BY REALIZSE WILL NOT BE CONSIDERED ADVISORY SERVICES OF ANY NATURE OR RESPECT, AND THAT REALIZSE IS NOT AN ADVISOR, BROKER, DEALER, OR FIDUCIARY, AND IT DOES NOT OWE ANY FIDUCIARY OR SIMILAR DUTIES TO YOU IN PERFORMING THE SERVICES. PLEASE NOTE THAT IN PERFORMING THE SERVICES REALIZSE MAY INTERACT WITH MANY PARTIES, INCLUDING MULTIPLE BUYERS OR MULTIPLE SELLERS, IN RESPECT OF A TRANSACTION, AND AS A RESULT MAY POSSESS INFORMATION AND TAKE RELATED ACTIONS THAT CONFLICT WITH THE INTERESTS OF ANOTHER PARTY. YOU ACKNOWLEDGE AND AGREE THAT YOU ARE USING ALL SUCH INFORMATION AT YOUR OWN DISCRETION AND AT YOUR OWN RISK.
22.6. YOU HEREBY ACKNOWLEDGE AND AGREE THAT, UNLESS EXPLICITLY AGREED TO BETWEEN YOU AND ANY RELEVANT TRANSACTING PARTY, YOU WILL NOT BE ENTITLED TO ANY EXCLUSIVITY RIGHTS IN RESPECT OF A LISTING OR TRANSACTION, AND SUCH RELEVANT TRANSACTION PARTY MAY BE DISCUSSING OR PURSUING ALTERNATIVE TRANSACTIONS WITH OTHER PARTIES, WHETHER VIA THE PLATFORM OR OTHERWISE, AND THAT REALIZSE MAY BE INVOLVED IN THE FACILITATION OF SUCH ALTERNATE TRANSACTIONS. Realizse does not disclaim any warranty or other right that Realizse is prohibited from disclaiming under applicable law.
22-A. Customer Representations and Warranties Regarding Customer-Uploaded Content
22-A.1 General Representations and Warranties
Customer represents and warrants to Realizse, as of the Effective Date and on a continuing basis throughout the Term, that:
(a) Authority and Legal Right. Customer has full legal right, title, license, authority, and all necessary permissions and consents to upload, submit, store, share, process, and otherwise make available on the Platform all Customer-Uploaded Content, including without limitation the right to grant Realizse the limited rights and licenses to Customer-Uploaded Content set forth in this Agreement;
(b) No Conflicting Rights. The upload, submission, storage, processing, or other use of Customer-Uploaded Content on the Platform does not and will not: (i) infringe, misappropriate, or otherwise violate the intellectual property rights, privacy rights, contractual rights, or any other proprietary or legal rights of any third party; (ii) breach any agreement, obligation, or duty owed by Customer or any third party to any other person or entity; or (iii) violate any applicable law, regulation, or governmental order;
(c) Multi-Party Data. To the extent Customer-Uploaded Content includes data, documents, records, or other materials that were created by, belong to, or are subject to claims by any third party — including without limitation co-owners, co-developers, certifiers, auditors, contractors, subcontractors, licensors, or any other affiliated or contributing party — Customer has obtained all required authorizations, consents, licenses, and releases from such third parties necessary to upload such materials to the Platform and to authorize Realizse to process and store such materials in accordance with this Agreement;
(d) No Misrepresentation. All Customer-Uploaded Content is accurate and complete in all material respects as of the time of upload, and Customer has not knowingly omitted any information that would be material to Realizse's processing of such content or to any third party's rights therein;
(e) Compliance with Law. Customer's upload and use of Customer-Uploaded Content on the Platform complies and will comply with all applicable federal, state, local, and foreign laws and regulations, including without limitation applicable data protection and privacy laws, export control laws, and any sector-specific regulations applicable to Customer's business or industry; and
(f) Authorized Users. All individuals and entities uploading Customer-Uploaded Content to the Platform on Customer's behalf — including Customer's employees, contractors, agents, authorized users, and any third parties acting at Customer's direction — have been duly authorized by Customer to do so, and Customer has ensured that such individuals and entities are bound by terms no less protective of Realizse's rights than those set forth in this Agreement.
22-A.2 Specific Warranties Regarding Digital Passport Content
Without limiting the generality of Section 22-A.1, Customer further represents and warrants that:
(a) Project Documentation. All project documentation, certifications, engineering studies, energy models, tax forms, compliance records, and other materials uploaded to a Digital Passport have been lawfully obtained by Customer and may be lawfully submitted for the purposes for which Customer is using the Platform, including without limitation for purposes of tax credit and deduction compliance (including Section 179D), insurance underwriting, and regulatory reporting;
(b) Certification and Compliance Data. Where Customer-Uploaded Content includes data or documentation prepared by or belonging to a third-party certifier, auditor, engineer, or other professional, Customer has obtained such professional's authorization to upload and incorporate such data into the Platform, or Customer's contractual or legal relationship with such professional grants Customer the right to do so;
(c) No Disputed Ownership. To Customer's knowledge, at the time of upload, no third party has asserted or threatened any claim disputing Customer's right to control, submit, or use any Customer-Uploaded Content in the manner contemplated by this Agreement. Customer shall promptly notify Realizse in writing if Customer becomes aware of any such claim or dispute after upload;
(d) Sensitive and Regulated Data. If Customer-Uploaded Content includes any personally identifiable information, protected health information, financial data, export-controlled technical data, or other categories of data subject to heightened legal protections, Customer has complied with all applicable legal requirements governing the collection, use, and disclosure of such data prior to uploading it to the Platform; and
(e) Affiliated Party Uploads. Where documents are uploaded to the Platform by certifiers, auditors, contractors, or other affiliated parties on a project associated with Customer's account, Customer acknowledges and agrees that by permitting or requesting such uploads, Customer is representing that it has secured all necessary rights and authorizations for such uploads and that such affiliated parties are acting under Customer's authority and direction for purposes of this Agreement.
22-A.3 Realizse's Reliance
Customer acknowledges and agrees that Realizse will rely on the representations and warranties in this Section 22-A without independent investigation or verification. Realizse shall have no obligation to review, audit, or confirm the accuracy of Customer's representations with respect to any Customer-Uploaded Content, and Realizse's acceptance or processing of Customer-Uploaded Content shall not constitute any representation by Realizse regarding the ownership of, rights to, or lawfulness of such content.
22-A.4 Notice of Breach
Customer shall promptly notify Realizse in writing — and in no event later than five (5) business days after Customer becomes aware — of any facts or circumstances that would cause any representation or warranty in this Section 22-A to be or become untrue, inaccurate, or misleading in any material respect. Such notice shall describe the nature of the issue and the Customer-Uploaded Content affected, and Customer shall cooperate with Realizse in determining the appropriate course of action, which may include removal or suspension of access to the affected content.
22-A.5 Survival
The representations and warranties in this Section 22-A shall survive the expiration or termination of this Agreement with respect to Customer-Uploaded Content uploaded during the Term.
23. Limitation of Liability
23.1 Exclusion of Consequential Damages
TO THE FULLEST EXTENT PERMITTED BY LAW, NEITHER PARTY NOR ITS AFFILIATES, OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, OR LICENSORS (COLLECTIVELY, A PARTY'S "RELATED PERSONS") SHALL BE LIABLE TO THE OTHER PARTY OR ITS RELATED PERSONS FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES (INCLUDING DAMAGES FOR LOSS OF PROFITS, REVENUE, GOODWILL, DATA, OR ANY OTHER INTANGIBLE LOSS) ARISING OUT OF OR RELATING TO THESE TERMS, THE SERVICE, OR THE INABILITY TO USE THE SERVICE, WHETHER BASED ON WARRANTY, CONTRACT, TORT (INCLUDING NEGLIGENCE), STATUTE, OR ANY OTHER LEGAL THEORY, AND WHETHER OR NOT THE LIABLE PARTY HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGE.
FOR THE AVOIDANCE OF DOUBT, THE FOREGOING LIMITATION EXTENDS TO LOSSES IN CONNECTION WITH TAX DEDUCTIONS IDENTIFIED OR ALLOCATED ON THE PLATFORM. NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR ANY LOSS IN CONNECTION WITH TAX DEDUCTIONS OR OTHER TAX BENEFITS, INCLUDING WITHOUT LIMITATION DAMAGES FROM RECAPTURE, LOSS OF PROFITS, OR REDUCTION IN VALUE OF TAX DEDUCTIONS COMPARED TO THE VALUE EXPECTED.
23.2 Aggregate Liability Cap
TO THE FULLEST EXTENT PERMITTED BY LAW, THE AGGREGATE LIABILITY OF EACH PARTY AND ITS RELATED PERSONS TO THE OTHER PARTY FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THESE TERMS, THE SERVICE, OR THE INABILITY TO USE THE SERVICE, WHETHER IN CONTRACT, TORT, OR OTHERWISE, SHALL BE LIMITED AS FOLLOWS:
(a) General Cap. For all claims not falling within subsections (b) or (c) below, the aggregate liability of each party and its Related Persons shall not exceed one hundred percent (100%) of the total fees actually paid or payable by Client to Realizse under these Terms in the twelve (12) months immediately preceding the first event giving rise to the applicable claim (the "Fee Reference Amount"), or, if the Fee Reference Amount is less than ten thousand U.S. dollars ($10,000.00), then ten thousand U.S. dollars ($10,000.00) (the "General Cap").
(b) Enhanced Cap. For claims arising from any of the following, the aggregate liability of each party and its Related Persons shall not exceed two times (2×) the Fee Reference Amount, or, if such amount is less than twenty thousand U.S. dollars ($20,000.00), then twenty thousand U.S. dollars ($20,000.00) (the "Enhanced Cap"):
(i) a material breach of the confidentiality obligations set forth in Section 20;
(ii) a party's infringement or misappropriation of the other party's intellectual property rights;
(iii) a Security Incident (as defined in Section 14.6(d)) attributable to a party's failure to maintain the security measures required by these Terms; or
(iv) a party's breach of its indemnification obligations under Section 24, to the extent such breach relates to a matter described in clauses (i) through (iii) above.
(c) Uncapped Liability. Nothing in these Terms shall limit or exclude the liability of either party for:
(i) fraud or intentional misrepresentation;
(ii) willful misconduct or gross negligence;
(iii) death or personal injury caused by negligence;
(iv) a party's obligations under Section 24 (Indemnification) with respect to third-party claims arising from matters described in Section 23.2(c)(i) or (ii);
(v) Client's payment obligations for fees due under these Terms; or
(vi) any other liability that cannot be excluded or limited by applicable law.
(d) Claim Aggregation. Where multiple claims arise from the same underlying event or series of related events, such claims shall be treated as a single claim for purposes of applying the caps set forth in this Section 23.2. The applicable cap shall be determined by the nature of the highest-tier claim asserted in connection with such event.
23.3 Sub-Processor Limitation
The Service relies on third-party infrastructure and service providers (as identified in Section 13). Neither party shall be liable for outages, data loss, or service interruptions caused by the acts or omissions of Sub-Processors, to the extent that such events are beyond the affected party's reasonable control; provided, however, that Realizse shall remain responsible for exercising commercially reasonable diligence in selecting and monitoring Sub-Processors.
23.4 Force Majeure
Neither party shall be liable for failure to perform its obligations under these Terms due to causes beyond its reasonable control, including natural disasters, acts of government, pandemics, epidemics, war, terrorism, civil unrest, labor disputes, internet or telecommunications failures, utility outages, or failures of third-party service providers (each, a "Force Majeure Event"). The affected party shall provide prompt written notice to the other party of any Force Majeure Event and shall use commercially reasonable efforts to mitigate its effects. If a Force Majeure Event prevents performance for more than sixty (60) consecutive days, either party may terminate these Terms upon written notice.
23.5 Essential Basis of the Bargain
EACH PROVISION OF THESE TERMS THAT PROVIDES FOR A LIMITATION OF LIABILITY, DISCLAIMER OF WARRANTIES, OR EXCLUSION OF DAMAGES IS INTENDED TO AND DOES ALLOCATE THE RISKS BETWEEN THE PARTIES UNDER THESE TERMS. THIS ALLOCATION IS AN ESSENTIAL ELEMENT OF THE BASIS OF THE BARGAIN BETWEEN THE PARTIES. EACH OF THESE PROVISIONS IS SEVERABLE AND INDEPENDENT OF ALL OTHER PROVISIONS OF THESE TERMS. THE LIMITATIONS IN THIS SECTION 23 SHALL APPLY EVEN IF ANY LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE.
24. Indemnification
24.1 Realizse Indemnification
Realizse shall defend, indemnify, and hold harmless Customer and its officers, directors, employees, agents, and permitted successors and assigns (collectively, "Customer Indemnitees") from and against any third-party claims, actions, suits, proceedings, losses, liabilities, damages, costs, and expenses (including reasonable attorneys' fees and court costs) (collectively, "Losses") arising out of or relating to:
(a) IP Infringement. Any claim that the Platform, as provided by Realizse and used by Customer in accordance with these Terms and applicable documentation, infringes or misappropriates any third-party patent, copyright, trademark, trade secret, or other intellectual property right;
(b) Material Breach. Realizse's material breach of these Terms, including its data protection obligations under Sections 12, 13, 14, and 15;
(c) Gross Negligence or Willful Misconduct. The gross negligence or willful misconduct of Realizse or its employees, agents, or contractors in connection with the performance of its obligations under these Terms; and
(d) Security Incidents. Any Security Incident (as defined in Section 14.6(d)) to the extent caused by Realizse's failure to implement or maintain the security measures required by Section 14.
Exclusions. Realizse shall have no indemnification obligation under this Section 24.1 to the extent Losses arise out of or relate to:
(i) Customer's breach of these Terms;
(ii) Customer's use of the Platform in a manner not authorized by these Terms or applicable documentation;
(iii) modifications to the Platform made by or on behalf of Customer without Realizse's prior written consent;
(iv) any matter for which Customer is obligated to indemnify Realizse under Section 24.2;
(v) Customer's combination, operation, or use of the Platform with any software, hardware, data, or service not provided or authorized by Realizse, to the extent the claim would not have arisen but for such combination; or
(vi) Customer's continued use of the Platform after Realizse has provided written notice of an alleged infringement and a commercially reasonable non-infringing alternative.
(e) IP Infringement Remediation. If the Platform becomes, or in Realizse's reasonable opinion is likely to become, the subject of an infringement claim under Section 24.1(a), Realizse may, at its sole option and expense: (i) procure for Customer the right to continue using the Platform; (ii) modify or replace the infringing component of the Platform so that it becomes non-infringing without material diminution in functionality; or (iii) if neither (i) nor (ii) is commercially practicable, terminate the affected subscription upon written notice and refund to Customer a pro-rata portion of any prepaid fees for the unexpired portion of the then-current subscription term.
24.2 Customer Indemnification
Customer shall defend, indemnify, and hold harmless Realizse and its officers, directors, employees, affiliates, agents, successors, and assigns (collectively, "Realizse Indemnitees") from and against any and all Losses arising out of or relating to:
(a) Customer Data and Digital Passport Content. Any claim, dispute, or proceeding arising out of or relating to: (i) the ownership of, title to, rights in, or lawful control over any Customer-Uploaded Content; (ii) Customer's alleged lack of authority, license, or legal right to upload, submit, share, or otherwise process Customer-Uploaded Content on the Platform; (iii) Customer's alleged violation of any third party's intellectual property rights, privacy rights, contractual rights, or any other proprietary or legal rights in connection with Customer-Uploaded Content; or (iv) any dispute between Customer and any co-owner, co-developer, licensor, contractor, subcontractor, affiliated party, or other person or entity regarding rights to or obligations associated with Customer-Uploaded Content;
(b) Breach of Customer Representations. Any breach of Customer's representations and warranties under Section 22-A (Customer Representations and Warranties Regarding Customer-Uploaded Content);
(c) Misuse of the Platform. Any claim arising out of or relating to Customer's use of the Platform in violation of these Terms, applicable law, or any regulatory requirement applicable to Customer or Customer's industry;
(d) Tax Deduction Disputes. Any claim, dispute, or proceeding arising out of or relating to the validity, accuracy, value, or tax treatment of any Tax Deduction identified or allocated on or through the Platform, including any IRS audit, recapture event, or challenge to a claimed tax benefit, except to the extent directly caused by a material defect in the Platform's calculation or documentation functionality as described in the applicable documentation;
(e) Unauthorized Signing and Credential Mismanagement. Any claim arising from or related to: (i) any claim that an individual who executed a document through the Platform lacked authority to bind Customer; (ii) any internal governance dispute regarding the authorization of a signing; or (iii) any failure by Customer to maintain appropriate access controls over Platform credentials, including failure to promptly disable accounts of former employees or unauthorized users; and
(f) Customer's Agents. Any acts or omissions of Customer's agents, employees, contractors, authorized users, or any third parties acting on Customer's behalf in connection with the Platform, to the same extent as if such acts or omissions were those of Customer directly.
24.3 Indemnification Procedure
(a) Notice. The Indemnified Party shall promptly notify the Indemnifying Party in writing of any claim for which indemnification is sought under this Section 24, provided that failure to provide prompt notice shall not relieve the Indemnifying Party of its obligations except to the extent the Indemnifying Party is actually and materially prejudiced by such failure.
(b) Control of Defense. The Indemnifying Party shall have sole control of the defense and settlement of any indemnified claim, provided that:
(i) the Indemnifying Party shall not settle any claim in a manner that imposes any obligation, restriction, admission of liability, or financial burden on the Indemnified Party without the Indemnified Party's prior written consent, not to be unreasonably withheld, conditioned, or delayed;
(ii) the Indemnified Party may participate in the defense of any claim with its own counsel and at its own expense; and
(iii) if the Indemnifying Party fails to assume the defense of a claim within fifteen (15) days of receiving notice, the Indemnified Party may assume the defense at the Indemnifying Party's expense.
(c) Cooperation. The Indemnified Party shall provide the Indemnifying Party with reasonable cooperation and assistance in connection with the defense of any indemnified claim, at the Indemnifying Party's expense.
24.4 Mitigation
Each party shall take commercially reasonable steps to mitigate any Losses for which the other party may have an indemnification obligation under this Section 24.
24.5 Relationship to Liability Caps
The indemnification obligations set forth in this Section 24 are subject to the limitations of liability set forth in Section 23, except that: (a) indemnification obligations arising from matters described in Section 23.2(c) (Uncapped Liability) shall not be subject to the General Cap or Enhanced Cap; and (b) the Enhanced Cap shall apply to indemnification obligations arising from matters described in Section 23.2(b).
24.6 Sole Remedy for Third-Party Claims
Subject to Section 23 (Limitation of Liability), the indemnification obligations set forth in this Section 24 shall constitute each party's sole and exclusive remedy with respect to third-party claims of the type described herein.
25. Term, Termination, and Modification
25.1 Subscription Fee; Annual Term
Access to the Realizse Platform is provided on an annual subscription basis. The applicable Annual Subscription Fee shall be as mutually agreed upon in writing between Customer and Realizse (including as set forth in an Order Form, Statement of Work, or other executed agreement between the parties) (each, a "Customer Agreement"). No fee is due without a signed Order Form or other Customer Agreement specifying it. All fees are quoted and payable in U.S. dollars unless otherwise specified in the applicable Customer Agreement.
25.2 Fee Determination; Project-Based Pricing
Annual Subscription Fees are determined on a project-by-project basis and shall reflect the Customer's specific project size, scope, and operational requirements, including but not limited to:
(a) project size and type, such as building floor area, number of buildings, installed or nameplate capacity (in kilowatts, megawatts, or other applicable unit), number of certifications or certification packages, and number of Allocations or Transactions;
(b) the number, type, and complexity of Projects or Digital Passports to be created, maintained, or verified through the Platform;
(c) the volume and nature of supporting documentation, third-party data integrations, or compliance workflows required; and
(d) the number of authorized Users, stakeholder access tiers, or organizational entities to be onboarded.
Realizse reserves the right to adjust the Annual Subscription Fee at renewal to reflect material changes in the Customer's project portfolio, asset count, or platform utilization, subject to reasonable prior notice as set forth in Section 25.6.
25.3 Minimum Fee; Setup and Asset Creation
Notwithstanding any other provision of this Section 25, all subscriptions are subject to a Minimum Fee covering Platform setup, account configuration, and initial asset creation services ("Onboarding Services"). The Minimum Fee is non-refundable and shall be due and payable upon execution of the applicable Customer Agreement or Order Form. The Minimum Fee will be specified in the Customer Agreement and shall reflect the scope of Onboarding Services required. The Minimum Fee may be applied as a credit against the Annual Subscription Fee at Realizse's sole discretion and as set forth in the Customer Agreement.
25.4 Additional and Variable Fees
Customer acknowledges that fees in addition to the Annual Subscription Fee may apply based on Customer's requirements and platform utilization. Such additional fees may include, without limitation:
(a) Digital Passport Issuance Fees — per-asset fees for the creation, cryptographic verification, and issuance of Digital Passports;
(b) Tax Incentive Compliance Services Fees — fees for tax credits (ITC, PTC, 45Y, 48E), Section 179D deductions, or other applicable tax incentive compliance workflows, including document verification, audit support, or regulatory filing assistance;
(c) Tax Credit Insurance Integration Fees — fees associated with facilitation of or integration with third-party tax credit insurance products or providers;
(d) Data Integration and API Fees — fees for custom integrations, API access beyond standard entitlements, or third-party data source connections;
(e) Enhanced Support and Professional Services Fees — fees for dedicated customer success, custom reporting, technical implementation support, or consulting services beyond the standard support tier; and
(f) Overage Fees — fees for utilization exceeding the contracted project count, asset volume, user count, or storage limits as set forth in the Customer Agreement.
All additional fees shall be disclosed in the applicable Customer Agreement, Order Form, or separately executed Statement of Work.
25.5 Invoicing and Payment
Unless otherwise specified in the Customer Agreement:
(a) Annual Subscription Fees shall be invoiced annually in advance, on or about the commencement date of each subscription term;
(b) Setup, Minimum, and Onboarding Fees shall be invoiced upon execution of the Customer Agreement;
(c) Additional and variable fees shall be invoiced monthly in arrears or as otherwise specified in the applicable Order Form or Statement of Work;
(d) All invoices are due and payable within thirty (30) days of the invoice date unless otherwise agreed in writing;
(e) Amounts not paid when due shall accrue interest at the lesser of one and one-half percent (1.5%) per month or the maximum rate permitted by applicable law, from the due date until paid in full; and
(f) Customer shall be responsible for all reasonable costs of collection, including attorneys' fees, incurred by Realizse in collecting overdue amounts.
25.6 Fee Adjustments; Renewal Pricing
Realizse may adjust fees applicable to a renewal subscription term by providing Customer with written notice no less than sixty (60) days prior to the end of the then-current subscription term. Customer's continued use of the Platform following the commencement of a renewal term shall constitute acceptance of the adjusted fees. If Customer objects to a fee adjustment, Customer may elect not to renew the subscription in accordance with Section 25.10 (Termination).
25.7 Taxes
All fees are exclusive of applicable federal, state, local, and foreign taxes, levies, duties, and similar governmental assessments, including sales, use, value-added, and withholding taxes (collectively, "Taxes"). Customer is responsible for paying all Taxes associated with its subscription and use of the Platform, excluding taxes based on Realizse's net income or property. If Realizse is required to collect or remit Taxes, such Taxes will be added to the applicable invoice and paid by Customer unless Customer provides Realizse with a valid tax exemption certificate.
25.8 Disputed Invoices
Customer must notify Realizse in writing of any good-faith dispute regarding an invoice within fifteen (15) days of the invoice date, identifying the specific charges disputed and the basis for the dispute. Customer shall pay all undisputed amounts when due. The parties agree to work in good faith to resolve any invoice dispute within thirty (30) days of Realizse's receipt of written notice of the dispute. Failure to timely notify Realizse of a dispute shall constitute Customer's acceptance of the invoice.
25.9 Suspension for Non-Payment
Without limiting any other rights or remedies available to Realizse, if Customer's account is overdue by more than thirty (30) days (and Customer has not disputed the invoice in accordance with Section 25.8), Realizse may, upon written notice, suspend Customer's access to the Platform until all overdue amounts are paid in full. Realizse shall not be liable for any damages, losses, or interruptions arising from a suspension due to non-payment.
25.10 Termination
If you violate any provision of these Terms, then Realizse may immediately suspend your access to the Service. In addition, Realizse may, at its sole discretion, terminate these Terms or your Account, or suspend or terminate your access to the Service, if: (a) you are in breach of these Terms and such breach remains uncured for thirty (30) days after receiving notice; or (b) your relationship with the entity on whose behalf you are using the Service has been terminated. Either party may terminate these Terms if the other party becomes insolvent, files for bankruptcy, or ceases operations. You may terminate your Account and these Terms with 30 days notice at any time by contacting customer service at support@realizse.com.
Realizse may terminate these Terms for convenience upon sixty (60) days' prior written notice to Client, provided that Realizse shall (i) continue to provide the Service through the end of the notice period, (ii) make available the data export described in Section 15.6 during the notice period, and (iii) refund to Client a pro-rata portion of any prepaid Annual Subscription Fees attributable to the period following the effective date of termination.
25.11 Effect of Termination
Upon termination of these Terms:
(a) Your license rights will terminate and you must immediately cease all use of the Service. You will no longer be authorized to access your Account or the Service.
(b) Realizse will retain compliance records (see Section 15.1) for the retention period set out in Section 15.1, with access revoked.
(c) For Client Data other than compliance records, Realizse will retain data for a transition period of ninety (90) days following termination, during which the Client may request data export in accordance with Section 15.6 (Data Portability).
(d) After the transition period, Realizse will delete Client Data other than compliance records to the extent technically feasible, subject to the deletion limitations set out in Section 15.3.
(e) Data stored at Sub-Processors (including verifiable credentials at Spherity) is subject to the Sub-Processor's retention policies and may not be deletable.
(f) You are responsible for retaining copies of any User Content you Posted to the Service since upon termination of your Account, you may lose access rights to any User Content you Posted to the Service.
25.12 Business Continuity Provisions
(a) Source Code Escrow. Upon the Client's written request and at the Client's expense, Realizse may, at its discretion, enter into a three-party source code escrow agreement with a reputable escrow agent mutually agreed upon by the parties. Any such escrow agreement is separate from these Terms and sets out the escrowed materials, the schedule for updating them, and the conditions for their release.
(b) Escrow Release Conditions. Where an escrow agreement under Section 25.12(a) is in place, the escrowed materials shall be released to the Client upon the occurrence of any of the following triggering events, which also apply for purposes of Sections 25.12(d) and 25.12(e) whether or not an escrow agreement is in place:
(i) Realizse files for bankruptcy, makes a general assignment for the benefit of creditors, or has a receiver or trustee appointed for its assets;
(ii) Realizse ceases substantially all operations related to the Service and fails to designate a successor operator within sixty (60) days;
(iii) Realizse fails to cure a material breach of its data availability or portability obligations under this Agreement within the cure period specified in Section 25.10.
(c) Self-Hosting Capability. Where an escrow agreement under Section 25.12(a) is in place, the escrowed materials shall include deployment documentation sufficient for a competent engineering team to deploy the Platform.
(d) Data Export Survival. Independent of and in addition to the escrow provisions, the Client retains the right to export all Client Data at any time during the term of the Agreement as described in Section 15.6 (Data Portability). Upon any triggering event described in Section 25.12(b), the data export right shall survive for a minimum of one hundred eighty (180) days, during which Realizse (or its successor, trustee, or escrow agent) shall maintain read-only access to Client Data.
(e) Decentralized Identifier Continuity. Realizse acknowledges that Verifiable Credentials issued through the Service reference Realizse's domain-linked Decentralized Identifier (DID). In the event of a triggering event under Section 25.12(b), Realizse shall cooperate with the Client to effectuate transfer or reassignment of the relevant DID resolution records (including DID documents and associated verification methods) to the Client or its designee, to the extent technically feasible and consistent with the applicable DID method specification. Where an escrow agreement under Section 25.12(a) is in place, Realizse shall include the DID transfer procedures in the escrowed deployment documentation.
(f) Insurance. Realizse shall use commercially reasonable efforts to maintain errors and omissions insurance or technology professional liability insurance in amounts appropriate for a company of its size and stage, and shall disclose its current coverage status to the Client upon written request.
25.13 Survival
The following provisions shall endure beyond the conclusion of this Agreement: Sections 1 (Definitions), 6 (Ownership; Proprietary Rights), 8 (Referrals; Non-Circumvention), 9 (Your Warranties), 11 (Data Ownership and Licensing), 15 (Data Retention and Deletion), 16 (Electronic Signatures), 20 (Confidentiality), 21 (Dispute Resolution and Arbitration), 22 and 22-A (Disclaimers; Customer Representations and Warranties), 23 (Limitation of Liability), 24 (Indemnification), 25.11 (Effect of Termination), 25.12 (Business Continuity Provisions), 25.13 (Survival), and 26 (General Provisions), along with any other terms which by their nature or express intent are meant to persist.
25.14 Modification of Terms
We may, from time to time, change these Terms. Revisions will be effective 30 days after we provide notice to you of the revisions, which may be done via email or through an acknowledgement on the Platform. To the extent any revisions directly conflict with any separate agreement that you have previously made with Realizse related to the Service and the Platform outside of the standard version of these Terms (including via an addendum to these Terms, a cloud services agreement, or a platform services agreement), such separate agreement will continue to govern and control in the case of any conflict, except to the extent such revisions are necessary to comply with law. If you do not accept such revisions and notify Realizse of your rejection thereof within such notice period, Realizse reserves the right to discontinue the Service, though will make commercially reasonable efforts to agree with you on arrangements whereby you may continue to use the Service and the Platform without the effect of such revisions, including if you are participating in any Projects or Transactions that were initiated and remain in process prior to you receiving notice of such revisions.
26. General Provisions
26.1 Governing Law
These Terms, and the rights and obligations of the parties, shall be construed, interpreted, and enforced pursuant to the laws of the State of Delaware, and exclusive venue in any and all actions existing under these Terms shall be laid in the federal and state courts located in the State of Delaware.
26.2 Privacy Policy
Please read the Privacy Policy carefully for information relating to our collection, use, storage, and disclosure of your personal information. The Realizse Privacy Policy is incorporated by this reference into, and made a part of, these Terms.
26.3 Consent to Electronic Communications
By using the Service, you consent to receiving certain electronic communications from us as further described in our Privacy Policy. You agree that any notices, agreements, disclosures, or other communications that we send to you electronically will satisfy any legal communication requirements, including that those communications be in writing.
26.4 Communications
We may send you emails concerning our products and services, as well as those of third parties. You may opt out of promotional emails by following the unsubscribe instructions in the promotional email itself.
26.5 Notices
All notices under these Terms shall be in writing and delivered to the addresses or email addresses specified in the subscription agreement or, in the absence of such, to the email address associated with the Client's Account.
26.6 Assignment
Neither party may assign or transfer these Terms or any of its rights or obligations hereunder, in whole or in part, by operation of law or otherwise, without the prior written consent of the other party, which consent shall not be unreasonably withheld, conditioned, or delayed; provided, however, that either party may assign these Terms without the other party's consent in connection with a merger, acquisition, corporate reorganization, change of control, or sale of all or substantially all of its assets, upon written notice to the other party. Any purported assignment or transfer in violation of this Section 26.6 shall be null and void. Subject to the foregoing, these Terms shall bind and inure to the benefit of the parties and their respective permitted successors and assigns.
26.7 Severability
If any part of these Terms is held to be invalid or unenforceable, then the unenforceable part will be given effect to the greatest extent possible, and the remaining parts will remain in full force and effect.
26.8 Entire Agreement
These Terms, together with any applicable subscription agreement, order form, Privacy Policy, Data Processing Addendum, and any documents incorporated by reference, constitute the entire and exclusive understanding and agreement between the parties with respect to the subject matter hereof.
26.9 Waiver
The failure of either party to enforce any provision of these Terms shall not constitute a waiver of that provision or any other provision.
26.10 Platform Maintainer Access
(a) General Restriction. Realizse and its authorized personnel shall not access, view, retrieve, copy, or otherwise process Client Data except as expressly permitted in this Section 26.10.
(b) Permitted Access. Realizse may access Client Data solely under the following circumstances:
(i) At Client's Request. Where a Client or authorized User submits a written request (including via email to support@realizse.com or through the Platform's designated support channel) for Realizse to investigate, diagnose, or resolve a technical issue affecting Client's use of the Service, Realizse personnel may access the minimum Client Data reasonably necessary to fulfill such request;
(ii) With Client's Permission. Where, in the course of providing technical support or investigating an issue, Realizse determines that access to additional Client Data is necessary to resolve the issue, Realizse shall request Client's permission before accessing such data, and Client may grant or withhold such permission at its sole discretion;
(iii) Platform Operations. Where access is reasonably necessary to maintain the security, integrity, or availability of the Service — including incident response, infrastructure maintenance, and data migration — provided that such access is limited to the minimum scope and duration necessary and does not involve review of the substantive content of Client Data except as incidental to the operational task;
(iv) Legal Obligation. Where access is required to comply with applicable law, regulation, subpoena, or court order, subject to the notice obligations in Section 20.5 (Compelled Disclosure); and
(v) Account Setup and Verification. Where access is needed for account setup and verification, meaning creating and maintaining a Client's Organization, Users, and roles and verifying Client information, provided that such access is limited to the records needed for that purpose.
(c) Personnel Restrictions. Access to Client Data under this Section 26.10 is restricted to Realizse personnel who have a legitimate need to access such data in connection with one of the purposes described in Section 26.10(b). Realizse shall maintain appropriate access controls to enforce this restriction.
(d) No Ongoing Surveillance. Realizse shall not monitor, review, or analyze the substantive content of Client Data on a routine or ongoing basis. Automated platform monitoring (including log aggregation, performance metrics, error tracking, and security event detection) that processes metadata or system-level information does not constitute access to Client Data for purposes of this Section 26.10.
(e) Audit Trail. Realizse shall maintain a log of each instance of access to Client Data under this Section 26.10, including the identity of the accessing personnel, the date and time of access, the purpose, and the scope of data accessed. Such logs shall be retained for a minimum of one (1) year and shall be made available to Client upon reasonable written request.
(f) Tax Return Information. Where Client Data includes tax return information protected by 26 U.S.C. §7216, such as a Form 7205 prepared through the Platform, Realizse personnel located outside the United States shall not access it unless the taxpayer has first given written consent under 26 C.F.R. §301.7216-3.
26.11 Public Entities
(a) Scope. "Public Entity" means a federal, state, or local government body or agency, a public school district, a public college or university, or any other governmental entity or political subdivision. For purposes of these Terms, "Organization" includes a registered tenant representing a Public Entity. This Section 26.11 applies to an Organization that is a Public Entity, whether it is a Client or a Participating Organization, and to its Users when they act for it. It does not make any otherwise inapplicable provision apply to a Participating Organization. Where this Section 26.11 conflicts with any other provision of these Terms, this Section 26.11 controls.
(b) Disputes. Section 21 (Dispute Resolution and Arbitration) does not apply. The parties will first try to resolve any dispute through good-faith negotiation for at least thirty (30) days after written notice of the dispute, and may then agree to non-binding mediation. This paragraph does not delay any mandatory claims procedure, filing deadline, or application for urgent interim relief permitted by applicable law. Where law applicable to the Public Entity requires a particular process for claims against it, that process applies.
(c) Governing Law and Venue. Section 26.1 does not apply. For a Public Entity other than a federal entity, these Terms are governed by the laws of its state of organization, with venue in a court of competent jurisdiction in that state, except as applicable law otherwise requires. For a federal entity, United States federal law governs, and claims proceed before the court or tribunal that federal law designates.
(d) Indemnification and Immunity. The Public Entity's obligations under Section 24.2 apply only to the extent permitted by the constitution and laws that apply to it. Nothing in these Terms waives the sovereign or governmental immunity of the Public Entity or of its officers or employees.
(e) Public Records. A disclosure that public records laws require of the Public Entity is a disclosure required by law under Section 20.5, and Section 20.5's notice and cooperation steps apply to the extent those laws permit.
(f) Separate Agreements. A separately executed written agreement between Realizse and a Public Entity covering the Service controls over these Terms where the two conflict, whether it was made before or after the Public Entity accepted these Terms, except as necessary to comply with law.
27. API-Specific Terms
27.1 API Access
API access is included with the Client's subscription and is subject to these Terms. All user API requests must be authenticated using valid JWT tokens issued through the identity provider.
27.2 Rate Limits
The API enforces the following rate limits: sustained rate of 50 requests per second; burst limit of 100 concurrent requests. Requests exceeding these limits may receive a 429 (Too Many Requests) response.
27.3 Fair Use
The Client shall use the API in a manner consistent with normal business operations. Realizse reserves the right to throttle or suspend API access that constitutes abusive or disproportionate usage.
27.4 API Changes and Versioning
(a) Backward Compatibility. Realizse shall use commercially reasonable efforts to maintain backward compatibility when making changes to the API. Additive changes — including the addition of new endpoints, new optional parameters, or new fields in response payloads — shall not be considered breaking changes.
(b) Breaking Changes. A "Breaking Change" means any change to the API that would cause a Client's existing, conforming integration to fail or produce materially different results without modification. Breaking Changes include, without limitation: removal of an endpoint, removal of a required response field, change to the data type of an existing field, or change to the authentication mechanism.
(c) Notice of Breaking Changes. Realizse shall provide at least sixty (60) days' prior written notice before implementing any Breaking Change, unless the change is necessary to address a security vulnerability, comply with applicable law, or respond to a Sub-Processor requirement, in which case Realizse shall provide as much advance notice as is reasonably practicable.
(d) Deprecation. When an API endpoint or feature is deprecated, Realizse shall: (i) mark the deprecated endpoint or feature in the API documentation; (ii) continue to support the deprecated endpoint or feature for at least ninety (90) days following the deprecation notice; and (iii) provide migration guidance where practicable.
28. Contact Information
The Service is offered by Realizse, Inc. You may contact us by sending an email to us at support@realizse.com.