LOCAL COMMANDER / TRUST & SUPPORT

Privacy policy

A clear view of what is handled, what is stored, and what stays under your control.

Pilot service Updated

At a glance

  • Project files and command output are not archived in the cloud by default.
  • Requested results can leave your computer to reach your AI client.
  • Basic account, permission and usage records are stored to run the service and deleted on fixed schedules.
  • Optional full logs are off by default. If the account owner turns them on for a computer, its requests and results are kept for 7 days, encrypted.

Who operates the service

Local Commander is operated by Peter Mamrukov, a private individual based in Israel. Postal address: Miryam Ben Porat 4, Rishon LeZion, Israel. For privacy, support or security questions, contact peter.mamrukov@localcmd.app.

Information we use

You choose whether to provide information and connect a computer. Providing it is voluntary; without a sign-in email and the necessary account and device details, we cannot provide the connected service.

Information and its purpose
InformationWhy it is used
Account and sign-in recordsYour email, account status, sign-in challenges and sessions let you sign in and help protect your account. Accounts we issue a password to (such as app-review accounts) also have that password stored, only as a salted hash. If you sign in with Google or GitHub, we receive that account's ID and verified email address; we store the ID to recognise future sign-ins and use the email to find your existing account or create one.
Device and permission recordsDevice public keys, connection status and authorization records control which computer and actions can be used.
Activity and usage recordsOperation references, timestamps, outcomes, usage counters and limited security records support execution, quotas and troubleshooting. Each operation record also notes which local tool ran (for example, reading a file or running a command) and how many bytes of output it returned and how many it trimmed from that output before sending it to your AI, which helps us improve the service. It never includes the command, its arguments, file paths, file contents or the output itself. Optional full logs, described in section 03, are separate. Security records note sign-ins, device pairing and revocation, permission changes and refused actions.
Setup progress eventsTo see where setup fails and improve the service, we record when your account reaches a setup step: email confirmed, computer paired, AI client connected, first successful task and usage allowance reached. Each event holds only the step, your account’s internal ID and a time. It never includes commands, file paths, file contents, output, your email address or IP address.
Country countsTo understand where the service is used, our server looks up the country of the network address when you use the website signed in or when your computer connects, using an offline database on our server. Only daily totals are kept, such as the number of computers that connected from one country on one day. The address is not stored, and no country is saved for your account or computer. To count each account or computer once a day, we keep a hashed code made from its internal ID and the date, without the country, for up to two days.
Model token countsOff unless the account owner turns them on for a computer in that computer’s details on the website. When on, Local Commander on that computer reads token counts and model names from Claude Code and Codex session files and sends daily totals for each AI client and model, which your Statistics page shows. Nothing else from those files is kept or sent: no prompts, replies, file contents or file paths.
Token counts sent by Claude Code and CodexOff unless you create a key on the Statistics page and add it to Claude Code or Codex. They then send their own usage metrics to Local Commander with that key. Only the token counts, the model name and the day are kept, as daily totals per AI client and model, plus a fingerprint of each received data point for 7 days so a resent one is not counted twice. Everything else they send is discarded on receipt: e-mail, user, account, organization and session identifiers, and all other metrics. Only a hash of the key is stored.

We publish daily aggregate usage statistics on our usage statistics page; they identify no account, computer or person, and any group of fewer than 5 accounts is hidden.

Your files and tool results

Operations run on your enrolled computer. Files, command arguments and results needed for your request may pass through the Local Commander relay to your chosen AI client. That provider handles what it receives under its own privacy terms.

Ordinary cloud execution records store metadata, not a default archive of your project files or command output. Results can be present temporarily in relay memory. The native application also keeps an encrypted local recovery journal that can contain operation results. Optional local audit logging is separate and is off by default.

