Terms of Service

These Terms of Service ("Terms") are a binding agreement between Miraspaces OÜ, trading as Chaindoc ("Chaindoc", "we"), and the organisation or individual using the Chaindoc platform ("Customer", "you"). The Terms take effect on the earliest of: (a) when you click to accept, (b) the effective date of the applicable subscription, statement of work, or online purchase (the "Effective Date"), or (c) when you first access or use any Chaindoc product, API, or mobile service. If you do not agree to the Terms, do not use the Service.

1.1 Authority and Capacity

When you act on behalf of a company, agency, public authority, or another legal entity, you represent and warrant that (i) you have authority to bind that entity and its affiliates, (ii) you are authorised and have legal capacity to enter into contracts, and (iii) you will ensure that all users under your account comply with the Terms. The entity you represent is deemed the Customer; if your representation is inaccurate, you are personally liable.

1.2 Key Definitions

• Service: the Chaindoc web application, APIs, mobile apps, and any accompanying support or consulting services.
• Workspace: a tenant or environment within the Service used to manage documents, users, and processes.
• Subscription (Subscription Plan): any subscription plan, online checkout, or other Chaindoc subscription accepted by the parties.
• Customer Data: documents, templates, signature packets, metadata, credentials, and any other information the Customer uploads to the Service.

1.3 Contract Structure

These Terms incorporate, by reference, the Chaindoc Acceptable Use Policy, the Data Processing Addendum, feature-specific or regional terms, and any applicable Subscriptions (collectively, the "Supplemental Terms"). In case of conflict, the Subscription prevails, followed by the Supplemental Terms, then these Terms. Third-party procurement terms (for example, those issued by resellers) do not modify the Terms without Chaindoc’s written consent.

1.4 Affiliates and Procurement Channels

Customer’s affiliates may use the Service under Customer’s account, and Customer remains responsible for their compliance. If Customer acquires the Service through an authorised Chaindoc reseller or marketplace, Customer is still bound by these Terms; billing or renewal disputes must be resolved with that reseller and do not relieve Customer of obligations owed to Chaindoc.

Chaindoc provides a cloud platform for preparing agreements, automating document workflows, collecting legally binding electronic signatures, generating blockchain fingerprints, and maintaining audit logs (the "Service"). The Service includes the Chaindoc web application, APIs, mobile apps, and any SDKs or plugins we provide.

2.1 Subscription and Term

Access to the Service is provided on a subscription basis for the term stated in the Subscription or online checkout. Features and limits vary by plan. Certain capabilities (for example, advanced identity verification or higher limits) may require an upgraded plan or a separate subscription.

2.2 Usage Limits

Your use of the Service is subject to the limits in your plan (such as seats, transactions/signature packets, API requests, storage, etc.). Customer must not intentionally circumvent technical controls. Chaindoc does not expand limits or change plans automatically; increases take effect only after Customer updates the subscription in the admin console. The product exposes the key usage metrics, and Customer solely monitors and manages the subscription entitlements.

2.3 Modifications and Availability

Chaindoc may enhance or modify the Service to improve security, performance, or compliance, without materially reducing core functionality during a paid term. If an API or feature is deprecated, Chaindoc will provide reasonable notice and, where feasible, a migration path. Planned maintenance may temporarily affect availability; any SLA parameters are set out in the Subscription or applicable agreement.

2.4 Beta, Test, and Free Services

Features or environments labelled “Beta”, “Preview”, “Labs”, or “Sandbox” are for testing only, are not meant for production, may change or end at any time, and are provided without SLA or warranties to the extent permitted by law. Chaindoc may use your feedback to improve the Service.

2.5 Third-Party Services

The Service may integrate with external solutions (for example, storage, identity, or workflow tools). Enabling an integration instructs Chaindoc to exchange Customer Data with that provider. Chaindoc is not responsible for third-party terms, performance, or security; use of any third-party service is solely Customer’s choice.

2.6 Suspension

