FOR ORGANIZATIONS
A set of eight Chrome extensions, built and published by one person. They add one thing to go on just before you send, open or paste — they do not decide whether anything is dangerous.
Whether to pass this on to the people you work with, and whether trying it is reasonable, is your call to make. The permissions each one asks for, what it stores, whether anything leaves the browser and what it cannot do are published per product.
WHAT THIS IS
What this is, and what it is not. Briefly.
Built by one person
Not a company. Published under the name k-wada@Legacy Tools, made one tool at a time in Tokyo, and listed on the Chrome Web Store.
Free
Everything currently published is free. There is no trial period and no feature that starts costing money later. Any change would be announced on each tool’s own page.
There is no account to create
There is no account to create in order to use the extensions. No sign-in, no registration, no email address to hand over.
They assist one small check
Just before something is sent, typed or pasted, they add one more thing to go on. Detection and display both happen inside each extension.
Setting up with help is an intended use
The first setup can be done together; after that the person uses Chrome as they always did. Nobody has to be asked to learn the settings.
This is not "security software for older people". It has nothing to do with age: it is about the slips that happen in a hurry, on a screen you know well.
WHERE IT HELPS
Sorted by the worry rather than by the product name. The step-by-step detail lives on its own page.
A check for strings that look like personal or internal information. Safe Privacy Mask replaces them with other text inside the field; Safe Privacy Gate shows a confirmation just before sending. Neither sends the text anywhere to be examined.
Safe Privacy Mask Safe Privacy Gate
How to hide personal data before an AI chat →Shows the text of the link next to where it actually goes. It never calls a link dangerous. Works in Gmail, Outlook on the web and Yahoo! Mail; other sites can be added in the settings.
Shows what the page states about who runs it, together with where it was written and what it said. It runs only when the toolbar icon is pressed, and leaves anything the page does not state marked as not found.
How to find out who runs a website →The moment a file is attached, it shows what the file carries — a photo’s location, a document’s author and tracked changes — inside the browser. The file is never rewritten, and the upload is never blocked.
How to check a photo for location data →The full list, including the tools not named here, is on the Use Cases page, sorted by the moment they help with.
See the use cases →BOUNDARIES
If you are deciding whether to pass this on, this is the part to read first.
What they cover is the moment just before a decision: noticing, once. Detection misses things and gets things wrong, and seeing nothing flagged does not mean anything is safe.
Installing them once does not make anything permanently safe either. When the services in use change, or the worry does, the settings need another look.
See the main limits, per product →WHAT YOU CAN CHECK
Instead of the word "safe", here is where to look. None of it asks you to take our word for it.
Does anything typed get sent somewhere?
No. None of the published extensions has any way to send what you type, or what it finds, to a developer’s server. The check finishes inside the browser.
Can a family member or supporter see how it is used?
No. There is no mechanism that records usage and passes it to anyone. It cannot be used for check-ins or reporting.
Can I verify this myself before recommending it?
Yes. The permissions each one asks for are visible under "Details" in chrome://extensions, and whether anything goes out is visible in the browser’s developer tools. The steps are on the transparency page.
Verification record — 16 August 2026
Every extension published at that point, at the same build that was on the store, was loaded into a browser with its settings screen and its popup opened. 234 requests were recorded, every one of them an extension reading a file bundled inside itself. Requests to anywhere outside: zero. That is a count taken on that day, of those versions, across the screens that were opened — it is not proof of safety, and it is not a promise that a later version measures the same.
What was tested, how, and how to check it yourself →Two separate things handle data
The Chrome extensions, and this website. They are published under one name, but they run in different places and handle different things.
HOW IT MIGHT BE USED
These are sketches, not case studies. Nothing below records an actual rollout, and none of it is a recommendation to follow.
A few instructors try it and note where the wording or the steps are unclear — the teaching side handling it first, before anything is mentioned to a class.
Mentioned to whoever asks, then their impressions collected from real use. Nobody needs to install it on everyone’s behalf.
The family adds it to Chrome once and helps with the few settings it needs. After that the person uses it as they always would.
See the page written for families →Checking the permissions and the network behaviour before writing anything up. Whatever is not stated here can be treated as unconfirmed.
There is no organisation contract, no fee and no admin console. It is installed the ordinary way, by each person, from the Chrome Web Store — there is no bulk deployment and no way for an administrator to collect usage. Before recommending anything, the terms and the disclaimer are on each tool’s own page too.
START SMALL
This is not a rollout proposal or a partnership pitch. Use it with a handful of people, and tell us what was unclear or what did not help.
What would be most useful to hear
"It did not help", "it made things more confusing", "we did not need it" — those are answers worth having, exactly as they are. There is no need to find something good to say.
It costs nothing. There is no reseller arrangement and no partnership being asked for. Just tell us how it went.
A trial tells us nothing about who used it or how often — the extensions have no mechanism for collecting that. No member’s name or contact details need to be sent either. What reaches us is the text you choose to write.
Write through the form on the support page — "Other" is fine for both the product and the category. Mail to support@legacy-tools.dev works just as well.
FAQ
Is it free?
Everything currently published is free. There is no trial period and no feature that starts costing money later. Any change would be announced on each tool’s own page.
Is an account required?
No. There is no sign-in mechanism at all, and no email address or other detail to register.
Is this only for older people?
No. It is not aimed at an age group. It is aimed at the slips that happen in a hurry, on a screen you know well. Setting it up with help from family is one intended use — it is a way of using it, not the definition of it.
Can a family member or supporter see how it is being used?
No. There is no mechanism that records usage and sends it to anyone. Treat it as unusable for check-ins or reporting.
Is data sent anywhere?
Not by the extensions. Detection and display both finish inside the browser, and nothing you type and no file is sent anywhere in order to be checked. What is stored is normally just settings, with two exceptions: Find My Age keeps the birthdates you enter and Copy & Prep keeps the passages you collect — both on that device only. Separately from the extensions, the website legacy-tools.dev uses Google Analytics; that has nothing to do with how the extensions run or are used.
Is this a security product?
No. It makes no judgement about danger or safety, and it does not stop scams or malware. It is not a replacement for antivirus software; it is meant to sit alongside one.
Does it work in browsers other than Chrome?
These are published as Chrome extensions on the Chrome Web Store, and no other browser has been tested. Some tools need a particular Chrome version (Safe Night Check needs Chrome 116 or later, for example); each tool’s page states its own requirements.
Can a group try it?
Yes, with no procedure to go through. It works like any other extension: each person adds it from the Chrome Web Store. There is no organisation contract, no fee, no admin console and no bulk deployment.
Can we check the technical details before recommending it?
Yes. The permissions each one asks for, its host permissions, what it stores and where, whether anything leaves the browser, whether there is any analytics, and its known limits are all published per product on the transparency page. The same page carries the steps for checking it yourself in chrome://extensions and the developer tools once it is installed.
What happens if development stops?
The Legacy Tools extensions are not built around a server of ours having to keep running. Development stopping is therefore not, on its own, a reason they would immediately stop being usable. What could still end that is a change on Chrome’s side, a change to the extension APIs, or a listing’s status on the Chrome Web Store. Take it that continued operation is not something we can promise. When it is no longer wanted, it can be removed from Chrome’s extensions page at any time.
Where do we write?
The form on the support page, or support@legacy-tools.dev. Japanese, English and Simplified Chinese. Enquiries are not taken anywhere else, GitHub issues included.
More detailed questions about individual tools are collected on the FAQ page.
See the FAQ →If it does not fit, removing it is the whole exit. Tell us what was unclear and the next release can fix it.
Safe Privacy Mask
Safe Privacy Gate
Safe Mail Link Check
Site Operator Check
Safe Attachment Check