This page explains what NatNux collects and how we treat it. NatNux is a Linux workspace with a coding assistant. You talk in everyday language; we run that work on isolated computers.
Account
When you continue with Google we receive your name and email to create and sign you into your account. We do not use your Google login for Gmail, Drive, Calendar, or other Google products.
Work datasets (encrypted)
Your private workspace — the files the assistant and you edit under /work — is stored as an encrypted dataset. Encryption keys are held by the platform so we can mount the workspace for you; they are not shown in the app and are not given to other users.
Conversation history, plans, and similar product data are stored so you can come back to your sessions. Treat that history as private to your account, not as a vault for passwords.
Public datasets (not encrypted)
Each account also has a public folder. That dataset is not encrypted. It is always mounted and published on the internet at natnux.net/your-username/ (and paths under it). Anyone who knows the URL can read those files. There is no separate “publish” step — what is in the folder is live.
Do not put secrets, API keys, private repositories, or personal data you are not willing to share in the public folder.
Keys and secrets
If you Allow Google Cloud access, we use that permission only to create an unpaid Google Cloud project in your account and a Gemini-restricted API key (the same free Gemini Developer API as Google AI Studio). We store the key encrypted. We do not attach a billing account on your behalf.
Other secrets you save for the assistant (for example MCP tokens) are also stored encrypted. We show only a hint in the UI, never the full secret again.
Assistants and isolated guests
OpenCode runs in an isolated guest virtual machine for each turn and calls Google Gemini with your key. That key is available inside that guest while the turn runs. Grok and Codex, if you choose them, use their own logins saved in your workspace.
Prompts you send are processed by those providers under their terms. We meter usage (for example CPU, network, and disk) so the free service stays fair.
Logs
We keep operational logs (errors, usage, security events) to run and protect the service. We redact tokens and keys from those logs when we can. We do not sell your personal information.
Changes
We may update this notice as the product changes. The date above is the latest revision.