01
Overview
概要
NameOps generates, validates, and fills paid-media names and UTM parameters. Version 1.0.2 has no cloud account, developer telemetry, advertising, behavioral analytics, or data-sale feature. Core data remains in the user's current Chrome profile.
NameOps 用于生成、校验和填入付费媒体名称与 UTM。v1.0.2 没有云端账号、开发者遥测、广告、行为分析或出售数据的功能;核心数据保存在用户当前的 Chrome 配置文件中。
02
Data stored locally
本机保存的数据
NameOps may store the following in chrome.storage.local:
- workspace name, display name, and local role;
- a salted PBKDF2-SHA-256 administrator credential hash and parameters, never the plaintext password;
- the active rule pack, rule source, Triple Whale setting, and optional remote-rule URL;
- up to three local rule backups and sync status; and
- up to 50 name or UTM outputs the user explicitly copied or filled. Campaign records also contain the platform and Account scope used for local duplicate warnings.
A temporary administrator session is stored inchrome.storage.session for no more than 30 minutes. NameOps does not upload the administrator password or its hash.
工作区名称、显示名称、本机角色、规则与设置、管理员口令的加盐哈希、最多 3 个规则备份和最多 50 条用户主动复制或填入的名称或 UTM 输出记录保存在当前 Chrome 配置文件中;Campaign 记录还包含用于本机同名提示的平台与 Account 作用域。临时管理员会话最长 30 分钟;明文口令和口令哈希都不会上传给开发者。
03
Current-tab access
当前标签页访问
NameOps uses activeTab and scripting only after an explicit user action. Clicking platform detection or Fill reads the current tab URL. Clicking Fill writes the already generated value to the currently focused text, URL, search, textarea, or contenteditable field on a recognized advertising editor.
When the user clicks Merge into Destination URL, NameOps reads the existing value of the currently focused destination URL field, merges UTM parameters locally, and writes the result back to that field. The original URL is not separately stored or uploaded.
NameOps does not continuously browse tabs, read cookies, intercept network requests, or click Save, Publish, purchase, or similar actions. It does not request permanent host access to advertising platforms.
只有用户点击检测或填入时才读取当前网址;只有点击填入时才写入受支持广告后台的当前聚焦字段。点击“合并至目标网址”时,会读取当前聚焦字段中的现有 Destination URL,仅在本机合并 UTM 后写回;原始网址不会另行保存或上传。扩展不会自动点击 Save 或 Publish。
04
Optional remote rule sync
可选远程规则同步
A local administrator may configure an HTTPS JSON rule source. Members may refresh an already configured source. NameOps requests the exact source origin permission only after an explicit sync click. An already authorized source may refresh when the side panel opens if more than 24 hours have passed since the last successful sync.
The selected server receives a read request and may log ordinary network metadata such as IP address, request time, and User-Agent under its own policy. NameOps does not upload local rules, history, current-page content, or administrator credentials to that server.
Remote URLs must use HTTPS and contain no embedded credentials or fragment. Responses are limited to 2 MB and 15 seconds; cross-origin redirects are rejected. Disconnecting or importing a pack with an empty source causes NameOps to attempt to revoke the old optional origin permission.
管理员可选择连接 HTTPS JSON 规则源。该服务器可能按自身政策获得 IP、请求时间和 User-Agent 等常规网络信息,但 NameOps 不会向其上传本机规则、历史、当前网页内容或管理员凭据。响应限制为 2 MB、15 秒,并拒绝跨 origin 跳转。
05
Triple Whale and advertising platforms
Triple Whale 与广告平台
The Triple Whale switch only controls whether generated output contains tw_* parameters. It does not connect NameOps to Triple Whale. After a value is copied or filled into another service, that service processes it under its own privacy policy.
Triple Whale 开关只决定输出中是否包含 tw_*参数,不会让 NameOps 连接 Triple Whale。值被复制或填入其他平台后,由目标平台按其政策处理。
06
Sharing and sale
数据共享与出售
NameOps v1.0.2 does not sell or rent personal data, use it for advertising profiles, or transmit workspace data, rule packs, credential hashes, or name / UTM output records to a developer server. The only optional external read is the HTTPS rule source selected by the user.
NameOps v1.0.2 不出售或出租个人数据,不用于广告画像,也不把工作区资料、规则、凭据哈希或名称 / UTM 输出记录发送到开发者服务器。
07
Security and Limited Use
安全与 Limited Use
The local administrator feature is an editing lock for one Chrome profile, not organization authentication, SSO, audit, or compliance access control. Anyone who controls that profile may clear extension data or reinstall the extension. Rule packs are parsed as JSON data and are not executed as JavaScript. Extension pages load no remote scripts, styles, or fonts. Incognito mode is disabled.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
本机管理员只是当前浏览器的规则编辑锁,不是组织账号或 SSO。规则包仅作为 JSON 数据解析,不会作为 JavaScript 执行;扩展页不加载远程脚本、样式或字体,并禁用无痕模式。通过 Chrome API 获得的信息遵守 Chrome Web Store User Data Policy,包括 Limited Use 要求。
08
Retention and deletion
保留与删除
Local history is capped at 50 entries and rule backups at three. Other settings remain until the user modifies or resets them, clears extension data, or uninstalls NameOps. Export rules before removal if they should be retained. A remote server controls its own log retention.
本机名称或 UTM 输出记录最多 50 条,规则备份最多 3 个。用户可通过重置、清除扩展数据或卸载删除数据;如需保留规则,请提前导出 JSON。远程服务器日志由其运营者管理。
09
Children’s privacy
儿童隐私
NameOps is a productivity tool for paid-media professionals. It is not directed to children and does not knowingly collect children’s personal information.
NameOps 面向付费媒体工作人员,不以儿童为目标,也不会有意收集儿童个人信息。
10
Changes and contact
政策变更与联系
If a future version adds cloud accounts, telemetry, or a new data transfer, this policy and the Chrome Web Store disclosures will be updated before that feature is released.
- Publisher
- Wandrew Lab
- Version
- NameOps v1.0.2
若未来版本增加云账号、遥测或新的数据传输方式,本政策与商店数据披露会在功能发布前更新。联系邮箱:support@wandrewlab.com。