Trust Center

Security you can verify, not just claims.

AiCodeStation runs close to your code, your credentials, and your keys. This page explains exactly how it protects them, and points to the evidence behind every statement, from signed installers to a deny-by-default network policy.

Local-first by design

Your source code stays on your machine.

AiCodeStation is a desktop application. Your code, projects, and keys stay local and leave your machine only when you explicitly invoke an action that needs a network, such as calling an AI provider, importing a repository, or checking a dependency for known vulnerabilities.

No tracking

No analytics or telemetry, of any kind

The application bundles no usage-tracking SDK: no analytics, no session recording, no behavioral telemetry. Your editing, browsing, and command activity are not collected or transmitted.

You decide

The network is used only when you ask

AI requests, repository imports, and security lookups happen only when you trigger them. Two mutually-exclusive AI modes are available (your own provider key sent directly to the provider, or an optional AiCodeStation broker), alongside fully local models.

Minimal identity

Device licensing uses a one-way hash

License checks identify your device with a SHA-256 hash of hardware identifiers, rather than storing or sending the raw identifiers themselves.

Credential protection

API keys and tokens live in your operating system keyring.

Secrets are stored through your OS-native credential store (Windows Credential Manager, macOS Keychain, or the Linux Secret Service), never in plaintext configuration files.

OS keyring

Native, encrypted secret storage

Provider keys, refresh tokens, at-rest encryption keys, and the audit-chain signing key are all held in the OS keyring under a dedicated service entry.

No insecure fallback

If the keyring is unavailable, new secrets are not saved

When no keyring backend is present, the app refuses to write new secrets rather than falling back to an insecure store. Secrets from older versions are migrated into the keyring, then removed from the legacy location.

Server-enforced access

Paid capabilities are enforced by our servers, not by the client.

Entitlements arrive as a cryptographically signed manifest and are verified before any capability unlocks. The client is fail-closed by default: on any error, capabilities clear to none.

Signed manifest

Ed25519-verified entitlements

The entitlement manifest is verified with an Ed25519 signature. Editing or deleting local configuration cannot unlock features; an unsigned or missing manifest grants nothing.

Fail-closed

Errors reduce access, never expand it

If verification fails or the cache is tampered with, the previous entitlement cache is cleared and the client falls back to no paid capabilities.

Per-action grants

Sensitive tool runs are authorized server-side

Higher-risk actions request a short-lived, signed grant from the server, which checks entitlement and scope before the action is allowed to proceed.

Zero-trust network egress

Outbound connections follow a deny-by-default allowlist.

The application ships with an explicit allowlist of the hosts it may contact. A monitor mode (default) flags any off-list connection; an enforce mode blocks it outright. These are the categories it can reach, and why.

First-party

AiCodeStation services

api.aicodestation.com and its subdomains: licensing, entitlements, the optional AI broker, and the signed plugin catalog.

Sign-in

Identity providers

Google, Microsoft, GitHub, GitLab, Bitbucket, and Codeberg, only for the sign-in and repository flows you initiate.

Billing

Payments via an approved processor

An approved merchant of record handles checkout and subscription billing. Card data is processed by that provider and is not stored by the app.

AI providers

Only the models you use

With your own key, the app connects to that provider directly, for example OpenAI, Anthropic, Google, Azure, or Groq, and others you configure.

Package registries

Dependency and tool sources

PyPI, npm, crates.io, Maven Central, RubyGems, the Go proxy, and raw GitHub, used when you import or run tools that fetch dependencies.

Security feeds

Vulnerability intelligence

OSV, CISA, and FIRST, queried with dependency names, versions, and CVE identifiers to check for known vulnerabilities.

Local AI models

Offline model downloads

Hugging Face, to download the local speech-to-text (Whisper) model used for offline voice input.

Signed and verified builds

Installers and updates are cryptographically signed.

Every release is signed so you can confirm it came from us and was not modified in transit.

Windows

Authenticode-signed installer

The Windows installer is Authenticode-signed by AiCodeStation LLC through Microsoft Trusted Signing, and timestamped so the signature stays valid over time. You can confirm it in the file’s Digital Signatures tab before running it.

Updates

Signed update manifests

Updates are delivered as a release manifest signed with a pinned Ed25519 key. The app verifies the signature against its built-in key before an update is offered or applied.

Verify

Check the hash yourself

Each release publishes the exact filename, size, and SHA-256 hash. Compare the hash of your download before installing; the steps are on the download page.

Controlled execution

Automated actions are confined to your workspace.

Automated file operations are scoped to the project you are working in, and an optional hardened sandbox is available for full-auto runs. We describe this precisely so you know exactly what is and is not isolated.

Workspace containment

Agent file access stays inside the project

Automated read, write, and search operations are path-confined to your workspace. Sensitive locations such as .ssh, .aws, .azure, .gnupg, and .git are refused, and parent-directory escapes are blocked. Backups are written outside the workspace so a run can be reverted.

Optional sandbox

Hardened Docker sandbox (opt-in)

For full-auto runs on Linux, an optional Docker sandbox runs with no network, dropped capabilities, no-new-privileges, a non-root user, a read-only filesystem, and a disposable copy of the repo. It is off by default and server-gated. Everyday commands are not run in this sandbox unless you enable it, and because a container shares the host kernel it is defense-in-depth rather than an absolute guarantee.

Data and privacy

Clear about what data exists, where it lives, and who controls it.

AiCodeStation is operated by AiCodeStation LLC. Application data and licensing services are hosted on Microsoft Azure in the United States, with standard contractual clauses for cross-border transfers. The privacy policy documents each data flow in detail.

Have a security question or a disclosure to report?

We welcome responsible disclosure. Reach our team through the contact page, and review the full privacy policy and end-user licence for the complete data and legal detail.