1. Summary
The details below distinguish data processed locally from information transmitted when you choose an online action such as downloading a dependency, pushing to a Git remote, or using an AI provider.
2. Data stored or processed on your device
NanoIDE may create, access, and store the following locally to provide its core features:
- source code, project files, imported files, build outputs, previews, and local project metadata;
- downloaded SDKs, compilers, build tools, dependencies, documentation, and related caches;
- editor preferences, app settings, logs, recent-project state, and analytics consent;
- Git configuration and credentials that you enter;
- AI provider API keys, custom provider URLs, prompts, chat history, and agent settings that you enter; and
- signing keys or certificates you create or import.
This local data is not collected by the NanoIDE developer merely because it is stored in the app. Android app storage protections apply. You can also deliberately expose project files through Android’s system document picker, import/open flow, share sheet, or other apps you select.
3. Optional performance and stability analytics
Data collected after consent
- App and device context: app version and build number, Android API level, device model and manufacturer, CPU architecture, and locale.
- Performance information: startup, indexing, build, completion, and analysis timing; memory measurements; cache-effectiveness counts; and aggregated latency statistics.
- Build diagnostics: success or failure, duration, step counts, memory measurements, and a fixed failure category such as compiler, resource, tool, or out-of-memory.
- Crash diagnostics: exception type, thread name, and scrubbed NanoIDE or platform stack frames. Exception messages and file paths are removed.
- Pseudonymous identifiers: a random installation UUID and a new random session ID for each app launch. These are not linked to a NanoIDE account, advertising ID, IMEI, or device serial number.
Data not included in analytics
Optional analytics does not include:
- source code, file contents, project names, file names, package names, or file-system paths;
- individual keystrokes, clipboard contents, contacts, precise location, microphone, camera, or photos;
- Git credentials, signing keys, AI API keys, prompts, or chat content; or
- advertising identifiers, Android account information, IMEI, or device serial numbers.
Purpose and processing
NanoIDE uses this data only to measure performance, identify reliability problems, prioritize fixes, and understand whether builds and developer tooling work across app versions and device types. Telemetry is sent over HTTPS to a Supabase-hosted database. Like most hosted network services, Supabase and its infrastructure providers may temporarily process network metadata such as your IP address and request time for security, delivery, and server logging under their own policies.
4. Online services you choose to use
The following transmissions occur only when you request or configure the relevant feature. The remote service receives the information needed to complete your request and handles it under its own privacy policy and terms.
| Feature | Data sent | Recipient |
|---|---|---|
| Dependencies, SDKs, runtimes, and tools | Requested package/tool names and versions, request headers, and normal network metadata. Your source code is not included. | The selected repository, CDN, or tool provider, such as Maven repositories, Google download services, GitHub, Adoptium, or a repository configured by you. |
| Git clone, fetch, pull, or push | Repository URL, credentials supplied for that remote, Git metadata, commits, and project files involved in the operation. | The Git hosting provider or server selected by you. |
| AI assistant | Your API key or authorization token, prompts, selected model, conversation messages, tool results, and any project/code context you choose or permit the agent to send. | Your configured provider, which may be Anthropic, OpenAI, Google Gemini, OpenRouter, or a custom/self-hosted compatible endpoint. |
| Agent web or HTTP tools | The URL, request content, and project information you authorize for that request. | The website or endpoint you approve. |
| Share, export, open, or install | The file or APK you select and the temporary Android content permission needed to deliver it. | Android system components and the destination app you choose. |
NanoIDE does not control the retention or secondary use practices of services you choose. Review the destination’s privacy policy before sending code, credentials, prompts, or other sensitive material. Security for a custom URL or Git server also depends on the protocol and server configuration you select.
6. Android permissions and access
| Permission or access | Why NanoIDE uses it |
|---|---|
| Internet | Downloads, Git operations, user-configured AI/HTTP features, and optional consented analytics. |
| Install unknown apps | Lets you install an APK you built. Android displays its own installation approval UI. |
| Notifications and foreground services | Keeps user-initiated builds or large SDK/tool downloads running and shows their ongoing status. |
| Wake lock and Wi-Fi state/lock | Prevents the device from suspending an active user-requested SDK or toolchain download when the screen turns off. |
| System file picker and document provider | Lets you select imports/exports and, when you choose, browse or edit NanoIDE project files from compatible file-management apps. |
NanoIDE does not request access to contacts, call logs, SMS, precise location, camera, or microphone for its normal operation.
7. Security
NanoIDE uses Android’s app sandbox for private local data and HTTPS for NanoIDE-operated telemetry and official download endpoints. Analytics database access is restricted to insertion from the app. Crash details are scrubbed before transmission. No method of storage or transmission is completely secure, and NanoIDE cannot guarantee the security of a third-party or custom endpoint selected by you.
You are responsible for protecting API keys, Git credentials, signing keys, exported projects, and files shared with other apps or remote services. Remove credentials you no longer use and avoid committing secrets to a Git repository.
8. Data retention and deletion
Local data
Projects, settings, credentials, SDKs, build outputs, and caches remain on your device until you delete them, clear NanoIDE’s storage, or uninstall the app. Copies that you export, share, install, back up, or push to a remote service are controlled by you and the recipient service.
Optional analytics
- Turning analytics off immediately stops future collection and deletes telemetry still waiting in NanoIDE’s local send queue.
- Raw telemetry received by the analytics service is retained for up to 30 days and then deleted.
- Anonymous aggregate totals, such as daily event counts without installation or session identifiers, may be retained longer for historical performance comparisons.
NanoIDE does not create user accounts. Because submitted telemetry is intentionally not linked to your name, email address, or an account, the developer generally cannot identify which previously submitted records belong to a particular person. Automatic deletion of raw telemetry within 30 days is therefore the primary deletion mechanism. You may contact us with a privacy inquiry at any time.
Third-party services
Data sent to an AI provider, Git host, custom endpoint, package repository, or another app is retained according to that recipient’s policy. Send deletion requests concerning that data directly to the relevant recipient.
9. Your choices
- Decline analytics on first launch or turn it off later in NanoIDE settings.
- Do not configure AI, Git, or custom endpoints, or remove their credentials, if you do not want to use those services.
- Cancel a system file picker or installation prompt and deny optional Android permissions.
- Delete projects, caches, credentials, and settings from the app or Android system settings.
- Contact us about access, correction, objection, or deletion rights that may apply where you live.
10. Children’s privacy
NanoIDE is a developer tool and is not directed to children under 13. The developer does not knowingly collect personal information from children. If you believe a child has provided personal information through NanoIDE-operated services, contact us so we can investigate and take appropriate action.
11. International processing
Supabase and user-selected third-party services may process information in countries other than your own. Their privacy policies describe the locations, safeguards, and legal bases they apply.
12. Changes to this policy
This policy may change when NanoIDE’s features, data practices, service providers, or legal obligations change. The effective date at the top will be updated. Material changes will be communicated through an appropriate in-app or release notice when required.
13. Contact
For privacy questions or requests, contact the NanoIDE developer at asibalamin.cse@gmail.com.