Chaindoc may suspend the Service, in whole or in part, if (a) a security or fraud risk is detected, (b) Customer materially breaches the Terms or the Acceptable Use Policy, (c) the subscription is unpaid (for example, a charge is declined or a card expires), or (d) Customer’s actions degrade the Service for others. Where feasible we will provide notice, and any suspension is limited to what is necessary.

2.7 Records, Retention, and Export

Customer is responsible for document retention policies and legal hold settings. Chaindoc provides tools to export documents, logs, and verification artifacts in common formats. Chaindoc blockchain fingerprints are publicly verifiable, contain no document content, and are immutable once published.

2.8 Legality of Electronic Signatures

The Service supports major e-signature frameworks (eIDAS, ESIGN, UETA). Customer determines whether an electronic signature is appropriate for a given transaction and delivers any required notices and disclosures. Certain matters (for example, specific real-estate, family-law, or estate transactions) may require wet signatures. Advanced or qualified signatures may need additional verification or certificates.

2.9 Professional Services

If professional services are purchased, their scope, deliverables, and pricing are set out in the applicable Subscription. Unless stated otherwise, deliverables are licensed for Customer’s internal use with the Service and are not works made for hire.

2.10 Documentation and Policies

Customer must use the Service according to Chaindoc documentation and published policies, including the Acceptable Use Policy and the Data Processing Addendum.

2.11 Trial Period

Chaindoc provides a free trial of up to one month. If Customer does not cancel before the trial ends, the subscription automatically converts to a paid plan and the associated fee is charged immediately. Unused trial time does not entitle Customer to extensions or refunds, and the trial may be terminated if the Terms are violated.

Customer is responsible for all activity on the Chaindoc platform.

3.1 Registration and Administrators

Customer appoints at least one Account Owner authorised to (a) create or close Workspaces, (b) assign or revoke roles, (c) approve plan changes, and (d) receive operational, financial, and legal notices. Chaindoc may rely on instructions from any Account Owner until Customer updates that role in the admin console.

3.2 Seats, Roles, and Sharing

Seats are assigned to specific individuals and cannot be shared concurrently. Customer may reassign a seat to another user for future periods. Roles (Owner, Admin, Editor, Viewer, API, etc.) define permissions. Customer maps roles to responsibilities and is liable for user actions.

3.3 Credentials, MFA, and Security

Customer (a) protects logins, passwords, and authentication factors; (b) enforces strong password and session policies; (c) enables multi-factor authentication where available; and (d) promptly disables accounts of departing personnel. Suspected unauthorised access must be reported to Chaindoc immediately.

3.4 API Keys, Webhooks, and Integrations

API keys, OAuth secrets, and webhook signatures are treated as credentials and require the same safeguards as passwords. Customer is responsible for use of its keys, including actions by scripts, service accounts, or integration partners. Keys must be rotated, stored securely, and scoped via Chaindoc controls. Rate limits and fair-use policies apply.

3.5 External Signers and Guests

Individuals who only view or sign a document are not counted as seats and their access is limited to the specific transaction, provided no optional features that require an upgraded paid subscription (for example, KYC or KYB) are enabled. Customer remains the controller of such individuals’ personal data and must provide required disclosures and obtain consents.

3.6 Configuration, Retention, and Legal Hold

Customer manages retention periods, archival rules, and legal hold policies for documents and logs. Deleting a document in the Service does not remove blockchain fingerprints that have already been published. Customer ensures retention settings satisfy regulatory and judicial requirements.

3.7 Billing Contact and Notices

Customer keeps billing contacts, legal address, and administrator email up to date. Customer agrees to receive routine operational, payment, and legal notices by email to the provided address. Notices are deemed delivered when sent.

3.8 Compliance with Law

Customer ensures its use of the Service complies with applicable laws, including e-signature, privacy, export-control, and sanctions rules. Customer represents that it and its users are not located in, organised under, or controlled by broadly sanctioned jurisdictions.

