This Policy
This Privacy Policy is issued by AICodeStation LLC, referred to as AiCodeStation, we, us, or our. It applies to individuals outside our organization with whom we interact, including visitors to https://www.aicodestation.com, users of the AiCodeStation desktop software application, account holders, customers, trial users, support contacts, and enterprise prospects.
This Policy describes our practices regarding the collection, use, disclosure, retention, and protection of personal data when you use the Site, Application, accounts, subscriptions, APIs, support channels, contact forms, and related services, collectively referred to as the Service.
How We Collect Personal Data
We collect or obtain personal data directly from you when you create an account, submit a contact request, request support, purchase or manage a subscription, provide feedback, communicate with us, or use product features.
We may collect technical and usage information automatically when you visit the Site, use the Application, call APIs, submit forms, receive account emails, or interact with security and service infrastructure.
We may receive limited information from third-party services, such as payment processors or merchants of record, authentication providers, GitHub or source-control integrations, email providers, infrastructure providers, analytics tools, and enterprise systems when those services are connected to the Service.
Categories of Personal Data We Process
We may process identity and account data such as name, email address, username, organization, role, account status, hashed passwords, authentication status, activation status, password reset activity, and account-related preferences.
We may process contact and communications data such as messages submitted through the Contact page, support requests, inquiry category, business or personal email address, phone number if provided, company or organization if provided, response history, feedback, and operational metadata needed to respond.
We may process subscription and transaction data such as plan name, subscription status, trial status, renewal status, cancellation status, transaction confirmation, invoice or billing references, and merchant of record or payment processor references. We do not store full payment card numbers on the public Site.
We may process technical, device, and usage data such as IP address, browser type, operating system, Application version, device identifiers where applicable, API request metadata, timestamps, diagnostic logs, crash or performance data, security logs, session metadata, and feature usage signals.
We may process workflow data that you choose to submit or authorize within the Service, including prompts, code snippets, command descriptions, workspace configuration, repository metadata, tool requests, import actions, and developer workflow outputs. You should not submit secrets, passwords, private keys, tokens, or regulated data unless a secure enterprise process has been agreed in writing.
Purposes and Legal Bases for Processing
We process personal data to provide and manage the Service, create and secure accounts, authenticate users, activate accounts, reset passwords, deliver subscription access, operate the desktop Application, respond to inquiries, provide support, and maintain service reliability.
We process data to perform contracts with you, comply with legal obligations, protect legitimate business and security interests, prevent abuse or fraud, improve product quality, communicate important service notices, and, where required, based on your consent.
Service delivery
Account access, activation, password reset, support, subscriptions, API availability, and Application workflows.
Security
Fraud prevention, abuse detection, rate limiting, audit logs, account protection, and infrastructure monitoring.
Product improvement
Diagnostics, performance review, workflow reliability, error correction, and product planning.
AI-Assisted Developer Workflows
When you use an AI feature — asking the assistant, requesting a fix, running an AI-assisted code review — the relevant content is sent to a model provider. Depending on the feature that may include the code or file you are working on, the command you ran, its output and error text, and your prompt.
Where it goes depends on which of two modes you are in, and they are mutually exclusive.
Your own key (the default). The application talks directly to the provider you configured — Anthropic, OpenAI, Google, Azure OpenAI or another compatible service — using an API key you supply, which is stored in your operating system’s credential store. In this mode your content goes to that provider under your agreement with them and does not pass through us.
Our broker, available on plans that include it. Requests go to our servers, which forward them to the provider using our key. In this mode your content passes through us.
Local models. If you point the application at Ollama, LM Studio, LocalAI, vLLM or llama.cpp, nothing leaves your machine at all.
The terminal watcher. When a command in the built-in terminal produces output matching an error pattern, the assistant may offer help, and doing so sends the recent command history and output — which can include file paths and code — to the configured model provider.
You are responsible for reviewing content before submission and for avoiding the inclusion of passwords, private keys, API secrets, customer data, regulated data, or confidential third-party information unless an appropriate secure workflow is in place.
What the Desktop Application Transmits
This section describes the desktop application. The same text is distributed inside the application as PRIVACY.txt.
Before you sign in. The application contacts our servers before you have an account session, so we disclose it separately: a connectivity check repeated every 10–30 seconds while the app is open, which sends no body but reveals your IP address; a configuration fetch at startup that retrieves server-side feature switches and sends no personal data; and, if enabled, an update check that sends only the release channel and an operating-system key, with no account identity and no device identifier. The update check can be switched off in Settings.
Device identification for licensing. To bind a licence to a machine, the application computes a SHA-256 fingerprint from your operating system name, CPU architecture, hostname, machine GUID, network adapter address and operating-system login name. Only the resulting hash is transmitted; the underlying values are not. Alongside it we send a device label of the form “hostname — operating system” in plain text so you can recognise your own devices. If your hostname contains your name, that label contains your name.
Speech. Speech recognition runs locally using a bundled model; audio is processed on your machine. An optional fallback that would send the recording to a third-party cloud service is off and transmits nothing unless you deliberately enable it.
Security scanning. When you scan a project for vulnerable dependencies, the application sends dependency names and versions — not your code — to the OSV database, and CVE identifiers to public advisory services.
Connected services you choose. If you connect GitHub, GitLab or Bitbucket, the application acts on your behalf against that service. Settings Sync, if you use it, stores your tool registry — tool names, local paths, interpreters and repository URLs — in a private Gist under your own GitHub account. Those paths can identify your machine and your projects; the gist is yours and you can delete it.
Optional features that transmit, all off by default. Audit forwarding sends a copy of the local audit log to our servers every two minutes, including your account email, your role and the commands you ran with their file paths; it is intended for organisations that need central audit and have told their staff. Contributing fixes shares the shape of a verified fix — the kind of action, its arguments, and a file’s name without its directory — and never your file contents.
Reading community fixes is on by default. To find a matching fix, the application sends a normalised version of your error message to our servers. Error text can contain a file path. You can switch this off in Settings.
What stays on your computer. Your settings, the tool registry, application logs, the local audit log, your AI usage and cost history, and imported project files are stored locally and are not uploaded by us. Credentials are held in your operating system’s credential store, and the logger masks credential-shaped strings before writing.
Payments, Subscriptions, and Merchant of Record Providers
Paid subscriptions may be processed by a designated third-party merchant of record or payment processor, such as an approved provider. These providers may process payment details, billing details, tax information, fraud prevention signals, transaction confirmations, subscription status, refunds, disputes, and chargeback information.
AiCodeStation receives only the information needed to confirm purchases, manage access, support billing inquiries, and maintain subscription status. We do not ask you to submit payment card details through the Contact page.
Disclosure of Personal Data to Third Parties
We do not sell your personal data. We may disclose personal data to service providers that help us operate the Service, including hosting providers, infrastructure providers, email providers, authentication providers, analytics providers, payment processors, merchants of record, support tools, security tools, and professional advisors.
We may disclose data where required by law, regulation, subpoena, court order, legal process, law enforcement request, or to protect the rights, safety, security, and integrity of AiCodeStation, users, customers, and the public.
If AiCodeStation is involved in a merger, acquisition, financing, restructuring, sale of assets, or similar transaction, personal data may be transferred as part of that transaction, subject to appropriate protections.
International Data Transfers
Your information may be processed in countries other than your country of residence. Data protection laws in those countries may differ from the laws where you live.
Where required, we use appropriate safeguards for international transfers, such as contractual protections or other mechanisms recognized by applicable data protection laws.
Data Security
We implement technical and organizational measures designed to protect personal data from accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or access. These measures may include TLS encryption in transit, password hashing, restricted access, environment-based secret management, rate limiting, monitoring, logging, and operational security controls.
No method of transmission over the Internet or method of electronic storage is completely secure. You are responsible for protecting your account credentials, devices, repositories, workspaces, and any secrets or credentials used in your development environment.
Data Retention
We retain personal data for as long as necessary to provide the Service, maintain accounts, comply with legal and tax obligations, resolve disputes, enforce agreements, protect security, prevent fraud, and support legitimate business operations.
When personal data is no longer needed, we will delete, anonymize, or otherwise handle it in accordance with applicable law and operational requirements.
Your Legal Rights and Choices
Depending on your location and applicable law, you may have rights to request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or information about how your personal data is processed.
California residents and residents of other jurisdictions may have additional rights, including the right to know, delete, correct, opt out of certain sharing or sales where applicable, and limit certain uses of sensitive personal information where applicable. AiCodeStation does not sell personal data as that term is commonly understood.
To exercise privacy rights, contact us through the Contact page. We may need to verify your identity before completing a request.
Children’s Privacy
The Service is not directed to children under 13. We do not knowingly collect personal data from children under 13. If we become aware that we collected personal data from a child under 13 without appropriate consent, we will take steps to delete that information.
Sensitive Information and Secrets
Public pages, support requests, and general Contact submissions are not intended for passwords, private keys, API secrets, recovery phrases, payment card details, regulated health information, financial account numbers, or confidential third-party customer data.
If your organization requires a sensitive enterprise workflow, contact us first so an appropriate process can be evaluated.
Changes to This Policy
We may update this Privacy Policy to reflect changes in our practices, technologies, legal requirements, or services. The updated version will be posted on this page with a revised date.
We encourage you to review this page periodically.
Contact Details
Questions about this Privacy Policy, data processing, or privacy rights requests can be sent through the AiCodeStation Contact page.