效率工具的开发者不收集、不存储、不读取、不共享你的任何个人信息。 全部工具的数据都只保存在你自己的设备上。所有工具都不含统计埋点、不含广告、不含行为追踪组件，事件提醒的授权校验也完全在离线完成。 只有当你主动开启推送、邮件、同步或设备采集功能时，相关数据才会按你的配置，发送到你自己指定的服务器、你自己注册的第三方服务，或你自己的设备——开发者不参与、不经手，也无法访问这些数据。
本隐私策略（以下简称"本策略"）适用于由开发者 INNF 发布、统称为效率工具的全部 Windows 桌面工具，包括：
本策略说明上述工具会接触哪些信息、这些信息存放在哪里、在什么条件下会离开你的设备、以及你可以如何控制与删除它们。文档版本 2.0 起，本策略由原先仅覆盖事件提醒扩展为覆盖效率工具全部工具；事件提醒的服务器同步、邮件与推送细节，作为第 4 节的一部分继续保留。本策略与使用条款（EULA）相互独立。
不收集任何信息。
具体而言，全部工具：
为实现各自功能，各工具会在程序所在目录（或各自的用户数据目录）创建并维护下列文件，全部保存在你自己的电脑上，不会自动上传到任何地方：
| 工具 | 本机数据文件 | 包含的内容 | 用途 |
|---|---|---|---|
| 事件提醒 | reminders.json config.json email_log.txt |
提醒记录（标题、备注、日期时间、农历标志、循环规则、提前与延后分钟、通知开关、同步标记、状态）；设置（SMTP 与邮箱授权码、PushPlus 令牌、企业微信 Webhook、同步服务器地址与设备令牌、注册码、随机设备标识）；邮件发送结果日志 | 实现提醒、邮件与服务器同步 |
| 网络监控 | 程序目录下的设备清单与告警配置 network_devices.xlsx（导出清单） |
被监控设备（名称、地址、类型）、延迟阈值与告警次数、告警通道凭据、历史最高延迟 | 实现批量 Ping 监控与告警 |
| 密码记录 | vault.dat vault.meta.json |
vault.dat 为全部账号条目的密文（由主密码派生密钥加密）；vault.meta.json 仅存放盐、校验值与密码提示，均非机密。主密码永不落盘 | 本地加密存储账号密码 |
| 工作日志 | work_log.db attachments/ |
SQLite 单文件库（日志内容、类别、日期）；attachments/ 存放你自行添加的截图附件 | 记录、查询与导出工作日志 |
| 设备监控 | devices.json device_history.json settings.json vendor_profiles.json logs/ |
设备与 OID 配置、近 7 天采集历史、全局设置与各通道凭据、厂商私有 MIB 档案、运行与调用日志（MIB 缓存另存于 %LOCALAPPDATA%） | 实现 SNMP 监控与多渠道告警 |
| 餐费记录 | canteen_data.json | 餐次记录、充值、余额与价格设置（程序目录不可写时回退到 %APPDATA%\Local\CanteenAccount） | 食堂餐费记账与导出 |
| 运维命令生成器 | 无需保存用户数据 | 命令模板全部内置于程序；运行时仅在系统临时目录写入一个网页文件用于显示界面，不含任何用户数据，退出后即失效 | 本地生成运维命令 |
为避免频繁输入，部分工具会把你填写的邮箱授权码、PushPlus / WxPusher 令牌、企业微信 / 钉钉 Webhook、同步服务器设备令牌、SNMP 团体字、云平台账号等凭据以明文形式保存在本机配置文件中，其安全性依赖 Windows 用户账户的访问控制。请勿把这些文件发送或分享给他人；在公共或共享电脑上，请不要启用邮件、推送与设备采集功能。这些工具不采集、不上传上述凭据。
例外与对照：「密码记录」的账号数据是加密存储的——落盘的 vault.dat 只有密文，主密码不存在任何文件里，因此即便数据文件被拿走，没有主密码也无法读出条目内容。
你也可以随时删除各工具的整个目录来彻底清除上述数据（详见第 6 节）。删除后，开发者侧没有任何副本可供删除，因为开发者从未获得这些数据。
全部工具默认不进行任何网络通信。「工作日志」「餐费记录」「运维命令生成器」不进行任何联网；下列功能默认关闭，只有你在设置中手动填写并开启后才会生效，且数据只发送到由你指定、或由你本人运营的接收方：
| 数据项 | 触发条件 | 传给谁 | 加密 |
|---|---|---|---|
| 提醒内容（标题、备注、时间等） | 你开启服务器同步（事件提醒） | 你自己搭建的服务器 | HTTPS（取决于你的配置） |
| 账号、密码、动态验证码 | 你在同步设置中点击登录 | 你自己搭建的服务器 | HTTPS（取决于你的配置） |
| 提醒 / 告警标题与正文 | 你开启邮件、PushPlus、企业微信或钉钉推送 | 你填写的邮箱服务商 / PushPlus / 腾讯企业微信 / 钉钉 / WxPusher | SSL / TLS 或各服务的 HTTPS |
| 设备运行指标（SNMP 读取） | 你开启对应设备的监控 | 你自己的网络设备 | 取决于你在设备上启用的 SNMP 版本（v3 可加密） |
| 云主机 / 宿主机查询请求 | 你添加并开启云平台监控 | 你自己的 ZStack 云平台 | HTTP / HTTPS（取决于你的 API 地址） |
| 除以上功能之外，各工具不发生任何其他网络通信。开发者不经手其中任何数据；工作日志、餐费记录、运维命令生成器完全不联网。 | |||
| 你想做的事 | 怎么做 |
|---|---|
| 关闭某类通知 / 告警 | 在各工具的「通知」或「告警」设置中关闭对应通道，或只对单条记录取消勾选 |
| 停止服务器同步（事件提醒） | 在「同步设置」中取消勾选启用同步；此前已同步到服务器的记录需登录你自己的服务器删除 |
| 只让某条提醒留在本机 | 在新增 / 编辑提醒时取消勾选「同步到服务器」，或把已同步的提醒设为本地 |
| 停止设备采集 | 在设备监控中暂停 / 停止某台设备的监控，或直接删除该设备 |
| 删除单条数据 | 在各工具的主列表中删除对应条目（已同步的提醒可选择同时从服务器删除） |
| 删除全部本机数据 | 退出工具后，删除其目录下的数据文件（见第 3 节），或直接删除 / 卸载该工具 |
| 撤回已外发的数据 | 登录你自己的同步服务器删除对应记录；在 PushPlus / 企业微信 / 钉钉 / WxPusher 中停用相应令牌或机器人；在邮箱服务商处删除已收到的邮件 |
| 取消开机自启动 | 在对应工具的设置中关闭「开机自启」，该工具会删除写入的注册表启动项 |
本工具是面向成年人的通用效率工具，不面向儿童设计，也不会有意收集未成年人的个人信息。由于各工具不向开发者回传任何数据，开发者不掌握任何用户（包括未成年人）的个人信息。若你在未成年人使用的设备上安装本工具，请由监护人指导并监督使用，尤其注意不要在其中填写他人的邮箱或推送凭据。
各工具可能连接的第三方服务，全部由你自行配置与授权，其数据处理行为遵循各自的隐私政策。建议你在启用前阅读：
| 服务 | 作用 | 隐私说明 |
|---|---|---|
| PushPlus | 微信消息推送 | www.pushplus.plus |
| 腾讯企业微信 | 群机器人消息推送 | work.weixin.qq.com |
| 钉钉 | 群机器人消息推送 | www.dingtalk.com |
| WxPusher | 微信消息推送 | wxpusher.zjiecode.com |
| 你的邮箱服务商 | 发送提醒 / 告警邮件 | 见你所用邮箱服务商的隐私政策 |
| 你自建的同步服务器 | 多设备提醒同步 | 由你（服务器运维者）自行制定 |
| 你的网络设备与云平台 | SNMP 采集、ZStack API 查询 | 均为你自己运维的系统，由你自行制定 |
本工具不含任何广告 SDK、统计分析 SDK 或其他第三方数据收集组件。
如果某个工具新增了会接触个人信息的功能，我们会同步更新本策略，并在本页面发布新版本、更新"生效日期"。涉及数据收集方式、共享对象变化的重大变更，我们会通过工具内提示或应用商店更新说明告知你。继续使用更新后的版本，即表示你接受更新后的策略。
如果你对本策略或任一工具的数据处理方式有任何疑问、意见或投诉，请联系：
我们将在收到请求后尽快回复。
| 系统功能 | 使用方式 | 何时发生 |
|---|---|---|
| 文件读写 | 读写各自目录下的配置文件与数据文件（见第 3 节）；读写你在导入 / 导出 Excel 时主动选择的文件 | 启动、保存数据、导入导出时 |
| 注册表（当前用户） | 在你开启"开机自启"时写入 HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run 下的启动项；关闭时删除该启动项 | 仅在你手动切换该开关时 |
| 网络访问 | 仅用于第 4 节列出的可选功能；设备监控另需与你自己网络内的设备及云平台通信 | 仅在你开启对应功能后 |
| 桌面通知 | 以应用内窗口或系统通知的形式弹出提醒 / 告警 | 提醒到期或告警触发时 |
| 系统托盘 | 部分工具（如网络监控、设备监控）常驻系统托盘，便于后台运行与快速唤出 | 在你开启托盘 / 最小化时 |
| 系统临时目录 | 运维命令生成器运行时写入一个网页文件用于显示界面，不含用户数据，退出后失效 | 工具启动时 |
The developer of the Efficiency Toolbox does not collect, store, read, or share any of your personal information. All data stays on your own device. None of the tools contain analytics, advertising, or behavioural tracking, and licence validation for Event Reminder is performed entirely offline. Data leaves your device only when you choose to enable push, email, synchronisation, or device polling — and then it goes only to a server you operate yourself, a third-party service you registered yourself, or your own devices. The developer is not involved in, does not handle, and cannot access that data.
This Privacy Policy applies to all Windows desktop tools published by the developer INNF and collectively known as the "Efficiency Toolbox":
It explains what information the tools touch, where that information is stored, under what conditions it leaves your device, and how you can control and delete it. From document version 2.0 onwards, this policy has been broadened from covering only "Event Reminder" to covering the whole "Efficiency Toolbox"; the server-sync, email, and push details specific to Event Reminder are retained as part of section 4. This policy is separate from, and independent of, the End User Licence Agreement (EULA).
We collect nothing.
To provide their functionality, the tools create and maintain the following files in their own program directory (or their own user-data directory) on your computer. They are never uploaded automatically:
| Tool | Local data files | Contents | Purpose |
|---|---|---|---|
| Event Reminder | reminders.json config.json email_log.txt |
Reminders (title, notes, date/time, lunar flag, repeat rule, advance/postpone minutes, notification switches, sync flag, status); settings (SMTP and email authorisation code, PushPlus token, WeCom webhook, sync server address and device token, licence key, random device identifier); email delivery log | Reminders, email, and server sync |
| Network Monitor | Device list and alert settings in the program directory network_devices.xlsx (exported list) |
Monitored devices (name, address, type), latency thresholds and alert counts, alert-channel credentials, historical peak latency | Batch Ping monitoring and alerting |
| Password Vault | vault.dat vault.meta.json |
vault.dat holds ciphertext of all entries (encrypted with a key derived from your master password); vault.meta.json holds only the salt, verifier, and password hint — none of it secret. The master password is never written to disk. | Local encrypted credential storage |
| Work Log | work_log.db attachments/ |
A single SQLite database (log entries, categories, dates); attachments/ holds screenshot files you add yourself | Recording, querying, and exporting work logs |
| Device Monitor | devices.json device_history.json settings.json vendor_profiles.json logs/ |
Device and OID configuration, ~7 days of polling history, global settings and channel credentials, vendor private-MIB profiles, runtime and call logs (MIB cache is kept separately under %LOCALAPPDATA%) | SNMP monitoring and multi-channel alerting |
| Canteen Ledger | canteen_data.json | Meal records, top-ups, balance, and price settings (falls back to %APPDATA%\Local\CanteenAccount when the program directory is not writable) | Canteen expense bookkeeping and export |
| Ops Command Generator | No user data is stored | All command templates are built into the program; at runtime it writes only a web-page file to the system temp directory to display the interface, containing no user data, which expires on exit | Generating operations commands locally |
To avoid repeated data entry, some tools store credentials such as your email authorisation code, PushPlus / WxPusher token, WeCom / DingTalk webhook, sync device token, SNMP community string, or cloud account in plain text in a local configuration file. Their security relies on Windows user-account access control. Do not send or share these files, and do not enable email, push, or device polling on a shared or public computer. The tools neither collect nor upload these credentials.
Exception and contrast: the account data in Password Vault is encrypted at rest — the on-disk vault.dat contains only ciphertext and the master password is stored nowhere, so even if the data file is taken, its contents cannot be read without the master password.
All tools perform no network communication by default. Work Log, Canteen Ledger, and Ops Command Generator perform no network communication at all. The features below are off by default and only become active once you configure and enable them, sending data only to a recipient you choose or operate yourself:
| Data | Trigger | Sent to | Encryption |
|---|---|---|---|
| Reminder content | You enable server sync (Event Reminder) | Your own server | HTTPS (per your configuration) |
| Account, password, TOTP code | You click sign-in in sync settings | Your own server | HTTPS (per your configuration) |
| Reminder / alert title and body | You enable email, PushPlus, WeCom, or DingTalk push | Your email provider / PushPlus / Tencent WeCom / DingTalk / WxPusher | SSL / TLS or the service's HTTPS |
| Device metrics (SNMP reads) | You enable monitoring for a device | Your own network devices | Depends on the SNMP version you enable (v3 can encrypt) |
| Cloud host / host queries | You add and enable cloud-platform monitoring | Your own ZStack cloud | HTTP / HTTPS (per your API address) |
| Beyond these features, no tool performs any other network communication. The developer handles none of this data; Work Log, Canteen Ledger, and Ops Command Generator never go online. | |||
| What you want | How to do it |
|---|---|
| Turn off a notification / alert channel | Disable the channel in the relevant tool's notification or alert settings, or untick it for an individual entry |
| Stop server synchronisation (Event Reminder) | Untick "enable sync" in Sync Settings; records already on the server must be deleted by signing in to your own server |
| Keep a reminder local only | Untick "sync to server" when adding or editing a reminder, or set a synced reminder back to local |
| Stop device polling | Pause or stop monitoring for a device in Device Monitor, or delete the device |
| Delete an entry | Delete it from the relevant tool's main list (for synced reminders you can also delete it from the server at the same time) |
| Delete all local data | Exit the tool, then delete its data files (see section 3), or simply delete / uninstall the tool |
| Withdraw data already sent | Delete the records on your own sync server; revoke your PushPlus / WeCom / DingTalk / WxPusher token or bot; delete received emails at your email provider |
| Disable launch at startup | Turn off "Start with Windows" in the tool; it removes the registry startup entry it created |
The Toolbox is a general-purpose productivity suite intended for adults. It is not directed at children and does not knowingly collect personal information from minors. Because the tools transmit nothing to the developer, the developer holds no personal information about any user, including minors. If you install the Toolbox on a device used by a minor, please supervise its use and take care that no one else's email address or push credentials are entered.
Any third-party service a tool can connect to is configured and authorised by you alone, and its own privacy policy governs its processing. We recommend reviewing them before enabling:
| Service | Role | Privacy information |
|---|---|---|
| PushPlus | WeChat message push | www.pushplus.plus |
| Tencent WeCom | Group-bot message push | work.weixin.qq.com |
| DingTalk | Group-bot message push | www.dingtalk.com |
| WxPusher | WeChat message push | wxpusher.zjiecode.com |
| Your email provider | Sending reminder / alert emails | See your provider's privacy policy |
| Your own sync server | Multi-device reminder sync | Defined by you, the server operator |
| Your network devices and cloud | SNMP polling, ZStack API queries | Systems you operate yourself; defined by you |
The Toolbox contains no advertising SDK, no analytics SDK, and no other third-party data-collection component.
If a tool gains a feature that touches personal information, we will update this policy, publish a new version on this page, and revise the effective date. For material changes to how data is collected or with whom it is shared, we will notify you through an in-tool notice or the app-store release notes. Continuing to use the updated version constitutes acceptance of the revised policy.
For any question, comment, or complaint about this policy or any tool's handling of data, please contact:
We will respond as soon as possible.
| System feature | How it is used | When |
|---|---|---|
| File access | Reads and writes configuration and data files in each tool's directory (see section 3); reads and writes the Excel file you explicitly choose when importing or exporting | On launch, when saving data, when importing or exporting |
| Registry (current user) | When you enable "Start with Windows", writes a startup entry under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run; removes it when you disable the option | Only when you toggle that setting |
| Network access | Only for the optional features in section 4; Device Monitor additionally communicates with devices and cloud platforms on your own network | Only after you enable the corresponding feature |
| Desktop notification | Shows reminders / alerts as an in-app window or system notification | When a reminder is due or an alert fires |
| System tray | Some tools (e.g. Network Monitor, Device Monitor) stay in the system tray to run in the background and be summoned quickly | When you enable the tray or minimise |
| System temp directory | Ops Command Generator writes a web-page file at runtime to display its interface, containing no user data, which expires on exit | When the tool launches |