1. Your workspace stays on your Mac
Starkomand stores your canvas, notes, tasks, preferences, backgrounds and connection settings locally. The local terminal server processes your commands and output. The app does not automatically upload workspaces, crash reports or adoption metrics.
In new releases, starting a trial does not require an email or account. When you choose Start free trial, the app sends a random installation identifier and an app-specific cryptographic hash derived locally from your Mac’s platform identifier to Starkomand’s Cloudflare-hosted trial service. Cloudflare D1 stores this pseudonymous Mac identifier, a random trial reference, the original trial dates, last check time, hashed session credentials and administrative trial-termination records. Reinstalling on the same Mac restores its original deadline. The raw platform identifier and workspace contents are not sent. An internet connection is required to start or restore a trial and at least once every 24 hours during the trial. Temporary keyed hashes of Mac identifiers and IP addresses limit registration abuse. Raw IP addresses are not stored in the trial database, although Cloudflare processes normal network metadata. We retain trial history to enforce the trial limit and help with support.
Older releases use email verification. For those releases, the trial and email delivery services process the requested email to send a code. D1 stores verified emails, verification times, keyed email hashes and any optional outreach preferences separately from trial enforcement. Pending codes expire and are cleaned up during later trial requests. Existing contact records and communication preferences are preserved when you update. Starting or restoring a trial in a new release does not add an email contact or subscribe you to messages.
Your agents and connected services can still send information off your Mac, as described below. This policy covers the data handled by Starkomand’s operator, Developer Timeline; it does not replace those services’ policies.
2. Connected tools receive what they need
- Agents: prompts, code, files and terminal context may go to your chosen provider, using your existing sign-in and permissions.
- Work summaries: nothing is summarized automatically. When you ask for a summary (⌘K → Summarize whole canvas, or Summarize selected agents), the recorded terminal text of those agent windows goes to the writer chosen in Settings → Privacy → Work summaries: the Claude or Codex CLI with your sign-in, or an OpenAI-compatible service with a key you enter, which is kept in a private file on your Mac. Until you choose, the writer is whichever of Claude or Codex is installed. Starkomand never falls back to another writer, and Off means terminal text is never sent for a summary.
- Window backs, routing and squads: a window’s back is built on your Mac from the agent CLI’s own session files and the activity hooks Starkomand adds to its launch; Auto model routing decides locally; squad journals stay on your Mac. None of them calls a model. A handoff, or continuing a conversation on another plan, gives the receiving agent a brief drawn from the recorded conversation, which then goes to that agent’s provider.
- GitHub and usage: the app uses your credentials to request repository, issue, pull-request, contribution and provider-usage information from the relevant service.
- Browser previews: the websites you open receive normal browser requests and may use their own cookies and tracking.
Those providers set their own retention and model-training policies. Deleting something locally does not delete a provider’s copy.
3. Voice and camera are optional
Default dictation processes speech on your Mac. Its first setup downloads the local runtime and model; those download hosts receive ordinary connection information.
If you choose OpenAI dictation, your audio is sent to OpenAI using your API key. Text submitted to an agent may then go to that agent’s provider, regardless of how it was transcribed.
Hand tracking processes camera frames locally without uploading them through that feature. You can turn off voice or hand control and revoke microphone or camera access in macOS Settings.
The backdrop library is fetched from Starkomand’s Cloudflare storage only when you open it, and a backdrop you pick is downloaded and kept on your Mac. These requests carry no account, cookie or identifier; Cloudflare processes normal network metadata.
4. Website, purchases and support
Cloudflare hosts this website and may process IP addresses, requested pages, browser information and security logs to deliver and protect it. The site sets no cookies and stores nothing in your browser; the Cookie Policy covers the security cookies our host can set. It uses Cloudflare Web Analytics, which counts pages viewed, referrer, country and device type without cookies, advertising pixels or cross-site tracking.
Dodo Payments handles checkout, billing and card information. We may receive your email, order details and payment status to deliver and support your license. When you activate Starkomand, the app sends your license key and a random installation identifier to Dodo Payments. License verification and deactivation send the key and its activation identifier. These requests do not include your files, workspace contents or Mac account name.
The app stores your trial dates and license activation in an encrypted record on your Mac using macOS-backed encryption. It verifies activated licenses when the app starts; a temporary connection failure does not remove previously activated access. Deactivating a license frees its activation slot for another Mac.
If you contact support, we receive your email and anything you send us. Please leave out passwords, API keys and unrelated private information.
5. Why we use and share information
We use information we receive to run the website, fulfill purchases, answer support requests, prevent abuse and meet legal obligations. We do not sell personal information or share it for behavioral advertising.
Hosting, payment and support providers receive information needed for their role. We may also share records when required by law, to protect legal rights or during a business transfer with appropriate safeguards.
Where data-protection law requires a legal basis, we rely on fulfilling our agreement with you, legitimate interests in operating and securing the service, legal obligations, or consent where required. Providers may process data in other countries; legally required transfer safeguards apply.
6. Keeping and deleting data
Local data stays until you remove it. Uninstalling the app may leave preferences, model downloads, credentials or agent history behind. Temporary squad files are normally cleaned up when sessions end, but backups or interrupted shutdowns can leave copies.
We keep support records while needed to resolve requests and related claims. Purchase records are kept to support licenses and meet accounting, tax and other legal requirements. Cloudflare’s operational records follow its service configuration and retention practices. Records we no longer need are deleted or anonymized; backups may take longer to expire.
Protect your Mac, credentials and backups. No software or storage system is completely secure.
7. Your choices and rights
You can clear local data, disconnect integrations, remove saved keys and use local dictation. Use a provider’s own controls to revoke its tokens or delete information it holds.
Depending on your location, you may ask to access, correct, delete or receive a copy of personal information we hold, object to or restrict processing, or withdraw consent. Some records must be kept by law. Email [email protected] to make a request. We may need to verify your identity. You can also complain to your local data-protection authority.
8. Questions and updates
Starkomand is not directed to children under 13. Contact us if you believe a child has sent us personal information.
We update this policy when our practices change and give additional notice where required. For questions, contact [email protected].