Privacy policy

Engineering Reads is made by Sagar Chapagain, an independent developer. This policy covers the website at engineeringreads.sagarchapagain.com.np and the Engineering Reads app for Android (package app.engineeringreads).

In short

• There is no account, and neither the website nor the app asks for your name, email or any other personal detail.
• There are no analytics, no advertising and no tracking cookies.
• Your saved links, followed feeds, favourites, read history and reading preferences stay on your own device. We have no server that stores them.
• From Android version 1.0.2, Google Play handles optional reviews and app updates under its own policies, as explained below.
• Posts open on their authors’ own sites, which have their own privacy policies.

The website

The website is a set of static pages served by Cloudflare. Like any web host, Cloudflare receives the technical details every browser sends with a request, such as your IP address and browser type, and uses them to deliver the page and to protect the site from abuse. We do not add analytics to the site and do not receive a log of who visited.

Posts you save on the website, your favourite sources, read history and your reading preferences are kept in your browser’s local storage. Read history can include a post’s title, link, source and when you read it. These records are not automatically uploaded to us or synced between devices, and clearing your browser data removes them. The site sets no cookies.

Pictures beside a post are loaded from the publisher’s own server, so that server sees the request in the same way it would if you visited it.

The Android app

Your reading data stays on your phone. The app connects to the internet to:

• download the list of posts and sources from this website;
• read the public feeds of the sources, and of any feed you choose to follow;
• read the title, summary and picture of a page you keep, so the saved link is recognisable later;
• open the pages you tap, in its built-in browser or in your browser of choice.

Those requests go straight from your phone to the site concerned. The websites you open in the built-in browser may set their own cookies and are covered by their own privacy policies.

Your kept links, tags, followed feeds and read history are stored in a database on the phone. Read history can include a post’s title, link, source and when you read it, so it can remain available after the post leaves the feed. The sources you star as favourites and your theme and font choices are kept in the app’s settings on the phone. When you share a link to the app, it receives only that link and its title. When you import or export a file, it reads or writes only the file you pick.

If Android backup is turned on for your Google account, Android may include the app’s database and settings in that backup so they come back on a new phone. That backup is made, encrypted and stored by Google under your Google account; we cannot read it. You can turn it off in your phone’s settings.

From version 1.0.2, the app may ask Google Play to show its optional review card after you return from several articles. The article counter and whether the card has been requested stay on your phone. If you choose to leave a rating or review, Google Play handles it under its own policies; reviews may be public. The app does not receive the rating or review fields. You can edit or delete your review in Google Play. See Google’s rating and review guidance.

From version 1.0.2, the Android app can check for newer versions through Google Play and offer an update. Google Play uses device metadata, the installed app version and information about installed modules or asset packs to check availability and estimate download size. Google states this data is encrypted, is not shared with third parties and is deleted after a fixed retention period. Downloads use Google Play’s consent flow; you choose when to restart. See Google’s in-app update disclosure.

The app asks for one permission, internet access. It contains no advertising, analytics or crash reporting code.

Exports and sharing

You can export saved links and read history from the website, and saved links, followed feeds and read history from the app. Exported files contain the records you choose to export; searches do not limit a full-history export. We do not receive those files. If you save a file to a cloud provider or share it with another app or person, that destination handles it under its own policies. Sharing the Android app sends its public Play Store link through the sharing destination you choose, without attaching your reading data.

Removing your data

On the website, clear the site’s data in your browser. In the app, remove items one by one, or clear the app’s storage or uninstall it, which deletes everything it kept. These steps remove your local reading data. We hold no copy of it to delete. They do not remove Android backups, exported files or Google Play reviews; manage those through the service or destination that holds them.

Children

Engineering Reads is written for adults who work in software. It is not directed at children and does not knowingly collect anything from them.

Changes

If this policy changes, the new text is published here with a new date at the top.

Contact

Questions about privacy, or a request from a publisher, go to developersagar2093@gmail.com. More on the contact page.