Terms of Service & EULA

1. Definitions

The following capitalised terms have the meanings set out below throughout these Terms:

• Account — the registered user identity authenticated via Firebase Authentication.
• Admin — a User holding the highest permission role within a Project.
• API — the Cloudverest REST API provided via Cloudflare Workers.
• Audit Log — the immutable, append-only activity record maintained per Project.
• Branch — a named, parallel version of a Project's file tree.
• CLI — the Cloudverest command-line interface tool.
• Desktop App — the Cloudverest Electron-based desktop application for Windows.
• File Lock — the exclusive-editing reservation mechanism that signals intent to prevent concurrent edits.
• Merge — the operation that combines changes from one Branch into another.
• Project — a collaborative workspace containing folders, files, branches, and team members.
• Pull Request — a proposed Merge submitted for review and approval by authorised Users.
• Ritsea — Ritsea SRL, a company registered in Romania, operating the Cloudverest platform.
• Service — collectively: the web application, Desktop App, CLI, VS Code Extension, UE5 Plugin, API, and real-time sync infrastructure.
• Share Link — a URL generated to grant access to specific content to third parties.
• Soft Delete / Trash — the 30-day recoverable deletion state prior to permanent deletion.
• UE5 Plugin — the Cloudverest C++ plugin for Unreal Engine 5.
• User Content — all files, folder structures, metadata, comments, and other data uploaded or created by a User.
• Version — a point-in-time snapshot of a file created during an upload or edit operation.
• VS Code Extension — the Cloudverest source control integration for Visual Studio Code.
• WebSocket Connection — the persistent real-time connection maintained via Cloudflare Durable Objects.

2. Description of Service

Cloudverest is a secure cloud file collaboration and version control platform operated by Ritsea SRL. The Service currently includes:

• Web Application — accessible at app.cloudverest.com
• Desktop Application — an Electron-based Windows application providing local file synchronisation
• CLI Tool — a command-line interface for automation and scripting
• VS Code Extension — source control integration for Visual Studio Code (currently in preview)
• UE5 Plugin — a native C++ plugin for Unreal Engine 5 (currently in preview)
• API & Real-Time Sync — a REST API and WebSocket-based synchronisation infrastructure powered by Cloudflare Workers and Durable Objects

The Service is provided as a platform in active development. Features described in marketing materials, the pricing page, or documentation may be subject to change, limitation, or removal without notice. Preview and early-access features are provided without warranty of any kind and may be discontinued at any time.

3. Account Registration and Eligibility

To use the Service you must:

• Be at least 16 years of age (the minimum digital consent age under Romanian law and GDPR Article 8)
• Have received a valid, single-use invitation token from an authorised administrator — tokens are non-transferable
• Provide accurate and complete registration information
• Maintain only one Account per natural person unless explicitly authorised in writing

If you accept these Terms on behalf of an organisation, you represent and warrant that you have authority to bind that organisation, and that the organisation will be responsible for all actions taken under Accounts created on its behalf.

3.1 Firebase Authentication

Authentication services are provided by Google Firebase Authentication. Ritsea does not store your password. Account recovery, credential management, and any two-factor authentication features are subject to Google's terms and policies. Ritsea is not responsible for loss of Account access resulting from Firebase service disruptions, credential loss, or Google account termination.

3.2 Account Security

You are responsible for maintaining the confidentiality of your credentials, for all activities that occur under your Account, and for promptly notifying us at polytooldesign@gmail.com if you suspect any unauthorised use. We reserve the right to suspend or terminate Accounts that appear compromised or that violate these Terms.

4. End User Licence Agreement — Desktop Application

Subject to these Terms, Ritsea grants you a limited, personal, non-exclusive, non-transferable, revocable licence to install and use one (1) copy of the Desktop Application on a Windows 10 or Windows 11 (64-bit) device that you own or control, solely for accessing the Service.

4.1 Automatic Updates

The Desktop Application may automatically download and install updates without prior notice in order to maintain compatibility, security, and feature parity with the Service. By installing the Desktop Application you authorise this automatic update mechanism.

4.2 Local Filesystem Access

The Desktop Application requires access to local filesystem directories you designate as synchronisation workspaces. It reads files from and writes files to those directories as part of the sync functionality. The application also stores local state data including workspace paths, a device UUID, and a synchronisation state cache. You are responsible for ensuring you have appropriate rights to all content in your designated workspace directories.

4.3 Restrictions

You may not:

