Privacy
What Browse keeps, and what it never does.
Browse has no accounts, no cookies, no analytics, no advertising and no third-party scripts. What you follow, save and set up stays in your own browser.
What stays on your device
The places you follow, the stories, topics and words you follow or mute in News, what you save, what you have already seen (so Browse can mark what is new since your last look), how many discoveries you have explored, the words you mark and the notes you write on newspaper pages, and your choices of layout, density, currencies and pictures from outlets are kept in your browser's storage on this device. We never receive them. Clearing this site's data in your browser erases them. A follows file you save is a file on your device, and a wall link you share carries the places on it only because you chose to share it.
What reaches our server
- Opening a page. Browse reads its public sources once for everyone and serves the result; asking for a page tells us nothing about you beyond what any web request carries.
- Typing a place. The suggestions come from a list of places Browse serves itself (GeoNames' towns and cities, the US Census Bureau's ZIP codes), fetched a few letters at a time and matched in your browser: what you type is not sent anywhere while you type.
- Looking up or following a place. The name you typed or chose, and its coordinates to two decimal places (about a kilometre), are sent to our server. It asks OpenStreetMap's Nominatim to find a typed name, then asks the US Geological Survey, the National Weather Service and the Aviation Weather Center about that area, the National Weather Service or MET Norway for its forecast, NOAA for the chance of an aurora in its one-degree square, and Wikipedia and Wikidata for a photograph of the place, and sends back what they said. Our server keeps none of it about you. If evidence storage is switched on, a record of what those sources said may be kept with the area rounded to about a kilometre; it never holds the words you typed or anything about who asked.
- Near you, before you choose a place. Our host, Vercel, tells our server the approximate city a request comes from, worked out from its IP address. Browse uses it, rounded to about 10 km, to show weather and alerts for that area in the live map's Near you, and the public cameras near it on Live views (sent from our server to Windy.com rounded to about 10 km); both say that it was detected and offer to switch. It is not kept, and it is never served to anyone else.
- Use my location. Your browser asks your permission first, and Browse rounds the position to about a kilometre before it leaves your device.
- Pictures. Your browser asks browse.info for every picture; our server fetches it from Wikimedia, from NASA for the globe's view of the Earth, from the Library of Congress for a newspaper page (with its machine-read words, for Find and marks), or from a camera's host (Caltrans, the USGS, Windy.com) for a Live views still. The exceptions are below, under Show pictures and Videos. To find the cameras near your place, its position goes to our server rounded to about a kilometre, and from there to Windy.com rounded to about 10 km; neither is kept.
- Space. When the space station passes over the places you follow is worked out in the page; those places are not sent anywhere.
- News stories. What changed in a story is read from Wikipedia's own edit history by our server, the same for everyone. Checking a line's quoted words sends our server only the story and the line; it reads the pages that line cites (after their robots.txt), keeps only the verdict, and never a page's text. A story's feed is a public address: a feed reader that asks for it tells us nothing about who reads it.
- Listening. Listen uses your device's own speech engine, a machine voice, and only the voices your device says it runs itself, so the words are not sent anywhere. With no such voice, Browse does not read aloud.
- Requests in general. To stop abuse, our server may hold a request's IP address in memory for a few minutes to limit how often one address can ask. Our host, Vercel, processes the usual request details (IP address, browser and time) to deliver and protect the site.
Show pictures: outlets' pictures and video thumbnails
On the home page, the News page and a news story's page, a story can show the picture its outlet published to go with the article, with a credit naming the outlet. Your browser loads that picture directly from the outlet's own server, not through Browse, so that server sees your IP address, your browser and the time, as it would for any picture, under that outlet's own privacy policy. No referrer is sent, so it is not told which Browse page you are on, and Browse is not told what you looked at. Nothing loads from an outlet on any other page of Browse. The same goes for the thumbnails of the videos in Worth understanding on the home page: each loads from YouTube's server, with no referrer.
To turn them off, untick Show pictures on the home page, the News page or in Coverage's tools. The choice stays on this device, and with it off only free pictures show, served by Browse, and no outlet's or YouTube's server is asked for one. Our server keeps only each picture's address and alt text, never the picture, and reads an article's page for them at most once, the same for everyone. An outlet's small icon beside its name is different: it is a copy kept on Browse's own server, so showing it contacts nobody.
Videos, on the home page
Worth understanding shows three videos Browse chose. Nothing of YouTube's player is in the page until you press play on one. Then the video plays over the page in YouTube's own embedded player, in its privacy-enhanced mode (youtube-nocookie.com), and from that moment YouTube, which is Google, receives what any embedded video sends it: your IP address, your browser, that browse.info is the site (its name only, not the page's address), and what you do in the player, under Google's privacy policy; it may store data in your browser once the video plays. Closing the player removes it. Watch on Playback opens the video on playback.tv, a separate site with its own privacy policy, which plays it in YouTube's player too. Browse is not told what you watched.
Links that leave Browse
A source link opens that source's own site, under its own policies; links to publishers send no referrer. Street View on a place opens Google Maps at that point in a new tab, and only when you choose it; Google's own privacy policy applies there. Opening a Windy.com webcam in Live views shows its timelapse in Windy's own player, loaded from Windy when you open it, under Windy's privacy policy. Tapping Load here on one of NASA's Eyes apps in Space in 3D loads NASA's own app from eyes.nasa.gov inside the page; NASA measures visits to it with Google Analytics through the US government's Digital Analytics Program, under NASA's privacy policy. Nothing from NASA loads until you tap. Open in Yank opens yank.info, a site we also run, whose own privacy page applies there.
Changes and questions
If what Browse sends or keeps changes, this page changes first. Questions: comboventures+browse@gmail.com. See also the terms of use.
Last updated 4 November 2026