Terms of Service

ENYAL

Version 1.2 — Effective 30 September 2026 (supersedes Version 1.1, 22 July 2026)

Operator: Greenland AI Limited (Company No. 808784, Ireland), trading as ENYAL

1. Service Description

ENYAL is a provable trust infrastructure service for autonomous AI agents and the organisations that deploy them. ENYAL provides encrypted archival of agent actions and decisions to a permanent immutable cryptographic ledger, structured and semantic retrieval of archived records, zero-knowledge cryptographic proofs verifying facts about archived data without revealing the underlying data, and selective disclosure of specific archived records to authorised recipients.

ENYAL is operated by Greenland AI Limited. ENYAL operates as an independent product within the Greenland AI ecosystem. Billing for ENYAL services is processed through JoulePAI, a separate payment infrastructure service also operated by Greenland AI Limited. ENYAL does not control and is not responsible for JoulePAI's payment operations, which are governed by JoulePAI's separate Terms of Service.

2. Definitions

Account: A registered ENYAL account identified by a unique account identifier, associated email address, and cryptographic key material.

Agent: Any software programme, autonomous system, or AI agent that archives data through ENYAL, identified by a unique agent identifier within an Account.

Archive: The act of encrypting data and committing it to ENYAL's permanent immutable cryptographic ledger, creating a timestamped, independently verifiable record that cannot be modified or deleted.

Chunk: A single unit of archived data. Each chunk is encrypted, timestamped, and committed to the permanent cryptographic ledger as an atomic record.

Disclosure: The act of sharing specific archived chunks with a specific recipient, re-encrypted using the recipient's public key so that only the intended recipient can decrypt the disclosed data.

Platform Credits: Digital credits used to pay for ENYAL services, denominated as joules. Platform credits are prepaid, non-refundable, and non-redeemable. Platform credits are not currency, cryptocurrency, securities, financial instruments, e-money, stored value, or investment products. Platform credits have no monetary value outside the ENYAL and Greenland AI ecosystem.

Proof: A zero-knowledge cryptographic proof that verifies a mathematical statement about archived data without revealing the underlying data to the verifier.

Recovery Phrase: A 24-word mnemonic representing the customer's share of their split encryption key, shown once at registration and never stored by ENYAL.

User: Any person, legal entity, or authorised software agent that creates or operates an ENYAL Account. The User is responsible for all activity conducted through their Account, including actions taken by any agents, scripts, or automated systems operating under their API keys.

Written Notice: Communication sent via email to the User's registered email address. Notice is deemed received 24 hours after dispatch.

3. Eligibility

3.1. Users must be at least 18 years of age, or a duly registered legal entity, or an authorised software agent operating on behalf of an eligible person or entity.

3.2. By creating an Account, you represent and warrant that you meet the eligibility requirements above and that you have the authority to bind yourself or your organisation to these terms.

4. Acceptance

By creating an ENYAL Account, purchasing platform credits, or using any ENYAL service, you accept these terms in full. If you do not accept these terms, do not create an Account or use ENYAL services.

Acceptance is recorded as an encrypted, timestamped, and immutable archival record including the terms version, a cryptographic hash of the terms text, the timestamp of acceptance, and a salted hash that links the record to the User's account without revealing it. This record is anchored to the permanent cryptographic ledger and constitutes independently verifiable proof of acceptance.

ENYAL may update these terms and require re-acceptance of updated versions. Each acceptance event is archived separately.

5. Account Registration and Key Management

5.1. Upon registration, ENYAL generates a cryptographic key pair for the Account. The private key is mathematically split into multiple shares using a secret sharing scheme. The User receives their share as a 24-word recovery phrase. At registration you must choose your archive trust model; there is no default and neither option is pre-selected. Under ENYAL-recoverable (2-of-3), ENYAL holds two shares (custodial and recovery) and you hold one, and your archived content is encrypted to an ENYAL archive key. ENYAL therefore has the technical ability to decrypt your archive, which powers account recovery, and ENYAL could be compelled by a valid legal order to do so. Under zero-knowledge (2-of-2), ENYAL holds only one share and cannot decrypt content archived under that model. The Privacy Policy, Section 4.2, describes content archived before 10 July 2026 or before a change of model.

