Security

On the website, you sign in to your LocalDesk account with your email address and a password. Your password is handled by our authentication provider, which stores it only in hashed form. Every request that reads or changes your account, a payment, or your access is checked on our servers against your signed-in session.

Access rules in our database let each member read only their own records, and payment and access records can be changed only by our servers. Account creation, invite checks, and other sensitive requests are rate limited.

LocalDesk doesn't offer multi-factor authentication yet, so use a strong password that you don't use anywhere else, and sign out of browsers you don't control.

The LocalDesk app keeps your session in the macOS Keychain. Its local database refers to your project files rather than copying them, but it does keep your conversations, results from connected tools, and the earlier contents of files it edits. LocalDesk doesn't encrypt that database itself: it's protected by your Mac account and its disk encryption, such as FileVault.

LocalDesk is designed to keep its own data, your other projects, and common credential locations, such as your SSH keys and cloud provider credentials, out of what it gives connected tools. These are safeguards built into LocalDesk, not operating-system restrictions: connected tools and the commands you approve run with your user account's permissions.

LocalDesk 0.1.0 doesn't ask for or store your own AI provider API keys: model requests go through LocalDesk's backend. It doesn't store sign-in credentials for the tools you connect either.

The website never holds wallet private keys or recovery phrases, and it can't move funds from your wallet. The keys and credentials our servers use stay on our servers and are never sent to your browser.

LocalDesk will never ask for your password, your recovery phrase, or your private keys. Never share them with anyone.

• For a Mission, you approve its plan and the files it may change before it runs. If the plan changes, LocalDesk asks you to approve it again.
• A run carries out only the commands you approved for it.
• For connected-tool calls that involve credentials or could destroy data, LocalDesk asks you every time instead of remembering your answer.
• Before LocalDesk edits a file within a Mission's approved boundary, it saves the file's earlier state.
• When your project changes, a Mission's results are checked again rather than assumed to still hold.

What approval means. The app doesn't run in a sandbox. A command you approve runs with your user account's permissions, so it can read, change, or delete anything your account can, including files outside your project. A run you allow to write files can change files across your project, and those changes aren't saved as checkpoints. Approve only commands you understand, take extra care with anything that deletes data, deploys, or touches credentials, and keep backups and version control for work that matters, as the Acceptable Use Policy asks.

Untrusted content. Files, web pages, and tool output can contain instructions written to mislead an AI system. Review what LocalDesk proposes with particular care when it works with content you didn't write or don't trust.

• Our servers set the price of every order from the plan you choose. Your browser can't change the price, the amount due, or where payment is sent.
• Each payment request has its own exact amount. A transfer counts only after our servers verify it on the blockchain itself: the right token on the right network, the exact amount to LocalDesk's receiving address, and enough confirmations.
• A transaction hash or a notification from another service is never proof of payment on its own: every transfer is checked against the blockchain first.
• The same transfer can never be counted twice. A transfer of the wrong amount, one sent after its request expired, or a second payment doesn't complete an order automatically: it's set aside for review, and you can request a refund.
• Access is granted by our servers, never by a browser.

The Pre-order & Payments policy explains the payment steps you see.

The website is served only over encrypted HTTPS connections, and browsers are told to always use them. Other sites can't embed its pages, and a content security policy limits where its pages can load resources from.

Payments and access are changed only by our servers, with credentials that never reach a browser.

The desktop app relies on LocalDesk's servers, not on anything stored on your Mac, to decide which features your account can use.

Our payment systems record unexpected events, such as a wrong amount, a duplicate payment, or a blockchain reorganization, so they can be reviewed, and none of them grants access.

We can suspend access to an account to contain a problem. If we learn of a security incident that affects your personal information, we'll investigate it and notify you and the authorities where the law requires.

If you believe you've found a vulnerability in LocalDesk, please report it privately, as our Responsible Disclosure policy describes.