Corridor

Privacy Policy · 隐私政策

Corridor · Art New Tab · 长廊 Corridor · 艺术新标签页 Last updated: 1 November 2026 · 最后更新:2026-11-01

English · 中文


English

In one line

Corridor collects nothing. There is no server, no account, and no analytics. Everything lives on your own computer.

What is stored, and where

What Where Does it leave your computer?
Settings (mode, frame, language…) chrome.storage.local No
Favorites and history chrome.storage.local No
Cached artwork images IndexedDB allocated to this extension No
Folder handles for your custom sources IndexedDB No
Any API key you enter chrome.storage.local Only to the endpoint you typed in, nowhere else
AI-generated translations and fields chrome.storage.local No
Sites you pin or remove in Pause Gallery, and the order of their labels chrome.storage.local No
Backup files (only when you export one) Wherever you choose in the Save As dialog Kept by you; API keys are left out by default

The developer cannot see any of it. Corridor has no backend.

When does it make network requests?

Only in these cases, all of which you control:

  1. Artwork images — requests to upload.wikimedia.org for public-domain paintings. No identifying information is attached.
  2. Daily additions (on by default) — metadata queries to commons.wikimedia.org and www.wikidata.org.
  3. AI enrichment / multilingual (off by default, needs your own endpoint) — sends a JPEG downscaled to at most 1024px, plus the prompt, to the endpoint address you entered. Leave it blank and not a single request is made.
  4. Online gallery sources (off by default, needs a URL from you) — requests the page, images and videos from the site you entered. Some sites (shared tables, cloud drives and the like) need their sign-in domains as well; Chrome lists every domain in its permission prompt the first time, before anything is sent. For those sites the extension uses that site’s cookies in your browser, exactly as if you opened the link yourself — if you are signed in there, the site sees your account. If you turn on scheduled sync (off by default), these same sites are asked again for their image list at the interval you choose, while a Corridor tab is open. Nothing from the site is sent anywhere else.

The Pause Gallery screen makes no network requests and fetches no site icons. If your model runs on your own machine (localhost and the like), its requests never leave that machine.

Nothing else. No analytics, no telemetry, no ads, no third-party SDKs.

About your API key

About local folders

Pause Gallery can list sites from three places: the ones you pin yourself, Chrome’s most-visited list, and the tabs you have open right now.

About backup files

Why each permission

Permission What it is for
storage Settings, favorites, history
unlimitedStorage The image cache can reach several hundred MB
alarms Waking the background worker for daily additions and scheduled enrichment
downloads The “export images” feature writes cached artworks to your Downloads folder; downloading the current work; saving backup files
declarativeNetRequestWithHostAccess Local models only: rewrites the Origin header on the extension’s own requests to an address on your machine (localhost, 127.0.0.1…) so that services such as Ollama accept them. It works only on addresses you have granted, and requests to public endpoints are left untouched
topSites (optional) Showing Chrome’s most-visited sites in Pause Gallery. Not requested at install; asked for when you turn it on
tabs (optional) Showing your open tabs in Pause Gallery, and “Close selected tabs” in tidy mode. Also asked for only when needed
Three Wikimedia hosts Fetching public-domain artwork images and metadata
All other hosts (optional) Never requested up front. Only when you enter your own AI endpoint or gallery URL and press a button does Chrome ask you about the domains that source needs — usually just that one host

Changes

Any change to this policy will be noted in the extension’s release notes and on this page.

Contact

Charles Chern · achillesmars@gmail.com


中文

一句话

长廊不收集你的任何信息,没有服务器,没有账号,没有统计代码。所有数据都存在你自己这台电脑上。

它到底存了什么,存在哪

存了什么 存在哪 会不会离开你的电脑
设置(呈现方式、画框、语言等) chrome.storage.local 不会
收藏与浏览记录 chrome.storage.local 不会
画作图片缓存 浏览器分给本扩展的 IndexedDB 不会
自定义图库的文件夹句柄 IndexedDB 不会
你填的 API 密钥 chrome.storage.local 只发往你自己填的那个接口地址,别处一概不发
AI 生成的译文与作品信息 chrome.storage.local 不会
暂歇里自己钉的站点、摘掉的站点、展签顺序 chrome.storage.local 不会
备份文件(你点导出时才有) 你在「另存为」里选的位置 由你保管;密钥默认不写进去

开发者看不到上面任何一项。 长廊没有后端,作者没有任何途径读到你的数据。

它会往外发请求吗

只在这几种情况,且都是你主动开启的功能:

  1. 取画作图片 —— 向 upload.wikimedia.org 请求公有领域画作的图片文件。这是扩展默认就有的能力,请求里不带任何身份信息。
  2. 每日新作(默认开启)—— 向 commons.wikimedia.org 与 www.wikidata.org 查询公有领域画作的元数据。
  3. AI 补全 / 多语言(默认关闭,需要你自己填接口)—— 把图片缩成不超过 1024px 的 JPEG,连同提示词发往你自己填写的那个接口地址。你不填,一个请求都不会发。
  4. 在线图库(默认关闭,需要你自己填网址)—— 只向你填写的那个网站请求页面、图片与视频。有些网站(共享表格、网盘之类)还需要它自己的登录域名;第一次使用时,浏览器会在弹窗里列出全部域名,你同意之后才发请求。对这类网站,扩展用的是浏览器里该网站的 cookie,等同于你自己打开那个链接:如果你在那里登录着,对方看到的就是你的账号。如果你打开定时同步(默认关闭),长廊会在标签页开着时,按你设的间隔重新向这些网站要一次图片清单。从网站取回的内容不会发往任何其他地方。

暂歇那一屏不发任何网络请求,也不取站点图标。接的如果是本机模型(localhost 这类地址),请求不出这台电脑。

除此之外没有任何网络请求。没有分析、没有埋点、没有广告、没有第三方 SDK。

关于你的 API 密钥

关于本机文件夹

关于暂歇读到的站点

暂歇那一屏可以显示三处来的站点:你自己钉的、Chrome 的常访问榜、此刻开着的标签页。

关于备份文件

权限为什么要这些

权限 干什么用的
storage 存设置、收藏、历史
unlimitedStorage 图片缓存可能到几百 MB,默认配额不够
alarms 「每日新作」与「定时补全」要按时唤醒后台
downloads 「导出图片」把缓存里的画作存到你的下载目录;下载当前作品;保存备份文件
declarativeNetRequestWithHostAccess 只用于本机模型:把扩展自己发往本机地址(localhost、127.0.0.1 等)的请求的 Origin 头改成那个地址本身,好让 Ollama 这类服务放行。只在你已授权的地址上生效,发往公网的请求一个字不改
topSites(可选权限) 暂歇显示 Chrome 常访问的站点。装上时不申请,打开那一项时才问你
tabs(可选权限) 暂歇显示此刻开着的标签页,以及整理模式里的「关掉所选标签页」。同样是用到时才问你
upload.wikimedia.org 等三个域名 取公有领域画作的图片与元数据
其他所有域名(可选权限) 不会预先索取。只有当你填了自己的 AI 接口或在线图库网址、并点下按钮时,浏览器才会就这个来源需要的域名向你确认 —— 通常只有那一个

变更

政策若有变更,会在扩展的版本更新说明与本页同步说明。

联系

Charles Chern · achillesmars@gmail.com


This page is published at https://github.com/yearnst/corridor-newtab/blob/main/PRIVACY.md and is the privacy policy referenced in the Chrome Web Store listing for Corridor · Art New Tab (长廊 Corridor · 艺术新标签页).
本页公开地址:https://github.com/yearnst/corridor-newtab/blob/main/PRIVACY.md