Skip to content

Smart Launch. Describe the workload, get the GPUs that fit.See how →
    • GPU CloudTrain and serve on NVIDIA GPUs in partner datacenters.
    • PricingPer GPU-hour, billed by the minute.
    • CommunityIndependent GPU machines, a private VM per session.
    • Smart LaunchDescribe the workload. Get the GPUs that fit.
    • Budget GuardSet a budget. Never pay past it.
    • EnvironmentsJupyterLab, PyTorch, vLLM, Ollama. Ready at launch.
    • BillingBy the minute, on demand or reserved.
    • SecurityIsolation, access and what each tier protects.
    • GPU calculatorWhich GPU holds your model, line by line.
    Two tiersSecure or Community?Pick the right one for your data.→
    • CLI and SDKTypeScript, Python and the nodelodge command.
    • MCP serverClaude and your agents launch GPUs, under a cap.
    • Agent frameworksLangChain, LlamaIndex, OpenAI and Claude agents.
    • GitHub ActionA GPU step in your workflow, always stopped.
    • NotebooksA GPU from a Jupyter cell.
    • API referenceEvery endpoint, with examples.
    • Overview →
    Hard capsA GPU you can hand to an agent.Spending limits on every API key, enforced by Node Lodge.→
    • LLM inferenceAn OpenAI-compatible endpoint with vLLM.
    • Fine-tuningTrain on your data. Keep the weights.
    • Batch jobsThousands of files, one session.
    • 3D renderingBlender and Cycles, headless.
    • Earn with your GPUsYour price, 85 percent to you, on Community.
    • Install the agentList a machine with one command.
    • Datacenter partnersSell capacity through your cloud API.
    RequirementsUbuntu 24.04 and a recent NVIDIA GPU.HWE kernel 6.12 or newer. Ampere or newer, 12 GB of VRAM or more.→
    • QuickstartFrom access to SSH, step by step.
    • Pick a GPUHow Smart Launch sizes your model.
    • Connect over SSHKeys, addresses, tunnels, files.
    • Sessions and limitsOn demand, reserved, the end of a session.
    • RecipesvLLM, ComfyUI, LoRA, Blender.
    • All docs →
    • AboutWho runs Node Lodge.
    • ContactRequest access, ask a question.
    • ChangelogWhat shipped, and when.
    • Report a vulnerabilityResponsible disclosure, by email.
    • Legal centerTerms, privacy, cookies and data processing.
Sign in
  • English
  • Français
  • Deutsch
  • Español
  • English
  • Français
  • Deutsch
  • Español
Sign inRequest access

Node Lodge legal documents

  • Overview
  • Applies to every service

    • Terms of Service
    • Acceptable Use Policy
    • Privacy Policy
    • Cookie Policy
    • Data Processing Addendum
    • Sub-processors
  • Secure

    • Secure Service Terms
  • Community

    • Community Service Terms
    • Host Agreement
  1. Legal
  2. Privacy Policy
Version française

Privacy Policy

What personal information Node Lodge collects, why, where it goes, how long it is kept, and your rights under Québec Law 25, GDPR, UK GDPR and US state laws.

Version
1.1
Published
November 8, 2026
Effective
November 8, 2026

1. Who we are