3.9 Resale and Transfer

Customer may not resell, rent, or sublicense the Service, nor share credentials with third parties except authorised integrators acting on Customer’s behalf under scoped API keys. Any assignment of the Terms requires Chaindoc’s prior written consent, except for permitted corporate reorganisations.

3.10 Engagement and Support

Customer supplies information needed to support the account (error reports, timestamps, non-sensitive logs). Chaindoc never requests access to a Customer Workspace or account and performs diagnostics solely using the data and telemetry provided.

Chaindoc supports the creation, delivery, and execution of electronic documents and signatures in line with major frameworks (eIDAS, ESIGN, UETA). Chaindoc is not a law firm and does not provide legal advice, so Customer is responsible for evaluating whether an electronic signature is permissible for each transaction.

4.1 Consent and Presentation

• Customer is responsible for obtaining consent for electronic interactions and delivering all required notices.
• Customer controls document content, signer order, deadlines, reminders, and acknowledgement fields.

4.2 Authentication and Identification

• Customer selects authentication methods (email link, one-time code, MFA, corporate SSO/IdP, or qualified trust service provider where available).
• Some methods incur fees or require separate agreements with identity providers. Customer must choose a method that matches the transaction’s risk and legal requirements.

4.3 Audit Trail and Blockchain Evidence

• The Service logs key events (envelope creation, views, consents, IP address and user agent, timestamps, signature actions) and generates an audit certificate attached to the final packet.
• Chaindoc computes a cryptographic hash of the contents and anchors it to a public blockchain. The hash reveals no contents and proves the document has not changed. Once recorded, the hash is immutable.

4.4 Integrity and Encryption

Chaindoc protects completed files against alteration (for example, PDFs with certificate metadata and per-page hashes). Any edits after completion invalidate the verification.

4.5 Storage and Retrieval

Chaindoc stores documents according to the selected plan and your retention settings. Chaindoc is not an archival service; Customer maintains retention schedules, legal hold rules, and exports copies and logs as needed.

4.6 Notarial Acts and Witnessing

If Customer enables notarisation, witnessing, or similar processes in the Service or via an integration, they are performed by the relevant provider under that provider’s terms. Customer is responsible for the legal sufficiency of the chosen process.

4.7 Prohibited or High-Risk Transactions

Certain transactions may be excluded from electronic execution or require wet signatures (for example, specific real-estate, family-law, or estate matters). Customer must confirm legality before sending such transactions through the Service.

4.8 Evidence Requests and Cooperation

Chaindoc will reasonably assist with lawful requests for transaction data (court orders, regulatory inquiries). Chaindoc may charge for actual costs and may require a protective order before sharing sensitive logs or backups.

4.9 Delivery of Final Copies

After completion, Chaindoc may provide Customer and signers with links or copies of executed documents and the audit certificate, based on configuration. Customer is responsible for furnishing final documents to signers as required by law.

Customer must use the Service lawfully and responsibly. Chaindoc may monitor and investigate suspicious activity and take action if it threatens the platform, other customers, or document integrity.

5.1 Prohibited Content and Conduct

Customer will not use the Service to create, store, or transmit unlawful, defamatory, misleading, obscene, or infringing content. Mass spam campaigns, chain letters, and phishing activity are strictly prohibited.

5.2 Security and Integrity

Customer will not upload malicious code, interfere with encryption, attempt to access another Customer’s Workspace, overload the Service with automated scripts, or bypass technical limits (request caps, API quotas). Credentials, API keys, and certificates must be protected per industry practice.

5.3 Regulatory and Payment Compliance

Documents and payment instructions sent through the Service must comply with sanctions, export-control, AML, and payment-network rules. The Service may not be used for illicit financial activity, unlicensed gambling, or operations that require special authorisations.

5.4 Identity and Record Integrity

