Privacy Policy

This policy covers LocalDesk's website at localdesk.dev, your LocalDesk account, pre-orders and payments, and the LocalDesk desktop app. LocalDesk (“LocalDesk,” “we,” “us”) is responsible for the personal information described here.

Local-first, explained. LocalDesk is designed to keep your work on your Mac where it can. That doesn't mean nothing ever leaves your device: signing in, conversations with LocalDesk, Missions and runs use LocalDesk's servers and an AI model. This policy explains what stays on your Mac, what is sent, and why.

• Account information. Your name, your email address, and the password you create. Your password goes to our authentication provider, which stores it hashed; LocalDesk's own systems never store it. If you sign in to the app with Google or GitHub instead, we receive the account details that service shares with us, such as your name and email address.
• Access and order records. The LocalDesk identity issued to you (a nickname, your number in LocalDesk's access sequence, and your Pre-order ID), your plan, and the status and timing of your access.
• Payment and transaction records. For each payment request: the network, the asset, the exact amount, the receiving address, its expiry, and its status. For each transfer we verify: the network, the transaction hash, the sending wallet address, the amount, and when it was confirmed.
• Usage and device information. Our hosting provider processes standard request information, such as your IP address, browser type, and the pages requested, to deliver and protect the site. We also use IP addresses to apply rate limits, and keep them for that only in hashed form.
• Measurement and attribution. If you allow it, our pages count a few moments of a visit, such as its first page or a pre-order step reached, with the page path and where the visit came from. These counts carry no name, email, account, or wallet. If you then start a checkout, the source and any Founder referral code are saved with your account, so we know where your pre-order came from. See Cookies & Privacy Choices.
• Communications. Messages you send us, such as support, refund, or privacy requests, and what we need to answer them. Our authentication provider sends your account emails, such as email confirmation and password reset.
• Founding event information. If you took part in Mehrad vs Internet: your Founding number, the name on your Founder Card, your Missions and whether each is public, and the link or site that brought you.
• Desktop app information. What the LocalDesk app keeps on your Mac and what it sends, described in the next two sections.

A Founder Card and the Mission Wall show only what you chose to make public. Your email address, payment details, wallet, and private Missions are never shown.

When you connect a project, the LocalDesk app keeps its working records in a local database on your Mac: your projects and where they are on disk, Missions with their plans, approvals, acceptance criteria and evidence, conversation history, results returned by connected tools, and checkpoints with the earlier contents of files it edits. Context is kept as references to your files, not copies of them. LocalDesk doesn't encrypt this database itself; it's protected by your Mac account and its disk encryption.

The app keeps your LocalDesk session in the macOS Keychain, and writes diagnostic logs on your Mac. Version 0.1.0 includes no crash-reporting or analytics service.

This information stays on your Mac unless a feature described below needs part of it. You can delete Missions and disconnect projects in the app.

Some features work through LocalDesk's backend and the AI model it's configured to use. When you use them, the backend receives:

• Sign-in. Your email address and password, or the Google or GitHub account you choose, to sign you in to the app.
• Conversations. The messages you send LocalDesk, the conversation so far, your project's location, and an overview of the project: its Git branch and commit, its top-level folders and files, and excerpts of files that describe it, such as package.json. Files that commonly hold secrets are left out of that overview.
• Missions and runs. A Mission's description and project details, and the activity of its runs. Before a run starts, the app asks you to acknowledge that repository excerpts and command output are sent to the configured AI model to decide each step; a run doesn't start without that acknowledgement.
• Voice input. If you speak to LocalDesk, the app asks for microphone access, and the audio you record is sent to the backend to be transcribed.

AI model providers. The context a request needs is processed by the AI model provider LocalDesk uses to generate a response, under that provider's own terms and privacy policy.

Your own API keys. LocalDesk 0.1.0 doesn't ask for or store your own AI provider API keys. Model requests go through LocalDesk's backend, so a model provider doesn't bill you for them. If you connect a tool or service that uses your own account, that service may charge you under its own terms.

You can connect external tools to LocalDesk through tool servers (MCP). LocalDesk records what each tool may do and asks you to grant its use once, for a session, for a Mission, or for a project. A tool receives the information LocalDesk passes to it for the work you approved, and handles it under its own terms.

LocalDesk is designed not to give connected tools its own data or common credential locations, such as your SSH keys and cloud provider credentials. Connected tools run with your user account's permissions, so these are safeguards in LocalDesk, not operating-system barriers. Version 0.1.0 doesn't store sign-in credentials for connected tools. The Security page describes these boundaries.

We use payment and transaction records to verify your payment on the blockchain, activate your access, keep financial records, prevent fraud and duplicate payments, and answer support and refund requests. To verify transfers, our servers read the blockchain through a blockchain data provider.

Blockchain transactions are public. A transfer you send is recorded permanently on its network: the sending and receiving addresses, the amount, and the time are visible to anyone, and no one, including LocalDesk, can change or remove them. The link between a transfer and your LocalDesk account stays in our records.

Wallets. If you pay with a browser wallet, LocalDesk asks your wallet to prepare one transfer for you to approve. We never receive your wallet's private keys or recovery phrase, and we can't move funds from your wallet.

LocalDesk doesn't take card payments today, so we don't receive card details.

• To provide the Services: your account, checkout, your access, and the app's features.
• To verify payments, activate access, and keep records of purchases.
• To send account emails, such as email confirmation and password reset, and to answer your messages.
• To protect LocalDesk and its users: rate limits, payment verification, and investigating misuse.
• To understand which pages and links bring people to LocalDesk, where you allow measurement.
• To meet legal, accounting, and tax obligations.

LocalDesk doesn't sell personal information, and doesn't use it for targeted advertising.

Legal bases. Where the GDPR or similar laws apply, we rely on our contract with you (your account, purchases, and the Services), our legitimate interests in securing and improving LocalDesk, your consent (optional measurement, which you can withdraw at any time), and our legal obligations.

We share personal information only with providers that help us run LocalDesk, and only as their work requires:

• Supabase. Authentication and our account and payment database.
• Vercel. Hosting for this website and for LocalDesk's backend, including request logs.
• Alchemy. Blockchain data, used by our servers to verify transfers.
• AI model providers. Processing the context of AI requests, through LocalDesk's backend.

Between LocalDesk's systems. When a payment is confirmed, the website sends your email address, plan, payment reference, and confirmation time to LocalDesk's backend, so that your app access can be issued.

When the law requires. We may disclose information when the law requires it, or where it's needed to protect the rights, safety, and security of LocalDesk, our users, or others.

International transfers. Our account and payment database is hosted in the European Union (Ireland). Our hosting and blockchain data providers are based in the United States, so your information may be processed there and in other countries where they operate.

The website uses a few essential cookies and browser storage for sign-in and checkout, and optional measurement only where you allow it. It loads no advertising or third-party analytics tools. Cookies & Privacy Choices lists each one and lets you change your choice.

We keep account, access, and order records while your account exists, and afterwards for as long as we need them for the purposes in this policy, including accounting, tax, and legal obligations, resolving disputes, and preventing fraud.

• Payment records. Kept as part of LocalDesk's financial records. The blockchain transactions themselves can't be deleted by anyone.
• Measurement cookies. Expire after 30 days, and are removed as soon as you turn measurement off.
• App data on your Mac. Stays on your Mac until you delete it in the app or remove the app's data.

Deleting your account. To delete your account, contact LocalDesk. Deleting it removes your sign-in, your access record, and the records linked to them. Before an account is deleted, we set aside the records the law requires us to keep, such as payment records, and keep them only for as long as it requires.

Depending on where you live, you may have the right to:

• access the personal information we hold about you, and receive a copy of it in a portable format;
• correct information that is inaccurate or incomplete;
• delete your information, or restrict how we use it;
• object to processing based on our legitimate interests;
• withdraw your consent at any time, without affecting what was done before;
• complain to your data protection authority.

Making a request. Send your request to LocalDesk. We may need to confirm your identity first, for example by confirming the email address on your account. Exercising a right never changes the price or quality of the Services you receive.

Choices you can make now. Turn optional measurement on or off in Cookies & Privacy Choices, and reset your password from your account.

LocalDesk is built for professional work and isn't directed to children. You must be old enough to form a binding contract where you live to create an account or buy. If you believe a child has given us personal information, contact LocalDesk and we'll delete it.

We'll update this policy as LocalDesk changes. Each version is published here with its date, and we'll tell you about material changes before they take effect.

Questions about this policy or your information go to LocalDesk.