• Redistribute, sublicence, or resell the Desktop Application
• Reverse engineer, decompile, disassemble, or attempt to derive the source code
• Extract, copy, or use any embedded API keys, credentials, or cryptographic secrets
• Modify or create derivative works of the Desktop Application

4.4 "As Is" Disclaimer

The Desktop Application is provided "AS IS" without warranty of any kind. Ritsea makes no representations regarding the Desktop Application's fitness for a particular purpose, compatibility with your hardware, or freedom from defects. See Section 22 for full warranty disclaimers.

5. End User Licence Agreement — CLI Tool

Subject to these Terms, Ritsea grants you a limited, non-exclusive, non-transferable, revocable licence to use the CLI Tool to interact with the Service for personal or organisational purposes.

You may use the CLI Tool to automate interactions with the Service, provided that:

• Automated usage remains within the applicable API rate limits
• You do not use automation to circumvent rate limits via credential rotation, multiple accounts, or proxy chains
• You do not use the CLI for bulk data extraction, competitive intelligence scraping, or any purpose not supported by the intended API design

You may not redistribute, sublicence, or resell the CLI Tool independently. The CLI uses the same JWT authentication as the web application and is subject to all security and access control policies of the Service.

6. End User Licence Agreement — VS Code Extension

Subject to these Terms, Ritsea grants you a limited, non-exclusive, non-transferable, revocable licence to install and use the VS Code Extension within Visual Studio Code.

The VS Code Extension may also be distributed via the Visual Studio Code Marketplace. Use of the Marketplace is additionally subject to Microsoft's Marketplace Terms of Use. The VS Code Extension accesses your local filesystem for file status queries and sends push/pull operations to the Cloudverest API using your authenticated session.

Preview status: The VS Code Extension is currently in preview. It may be incomplete, unstable, or subject to breaking changes without notice. It is provided without warranty of any kind.

7. End User Licence Agreement — UE5 Plugin

Subject to these Terms, Ritsea grants you a limited, non-exclusive, non-transferable, revocable licence to use the UE5 Plugin within Unreal Engine 5 projects that you own or control.

7.1 Epic Games EULA

Use of the UE5 Plugin is additionally subject to the Epic Games Unreal Engine End User Licence Agreement. Ritsea does not provide or grant any licence to Unreal Engine itself. The UE5 Plugin is an interface layer that communicates with the Cloudverest API; it does not include any Unreal Engine IP.

7.2 Restrictions

• You may not redistribute the UE5 Plugin source code or precompiled binaries independently of a compiled Unreal Engine project
• All API rate-limiting policies applicable to the Service apply equally to the UE5 Plugin

7.3 Credential Storage

The UE5 Plugin may store authentication tokens in Unreal Engine editor configuration files. Ritsea is not responsible for unauthorised access resulting from insecure Unreal Engine editor configuration or project repository settings.

7.4 Preview Status & Disclaimer

The UE5 Plugin is currently in preview and is provided "AS IS" without warranty of any kind. It is not suitable for use in production pipelines without independent validation. Studios and enterprises using the UE5 Plugin in commercial projects do so at their own risk. Ritsea's total liability for any claim arising from UE5 Plugin use is limited as set forth in Section 23.

8. User Content and File Storage

8.1 Ownership

You retain all intellectual property rights in User Content you upload to the Service. Ritsea claims no ownership over User Content.

8.2 Licence Grant to Ritsea

By uploading User Content, you grant Ritsea a limited, worldwide, non-exclusive, royalty-free licence to store, reproduce, transmit, and display your User Content solely as necessary to provide the Service to you and your authorised team members. This licence terminates when the relevant content is permanently deleted from the Service.

8.3 File Size Limits

The Service currently supports individual file uploads of up to 1 TB (1,000 GB) per file. This limit may be adjusted at any time with reasonable notice. Files exceeding the applicable limit will be rejected at upload time. Ritsea is not responsible for upload failures resulting from network interruptions during large file transfers. Files approaching the 1 TB limit may experience increased transfer times and are subject to greater risk of partial-upload failure. You should maintain independent backups of all critical data regardless of file size.

8.4 Content Responsibility

You represent and warrant that: (a) you own or have all necessary rights to upload your User Content; (b) your User Content does not infringe any third-party intellectual property, privacy, or other rights; and (c) your User Content complies with all applicable laws.

8.5 No Content Scanning

