Coduf
Guides

Coduf Security and Data Handling: What Happens to Project Context

A plain-language explanation of local workspace permissions, remote model requests, published downloads and security assurance limits.

Local projects and remote model requests

Coduf's desktop workflow operates with files in a project workspace selected on the user's machine. Local-first does not mean that every AI request remains local. When you submit a request to a configured remote model, the prompt and selected code or context necessary for that request may be transmitted to that provider. Responses and usage information can pass through the configured gateway.

Before working with confidential material, check which project folders and files the application can access, what permissions are granted for edits and commands, and which AI provider will receive the selected context. Never paste passwords, private keys or customer records into a prompt unnecessarily.

A local model endpoint, when explicitly configured and accessible, can have a different network boundary. A provider name or logo alone does not demonstrate local processing.

Permissions, execution and review

A coding agent may request file reads, file edits or terminal commands. These actions are not equivalent. Review the task scope, file changes and execution permissions before allowing risky operations. Use a version-controlled project when possible, inspect diffs, and run the relevant tests. An AI-generated result can be incorrect even when a command exits successfully.

The web account service has separate responsibilities for identity, subscription status, usage accounting and model routing; do not confuse those server functions with the authority granted to a local process.

What the privacy notice covers

The Privacy Notice explains categories of account information, sessions, billing records, operational logs, selected context and external recipients. Provider-specific logging, retention and processing terms can differ. The Terms of Use describe your obligations and current product constraints.

Do not rely on marketing phrases such as "zero source code retention" as a substitute for written provider and account policies.

Account and transport security

Account access and desktop authorization use controls including session management and a PKCE-based sign-in path. Security depends on the deployed configuration, updates, user choices and external providers. Encryption, authentication and request authorization should be evaluated at the actual deployment boundary, not assumed from one code sample.

Our internal checklist is not a SOC 2 Type II report, ISO 27001 certification, independent penetration test, GDPR legal determination or externally signed security attestation. Any formal assurance should be supported by a genuine independent assessor and the actual report.

Verify a downloaded installer

Download from the official Coduf download page, review the release version and applicable SHA-256 digest, and verify the file before executing it. A checksum helps identify whether the bytes match the published release; it does not establish a third-party code audit or guarantee that every installer is signed.

At the time of this article's initial publication the release catalog listed a Windows installer. We do not claim that unreleased macOS or Linux installers are available.

Vulnerability reporting and questions

If you find a security concern, share a minimal description of the affected feature and the steps needed to reproduce it with the support channel listed on the website. Avoid uploading exploits that include real customer data or secrets.

For product evidence and explicit testing limitations, see Product Verification. For account help or billing issues, use Contact and Support.

What this page does not promise

No software can truthfully guarantee error-free code, automatic prevention of all vulnerabilities, universal zero data retention or permanent provider availability. Coduf's goal is to make permissions, information flow and review responsibilities understandable so a developer can make an informed decision.

PUT IT INTO PRACTICE

Your next project starts here.

Explore the desktop app and choose the plan that fits your workflow.