What happens to your data

This page covers the Codepit desktop app, the Codepit app for iPhone, the remote in your browser at codepit.app/p, and this website, codepit.app. Last updated on 3 November 2026.

Who we are

Codepit is an independent app, not made by or affiliated with Anthropic. It is made by Wiktor Strzyżakowski Business Lab (Wiktor Strzyżakowski, sole trader, NIP 1182316211), ul. Josepha Conrada 14/8, 01-922 Warszawa, Poland, who is responsible for the data described here. Questions about privacy, or a request about your data: hello@codepit.app.

The desktop app

• Claude. Codepit runs the Claude Code you have installed, signed in with your own Claude account. What you write in a chat, the files Claude reads and what it answers travel between your computer and Anthropic, exactly as they do in a terminal, under Anthropic's privacy policy and the terms of your plan. Codepit never sees your sign-in and sends nothing to Claude of its own.
• On your computer. Your settings, chat list, notes, night shift lists and paired phones stay in Codepit's folder on your computer. The chats themselves are the ones Claude Code keeps.
• No analytics. Codepit sends no usage data, crash reports or telemetry anywhere.
• Updates. Codepit asks codepit.app whether there is a newer version and downloads it from there. Like any download, our server sees your IP address and the file asked for; see "This website" for how long that is kept.
• GitHub, only when you use it. Signing in to GitHub, the same chat on your other computer, Live with your team and pull requests go between your computer and your own GitHub account, through GitHub's own tools. The chat history for your other computer is kept in a private repository on your account, with the skills a chat used, so they come along, and a list of your projects (with the icon you picked for each) and of your computers (each one's name, system and when it was last seen, never a key). A chat you delete is marked as deleted there and removed from the repository after 48 hours. We never see any of it.
• Models on your computer. Suggestions as you type and chats on a local model run on your own computer, through the model tool you installed there. What they read stays on your computer.
• Other services, only when you use them. Searching for a model in Local AI asks Hugging Face. Pictures and charts that Claude draws in the chat can load their drawing code from public code libraries (cdnjs, jsDelivr, unpkg) and fonts from Google Fonts. Connectors, Claude in Chrome and the like work through Claude Code, under your own settings there.

Your computers together

• Tasks between computers. When you connect your computers to each other, they can hand each other tasks and share a render. The tasks, the frames and their files go through the relay on codepit.app, sealed end to end like the phone's messages, so the relay cannot read them. To connect two computers with a short code, the relay keeps a scrambled form of the code (a SHA-256 hash) in memory for at most two minutes, to match them once, and never writes it down.
• Chats from another computer. If you allow a computer to see your chats, their list, what each one is doing and what you write go to it live through the relay, sealed end to end, so the relay cannot read them.
• Sub-chats on another computer. When a sub-chat runs on your other computer, your code as it is, unsaved files too, goes there over the same sealed link as a patch (a list of changes). A patch too big for that goes through the project's own private repository on GitHub instead, under a hidden reference that does not show up as a branch.
• A screen from afar. If you allow a phone or another computer to use a computer's screen, pictures of that screen, your clicks and typing, and what you copy and paste between the two go through the relay in the same sealed boxes. It is off for every device until you turn it on for that one, only one device can be in at a time, and the screen shows a bar with Stop while it is. Nothing of it is kept on the way.

On your phone

• Pairing. You pair the phone by scanning a QR code that Codepit shows on your computer. The camera is used only for that. The code holds a key made for that phone; the phone keeps it in its Keychain and your computer keeps its copy. An unused code stops working after 15 minutes. A phone can be paired with several computers; each one keeps its own copy of what it needs.
• Sealed on the way. Your phone and your computer reach each other through a relay on codepit.app. Everything they say to each other is sealed with that key (AES-256-GCM), so the relay passes along boxes it cannot open.
• What the relay keeps. No accounts, no messages and no access log. While a phone or a computer is connected, the relay holds in memory which computer is online (as an id made from a secret on your computer), which phone connections belong to it, and how many connections come from one network address, to stop abuse. It forgets all of it when they disconnect.
• Notifications. If you allow them, the phone gives your computer its notification token, and your computer keeps it. For each notification, your computer sends the token and a sealed note through the relay to Apple's push service. Apple and the relay see only a general line such as "Claude needs you", an id to group notes from one chat, and the sealed note, which the phone opens itself.
• In a browser. The remote also works in a browser at codepit.app/p. There the pairing key is kept in that browser's own storage (IndexedDB), on that device only, in a form the page can use but not read out, and the messages are sealed the same way.
• Siri and Shortcuts. Asking what Codepit is doing, or stopping it, goes from the phone to your computer through the relay, sealed like the app's own messages. Sending a request to Claude by voice is off until you turn it on in the app's settings and asks for Face ID each time; then what you said goes the same way to your computer, and from there to Claude. Siri itself hears you under Apple's privacy policy.
• Face ID. The lock is handled by iOS. Codepit only learns whether it opened.
• No tracking. The iPhone app and the remote in your browser have no analytics, no ads and no tracking. The iPhone app comes through Apple's App Store (test versions through TestFlight), where Apple's privacy policy applies; Apple may share crash reports and feedback you choose to send with us.

This website

• No cookies, no analytics, and nothing loaded from other sites: the fonts, pictures and scripts come from codepit.app itself.
• Toolbox. Each tool's page in the toolbox shows its author's GitHub picture and, for some, the author's own screenshots or clips. We copy those to codepit.app when we build the site, so opening a page asks no other site for anything. Links to a tool's source take you to GitHub only when you click them.
• Like most web servers, ours writes a log of each request: your IP address, the time, the page or file asked for and what your browser says it is. We use it to keep the site safe and find problems, and it is deleted after 14 days. The phone relay keeps no such log.
• If you turn the demo's sound on or off, your browser remembers that on your device. It is never sent to us.

The waiting list

• What we keep. Your email address, the note you add if you add one, when you joined, and whether you have access yet.
• Why. To send you your download links when your spot opens. You give us the address for that, and you can take it back at any time.
• Download links. Your links are for you, so we count downloads, note the day of the first one and keep a short scrambled fingerprint of the networks they come from (made from part of the IP address, which itself is not kept). Past a few networks, downloads or weeks, the link stops and we take a look.
• Emails. We send them through Resend, which sees your address and what the email says, only to deliver it. To stop sign-up spam, the server remembers which IP addresses signed up in the last hour, in memory only.
• Leaving. Every email from us has a link that deletes your address from the list. Otherwise we keep it until the waiting list closes.

Your rights

You can ask what we hold about you, have it corrected or deleted, take back your consent to the waiting list, or object to how we use it. Write to hello@codepit.app. You can also complain to the data protection authority where you live.

Changes

When Codepit starts doing something new with data, this page changes first, with a new date at the top.