Ritsea does not scan, inspect, or analyse the contents of your files for advertising purposes, AI model training, or any purpose other than providing the Service. Files are stored and processed as opaque binary data. We do not read file contents unless required by a valid legal process.

8.6 Prohibited Content

You may not upload, store, or distribute content that:

• Constitutes child sexual abuse material (CSAM) — such content will be immediately reported to applicable authorities and will result in immediate account termination
• Contains malware, ransomware, spyware, or code designed to harm or gain unauthorised access to third-party systems
• Is subject to export control regulations (including ITAR and EAR) without prior written authorisation from Ritsea
• Infringes the copyright, trademark, or other intellectual property rights of any third party
• Violates any applicable law or regulation

9. Version Control, Branching, and Merging

9.1 Version Retention

The Service retains all historical Versions of a file from the time of first upload until the file is permanently deleted. Version history is available for rollback at any time during an active Project. Ritsea does not guarantee specific retrieval performance for files with extensive version histories.

9.2 Branching

Branches are independent parallel copies of the file tree at the time of branching. Modifications on one Branch do not affect other Branches until a Merge is performed and accepted by an authorised User.

9.3 Merge Conflicts and Data Loss Disclaimer

When a Merge encounters conflicting changes — defined as modifications to the same file on both the source and target Branch since their common ancestor — the Service will report the conflict and halt the Merge operation. The Service does not automatically resolve binary file conflicts. You are responsible for reviewing and resolving all conflicts before re-initiating a Merge.

Ritsea is not liable for any data loss, corruption, or overwriting resulting from Merge operations initiated by Users with the necessary permissions. The Audit Log records the identity of the User who approved each Merge. You acknowledge that Merge operations are irreversible once completed and that the version history provides the only rollback mechanism.

9.4 Pull Requests

A Pull Request is a collaborative review mechanism. Approval of a Pull Request by an authorised User initiates a Merge. By approving a Pull Request, the approving User accepts responsibility for that action as recorded in the Audit Log.

10. File Locking

10.1 Advisory Nature

File Locks are advisory signals, not technical enforcement mechanisms. While the Service displays lock status to all collaborators and warns Users attempting to edit a locked file, a User with sufficient permissions may override a lock. Ritsea does not guarantee that concurrent edits will never occur.

10.2 Stale Lock Release

File Locks that remain active for an extended period without active editing activity may be automatically released by the Service. Ritsea is not liable for conflicts arising from stale lock auto-release.

10.3 Liability

Ritsea is not responsible for data loss or conflicts arising from concurrent editing, lock override, or lock expiry. You are responsible for coordinating editing workflows among your team.

11. Real-Time Synchronisation and WebSocket Terms

11.1 Service Description

Real-time synchronisation is provided via persistent WebSocket Connections managed through Cloudflare Durable Objects. Real-time features include live file status updates, sync notifications, and collaborative presence indicators.

11.2 Offline Editing and Sync Conflicts

The Desktop Application supports offline local editing. Changes made offline are queued for upload when internet connectivity is restored. If the same file is edited locally while offline and by another User via the web application during that offline period, a conflict will occur upon reconnection. Ritsea is not liable for data loss resulting from offline sync conflicts. You are responsible for resolving such conflicts using the version history and conflict detection features of the Service.

11.3 Best-Effort Delivery

WebSocket-delivered notifications and sync events are provided on a best-effort basis. Ritsea does not guarantee real-time message delivery in cases of network interruption, server maintenance, or high infrastructure load. Critical coordination decisions should not rely solely on real-time notifications.

11.4 Session Termination

WebSocket sessions may be terminated by the Service after periods of inactivity or in response to infrastructure maintenance events. Clients are expected to implement reconnection logic. Ritsea is not liable for data loss resulting from WebSocket session termination.

12. Share Links

12.1 Features

Share Links may optionally be configured with:

• Password protection — a hashed password stored server-side; recipients must enter the correct password to access content
• Expiry date/time — after which the link becomes inaccessible

Share Links may be revoked at any time by a User with sufficient Project permissions.

12.2 User Responsibility

You are responsible for the distribution of Share Links. Once a Share Link URL has been shared with a third party, Ritsea cannot prevent that party from further distributing the URL. Password expiry is your primary mechanism for limiting access. You should not use Share Links to share content that must be kept strictly confidential, as URL interception or unauthorised forwarding is outside Ritsea's control.

12.3 Third-Party Recipients

Recipients of Share Links who do not have Cloudverest Accounts are not directly bound by these Terms. You, as the link creator, accept full responsibility for the appropriateness of granting access via Share Link and for any consequences of that access.

