The short version
- Your projects, chats, Piye's notes and your keys stay on your computer.
- When Piye's AI works, the request to the AI model goes out: through Piye Cloud, or straight to the maker with your own key.
- Your account and billing are on piye.dev, with payments at Stripe.
- Piye sends no usage tracking from the app, and we do not use your projects to train public models. We do not sell personal data.
What stays on your computer
| What | Where |
|---|---|
| Your source code and files | Your project folder, and your Git remote if you use one |
| Piye's notes about a project (plan, Blueprint, chats, memory) | The project's .piye folder |
| API keys, sign-ins, deploy and store keys | Your computer's secure storage (Keychain on a Mac, keyring on Linux) |
| MCP connections | Piye's own settings folder on your computer |
| Settings | Piye's settings on your computer, and .piye for a project's own settings |
Chats are kept in the project's .piye/memory folder. Handoff never sends them, and Piye gives that folder its own .gitignore so it doesn't end up in your repository.
What is sent, and to whom
| What | Sent to | When |
|---|---|---|
| The AI request: your message, and the files, results and context the agent includes | Piye Cloud, then the model's maker (or a cloud that runs the maker's model) | When Piye's AI works on Piye credits |
| The same AI request | The maker directly (Anthropic, OpenAI, Google, xAI or Mistral) | When it runs on your own API key |
| Your account details, plan and usage counts | piye.dev | When you sign in and use credits |
| Payment details | Stripe, on its own pages | When you pay |
| A short record of the apps you open (name, folder, branch, deploy and domain details, Operations results) | piye.dev, for the console's Apps and Operations pages | While you are signed in |
| Your project's files (without secrets) | A private repository on your own GitHub | Only when you send a project with Handoff |
| Your app | Your web host, Apple, Google | Only when you publish |
Note
The agent decides what to include in an AI request: usually the files and results it needs for the task. In Code, Settings, AI, Context sets how much of the editor goes with each message (the message only, the active file, or the file and its problems), and Code Indexing under Privacy & Security sets whether a map of the project's folders goes with it.
Your .env files are read as names only: their values never go to the AI. Values that look like keys are masked in what the Code agent reads.
Settings that control privacy
All of these are in Settings (Code: Settings, Developer, Privacy & Security and Settings, AI; Visual: Settings, Privacy & about).
| Setting | What it does |
|---|---|
| Privacy Mode | Blocks Piye Cloud and your own API keys, so nothing about your code leaves the computer. Local models through Ollama keep working in Code. |
| Disable AI | Turns off every AI feature: the agent, Tab suggestions and the terminal's AI. |
| Data Retention / Keep my chats for | How long chats are kept on this computer: 30 days, 90 days (the default), 1 year or forever. |
| Code Indexing | Whether the agent gets a map of the project's folders with each message. Off sends less. |
| Telemetry | Reserved. Piye sends no usage data today; the setting is kept so it's honoured if that ever changes. |
No tracking in the app
The desktop app has no usage tracker and no crash reporter. Piye also turns off the usage reporting of the tools it runs for you (Next.js, Expo, .NET and Go).
On piye.dev, analytics cookies are only used with your consent. Manage them at Cookie Preferences.
AI and training
We do not use your projects to train public models. When a request reaches an AI company, that company's own terms for API use apply.
Your rights
You can ask for a copy of your data, or for it to be deleted, at privacy@piye.dev. The full details, including the legal basis for each use, are in the Privacy Policy.