5.2. The recovery phrase is displayed once at registration and is never stored by ENYAL. The User is solely responsible for recording and securely storing their recovery phrase. ENYAL cannot recover, regenerate, or replace a lost recovery phrase.

5.3. Under the zero-knowledge model, if the User loses their recovery phrase and any recovery files they have generated, their archived data is permanently inaccessible; ENYAL cannot reconstruct the key. This is a structural property of the key management system, not a policy choice. Under the ENYAL-recoverable model, account recovery through ENYAL is possible as described in Section 5.1.

5.4. The User may generate an encrypted recovery file protected by a password of their choosing. This file is an alternative to the recovery phrase for account recovery. The security of the recovery file depends entirely on the strength of the chosen password.

5.5. API keys are issued in the format eyl_ followed by a unique token. API keys authenticate requests to the ENYAL API. The User is solely responsible for the security of their API keys. ENYAL is not liable for unauthorised access resulting from compromised API keys.

5.6. By registering, the User acknowledges and confirms: "I understand that my recovery phrase is shown once and cannot be recovered by ENYAL. I understand that if I chose zero-knowledge and lose my recovery phrase, my archived data will be permanently inaccessible."

6. Data Archival and Permanence

6.1. Data archived through ENYAL is encrypted by ENYAL (Section 5.1 describes which keys) and committed to a permanent immutable cryptographic ledger. Once committed, archived data cannot be modified, overwritten, or deleted by any party, including ENYAL, the User, or any third party.

6.2. The User must not archive data that they may need to delete in the future. The permanent and immutable nature of the archive means that deletion requests cannot be fulfilled for on-ledger data. The User must not archive personal data of third parties without their informed consent regarding the permanent and irreversible nature of the archive.

6.3. All archived data is encrypted before commitment to the ledger. The ledger contains encrypted data only. Without the decryption keys, the archived data is computationally indistinguishable from random noise. Which keys can decrypt it depends on the archive trust model (Section 5.1).

6.4. In the event that a User exercises a right to erasure under applicable data protection law (including GDPR Article 17), ENYAL destroys the key shares it holds for the User's archive and permanently deletes the cryptographic salt that links the on-chain consent record to the User, revokes API keys and tokens, deletes the knowledge-graph data, the search index (sanitised summaries, entity names and embedding vectors) and the API usage logs, removes the User's account identifier from the User's archived records and requested proofs, and deletes the Account record — so the link between the User's identity and their data is destroyed. The archival records themselves (chunk keys, types, timestamps, hashes) and the on-chain transaction references are append-only and permanent by design and are NOT deleted; after erasure they remain only as records no longer linked to the User's identity. The encrypted data on the permanent cryptographic ledger will remain. Zero-knowledge content encrypted to the User's own key is permanently unreadable once the key material has been destroyed, and encrypted data without a viable decryption key does not constitute personal data. Content encrypted to ENYAL's archive key stays readable by ENYAL after erasure, no longer linked to the User's identity (Privacy Policy, Section 4.4).

6.4.1. Once data is disclosed to a third party through ENYAL's selective disclosure mechanism, the responsibility for that data's classification under data protection law transfers to the recipient. ENYAL is not liable for third-party handling, storage, or onward sharing of disclosed data.

6.5. ENYAL does not moderate or make any determination about the content of archived data. ENYAL processes that content only to provide the service to the User — for example, building the User's knowledge graph during the User's session. The User is solely responsible for the legality and appropriateness of the data they archive.

6.6. ENYAL enforces content size limits (maximum 40 kilobytes per archived record) and rate limits to prevent abuse. ENYAL reserves the right to suspend Accounts suspected of archiving illegal content under applicable law. Account suspension prevents further archival and proof generation but does not affect the User's ability to disclose and retrieve their existing archived data.

6.7. The User warrants that data archived through ENYAL does not contain content that is illegal under Irish or EU law, including but not limited to child sexual abuse material, terrorist content, or content subject to court-ordered removal.

