Privacy
Cut is a metasearch engine: it passes your search to other search engines and shows you what they return. It is built to keep nothing about you.
What Cut stores
Nothing that identifies you. There are no accounts, no analytics and no request logs. Searches and IP addresses are never written to disk.
A few things are held in memory for a short time so the site works:
- Results from each engine are cached for 10 minutes so that “More results” loads quickly. Cache keys are hashed with a random value that changes every time Cut starts.
- Site icons and image thumbnails are cached for a few hours.
- Requests are rate-limited so upstream engines don’t block the server. The limiter keys on a salted hash of your IP address, keeps it for about two minutes, and the salt changes daily.
Cookies
Cut sets one cookie, cut, and only when you change a setting. It contains your settings (theme, region, safe search and which engines to use) and nothing else. You can see its exact contents on the settings page.
What search engines see
Your browser only talks to Cut. Cut sends your query to the engines you have enabled from its own server, without your IP address, cookies or browser details. Suggestions, site icons and image previews are fetched the same way, along with a Global Privacy Control signal unless you turn it off.
Cut can send all of this through a proxy or the Tor network, with a new Tor circuit for every search, and look up engines with DNS over HTTPS. This server currently uses: Direct connection. See connection settings.
Links
Result links point straight to the destination. Cut removes click-tracking redirects and tracking parameters such as utm_source, fbclid and gclid, replaces Google AMP pages with the original, and can open YouTube, Reddit, X and Medium links in privacy-friendly front-ends. Pages are served with Referrer-Policy: no-referrer, so the sites you visit aren’t told what you searched for.
Result links are also checked, on Cut’s server, against public lists of phishing and malware sites.
Who hosts this copy
This copy of Cut runs on Netlify. Like any web host, Netlify carries the connection between your browser and Cut, so it handles your IP address and your requests. Netlify’s privacy policy says what it keeps.
Running your own copy
Cut is a small Node.js application. If you run it on your own computer or server, nobody else is in a position to see your searches.