隐私政策 — Area Screenshot
一句话:这个扩展只把你在网页上框选的那块区域,在你自己的电脑上拼成一张 PNG 图片,然后存到你的下载文件夹。
没有任何数据被上传、存储到服务器、分享给第三方或用于广告。
即使这些处理全部在你的设备本地完成,我们也按下面各节完整披露处理了什么、为什么处理、以及不处理什么。
1. 这个扩展做什么
Area Screenshot 是一个截图工具。你在网页上点击扩展图标后,拖拽确定截图区域的起点和宽度,滚动到想结束的位置,点确认,扩展会把这段跨越多屏的内容截成一张完整的 PNG 图片并保存到本地。
它没有其他功能。这是它在 Chrome 应用商店里申报的单一用途(single purpose)。
2. 我们处理哪些数据
2.1 网页内容(截取区域内的画面)
当你完成选区并确认后,扩展会读取选区覆盖范围内的网页渲染画面,用于生成你要的那张截图。这属于 Chrome 应用商店定义的「网站内容(Website content)」。读取范围严格限制在你框选的矩形内,不会读取选区之外的页面内容。
这些像素数据只在你的浏览器内存里存在,用于拼接画面,图片生成后即释放。
2.2 页面几何信息与滚动位置
为了让跨多屏截图对齐,扩展需要知道:选区在页面中的坐标、当前滚动容器滚到了哪里、可视区域有多大。这些信息从当前页面即时读取,仅用于计算下一屏该截哪里,不写入任何存储、不发送到任何地方。
2.3 框选过程中的操作信息
在你框选和滚动定位的阶段,扩展会响应鼠标按下、移动、松开和页面滚动事件,用来画选框、跟随滚动延伸选区。这些事件只用于界面即时反馈,不记录、不统计、不上报。
2.4 我们不处理的数据
| 数据类型 | 是否处理 |
|---|---|
| 浏览历史(访问过哪些网站、网址列表) | 不处理。扩展没有申请 history 权限,不读取、不记录任何地址 |
| 表单中输入的内容、密码、支付信息 | 不处理。除非你主动把某一区域框进了截图,否则不会被读取 |
| 身份信息(姓名、邮箱、账号、手机号) | 不处理。扩展不登录、不申请任何身份相关权限 |
| 设备标识符、指纹 | 不处理 |
| 地理位置 | 不处理 |
| 剪贴板 | 不读取。只有你主动点击「复制图片」时,扩展才会把刚生成的那张截图写入剪贴板;它从不读取剪贴板里已有的内容 |
| 使用统计、崩溃报告、埋点 | 不存在。代码中没有任何分析 SDK 或统计上报 |
3. 数据如何被使用
只有一个用途:生成你要的那张截图。具体过程是:扩展控制页面逐屏滚动,每屏截取选区范围内的画面,在浏览器后台把多张画面拼接成一张完整图片,随后在扩展自己的页面里提供标注功能,你确认后再保存为 PNG 文件。
截图开始前,扩展会记录当前的滚动位置;截图完成后会把页面滚动位置恢复回去。截图期间你会看到页面自动上下或左右滚动,这是功能的固有行为,不是采集行为。
4. 数据存储与保留
- 截图只在扩展内部短暂交接一次,随即删除。拼接完成后,PNG 会用一个一次性的随机 ID 写入扩展自身来源(origin)下的 IndexedDB,交给紧接打开的标注编辑器读取;编辑器读到数据的同一时刻就删除这条记录。其他网站页面、其他扩展都访问不到这份数据。
- 如果标注编辑器没能打开(例如标签页创建失败),扩展会立即删除这条记录并改为直接保存原图——不会留下无人读取的副本。
- 除此之外只使用本地存储保存一个界面语言偏好(值为
auto、zh_CN、zh_TW、en之一):编辑页用localStorage即时读写,同一份偏好也写入chrome.storage.local,让框选界面读到一致的语言。除这个语言偏好外不存储任何其他内容,没有 Cookie。标注内容(文字、箭头、矩形)只存在于编辑器页面的内存中,关闭页面即消失。 - 最终生成的 PNG 文件保存在你自己的下载文件夹,由你自行决定保留、移动或删除。扩展不会再次读取它。
- 如果你使用「复制图片」,截图会进入系统剪贴板,由操作系统保管,直到被下一次复制覆盖;扩展不会读取剪贴板中的内容。剪贴板内容只会流向你自己粘贴到的应用。
5. 数据是否传输到外部
不传输。扩展代码中不存在任何向外部服务器发送数据的网络请求——没有 fetch 到远程地址、没有 XMLHttpRequest、没有 WebSocket、没有打点上报。(代码中共两处 fetch 调用:一处读取扩展包内的 _locales 语言文案 JSON,另一处读取浏览器内存里的本地 data: URL,用于在下载接口失败时兜底保存文件;两者都不产生任何网络流量。)
6. 数据共享与出售
不共享,不出售。扩展不包含任何第三方 SDK、广告组件、统计工具或外部分析服务。我们不会把数据转让给广告平台、数据经纪商或任何其他第三方。
7. 权限说明
扩展申请了五项权限,每一项都只服务于「截图」这一个用途:
| 权限 | 为什么需要 |
|---|---|
activeTab |
只在你主动点击扩展图标或按下快捷键时,临时获得当前这一个标签页的访问权。不使用常驻的站点访问权限,不会在你浏览时后台读取任何页面。 |
scripting |
把框选界面注入当前页面,并在截图过程中控制页面滚动位置。 |
downloads |
把生成好的 PNG 文件保存到你的下载文件夹。 |
debugger |
调用 Chrome 调试协议(CDP)的截图接口读取页面画面。详见下一节。 |
storage |
只保存一个界面语言偏好(自动 / 简体 / 繁体 / 英文),让框选界面和标注编辑器使用同一种语言。不保存任何其他内容。 |
8. 关于 debugger 权限的特别说明
这是五项权限里最需要解释的一项,所以我们单独说明它具体做了什么、以及没做什么。
- 什么时候附加:只在你点击扩展图标、开始截图之后。不是常驻附加,不会在你日常浏览时挂在页面上。
- 附加期间会做什么:只发送一条命令 ——
Page.captureScreenshot,也就是「把当前页面画面给我」。除此之外不读取 DOM、不读取网络请求、不读取 Cookie、不读取表单内容、不执行 JavaScript、不修改页面。 - 什么时候断开:截图结束立即断开,无论成功还是失败都会断开(代码中放在
finally块里)。 - 你会看到什么:附加期间 Chrome 会在顶部显示一条「正在调试此浏览器」的提示条,截图结束自动消失。这条提示是 Chrome 的安全机制,不是扩展自己的界面。你的浏览器不需要开启「开发者模式」。
- 做不到的事:它不能在你不知情时附加,不能跨标签页截图,不能读取未选中的区域。
- 为什么需要它:扩展自带的
tabs.captureVisibleTab只能截当前可见的一屏,且无法在程序化滚动后保证每次截取的画面尺寸一致;跨多屏拼接需要更精确的分屏控制。CDP 是 Chrome 提供的官方接口,只在你授权的情况下可用。
如果某个页面已经打开了 DevTools,Chrome 不允许扩展同时附加调试器,此时扩展会显示失败标记 ! 并自动退出。
9. 你的控制权
- 随时在
chrome://extensions里卸载扩展,所有功能立即停止。 - 截图过程中按
Esc或点右键即可取消,不会生成任何文件。 - 已经保存到下载文件夹的图片完全由你掌控,扩展不会回读、不会删除、不会上传。
- 不想要调试提示条?不启动截图就不会附加调试器。
10. 儿童隐私
扩展不是为 13 岁以下儿童设计的,也不会有意处理儿童的个人信息。由于扩展不收集、不上传任何数据,我们无法也不需要识别用户年龄。
11. 政策变更
如果扩展的功能发生变化导致数据处理方式改变,本页面会同步更新,并修改顶部的「最后更新」日期。重大变更会在本页面显著位置说明。
12. 联系方式
关于本政策或扩展的数据处理有任何疑问,请联系:
xiaoyan.zhuxu@gmail.com
通常会在 7 个工作日内回复。
13. 合规声明
本扩展对用户数据的使用遵循 Chrome Web Store 用户数据政策,包括其中的「有限使用(Limited Use)」要求:
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
具体而言:我们只把必要的数据用于实现扩展已申报的单一用途(截图);不转让给第三方;不用于广告投放、用户画像、信用评估或贷款判定;不允许人工读取你的数据。
English Version
Privacy Policy — Area Screenshot
In one sentence: this extension stitches the area you select on a web page into a single PNG image, on your own computer, and saves it to your Downloads folder.
No data is uploaded, stored on a server, shared with third parties, or used for advertising.
Even though all processing happens locally on your device, the sections below disclose in full what we process, why, and what we do not process.
1. What this extension does
Area Screenshot is a screenshot tool. After you click the extension icon on a web page, you drag to set the starting point and width of a capture region, scroll to the point where the capture should end, and confirm. The extension then captures that multi-screen region as one complete PNG image and saves it locally.
It has no other functionality. This is the single purpose declared to the Chrome Web Store.
2. What data we process
2.1 Website content (the pixels inside your selection)
After you confirm a selection, the extension reads the rendered appearance of the web page within your selected rectangle in order to produce the screenshot. This is "Website content" as defined by the Chrome Web Store. Reading is strictly limited to the rectangle you selected; content outside it is not read.
These pixel values exist only in your browser's memory while the image is being stitched, and are released once the file is generated.
2.2 Page geometry and scroll position
To align a capture that spans multiple screens, the extension needs to know the coordinates of the selection on the page, where the current scroll container is scrolled to, and how large the visible viewport is. This information is read from the current page at the moment it is needed, used solely to compute the next capture segment, and is never written to storage or transmitted anywhere.
2.3 Interaction events during selection
While you drag and scroll to define the capture region, the extension responds to mouse press, move, release, and page scroll events in order to draw the selection box and extend it as you scroll. These events drive immediate interface feedback only; they are not logged, measured, or reported.
2.4 What we do not process
| Data type | Processed? |
|---|---|
| Browsing history (which sites you visited, list of URLs) | No. The extension does not request the history permission and reads no addresses. |
| Form entries, passwords, payment details | No, unless you deliberately include a region containing them in a screenshot. |
| Identity information (name, email, account, phone) | No. There is no sign-in and no identity-related permission. |
| Device identifiers or fingerprints | No. |
| Location | No. |
| Clipboard | Not read. The extension writes the screenshot you just generated to the clipboard only when you click "Copy image"; it never reads existing clipboard contents. |
| Usage analytics, crash reports, telemetry | None. There is no analytics SDK and no reporting code of any kind. |
3. How data is used
For one purpose only: producing the screenshot you asked for. The extension scrolls the page one screen at a time, captures the selected area on each screen, stitches the screens into a single image in the background, then opens its own annotation page so you can add markings before saving the PNG file.
Before capturing, the extension records the current scroll position and restores it when finished. You will see the page scroll by itself during the capture; this is inherent to how the feature works, not a form of collection.
4. Storage and retention
- The screenshot is handed over once, inside the extension, and deleted immediately. After stitching, the PNG is written to IndexedDB under the extension's own origin with a one-time random ID, so the annotation editor that opens next can read it. The editor deletes that record the moment it reads it. No website page and no other extension can reach this data.
- If the annotation editor fails to open (for example, the tab cannot be created), the extension deletes the record immediately and saves the original image directly instead — no unread copy is left behind.
- The only other local storage is a single interface-language preference (one of
auto,zh_CN,zh_TW,en): the editor reads and writes it inlocalStorage, and the same value is mirrored tochrome.storage.localso the region-selection overlay shows the same language. Nothing else is stored and no cookies are used. Annotations (text, arrows, rectangles) exist only in the editor page's memory and disappear when the page closes. - The resulting PNG is saved to your own Downloads folder. You decide whether to keep, move, or delete it. The extension never reads it again.
- If you use "Copy image", the screenshot is placed on the system clipboard by the operating system and stays there until overwritten by your next copy action. The extension never reads clipboard contents; the image only goes to whichever application you paste it into.
5. Transmission to external servers
None. The extension contains no network requests that send data anywhere — no remote fetch, no XMLHttpRequest, no WebSocket, no telemetry endpoint. (There are two fetch calls in the code: one reads the bundled _locales language JSON from inside the extension package, the other reads a local data: URL held in browser memory as a fallback for saving the file when the downloads API fails. Neither generates any network traffic.)
6. Sharing and sale of data
Not shared, not sold. The extension contains no third-party SDKs, ad components, analytics tools, or external services. We do not transfer data to advertising platforms, data brokers, or any other third party.
7. Permissions
| Permission | Why it is needed |
|---|---|
activeTab | Grants temporary access to the current tab only, and only after you click the extension icon or press its keyboard shortcut. There is no persistent host access and no background reading of pages while you browse. |
scripting | Injects the region-selection interface into the current page and controls page scrolling during the capture. |
downloads | Saves the generated PNG to your Downloads folder. |
debugger | Calls the Chrome DevTools Protocol screenshot method to read the rendered page. See the next section. |
storage | Stores a single interface-language preference (auto / Simplified Chinese / Traditional Chinese / English) so the region-selection overlay and the annotation editor use the same language. Nothing else is stored. |
8. About the debugger permission
This is the most powerful permission we request, so here is exactly what it does and does not do.
- When it attaches: only after you click the extension icon and start a capture. It is never attached persistently and is never attached while you browse normally.
- What it does while attached: it sends exactly one command —
Page.captureScreenshot, meaning "give me the rendered image of the current page." It does not read the DOM, network requests, cookies, or form values; it does not execute JavaScript; it does not modify the page. - When it detaches: immediately when the capture ends, on success and on failure alike (the detach call sits in a
finallyblock). - What you will see: while attached, Chrome displays a "being debugged" banner at the top of the browser. It disappears when the capture finishes. This banner is Chrome's own safety indicator, not part of the extension's UI. You do not need to enable Developer Mode.
- What it cannot do: it cannot attach without your action, cannot capture other tabs, and cannot read anything outside your selection.
- Why it is necessary: the built-in
tabs.captureVisibleTabcaptures only the currently visible screen and cannot guarantee consistent capture dimensions across programmatic scrolls; accurate multi-screen stitching requires finer control over per-screen capture. The DevTools Protocol is Chrome's official interface for this and is available only with your authorization.
If a page already has DevTools open, Chrome does not allow the extension to attach a debugger. In that case the extension shows a failure badge ! and exits without producing a file.
9. Your controls
- Uninstall the extension at any time from
chrome://extensions; all functionality stops immediately. - Press
Escor right-click during a capture to cancel; no file is produced. - Images already saved to your Downloads folder are entirely under your control; the extension never reads, deletes, or uploads them.
- Do not want the debug banner? If you never start a capture, the debugger is never attached.
10. Children's privacy
The extension is not directed to children under 13 and does not knowingly process their personal information. Because it collects and transmits no data, we neither can nor need to identify a user's age.
11. Changes to this policy
If a change in functionality alters how data is handled, this page will be updated and the "Last updated" date at the top revised. Material changes will be described prominently on this page.
12. Contact
Questions about this policy or the extension's data handling:
xiaoyan.zhuxu@gmail.com
We aim to respond within 7 business days.
13. Compliance statement
This extension's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements:
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Specifically: data is used only as necessary to provide the declared single purpose (screenshots); it is not transferred to third parties; it is not used for advertising, profiling, credit-worthiness, or lending determinations; and no human may read it.