Privacy Policy

1. Introduction

This Privacy Policy describes how Cybrix, LLC ("Company," "we," "us," or "our"), operating as Caprock, collects and uses information when you use Caprock, a local, open-source desktop app for Claude Code and other coding agents, and this website (together, the "Service"). Caprock runs on your own machine. It reads the transcripts your coding agents already write to your disk, and what it computes from them — who is waiting on you, what each session and pull request cost — stays there. Caprock does not send your prompts, credentials or usage to Cybrix. It reaches the network only for a feature you switch on (section 4) or a message you press Send on (section 2). Caprock for Teams is a server a team installs on a machine it owns. Each developer's Caprock sends it aggregates only. Sums without content and without per-person rows: cost and sessions per repository, per pull request, per release, per week. The team payload has no field for prompts, replies or tool output, so a misconfiguration cannot leak one. Those reports go to the team's own server, never to Cybrix.

2. What We Collect

We collect messages, purchase details and site analytics:

• ·Messages: your email and what you write, if you send feedback, ask about the team version or email us
• ·Install link: your email, if you ask us on your phone to email you the link to Caprock. We send that one email and nothing else
• ·Bug reports: only when you press Send to support in the app's Report a bug, your text, up to three screenshots you attach, your email if you give one, and the Caprock version and operating system. Never transcripts or logs. Screenshots are deleted after 90 days
• ·Survey answers: only when you press Send on a question the app asks, your answers and your email if you add one
• ·Shared week cards: only when you press X, Threads or LinkedIn on the app's week card, the card picture you chose and nothing else. It shows totals, never names, file paths or repositories. We store it on caprock.dev so the post can show it as a preview, and keep it until you delete it from the app. X, Threads and LinkedIn may keep their own copy of a preview, which deleting it here does not remove
• ·Purchases: your email, the plan you bought and the licence key we issue. Stripe handles the payment; your card details go to Stripe, never to us
• ·Site analytics: page visits and button clicks on caprock.dev, counted by Umami without cookies or cross-site tracking

3. What We Do Not Collect

Caprock never sits between you and Anthropic. It reads the transcripts your coding agents already write to your disk. None of the following reaches Cybrix:

• ·Your card number or any payment credentials
• ·Your prompts, model responses or anything your coding agents process
• ·Your Anthropic or other provider credentials and configuration
• ·Your usage, cost data or anything shown on the Caprock dashboard, which is computed and stored on your machine
• ·Your use of a licence key, which is checked on your machine without contacting us

4. Optional Features That Use the Network

Each is off until you turn it on or ask for it. When on, it connects your machine directly to the service named; only the relay and the phone page (m.caprock.dev) that a paired phone or a linked computer goes through are run by us:

• ·Release check: the desktop app asks GitHub for the latest Caprock release every 15 minutes and when you come back to its window, never more than once in ten minutes unless you ask. The desktop app asks once, on its first launch, whether to turn it on. It sends nothing about you, not even your version; GitHub sees your IP address
• ·App updates: when you check for updates or press Update, the app fetches the release's update manifest (latest.json) and, to update, the new build from GitHub's release downloads, and installs it only if it checks out against Caprock's update key. Nothing about you or your work is sent
• ·GitHub connection: off until you connect your account in the app's settings. Then the Caprock daemon on your machine calls GitHub's API (api.github.com) with your token, to list your repositories, create a repository or pull request when you ask, and read checks and reviews. The token stays on your machine — in your macOS login keychain, a file only you can read, or your own GitHub CLI login — and never reaches the dashboard, your phone or us. Disconnecting removes the token Caprock kept
• ·Weekly report: sends a summary of your figures to your own Telegram bot
• ·Phone alerts: when a session waits for approval or finishes, sends to your own Telegram bot the agent, the project and session title, the folder and branch, the command, file, URL or question it asks about (up to 100 characters), for a finished run its duration, cost, tool calls, the files it changed and the first line of the reply, and a link to the session when phone access is on — never tool output
• ·Ask your numbers: sends your question, with the figures it needs, to Google's Gemini API on your own key
• ·Paired phone or tablet: opens Caprock's page at m.caprock.dev and reaches your machine through Caprock's relay (relay.caprock.dev, or one you run), encrypted end to end. The relay sees which machine a phone connects to, when, from which IP address and how many bytes pass, never a session, and stores nothing. The command caprock up --lan pairs over your own Wi-Fi without it. A paired phone can control sessions unless you untick that before showing its pairing code, and Take control away in settings makes it view only
• ·Caprock for iPhone: the App Store app shows the same phone page, bundled inside the app rather than loaded from m.caprock.dev, and reaches your machine the same way, through the relay, encrypted end to end. It has no analytics, crash reporting or advertising, and we collect no data from it. The camera is used only to read the pairing code and records nothing; voice input is recognised on the iPhone and is not sent; Face ID is answered by iOS and never reaches the app or us. The demo uses sample data built into the app and sends nothing
• ·In-app browser (beta): off until you turn it on. It loads the pages you open and sends what you type in its address box to DuckDuckGo, or the search engine you pick

5. How We Use It

• ·Reply to your messages
• ·Deliver your licence key and handle your purchase
• ·Meet legal obligations

6. Who We Share It With

We do not sell your personal information. These services process it for us:

• ·Stripe: payments
• ·Resend: the email that delivers your licence key, the install link you ask for and our replies
• ·Cloudflare: hosts this website and stores the answers to the team form, install-link requests, bug reports, survey answers and the week cards you share
• ·Telegram: we receive form messages, bug reports and purchase notices (email, plan and key) in our own chat
• ·Cal.com: if you book a call, it receives your name and email to schedule it
• ·Umami: site analytics, as above
• ·Authorities, only when required by law

7. Security & Retention

We use reasonable measures, including encryption in transit, for the limited data we hold. No internet transmission is ever 100% secure. We keep your data until you ask us to delete it. A week card you shared is kept until you delete it from the app or ask us to, so the post that links to it keeps its preview. Email legal@caprock.dev and we will do it within 30 days.

8. Changes

We may update this policy. Material changes will be announced by email or on this page.