Customer will not spoof signer identities, mask IP addresses, disable audit features, or misrepresent the evidentiary value of Chaindoc signatures, blockchain fingerprints, or verification tools. Notices and disclosures sent to signers must be accurate and complete.

5.5 Enforcement

Chaindoc may investigate suspected violations, suspend or limit access, and remove offending content. Where required by law, Chaindoc cooperates with regulators or law enforcement. Fees remain payable during any suspension caused by Customer’s violations.

Chaindoc’s fees are stated in the applicable Subscriptions ("Subscription"). All subscriptions are billed in advance in the Subscription currency and are non-refundable, including when Customer does not use the Service or the trial.

6.1 Automatic Charging

Chaindoc stores Customer’s authorised payment method and charges the subscription automatically at the start of each billing period or upon an upgrade. Individual invoices are not issued. If a payment fails, Customer must promptly update the payment details; access may be suspended until funds are received.

6.2 Self-Managed Plans

Chaindoc does not add seats, transactions, or other resources without Customer’s explicit action. When limits are reached, Customer selects a new plan or add-ons through the billing portal. The Service displays current usage metrics, and Customer alone ensures compliance with those limits; Chaindoc does not charge overages without a confirmed upgrade.

6.3 Taxes

Displayed fees exclude taxes. Chaindoc automatically adds applicable VAT, GST, or similar mandatory taxes based on Customer’s billing country and does not apply other government fees to the subscription. Customer is responsible for paying all such taxes together with the subscription fee.

6.4 Payments Within Business Documents

Business-plan customers may issue invoices and initiate payments directly inside documents (agreements, contracts). Those payments are processed by Stripe; Chaindoc retains a fee equal to Stripe’s fee for the transaction plus a 0.5% platform fee. Customer must inform its counterparties about the applicable fees.

6.5 Disputes

Customer must notify Chaindoc in writing within 15 days of a debit if an amount is disputed; the parties will work in good faith to resolve the issue. Undisputed amounts may not be withheld.

6.6 Suspension for Non-Payment

If the payment method is declined and funds are not received, Chaindoc may suspend the subscription until payment is made and may require prepayment for future periods. Suspension does not relieve Customer of amounts already due.

Chaindoc processes Customer Data solely to provide, protect, and support the Service, acting as the processor of personal data contained in Customer’s documents. The Chaindoc Data Processing Addendum ("DPA") is incorporated by reference.

7.1 Roles and Responsibilities

Customer remains the controller of personal data in its documents, determines the legal basis for processing, delivers required notices, and responds to data-subject requests. Chaindoc acts as the processor and handles data according to Customer’s documented instructions and the DPA.

7.2 Security Measures

Chaindoc maintains administrative, technical, and physical safeguards aligned with recognised standards, including encryption in transit and at rest, role-based access, key management, logging, and disaster-recovery planning. Details appear in the DPA or Chaindoc security documentation.

7.3 Subprocessors

Chaindoc may engage subprocessors for infrastructure, storage, identity verification, or support. A current list is available on request. Chaindoc imposes privacy and security obligations on subprocessors no less protective than those in the Terms and DPA and remains responsible for their performance.

7.4 Data Transfers

Chaindoc may process and store Customer Data in the EU, the US, and other jurisdictions where Chaindoc or its subprocessors operate. For transfers subject to GDPR or similar regimes, Chaindoc relies on appropriate mechanisms such as the EU Standard Contractual Clauses.

7.5 Incident Notification

Chaindoc will notify Customer without undue delay after confirming a security incident affecting Customer Data, provide available information, and assist with mitigation in accordance with law.

7.6 Data Subject Requests

Where legally permitted, Chaindoc will promptly inform Customer of data-subject or regulator requests concerning Customer Data and will provide reasonable assistance in responding to such requests.

7.7 Deletion and Retention

Upon subscription completion or termination, Chaindoc will delete Customer Data as described in the DPA, except for blockchain fingerprints and information retained to comply with law or resolve disputes. Customer may export documents and logs before deletion.

