niuz has no accounts and shows no ads, and it sets no cookie unless you ask for one (below). This page lists everything it records about a visit, what it keeps on your device, and who else sees the connection.
Each page loads a small script that reports which pages were opened, links followed out of the site, forms sent, the size of the window, the page that sent you here if it was another site, and how long the visit lasted. It sends this to niuz.app itself, and our server passes a copy to stats.kapps.dev, our own statistics service, with your IP address, browser and country so that visitors can be counted. There the IP address and browser are turned into a one-way code that changes every day, and the IP address is not stored; what is kept is the country and the kind of device and browser. The script writes nothing to your device: its visit number lives only in the open page.
niuz also adds one to a counter for the country a page is about (Israel, Spain…) and notes the time, so countries people read are updated every five minutes and the others every three hours. The counter holds only the country, a number and a time: nothing about you or your visit.
When you send the feedback form, niuz passes on your message, the kind you chose, your email if you gave one, the page you came from, the edition's language and a coarse device name such as "android/chrome". It is stored in our own inbox at remote-manage.kapps.dev, and the message is sent as a notification to the person who runs niuz. Your email is used only to reply.
niuz remembers a few things in your browser's own storage, and they are not sent to niuz: which stories you have already seen, for 8 days, so new ones can be marked and shown first; whether you chose "New first" or "Top" for that; the views you saved with the star; whether you turned translations on; and, for each language of the site, how you sorted and filtered a story's sources (newest, oldest or most detail, and which language). If you tick "Open niuz on this view", niuz sets one cookie, niuz_home, holding only that page's address, for a year, so that niuz.app can send you there; unticking it deletes the cookie.
When you ask niuz to summarise what the reports add to a story, or an English page asks for titles that have not been translated yet, or you turn on translations on a story, niuz keeps a one-way code made from your IP address, with the hour and a count of requests that hour, to limit how many one visitor can ask for. Titles already translated are sent without it. Summaries and translations are stored with the story and shown to everyone; they record nothing about who asked. Until 29 September 2026 niuz also wrote points of view on request and kept the same kind of rows for them, and recorded when a point-of-view feed was opened, not who opened it. Those rows are still stored and are not deleted at present.
niuz runs on Cloudflare, which carries every request, and niuz's own error and activity logs are kept there for a few days. Fonts are loaded from Google Fonts, so Google sees your IP address when fonts load. The share image of a page is drawn by og.kapps.dev, also ours, when a chat app asks for it. Links to sources take you to their own sites, under their own rules.
niuz reads the public feeds of news outlets. It does not read behind paywalls. See every source and how it works.
Something here is wrong or unclear? Tell us.
Back to the newsThe shading behind a date drains as it ages: full when new, three quarters at 1 hour, half at 6 hours, a quarter at 12 hours, empty after a day. The date is when the source published it.