Secure Service Terms

1. Scope

1.1. These Secure Service Terms apply to every Session you launch on a Machine of the Secure tier. They are part of the Terms of Service, whose definitions apply.

1.2. If these Secure Service Terms conflict with the Terms of Service, these Secure Service Terms prevail for Secure Sessions.

2. The Secure service

2.1. Infrastructure partners. Secure Machines run in datacenters operated by infrastructure partners selected by us. VDTI provides the Secure service to you under the Node Lodge brand and is your only contracting party. You have no contract with a partner through the Service.

2.2. Location. The console shows the country and city of each Secure Machine before you launch it. Your Session and its data stay in that location for the life of the Session.

2.3. Partners as sub-processors. Partners are listed by category and country on our Sub-processors page. We impose on them obligations that protect your data, as described in the Data Processing Addendum.

3. Your Session

3.1. Dedicated VM. Each Secure Session runs in a virtual machine created for it, with its GPUs attached to that VM alone.

3.2. Access. You connect with SSH, using a public key you give. The key is installed for that Session. We install no key of ours and do not sign in to the Machine.

3.3. Firewall. Inbound traffic from the internet is limited to SSH from the IP address or range you give. Outbound TCP port 25 (SMTP) is blocked. Do not try to change or get around these rules.

3.4. Your responsibilities. You are responsible for the software you run on the Machine, for its configuration and security updates during the Session, and for copying your results off before the end.

4. Interruptions and maintenance

4.1. Interruptible offers. A Secure offer marked interruptible runs on capacity that the partner can reclaim at any time. Your Session then ends and you pay only for the time used.

4.2. Partner events. A partner may stop or restart a Machine for maintenance, hardware failure, security or legal reasons. If a Machine is lost, your Session ends, you pay only for the time the Machine ran for you, and the unused Budget returns to your Credit.

4.3. Platform protection. We may pause new Secure launches, or stop running Sessions, to protect the Service, a partner or other customers, or to comply with law. We tell you the reason when we stop your Session.

5. End of a Session and deletion

5.1. At the end of a Session, we ask the partner to delete the Machine and its disks, and we confirm the deletion. A deletion that fails is retried until it is confirmed.

5.2. Everything on the Machine is deleted. We do not keep backups or snapshots of Secure Machines.

5.3. Partners erase and reuse storage under their own datacenter procedures, which we select for their security controls but do not operate.

6. Physical security and partner access

6.1. Partners operate the physical hardware and the virtualization layer, and control physical access to their datacenters.

6.2. Their personnel may have technical access to the hardware under their own security controls, and are bound by obligations of confidentiality and data protection toward us.

6.3. Secure is the tier for confidential code, data and model weights. If your obligations require specific certifications or controls, ask us before launching.

7. Liability

The disclaimers and limitations of liability of the Terms of Service apply to Secure Sessions. A partner’s failure is a cause beyond our reasonable control under section 26.2 of the Terms of Service, without affecting the Budget Guard guarantee.