Privacy Policy

Last updated: 14 June 2026

VeePy is a code editor and on-device Python IDE for iPhone and iPad. This policy explains exactly what data VeePy does and does not handle. The short version: VeePy has no servers, no accounts, and no tracking. Your code, your keys, and your activity stay on your device unless you explicitly send them somewhere.

1. We do not collect personal data

VeePy contains no analytics, no crash reporters, no advertising SDKs, and no third-party telemetry. We do not run any backend that receives your data. We do not know which files you open, how often you run code, what you type, or whether you use the app at all. There are no user accounts and no sign-up.

Apple’s standard, OS-level crash reports may be sent to Apple if you opted in during iOS setup. Those go to Apple, never to us, and are governed by Apple’s privacy policy — not this one.

2. Your files and code

All files you create or edit, and all Python code you run, stay on your device. Python executes locally inside the app; nothing is uploaded to run it. The only times data leaves your device are the user-initiated network actions listed in Section 3 — and each one is started by you, by tapping a button. There is no background sync and no background fetch.

3. Network features (all user-initiated)

VeePy never talks to the network on its own. Network activity happens only when you explicitly trigger one of these features:

• AI assistant (optional, bring-your-own-key). If you configure an AI provider, the prompt and the code context you choose to share are sent directly to the AI provider you selected (for example OpenAI, Anthropic, or OpenRouter). VeePy has no AI server in the middle — requests go straight from your device to that provider over HTTPS. Before any data is sent to a given provider for the first time, VeePy shows a consent screen that names the exact provider and states that your data will leave the device. Nothing is sent until you approve. Consent is tracked per provider and can be withdrawn. What the provider does with the data is governed by that provider’s own privacy policy. The AI assistant is explanatory only; it cannot run code for you.
• Git. Fetch, pull, and push contact only the remote repository you configured, when you tap the corresponding button.
• SSH / SFTP (optional). Connecting to a server, or pulling/pushing a remote file, contacts only the host you entered, when you initiate it.
• iCloud Drive folders (optional, Pro). If you link an iCloud folder, files are pulled or pushed only when you tap Pull or Push. They sync only through your own private iCloud account (Apple’s infrastructure), never through us. There is no automatic background sync.
• In-app purchases. Purchase and restore go through Apple’s StoreKit. We never see your payment details; Apple handles the transaction.

4. Credentials and API keys

API keys, SSH/SFTP credentials, and SSH private keys you enter are stored only in the device Keychain (Apple’s encrypted credential store). They are never transmitted to us — we have no server to transmit them to — and are sent only to the corresponding service (your AI provider, your git/SSH/SFTP host) when you use that feature.

5. Children

VeePy does not knowingly collect any data from anyone, including children. The App Store age rating is 13+.

6. Third-party services

When you choose to use them, the following independent services receive only the data you direct to them, under their own privacy policies:

• AI providers you configure (e.g. OpenAI, Anthropic, OpenRouter, or any custom OpenAI-compatible endpoint you specify).
• Git/SSH/SFTP hosts you connect to.
• Apple (App Store purchases, iCloud Drive, optional crash reports).

VeePy bundles open-source components (editor, syntax engine, Python runtime, SSH library). They run entirely on-device and do not transmit your data.

7. Changes to this policy

If this policy changes, the updated version will be posted at this page with a new “last updated” date.

8. Contact

Questions about privacy? Email burbekristina222+veepy@gmail.com.