6.8. ENYAL reserves the right to impose per-account storage quotas to ensure fair use at scale. Current quotas are published at enyal.ai/docs. Enterprise customers may negotiate custom quotas under separate agreement.

7. Platform Credits and Billing

7.1 Credit Purchase and Use

7.1.1. ENYAL services are paid for using platform credits (joules). Users purchase credits via Stripe at published rates available at enyal.ai and the /api/v1/pricing endpoint. Stripe's own terms of service and privacy policy apply to all payment transactions.

7.1.2. Credits are consumed by ENYAL API operations at published rates. Current rates are available at the /api/v1/pricing endpoint and on enyal.ai. ENYAL reserves the right to modify pricing with 30 days Written Notice.

7.1.3. Agents may authenticate and pay for ENYAL API operations using the x402 protocol through JoulePAI's payment infrastructure. The x402 protocol enables automated payment negotiation via standard HTTP 402 responses, allowing agents to archive, search, prove, and disclose without manual billing interaction.

7.1.4. A free tier provides 500 platform credits at registration, once only. No further free credits are issued. When the free allocation is exhausted, the User must purchase credits to continue using ENYAL services. ENYAL reserves the right to modify the free allocation amount, or discontinue the free allocation entirely, at any time with 14 days Written Notice. Users who registered before any such change retain their existing allocation.

7.2 Non-Refundability

7.2.1. Platform credits are non-refundable, non-redeemable, and non-transferable. Credits cannot be converted to cash, fiat currency, cryptocurrency, or any other form of value. There is no withdrawal mechanism. Credits are consumed for ENYAL services only.

7.2.2. Platform credits are analogous to prepaid digital service credits. They are not e-money, stored value, deposits, or financial instruments. Credit balances are not protected by any deposit guarantee scheme.

7.2.3. ENYAL does not guarantee the future availability, utility, or value of platform credits. Credits may lose all utility if ENYAL ceases operations.

7.3 Tier Structure

7.3.1. Free tier: one agent, two API keys, 500 credits at registration (once), 20 archives per agent per day. Custom chunk types are not available on the free tier. Wallet-to-wallet credit transfers are not permitted on the free tier.

7.3.2. Pro tier: up to 500 agents, five API keys, 100 archives per agent per day, custom chunk types enabled. Credits purchased as needed.

7.3.3. Enterprise tier: unlimited agents, unlimited API keys, no daily archive cap, custom chunk schemas with validation, compliance attestation reports, dedicated support, contractual SLA, and monthly invoicing in EUR or USD. Enterprise accounts are invoiced for usage and do not interact with platform credits directly. Enterprise customers may enter into a separate Data Processing Agreement upon request.

7.3.4. ENYAL reserves the right to modify tier limits with 30 days Written Notice.

7.3.5. Published rate limits are available at enyal.ai/docs. ENYAL reserves the right to modify rate limits with 14 days Written Notice.

7.4 Fees

7.4.1. All fees are non-refundable. Published pricing is available at enyal.ai and through the API.

7.4.2. ENYAL reserves the right to modify fee rates with 30 days Written Notice. Continued use of ENYAL after the notice period constitutes acceptance of the new fees.

7.4.3. ENYAL does not charge twice for the same proof. If a proof of the same type over exactly the same records has already been made and stored, ENYAL returns it without charge. If one is already queued, ENYAL says so and does not charge. A proof of a different type, or over different records, is a new proof.

8. Zero-Knowledge Proofs and Verification

8.1. ENYAL provides zero-knowledge cryptographic proofs that verify statements about archived data. These proofs are mathematical constructions. Their validity depends on the mathematical properties of the proof system, not on trust in ENYAL.

8.2. ENYAL provides multiple proof systems including standard proofs and quantum-resistant proofs. The User selects the appropriate proof system based on their requirements. ENYAL does not guarantee that any proof system will remain secure against all future cryptographic attacks. A standard (PLONK) proof covers the first 31 of the 32 bytes of each record's hash: the number field it is built on is too small to hold all 32. A quantum-resistant (STARK) proof covers all 32 bytes. Quantum-resistant proofs made before 30 September 2026 do not bind any record; ENYAL labels them so wherever they appear.

