Effective October 23, 2026 · Last updated November 3, 2026
Realizse Data Processing Addendum
Preamble
This Data Processing Addendum ("DPA") is incorporated into and forms part of the Realizse Platform Terms and Conditions (the "Terms") between Realizse, Inc. ("Realizse") and the Client. Capitalized terms not defined in this DPA have the meanings given in the Terms.
This DPA governs Realizse's processing of Personal Data on behalf of the Client in connection with the delivery of the Service. It is intended to satisfy the data processing agreement requirements of the California Consumer Privacy Act, as amended by the California Privacy Rights Act ("CCPA/CPRA"), and any other applicable U.S. state privacy laws that require a written contract between a data controller and a data processor or service provider.
Relationship to the Privacy Policy. As described in Section 12.4 of the Terms, 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. This DPA governs Realizse's processing of Personal Data contained in Client Data in its capacity as a processor or service provider, on behalf of and at the direction of the Client. The two instruments are intended to be non-overlapping.
Controller / Processor Roles. As between the parties:
- The Client is the data controller (or "business" under CCPA/CPRA) with respect to Personal Data that Client submits to the Service. The Client determines the purposes and means of processing Personal Data in connection with its business operations.
- Where Personal Data is associated with a Realizse Passport, the Passport Owner (as defined in Section 11.3(a) of the Terms) exercises controller authority over such Personal Data, including the exclusive right to direct erasure, request export, and authorize or restrict third-party access in accordance with Sections 11.3(d), 15.4, and 15.6 of the Terms.
- Realizse is the data processor (or "service provider" under CCPA/CPRA) with respect to Personal Data processed on behalf of the Client. Realizse processes Personal Data solely as directed by the Client (or, with respect to Passport Data, the Passport Owner) and as necessary to provide the Service.
- A Contributing Organization (as defined in Section 11.3(a)(ii) of the Terms) that submits data associated with another Organization's Realizse Passport is not the controller of Personal Data contained in such Passport Data. The Contributing Organization's submission constitutes a transfer of control over such data to the Passport Owner in accordance with Section 11.3(c) of the Terms. Realizse is entitled to treat the Passport Owner as having full authority over all Passport Data without independent verification, and has no liability for disputes between a Passport Owner and a Contributing Organization regarding rights to contributed data. (T&C Section 11.3(h).)
- Personal Data that a Participating Organization (as defined in Section 1 of the Terms) contributes to a Client's Project is processed by Realizse on behalf of that Client under this DPA.
This B2B framework reflects the parties' mutual understanding that the Service is designed for use by business entities. Realizse does not operate a consumer-facing platform and does not sell or share Personal Data for advertising or marketing purposes.
1. Definitions
"Applicable Privacy Law" means any U.S. state privacy law applicable to the Client's use of the Service or to Realizse's processing of Personal Data on the Client's behalf, including without limitation the CCPA/CPRA, the Virginia Consumer Data Protection Act (VCDPA), the Colorado Privacy Act (CPA), the Connecticut Data Privacy Act (CTDPA), and the Maryland Online Data Privacy Act (MODPA), each as amended from time to time, to the extent any such law applies based on the Client's operations, the Client's users, or the nature of Personal Data processed. These laws are collectively referred to as "State Privacy Laws" in Section 12.5(b) of the Terms.
"Data Subject" means an identified or identifiable natural person whose Personal Data is processed by Realizse under this DPA, including without limitation employees, contractors, authorized signatories, document signers, project participants, and other individuals whose information appears in Client Data.
"Passport Data" has the meaning given in Section 11.3(b) of the Terms: all Verifiable Credentials, data, documents, files, and other content associated with a Realizse Passport, regardless of which Organization or individual originally contributed any element of it.
"Personal Data" means any information that identifies or could reasonably be used to identify a natural person, as further described in Schedule A. For purposes of CCPA/CPRA, "Personal Data" includes "personal information" as defined therein. Personal Data excludes only Aggregated Data and de-identified Usage Data, each as defined in Section 1 of the Terms.
"Processing" (and "process," "processes," "processed") means any operation performed on Personal Data, including collection, recording, storage, use, disclosure, transmission, and deletion.
"Security Incident" has the meaning given in Section 14.6(d) of the Terms: 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. Unsuccessful security events — including 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, and failed login attempts — do not constitute Security Incidents.
"Sub-Processor" means any third-party service provider engaged by Realizse to process Personal Data in connection with the Service, as listed in Schedule B.
All other capitalized terms have the meanings given in the Terms.
2. Scope and Nature of Processing
2.1 Subject Matter
Realizse processes Personal Data solely to the extent necessary to provide the Service as described in the Terms, including:
(a) document generation and electronic signature workflows via PandaDoc (T&C Section 16); (b) verifiable credential issuance, storage, correction at the Passport Owner's request, and revocation where supported (T&C Sections 17.1–17.3); (c) Realizse Passport creation, maintenance, transfer, and lifecycle management (T&C Sections 11.3, 11.3(f)); (d) platform security monitoring and incident response (T&C Sections 14.3, 14.5, 14.6); (e) compliance workflow support for 179D Tax Deduction projects and other Project types added to the Service; (f) facilitation of Transactions between Allocators and Qualified Off-takers (T&C Sections 2.4, 2.5); and (g) data export and portability services (T&C Section 15.6).
2.2 Duration
Realizse processes Personal Data for the duration of the Client's subscription and thereafter in accordance with the data retention obligations set out in Section 15 of the Terms and Section 7 of this DPA, including the post-termination transition period of ninety (90) days set forth in Section 25.11(c) of the Terms and any longer period required by Section 15.1 of the Terms.
2.3 Nature of Personal Data and Categories of Data Subjects
The categories of Personal Data in Client Data that Realizse processes on the Client's behalf, and the categories of Data Subjects, are described in Schedule A. Schedule A reflects the Personal Data inventory set out in Section 12.1 of the Terms and is not intended to expand the categories described therein.
2.4 Business Purpose
Realizse processes Personal Data solely for the following business purposes:
(a) delivering the Service in accordance with the Terms; (b) facilitating document generation, signing, and storage; (c) issuing, storing, and managing Verifiable Credentials and Realizse Passports; (d) operating, maintaining, and improving the security and reliability of the Service; (e) generating Usage Data and Aggregated Data in accordance with Section 11.4 of the Terms; (f) complying with applicable legal obligations and retaining compliance records under Section 15.1 of the Terms; and (g) as otherwise expressly authorized by the Client in writing.
Realizse shall not process Personal Data for any purpose outside of those listed in this Section 2.4 without the Client's prior written authorization, except as required by law.
3. Realizse's Obligations as Service Provider / Processor
3.1 Processing on Instruction
Realizse shall process Personal Data only on documented instructions from the Client, which instructions are set out in this DPA and in the Terms. Where Personal Data is associated with a Realizse Passport, Realizse shall treat the Passport Owner's instructions as the operative controller instructions in accordance with Section 11.3 of the Terms. If Realizse is required by applicable law to process Personal Data in a manner inconsistent with the Client's instructions, Realizse shall notify the Client of that requirement before processing, unless prohibited by law from doing so.
3.2 Prohibited Uses
Realizse shall not:
(a) sell or share Personal Data (as those terms are defined under CCPA/CPRA), consistent with Section 12.5(d) of the Terms; (b) retain, use, or disclose Personal Data for any commercial purpose other than providing the Service; (c) retain, use, or disclose Personal Data outside of the direct business relationship with the Client; or (d) combine Personal Data received from the Client with Personal Data obtained from any other source, except as permitted under CCPA/CPRA for a service provider, or as necessary to generate Aggregated Data in accordance with Section 11.4 of the Terms.
3.3 Confidentiality
Realizse shall ensure that personnel authorized to process Personal Data are subject to appropriate confidentiality obligations consistent with Section 20 of the Terms. Realizse shall not disclose Personal Data to any person who does not have a need to access it for the purposes of providing the Service. Personal Data constitutes Confidential Information under Section 20.1 of the Terms.
3.4 Internal Access Controls
Access to Personal Data by Realizse personnel is governed by Section 26.10 of the Terms (Platform Maintainer Access). Realizse and its personnel shall not access, view, retrieve, copy, or otherwise process Personal Data except under the circumstances described in Section 26.10(b):
(a) At Client's request — to investigate, diagnose, or resolve a technical issue, limited to the minimum Personal Data reasonably necessary; (b) With Client's permission — where additional access is necessary, subject to the Client's discretion to grant or withhold; (c) Platform operations — where reasonably necessary to maintain security, integrity, or availability, limited to the minimum scope and duration necessary and without review of substantive content except as incidental to the operational task; (d) Legal obligation — where required to comply with applicable law, regulation, subpoena, or court order, subject to the notice obligations in Section 20.5 of the Terms; and (e) Account setup and verification — where needed to create and maintain a Client's Organization, Users, and roles and to verify Client information, limited to the records needed.
Access is restricted to personnel with a legitimate need, enforced through appropriate access controls. (T&C Section 26.10(c).)
Content moderation under Section 11.6 of the Terms stays within these limits.
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. (T&C Section 26.10(f).)
No ongoing surveillance. Realizse shall not monitor, review, or analyze the substantive content of Personal Data on a routine or ongoing basis. Automated platform monitoring — log aggregation, performance metrics, error tracking, and security event detection — that processes metadata or system-level information does not constitute access to Personal Data for purposes of this Section 3.4. (T&C Section 26.10(d).)
Audit trail. Realizse maintains a log of each instance of access under 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 are retained for a minimum of one (1) year and are made available to Client upon reasonable written request. (T&C Section 26.10(e).)
3.5 Compliance Certification
Realizse certifies that it understands and will comply with the restrictions in this Section 3 and will process Personal Data in a manner consistent with the Client's rights and obligations under Applicable Privacy Law.
3.6 Notice and Remediation
(a) Realizse shall notify the Client if it determines that it can no longer meet its obligations under the CCPA/CPRA and its implementing regulations.
(b) Upon notice, including notice under Section 3.6(a), the Client may take reasonable and appropriate steps to stop and remediate any unauthorized use of Personal Data by Realizse.
4. Client's Obligations as Controller / Business
4.1 Lawful Basis
The Client represents and warrants that it has established and will maintain a lawful basis for any Personal Data it submits to the Service, and that its instructions to Realizse comply with Applicable Privacy Law.
4.2 Data Subject Rights
The Client is responsible for receiving and responding to requests from Data Subjects exercising rights under Applicable Privacy Law, including rights to know, access, correct, delete, and opt out of sale or sharing. Realizse shall provide reasonable assistance to the Client in fulfilling such requests to the extent technically feasible, subject to the deletion limitations described in Section 15.3 of the Terms and Section 7.2 of this DPA.
4.3 Notice to Data Subjects
The Client is responsible for providing any required privacy notices to Data Subjects whose Personal Data is submitted to the Service. This includes providing notice to document signers, as described in Section 16.4 of the Terms, to the extent required by Applicable Privacy Law. Realizse's role as a service provider processing data on behalf of the Client does not relieve the Client of this obligation. (See also T&C Section 12.4(c).)
4.4 Accuracy
The Client is responsible for the accuracy of Personal Data submitted to the Service. Where Personal Data becomes part of an issued Verifiable Credential:
(a) Realizse does not independently verify the accuracy of Client-supplied data used to generate Credential content, and is not liable for losses arising from Credentials that accurately reflect inaccurate Client-supplied data. (T&C Sections 17.3(b), 17.4.)
(b) Verifiable Credentials cannot be modified without invalidating their cryptographic proofs and cannot be deleted through the Service after issuance. Realizse issues a corrected Credential at the Passport Owner's request. (T&C Sections 17.2, 17.3(a).)
(c) The first correction per calendar quarter is provided at no charge; subsequent corrections within the same quarter may be subject to a reasonable administrative fee as set forth in the applicable Order Form. (T&C Section 17.3(d).)
4.5 Client Representations Regarding Uploaded Content
The Client's representations and warranties regarding Customer-Uploaded Content — including its authority to upload Personal Data, its authorization from third parties whose materials are submitted, and its compliance with laws governing sensitive and regulated data categories — are set forth in Section 22-A of the Terms. Realizse relies on those representations without independent investigation or verification. (T&C Section 22-A.3.) The Client's indemnification obligations with respect to Customer-Uploaded Content are set forth in Section 24.2 of the Terms.
4.6 Signatory Authority and Credential Management
The Client is responsible for managing, restricting, and revoking Platform access credentials and signing permissions, and for promptly disabling the Accounts of individuals who are no longer authorized. (T&C Sections 4.5, 16.7(c).) The Client's representations regarding the authority of Authorized Signatories, and its indemnification obligations for unauthorized signing and credential mismanagement, are set forth in Sections 16.7 and 24.2(e) of the Terms.
5. Sub-Processors
5.1 Authorized Sub-Processors
The Client authorizes Realizse to engage the Sub-Processors listed in Schedule B to process Personal Data in connection with the Service. Each Sub-Processor processes Personal Data solely for the purpose of performing its designated function as described in Section 13.1 of the Terms.
5.2 Sub-Processor Obligations
Realizse shall enter into written agreements with each Sub-Processor that impose data protection obligations no less protective than those set forth in this DPA. The current DPA status of each Sub-Processor is shown in Section 13.1 of the Terms, which Realizse shall update, notifying affected Clients within thirty (30) days of any material change (T&C Section 13.2).
Realizse remains responsible for the acts and omissions of its Sub-Processors to the same extent Realizse would be responsible if performing the processing directly, subject to the Sub-Processor limitation in Section 23.3 of the Terms and Realizse's obligation to exercise commercially reasonable diligence in selecting and monitoring Sub-Processors.
5.3 Sub-Processor Changes
Sub-Processor changes are governed by Section 13.4 of the Terms:
(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. Notice may be provided by email to the Account address or through an in-Platform notification.
(b) Objection Right. Client may object in writing within fifteen (15) days on reasonable, good-faith data protection or security grounds, specifying the basis for the objection. Realizse shall use commercially reasonable efforts to address the objection, which may include offering an alternative Sub-Processor or modifying the scope of data processed. If unresolved within thirty (30) days, Client may terminate the Terms upon written notice and receive a pro-rata refund of prepaid fees for the unexpired subscription term.
(c) Emergency Changes. 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, with notice provided as soon as reasonably practicable and no later than five (5) business days after engagement.
(d) Successor E-Signature Provider. Realizse may designate an alternative electronic signature provider upon reasonable notice to Client, provided any successor maintains equivalent SOC 2 certification or comparable security standards. (T&C Section 16.2.) Section 13.1 of the Terms will be updated accordingly.
5.4 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. (T&C Section 13.3(a).)
(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) under Commission Implementing Decision (EU) 2021/914; (ii) the EU-U.S. Data Privacy Framework or any successor adequacy mechanism; or (iii) such other mechanism as is recognized under applicable law. (T&C Section 13.3(b).)
(c) Data Localization. A Client requiring that no Personal Data be transferred outside the United States 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. (T&C Section 13.3(c).)
(d) Status. As of the date this DPA was 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. (T&C Section 13.3(d).)
5.5 Business Continuity, Successors, and Escrow Access
(a) Escrowed materials. Where Realizse and a Client enter into a source code escrow arrangement under Section 25.12 of the Terms, the escrow agreement sets out the escrowed materials, such as Platform source code, infrastructure-as-code configurations, deployment documentation, and operational runbooks. Escrowed materials do not include Client Data or Personal Data.
(b) Continuity access. Upon the occurrence of a triggering event described in Section 25.12(b) of the Terms — Realizse's bankruptcy or insolvency, cessation of substantially all Service operations without designation of a successor, or failure to cure a material breach of its data availability or portability obligations — Realizse, or its successor, trustee, or escrow agent, shall maintain read-only access to Client Data for a minimum of one hundred eighty (180) days to enable the Client to exercise its export rights. (T&C Section 25.12(d).)
(c) Confidentiality of successors. Any successor, trustee, or escrow agent with access to Personal Data under Section 5.5(b) shall be bound by confidentiality obligations no less protective than those in Section 20 of the Terms, and may access Personal Data solely for the purpose of enabling Client data export and continuity of service.
(d) DID continuity. Upon a triggering event, Realizse shall cooperate with the Client to effectuate transfer or reassignment of the relevant Decentralized Identifier 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. (T&C Section 25.12(e).)
(e) Assignment. Any assignment of the Terms in connection with a merger, acquisition, corporate reorganization, change of control, or sale of all or substantially all assets is governed by Section 26.6 of the Terms. Any assignee assumes Realizse's obligations under this DPA.
6. Security
6.1 Technical and Organizational Measures
Realizse shall implement and maintain the technical and organizational security measures described in Section 14 of the Terms. These measures are designed to protect Personal Data against unauthorized access, disclosure, alteration, loss, or destruction, and include:
(a) authentication via a SOC 2-certified identity provider using OAuth 2.0 and JSON Web Tokens, with JWT validation (signature, expiration, audience, issuer) at the API gateway (T&C Section 14.1); (b) role-based access control with defined permission scopes enforced on every user API request, and organization-scoped data isolation (T&C Sections 4.3, 4.4, 14.1); (c) encryption of Personal Data at rest and in transit (TLS 1.2 or higher) (T&C Section 14.2); (d) web application firewall, rate limiting, and input validation (T&C Sections 14.3, 7.3, 27.2); (e) content-addressed storage with SHA-256 integrity verification for files and signed documents (T&C Sections 14.4, 18.1, 18.2); (f) cryptographic proofs in Verifiable Credentials making tampering detectable (T&C Section 14.4(d)); (g) encrypted logging and monitoring of API access, application execution, and CDN traffic (T&C Section 14.5); and (h) Platform Maintainer access controls with audit logging (T&C Section 26.10).
6.2 Standard of Care
Realizse implements and maintains commercially reasonable administrative, technical, and organizational security measures, 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, consistent with Section 14.6(a) of the Terms.
Client acknowledges that no method of electronic storage or transmission over the Internet is completely secure, and that Realizse's obligation under this Section 6 is limited to the exercise of commercially reasonable efforts as described in Section 14.6(b) of the Terms.
6.3 Security Maturity
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. (T&C Section 14.6(c).)
6.4 Security Incident Notification
In the event of a Security Incident affecting Personal Data processed under this DPA, Realizse shall:
(a) notify the 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 (T&C Section 14.6(d)(i)); (b) provide the Client with a description of the nature of the incident, including — to the extent known — the categories and approximate number of Data Subjects affected, the categories and approximate volume of Personal Data involved, the likely consequences of the incident, and the measures taken or proposed to address it (T&C Section 14.6(d)(ii)); (c) take reasonable steps to mitigate the effects of and to remediate the Security Incident; and (d) cooperate with the Client in good faith to investigate and remediate the incident (T&C Section 14.6(d)(iii)).
Notification under this Section 6.4 does not constitute an acknowledgment of fault or liability by Realizse. The Client is responsible for determining whether and how to notify affected Data Subjects and relevant regulatory authorities under Applicable Privacy Law.
7. Data Retention and Deletion
7.1 Compliance Record Retention
Realizse shall retain Personal Data that is part of compliance records — signed documents, Verifiable Credentials, building data, certification records, and supporting files — for seven (7) years from the date the certification package is issued, as set out in Section 15.1 of the Terms. 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 unless the Client asks Realizse to keep the records longer. This retention obligation supersedes any deletion request with respect to such data. (T&C Sections 15.1, 15.4(b)(i).)
Platform retention periods for all data categories are set out in the table at Section 15.2 of the Terms.
7.2 Deletion Limitations
The Client acknowledges the deletion limitations described in Section 15.3 of the Terms:
(a) Files stored in Content-Addressed Storage cannot be deleted by Users through the Service. (b) 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 and keeps a record of the Credential's identifier, issuer, issuance date, and hash. (T&C Section 17.2.) (c) User accounts can be disabled but not permanently deleted through the Service; references 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) Data shared with Sub-Processors and other service providers is subject to each provider's own retention policies. Verifiable Credentials stored at Spherity are immutable and persist indefinitely; signed documents at PandaDoc are retained per PandaDoc's policy, with Realizse maintaining independent copies; a User's identity record at the identity provider is removed when Realizse disables the User's account under Section 15.4(e) of the Terms. (T&C Section 15.5.) (f) 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.
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 — consistent with Section 15.4(b)(ii) of the Terms.
To the extent a Data Subject submits a deletion request that cannot be fulfilled due to the above limitations, Realizse shall provide the Client with written notice of the specific limitation(s) so that the Client may communicate appropriately with the Data Subject.
7.3 Erasure Process
Erasure of Personal Data associated with Realizse Passports is governed by Section 15.4 of the Terms:
(a) Authorized Requestor. Only the Passport Owner may request erasure of Passport Data, by written request to support@realizse.com. A Contributing Organization may request erasure of its own organizational account and profile data, but not Passport Data it contributed to another Organization's Realizse Passport. (T&C Sections 15.4(a), 15.4(d).)
(b) Retention Override. Erasure is subject to the compliance record retention in Section 15.1 of the Terms. Realizse shall inform the Passport Owner of any data that cannot be deleted due to compliance record retention. (T&C Section 15.4(b)(i).)
(c) Technical Limitations. Erasure is subject to the deletion limitations in Section 7.2 above. Where full deletion is not feasible, Realizse shall render the data inaccessible. (T&C Section 15.4(b)(ii).)
(d) Sub-Processor Data. Erasure of data at Sub-Processors is subject to each Sub-Processor's technical capabilities and retention policies. Realizse shall use commercially reasonable efforts to cause Sub-Processors to delete or render inaccessible the relevant data. (T&C Section 15.4(b)(iii).)
(e) Contributing Organization Notice. Prior to executing an erasure request affecting Passport Data to which Contributing Organizations had access, Realizse shall provide notice in accordance with Section 11.3(e) of the Terms and allow the applicable notice and transition periods to expire. Contributing Organizations receive thirty (30) days from receipt of notice, or the remainder of the transition period under Section 25.11(c), whichever is longer. (T&C Sections 15.4(b)(iv), 11.3(e)(iii).)
(f) Timeline. Erasure of eligible data shall be completed within thirty (30) days following expiration of all applicable notice and transition periods. (T&C Section 15.4(c).)
(g) Account Disabling. Where full deletion of a User account is not feasible, Realizse shall disable the account and remove the User's identity provider record. References to the User in project records, file metadata, activity logs, and Verifiable Credentials are preserved to the extent required for compliance record retention and platform integrity. (T&C Section 15.4(e).)
7.4 Data Portability
Data portability is governed by Section 15.6 of the Terms:
(a) Export Right. The Client may request export of all Client Data, and the Passport Owner may request export of all Passport Data, at any time during the subscription and during any applicable post-termination transition period. (T&C Section 15.6(a).)
(b) Export Format. Records are exported as JSON files, with Verifiable Credentials conforming to the W3C Verifiable Credentials Data Model. Supporting documentation is exported as a compressed ZIP archive organized by Passport and project or asset. (T&C Section 15.6(b).)
(c) Delivery. Export requests are fulfilled within thirty (30) business days via a secure, authenticated download link, or within the post-termination transition period under Section 25.11(c). (T&C Section 15.6(c).)
(d) Export Fees. One export per twelve-month subscription period is provided at no charge. Additional exports may be subject to a reasonable administrative fee as set forth in the applicable Order Form. (T&C Section 15.6(d).)
(e) API Access. Nothing in this Section limits the Client's ability to retrieve its data on a per-resource basis through the API during the subscription term. (T&C Section 15.6(e).)
(f) Participating and Contributing Organization Exports. Exports to Participating or Contributing Organizations are governed by Section 15.6(f) of the Terms.
7.5 Post-Termination
Upon termination of the Terms, Realizse shall handle Personal Data in accordance with Section 25.11 of the Terms:
(a) Compliance records are retained for the period set out in Section 15.1 of the Terms, with access revoked. (T&C Section 25.11(b).) (b) Other Client Data is retained for a transition period of ninety (90) days, during which the Client may request data export under Section 15.6. (T&C Section 25.11(c).) (c) After the transition period, Realizse deletes Client Data other than compliance records to the extent technically feasible, subject to the deletion limitations in Section 7.2. (T&C Section 25.11(d).) (d) Data stored at Sub-Processors, including Verifiable Credentials at Spherity, is subject to each Sub-Processor's retention policies and may not be deletable. (T&C Section 25.11(e).) (e) Where a Passport Owner departs the Platform, Contributing Organizations receive notice and an export window in accordance with Section 11.3(e) of the Terms.
8. Assistance to Client
8.1 Data Subject Rights Requests
Realizse shall provide the Client with reasonable technical assistance in responding to Data Subject rights requests under Applicable Privacy Law, including requests to know, access, correct, or delete Personal Data. The Client acknowledges that Realizse's ability to fulfill deletion requests is subject to the limitations in Section 7.2.
If Realizse receives a verifiable consumer request directly from an individual seeking to exercise rights under Applicable Privacy Law with respect to Personal Data contained in Client Data, Realizse shall promptly notify the Client and shall cooperate with the Client in responding. Realizse shall not independently respond to such requests except as directed by the Client or required by applicable law. (T&C Section 12.5(e).)
8.2 Privacy Impact Assessments
Upon request, Realizse shall provide the Client with reasonable cooperation and information to assist the Client in conducting any privacy impact assessments or data protection impact assessments required under Applicable Privacy Law with respect to the Client's use of the Service.
8.3 Regulatory Inquiries
Realizse shall promptly notify the Client of any regulatory inquiry, investigation, or order received by Realizse that relates to Personal Data processed on the Client's behalf, to the extent permitted by applicable law. Such notification is subject to the compelled disclosure provisions in Section 20.5 of the Terms.
9. Audit Rights
9.1 Documentation
Realizse shall make available to the Client, upon written request, documentation reasonably necessary to demonstrate compliance with Realizse's obligations under this DPA, which may include completed security questionnaires, Sub-Processor agreements in redacted form, audit certifications, and Platform Maintainer access logs maintained under Section 26.10(e) of the Terms.
9.2 Audit
No more than once per calendar year — unless required by Applicable Privacy Law or following a Security Incident — the Client may, at its own expense and upon at least thirty (30) days' prior written notice, conduct or commission an audit of Realizse's processing activities covered by this DPA, subject to reasonable confidentiality protections. Realizse may satisfy this obligation by providing a current SOC 2 report (once available) or by completing a recognized industry security questionnaire in lieu of an on-site audit.
10. Liability
The parties' respective liabilities arising out of or relating to this DPA are subject to the exclusions, caps, and carve-outs set forth in Section 23 of the Terms, including the General Cap in Section 23.2(a), the Enhanced Cap in Section 23.2(b) — which applies to Security Incidents attributable to a party's failure to maintain required security measures and to material breaches of confidentiality obligations — and the uncapped categories in Section 23.2(c). Claims arising from the same underlying event or series of related events are treated as a single claim in accordance with Section 23.2(d).
Indemnification obligations relating to data protection are set forth in Sections 24.1 and 24.2 of the Terms.
11. Term and Termination
This DPA is effective as of the date the Client accepts the Terms and remains in effect for the duration of the Terms, including any post-termination transition period under Section 25.11(c) of the Terms and any period during which Realizse continues to hold Personal Data subject to compliance record retention under Section 15.1 of the Terms. Termination of the Terms automatically terminates this DPA upon expiration of those periods. The obligations in Sections 3.2, 3.3, 3.4, 5.5, 6, 7, and 8 survive termination.
12. Order of Precedence
In the event of any conflict between this DPA and either the Terms or the Privacy Policy with respect to the processing of Personal Data contained in Client Data, this DPA shall govern, consistent with Section 12.4(d) of the Terms. In the event of any conflict between this DPA and any applicable Standard Contractual Clauses incorporated herein, the Standard Contractual Clauses shall govern. In all other respects, the Terms govern the parties' contractual rights and obligations.
13. Changes to This DPA
Realizse may update this DPA from time to time. Material changes are subject to the modification notice process described in Section 25.14 of the Terms — thirty (30) days' prior written notice, with the Client's right to reject revisions within the notice period. The Client's continued use of the Service following the effective date of an updated DPA constitutes acceptance, subject to the provisions of Section 25.14 regarding pre-existing separate agreements.
14. Contact
For questions or requests related to this DPA:
Email: legal@realizse.com Erasure and account requests: support@realizse.com Mail: Realizse, Inc., 444 Somerville Ave., Somerville, MA 02143
Schedule A: Personal Data Inventory
This Schedule A reflects the Personal Data in Client Data that Realizse processes on the Client's behalf, as described in Section 12.1 of the Terms.
| Category of Data Subjects | Categories of Personal Data | Purpose of Processing |
|---|---|---|
| Document Signers (standard) | Name, email address, job title, company name | Document generation and electronic signing via PandaDoc (T&C Section 16.4) |
| Document Signers (allocation agreements) | Name, email, job title, company, street address, city, state, postal code, phone number | Execution of definitive transaction documents via PandaDoc (T&C Section 16.4) |
| Document Signers (audit trail, for documents signed through the Platform) | Verified email address, IP address, geolocation data, UTC timestamp, device fingerprint, document hash | E-signature audit trail and evidentiary record (T&C Section 16.6(a)); documents signed elsewhere and uploaded are stored with a hash from the date of upload (T&C Section 16.6(f)) |
| Project participants | Names, email addresses, and (for final allocation agreements) physical addresses and phone numbers; qualified individuals' names, employers, and business addresses used in certification and tax records | Project workflow orchestration and credential issuance (T&C Section 12.1) |
| Data Subjects whose Personal Data from Client Data appears in Service Logs | Personal Data from Client Data in Service Logs (CDN access logs, API access logs, and application execution logs), such as identifiers, email addresses, and IP addresses | Operating, securing, and supporting the Service (T&C Sections 1, 14.5) |
Schedule B: Authorized Sub-Processors
The Sub-Processors are the service providers listed in Section 13.1 of the Terms that handle data for the Client. Section 13.1 shows each Sub-Processor's role, data location, the data it processes, and its DPA status, which Realizse updates as described in Section 13.2 of the Terms.
Appendix: Cross-Reference to Terms and Conditions and Privacy Policy
Section references are to the current versions of the Terms and the Privacy Policy.
| Topic | DPA | T&C | Privacy Policy |
|---|---|---|---|
| Controller/processor designation | Preamble | 12.4(c), 12.5(c) | Introduction |
| Passport Owner controller authority | Preamble, 3.1 | 11.3 | Introduction |
| Contributing Organization status | Preamble | 11.3(c), 11.3(h) | Introduction |
| Processing purposes | 2.4 | 12.2 | 2 |
| Prohibited uses / no sale | 3.2 | 12.5(d) | 3.5 |
| Usage Data / Aggregated Data | 3.2(d) | 11.4 | 2.4 |
| Confidentiality | 3.3 | 20 | 3.7 |
| Internal access controls | 3.4 | 26.10 | 9 |
| Client warranties re uploaded content | 4.5 | 22-A | Introduction |
| Signatory authority | 4.6 | 16.7, 24.2(e) | — |
| Credential correction | 4.4 | 17.3 | 4.3 |
| Sub-Processors | 5.1, Schedule B | 13.1, 13.2 | 3.1 |
| Sub-Processor changes | 5.3 | 13.4 | 3.1 |
| Cross-border transfer | 5.4 | 13.3 | 8 |
| Data localization | 5.4(c) | 13.3(c) | 8 |
| Business continuity / escrow | 5.5 | 25.12 | 3.4 |
| Assignment | 5.5(e) | 26.6 | 3.4(a) |
| Security measures | 6.1 | 14.1–14.5 | 7 |
| Standard of care | 6.2 | 14.6(a), (b) | 7 |
| SOC 2 roadmap | 6.3 | 14.6(c) | 7 |
| Incident notification | 6.4 | 14.6(d) | 7 |
| Compliance record retention | 7.1 | 15.1, 15.2 | 4.2 |
| Deletion limitations | 7.2 | 15.3, 15.5 | 4.3, 4.4 |
| Erasure process | 7.3 | 15.4 | 5.4 |
| Data portability | 7.4 | 15.6 | 5.4 |
| Post-termination | 7.5 | 25.11, 11.3(e) | 4.5 |
| Data subject rights routing | 8.1 | 12.5(e) | 5.1 |
| Audit rights | 9 | — | — |
| Liability | 10 | 23, 24 | — |
| Order of precedence | 12 | 12.4(d) | Introduction |
| Changes | 13 | 25.14 | 12 |
| Personal Data inventory | Schedule A | 12.1 | 1 |
Document History
| Version | Date | Author | Notes |
|---|---|---|---|
| 0.1 | 2026-03-18 | Legal (AI-assisted) | Initial draft; coordinated with T&C v0.3 and Privacy Policy v0.1 |
| 0.2 | 2026-03-27 | Legal (AI-assisted) | Added Passport Owner framework, Platform Maintainer access, expanded erasure and portability, Document Signer audit trail in Schedule A |
| 0.3 | 2026-08-13 | Legal (AI-assisted) | Reconciled against T&C v0.5 and Privacy Policy v0.3. Corrected modification cross-reference from 25.13 (*Survival*) to 25.14 (*Modification of Terms*). Added relationship-to-Privacy-Policy statement (Preamble) and revised order of precedence (Section 12) to track new T&C 12.4(d). Added Section 5.5 (Business Continuity, Successors, and Escrow Access) covering T&C 25.12. Added Section 10 (Liability) referencing T&C Section 23 caps. Added Section 4.5 (Client Representations re Uploaded Content, T&C 22-A) and Section 4.6 (Signatory Authority, T&C 16.7). Expanded Section 4.4 to cover credential correction by supersession. Added data localization (5.4(c)), successor e-signature provider (5.3(d)), third-party retention (7.2(e)), Contributing Organization notice periods (7.3(e)), API access carve-out (7.4(e)). Added Passport Data definition. Added project participants and Realizse access records to Schedule A. Added DPA status column to Schedule B. Replaced stale numeric decision-item references with T&C Appendix A Part 2 lettering. Added Open Items table. |
| — | 2026-11-02 | Legal (AI-assisted) | Applied counsel's decisions of October 29, 2026 and the approved new wording, in one release with the Terms and Privacy Policy. Renamed from Data Processing Agreement to Data Processing Addendum. Header gives the effective and last-updated dates; the internal status, owner and version lines are removed. Visitors to the Public Websites, and Participating Organizations' contributions processed for the Client (Preamble). Personal Data excludes only Aggregated Data and de-identified Usage Data; wider Security Incident definition (1). User accounts are Realizse's own data, so authentication leaves the processing scope (2.1, 2.4); IRS retention wording removed (2.4, 7.1). Fifth Platform Maintainer access purpose, content moderation limits and tax return information (3.4); California notice and remediation terms (3.6). Corrected Credentials on request (4.4). Notices to the account administrator (6.4). Compliance record retention replaces regulatory retention (7.1, 7.3, 7.5, 11); minimal personal details, identity record removal and backups (7.2); export of all Client Data (7.4). Schedule A limited to Personal Data in Client Data; Schedule B refers to the service-provider list in T&C 13.1. |