1.1. Node Lodge (https://nodelodge.com) is operated by Vision Digitale TI Inc. (“VDTI”, “we”, “us”), a corporation incorporated under the laws of Québec, Canada.

1.2. This policy explains how we handle personal information when you visit our website, request access, subscribe to product updates, use the console, the API or our developer tools, buy Credit, contact Support, report abuse, or host a machine on Community.

1.3. Person in charge of the protection of personal information. Under Québec’s Act respecting the protection of personal information in the private sector (“Law 25”), the person in charge of the protection of personal information at VDTI is its President. Contact: privacy@nodelodge.com.

2. Our role

2.1. Controller. We decide why and how we process the information described in section 3. For it, we are the enterprise accountable under Québec and Canadian law, and the controller under the GDPR and the UK GDPR.

2.2. Processor. The data, code, models and files you put on a Machine (“Customer Content”) belong to you. We process them only to run your Sessions, on your instructions, as your processor or service provider. Our Data Processing Addendum governs that processing. We do not open, read or analyze Customer Content.

3. Information we collect

3.1. Information you give us

Context Information
Access request Email address, company, role and use case you describe
Account Email address, display name, password (stored only as a hash), version and date of acceptance of the Terms
Organization Name, members and their roles
Two-factor authentication Authenticator secret (stored encrypted) and recovery codes (stored only as hashes)
SSH keys Public keys you save, their names, and the IP address or range you allow for a Secure Session
API keys Key name, scopes, expiry and the spending and concurrency caps you set
Payments Billing name and address, business tax number if you give one; card brand, last four digits and expiry. Card numbers are collected by our payment processor, never by us
Support Your requests, messages, attachments and satisfaction ratings
Abuse reports Your email address, the target reported, the description and evidence you give
Host Machine name, offer (rate, declared country), payout schedule. Identity verification for payouts is done by our payment processor (section 6.3)
Product updates Email address, the consent text you agreed to, and the dates and truncated IP address (first 24 bits for IPv4, first 48 bits for IPv6) of your request, confirmation and withdrawal

Smart Launch and the GPU calculator compute in your browser or answer your request without storing what you enter.

3.2. Information generated when you use the Service

Context Information
Sign-in Session token (stored only as a hash), its dates, and when a two-factor code was last confirmed
Account security One-time email links (stored only as hashes); failed attempt counters keyed by a one-way hash
Sessions Machine, tier, country, environment, Budget, start and stop times, rate, charges, reason for ending, the Account or API key that launched it, and licences you accepted for a model
Credit and payments Ledger entries, payments, taxes, failures, refunds and disputes, automatic top-up settings, and whether the Account is blocked
Account limits Your account tier and the facts it is computed from (age of the Organization, successful payments, disputes)
Activity log Security-relevant actions on accounts, sessions, payments and administration: who, what, when, request identifier, API key used and some details
Host agent The machine’s public key, agent version, heartbeats every 30 seconds, hardware inventory (system, CPU, memory, GPU model, memory and driver, a hash of each GPU’s identifier, storage), weekly speed test results, and the IP address of the agent’s requests. The agent collects no hostname, user name, serial number or file
Host earnings Earnings, holds, reversals and payouts
Community network records For each Community Session: time, protocol, destination address and port and volume of the connections it opens outside the relay. No content
Relay logs Session identifier and network addresses of connections through the Session relay
Server logs IP address, date, method and path of each request, status, duration and a request identifier. Query values, passwords, cookies, authorization headers and signatures are removed
Error reports The error, where it happened, the page address without its query string, browser and system type, and software version. Cookies, headers and request bodies are removed

3.3. What we do not do

We do not use advertising or analytics trackers, do not buy data about you, do not sell personal information, and do not share it for cross-context behavioral advertising.

4. Why we use it

Purpose Information Legal basis (GDPR, UK GDPR)
Answer access requests and send invitations Access request Steps at your request before a contract; legitimate interest
Create and run your Account and Organization Account, organization, two-factor Contract
Run Sessions: create, connect, meter, stop and delete them Sessions, SSH keys, IP range Contract
Sell Credit, hold and charge Budgets, calculate taxes, issue receipts, keep accounts Payments, ledger, sessions Contract; legal obligation
Set account limits, prevent fraud and handle disputes Limits, payments, activity log Legitimate interest in protecting the Service and its users; legal obligation
Review, list and pay Hosts Host agent, offers, earnings Contract with the Host; legal obligation (tax)
Secure the Service and answer abuse reports Sign-in, security, activity log, logs, network records, reports Legitimate interest; legal obligation
Answer Support requests Support Contract; legitimate interest
Fix errors and keep the Service reliable Error reports, logs Legitimate interest
Send service emails and console notifications Email address, notifications Contract
Send product updates Product updates Consent
Comply with law and lawful requests As needed Legal obligation

We use your information only for these purposes or for compatible purposes the law allows. For any other purpose, we ask for your consent first.

5. Emails and notifications

5.1. Service emails cover money, security and actions only you can take: confirmations, password resets, receipts, payment and dispute notices, budget and session alerts, security alerts and notices about these documents. Other notices stay in the console. You choose optional emails in your notification settings.

5.2. Product updates are sent only to people who asked for them on our website and confirmed by clicking the link in a confirmation email. Each one has a one-click unsubscribe link and identifies VDTI, as Canada’s Anti-Spam Legislation requires. We act on a withdrawal at once, and within 10 business days at the latest.

6. Who we share it with

6.1. Service providers. Our sub-processors host the platform, store backups and support attachments, deliver email, process payments, and receive error reports. They are listed by category and country on our Sub-processors page. They process information only on our instructions, under written contracts that protect it.

6.2. Infrastructure partners and Hosts. To run a Session, the Secure partner or the Community Host receives what the Machine needs: its settings and, for Secure, your SSH public key and allowed IP range. Neither receives your name or email address. Customer Content is on their hardware for the life of the Session.

6.3. Payment processor. Our payment processor handles card payments, tax calculation, receipts and Host payouts, and verifies the identity of Hosts. It also uses payment and identity data as an independent controller, for fraud prevention and its legal obligations, under its own privacy policy.

6.4. Your Organization. Owners and admins of your Organization see its members, Sessions, Credit, payments and activity log. Hosts see the Sessions on their machines without the renter’s identity.

6.5. Our personnel. Authorized VDTI personnel access records to operate, support and secure the Service, with two-factor authentication, and their changes are recorded in the activity log.

6.6. Legal requirements. We disclose information when the law requires it, in response to a valid order of a competent authority, or to protect the rights, property or safety of users, partners, Hosts or the public. When the law allows, we tell you first.

6.7. Business transfers. In a merger, acquisition or sale of assets, information may be transferred to the other party under an agreement that limits its use to the purposes of this policy.

7. Where information is stored

7.1. Our platform and database run on servers in Canada.

7.2. Some information is processed outside Québec and outside Canada, in the countries listed on our Sub-processors page, including the United States and the European Union. Customer Content is processed in the country of the Machine you choose, shown before launch.

7.3. Québec. Before communicating personal information outside Québec, we conduct a privacy impact assessment and communicate it only if the information will receive adequate protection, under a written agreement.

7.4. GDPR and UK GDPR. Transfers to Canada rely on the European Commission’s adequacy decision for Canada and on the corresponding UK regulations. Other transfers rely on an adequacy decision or on the standard contractual clauses of the European Commission and the UK addendum. You can ask privacy@nodelodge.com for a copy of the safeguards.

7.5. Information stored in another country may be accessible to its authorities under its laws.

8. How long we keep it

Information Retention
Customer Content on a Machine Deleted with the Machine at the end of the Session
Access request not followed by an account 12 months
Account and Organization While the Account is open, then deleted or de-identified within 30 days after closing
Sign-in records Until they expire, at most 7 days
One-time email links 30 days after expiry or use
SSH key, IP range and machine address of a Session 12 months after the Session
Ledger, payments, receipts and billed Sessions While the Account is open, then 6 years after the end of the fiscal year in which it is closed (tax and accounting)
Host earnings and payouts While the Account is open, then 6 years after the end of the fiscal year in which it is closed (tax and accounting)
Activity log 6 years for money actions, 2 years for the rest
Support requests and attachments 3 years after the request is closed
Abuse reports 3 years after closing, or longer while a legal claim or investigation requires it
Community network records 90 days
Server and relay logs 30 days
Error reports 90 days
Database backups Up to 30 days
Product updates While subscribed, then 3 years after withdrawal, after which the email address is replaced by a keyed fingerprint
Console notifications 180 days

The tax laws of Canada and Québec require us to keep accounting records for 6 years after the end of the last fiscal year they relate to.

When an Account is closed, what the law requires us to keep is kept only for that purpose, linked to a random identifier instead of your name and email address. At the end of its retention period, information is deleted or anonymized.

9. Security

9.1. We protect information with measures suited to its sensitivity, including: encryption in transit; passwords hashed with argon2id; tokens, links and API keys stored only as hashes; two-factor authentication required for our administrators; a session cookie that scripts cannot read; a database not exposed to the internet; server administration through a private network only; an append-only activity log and ledger; and daily backups.

9.2. No system is perfectly secure. Report a vulnerability to security@nodelodge.com.

10. Your rights

10.1. Everyone. Wherever you live, you can ask us to: confirm whether we hold personal information about you and give you access to it; correct information that is inaccurate, incomplete or ambiguous; delete information we no longer need, and close your Account; withdraw a consent, for the future.

10.2. Québec. You also have the right to: receive computerized information you provided in a structured, commonly used technological format, and have it sent to a person you choose; ask us to stop disseminating your information or to de-index a link to your name where the law’s conditions are met; be informed of a decision based exclusively on automated processing; and file a complaint with the Commission d’accès à l’information du Québec.

10.3. Canada. You can file a complaint with the Office of the Privacy Commissioner of Canada.

10.4. European Union, United Kingdom and Switzerland. You also have the right to restrict processing, to object to processing based on our legitimate interests, and to data portability, and to lodge a complaint with your supervisory authority (in the United Kingdom, the Information Commissioner’s Office; in Switzerland, the Federal Data Protection and Information Commissioner).

10.5. California and other US states. Where a US state privacy law applies to us, residents of that state may have the right to know, access, correct and delete their personal information and to receive it in a portable format, and to appeal our decision on their request by replying to it. We do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information to infer characteristics about you. We will not treat you differently for exercising your rights. An authorized agent may make a request for you with proof of authorization.

10.6. Global Privacy Control. We honor Global Privacy Control signals as a request to opt out of sale and sharing. Since we do neither, the signal changes nothing on our Service.

10.7. How to ask. The owner of an Organization can close the Account from the console settings. For any other request, write to privacy@nodelodge.com. We verify your identity before acting, usually by asking you to write from the email address of your Account. We answer within 30 days, and access and correction are free. If the law that applies to you allows more time and we need it, we tell you why within those 30 days.

11. Automated decisions

11.1. We make no decision based exclusively on automated processing that produces legal effects for you or affects you as significantly.

11.2. Some controls run automatically, and you can ask privacy@nodelodge.com to explain them and to have a person review a decision: refusal of a launch that exceeds your Credit, Limits or API key caps; stop of a Session at its Budget; account tiers raised from age and payments, and lowered to the first tier after a payment dispute; blocking of an Account after a refunded or disputed payment; temporary blocking of sign-in after repeated failures.

12. Cookies

We use one strictly necessary cookie to keep you signed in, and storage in your browser for your interface preferences. See our Cookie Policy.

13. Children

The Service is not intended for people under 18, and we do not knowingly collect their information.

14. Confidentiality incidents

14.1. We record every confidentiality incident involving personal information in a register.

14.2. When an incident presents a risk of serious injury, we promptly notify the Commission d’accès à l’information du Québec, the Office of the Privacy Commissioner of Canada when federal law applies, and the people concerned. Under the GDPR and the UK GDPR, we notify the competent authority within 72 hours when required, and the people concerned when the risk to them is high.

15. Changes

We may update this policy. For a material change, we tell you by email or in the console before it takes effect. Each version has a number and dates, and previous versions remain available on our legal page.

16. Contact

Questions about this policy or your information: privacy@nodelodge.com.

Previous versions

  • Version 1.0Effective November 7, 2026 · Replaced on November 7, 2026

Questions about these documents? support@nodelodge.com · privacy@nodelodge.com

On this page

  • 1. Who we are
  • 2. Our role
  • 3. Information we collect
  • 4. Why we use it
  • 5. Emails and notifications
  • 6. Who we share it with
  • 7. Where information is stored
  • 8. How long we keep it
  • 9. Security
  • 10. Your rights
  • 11. Automated decisions
  • 12. Cookies
  • 13. Children
  • 14. Confidentiality incidents
  • 15. Changes
  • 16. Contact

Get Node Lodge product updates by email.

Confirm by email. Unsubscribe anytime.

Product

  • GPU Cloud
  • Pricing
  • Community
  • Secure or Community
  • Smart Launch
  • Budget Guard
  • Billing
  • Security
  • GPU calculator

Developers

  • Overview
  • Quickstart
  • CLI and SDK
  • MCP server
  • API reference
  • Recipes
  • All docs

Use cases

  • LLM inference
  • Fine-tuning
  • Batch jobs
  • 3D rendering

Providers

  • Earn with your GPUs
  • Install the agent
  • Datacenter partners

Company

  • About
  • Contact
  • Request access
  • Changelog
  • Report a vulnerability

Node Lodge by VDTI · © 2026 VDTI

  • Terms
  • Privacy
  • Cookies
  • Acceptable use
  • Sub-processors
  • Legal center
  • English
  • Français
  • Deutsch
  • Español