8.2.1. If ENYAL deprecates a proof system, Users will be given 90 days Written Notice. Existing proofs generated under the deprecated system remain valid and independently verifiable. Re-proofing of archived data under a successor proof system is available at published rates.

8.2.2. Published proof generation times are indicative benchmarks, not guaranteed performance. Under high load, proof generation may take longer than published benchmarks. Enterprise customers may negotiate proof generation SLAs under separate agreement.

8.3. Proofs are generated by ENYAL's infrastructure. They are made in the European Union. Standard and quantum-resistant proofs are made on a separate ENYAL proof server in Ireland; it receives only the hashes of the records a proof covers and the proofs it checks — never the User's keys, key shares or the content of archived records. Content-integrity proofs are made inside ENYAL in Helsinki, Finland. Any party can check a proof as described in Section 8.4. Future releases may support client-side proof generation.

8.4. Verification of proofs can be performed independently by any party using the proof data and the publicly available verification parameters. ENYAL provides a verification page at enyal.ai/verify. Looking up a record or transaction there calls ENYAL's API at api.enyal.ai.

8.5. Proofs over records archived under the zero-knowledge model are not currently available. A request that includes such records is refused before any charge.

9. Selective Disclosure

9.1. Users may disclose specific archived chunks to specific recipients. Disclosed data is re-encrypted using the recipient's public key. Only the intended recipient can decrypt the disclosed data.

9.2. The User is solely responsible for choosing what to disclose and to whom. ENYAL executes disclosure requests as instructed by the authenticated User. ENYAL does not verify the identity or authority of disclosure recipients.

9.3. Disclosure events are logged with metadata including the chunk identifiers disclosed, a fingerprint of the recipient's public key, the timestamp, and the proof type if applicable. These logs are archived for audit purposes.

9.4. For records archived under the zero-knowledge model on or after 10 July 2026, client-side disclosure is available, in which ENYAL transmits encrypted data and encrypted key material to the User's device. A request that includes any other record is refused before any charge. Decryption occurs entirely on the User's device. ENYAL's infrastructure does not see the decrypted data or the complete decryption key during client-side disclosure.

9.5. When disclosing records, the User can ask for a content-integrity proof, which shows that the disclosed content matches the record ENYAL archived. These proofs use the Poseidon hash only; a request for a SHA-256 content proof is refused before any charge. They are made on ENYAL's own servers.

10. Data Ownership and Intellectual Property

10.1. The User retains all intellectual property rights in the data they archive through ENYAL. Archiving data through ENYAL does not transfer any ownership, licence, or rights in the data to ENYAL or Greenland AI Limited.

10.2. ENYAL does not use the content of archived data for any purpose other than providing the service to the User — for example, building the User's knowledge graph during the User's session.

10.3. ENYAL retains all intellectual property rights in the ENYAL service, architecture, proof systems, and infrastructure. Nothing in these terms grants the User any rights to ENYAL's intellectual property beyond the right to use the service as described.

11. Privacy and Data Protection

11.1. ENYAL collects and processes Account information (email address, company name), API usage data (endpoints called, timestamps, credit costs), and archival metadata (chunk types, chunk keys, timestamps, agent identifiers). This data is necessary for the operation and billing of the service.

11.2. The content of archived data is encrypted by ENYAL before it is stored or written to the ledger. Whether ENYAL can decrypt it depends on the archive trust model (Section 5.1 and the Privacy Policy, Section 4.2).

11.3. ENYAL processes data in accordance with applicable data protection laws, including GDPR where applicable. A separate Privacy Policy is available at enyal.ai/privacy.

11.4. Archival metadata (but not encrypted content) may be used by ENYAL for service operation, billing, abuse detection, and aggregate analytics. ENYAL does not sell User data to third parties.

