← Dolaima← Docs indexPrivacy Policy原文中文

Privacy Policy

This page explains what data Dolaima touches, where that data goes, what is stored on your phone, and how to delete it.

In one sentence: Dolaima runs no server of its own. It collects no data, sends no analytics, and shows no ads. Your code and your conversations go only to the model provider you configure.

_Last updated: 2026-09-29_

1. What is sent to your model provider

Dolaima is an AI coding assistant: its whole job is handing context to a large language model. The following is sent over HTTPS to the provider you entered in Settings (both the base URL and the API key are yours -- it can be DeepSeek, OpenAI, Claude, Gemini, OpenRouter, a server you run yourself, or a local model on your phone):

WhatNotes
Your promptsThe text you type on the Chat page
Conversation historyThe context accumulated in this session, including compacted summaries
File contents it readThe body of files the agent read with its tools
Command outputstdout/stderr from commands it ran
Images / audioOnly when you use photo input or speech-to-text
System promptGenerated by the app (includes project structure and similar)

WARNING: it decides which files to read. If your workspace contains keys, certificates or .env files, the model may read them and send them to the provider. Keep sensitive files out of the project, or switch to Plan mode (read-only) first.

Who receives it is entirely up to your configuration. We do not relay, proxy or re-upload anything, and we cannot see this content -- the API key and the provider account are yours.

2. Other network requests

Apart from your model provider, these features reach the network, and only when you (or the agent) actually use them:

FeatureGoes toSends
Web searchA search engineYour search keywords
Fetch page / downloadA URL you or the agent specifyAn HTTP request
Speech-to-textThe Whisper-compatible endpoint you configuredThe audio to transcribe
MCP serversServers you configured yourselfDetermined by that protocol

3. What is stored on your phone

All of it stays on the device; none of it is uploaded to us (we have no server to upload to):

WhatWhere
API keysapi_keys.json in the app's private directory (plain text, not encrypted)
Settings, connections, model choiceConfig files in the app's private directory
Sessions and memorysessions/, memory/ in the app's private directory
Your code and projectsThe workspace directory (see below)

Where the workspace lives: by default inside the app's private directory. On Android, if you grant "All files access", the workspace and config move to a waycoder/ directory in external storage, so other file managers can see the code you write. On iOS it always stays inside the app's private directory.

WARNING: the key is plain text. Anyone who can read that storage on this device can read it. Do not keep production keys on a shared device.

4. Phone permissions we request

PermissionWhen we askWhat it is for
CameraWhen you tap "Take photo"Photograph something for the AI to look at
PhotosWhen you tap "Pick image"Choose an existing image for the AI to look at
MicrophoneWhen you tap "Voice input"Turn your speech into text
All files access (Android only)When you enable it in system settingsPut the workspace in external storage so other apps can open your code

We ask only when the feature is used, and declining still leaves everything else working -- only that one feature becomes unavailable.

5. No telemetry

Dolaima contains no analytics, no crash reporting and no advertising SDK. The only outbound check is the version update query you trigger yourself; it reads a version number and sends nothing about your device.

6. Reducing what leaves the device, and deleting it

7. Children and age

Dolaima is intended for developers with a basic programming background. It is not directed to children under 13, and we do not knowingly collect information from them. The store age rating is 13+.

If you are under 18, please use it with a guardian's consent -- and make sure you have permission before entering a model provider's API key, since the charges from that key are billed to the account holder.

8. Contact

Questions, bug reports and privacy concerns all go to the repository issue tracker: <https://github.com/alecksty/waycoder/issues>

You can also email <alecksty@163.com>.

This policy is also published at: <https://github.com/alecksty/waycoder/blob/master/docs/PRIVACY.md>