Eight Point Labs

Kept privacy

No account, no server, no analytics. What you read stays on your phone.

Last updated 30 August 2026 · Eight Point Labs LLC

The short version. Kept has no account, no server of ours, and no analytics. We never receive your subscriptions, your saved articles, or a record of what you read, because there is nowhere for any of it to go. What does leave your phone is the one thing a reader cannot avoid: requests to the sites you chose to follow, made the same way a browser makes them.

Who this covers

Eight Point Labs LLC publishes Kept, an Android app for reading feeds and saving articles to read later. This page describes Kept. Our other apps have their own policies, linked from the main privacy page.

This site itself uses Google Analytics to count page views. That is the website, not the app; the app contains no analytics of any kind.

1. What we collect

Nothing. Eight Point Labs operates no server for Kept, holds no account for you, and receives no copy of anything the app stores. There is no analytics SDK, no crash-reporting SDK, no advertising SDK, and no tracking library anywhere in the app. You are never asked to sign in, because there is nothing to sign in to.

2. What leaves your phone, and why

Kept is a reader, so it fetches things. Every request it makes goes directly to the publisher you chose, and to nobody else. Nothing is routed through us.

  • Feeds you subscribe to. Kept fetches each feed's address on a schedule, including in the background while the app is closed, so new articles are waiting when you open it. It identifies itself with a user agent beginning Kept/ and sends no cookies or identifiers of its own.
  • Articles you open. The reader displays the article's own HTML, so images and embedded media inside that article load from the publisher's servers, exactly as they would in a browser tab.
  • Addresses you paste. When you add a subscription by pasting a site address, Kept requests that page once in order to find its feed.

In each case the publisher's web server sees the request the way any web server sees a request, which includes your IP address. That is inherent to fetching anything over the internet and is not something Kept adds. If you would rather a publisher not see your address directly, use a VPN, exactly as you would when browsing.

3. What stays on your device

Your subscriptions, the articles Kept has fetched, which ones you have read, and which ones you have saved all live in the app's own private storage on your phone. No other app can read it, and we cannot read it. Uninstalling Kept deletes all of it.

You can export your subscriptions as a standard OPML file at any time from the Feeds tab. It is a plain text file any other reader can import, written to whatever location you pick.

4. Permissions, and why

  • INTERNET — to fetch the feeds and articles you asked for. A reader cannot work without it, and we would rather say that plainly.
  • ACCESS_NETWORK_STATE — so a scheduled refresh waits for a connection instead of failing and wasting battery.
  • ACCESS_LOCAL_NETWORK — so a feed you host yourself on your own network keeps working on Android 17 and later, which otherwise blocks apps from reaching local addresses. Kept contacts a local address only if you subscribed to one.

Kept asks for no location, no contacts, no microphone, no camera, and no access to your photos or files beyond the single file you pick when importing or exporting OPML.

5. No cloud backup of your reading

Kept's manifest sets android:allowBackup="false". Android's automatic backup would otherwise copy the app's database, which is a record of what you read, into your Google Drive. We turned it off, because a promise that your reading stays on your device should hold in the manifest and not only in the marketing. The trade is deliberate: you move your subscriptions to a new phone with the OPML export rather than having them silently restored.

6. The reader runs no scripts

Article content is untrusted by definition, because it comes from whoever published it. The reader displays it with JavaScript disabled, so a page cannot run code, fingerprint you, or act on your behalf inside the app. Tapping a link hands it to your normal browser instead of following it inside Kept.

7. Things that hand data to another app, at your request

  • Opening in your browser. Kept passes the article's address to whichever browser you use. What happens after that is between you and that browser.
  • Sharing. Sharing an article sends its title and address to the app you pick from the system share sheet, and nowhere else.
  • Saving into Kept. When you share a link into Kept from another app, that app hands Kept the link. Nothing travels the other way.

8. Children

Kept is not directed at children and collects no personal information from anyone, including children.

9. Your data rights

There is no request to make, because we hold nothing about you. Everything Kept knows is on your phone: export it with OPML, delete it by uninstalling. If you would like to ask us something anyway, the address is below and a person answers it.

10. Changes to this policy

If Kept ever gains a feature that changes any of the above, this page changes first and carries a new date at the top. We will not quietly widen what the app does and update the policy afterwards.

11. Contact

Privacy questions: [email protected]. Anything else: [email protected].

How to verify this yourself

None of this asks for trust. Every claim above is checkable from the installed app:

  • The permission list. Any APK inspector reads the manifest and shows exactly three permissions: INTERNET, ACCESS_NETWORK_STATE and ACCESS_LOCAL_NETWORK.
  • No cloud backup. The same manifest shows android:allowBackup="false".
  • No trackers. The package can be scanned by a third-party tracker analyser such as Exodus Privacy, which lists any known tracking library found inside it.
  • Where it connects. Point a network monitor at your phone and watch Kept refresh. The only hosts it contacts are the feeds you added.