aireader

Privacy Policy

Effective 20 October 2026

This policy covers the aireader app for iPhone and iPad, the web app at https://aireader.news/app/, and the aireader.news service both connect to. All three are operated by Inal Kardanov, an individual in the United Arab Emirates ("we"). Questions: [email protected].

1. The short version

2. What we store on the server, and why

DataDetailsWhy
Your accountOur internal number for the account, the date it was created, and the sign-in methods connected to it (the next two rows), each with the date it was addedTo keep your account
Sign in with AppleThe identifier Apple gives us for your Apple Account (specific to this app's developer). We do not ask Apple for your name or email address. If the sign-in data Apple sends contains an email address all the same, as it can for an account created with a pre-release version of the app, we store that address and the name given then, and Settings → Account shows the addressTo recognise you when you sign in with Apple and show the account in Settings
Sign in with Google (web app)Only if you sign in with Google or add it to your account: the identifier Google gives us for your Google Account, and what Google sends with each Google sign-in: your email address and whether Google has verified it, your name, first name and last name, the web address of your profile picture and, if your Google Account belongs to a Google Workspace or Cloud organisation, its domain; and when Google was added and last used to sign in. At each Google sign-in these details are replaced and no earlier version is kept on the server; copies in backups go on the schedule in section 6. We never download or show the picture. We do not keep the access token Google issues. The iPhone and iPad app never receives any of these detailsTo recognise you when you sign in with Google, to show which Google Account is connected, and to know where we may answer you (section 8)
Sign-in sessionsFor each device or browser you sign in on: a random identifier the app creates for that installation (the web app, for that browser profile), a device label (the text "aireader on iPhone" or "aireader on iPad"; from the web app the browser and system, for example "Safari on Mac" or "Chrome on Windows"), when you signed in, when the session was last used (updated at most once an hour), when it expires and, in the web app, when you last confirmed it's you before changing a sign-in method (cleared when the change is made). We store a one-way hash of the session token, not the tokenTo keep you signed in and to let you sign out of one device or all of them
Folders and subscriptionsFolder names and their order; which feeds you follow, the folder each one is in, any title you gave it, and when you added itThis is your reading list. It syncs to your devices
Reading stateFor each article delivered to you: whether it is read, whether it is in Read later, and when each of those changedSo that read and saved articles are the same on every device
Settings that syncWhether summaries are automatic, the summary language, the daily summary limit, and the language code of your device (for example "en"), which the app sends on its own so that summaries can be written in your languageTo apply your choices on the server
Sync bookkeepingA record of what changed and when, so each device can fetch only what is new; markers for things you deleted; the identifiers and results of changes your device sent; one-time request keys with a fingerprint of the request and the stored replySo that changes made offline are applied exactly once and nothing is lost
SummariesThe summaries generated for you, each with the model and language used, and a counter of how many were generated in the last dayTo show them on your devices and to enforce your daily limit
ChatGPT connectionSee section 4To generate summaries with your own account
Technical logsFor each request: time, address and method, response status and duration, a request identifier and the IP address it came from. Background jobs may log our internal number for your account. Sign-in tokens, one-time sign-in codes and authorization headers are removed before anything is written, and the details Apple and Google send about you are not written to the logsTo find faults and stop abuse

Sign-in methods. An account can have one Apple and one Google sign-in. Where the web app offers Sign in with Google, you can add the second one under Settings → Account → Sign-in methods; either then opens the same account. You can remove either one there, but not the last. Removing a sign-in method deletes its identifier and every detail that came with it from our server at once; copies in backups go on the schedule in section 6, and if a backup is ever restored, the removal is repeated from a record we keep for that purpose.

Information from Google is used only to sign you in, to show which Google Account is connected and to know where we may answer you when you write to us. We do not sell it, use it for advertising, share it with anyone, send it to OpenAI or use it to train AI models. Our use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.

Request limits (for example, how many sign-in attempts an address may make per minute) are counted by IP address in the server's memory and are not written to disk.

Articles are not personal data. Feeds, articles, the extracted text and the images are stored once on the server and shared by everyone who follows the same feed. They say nothing about you. The fact that it is you who follows a feed is part of your subscriptions, above.

Feed addresses. When you add a feed, its address is stored on the server, in a list shared by all accounts. If a feed address contains a private key or token of yours, be aware that it is stored as you entered it. The address stays in that list after you unsubscribe or delete your account; it is then no longer linked to you.

OPML files you import are read to create your subscriptions and are not kept. The list of feeds found in the file is stored with the request key for 30 days.

Discover. The Discover catalog is a list that ships inside the app and is refreshed from our server as one file; the web app fetches the same file when you open Discover. Which sources you look at is not sent anywhere. Adding a source from it is the same as adding its feed by hand.

3. What we do not collect

Your name or email address from Apple, except as described in section 2. Location. Contacts, photos, microphone or camera. Advertising identifiers. Payment details. What you type into search: search runs on your device and never leaves it. Crash reports or usage analytics: the app contains no third-party code at all, and the web app contains none of ours or anyone else's beyond one script from Apple that performs the sign-in (section 7). Apple may show us crash and usage statistics from people who agreed on their device to share them with app developers; they do not identify you.

Our server sets no cookies, and the pages of this website and the web app set none. The web app keeps its sign-in in the browser's own storage, not in a cookie, so it is never sent anywhere by itself.

4. Summaries with your ChatGPT account

This feature is optional, and nothing is sent until you connect an account. The app shows what is described here before you do.

5. What is stored on your device

Signing out erases the database, the downloads, the session token and the Apple account identifier from the device. The installation identifier stays in the Keychain so that the device is recognised if you sign in again. It is a random value that means nothing outside this app, and iOS may keep it even after the app is deleted. Deleting your account from a device removes the database, the downloads and all three Keychain items from that device, the installation identifier included. Your reading, appearance and offline settings stay; they say nothing about the account.

The app reads the clipboard only when you tap "Paste link from clipboard", and writes to it only when you tap a Copy button or, while connecting ChatGPT, "Open sign-in page", which copies the one-time code so that you can paste it on OpenAI's page.

The app can be pointed at a different server under "Advanced" on the sign-in screen. If you do that, this policy does not apply to that server; whoever runs it is responsible for your data there. iOS asks for local-network permission only if the address you enter is on your local network.

In the web app

The web app at https://aireader.news/app/ keeps everything in the storage your browser sets aside for that site, on the computer or device the browser runs on, and nowhere else:

Nothing is kept in a cookie. Apart from signing in with Google and changing sign-in methods, which only the web app offers, no information about you is sent to our server that the app would not send. The web app always connects to aireader.news; it cannot be pointed at another server.

Signing out erases the database, the downloads and the session token from the browser. The installation identifier stays, so that the browser is recognised if you sign in again; it is a random value that means nothing outside the web app. Deleting your account from the web app removes the database, the downloads and the installation identifier as well. The browser's own controls remove the same things: clearing the site's data for aireader.news, or "Clear history and website data", deletes everything the web app stored, and you are signed out of it. Safari also deletes a site's stored data by itself after seven days of Safari use without a visit to the site; the web app says so in Settings → Offline on Safari. The web app asks the browser once, after you sign in, to keep its storage; a browser that does not promise to may remove the downloaded articles when space runs low, and Settings → Offline then says so.

The web app writes to the clipboard only when you tap "Copy code" while connecting ChatGPT, or when you share an article in a browser that has no share sheet and the link is copied instead. It never reads the clipboard. Sharing hands the article's title and address to your device's share sheet when the browser has one.

6. How long we keep it

DataKept for
AccountUntil you delete it. An account is not removed for being unused. The details of a Google sign-in: until you remove Google from the account or delete the account; they are replaced at each Google sign-in
Sign-in sessions180 days after last use. Expired sessions are removed at the next nightly clean-up; a session you signed out of is removed 30 days later
Folders and subscriptionsUntil you change or remove them, or delete the account. When you unsubscribe from a feed, its articles are removed from your account at once, except those in Read later; the subscription record goes once no saved article from it remains
Reading state of articles you have readDeleted 60 days after the article reached your account, unless it is in Read later
Unread articlesMarked read automatically once the article is more than 30 days old, or when one feed has more than 500 unread, then deleted as above
Read laterUntil you remove the article from Read later or delete the account
Markers for deleted items30 days
Records of applied changes and one-time request keys30 days
SummariesAs long as the article's text is kept on our server, which can be longer than the article stays in your list, or until you delete the account. The daily counter: 2 days
ChatGPT connectionUntil you disconnect or delete the account. Unfinished sign-in attempts: 1 day
One-time sign-in codes used with Apple or Google, and Google sign-ins that were started and not finished10 minutes; every value that could be used to sign in is stored only as a hash; deleted at the latest the day after they expire
Technical logsKept in files of limited size and overwritten by newer entries; they are not archived. Entries about a deleted account (IP address, internal account number) are not edited; they go when they are overwritten
Shared articles, text and imagesAn article nobody's account refers to any more is removed about 90 days after it was fetched; its text and images follow within about a week
Shared feed addressesKept. They are not linked to an account once nobody follows them
BackupsThe whole database is backed up daily on the same server. Encrypted copies of the backups are also kept off the server, on storage we hold ourselves in the United Arab Emirates, so that the data survives the loss of the server; no outside storage provider is involved. A backup, and every copy of it, is deleted after at most 35 days, so data you delete leaves the last backup within 35 days. If the database is damaged, a copy of it may be set aside for repair for at most 30 days
Record of deleted accounts180 days. It holds only our internal number of the account and the time it was deleted. If a backup ever has to be restored, the deletions made after that backup are repeated from this record before the service comes back
Record of removed sign-in methods180 days. It holds only our internal number of the account, which method was removed and when. If a backup ever has to be restored, the removals made after that backup are repeated from this record before the service comes back, except one that would leave an account with no way to sign in

A deletion or a removal of a sign-in method made after our last off-site copy of those records can be lost together with the server, and would then have to be made again.

7. Who else is involved

We share personal data with no one for their own purposes. These parties take part in delivering the service:

No advertising networks. No analytics providers. No data brokers. The article text is extracted by software running on our own server, not by an outside service.

We would disclose data if a law that applies to us required it, and would tell you unless the law forbade that.

8. Your choices

If you are in the European Economic Area, the United Kingdom or another place with similar law, you also have the right to object to or restrict processing and to complain to your data protection authority. We process account, subscription and reading data because it is necessary to provide the service you asked for; logs because we have a legitimate interest in keeping the service secure and working; the ChatGPT connection because you asked for it and can withdraw it at any time by disconnecting; and the Google identifier and the details Google sends with it because keeping them is part of how Sign in with Google works in aireader, as this policy says before you choose it (to provide the service you asked for). If you do not want them kept, sign in with Apple instead, remove Google if your account has another sign-in method, or delete your account.

9. Where it is kept, and how it is protected

The service runs on a single server operated by us in the United Arab Emirates. It is not rented cloud hosting. If you use the app from another country, your data is transferred to and stored in the United Arab Emirates. The encrypted backup copies kept off the server (section 6) are in the United Arab Emirates as well.

This is a small service run by one person. No system is perfectly secure. If we learn of a breach that affects your data, we will tell you and the authorities where the law requires it.

10. Children

The service is not directed at children. You must be at least 16 years old to use it. If you believe a child has created an account, write to us and we will delete it.

11. Changes

When this policy changes, the new version is published here with a new date. Earlier versions are available on request. We will not start using your data in a new way without publishing the change first.

12. Contact

Inal Kardanov

[email protected]