Tokens and Credentials
After reading this page you will be able to: distinguish the three credential types, know where they are stored and sent, and reduce exposure risk.
This page distinguishes three credential types and explains when they participate in network requests. Local storage does not mean a credential is never sent to its relevant service.
Three Credential Types
Section titled “Three Credential Types”| Type | Purpose | Settings entry |
|---|---|---|
| HuiAI sign-in token | Shared by automation, voice, remote access, and public tunnel features | Settings -> Required Setup |
| Model API key | Belongs to an individual model provider such as OpenAI, Anthropic, or DeepSeek | Settings -> Models |
| Chat platform credential | Belongs to a bot or integration for WeChat, Feishu, Telegram, Slack, Discord, and other channels | Settings -> Remote Connections -> Chat Platforms |
Where They Are Stored
Section titled “Where They Are Stored”- The HuiAI sign-in token is stored in
.aipc-up/config.jsonwithin the local application-data directory. The location of that directory depends on the operating system and installation method. - Model provider records and API keys are stored in provider storage in the local application database. Treat the database and its backups as sensitive; this page makes no claim that they are encrypted.
- Chat-platform credentials are stored by the relevant integration in local application or provider storage; the exact storage depends on the platform integration. Treat the related configuration and backups as sensitive.
- Project files remain in the filesystem directory you selected, not in the application database. Copy or back them up separately when migrating.
What Leaves the Device
Section titled “What Leaves the Device”| Action | Destination | Possible content |
|---|---|---|
| Send a message | Selected model provider | Prompt, context, and attachments needed for the request |
| Use HuiAI features | HuiAI services | Feature request, token authentication, and required account-resource information |
| Voice transcription | Speech recognition service | Audio produced by an active recording |
| Enable a public tunnel | HuiAI tunnel relay | Remote page and command interaction |
| Check for updates | Official update server, with GitHub Release as a fallback | Version-check request or installer package |
Release builds configured with Sentry may also send crash and diagnostic events. The source includes a delayed startup log report and a 24-hour throttle. Do not interpret “stored locally” as a promise that all runtime information always stays local.
Good Credential Habits
Section titled “Good Credential Habits”- Never share or screenshot tokens and API keys.
- Revoke and regenerate a credential immediately after a suspected leak.
- Sign out on a public computer and check whether the browser retained a remote session.