TuxNest privacy
Your data.
Know the route.
Privacy and data control for TuxNest for VS Code and this public website. Updated 4 November 2026.
Workspace and local inference
The TuxNest VS Code extension works with the developer-selected workspace and model connection. When a compatible Ollama runtime runs on the same machine using a loopback endpoint, inference requests need not be sent to an external hosted model service. Protect local files with appropriate device permissions, disk encryption and backups.
Remote models and provider APIs
When you deliberately use an SSH-connected model host, selected prompts and context are processed on that authorized host. When you configure a third-party provider, task inputs go to that provider under its retention, security and privacy policies. Do not send confidential source code or credentials to an unapproved service.
Permissions and verification
Review model routes, workspace scope, proposed edits, tool permissions, logs and command results before proceeding with sensitive tasks. Local-only inference does not automatically secure your entire toolchain or every connected integration.
Detailed privacy and data control →Website, help and updates
This static website does not request model-provider keys. Cloudflare and linked third-party sites process browser requests under their own policies. For questions, use the TuxNest support resources without sharing passwords, API keys or confidential project contents.
Contact and support →