Privacy Policy
Last updated 2026-10-20
This policy explains what personal data Padock handles, why, and what you can do about it. Ihor Sorokin, the owner of Padock, is the controller of that data. Write to [email protected] with any question or request.
In short
- Your code, prompts, terminals and agents stay on your machines. We never see them.
- Between your phone and your machines, everything is encrypted end to end. Our relay passes it on and can't read it.
- We keep what an account needs: your Google email, name and picture, and the machines and phones you connect.
- No analytics, no advertising, no tracking, no crash reports sent to us. We don't sell your data or train AI on it.
What we collect
| What | Details | Why |
|---|---|---|
| Account | From Google when you sign in: email address, name, profile picture link, and Google's account ID. We add: whether you are on the waitlist, allowed or blocked, your role, the update channel you chose, and when you signed up and were last seen. | To sign you in, let you in from the waitlist and keep your account. |
| Machines | For each Mac or server you connect: its hostname, operating system and version, Padock's version, and when it was added and last seen. | To show your machines, connect your devices to them and offer the right updates. |
| Phones | For each phone you pair: the device name its system reports (e.g. “Alex's iPhone”), and when it was paired and last used. | To list your paired phones and let you remove one. |
| Sign-in sessions | Which app or device a session belongs to, and when it was created, last used, expires or was revoked. Tokens are stored only as hashes. | To keep you signed in, and to let you sign out everywhere. |
| Waitlist | Your email address and where you signed up, if you join the waitlist. | To let you in when there's room. |
| Technical logs | For each request to our servers: the method, the address path, the result, how long it took. Your IP address is used for a moment to limit request rates and is not written to our logs. The relay records when a machine connects and disconnects. | To run the service, fix faults and stop abuse. |
| Relay metadata | Which of your devices talks to which of your machines, when, and how much data passes. Never the content: it is encrypted end to end. | To connect your phone to your machines. |
| Messages to us | What you write when you email us, and your address. | To answer you. |
What stays on your devices
Padock does its work on your own machines: your Mac, and any server you connect over your own SSH. Your projects, code, branches, terminals, agent conversations, reviews, browser profiles, test accounts and settings are stored there, not with us. So are the credentials you give it: tokens for GitLab and other services, and the sign-in of your Claude account, which Padock reads from and keeps in your Mac's Keychain.
When Padock uses another service, your machine talks to it directly: Anthropic for Claude and your subscription's usage, GitLab and similar services for code review, Google for your profile picture and the in-app browser's search, GitHub for a public table of AI model prices. Those services handle your data under their own privacy policies.
The phone app uses the camera only to scan the pairing code your Mac shows; the image never leaves the phone. Its keys and tokens are kept in the phone's secure storage.
Legal bases
Under the GDPR and the UK GDPR we rely on:
- Contract: the account, machine, phone and session data, to provide the Padock you signed up for.
- Legitimate interests: the technical logs and relay metadata, to keep Padock running and secure; the waitlist, to let people in in order. You may object; see “Your rights”.
- Legal obligation: where the law requires us to keep or disclose data.
Cookies
padock.dev sets no cookies. The Padock account and admin sites set one strictly necessary cookie, padock_refresh, on api.padock.app: it keeps you signed in, is sent only to our sign-in endpoint, and is removed when you sign out. There are no analytics or advertising cookies.
Who else processes it
| Provider | For | Where |
|---|---|---|
| Hetzner Online GmbH | Hosting our servers and database | European Union |
| Cloudflare, Inc. | DNS, and the network that carries traffic to our sites, API and relay (it sees IP addresses) | Worldwide |
| Google LLC | Sign-in with Google | Worldwide |
| Apple Inc., Google LLC | Distributing the phone apps through the App Store and Google Play, under their own policies | Worldwide |
We share personal data with no one else, except when the law requires it, to protect people's safety or our rights, or as part of a merger or sale of the business, which would keep this policy's protections.
Where data leaves the European Economic Area or the UK, it is protected by the European Commission's Standard Contractual Clauses or an adequacy decision, such as the EU-US Data Privacy Framework.
How long we keep it
- Account, machine and phone data: while your account exists. A machine or phone you remove is deleted at once.
- Sessions: deleted 7 days after they expire; one-time sign-in codes within minutes.
- Technical logs: up to 30 days.
- Waitlist entries: until you are let in or ask us to remove you.
- When you delete your account, we delete its data within 30 days, except what the law makes us keep.
Your rights
You may ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Write to [email protected]; we answer within one month. To delete your account, see padock.dev/delete-account. You may also complain to the data protection authority where you live or work.
If you live in California or another US state with a privacy law, you have the rights that law gives, including to know, delete and correct your data. We don't sell or share personal data for advertising, and we don't use sensitive personal data to infer anything about you.
Security
Traffic is encrypted in transit. Traffic between your phone and your machines is also encrypted end to end (Noise, with X25519 and ChaCha20-Poly1305). Sign-in tokens are stored only as hashes. Access to our servers is limited to the people who run them.
Children
Padock is a tool for developers and is not meant for anyone under 16. We don't knowingly collect data from children.
Changes
We'll update this policy when what we collect or why changes, and tell you in the app or by email before a significant change takes effect. The date at the top shows the latest version.
Contact
Ihor Sorokin. Email: [email protected].