13. Webhooks

13.1 Delivery

Webhooks deliver HTTP POST requests to endpoints you configure. Ritsea does not guarantee webhook delivery in cases of endpoint unavailability, network failure, or target server errors. Ritsea will attempt to retry failed deliveries a limited number of times before marking an event as failed. Webhook delivery records are retained for 30 days.

13.2 Security

You are responsible for validating webhook signatures and for securing your webhook receiver endpoints. Ritsea is not responsible for unauthorised access resulting from insecure webhook implementations on your end.

13.3 Payload Contents

Webhook payloads contain file and event metadata (e.g., file name, size, version ID, action type, actor identity). Payloads do not include raw file content. Webhooks are an event notification mechanism, not a file synchronisation mechanism.

14. Audit Logs

14.1 Immutability

Audit Log entries are append-only and cannot be deleted or modified by any User, including Admins. Audit Logs may only be removed upon deletion of the entire Project or upon account termination, subject to the retention periods described in Section 19.

14.2 Retention

Active Audit Log data is retained indefinitely for the life of the Project. Entries older than 90 days are archived but remain accessible upon request. Archived log retrieval may require additional processing time. Upon account or Project termination, Audit Logs are retained for 30 days and then permanently deleted, unless subject to a valid legal hold.

Legal basis under GDPR: Audit Log retention is justified under Article 6(1)(f) — legitimate interests — specifically: platform security, fraud prevention, access accountability, and dispute resolution capability.

14.3 Legal Disclosure

Audit Logs may be disclosed in response to valid legal process, including court orders or subpoenas from authorities with applicable jurisdiction. Please refer to our Privacy Policy for further details on law enforcement disclosure procedures.

15. Acceptable Use Policy

You agree to use the Service only for lawful purposes and in a manner consistent with these Terms. You may not:

• Upload, store, or distribute malware, ransomware, spyware, or any code designed to harm or gain unauthorised access to third-party systems
• Attempt to gain unauthorised access to any part of the Service, its infrastructure, or other Users' data
• Reverse engineer, decompile, or attempt to extract source code, API keys, or cryptographic secrets from any component of the Service
• Circumvent API rate limits through credential rotation, multiple accounts, automated proxy chains, or similar means
• Use the CLI or API for bulk scraping, data mining, or extraction not supported by the intended API design
• Store or transmit content subject to export control regulations (ITAR, EAR) without prior written authorisation from Ritsea
• Store or distribute copyright-infringing content, including large-scale piracy of commercial software, media, or other protected works
• Share Account credentials with unauthorised individuals
• Resell, sublicence, or otherwise provide third-party access to the Service without a written agreement with Ritsea
• Engage in any activity that could disrupt, damage, or impair the Service or its infrastructure
• Use the Service for any illegal purpose or in violation of any applicable law or regulation

15.1 Resource Abuse

Attempting to consume unreasonable storage, API operations, or bandwidth through automated means, artificial inflation of operation counts, or other abusive patterns is prohibited. Ritsea may throttle, suspend, or terminate Accounts exhibiting such behaviour without prior notice.

15.2 Large File Responsibility

You are responsible for ensuring that files you upload do not contain embedded malware or illegal content. You acknowledge that Ritsea does not scan file contents and relies entirely on your representations regarding content legality.

16. Pricing, Billing, and Payment

16.1 Current Free Tier

The Service is currently available free of charge during the platform's early access period. No payment method or billing credentials are required to use the Service at this time.

16.2 Future Paid Plans

Ritsea intends to introduce paid subscription plans in the future. Pricing, storage limits, and operation quotas for future plans will be described at cloudverest.com/pricing and are subject to change. No billing will occur without your explicit, affirmative consent at the time of plan selection.

16.3 Notice Before Billing Activation

Ritsea will provide no less than 30 days' advance notice before activating any billing obligation for existing Users. You will be required to affirmatively accept updated payment terms before any charge is made. Existing Users who do not accept billing terms will not be charged and may continue using the Service at whatever free-tier level is available at that time.

16.4 No Current Charges

As of the effective date of these Terms, no charges are being applied to any User account. Any paid_units or billing-related fields visible in account data are reserved for future use and do not reflect any current financial obligation.

17. Intellectual Property

17.1 Ritsea IP