Chaindoc designs and operates the Service with layered safeguards and independent testing. Customer is responsible for configuring the Service to satisfy its own compliance requirements.

8.1 Security Program

Chaindoc maintains administrative, technical, and physical controls aligned with recognised standards, including access management, encryption in transit and at rest, key management, vulnerability management, secure development, and recovery plans. Documentation is available on request.

8.2 Audits and Reports

Chaindoc undergoes regular independent audits and assessments. Subject to reasonable confidentiality obligations, Chaindoc provides available reports or attestations (for example, SOC reports or pentest summaries). Customer may not run invasive testing without Chaindoc’s written consent.

8.3 Customer Responsibilities

Customer configures access, storage, and encryption within the Service and secures its own networks, devices, and credentials. Chaindoc is not responsible for security incidents caused by Customer’s configurations or by users/third parties under Customer’s control.

8.4 Cooperation and Remediation

If Chaindoc discovers a material vulnerability or incident affecting the Service, it will take commercially reasonable remedial actions and inform Customer consistent with Section 7. Customer will support investigations by providing relevant logs or information to the extent permitted by law.

8.5 Right to Verify

Where required by law or contract, Customer may request confirmation of Chaindoc’s compliance with its security obligations. Such verification is limited to reviewing available reports or a mutually agreed remote assessment and must not disrupt Chaindoc’s operations.

Chaindoc and its licensors own all rights in the Service, including the software, documentation, interfaces, APIs, templates, visual design, and any enhancements or derivative works. Customer owns the Customer Data uploaded to the Service.

9.1 Licence to Use

Subject to compliance with the Terms and payment of all fees, Chaindoc grants Customer a limited, non-exclusive, non-transferable right to use the Service and documentation for internal business purposes during the subscription term. All other rights remain with Chaindoc.

9.2 Customer Data

Customer grants Chaindoc a limited licence to process Customer Data solely to provide, maintain, and improve the Service and to meet legal obligations. Chaindoc does not obtain ownership of Customer Data. Customer represents it has all rights necessary to upload and distribute the data through the Service.

9.3 Feedback

If Customer or its users provide feedback, suggestions, or ideas about the Service ("Feedback"), Chaindoc may use them without restriction or compensation. Chaindoc is not obligated to implement Feedback.

9.4 Branding and Communications

Customer may use Chaindoc’s name and logos only in accordance with brand guidelines and solely to reference its use of the Service. Chaindoc may list Customer’s name and logo in customer lists and marketing materials unless Customer objects in writing.

9.5 Third-Party Components

Some features may include third-party or open-source software subject to their own licences. Chaindoc will disclose such components where required.

9.6 Protection

Except as permitted by law, Customer will not copy, modify, decompile, disassemble, or attempt to derive the source code of the Service. Chaindoc may employ legal and technical measures to prevent use of the Service in violation of the Terms.

Each party ("Receiving Party") will protect the other party’s ("Disclosing Party’s") confidential information with the same level of care it uses for its own confidential information, but no less than reasonable care. Confidential information includes business plans, technical data, customer information, pricing, security documentation, and any non-public information marked or reasonably understood as confidential.

10.1 Permitted Use and Disclosure

The Receiving Party may use confidential information only to perform its obligations or exercise its rights under the Terms and may disclose it solely to employees, contractors, advisors, or subprocessors who need to know it and are bound by comparable confidentiality obligations.

10.2 Exceptions

Confidential information does not include information that (i) becomes public through no fault of the Receiving Party, (ii) was lawfully known to the Receiving Party before disclosure, (iii) is independently developed without reference to the Disclosing Party’s information, or (iv) is received from a third party without restriction.

10.3 Compelled Disclosure

The Receiving Party may disclose confidential information when required by law if it (i) promptly notifies the Disclosing Party (unless prohibited), (ii) cooperates to obtain protective measures, and (iii) discloses only what is legally necessary.

10.4 Return or Destruction