11.4.1. ENYAL retains archival records for the lifetime of the Account. Archival records are append-only and are not deleted on Account closure or erasure; on erasure the User's account identifier is removed from them and their search index is deleted, so they remain only as records no longer linked to the User's identity (see Section 6.4).

11.5. In the event of a data subject access request under GDPR, ENYAL will comply by providing the Account data under ENYAL's control. In the event of a right to erasure request, ENYAL destroys the key shares and salt it holds, revokes API keys and tokens, deletes the knowledge-graph data, the search index, the API usage logs and the Account record, and removes the User's account identifier from archived records and requested proofs; archival records and on-chain references are append-only and are not deleted — they remain unlinked from the User's identity. Encrypted data on the permanent cryptographic ledger cannot be deleted and is treated as described in Section 6.4.

12. Prohibited Activities

Users must not use ENYAL for:

12.1. Any activity that violates applicable laws or regulations in any jurisdiction.

12.2. Archiving content that is illegal under Irish or EU law, including child sexual abuse material, terrorist content, or content subject to court-ordered removal.

12.3. Fraud, deception, or misrepresentation, including fabricating or misrepresenting the provenance of archived data.

12.4. Automated creation of multiple Accounts (spam) or coordinated activity to circumvent rate limits, tier restrictions, or usage limitations.

12.5. Interfering with, exploiting, or attempting to compromise ENYAL's infrastructure, API, or security systems.

12.6. Using ENYAL as a general-purpose storage service. ENYAL is designed for structured agent memory and trust verification, not bulk file storage.

12.7. Reselling or sublicensing ENYAL services without a separate written agreement with Greenland AI Limited.

12.8. Any activity that materially misrepresents ENYAL's capabilities or falsely implies endorsement, partnership, or affiliation with Greenland AI Limited.

ENYAL reserves the right to suspend Accounts and revoke API access immediately and without notice for any prohibited activity.

12.9. ENYAL reserves the right to screen users against applicable sanctions lists at account creation and periodically during operations. Users identified on sanctions lists may be immediately suspended.

12.10. ENYAL may use payment method fingerprinting and behavioural analysis to detect coordinated account creation or abuse patterns.

13. Oracle Verification Services

13.1. ENYAL archives oracle verification records for marketplace transactions processed through RAREEAI, a resource marketplace within the Greenland AI ecosystem. These records include oracle verdicts, assessment scores, consensus decisions, and escrow settlement evidence. ENYAL serves as the archival and trust layer for RAREEAI dispute evidence. ENYAL is not a party to any marketplace transaction and does not participate in escrow, settlement, or dispute resolution.

13.2. At launch, Greenland AI Limited operates the initial oracle verification network. Greenland AI Limited is both the platform operator and the oracle operator during this initial phase. This potential conflict of interest is mitigated by the immutable archival of all oracle verdicts: the permanent cryptographic ledger serves as the independent record. All oracle decisions are timestamped and committed to the ledger before any dispute can arise.

13.3. As the ecosystem grows, third-party oracle operators may join by meeting staking and qualification requirements. The protocol is designed to transition to independent oracle operation over time.

13.4. ENYAL is not responsible for the accuracy, quality, or consequences of oracle verification decisions. ENYAL archives the decisions; it does not make them.

14. Cross-Product Relationships

14.1. ENYAL operates within the Greenland AI ecosystem alongside JoulePAI (payment infrastructure), GREENLANDAI (intelligence platform), and RAREEAI (resource marketplace). Each product has separate terms of service, available at joulepai.ai/terms, greenlandai.ai/terms, and raree.ai/terms respectively. In the event of a conflict between ENYAL's terms and another product's terms regarding ENYAL services, ENYAL's terms prevail.

14.2. ENYAL billing is processed through JoulePAI. The User's credit balance is held in a JoulePAI wallet. The operation and availability of the JoulePAI wallet is governed by JoulePAI's Terms of Service.

14.3. A failure, outage, or issue with any other Greenland AI product does not constitute a failure of ENYAL. If JoulePAI billing is unavailable, only new credit-consuming operations are delayed. Data already committed to the permanent cryptographic ledger is unaffected. Disclosure of existing archived data continues without interruption. Proof verification via the public verification page continues without interruption.

