Privacy
CyPress Reader doesn’t need an account, and it doesn’t sell or share anything about you. Your feeds, settings and reading history stay on your own device. Here is the full picture, including the places where your device talks to other services.
Last updated November 19, 2026.
What stays on your device
- The sites you follow, your settings, saved stories, highlights, notes and reading history.
- Saved copies of stories and, if you turn it on, their photos, so you can read offline.
- The app has no tracking of what you read. The only usage numbers it can send are the opt-in weekly counts described below, which are off unless you turn them on. After you’ve used the app for a while, it asks you once; nothing is sent unless you say yes.
What leaves your device, and why
To show you news, CyPress Reader has to ask other services for it. These requests carry the address of the page being loaded, and, like any web request, your IP address. They don’t carry your name, because CyPress Reader doesn’t have one for you.
- The news sites themselves. The Android app loads feeds, stories and photos straight from each site. There are two exceptions. A few sites in the catalog offer no list of their own stories, so CyPress Reader follows them through a Google News search for that site, and borrows their pictures from a Bing News search for the same site. And when a site’s own list is blocked, empty or broken, CyPress Reader tries a Google News search and then a Bing News search for that site, so you still get its headlines. These searches see the site’s name and your IP address, not which stories you open. To open a story found this way, the Android app may ask Google News for the story’s real address. If a site turns the app away as a suspected robot, the app opens that one page in a hidden browser on your phone, the way you would open it yourself. That page can set the site’s own cookies, and the site’s robot check may load from its provider (for example Cloudflare, DataDome, hCaptcha or HUMAN). Other companies’ scripts and ads on that page are blocked.
- Relay services (web version). A web page isn’t allowed to read most sites directly, so the web version sends the request through a relay. It tries CyPress Reader’s own relay on Cloudflare first. If that fails, it can fall back to public relays (allorigins.win, codetabs.com and corsproxy.io). Each relay can see which feed or article address was requested. In Settings you can point the web version at a relay you run yourself.
- A last-resort feed reader. If a feed can’t be read any other way, CyPress Reader may ask rss2json.com (api.rss2json.com), a service that reads a feed and sends it back as plain data. It sees the address of that feed and your IP address.
- Getting a full story. When a feed only has a short excerpt, CyPress Reader may try other routes for the full text: the Jina reader (r.jina.ai), Morss.it (morss.it), and Google News search to find the same story elsewhere. Each of these sees the address of that story, or of its feed. The Google News search sees the story’s headline. CyPress Reader does not try to get around a paywall: a story a site keeps for subscribers is shown as the site gives it.
- Videos (YouTube). A story with a video shows its thumbnail from YouTube (i.ytimg.com). Only when you tap play does the app load YouTube’s privacy-enhanced player (youtube-nocookie.com), which then sees your IP address. Nothing is loaded from the player before you tap.
- Translate story (optional). In the Android app the story is translated on the phone itself, and its text is never sent anywhere. The first time you translate from or into a language, the app downloads that language’s small translation pack (about 30 MB) from Google; only the download request is made, never the story. If your phone can’t translate on the device, CyPress Reader asks first, and only when you choose Open does Google Translate (translate.google.com) load, which then sees the story’s address and your IP address. Translated headlines (a per-site or all-sites option in the Android app) work the same way: the headlines are translated on the phone and only the language-pack download is made. Google’s translation component can also send Google anonymous technical details about the feature (such as that a translation ran and whether it failed), never the story or its headlines.
- Sync (optional, off unless you turn it on). Sync keeps your library the same on two of your devices through a relay you run yourself (a small Cloudflare Worker you set up). Everything is locked on your device with your sync code before it is sent, so the relay only stores scrambled data it can’t read. Like any web service, your relay sees your IP address. CyPress Reader runs no sync service of its own.
- Fonts in the app. The app’s fonts are built in. Only the dyslexia-friendly font, if you choose it in settings, is loaded from jsDelivr, which sees your IP address when the font loads.
- Updates (Android). About once a day the Android app asks GitHub for the newest release. If you accept an update, the app downloads it from GitHub and asks Android to install it. CyPress Reader isn’t on the Play Store, so this is how updates reach you.
- AI summary (Android, some phones). On phones with Google’s built-in AI, the app makes a short summary of English stories on the phone itself. The story text is never sent anywhere. The first time, the phone may download the summary part from Google; only that download request is made, never the story.
- Natural voice (Android, optional). Off unless you choose a voice size in Read aloud settings. Then the voice files (about 200 or 360 MB) download once from CyPress Reader’s GitHub page, over Wi-Fi only, and nothing comes from anywhere else. The voice runs on your phone, so the stories it reads are never sent anywhere. Delete removes the files. Built with open-source parts: the Kokoro voice model (hexgrad) and sherpa-onnx (k2-fsa), misaki, g2p_en and Apache OpenNLP (all Apache 2.0), the CMU Pronouncing Dictionary (BSD-style license), and a grammar model trained on the Universal Dependencies English Web Treebank (CC BY-SA 4.0).
- Looking up a word (optional). If you select a word in a story and tap Look up, the word is opened in Wiktionary (en.wiktionary.org) in your browser. Nothing is sent until you tap.
- Moving to a new phone (optional). “Move to a new phone” in Settings, Sites & backup, shows your sites, saved stories and highlights as codes on the old phone’s screen, and the new phone reads them with its camera. The camera is used only while that box is open, and the pictures it sees are never saved or sent. Nothing goes over the internet. The Android app asks for camera permission only the first time you tap Scan codes.
- Local news (optional). CyPress Reader never asks for your location. With “Near you”, the place name you type (for example a town or city) is sent to Google News and Bing News as a search, and their results become feeds. Those services also see your IP address. In the web version this search can pass through the relays described above. Places you save stay on your device only.
- Finding new feeds (optional). When you type a topic or feeling in Add a site and the built-in list has little to show for it (or you tap “Search the web”), the words you typed are sent to Feedly’s public search (cloud.feedly.com), which sees them along with your IP address. Addresses and the names of sites in the built-in list are not sent. The feeds it lists are then fetched from their own sites to measure how active they are.
- Sharing a story. When you share a story, its headline, source name, web address, color and date (and its picture address) are packed into a CyPress Reader link. With “Shorten shared links” on (Settings, About CyPress), only when you tap Share, that link is sent to CyPress Reader’s own link service on Cloudflare, which stores it for about 13 months so the short link cypressreader.com/s/… keeps working; Cloudflare sees your device’s address as any website does. If you turn the setting off, or the service does not answer, CyPress Reader shares the story’s own web address instead and contacts no one. When someone opens a short link in the Android app, the app asks the same link service for the story behind that code; a long link is read on the phone. When someone opens a shared link in a web browser, the page on cypressreader.com shows the story’s picture straight from the site that published it, so that site sees the visitor’s IP address, as it would if they visited it.
- Usage counts (optional, off unless you turn it on). With “Share anonymous usage counts” on (Settings, Sites & backup), the app sends one small report a week to CyPress Reader’s server on Cloudflare: app version, whether you use the app or the website, system and device type (phone, fold, tablet or computer), language, your theme and a few layout settings, the Natural voice size you chose (if any), rough counts of your sites, folders and saved stories (such as “6-20”), how many times a few features were used (stories opened, read aloud, shares, saves, searches, Near you, side by side), how many errors happened with a short code for each kind and up to three error messages (web addresses removed), how many times the app closed unexpectedly while on screen (and how many times installing an update closed it), typical seconds until stories showed and until a refresh finished, how often the screen froze briefly, how many times something was tapped three times quickly without doing anything (and what kind of thing it was, such as “a picture”, never its text), how often Add was closed without adding a site or a story was closed within 3 seconds, and which sites from the app’s own catalog failed to load and why (for example “blocked by the site”). Sites you added yourself are never named. It never includes your sites, stories, searches, places or anything that identifies you or your device, and no ID links one week’s report to the next. Your internet address is not stored. Reports are deleted after about 13 months. “What the counts contain” in Settings shows exactly what would be sent. Turn it off at any time and nothing more is sent.
- Reporting a problem. When you use “Report a problem” in Settings or in a story’s menu, what you write is sent to CyPress Reader’s server with the details shown in the box (the story’s web address when you report from a story, app version, whether it’s the preview or the released app, screen size, browser details, theme and light/dark setting, number of sites, recent error messages, and your last 20 taps by button name, such as “menu” or “go Daily”, never story titles or what you typed). Your sites’ web addresses are included only if you tick “Include the addresses of my sites”; it is off every time the box opens, and the details preview shows them before you send. After you send, the app keeps the report’s random code and once a day asks the server whether it’s being worked on or fixed, so Settings can show you; only that code is sent. Tap “See the details that are sent” to read all of it before you press Send. “Email instead” opens your own email app with the same text, so you can get a reply; nothing is sent until you send that email. It is kept for about 13 months and read only by the developer, who may use an AI assistant (Claude, made by Anthropic) to help sort reports and find the bug. Reports are not used to train AI models, and the assistant never sees anything the report doesn’t already contain.
- Sending a messy story. “Send a messy story” in a story’s menu (under “Something wrong?”) sends that story’s web address, its title, the page as your phone downloaded it, the text the app kept and the app’s technical notes on how it got the story, plus a note if you write one. Nothing else about you is sent. It goes to the same server, only when you press Send, is kept for about 13 months and is used only to improve how the app cleans up stories.
This website
cypressreader.com uses no analytics at all: no page-view counting, no cookies, no trackers. The home page makes no third-party requests; its fonts are hosted on the site itself. The site is served through Cloudflare, which, like any web host, sees each request (your IP address and the page asked for) and keeps standard server logs. We do not add Cloudflare’s analytics script, or any other script that counts visits, to our pages.
Your choices
- Turn on Offline mode or Only on Wi-Fi in Settings to limit what the app downloads.
- Use the Android app to skip the relay services, or run your own relay for the web version.
- Don’t use “Near you” or the “Keep photos for offline” setting, and none of those requests happen.
- Usage counts are off unless you turn them on, and Report a problem sends only when you press Send.
- Delete everything CyPress Reader keeps with Erase everything and start over in Settings, About CyPress, or by clearing the app’s storage in Android.
- Emailing hello@cypressreader.com. Email to this address arrives through Cloudflare. A copy of the whole message, attachments included, goes to the developer’s own inbox (Gmail). A short version is also kept on CyPress Reader’s server next to the problem reports: your email address, the subject and the text of the message; attachments are only listed there by name. The server copy is deleted after about 13 months, or sooner if you ask, and the inbox copy will be deleted too if you ask.
- Data on CyPress Reader’s server. Erase everything only clears your device. Problem reports, emails and short links are deleted on their own after about 13 months. To have them deleted sooner, email hello@cypressreader.com with roughly when you sent the report (or the short link itself), and it will be removed within 30 days. Usage counts carry nothing that links them to you, so there is no way to find or remove one person’s reports; turning them off stops new ones.
The demo on the home page
The “Try it live” demo on cypressreader.com runs a copy of CyPress Reader with made-up stories. It keeps everything in memory, sends nothing to other services, and never touches the sites, settings or saved stories in your own CyPress Reader.
Questions
CyPress Reader is made by Cy. Email hello@cypressreader.com or ask on the CyPress Reader support page. If something here is out of date, please tell us.