Upon request or after termination, the Receiving Party will return or destroy the Disclosing Party’s confidential information, except for copies required to be retained by law or archived copies. Any retained copies remain subject to this Section.

10.5 Equitable Relief

Unauthorised use or disclosure of confidential information may cause irreparable harm. The Disclosing Party is entitled to seek injunctive relief or other equitable remedies in addition to available legal remedies.

Chaindoc may offer optional connectors, APIs, or listings that integrate with third-party services ("Third-Party Services"). Customer’s use of any such service is governed solely by the agreement between Customer and the provider.

11.1 Activation and Data Sharing

By enabling or authorising a Third-Party Service, Customer instructs Chaindoc to exchange Customer Data and credentials with the provider as needed. Chaindoc is not responsible for how the third party alters, deletes, or uses Customer Data.

11.2 Compliance and Permissions

Customer evaluates the security, privacy, and compliance requirements of each Third-Party Service and ensures it has the rights and consents needed for the integration. Chaindoc may disable an integration if its use creates a security risk or violates law or policy.

11.3 Support and Availability

Chaindoc does not provide warranties or support for Third-Party Services. If an external service becomes unavailable or incompatible with the Service, Chaindoc may suspend or terminate the integration without liability. Customer’s payment obligations to Chaindoc remain in effect. The “Partnership” page lists Chaindoc technology partners who can assist with integrations and additional services.

11.4 Marketplace and Resellers

Listings, ratings, or certifications in the Chaindoc marketplace are informational and do not constitute endorsements. When purchasing a Third-Party Service or Chaindoc offering through a reseller, Customer remains bound by these Terms and addresses billing and SLA matters directly with the reseller.

11.5 Third-Party Claims

Customer will not hold Chaindoc liable for losses or claims arising from use of Third-Party Services. If a third-party provider asserts a claim against Chaindoc due to Customer’s acts or omissions, Customer will defend and indemnify Chaindoc pursuant to the applicable indemnity terms (for example, Section 18, if provided).

The Terms start on the Effective Date and remain in force for the subscription term stated in the Subscription. Unless otherwise specified, self-service subscriptions automatically renew for successive periods.

12.1 Renewal and Pricing

Chaindoc may change renewal pricing by giving at least 30 days’ notice before the current term ends. Customer may prevent renewal via the billing portal or by notifying Chaindoc in writing before the renewal date.

12.2 Termination for Cause

Either party may terminate the relevant Subscription or the Terms for a material breach not cured within 30 days after notice (10 days for payment breaches). Chaindoc may terminate immediately in case of Customer bankruptcy, insolvency, or severe violations of the Acceptable Use Policy.

12.3 Effect of Termination

Upon expiration or termination, Customer’s right to access the Service ends. Customer may export its data for 30 days provided the subscription is paid and access remains active; afterwards Chaindoc will delete it per Section 7.7, except for copies retained for legal obligations or audit. Fees accrued before termination are non-refundable, and unused periods (including trials) are not credited unless required by law or the Subscription.

12.4 Suspension

Chaindoc may suspend the Service or a Workspace if (i) the subscription is unpaid (for example, a charge is declined or the card limit is reached), (ii) a security or fraud risk is detected, or (iii) Customer’s use threatens the Service or violates law. Chaindoc will limit the suspension to what is necessary and restore access once the issue is resolved.

Chaindoc warrants that it will provide the Service in a professional manner consistent with generally accepted industry standards and that the Service will substantially conform to the Documentation during the applicable period.

13.1 Customer Warranties

Customer represents that it has obtained all rights, permissions, and consents necessary to submit Customer Data to the Service and to grant Chaindoc the right to process that data under the Terms.

13.2 Disclaimer

Except for the express warranties above, the Service, APIs, documentation, and support are provided “as is”. Chaindoc disclaims all other warranties—express, implied, statutory—including merchantability, fitness for a particular purpose, title, and non-infringement. Chaindoc does not warrant uninterrupted or error-free operation, freedom from harmful components, or that Customer Data will remain intact without loss.

