Effective 10 November 2026.

Reader Classic is published by Indevlin, LLC (“Indevlin”, “we”, “us”). This policy covers the Reader Classic app for Android: what it keeps on your device, what it sends and to whom, and what Indevlin receives.

In short

• Indevlin runs no server for Reader Classic and collects no personal data from it. There is no account to create.
• Reader Classic fetches the feeds you subscribe to directly from the sites that publish them. Your subscriptions and reading history stay on your device.
• Unless you have bought ad removal, Reader Classic shows ads from Google AdMob in your list of articles. Google’s ads software collects device data to serve them, as described below. Where the law requires your consent first, Reader Classic asks for it before any ad is requested.
• The one-time ad removal purchase is handled by Google Play. Indevlin never sees your name, email address or payment details.
• Indevlin sees only totals from Google (revenue, ad impressions, installs), never information about you.

What stays on your device

Reader Classic keeps these in its private app storage on your device. Uninstalling Reader Classic deletes them.

• Your subscriptions and folders.
• Articles downloaded from your feeds, and which you have read or starred.
• Your settings: theme, list layout and the unread-only filter.
• Whether ad removal has been bought, so ads stay hidden in the moment before Google Play confirms it.
• Your answer to the ad consent message, kept by Google’s consent software.

If Android backup is on for your device, your subscriptions, articles and settings are included in your device’s backup to your Google account, so they can be restored to a new phone. Google encrypts these backups; Indevlin cannot read them. You can turn backup off in Android’s settings.

Fetching feeds

When Reader Classic refreshes, it connects directly to each site you subscribe to and downloads its feed and the images in it. Those sites receive what any web request carries: your IP address, the time, and an identifier naming the app and Android version (for example “ReaderClassic/0.1.0 (Android 16)”). Each site’s own privacy policy covers what it does with that. Reader Classic sends those sites nothing else about you, and none of it passes through Indevlin.

Opening “Read on website” or a link in an article opens it in your browser, where that browser’s and that site’s policies apply.

When you share a link to Reader Classic from another app, it receives only the text you share, to fill in the subscription form.

Advertising: Google AdMob

Unless ad removal has been bought, Reader Classic shows ads served by Google AdMob between articles in your list. They are labeled “Ad”. Ads do not appear on the screen where you read an article. To serve, limit and measure ads and to prevent fraud, Google’s ads software collects and sends to Google:

• your device’s advertising ID (or, where that is unavailable, an app set ID);
• your IP address, which Google may use to estimate your general location;
• information about your device and Reader Classic (model, Android version, language, app version) and how ads in Reader Classic are shown and tapped;
• diagnostic information about the ads software’s own performance.

Google uses this as described in How Google uses information from sites or apps that use our services and the Google Privacy Policy. Where you consent, Google may also use it to personalize the ads you see. Ads in Reader Classic are limited to Google’s “T” (teen) content rating.

Indevlin does not receive any of this. AdMob gives Indevlin totals only (earnings, impressions and clicks by date, country, app and ad unit), never information about a person or a device.

Your choices

• In the European Economic Area, the United Kingdom and Switzerland, Reader Classic shows Google’s consent message the first time it opens, and no ad is requested until it has been answered. If you do not consent, Google shows only limited, non-personalized ads, where the law permits them.
• In US states with privacy laws, you can opt out of the sale or sharing of your personal information for advertising.
• In both cases, Settings → Ad privacy choices in Reader Classic opens Google’s form, so you can change your answer or opt out at any time.
• In Android’s settings you can reset or delete your advertising ID, which stops it being used to personalize ads.
• Buying ad removal stops Reader Classic from starting Google’s ads software at all.

Ad removal: Google Play

“Remove ads”, in Reader Classic’s Settings, is a one-time purchase made through Google Play under Google’s terms and the Google Privacy Policy. Google handles the payment. For each order, Indevlin receives from Google the order number, the product, the price and taxes, the date, and the country of purchase. When the seller of record is not Google, Indevlin also receives the state or province and postal code needed for sales tax. Indevlin does not receive your name, email address or payment details.

Reader Classic checks with Google Play, from your device, whether your Google account owns ad removal. Nothing about the purchase is sent to Indevlin by the app. Indevlin keeps order records as long as tax and accounting law requires.

Google Play

Reader Classic is distributed through Google Play, and Google’s own privacy policy covers your use of the Play Store. Google provides Indevlin with statistics about Reader Classic, such as installs, uninstalls and ratings, as totals. If you have allowed your device to share usage and diagnostics with Google, Google Play may also give Indevlin reports of Reader Classic crashing or not responding. These include the device model, the Android version and what the app was doing, but not who you are. If you review Reader Classic on Google Play, your review and the name shown with it are public, and Indevlin can see and reply to it.

Permissions

Reader Classic asks for network access, to fetch your feeds and, for ads and purchases, to reach Google. Google’s ads software adds the permissions it needs, including the advertising ID permission and access to network and basic device state, and Google Play Billing adds its own permission for purchases. Reader Classic does not ask for your location, contacts, camera, microphone, files or any other data on your device.

Email

If you email Indevlin, we use your address and message only to reply, keep them only as long as that requires, and delete them on request.

What we never do

Indevlin does not sell or share personal data, uses no analytics or tracking of its own in Reader Classic, and builds no profile of you.

Children

Reader Classic is a general-audience app and is not directed at children under 13. Indevlin does not knowingly collect information from children.

Your rights

Depending on where you live, you may have the right to know, access, correct or delete personal data, and to object to or withdraw consent for its use. Indevlin holds no personal data from Reader Classic beyond the order records and emails described above; ask us about those. For data collected by Google, use the choices above and Google’s own account controls.

Changes

If this policy changes, the date at the top changes with it, and significant changes are noted in Reader Classic’s release notes.

Contact

Indevlin, LLC: [email protected]