Trust Center
Arrows Lite is a Chrome extension for saving unfinished browser work and resuming it later. Installing any extension — especially one with an AI feature — is a trust decision. This page collects everything relevant to that decision in one place, written from the implementation, not from marketing.
Security principles
- Local first: Saved Cases, sticky notes, and settings live in your browser on your device. No external sync, no server-side account data.
- Nothing leaves without your action: the optional AI summary is the only feature that sends data, and only when you press its button.
- Minimal permissions: no <all_urls>, no cookies, history, webRequest, or debugger permissions. The only external endpoint is our own relay server.
- No tracking: the extension contains no analytics, tracking, or ad SDKs, and loads no remote code.
- Verifiable claims: the “What we send” list below is grounded in the request-building and text-extraction code and is updated together with it.
AI data handling — what we send and never send
The AI page summary runs only when you press the button, reads only the tab you are saving (main frame), and its draft is editable before saving. The request contains exactly three fields:
| Sent when you click | Never sent |
|---|---|
| Page title (trimmed to 300 chars) | URLs — the request has no URL field |
| Visible page text (max 6,000 chars) | Images, video, audio, cookies, passwords |
| Output language code (7-value allow-list) | Form values, hidden elements, scripts and styles |
| — (auth: Google token, memory only) | Saved Cases, sticky notes, settings, browsing history, the contents of other tabs |
The request goes over HTTPS to our own relay server (a Cloudflare Worker), which enforces usage quotas and forwards it to the AI provider (Anthropic). Page text, titles, and tokens are not written to server logs. The full item-by-item explanation is on the “What Arrows Lite sends to AI” page.
Since 1.1.4 there is a second, separate AI action: an overview of a saved work group. When you press it, it sends only the group name you typed and the titles of the tabs in that group, plus the output language — one request per group, no matter how many tabs it holds. Addresses, page contents, images, and cookies are not sent, and no page is read to build it.
Where your data lives
| Data | Where | Notes |
|---|---|---|
| Saved Cases | Your device (browser storage) | Title, URL, note, AI summary, timestamps. Export/import as JSON. Removed on uninstall |
| Sticky Notes | Your device | Keyed by a page hash — the raw URL is not stored for notes |
| Work groups | Your device | A name you type plus the title and address of each tab you grouped. The optional AI overview of a group is written from the tab titles only — addresses and page contents are never sent |
| Bookmarks | Chrome’s own bookmarks | Read to show the Side Panel list. Since 1.1.3 you can also delete or move one bookmark you pick yourself, in the folder view. Nothing is bulk-edited, and bookmarks are never sent anywhere |
| Settings | Your device | Display language (“auto” or one language) |
| AI sign-in token | Memory only | Never written to storage on your device or our server |
Chrome permissions and why
| Permission | Why Arrows Lite needs it |
|---|---|
| tabs | Move/save/close the tab you right-click; manage the two Working Area marker tabs; when you press “Save the Working Area as a group”, list the titles and addresses of the tabs currently inside the Working Area in that one window |
| storage | Store Saved Cases, notes, and the language setting locally |
| contextMenus | The right-click ARROWS LITE menu (MOVE / SAVE / notes / Saved Cases) |
| activeTab + scripting | On your explicit action only: show the sticky-note overlay and extract visible text for AI |
| sidePanel | The Saved Cases side panel |
| bookmarks | Show your bookmarks in the side panel, and delete or move a bookmark you choose there (1.1.3) |
| favicon | Show page icons on Saved Cases cards via Chrome’s internal favicon store (no external fetch) |
| identity + one host permission | Google sign-in for the optional AI summary; HTTPS to our single relay endpoint |
Not requested: <all_urls>, cookies, history, webRequest, downloads, debugger, management. You can verify the list yourself in Chrome’s extension settings.
Google OAuth
Google sign-in is used only to control usage of the AI summary. The requested scope is the minimal “openid” — Arrows Lite does not request access to your Gmail, Drive, contacts, or any other Google data. The token authenticates your request to our relay and is held in memory only.
Developer information
| Product | Arrows Lite (Chrome extension) |
| Development brand | Deskflow Labs |
| Legal entity | JEWELRY SUNFLOWER, K.K. (株式会社ジュエリーサンフラワー), Japan |
| Support | Via the support page on this site (anonymous form; reports are read but not answered individually) |
Related pages: the full privacy policy, the “What we send” explanation, the changelog, and support are linked below and from the footer of every page.
FAQ
Yes. All core features work without AI, and nothing is ever sent unless you press the AI summary button.
The permission list is visible in Chrome’s extension settings. The AI data claims match the extension’s request-building and extraction code, and are documented item by item on the “What we send” page.
Requests go through our relay to the AI provider’s (Anthropic’s) API solely to generate the summary. Our relay does not write page text to its logs.
Private by design — and built to resume your work
What gets sent is explicit and small. Save unfinished work and resume anytime.
Get it on Chrome Web Store — Free