13.3 Liability Cap

To the fullest extent permitted by law, each party’s aggregate liability under the Terms is limited to the fees paid or payable by Customer to Chaindoc during the 12 months preceding the claim. The cap applies to all claims regardless of theory.

13.4 Exceptions

The limitation in Section 13.3 does not apply to (i) Customer’s payment obligations, (ii) a party’s gross negligence or wilful misconduct, (iii) indemnification obligations if provided, or (iv) Customer’s breach of Sections 5 (Acceptable Use) or 9.6 (Reverse Engineering).

13.5 Remedies

The parties agree that the limitations and disclaimers in this Section are an essential part of the bargain, and the pricing reflects the allocation of risk.

Unless a Subscription specifies another jurisdiction, the Terms are governed by the laws of Estonia, excluding conflict-of-law rules. The courts of Tallinn have exclusive jurisdiction over disputes arising out of or relating to the Terms, and each party consents to that jurisdiction and venue.

14.1 Injunctive Relief

Nothing in the Terms prevents either party from seeking injunctive or other equitable relief to protect intellectual property, Confidential Information, or compliance obligations.

14.2 Negotiation

Before initiating formal proceedings, the parties will use reasonable efforts to resolve the dispute through negotiations between senior representatives. This requirement does not prevent either party from seeking urgent relief.

14.3 Legal Compliance

Each party complies with applicable laws and regulations while performing the Terms, including anti-corruption, sanctions, and export-control laws.

Chaindoc may make commercially reasonable changes to the Service, provided they do not materially reduce core functionality during the current term.

15.1 Updating the Terms

Chaindoc may update the Terms and referenced policies to reflect changes in the Service, law, or business needs. Material changes take effect 30 days after notice (or sooner if required by law). By continuing to use the Service after that date, you accept the updated Terms.

15.2 Notice Methods

Chaindoc may communicate changes via email, in-product messages, or postings in the admin console or Trust Center. Customer must keep contact information current.

15.3 Objections

If Customer objects to a material change that materially and adversely affects it, Customer must notify Chaindoc within 30 days after the change takes effect. Chaindoc will review the objection in good faith; if unresolved, Customer may terminate the affected Subscription by giving notice within 30 days, and Chaindoc will refund prepaid amounts for the period after termination.

15.4 Preview Features

Beta or preview features may change at any time without notice and are provided without warranties, SLAs, or support. Customer’s obligations under the Terms continue to apply when using them.

16.1 Assignment

Neither party may assign the Terms without the other party’s prior written consent, except to an affiliate or in a merger, acquisition, or sale of substantially all assets, provided the successor assumes all obligations. Invalid assignments are void.

16.2 Entire Agreement

The Terms, together with the Subscription, the DPA, and referenced policies, form the entire agreement between the parties and supersede all prior or contemporaneous arrangements on the subject matter.

16.3 Waiver

Failure to exercise a right is not a waiver. Any waiver must be in writing and signed by the waiving party.

16.4 Severability

If any provision is deemed unenforceable, the remaining provisions remain in effect, and the unenforceable provision will be replaced with an enforceable one that best reflects the parties’ intent.

16.5 Independent Contractors

The parties are independent contractors; nothing in the Terms creates a partnership, joint venture, or agency relationship.

16.6 Force Majeure

Neither party is liable for failure or delay (other than payment obligations) caused by events beyond reasonable control, including natural disasters, acts of government, labour disputes, or internet outages, provided the affected party mitigates the impact and resumes performance once the impediment is removed.

16.7 Notices

Formal notices must be sent in writing to the contacts listed in the Subscription and, for Chaindoc, also to legal@chaindoc.io. Electronic notices are deemed delivered when sent; mailed notices upon receipt.

Company address

Harju maakond, Tallinn, Lasnamäe linnaosa, Katusepapi tn 6-502, 11412, Estonia.