← Free, open source, non-profit← 免费、开源、非营利
Privacy隐私政策
This page is what the nanoMuse apps (the phone, the web and desktop apps, the dsh plugin) and nanoMuse Cloud do with your data. It is short because they do little with it. Where it matters, the one thing you decide is a switch: Settings → Data controls.这一页讲 nanoMuse 的各个应用(手机 App、网页版和桌面版、dsh 插件)以及 nanoMuse Cloud 怎么处理你的数据。它很短,因为它们对数据做的事很少。在要紧的地方,由你决定的只有一个开关:设置 → 数据控制。
Everything stays on your device一切都留在你的设备上 {#everything-stays-on-your-device}
The agent runs inside the app: on the phone, in a Linux root file system in the app's private storage; on a computer, in the runtime you installed. Conversations, memory, files the agent writes, scheduled tasks, skills and settings are stored there and, where you mount them, in folders you chose. There is no analytics, no crash reporting to us and no telemetry of any kind. The only nanoMuse server is the optional relay described below, and the apps work fully without it.智能体在 App 里面运行:在手机上,是 App 私有存储里的一个 Linux 根文件系统;在电脑上,是你装的那个运行时。对话、记忆、智能体写的文件、定时任务、技能和设置都存在那里,以及你挂载的那些自己选的文件夹里。没有任何分析统计、没有向我们发送的崩溃报告、没有任何形式的遥测。nanoMuse 唯一的服务器是下面说的那个可选的中继,没有它各个 App 也能完整使用。
What leaves the device哪些会离开设备 {#what-leaves-the-device}
- Your model provider. Messages, attached images and tool results are sent to the model endpoint you configured (Alibaba Cloud Bailian, DeepSeek, OpenAI, OpenRouter, your own vLLM or Ollama, …), under that provider's terms, with the API key you entered. The key is stored on your device only.你的模型服务商。 消息、附带的图片和工具结果会发给你配置的模型端点(阿里云百炼、DeepSeek、OpenAI、OpenRouter、你自己的 vLLM 或 Ollama……),受那家服务商的条款约束,用的是你输入的 API key。key 只存在你的设备上。
- nanoMuse Cloud, if you signed in. Sign in (free) on the first screen (or Settings → nanoMuse Cloud) signs you up with a phone number or an e-mail address and a code, and the app then uses our relay as a model provider: free, ¥10 of model use per account (community members: no limit; each new person who signs up with your invite code and makes a first request adds ¥5 to your allowance and ¥5 to theirs), paid by the developer; nanoMuse is a non-profit community project and never charges. The relay forwards chat, attached images and screen-operation requests to the operator's
Qwen/Qwen3.6-27B-FP8deployment on Tencent Cloud. It does not offer hosted image or video generation; those requests go only to a provider you configure with your own key. What it keeps about the account: a salted hash of your address, the address itself encrypted so the person running the relay can see whose account it is (the database file alone shows nothing), a masked hint such ass***@example.com, the hash of the key issued to this device, the kind, model and token count of each request (and, since relay 0.28, how each chat request went: how long it waited for a slot at the model, the time to the first token and to the end, how it ended, how many messages and pictures it carried, the names of the tools the app offered and the reply called, whether it was a screen-operation turn, and the client platform; never a word of the conversation; these rows are kept 90 days and the operator's pages read them in aggregate), your invite code with the ids of accounts that used it, and, so your devices wear the same one, the agent's name and look (which face; for one drawn in the avatar studio, its five small pictures and, from 1.0.7, the short clips a device made of it, so the others need not render their own). With each sign-in, request, timeline event and device it also records the network address the request came from and the client software (theUser-Agent: the Android app and its version, the runtime on Windows, macOS or Linux, a browser), and the account keeps its first and last address and when it was last seen; the person running the relay sees these on the operator's page, per account and per address, to tell one person on two accounts from two people on one address and to see a problem's shape. Of the conversations themselves it keeps, since relay 0.29, the record: every chat turn it answered, in full: the request as it sent it to the model (every message: the system prompt with your memory, SOUL and instructions, what you wrote, what tools returned, the screenshots and pictures) and the answer as the model gave it. It is kept as your account's own data, so that your devices can show the same history, screenshots included, and the person running the relay can see a problem whole. Pictures are stored once each as files named by their hash; the turn says which device and conversation they belong to when the app names them (1.0.7 on). Your devices read the record back through the relay; the operator can read it too; nobody else can, and a file opens only for the account whose turn it belongs to. It stays until you delete it (one tap under Settings → Data controls removes the whole record with the training turns described next) or delete the account; a relay you run yourself can set a retention period (RECORD_KEEP_DAYS) and keeps no record at all withRECORD_TURNS=0. The pictures have a ceiling in all (MEDIA_MAX_GB): past it the least recently used are removed first and the words stay. From 1.0.7 an app that ran a turn on a key of your own sends that turn up as well, so the record is whole wherever the model was. From relay 0.31 the apps also say, with each turn, where it came from: whether a person started it or a scheduled task, the feed's routine, a goal's check or another of your devices; which turn of the conversation it is and which model call within the turn; which screen-operation task and step it belongs to; and the relay notes one word for the script of what you wrote (zh,latin,ja, …), never the words. And the apps report, as short codes and numbers tied to the turn and never as text, what happened around it: what the Sentinel decided about a tool call and at which risk level, how an approval went, why you stopped a reply when you chose to say, a thumb up or down you gave an answer, how a screen-operation step went. Those reports are deleted with the turns and with the account. Two switches, described next, decide what else is made of the conversations. It does not receive your location: the apps never send it. Next to an address, the operator's page shows the country, province and city that address belongs to, read from an offline copy of ip2region's public database on the relay's own disk when the page is drawn; no third party is asked and the place is not stored. Signing out revokes the key; deleting the account removes all of it, addresses included. The relay's source is in the repository undercloud/, and docs/cloud.md says how to run your own. Nothing about the relay applies when you use your own key.nanoMuse Cloud,如果你登录了。 第一屏的「登录,免费开始」(或 设置 → nanoMuse Cloud)用手机号或邮箱加一个验证码给你注册,之后 App 把我们的中继当成一个模型服务商来用:免费,每个账号 ¥10 的模型用量(社区成员不限;每有一个新人用你的邀请码注册并发出第一次请求,你的额度加 ¥5,对方也加 ¥5),钱由开发者出;nanoMuse 是非营利的社区项目,从不收费。中继把对话、附带图片和操作屏幕请求转发给运营者部署在腾讯云的Qwen/Qwen3.6-27B-FP8。它不提供托管生图或生视频;这两类请求只会发给你用自己的 key 配置的服务商。关于账号,它保存这些:你地址的加盐哈希;地址本身的加密副本,让运行中继的人能看出账号是谁的(单看数据库文件什么也看不出来);一个打码的提示,比如s***@example.com;发给这台设备的 key 的哈希;每次请求的类型、模型和 token 数(中继 0.28 起还有每次聊天请求的经过:在模型那里等位子等了多久、到第一个 token 和到结束各用了多久、怎么结束的、带了几条消息和几张图、App 提供了哪些工具和回答调用了哪些(只有名字)、是不是一轮屏幕操作、客户端平台;从来没有对话里的一个字;这些行保留 90 天,运营者页面只看它们的汇总);你的邀请码以及用过它的账号 id;还有,为了让你的各台设备显示同一个,智能体的名字和形象(用的是哪一张;如果是形象工作室里画的,还有它的五张小图,以及 1.0.7 起某台设备为它做的几段短视频,其他设备就不用各自再渲染)。每次登录、请求、时间线事件和设备,它还会记下请求来自的网络地址和客户端软件(User-Agent:Android App 及其版本、Windows、macOS 或 Linux 上的运行时、某个浏览器),账号则保留第一个和最后一个地址,以及最后一次出现的时间;运行中继的人在运营者页面上按账号、按地址看到这些,用来分辨「一个人开两个账号」和「两个人共用一个地址」,以及看清一个问题的轮廓。关于对话本身,中继 0.29 起保存记录:它答过的每一轮聊天,完整保留:它发给模型的请求原样(每条消息:带着你的记忆、SOUL 和指令的系统提示词、你写的、工具返回的、截图和图片)和模型给出的回答原样。这是你账号自己的数据,好让你的各台设备显示同一份带截图的历史,也让运行中继的人能看清一个问题的全貌。图片按哈希命名,每张只存一份文件;App 报了设备和对话时(1.0.7 起),这一轮会记下它属于哪台设备、哪个对话。你的设备通过中继把记录读回来;运营者也能读;其他任何人都不能,一个文件只对它所属那一轮的账号打开。它会一直保留到你删掉为止(设置 → 数据控制 里点一下,整份记录连同下面说的训练轮次一起删除),或者删除账号;自己部署的中继可以设保留期(RECORD_KEEP_DAYS),设RECORD_TURNS=0则完全不保留。图片总量有上限(MEDIA_MAX_GB):超过后最久没用到的先删,文字还在。1.0.7 起,用你自己的 key 跑的轮次 App 也会传上来,这样不论模型在哪,记录都是完整的。中继 0.31 起,App 随每一轮还会说明它的来历:是人发起的,还是定时任务、动态日报、目标检查或你的另一台设备发起的;它是对话里的第几轮、本轮里的第几次模型调用;属于哪个屏幕操作任务的第几步;中继另记一个词说明你写的那句话用的是哪种文字(zh、latin、ja……),从不记原文。App 还会以挂在轮次上的短代号和数字(从不是文字)回报这一轮前后发生的事:Sentinel 对某次工具调用判了什么、风险档是哪一级,一次审批怎么走的,你停掉一条回复时愿意说的原因,你给某条回答点的赞或踩,屏幕操作的某一步结果如何。这些回报随轮次一起删,随账号一起删。对话另外还会怎样,由两个开关决定,下面接着讲。它收不到你的位置:各个 App 从不发送位置。地址旁边,运营者页面会显示这个地址属于哪个国家、省、市:在画页面的那一刻,从中继自己磁盘上一份离线的 ip2region 公开数据库里读出来,不问任何第三方,地点也不保存。退出登录会吊销 key;删除账号会删掉上述全部,地址也包括在内。中继的源码在仓库的cloud/目录下,docs/cloud.md 讲怎么自己部署。用自己的 key 时,关于中继的这一切都不适用。 - The project site (nanomuse.cn), if you visit it. Its web server keeps an access log for seven days and then deletes it; a script turns it into counts per day: pages viewed, how many visitors, downloads per file, which sites linked here. A visitor is counted once a day through a hash of the address and browser string under a random salt made for that day and discarded after two; no address is stored beyond the week the raw log lives, nothing is shared with anyone, there are no cookies and no third-party analytics. The relay's own operator page shows counts of sign-ins and accounts per day, from the same records described above; nothing more is collected for it.项目网站(nanomuse.cn),如果你访问它。 它的 web 服务器保留七天访问日志,然后删除;一个脚本把日志变成按天的计数:看了哪些页面、多少访客、每个文件的下载次数、哪些网站链接过来。访客每天只计一次,用的是地址加浏览器字符串的哈希,盐是当天随机生成的、两天后丢弃;原始日志存活的那一周之外不保存任何地址,不和任何人共享,没有 cookie,也没有第三方统计。中继自己的运营者页面显示每天的登录数和账号数,来自上面说过的那些记录;没有为此多收集任何东西。
- The showcase (demo.nanomuse.dev), if you try it. The page sets no cookie and its web server keeps no access log. Starting a Muse there means signing in to nanoMuse Cloud first, through the showcase's gateway: the relay records that sign-in as described above, with your address, which the gateway passes on. The gateway's own database then keeps, per account: the account's id, the relay's masked hint, whether it was a phone number or an e-mail address, how many times you signed in, and the address and browser string of your first and your latest sign-in or demo; and one row per demo started: when, from which address, with which browser, whether you brought your own key, how it ended, and how many model calls, tokens, pictures and clips it used. Your browser holds a sign-in ticket good for thirty days; the gateway stores its hash. What you say to the Muse goes through the gateway to the model the operator configured (Alibaba Cloud Model Studio on the public showcase); the gateway counts calls and tokens and keeps no message content, and a key of your own lives in its memory for that session only and is never written down. The Muse runs in a container made for your session and removed with it, and everything in it, after thirty minutes or ten quiet ones; your browser's time zone name travels with the start so the Muse's clock is yours, and is not kept. The gateway's log names sessions by id and visitors by the masked hint, never by address, and Docker keeps at most 100 MB of it. The account and demo rows stay until the operator deletes them; there is no automatic deletion. The person running the relay sees them on its operator page, beside the account. The source is under
demo/showcase/in the repository, and its README says what each limit is.在线体验(demo.nanomuse.dev),如果你试了它。 页面不设 cookie,它的 web 服务器也不保留访问日志。在那里启动一个 Muse 要先通过体验网关登录 nanoMuse Cloud:中继按上面说的方式记下这次登录,包括你的地址,由网关转交。随后网关自己的数据库按账号保存:账号 id、中继给的打码提示、用的是手机号还是邮箱、登录过几次,以及你第一次和最近一次登录或体验的地址和浏览器字符串;每启动一次体验再记一行:什么时候、从哪个地址、用什么浏览器、有没有带自己的 key、怎么结束的,以及用了多少次模型调用、多少 token、几张图片、几段短片。你的浏览器里有一张三十天有效的登录凭据,网关存的是它的哈希。你对 Muse 说的话经网关发给运营者配置的模型(公开的体验站上是阿里云百炼);网关只计次数和 token,不保留任何消息内容;你自己的 key 只在那一场体验期间留在网关内存里,从不写入磁盘。Muse 跑在为你这一场体验创建的容器里,三十分钟后或十分钟没有动静后连同里面的一切一起删除;浏览器的时区名随启动一起发出,让 Muse 的时钟是你的时间,不保存。网关的日志用 id 称呼会话、用打码提示称呼访客,从不写地址,Docker 最多保留 100 MB。账号和体验的记录会一直保留到运营者删除为止,没有自动删除。运行中继的人在它的运营者页面上、账号旁边看到这些记录。源码在仓库的demo/showcase/下,它的 README 写明了每一项限制。 - Data controls: “Help improve nanoMuse's AI models”. Settings → Data controls on every app holds one switch. While it is on, the text of your chats with the nanoMuse Cloud models may train the community's own open model: what you wrote, what the model answered, and the tool calls it chose, together with the model, the token counts, and the app's platform and language from the request headers. The training set does not take the system prompt (your memory, SOUL and instructions), what tools returned, pictures, audio or clips (those are replaced by a marker), and its turns are tied to your account id only; exports for training carry no account id, address or hint. Beside each kept turn the relay stores its shape (since relay 0.28): the number of messages, character counts, tool calls and pictures, whether the prompt was trivially short, and a hash of what you wrote, so repeats can be counted without reading the turns; deleting the turns deletes the shapes. From relay 0.31 a turn the app ran on a key of your own and sent up to the record joins the training set in the same way while the switch is on, and each kept turn says where it came from (a person or a routine, which turn and step, on the relay's model or your own key), so the thumbs and stop reasons above can be matched to it. Exports for training name your account by a pseudonym (a keyed hash the relay alone can make, which recovers nothing without its secret); when you delete your kept data or your account, the relay writes that pseudonym and the time to a deletions ledger and nothing else about you stays, so a set built from an earlier export drops your turns in its next build. The switch decides what joins the training set, not what the record above holds. On
cloud.nanomuse.cnthe switch is on for accounts created from relay 0.9 on; accounts that existed before keep whatever they had chosen. The switch says so right next to it, and a relay you run yourself chooses withIMPROVE_DEFAULT. Turn it off at any time (nothing more joins the set from then on), delete everything kept so far, the training turns and the record, with one tap on the same page, and deleting the account deletes it too. Nothing about the allowance depends on this switch. Apps older than 1.0.7 describe the switch in the earlier words, with the record not yet mentioned; this page is current.数据控制:「帮助改进 nanoMuse 的 AI 模型」。 每个 App 的 设置 → 数据控制 里有一个开关。开着时,你和 nanoMuse Cloud 模型的聊天文本可以用来训练社区自己的开放模型:你写的、模型答的、它选择的工具调用,连同模型、token 数,以及请求头里 App 的平台和语言。训练集不取系统提示词(你的记忆、SOUL 和指令)、工具返回的内容、图片、音频或短视频(这些都换成一个标记),其中的轮次只和你的账号 id 关联;用于训练的导出不带账号 id、地址或提示。每条留下的轮次旁边,中继还存一行它的形状(中继 0.28 起):消息数、字符数、工具调用数、图片数、提示是不是短得没有内容,以及你所写内容的一个哈希,用来不读轮次也能数出重复;删掉轮次,形状也一起删。中继 0.31 起,开关开着时,App 用你自己的 key 跑完并传到记录里的轮次也以同样方式进入训练集,每条留下的轮次都记着来历(人发起的还是例行任务、第几轮第几步、中继的模型还是你自己的 key),这样上面说的赞踩和停止原因能对得上。训练用的导出以化名指代你的账号(只有中继能算出的带密钥哈希,没有密钥反推不出任何东西);你删掉留存的数据或注销账号时,中继把这个化名和时间写进一份删除台账,关于你的其他一切都不留,这样用早先导出训练的数据集会在下一版里剔除你的轮次。这个开关决定的是什么进入训练集,不是上面的记录保存什么。在cloud.nanomuse.cn上,中继 0.9 之后创建的账号这个开关默认开着;之前就有的账号保持它们当初的选择。 开关旁边就写着这一点,自己部署的中继用IMPROVE_DEFAULT来选。随时可以关掉(从那之后不再有新的进入训练集),在同一页上点一下就能删掉此前保留的全部(训练轮次和记录一起),删除账号也会一并删掉。额度和这个开关没有任何关系。1.0.7 之前的 App 还在用早先的话描述这个开关,没有提到记录;以本页为准。 - Synced conversations: on by default when you are signed in (relay 0.19 on). The text of your conversations is stored on nanoMuse Cloud so every device of your account shows the same chats. Files and images are not uploaded by this switch (the record above holds the pictures of each turn). Settings → Data controls turns it off and deletes what is stored; deleting a chat on one device deletes it on all of them. The text is stored as it is, so, as with the record, your devices and the person running the relay can read it and nobody else; the operator's page shows counts, not text. (What is stored, exactly: each conversation's title and which device started it, each message's role, text, time and device, and the names and sizes of attached files; never the files, never a picture, never what a tool returned. Chats addressed to another device, or run on this one for another, are not synced. The relay keeps at most 20 000 messages per account and cuts a message at 16 KB. docs/cloud.md has the details.) Since 0.1.38 only the main conversation is synced by default: side chats stay on the device that made them, and other devices' side chats do not arrive, unless you turn on Also sync side chats on that device. While one of your devices is answering, the others are told so (kwai is working…); that note goes through the relay's memory, is never stored, and is forgotten after ten minutes.同步的对话:登录后默认开启(中继 0.19 起)。 你对话的文本存在 nanoMuse Cloud 上,让你账号下的每台设备显示同样的聊天。这个开关不上传文件和图片(每一轮的图片在上面的记录里)。设置 → 数据控制 可以关掉它并删除已存的内容;在一台设备上删除一个聊天,所有设备上都会删除。文本按原样保存,所以和记录一样,能读它的只有你的设备和运行中继的人;运营页面显示的是数量,不是文本。(确切说,存的是:每个对话的标题和由哪台设备发起,每条消息的角色、文本、时间和设备,以及附件的名字和大小;从不存文件,从不存图片,从不存工具返回的内容。发给另一台设备的聊天,或者这台设备替别的设备跑的聊天,不同步。中继每个账号最多保留 20 000 条消息,单条消息在 16 KB 处截断。细节在 docs/cloud.md。) 0.1.38 起默认只同步主要聊天:旁聊留在创建它的设备上,其他设备的旁聊也不会过来,除非你在那台设备上打开「同时同步旁聊」。你的一台设备正在回答时,其他设备会收到提示(「kwai 正在处理…」);这条提示只经过中继的内存,从不保存,十分钟后就忘掉。
- Your devices, when they talk to each other (relay 0.9 on). With Devices on, each signed-in app keeps one connection to the relay, so your phone can ask your computer to run something and the other way round. The relay keeps a row per device: the id the app chose for itself, the name you gave it, whether it is a phone or a computer, its operating system, the app's version, the list of actions it offers, when it was first and last seen, and the address it connected from; your other devices see the same list (name, kind, version, online or not, address) under Settings → Devices. From 1.0.7 the row also carries two ids for what answers that device's chats:
cloudwhen the account's models do, otherwise the provider and model you configured (openrouter,bailian, a model id), never the key, the base URL or any other setting; the operator's page reads them to see which providers people configure for themselves. What one device asks another (a command, a file, a screen to operate, a provider request your phone sends through your computer) passes through the relay inside your account and is not stored; the relay's log notes the device kind and the first characters of the device and account ids, never the content. Forget removes an offline device's row, and signing out takes the device off the hub.你的设备之间互相调用时(中继 0.9 起)。 打开「设备」后,每个登录的 App 都和中继保持一条连接,手机就能让电脑跑一件事,反过来也一样。中继给每台设备存一行:App 自己选的设备 id、你起的名字、是手机还是电脑、操作系统、App 版本、它提供的动作列表、第一次和最近一次出现的时间,以及连进来的网络地址;你的其他设备在 设置 → 设备 里看到的就是这份列表(名字、类型、版本、在不在线、地址)。1.0.7 起这一行还带两个 id,说明这台设备的聊天由谁回答:账号的模型回答就是cloud,否则是你配置的服务商和模型(openrouter、bailian、一个模型 id),从来不是 key、base URL 或别的任何设置;运营者页面读它们,看大家自己配了哪些服务商。一台设备让另一台做的事(一条命令、一个文件、一块要操作的屏幕、手机经由电脑转发的服务商请求)在你的账号内部经过中继,不保存;中继的日志只记设备类型和设备 id、账号 id 的开头几个字符,从不记内容。「忘记」会删掉一台离线设备的那一行,退出登录会把设备从 hub 上拿下来。 - The web, when the agent uses it. Web search, page fetches, the in-app browser, MCP servers and command-line tools reach the sites and services they are for. What the agent sends is what you asked it to do.网络,当智能体使用它时。 网页搜索、抓取页面、App 内浏览器、MCP 服务器和命令行工具会访问它们各自对应的网站和服务。智能体发出去的,就是你让它做的事。
- Update check. Phones, the standalone harness and older desktop shells ask the project's download index at
nanomuse.cn/dl/index.json, then the GitHub API when it does not answer. A runtime you run yourself (nanomuse serve, Docker) checks once a day;server.update_check = falsestops that check. The Windows x64 desktop app checks Windows update metadata after startup and every six hours, first on the download mirror and then on GitHub, with a manual refresh in Settings. Its update library sends a random local staging identifier with metadata requests, and theUser-Agentnames the app and its version. Automatic downloads are on by default and can be switched off in Settings. Windows' network cost is read locally; metered or unknown connections wait for a manual download, and this classification is not sent to the update sources. No conversations, account credentials or settings are sent to the update sources.检查更新。 手机、独立 harness 和旧桌面壳先询问项目自己的下载索引nanomuse.cn/dl/index.json,它不答再问 GitHub API。自己跑的运行时(nanomuse serve、Docker)每天检查一次,server.update_check = false可以停掉这项检查。Windows x64 桌面版在启动后和每六小时检查 Windows 更新元数据,先问下载镜像,再尝试 GitHub,设置里也能手动刷新。更新库会在元数据请求中发送本地随机生成的分批发布标识,User-Agent包含 App 名称和版本。自动下载默认开启,可在设置中关闭。网络计费状态只在本机读取,计费或未知时等待主动下载,这个判断不会发送给更新来源。对话、账号凭证和设置不会发送给更新来源。 - Backups. If you back up to a remote destination (SMB, WebDAV, SFTP, S3, FTP), the backup goes there, encrypted with the password you chose.备份。 如果你备份到远端(SMB、WebDAV、SFTP、S3、FTP),备份会存到那里,用你选的密码加密。
Permissions权限 {#permissions}
Each permission is asked for when a feature needs it and is used for that feature only: notifications for the agent's status and reminders; accessibility for operating other apps' screens, which is off until you turn it on; storage folders you mount; the microphone for voice input; contacts, calendar and location for the tools of the same names, each callable only after you granted them. Nothing is read in the background.每项权限都在某个功能需要时才请求,并且只用于那个功能:通知用于智能体的状态和提醒;无障碍用于操作其他 App 的屏幕,你打开之前它是关的;存储是你挂载的文件夹;麦克风用于语音输入;通讯录、日历和位置分别对应同名的工具,每个都要你授权之后才能调用。后台不读取任何东西。
What the agent may do without asking智能体不问就能做什么 {#what-the-agent-may-do-without-asking}
Before anything it cannot take back (deleting your files, sending a message or data out, paying), the agent stops and a card asks you, in the shell, in the browser and on the phone's screen alike. What you may remember from that card comes in three tiers, and Settings → Permissions → Remembered approvals lists everything you remembered, grouped the same way, one line each, tap to revoke:做任何无法撤销的事之前(删你的文件、把消息或数据发出去、付款),智能体会停下来,弹一张卡片问你,在 shell 里、浏览器里和手机屏幕上都一样。你能从那张卡片上记住的内容分三档,设置 → 权限 → 记住的授权 列出你记住过的全部,按同样的方式分组,一行一条,点一下即可撤销:
- Runs, then tells you: installing software. Never asks; the agent says so afterwards.先做,再告诉你:安装软件。从不询问;智能体事后会说一声。
- Asks first; you may remember it: deleting and sending. Allow for this chat or Always allow for X (one folder, one recipient, one site or app).先问;你可以记住:删除和发送。「本次对话都允许」或「对『X』总是允许」(一个文件夹、一个收件人、一个网站或 App)。
- Highest: asks at the moment of paying, every time: buying, ordering, booking, trading, transferring. There is no “for this chat”. Remember and run next time in X exists, for one app or site only, and asks for your screen lock (fingerprint, face, PIN) before it takes; it is listed first on the permissions page, and every payment that runs on it is said out loud in the chat.最高一档:付款的那一刻问,每次都问:购买、下单、预订、交易、转账。没有「本次对话」这一项。「记住,下次在 X 里直接执行」是有的,只针对一个 App 或网站,并且在执行前要求验证你的锁屏(指纹、面容、PIN);它排在权限页的最前面,每一笔靠它执行的付款都会在聊天里明说。
Passwords, verification codes and card numbers are never typed by the agent; those screens are handed to you. Anything alarming in a command (wiping a disk, force-pushing history, a download piped into a shell) is asked about every time and cannot be remembered. Shopping and trading are fine when you asked for exactly that; nothing unlawful or harmful is done, however it is worded; the agent refuses and says why.密码、验证码和卡号从不由智能体输入;这些界面交给你。命令里任何吓人的东西(抹掉一块磁盘、强推覆盖历史、下载后直接管道进 shell)每次都会问,也不能记住。你明确要买、要交易时,购物和交易没问题;不管怎么措辞,违法或有害的事都不会做;智能体会拒绝并说明原因。
Feedback反馈 {#feedback}
Bug reports go to GitHub Issues from Settings → Feedback; the report is pre-filled with the app version and the device model and nothing else. Do not paste API keys or private conversations into an issue.Bug 报告通过 设置 → 反馈 提到 GitHub Issues;报告里预填了 App 版本和设备型号,别的都没有。不要把 API key 或私人对话贴进 issue。
Changes变更 {#changes}
This page changes when the apps' behaviour changes; the history is in the repository. The same text is at nanomuse.cn/privacy, in English and Chinese.各个 App 的行为变了,这一页就跟着变;历史在仓库里。同样的文字在 nanomuse.cn/privacy,中英文都有。