The Service — including its software, APIs, design, documentation, logos, the Cloudverest name, and all related branding — is the proprietary intellectual property of Ritsea SRL and is protected by applicable copyright, trademark, and other intellectual property laws. No licence to Ritsea IP is granted beyond what is explicitly stated in these Terms.

17.2 User IP

Users retain all intellectual property rights in User Content. Nothing in these Terms transfers any intellectual property rights in User Content to Ritsea.

17.3 Feedback

If you voluntarily provide feedback, suggestions, or ideas regarding the Service, Ritsea may use that feedback for any purpose without obligation or compensation. This clause does not apply to User Content files.

17.4 Copyright Infringement / DMCA

If you believe that User Content on the Service infringes your copyright, please send a notice to polytooldesign@gmail.com including: (a) identification of the work claimed to be infringed; (b) identification of the allegedly infringing material and its location on the Service; (c) your contact information; (d) a statement of good faith belief that use of the material is not authorised by the rights holder; (e) a statement of accuracy under penalty of perjury; and (f) your physical or electronic signature.

18. Third-Party Services and Integrations

The Service relies on the following third-party providers, whose own terms and policies apply to their respective components:

• Cloudflare, Inc. — provides compute (Workers), database (D1), object storage (R2), key-value cache (KV), real-time state (Durable Objects), and global content delivery. Ritsea is not liable for Service unavailability caused by Cloudflare infrastructure incidents.
• Google Firebase Authentication — provides identity and authentication services. Service login may be unavailable during Firebase outages. Google's Terms of Service apply.
• Resend — provides email delivery for Service notifications. Your email address is transmitted to Resend solely for this purpose. Resend's privacy policy governs its handling of your email address.

Reference to third-party services does not constitute endorsement. Ritsea does not control these third-party services and is not responsible for their availability, terms, or changes to their policies.

19. Data Retention

The following retention periods apply to data processed by the Service:

Where Ritsea relies on legitimate interests as a legal basis, we have balanced those interests against your fundamental rights and freedoms. You may contact us to exercise your GDPR rights, including requesting early deletion of personal data, subject to any overriding legal retention obligations. See our Privacy Policy for full details on your rights.

20. Security

20.1 Security Measures

Ritsea implements security measures consistent with industry standards, including Firebase JWT authentication, TLS 1.3 encryption in transit, encryption at rest, role-based access control, rate limiting, and strict CORS policies. Further details are available at cloudverest.com/security.

20.2 No Security Guarantee

No system is completely secure. Ritsea cannot guarantee that the Service will never be subject to a security breach, data theft, or unauthorised access. You acknowledge that use of cloud services carries inherent security risks.

20.3 No Third-Party Security Audit

The Service has not undergone a formal third-party penetration test or independent security audit as of the effective date of these Terms. Security practices described in these Terms and at cloudverest.com/security represent Ritsea's internal implementation standards. Ritsea makes no SOC 2, HIPAA, ISO 27001, or similar compliance representations. Users with specific regulatory compliance requirements should independently evaluate whether the Service meets those requirements before relying on it for regulated data.

20.4 Security Breach Notification

In the event of a security breach affecting your personal data or User Content, Ritsea will notify you in accordance with applicable law, including GDPR Articles 33 and 34 notification obligations to supervisory authorities and affected individuals within the required timeframes.

20.5 Your Responsibilities

You are responsible for: (a) maintaining the security of your Account credentials; (b) securing devices on which you have installed the Desktop App, CLI, or VS Code Extension; (c) immediately notifying Ritsea at polytooldesign@gmail.com if you suspect unauthorised access to your Account.

21. Service Availability

21.1 No SLA

The Service is provided without any formal Service Level Agreement (SLA). Ritsea does not guarantee specific uptime percentages, response times, or recovery time objectives.

21.2 Maintenance

Ritsea may perform scheduled or emergency maintenance that results in temporary service unavailability. We will attempt to provide advance notice of scheduled maintenance via email or in-app notification where practically feasible.

21.3 Cloudflare Dependency

Service availability depends substantially on Cloudflare's global infrastructure. Cloudflare publishes its own infrastructure status at cloudflarestatus.com. Ritsea is not liable for service unavailability caused by Cloudflare infrastructure incidents.

24. Indemnification

You agree to defend, indemnify, and hold harmless Ritsea SRL and its officers, directors, employees, agents, and service providers from and against any claims, liabilities, damages, judgments, awards, losses, costs, expenses, and reasonable attorneys' fees arising out of or relating to:

• Your use of the Service in violation of these Terms
• User Content you upload, including any claims that your User Content infringes third-party intellectual property rights
• Your violation of any applicable law or regulation
• Your distribution of Share Links and any access granted thereby to third parties
• Your use of the Desktop App, CLI, VS Code Extension, or UE5 Plugin in violation of their respective licence terms under these Terms

25. Termination

25.1 Termination by You

You may terminate your Account at any time by contacting us at polytooldesign@gmail.com. Upon request, we will initiate Account and associated data deletion subject to the retention periods in Section 19.

25.2 Termination by Ritsea

Ritsea may suspend or terminate your Account immediately and without prior notice if:

• You violate any provision of these Terms
• Your Account is involved in fraudulent, abusive, or harmful activity
• Required by applicable law or valid legal process
• Required to protect the security or integrity of the Service or other Users

Ritsea will provide notice of termination where legally required or practically feasible.

25.3 Effect of Termination

Upon termination of your Account:

• Your licence to use the Service and all Client Software terminates immediately
• You must uninstall the Desktop App, CLI, and any extensions or plugins
• Access to your User Content via the Service will be disabled
• User Content will be retained for 30 days and then permanently deleted, except as required by law

25.4 Survival

Sections 1, 8.1, 8.2, 17, 19, 22, 23, 24, 26, and 27 survive any termination of these Terms.

26. Dispute Resolution and Governing Law

26.1 Informal Resolution

Before initiating any formal legal action, you agree to attempt to resolve the dispute informally by contacting us at polytooldesign@gmail.com. Ritsea will attempt to respond within 30 days of receipt of a written description of the dispute.

26.2 Governing Law

These Terms are governed by and construed in accordance with the laws of Romania, without regard to its conflict of law principles. Any dispute arising out of or relating to these Terms or the Service shall be subject to the exclusive jurisdiction of the courts of Romania.

26.3 EU Consumer Rights

If you are a consumer located in the European Union, you may also benefit from mandatory consumer protection provisions of your country of residence that cannot be excluded by contract. Nothing in Section 26.2 limits your right to rely on those mandatory provisions. You may also have the right to use the EU Online Dispute Resolution platform at ec.europa.eu/consumers/odr.

26.4 Class Action Waiver

To the extent permitted by applicable law, you agree to bring claims against Ritsea only in your individual capacity and not as a plaintiff or class member in any purported class or representative proceeding. This waiver applies to non-EU Users only; it has limited enforceability in EU jurisdictions and is not intended to apply to EU consumers.

27. General Provisions

27.1 Entire Agreement

These Terms, together with the Privacy Policy at cloudverest.com/privacy, constitute the entire agreement between you and Ritsea SRL regarding the Service and supersede all prior agreements, understandings, and communications.

27.2 Severability

If any provision of these Terms is found to be unenforceable by a court of competent jurisdiction, that provision will be modified to the minimum extent necessary to make it enforceable, and the remaining provisions will continue in full force and effect.

27.3 Waiver

Failure by Ritsea to enforce any provision of these Terms on any occasion does not constitute a waiver of the right to enforce that provision on any future occasion.

27.4 Assignment

You may not assign your rights or obligations under these Terms to any third party without Ritsea's prior written consent. Ritsea may assign these Terms in connection with a merger, acquisition, corporate restructuring, or sale of substantially all of its assets, with notice to you.

27.5 No Partnership

These Terms do not create a partnership, joint venture, agency, employment, or franchise relationship between you and Ritsea.

27.6 Force Majeure

Ritsea is not liable for any failure or delay in performance resulting from causes beyond its reasonable control, including Cloudflare or Firebase infrastructure failures, natural disasters, acts of government or regulatory authorities, internet backbone disruptions, cyberattacks beyond Ritsea's control, or other events of force majeure.

27.7 Changes to These Terms

Ritsea may modify these Terms at any time by posting updated Terms at cloudverest.com/terms. For material changes, we will provide at least 30 days' advance notice via email or in-app notification. Continued use of the Service after the effective date of updated Terms constitutes your acceptance of those Terms. If you do not accept updated Terms, you must stop using the Service and may request account deletion pursuant to Section 25.1.

28. Contact Information

For questions, concerns, or notices relating to these Terms:

• Legal entity: Ritsea SRL (registered in Romania)
• Product: Cloudverest — cloudverest.com
• Email: polytooldesign@gmail.com
• Contact page: cloudverest.com/contact

These Terms were last updated on March 11, 2026 and are effective as of March 11, 2026.