Full logs (optional). Full logs are off by default. The account owner can turn them on for one computer at a time in that computer’s details on the website; nothing is logged until the owner chooses to keep them. While full logs are on for a computer, a copy of each request it runs through Local Commander is kept: the request, including command text and file paths, and its result, including file contents and command output. The copy is stored in a private Cloudflare R2 storage bucket, encrypted with a key for your account. We hold that key, so the operator can read the logs. Passwords, keys and sensitive files are removed where they are detected, but that is not guaranteed. We use full logs only to troubleshoot requests and problems with the service for that account. Anyone in the account can download its full logs from a computer’s details. Turning full logs off for a computer deletes the copies kept for it; otherwise they are deleted on the schedule in section 05. If other people use that computer, tell them before you turn its full logs on.

Cookies and service providers

We use cookies for sign-in and request security. Browser storage keeps pending connection or pairing references so setup can resume after email sign-in; normal completion removes them. Clearing this storage may sign you out or interrupt setup.

The website, sign-in and relay run on a Netcup server in Austria. Service records are kept in a hosted SQL Server database (databaseasp.net) on servers in Germany. Sign-in email is sent through Resend, an email provider in the United States. For computers with full logs turned on, those logs are stored, encrypted, with Cloudflare R2, a storage service of Cloudflare, Inc., a United States company. Your chosen AI provider receives the results you request. Information is therefore processed in the European Union, in the United States for email delivery, by PayPal for payments, by Cloudflare for full logs where they are on, and wherever your AI provider operates.

If you buy a Computer pack, PayPal processes the payment. You pay on PayPal's site; we never receive your card or bank details. We keep the PayPal subscription and transaction IDs, plan, amount, currency, payment dates and status to provide and verify the Computer pack, and as payment records. PayPal's signed notifications about your subscription can include your PayPal name and email; we store them encrypted and delete them after 30 days.

The reviewed website code contains no advertising or third-party analytics scripts, and setup progress events are stored only in our own database. Google and GitHub sign-in applications are registered. These sign-in methods are shown only when their production configuration is enabled.

Retention and your choices

Records are deleted automatically on the schedules below. Each period is a maximum.

How long records are kept
RecordKept for
Sign-in links and connection requestsUp to 30 days after they expire
Website sign-in sessionsUp to 30 days after they expire or are signed out
Operation and usage detail12 months. Monthly usage totals stay with the account.
Security records90 days
Setup progress events90 days
Daily country totalsKept as anonymous statistics; the codes used to count each account or computer once a day are deleted after two days
Model token counts, including those sent by Claude Code and Codex13 months; deleted when the account is closed
Encrypted copies of sign-in emails7 days after sending
Full logs (only for computers where they are on)7 days, or until full logs are turned off for that computer; deletion can take up to a day longer
Encrypted PayPal notifications30 days
Payment records (PayPal IDs, amounts, dates)While your account is open, then as long as accounting rules require
Account, device and permission recordsWhile your account is open, then closed as described below

To close your account, or to request access to or correction of your information, email peter.mamrukov@localcmd.app from the address on the account. We may need to verify your identity. We complete a verified closure within 30 days. Closing revokes your sessions, connected AI clients, devices and workspace permissions, deletes any password and pending sign-in links, and removes your email address and your account, device and workspace names from our records. Remaining operation detail is then no longer linked to you and is deleted on the 12-month schedule. Closing also deletes the account’s full logs.

Our database hosting provider makes its own backups. Deleted records can remain in those backups until the provider's backup rotation overwrites them. We use backups only to recover the service, and we reapply closures after any restore.

You can revoke available account, client, device or workspace access. Revocation does not undo completed actions or remove results already delivered to your AI client. Contact us if you need help with these controls.

Security and contact

The service uses encrypted cloud connections and protects stored authentication values. Device private keys stay on your computer. These protections do not eliminate every risk, and a permitted local program is not contained by a complete operating-system sandbox.

For a concern, email Peter at peter.mamrukov@localcmd.app with a brief description. Do not send passwords, sign-in links, tokens, private keys or recovery keys. Ask for a secure reporting route before sharing sensitive vulnerability details.