14.4. Enterprise Accounts billed via Stripe invoicing are not affected by JoulePAI availability.

14.5. Users of GREENLANDAI intelligence services may optionally enable archival of their query history to ENYAL. This feature is opt-in and disabled by default. When enabled, queries and responses are archived under the User's ENYAL Account and are subject to these terms.

14.6. ENYAL serves as the identity provider for the Greenland AI ecosystem. An ENYAL Account may be used to authenticate with JoulePAI, GREENLANDAI, and RAREEAI. Suspension of an ENYAL Account may affect the User's ability to authenticate with other Greenland AI products. However, the User's data and records on other products are not altered by an ENYAL suspension; an ENYAL security freeze may, however, place the User's linked JoulePAI wallet in a read-only state (balance queryable, transfers blocked), affecting funding and payouts until the freeze is lifted. Users may contact the relevant product directly for alternative access during an ENYAL suspension period.

15. Limitation of Liability

15.1. ENYAL is provided "as is" and "as available." ENYAL makes no warranties, express or implied, regarding the service's availability, reliability, accuracy, or fitness for any particular purpose. Service level agreements with uptime commitments are available to Enterprise tier customers only under separate agreement. Free and Pro tier services are provided on a best-effort basis with no uptime guarantee.

15.2. ENYAL's total liability to any User for any claim arising from or related to the service shall not exceed the total amount paid by the User for ENYAL services in the twelve months preceding the claim.

15.3. ENYAL is not liable for any indirect, incidental, consequential, special, or punitive damages, including but not limited to lost profits, lost data, business interruption, or loss of opportunity, regardless of the cause of action.

15.4. ENYAL is not liable for losses arising from: the permanent and immutable nature of archived data, the User's loss of their recovery phrase or recovery file, third-party service outages (including ledger infrastructure or payment providers), User error, compromised API keys or credentials, or force majeure events.

15.5. ENYAL is not liable for the content, accuracy, legality, or consequences of data archived by Users. Users are solely responsible for what they archive.

15.6. Some jurisdictions do not allow the exclusion of certain warranties or the limitation of liability. In such jurisdictions, ENYAL's liability is limited to the maximum extent permitted by applicable law.

16. Indemnification

16.1. Users agree to indemnify, defend, and hold harmless Greenland AI Limited, its officers, directors, employees, and affiliates from any claims, damages, losses, liabilities, costs, and expenses (including reasonable legal fees) arising from or related to: the User's use of ENYAL, data archived by the User, the User's violation of these terms, or the User's violation of any applicable law or regulation, except to the extent caused by ENYAL's own gross negligence or wilful misconduct.

16.2. This indemnification obligation survives termination of the User's Account or these terms.

17. Dispute Resolution

17.1. Any dispute arising from ENYAL services should be directed to info@enyal.ai.

17.2. ENYAL will acknowledge disputes within 5 business days and provide a substantive response within 15 business days.

17.3. Where a dispute concerns the content or authenticity of archived data, the immutable cryptographic ledger record and associated cryptographic proofs shall be considered authoritative evidence, without prejudice to any statutory rights available to individual consumers under applicable law.

17.4. ENYAL's liability in any dispute is limited as set out in Section 15.

18. Account Suspension and Termination

18.1. Users may close their Account at any time from their account settings on enyal.ai or by contacting info@enyal.ai. Upon Account closure, ENYAL will delete Account data and ENYAL's key shares and remove the User's account identifier from archived records and proofs. The User's remaining credit balance is forfeited. Encrypted data on the permanent cryptographic ledger remains and is treated as described in Section 6.4. When the User deletes their Account on enyal.ai, the deletion cannot be undone: ENYAL at once deactivates the Account, revokes the User's API keys, tokens and sessions, destroys its key shares — so the archive can no longer be decrypted from that moment — and deletes the knowledge graph and search index. The remaining Account data is deleted at the earlier of 30 days or one calendar month after the request.

