π Pi Dev

Legal

Privacy Policy

Last updated: July 9, 2026

This Privacy Policy describes how Pi Dev (“we,” “us,” or “our”) handles information when you use the Pi Dev iOS application (the “App”) and related documentation on this website. Pi Dev is a coding-agent client that connects to a Pi backend server that you (or your organization) operate.

We designed Pi Dev around a simple idea: your prompts, code, and sessions stay on the infrastructure you configure. We do not operate a mandatory cloud account service for the App, and we do not sell personal information.

1. Summary

  • No Pi Dev account required. You connect the App to a server URL and an authentication token that you control.
  • Conversation content is not sent to a Pi Dev cloud. Messages, files, and repository URLs go to the Pi server you configure.
  • Local settings only on device. The App stores your server URL and auth token on the device for convenience.
  • No advertising or analytics SDKs are bundled in the App for tracking users across apps or websites.
  • Third-party AI providers may process prompts if the operator of your Pi server configures LLM API keys (for example OpenAI, Anthropic, Google, or others).

2. Who this policy covers

This policy applies to:

  • The Pi Dev iOS app
  • This public website (including this Privacy Policy page), when hosted by us

It does not control how a third party runs their own Pi server, network, or LLM provider account. If you connect the App to a server operated by someone else (for example an employer), their policies may also apply to data processed on that server.

3. Information we collect and process

3.1 Information stored on your device

The App may store the following locally (via system preferences storage):

  • Server URL - the address of the Pi backend you choose to use
  • Authentication token - the API token required by that server

Chat UI state (drafts, in-progress messages, selected model, attachments before send) is held in memory while you use the App and is not used to build marketing profiles.

3.2 Information you provide while using the App

When you use Pi Dev, content you create or attach is sent to your configured Pi server, not to a separate Pi Dev account backend. That content may include:

  • Chat messages and prompts
  • Pasted text
  • Contents of files you choose to attach (for example source code or plain text)
  • Git repository URLs or paths you choose to include so the server can work in that project context
  • Preferences such as model selection and thinking level, when the server supports them

Do not attach secrets, credentials, or personal data you are not willing to send to the server and any LLM providers that server uses.

3.3 Optional GitHub public API lookups

If you use the repository picker to search public GitHub repositories by username, the App requests public repository metadata from api.github.com (for example repository name, description, and clone URL). That request is made from your device to GitHub. We do not use this to create a Pi Dev user profile, and the App does not require a GitHub login for public repo search.

GitHub’s processing of those requests is governed by GitHub’s privacy policy.

3.4 This website

This site primarily serves static informational pages (such as this policy). We do not require you to create an account to read it. Standard web server or hosting logs (for example IP address, user agent, and requested URL) may be generated by the host that serves the site, for security and reliability. We do not use third-party advertising cookies on this policy page.

3.5 Information we do not collect

As implemented today, Pi Dev does not:

  • Create or require a Pi Dev user account or email signup
  • Include third-party advertising, cross-app tracking, or marketing analytics SDKs
  • Access your contacts, precise location, microphone, camera, or photo library as part of core product features
  • Sell your personal information

4. How the Pi server handles data

Pi Dev talks to a Pi backend over HTTPS/HTTP using a bearer (or equivalent) API token. Depending on how that server is configured, it may:

  • Authenticate every request with the shared API token
  • Persist chat sessions on disk (unless session persistence is disabled by the operator)
  • Stream agent events (assistant text, tool use, and related session updates) back to the App
  • Clone git repositories you supply into a working directory on the server machine
  • Run developer tools on the server (for example shell commands in the agent workspace) as part of the coding agent
  • Call third-party LLM APIs using API keys stored on the server (for example in the operator’s agent auth configuration), so prompt and context data may leave the server and go to those providers

Operators can typically configure the working directory, session storage location, default model/provider, and whether sessions are kept. If you self-host, you control retention and access. If someone else hosts the server, ask them how long sessions are kept and which model providers they use.

5. How information is used

Information processed through Pi Dev is used to:

  • Connect the App to your chosen server
  • Provide coding-agent chat, tools, and session history
  • Clone or open repositories and apply model/thinking settings you select
  • Operate, secure, and debug software you or your operator run

We do not use App conversation content for advertising. We do not sell personal information.

6. Sharing and third parties

Data may be shared only as needed to operate the product:

  • Your Pi server operator - receives the content and settings you send from the App
  • LLM and model providers - if configured on the server, prompts and related context may be sent to those providers under their terms and privacy policies
  • GitHub - if you use public repository search, GitHub receives the public API request from your device
  • Infrastructure providers - if we host this website, standard hosting and network providers may process technical logs
  • Legal requirements - we may disclose information if required by law, regulation, or valid legal process

7. Retention

  • On device: Server URL and auth token remain until you clear App data, reinstall the App, or change/remove those settings.
  • On the Pi server: Session files and cloned repositories are retained according to the server operator’s configuration and practices (including optional settings that disable session persistence).
  • LLM providers: Retention of prompts and outputs is governed by each provider’s policy and the operator’s agreement with them.

8. Security

The App sends the authentication token on API requests so only clients that know the token can use the server. You should:

  • Use a strong, unique API token
  • Prefer HTTPS endpoints and avoid sharing tokens in screenshots or chat
  • Treat the Pi server like a development machine: it may store code, sessions, and credentials for model providers
  • Limit who can reach the server on the network and who knows the token

No method of transmission or storage is completely secure. Use Pi Dev only with servers and networks you trust.

9. Children’s privacy

Pi Dev is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has provided personal information through the App, contact us and we will take appropriate steps.

10. Your choices and rights

Depending on your situation, you can:

  • Disconnect the App by clearing the saved server URL and token (or deleting the App)
  • Stop sending content by not submitting prompts or attachments
  • Ask the operator of your Pi server to delete session files or disable persistence
  • Review and exercise rights under applicable law (for example access, deletion, or correction) with the party that controls the relevant data - often the server operator for session content

If you contact us about a privacy request, we will help identify whether the data is controlled by us (for example website hosting) or by your server operator.

11. International processing

If you use a server or model provider in another country, your information may be processed in that country. Those jurisdictions may have different data-protection laws than your own.

12. Apple App Store and device permissions

Pi Dev uses system capabilities only as needed for product features, such as network access to your server and optional file import for context. We do not use App Tracking Transparency for cross-app advertising, because we do not track you across apps and websites for ads.

Apple may independently collect certain analytics related to App Store distribution according to your device settings and Apple’s policies. That collection is controlled by Apple, not by Pi Dev.

13. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date at the top of this page. Continued use of the App or website after changes become effective constitutes acceptance of the updated policy, except where applicable law requires additional notice or consent.

14. Contact

For privacy questions about Pi Dev or this policy, contact the developer through the support channel listed on the App Store product page for Pi Dev, or the contact method provided with your distribution of the App.

If your question concerns data stored on a Pi server you do not operate, please also contact that server’s operator.