Your files stay here

By design: where your files are processed

Your files are handled inside your browser

What goes out: the Pass check, anonymous counts and a few more (see the table)

Check it yourself: once a page is open, turn the internet off and it still works

What leaves your device
Files	Never sent for processing
File names	Never sent for processing
What is in them	Never sent for processing
Licence key (Pass only)	Only when you use a Pass
Usage and page counts (anonymous)	Tool names, rough counts and times, why a job failed, a sign that a result was weak (you pressed “No” under a result, or compressing barely made the file smaller), your first move on a tool page (your own file, or “Try a sample”; once per page), that the free try was offered or used, the kind of place you came from (search, social…) and the kind of device (phone or computer). Page views are counted by Cloudflare Web Analytics without cookies; on PDF, Umami also counts page views and which screens were opened. Never file names, contents or addresses. Not sent if your browser asks not to be tracked
AI models (only when you use AI)	Received once you agree; no file is sent
Send's connection setup	Only what is needed to connect (the six-digit code and the like). No file goes through
A file you hand over with Send	Straight to the browser of the person you chose, encrypted; never stored on a server
A report of what did not work	Reports use a Google Form. Everything is shown before it is sent, and file contents and names are not included

What stays on this device

Continue: the results you saved (the newest 30)
Steps: each step's files and results, for 24 hours after the last step, so going back finds them ("close this work" deletes them at once; a setting keeps none)
Work history: when, which tool, which files went in and what came out (names and sizes, never contents; 5,000 lines or a year; a setting keeps no file names)
Saved recipes, settings, the Pass token, downloaded AI models, and the key that signs a history export (Business)
Chat's conversations and library (if you use Chat)

All of it is inside this browser only and is not sent to a server. Clearing the browser's site data removes it.

See the work history →

The Orihako AI Mask browser extension

In preparation. Once it is in the stores, you can add it from the AI Mask page. Below is how it will work.

On the ChatGPT, Claude, Copilot and Gemini sites it reads the text box and the AI's answers on this PC, only to mask before a send and to put the names back under an answer.
The extension does not send what it reads to Orihako or to anyone else. What reaches the AI's site is the text you send (masked, when you choose "Mask and send").
It runs only on those four AI sites, on orihako.com and on Orihako's nine sites (pdf, photo, stream, chat, image, data, translate, send and find .orihako.com). There it hands files to the tools and shares your word list and mask lists with the AI Mask page, inside this browser.
Your word list and the mask lists stay in this browser. Each mask list is deleted after 30 days, and the extension's window deletes everything at any time.
The extension sends no usage counts (this month's count is kept in this browser). How many places it masked (only a number for each kind) also goes into this browser's AI Mask usage record, from inside an Orihako page when one is open. An Orihako page it opens sends its usual anonymous counts.
A file you open with a right-click is read from where it is (the site that holds it) and handed, inside the browser, to the Orihako page that opens; it is not uploaded to Orihako.

The AI Mask page →

How AI Mask's finding is measured

How much it finds: phones, emails, addresses and the like 98% / people and companies 71% with your list, 98% with “Find more names of people and companies” (measured Oct 19, 2026)

117 made-up Japanese business texts (contracts, minutes, HR notes, customer lists, invoice mails) carry what a careful person hides; we count how much AI Mask hides with its first settings. A place counts as found only when every letter of it is hidden.
For people and companies there are two figures: with only the words the writer would likely have in the list, and with “Find more names of people and companies” as well. The second counts what that search found in each text, kept from one run.
The figures are made again from this measurement at every release; nobody types them. Percentages are rounded down.
Made-up texts look like real papers but vary less; on your papers the share may be lower. Something may be missed: check the coloured places before you send.

What the "Network" list can and cannot show

Shown: the hosts this page has loaded from or sent to, counted by kind, from the browser's own record.
Not shown: what was sent. The list says where, not what.
Not listed: traffic from background workers, and direct device-to-device connections (Send).
So "no unfamiliar host" is not proof that no file was sent. Where files are processed is fixed by design, and working with the network off (every tool but Chat and Send) is how you can check it.

Ways to check for yourself

"Not uploaded" is not something to believe; it is something to check.

The "Network" chip in the barOn any tool, press "Network" in the bar at the top: it lists the hosts this page has talked to, by kind, and names any unfamiliar one. What it can and cannot see is written above.
Turn the internet offOpen the page, then switch Wi‑Fi off before you work. It still works; that is the plainest proof there is.

Which AI runs on this computer?

For technical readers

What is inside (in plain words)

Processing happens in the browser: PDFs, pictures and data are handled by a small program (WebAssembly) loaded into your browser and run on your own computer's CPU.
The AI is on your computer too: Models for transcription, summaries or background removal are downloaded once, kept in the browser, and run there. Chrome's built-in AI is used when it is there.
What goes out: As in the table above: the Pass check when you use one, anonymous counts, AI models you agree to download, Send's connection setup and the file Send delivers straight to the person you chose. No file is sent for processing.
What is published: Every tool's entry points are published as an API and MCP for automation. The design records (ADRs) are in each site's docs.
Send's connection set-up: Only what is needed to connect (the six-digit code, network addresses), through a small room on send.orihako.com (a WebSocket relay) and a public STUN server (stun.l.google.com) that helps the two find each other. No file goes through them
Your browser's Network tab: Open F12 → Network and keep it open while you work. It shows each request one by one, including background traffic the bar cannot list, and what each one sent.

Who runs this, and support

Operator: Orihako (Japan). The privacy policy and the legal notices are on the Pass purchase page (Lemon Squeezy).
Contact: orihako.support@gmail.com — Replies within two business days. Bug reports, business enquiries and feature requests all go here. Tell us what did not work →
When something goes wrong: Start with each site's guide and the checks on this page. Questions about a Pass purchase or an invoice go to the same address.