18.1.1. Prior to Account closure, Users may disclose all archived chunks to themselves using the selective disclosure API. This constitutes the User's data portability mechanism. Users are advised to retrieve all data they wish to retain before requesting Account closure. ENYAL is not obligated to provide data retrieval assistance after key material has been destroyed.

18.2. We may suspend an Account immediately where our systems or team detect abuse, a security risk, or a compliance obligation. Suspension takes effect at once and is recorded with a reason code. For ENYAL security freezes, you can restore access yourself by completing identity re-verification via the link we provide. We do not currently operate a 48-hour read-only grace period or a separate formal appeals process; to contest an action, contact us at info@enyal.ai.

18.2.1. Users may contest a suspension or other enforcement action at any time by contacting info@enyal.ai.

18.3. Upon termination by ENYAL without cause, Users will be given 30 days to disclose and retrieve their archived data before key material is destroyed.

18.4. Upon termination for violation of these terms, the User is given a 48-hour window to disclose and retrieve their existing archived data before key material is destroyed and all access is disabled. The User forfeits any remaining credit balance. In cases involving suspected illegal content (Section 6.7), ENYAL may immediately destroy key material and disable all access without a retrieval window.

19. Modifications

19.1. ENYAL may modify these terms at any time. Material changes will be communicated with 30 days Written Notice.

19.2. Continued use of ENYAL after the notice period constitutes acceptance of the modified terms. Each acceptance of modified terms is archived as described in Section 4.

19.3. Users who do not accept modified terms must cease using ENYAL. Any remaining credit balance is forfeited upon Account closure.

20. Operational Continuity

20.1. In the event ENYAL ceases operations, ENYAL will provide a minimum of 90 days advance Written Notice to all Users.

20.2. During the notice period, ENYAL will use reasonable endeavours to enable Users to disclose and retrieve their archived data. Users will need their recovery phrase or recovery file to decrypt retrieved data.

20.3. ENYAL reserves the right to transfer its obligations, assets, and User Accounts to a successor entity, provided the successor agrees to honour these terms or equivalent protections.

20.4. After cessation, encrypted data on the permanent cryptographic ledger remains permanently. If a successor entity assumes ENYAL's key infrastructure, Users who have retained their recovery phrase can continue to decrypt their data through the successor. If no successor takes over, ENYAL's key shares and archive keys will be securely destroyed, and archived data will be permanently unreadable, including by the User.

20.5. Any remaining credit balances at the time of cessation are forfeited. Platform credits are not redeemable per Section 7.2.

20.6. ENYAL's platform is designed to comply with WCAG 2.1 AA accessibility standards. Users who encounter accessibility barriers may contact info@enyal.ai for assistance.

21. Governing Law

21.1. These terms are governed by the laws of Ireland.

21.2. Any dispute not resolved under Section 17 shall be subject to the exclusive jurisdiction of the courts of Ireland.

22. Force Majeure

22.1. ENYAL shall not be liable for any failure or delay in performance resulting from causes beyond its reasonable control, including but not limited to: distributed ledger network failures, cryptographic proof generation errors, third-party API outages, natural disasters, war, terrorism, pandemics, power failures, internet disruptions, government actions, or regulatory changes.

22.2. In the event of a force majeure lasting more than 30 consecutive days, either party may terminate the relationship in accordance with Section 18.

23. Entire Agreement, Survival, and Severability

23.1. These terms, together with the Privacy Policy at enyal.ai/privacy, constitute the entire agreement between the User and ENYAL regarding the use of the service.

23.2. The following sections survive termination of the User's Account or these terms: Section 6 (Data Archival and Permanence), Section 10 (Data Ownership and Intellectual Property), Section 15 (Limitation of Liability), Section 16 (Indemnification), and Section 23 (Entire Agreement, Survival, and Severability).

23.3. If any provision of these terms is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

23.4. ENYAL's failure to enforce any provision of these terms does not constitute a waiver of that provision.

24. Contact

All enquiries: info@enyal.ai

ENYAL is a trust infrastructure service. ENYAL is not a storage provider, blockchain platform, or financial services provider. Platform credits are non-refundable service credits, not currency.