Privacy
Personal Dev Team (PDT) runs on your own machine. There are no PDT servers your work goes through.
What stays on your machine
- Your tickets, documents, conversations and settings are kept in PDT's data folder on the computer it runs on.
- Sign-ins and secrets (tokens for GitHub, Google and other services) are kept in that computer's keychain.
- Nothing is sent to PDT's developers: no analytics, no telemetry, no copies of your data.
What PDT sends, and where
PDT talks to the services you connect it to, from your machine, as you: GitHub for your repositories, the coding agents you run, and the plugins you turn on. It checks GitHub for new releases.
- Signing in with Google asks only for the
drive.filepermission, with your email address to name the account. PDT can then open only the Docs and Sheets it makes and those you pick in Google's file picker, never the rest of your Drive. - Your Google sign-in is kept in your keychain and used only from your machine, to read and change those files when you or the agents you allowed ask it to.
- Agents use Google only when you allow them, for each account, and you can take that away in Settings → Plugins → Google at any time. What an agent reads from a file goes to that agent's own service (Claude, Codex or the agent you run), as anything else it works on does.
- Google's sign-in comes back through
pdt.dev/oauth/google, a page that only sends your browser back to the PDT you started from. It keeps nothing and sends nothing anywhere else.
Taking access back
Sign out of an account in Settings → Plugins → Google, or delete its connection: PDT forgets the sign-in. To take PDT's access back from Google's side, open your Google Account → Security → Third-party apps with account access, pick Personal Dev Team and remove its access.
Contact
Questions about privacy or support: support@pdt.dev.