Effective October 23, 2026 · Last updated November 3, 2026
Realizse Privacy Policy
Introduction
Realizse, Inc. ("Realizse," "we," "us," or "our") operates a cloud-hosted compliance technology platform at app.realizse.com (the "Platform"), the Realizse API, and our websites at www.realizse.com and www.179Dregistry.com ("Public Websites"). The Platform and the API (together, the "Service") are designed for use by business entities in connection with clean energy tax credit and deduction compliance, including Section 179D, digital passport issuance, verifiable credential management, and related workflows.
This Privacy Policy describes how Realizse collects, uses, stores, and discloses personal information in connection with:
- Platform Users — individuals who access and use the Service on behalf of a Client organization through an Account (as defined in Section 1 of the Terms);
- Organization Contacts — individuals named as contacts for Client organizations on the Platform (see Section 1.3);
- Website Visitors — individuals who visit the Public Websites; and
- Business Contacts — representatives of prospective or current Client organizations who interact with Realizse for sales, marketing, or support purposes.
Scope and Relationship to Other Agreements
What this Policy covers. This Policy governs Realizse's own first-party data practices — the personal information Realizse collects and processes for its own operational, security, and business purposes as a data controller.
What this Policy does NOT cover. This Policy does not govern how Realizse processes personal information contained in Client Data (as defined in Section 11.1 of the Terms) on behalf of Clients in connection with Client-initiated workflows — including project data, asset and product passport records, transaction documents, and verifiable credentials. Those processing activities are governed by the Data Processing Addendum ("DPA") incorporated into the Terms, under which the Client is the data controller and Realizse is the data processor (or "service provider" under applicable State Privacy Laws).
Where Client Data is associated with a Realizse Passport, controller authority is exercised by the Passport Owner as defined in Section 11.3(a) of the Terms. A Contributing Organization that submits data to another Organization's Realizse Passport transfers control over that data to the Passport Owner in accordance with Section 11.3(c) of the Terms. The Client (and, where applicable, the Passport Owner) is responsible for providing any required privacy notices to individuals whose personal information appears in Client-submitted content.
Client responsibility for uploaded content. The Client's representations and warranties regarding the lawfulness of, and its authority over, Customer-Uploaded Content — including personal information contained therein and materials contributed by third parties — are set forth in Section 22-A of the Terms.
B2B Platform. The Service is designed exclusively for use by business entities in a business-to-business context. Realizse does not knowingly offer the Service to, or collect personal information from, individual consumers acting in a personal capacity. See Section 12.5(a) of the Terms.
Incorporation. This Privacy Policy is incorporated into and made a part of the Realizse Platform Terms and Conditions (the "Terms") pursuant to Section 26.2 of the Terms. Capitalized terms not defined in this Policy have the meanings given in the Terms.
1. Personal Information We Collect
1.1 From Platform Users
When an individual creates a Platform Account or uses the Service on behalf of a Client organization, Realizse collects:
- Identity and contact information: First name, last name, business email address, phone number, job title, and optional department. (See T&C Sections 4.1 and 12.1.)
- Account and role information: Organization membership and assigned role — Admin, Editor, or Viewer. (See T&C Section 4.4.)
- Authentication data: Email address used for passwordless authentication; JSON Web Token (JWT) metadata (token issuance time, expiration, audience, issuer). Realizse does not store user passwords. (See T&C Section 4.2.)
1.2 From Document Signers
When an individual is designated as a signer for documents generated through the Service, the following information is shared with PandaDoc, Inc. for document generation and signing:
- Standard signer data: Name, email address, job title, and company name.
- Extended signer data (for final allocation agreements): Street address, city, state, postal code, and phone number.
Document Signers invited through the Service hold Platform Accounts. Signers receive signing invitations via email from PandaDoc and interact directly with PandaDoc's signing interface. PandaDoc's collection and processing of signer data is governed by PandaDoc's own privacy policy and terms of service. (See T&C Sections 16.3 and 16.4.)
Realizse handles signer details and the signing audit trail for the Client under the DPA, not under this Policy. A signer's own Platform Account remains covered by this Policy.
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. (See T&C Section 16.2.) Section 13.1 of the Terms will be updated to reflect any such change.
1.3 From Organization Contacts
Realizse collects contact information for individuals associated with Client organizations, including:
- Organization contact PII: Contact person names, job titles, business email addresses, phone numbers, and physical business addresses. (See T&C Section 12.1.)
Personal information about project participants — signer names, email addresses, and (for final allocation agreements) physical addresses and phone numbers, and qualified individuals' names, employers, and business addresses used in certification and tax records — is part of Client Data and is handled for the Client under the DPA, not under this Policy.
1.4 From Website Visitors
When individuals visit the Public Websites, Realizse may collect:
- Device and browser information: Browser type and version, operating system, screen resolution, and device type.
- Usage information: Pages visited, time spent on pages, referral source, and click activity.
- Network information: IP address and approximate geographic location derived from IP address.
This information is collected on www.realizse.com through Cloudflare Web Analytics, which does not use cookies, as described in Section 6 of this Policy.
1.5 From Business Contacts
Realizse collects business contact information from individuals who interact with Realizse in a sales, marketing, or partnership context, including:
- Contact information: Name, business email address, phone number, job title, company name, and business address.
- Communication records: Emails, meeting notes, and other correspondence related to business relationship management.
- Event participation: Webinar registrations, conference attendance, and related information.
1.6 Information Generated Through Use of the Service
Realizse automatically generates the following information through the operation of the Service:
- CDN access logs: Client IP addresses. Retained for 90 days.
- API access logs: Request timestamps, endpoints accessed, HTTP methods, response codes, and request identifiers. Retained for 365 days. (See T&C Section 15.2.)
- Application execution logs: Execution traces that may include user identifiers, email addresses, IP addresses, and other personal information. Retained for 365 days. (See T&C Sections 12.1 and 15.2.)
- E-signature audit trail data: For each document signed through the Platform, PandaDoc generates the signatory's verified email address, IP address, geolocation data, UTC timestamp of execution, device fingerprint, and document hash. Realizse handles this data for the Client under the DPA. Documents signed elsewhere and uploaded to the Platform are stored with a hash from the date of upload. (See T&C Sections 16.6(a) and 16.6(f).)
- Platform Maintainer access logs: Identity of accessing personnel, date and time of access, purpose, and scope of data accessed. Retained for a minimum of one (1) year. (See T&C Section 26.10(e).)
The CDN access logs, API access logs, and application execution logs are the "Service Logs" defined in Section 1 of the Terms. Realizse uses Service Logs only to operate, secure, and support the Service, and protects personal information in them in the same way as other personal information.
2. How We Use Personal Information
2.1 Service Delivery and Platform Operations
Realizse uses personal information to:
- Authenticate and authorize access to the Service through the identity provider (Auth0/Okta). (See T&C Sections 4.2, 14.1.)
- Manage organization accounts and enforce role-based access control and data isolation. (See T&C Sections 4.3, 4.4.)
- Generate documents and facilitate electronic signatures through PandaDoc. (See T&C Section 16.)
- Issue Verifiable Credentials and manage Realizse Passports through Spherity GmbH. (See T&C Sections 11.3, 17.)
- Process asynchronous operations including document signing, credential issuance, and file archival. (See T&C Section 2.6.)
- Fulfill data export and portability requests. (See T&C Section 15.6.)
2.2 Security, Monitoring, and Integrity
Realizse uses personal information to:
- Monitor platform security through logging, web application firewall analysis, and security event detection. (See T&C Sections 14.3, 14.5.)
- Investigate and respond to Security Incidents as defined in Section 14.6(d) of the Terms.
- Enforce acceptable use through rate limiting, input validation, and access control enforcement. (See T&C Sections 7.2, 7.3, 27.2.)
- Maintain audit trails for electronic signatures as described in Section 16.6 of the Terms.
2.3 Support and Communication
Realizse uses personal information to:
- Respond to support requests in accordance with the support levels described in Section 19.2 of the Terms.
- Communicate with Clients and Users regarding the Service, including service-related notices, security notifications, maintenance alerts, and incident notifications. (See T&C Section 19.1.)
- Facilitate Platform Maintainer access under the limited circumstances described in Section 26.10 of the Terms.
2.4 Business Operations
Realizse uses personal information to:
- Generate Usage Data and Aggregated Data as described in Section 11.4 of the Terms, for analytics, benchmarking, performance monitoring, and service improvement. Usage Data is information about the use of the Service that does not identify any individual, and Aggregated Data no longer reasonably identifies any individual, Client, or Project. Realizse keeps such data in de-identified form, takes reasonable technical measures to ensure that it cannot be associated with any individual, does not attempt to re-identify it, and contractually requires anyone with whom it shares such data to do the same.
- Manage billing and payment in connection with subscription and variable fees as described in Sections 25.1 through 25.9 of the Terms.
- Send marketing and promotional communications to business contacts, subject to opt-out rights described in Section 5 of this Policy.
- Comply with legal and regulatory obligations.
2.5 Legal Basis for Processing
Realizse processes personal information on the following bases:
- Performance of contract: Processing necessary to deliver the Service under the Terms and any applicable Customer Agreement.
- Legitimate business interests: Security monitoring, fraud prevention, service improvement, and business relationship management, balanced against the data subject's interests and reasonable expectations in a B2B professional context.
- Legal obligation: Processing required to comply with applicable law, including responses to lawful government requests.
- Consent: Where required by applicable law, including for certain marketing communications and non-essential cookies.
3. How We Share Personal Information
3.1 Service Providers and Sub-Processors
Realizse shares personal information with the service providers listed in Section 13.1 of the Terms, solely for the purposes described there. That list shows each provider's role, whether it handles data for Realizse or for the Client, and the data it processes, and, for each Sub-Processor, its data location and DPA status. The service providers that handle data for the Client are Sub-Processors.
Each Sub-Processor processes personal information solely for the purpose of performing its designated function. 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 of the Terms and is updated as circumstances change.
Sub-Processor changes are governed by Section 13.4 of the Terms, which provides Clients with thirty (30) days' prior notice, a fifteen (15) day objection window, and a termination right with pro-rata refund if an objection cannot be resolved. Emergency Sub-Processor changes may be made without prior notice where necessary to address a security incident, maintain Service availability, or comply with a legal obligation, with notice provided within five (5) business days. (See T&C Section 13.4(c).)
3.2 Professional Advisors and Service Providers
Realizse may share personal information with its attorneys, accountants, auditors, insurers, and other professional advisors in connection with Realizse's business operations, subject to confidentiality obligations.
3.3 Legal and Regulatory Disclosures
Realizse may disclose personal information if required by applicable law, regulation, legal process, subpoena, or governmental request — including IRS or other tax authority requests related to 179D compliance. Compelled disclosures are subject to the notice obligations described in Section 20.5 of the Terms. Where legally permitted, Realizse will notify the affected Client before making such a disclosure.
3.4 Business Transfers, Successors, and Business Continuity
(a) Business transfers. In the event of a merger, acquisition, corporate reorganization, change of control, or sale of all or substantially all of Realizse's assets, personal information may be transferred to the acquiring entity. Any such transfer is subject to the assignment provisions in Section 26.6 of the Terms, and the acquiring entity will assume Realizse's obligations under this Policy and the DPA.
(b) Source code escrow. Upon a Client's written request and at the Client's expense, Realizse may enter into a three-party source code escrow arrangement under a separate escrow agreement, as described in 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 information.
(c) Continuity access. If a triggering event described in Section 25.12(b) of the Terms occurs — including Realizse's bankruptcy, cessation of operations, or uncured material breach of its data availability obligations — Realizse, or its successor, trustee, or escrow agent, will maintain read-only access to Client Data for a minimum of one hundred eighty (180) days to enable Clients to export their data. Any such successor, trustee, or escrow agent is bound by confidentiality obligations and may access Client Data solely for the purpose of enabling Client data export and continuity of service. (See T&C Section 25.12(d).)
(d) Decentralized Identifier continuity. Upon a triggering event, Realizse will cooperate with the Client to transfer or reassign the relevant DID resolution records, including DID documents and associated verification methods, to the Client or its designee, to the extent technically feasible. (See T&C Section 25.12(e).)
3.5 No Sale or Sharing for Advertising
Realizse does not sell personal information and does not share personal information for cross-context behavioral advertising, as those terms are defined under CCPA/CPRA and other applicable State Privacy Laws. This applies to all categories of personal information collected by Realizse and is consistent with Section 12.5(d) of the Terms.
3.6 Public Announcements
Realizse may make public announcements regarding Client activity on the Platform, including the closing of a Transaction. Such announcements will not include the Client's name, the name of any Project, or any other identifying information without the Client's consent. (See T&C Section 20.4.)
3.7 Confidentiality
All personal information constitutes Confidential Information under Section 20 of the Terms and is subject to the confidentiality obligations set forth therein.
4. Data Retention
4.1 Retention Periods
Realizse retains personal information for the periods set out in Section 15.2 of the Terms:
| Data Category | Retention Period | Deletable | Basis |
|---|---|---|---|
| User account data (name, email, role) | Duration of service agreement | Disable only (T&C 15.3(c)) | Service delivery |
| Organization records and contact data | Duration of service agreement | No | Account management |
| Project, asset, and product passport records | Seven (7) years (T&C 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No | Compliance record retention and operational continuity |
| Files and signed documents | Seven (7) years (T&C 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No (T&C 15.3(a)) | Compliance evidence and data integrity |
| Verifiable credentials | Seven (7) years (T&C 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No (T&C 15.3(b)) | W3C standard; cryptographic integrity |
| Document signer data (at PandaDoc) | Per PandaDoc's retention policy; independent copies retained by Realizse | No | E-signature validity (T&C 15.5(b), 16.5) |
| E-signature audit trail data (documents signed through the Platform) | Seven (7) years (T&C 15.1), then personal details are removed unless the Client asks Realizse to keep the records longer | No | Evidentiary sufficiency (T&C 16.6) |
| API access logs | 365 days | Automatic | Security and operational monitoring |
| CDN access logs | 90 days | Automatic | Security and operational monitoring |
| Application execution logs | 365 days | Automatic | Debugging and incident response |
| Platform Maintainer access logs | Minimum one (1) year | No | Access accountability (T&C 26.10(e)) |
| Business contact and CRM data | Until no longer needed for the business purpose, or upon valid opt-out request | Yes | Legitimate business interest |
| Website analytics data | Per applicable analytics tool retention settings | Yes | Website improvement |
4.2 Compliance Record Retention
Compliance records — signed documents, Verifiable Credentials, building data, certification records, and supporting files — are Client Data. They are kept for seven (7) years from the date the certification package is issued, under Section 15.1 of the Terms and Section 7.1 of the DPA. Requests to delete them should be directed to the Client. (See T&C Sections 15.1 and 15.4(b)(i).)
4.3 Deletion Limitations
Due to the architecture of the Service, certain categories of data cannot be deleted through the Service:
- Users cannot modify or delete the contents of Files stored in Content-Addressed Storage through the Service.
- Verifiable Credentials, once issued, cannot be modified without invalidating their cryptographic signatures and cannot be deleted by users through the Service. Realizse issues a corrected Credential at the Passport Owner's request. (See T&C Section 17.3.) 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. (See T&C Section 17.2.)
- User accounts can be disabled (preventing further access) but references in project records, file metadata, activity logs, and Verifiable Credentials are preserved.
- Organization, project, and passport records do not have deletion mechanisms in the current version of the Service.
- 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.
These limitations are described in full in Section 15.3 of the Terms. Where a deletion request cannot be fulfilled due to these technical constraints or to compliance record retention, Realizse will render the data inaccessible through the Service — including by revoking all access permissions and removing the data from active query results — and will notify the requestor of the applicable limitation. (See T&C Section 15.4(b)(ii).)
4.4 Third-Party Retention
Data shared with Sub-Processors and other service providers is subject to each provider's own retention policies. In particular, verifiable credentials stored at Spherity are immutable and persist indefinitely; signed documents stored at PandaDoc are retained per PandaDoc's retention policy (with Realizse maintaining independent copies); and 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. (See T&C Section 15.5.)
4.5 Post-Termination Retention
Upon termination of the Terms, Realizse retains data as follows:
- Compliance records: Retained for seven (7) years under Section 15.1 of the Terms, with access revoked. (T&C Section 25.11(b).)
- Other Client Data: Retained for a transition period of ninety (90) days following termination, during which the Client may request data export. (T&C Section 25.11(c).)
- Contributing Organization notice: Where a Passport Owner departs the Platform, Contributing Organizations receive thirty (30) days' notice, or the remainder of the transition period (whichever is longer), to export data to which they had access. (T&C Section 11.3(e).)
- Sub-Processor data: Subject to each Sub-Processor's own retention policies, including indefinite retention of Verifiable Credentials at Spherity. (T&C Sections 15.5, 25.11(e).)
- After the transition period: Realizse deletes Client Data other than compliance records to the extent technically feasible, subject to the deletion limitations in Section 15.3 of the Terms. (T&C Section 25.11(d).)
5. Your Rights and Choices
5.1 Rights Under Applicable State Privacy Laws
To the extent applicable U.S. state consumer privacy laws — including CCPA/CPRA, VCDPA, CPA, CTDPA, or any successor legislation (collectively, "State Privacy Laws" as defined in Section 12.5(b) of the Terms) — apply to Realizse's processing of your personal information, you may have the following rights:
- Right to Know / Access: Request disclosure of the categories and specific pieces of personal information Realizse has collected about you.
- Right to Delete: Request deletion of personal information, subject to the retention and deletion limitations described in Section 4 of this Policy and Sections 15.1, 15.3, and 15.4 of the Terms.
- Right to Correct: Request correction of inaccurate personal information.
- Right to Opt Out of Sale/Sharing: Realizse does not sell personal information or share it for cross-context behavioral advertising, so this right is satisfied by default.
- Right to Non-Discrimination: Realizse will not discriminate against you for exercising any privacy right.
Where to direct requests. For personal information contained in Client Data, individuals should direct privacy rights requests to the Client organization (or, where applicable, the Passport Owner) that submitted such data. If Realizse receives such a request directly, Realizse will promptly notify the applicable Client and cooperate with the Client in responding. Realizse will not independently respond to such requests except as directed by the Client or as required by applicable law. (See T&C Section 12.5(e).)
For personal information that Realizse controls directly — Platform User accounts, organization contacts, website visitor data, and business contact data — submit requests to legal@realizse.com.
5.2 Marketing Communications
You may opt out of promotional emails from Realizse by following the unsubscribe instructions in any promotional email, or by contacting us at legal@realizse.com. Opting out of marketing communications does not affect service-related communications such as security alerts, maintenance notices, incident notifications, or support responses. (See T&C Sections 26.3, 26.4.)
5.3 Account Management
Clients are responsible for managing User accounts within their Organization, including ensuring that only authorized individuals receive Accounts, maintaining the accuracy of User information, and promptly disabling the Accounts of individuals who are no longer authorized to access the Service. (See T&C Section 4.5.) Individuals may also contact Realizse at support@realizse.com to request updates to their account information.
5.4 Erasure and Data Portability
Erasure and data portability rights are governed primarily by the Terms:
- Erasure requests. The Passport Owner may request deletion of Passport Data by written request to support@realizse.com. Requests are processed in accordance with Section 15.4 of the Terms, subject to the compliance record retention override, technical deletion limitations, Sub-Processor capabilities, and Contributing Organization notice requirements. Eligible data is erased within thirty (30) days following expiration of all applicable notice and transition periods. (See T&C Sections 15.4(a)–(c).)
- Contributing Organization requests. A Contributing Organization may request deletion of its own organizational account and profile data, but not Passport Data it contributed to a Realizse Passport owned by another Organization. (See T&C Section 15.4(d).)
- Data export requests. The Client may request export of all Client Data, and the Passport Owner may request export of its Passport Data. Requests are fulfilled in accordance with Section 15.6 of the Terms — JSON files, with credentials conforming to the W3C Verifiable Credentials Data Model, plus a ZIP archive of supporting documentation, delivered via secure authenticated link within thirty (30) business days. 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. (See T&C Sections 15.6(a)–(d).)
6. Cookies and Tracking Technologies
6.1 Cookies We Use
Public Websites. www.realizse.com uses Cloudflare Web Analytics to understand how visitors use the site. Cloudflare Web Analytics is cookieless: it does not use any client-side state, such as cookies or localStorage, to collect usage metrics, and it does not “fingerprint” individuals via their IP address, User Agent string, or any other data for the purpose of displaying analytics. www.179Dregistry.com redirects to realizse.com/179d.
Platform. The Platform does not run analytics or advertising tools, and it sets only these cookies:
- Strictly necessary cookies: sign-in cookies that keep a User signed in and protect the sign-in process. The Platform cannot be used without them.
- Functional cookies: a cookie that remembers which workspace a User last chose.
The Platform also keeps some preferences in the browser's local storage and unsaved form drafts in the browser's session storage.
6.2 Cookie Preferences
You may manage cookie preferences through your browser settings. Most browsers allow you to block or delete cookies through the browser's settings menu. Blocking the Platform's strictly necessary cookies prevents signing in, and disabling other cookies may affect the functionality of the Platform.
6.3 Do Not Track
There is no industry consensus on how to respond to Do Not Track (DNT) browser signals. Realizse does not currently alter its data collection practices in response to DNT signals. If an industry standard for DNT emerges, Realizse will reassess this position.
7. Security
Realizse maintains administrative, technical, and organizational security measures designed to protect personal information against unauthorized access, use, alteration, disclosure, or destruction. These measures are described in Section 14 of the Terms and include:
- Authentication through a SOC 2-certified identity provider using OAuth 2.0 with JSON Web Tokens, with JWT validation at the API gateway. (T&C Section 14.1.)
- Role-based access control with defined permission scopes and organization-scoped data isolation. (T&C Sections 4.3, 14.1.)
- Encryption at rest and in transit (TLS 1.2 or higher). (T&C Section 14.2.)
- Web application firewall with malicious traffic blocking, and rate limiting at the API gateway. (T&C Section 14.3.)
- Content-addressed file storage with SHA-256 integrity verification. (T&C Section 14.4.)
- Encrypted logging and monitoring of API access, application execution, and traffic. (T&C Section 14.5.)
Standard of care. Realizse implements and maintains commercially reasonable 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. (T&C Section 14.6(a).)
No absolute guarantee. 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. (T&C Section 14.6(b).)
Security maturity. Realizse is committed to pursuing independent security certifications, including SOC 2 Type 1, as organizational resources permit, and will notify Clients upon achieving any such certification. (T&C Section 14.6(c).)
Incident notification. A Security Incident is 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. In the event of a Security Incident, Realizse will notify affected Clients 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, including a description of the nature of the incident, the categories and approximate volume of data affected, and remediation measures. 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. (T&C Section 14.6(d).)
8. Cross-Border Data Transfer
Verifiable credential data is processed and stored by Spherity GmbH in the European Union (Germany) as described in Section 13.3 of the Terms. All other Sub-Processors process and store data within the United States.
The Service primarily serves U.S.-based business clients, and Realizse does not currently target or actively collect personal information from individuals located in the European Economic Area, United Kingdom, or Switzerland. To the extent any transfer of personal information to Spherity GmbH constitutes a cross-border data transfer subject to applicable data protection law, Realizse will ensure that such transfer is covered by an appropriate legal transfer mechanism, which may include the European Commission's Standard Contractual Clauses, the EU-U.S. Data Privacy Framework or any successor adequacy mechanism, or such other mechanism as is recognized under applicable law. (See T&C Section 13.3(b).)
Data localization. A Client that requires that no personal information be transferred outside the United States should notify Realizse in writing prior to onboarding. Realizse will work with the Client in good faith to assess whether an alternative architecture is available. Any additional costs associated with a data localization request are borne by the Client. (See T&C Section 13.3(c).)
9. Platform Maintainer Access to Personal Information
Realizse and its authorized personnel do not access, view, retrieve, copy, or otherwise process Client Data except as expressly permitted under Section 26.10 of the Terms. Permitted access is limited to five circumstances:
- At Client's request — where a Client or authorized User submits a written request for Realizse to investigate, diagnose, or resolve a technical issue, Realizse personnel may access the minimum Client Data reasonably necessary.
- With Client's permission — where additional access is necessary to resolve an issue, Realizse will request permission, which the Client may grant or withhold at its sole discretion.
- 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.
- Legal obligation — where required to comply with applicable law, subject to the compelled disclosure notice obligations in Section 20.5 of the Terms.
- 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 do 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 does not monitor, review, or analyze the substantive content of Client 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 Client Data. (T&C Section 26.10(d).)
Audit trail. Realizse maintains a log of each instance of access, including the identity of the accessing personnel, date and time, purpose, and scope. Logs are retained for a minimum of one (1) year and are available to Clients upon reasonable written request. (T&C Section 26.10(e).)
10. Children
The Service is designed for use by business professionals in a professional capacity, and users must be at least 18 years old. Realizse does not knowingly collect personal information from individuals under the age of 18. If Realizse becomes aware that personal information has been collected from a minor, it will take steps to delete such information promptly. (See T&C Section 3.)
11. Third-Party Services and Linked Websites
The Service may contain links to third-party websites or enable export of information to third-party services. Third-party services are not under Realizse's control, and Realizse is not responsible for their privacy practices or their use of exported information. Please review the privacy policy of any third-party service before sharing information with it. Once sharing occurs, Realizse has no control over the information shared. (See T&C Section 10.)
In particular, document signers interact directly with PandaDoc's signing interface, and PandaDoc's privacy practices are governed by PandaDoc's own privacy policy. (See T&C Section 16.4.)
12. Changes to This Policy
Realizse may update this Privacy Policy from time to time. If we make material changes, we will notify Clients via email to the address associated with the Client's Account or through an acknowledgement on the Platform at least thirty (30) days before the changes take effect, consistent with the Terms modification process described in Section 25.14 of the Terms. The updated Policy will be posted at https://app.realizse.com/privacy with a revised "Last updated" date.
Continued use of the Service following the effective date of an updated Policy constitutes acceptance of the updated Policy, subject to the provisions of Section 25.14 of the Terms regarding pre-existing separate agreements and the Client's right to reject revisions within the notice period.
13. Contact Us
For questions, concerns, or requests related to this Privacy Policy or Realizse's privacy practices:
Privacy and legal inquiries: legal@realizse.com General support, account changes, and erasure requests: support@realizse.com Electronic signature disputes: legal@realizse.com (within the timeframe specified in T&C Section 16.6(e)) Mail: Realizse, Inc., 444 Somerville Ave., Somerville, MA 02143
For data processing matters governed by the DPA — i.e., personal information contained in Client Data — contact Realizse at legal@realizse.com.
Appendix: Cross-Reference to Terms and Conditions
This Policy is designed to be read alongside the Terms and the DPA. The following table identifies where key privacy-related provisions appear across the three documents. Section references are to the current versions of the Terms and the DPA.
| Topic | Privacy Policy | T&C | DPA |
|---|---|---|---|
| Incorporation of Privacy Policy | Introduction | Preamble, 26.2 | — |
| Controller/processor designation | Introduction | 12.5(c) | Preamble |
| Passport Owner controller authority | Introduction | 11.3 | Preamble, 3.1 |
| Client warranties re uploaded content | Introduction | 22-A | 4.5 |
| PII categories collected | 1 | 12.1 | Schedule A |
| E-signature data and audit trail | 1.2, 1.6 | 16.4, 16.6 | Schedule A |
| Purpose of processing | 2 | 12.2 | 2.4 |
| Usage Data / Aggregated Data | 2.4 | 11.4 | 3.2(d) |
| Sub-Processors | 3.1 | 13.1, 13.2 | 5.1, Schedule B |
| Sub-Processor changes | 3.1 | 13.4 | 5.3 |
| Business continuity / escrow access | 3.4 | 25.12 | 5.5 |
| Assignment / business transfer | 3.4(a) | 26.6 | 5.5 |
| No sale / no sharing | 3.5 | 12.5(d) | 3.2(a) |
| Public announcements | 3.6 | 20.4 | — |
| Confidentiality | 3.7 | 20 | 3.3 |
| Retention periods | 4.1 | 15.2 | 7.1 |
| Compliance record retention | 4.2 | 15.1, 15.4(b)(i) | 7.1 |
| Deletion limitations | 4.3 | 15.3 | 7.2 |
| Credential correction | 4.3 | 17.3 | 4.4 |
| Third-party retention | 4.4 | 15.5 | 7.2(e) |
| Post-termination data | 4.5 | 25.11, 11.3(e) | 7.5 |
| State privacy law rights | 5.1 | 12.5 | 8.1 |
| Consumer rights request routing | 5.1 | 12.5(e) | 8.1 |
| Right to erasure | 5.4 | 15.4 | 7.3 |
| Data portability / export | 5.4 | 15.6 | 7.4 |
| Security measures | 7 | 14.1–14.5 | 6.1 |
| Standard of care | 7 | 14.6(a), (b) | 6.2 |
| SOC 2 roadmap | 7 | 14.6(c) | 6.3 |
| Incident notification | 7 | 14.6(d) | 6.4 |
| Cross-border transfer | 8 | 13.3 | 5.4 |
| Platform Maintainer access | 9 | 26.10 | 3.4 |
| Eligibility / minimum age | 10 | 3 | — |
| Third-party services | 11 | 10 | — |
| Changes to policy | 12 | 25.14 | 13 |
Document History
| Version | Date | Author | Notes |
|---|---|---|---|
| 0.1 | 2026-03-18 | Legal (AI-assisted) | Initial draft; B2B-scoped; coordinated with T&C v0.3 and DPA v0.1 |
| 0.2 | 2026-03-27 | Legal (AI-assisted) | Added e-signature data flows, Platform Maintainer access, Document Signer category, expanded retention table, cross-reference appendix |
| 0.3 | 2026-08-13 | Legal (AI-assisted) | Reconciled against T&C v0.5. Corrected modification cross-reference from 25.13 (Survival) to 25.14 (Modification of Terms). Added Passport Owner / Contributing Organization controller framework (Introduction), Section 22-A client warranties reference, business continuity and escrow access disclosure (3.4), public announcements (3.6), third-party retention (4.4), Contributing Organization post-termination notice (4.5), data localization right (8), successor e-signature provider (1.2), Platform Maintainer access logs as a data category (1.6, 4.1). Harmonized erasure request routing to support@realizse.com per T&C 15.4(a). Expanded Section 9 to enumerate all four permitted access circumstances. Updated open-item references to 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 DPA. Header gives the effective and last-updated dates; the internal status, owner and version lines are removed. Public Websites and the Service are each defined once (Introduction). Signer details, the signing audit trail and project participant data are handled for the Client under the DPA (Introduction, 1.2, 1.3, 1.6). Logs grouped as Service Logs (1.6); Usage Data narrowed, with de-identification commitments (2.4). IRS retention wording removed (2.4, 2.5); compliance records are kept seven years under T&C 15.1 (4.1, 4.2, 4.5). Vendor table replaced by the service-provider list in T&C 13.1 (3.1). Corrected Credentials on request, minimal personal details and backups (4.3); identity records removed when an account is disabled (4.4); export of all Client Data (5.4). Cookie and analytics wording matched to the Platform and www.realizse.com (1.4, 6). Wider Security Incident definition and notices to the account administrator (7). Fifth Platform Maintainer access purpose, content moderation limits and tax return information (9). |