Cookie and Local Storage Notice

In short: we do not use tracking cookies

Oatmeal Feed does not use tracking cookies, tracking pixels or advertising identifiers. You will not find a cookie consent banner here, because there are no cookies that require consent.

We do not run advertising, do not profile users and do not pass data to advertising companies.

For the reader to work, we must save technical data on your device: settings, your feed list, articles, and read and saved markers. This uses the browser's local storage — localStorage and IndexedDB — not cookies.

Below we explain exactly what we store, why it is necessary and how to remove it.

What cookies and local storage are

Cookies are small text files written by the browser and attached automatically to requests sent to a server. They are used, among other things, to keep sessions alive and to track users across websites.

Local storage — localStorage and IndexedDB — consists of browser mechanisms that also keep data on your device but do not send it to a server automatically. Data is written there only when an application deliberately stores it.

Oatmeal Feed sets no cookies at all — neither its own nor third-party ones. All application state is kept in localStorage and IndexedDB, which means the data is never attached to network requests automatically.

What we store in localStorage

localStorage holds small key–value pairs and is intended for low-volume data such as preferences.

We use localStorage only for interface settings. In version 1.0 of the application these are:

• the interface language preference (Polish or English) — key oatmeal:lang;
• the light or dark theme — key oatmeal:theme;
• the article list view mode — key oatmeal:view;
• the text size — key oatmeal:fontSize;
• the onboarding state, that is whether the first run has been completed — key oatmeal:onboarding.

Scope and purpose of the localStorage settings

These keys are technical in nature and serve only to restore your preferences on your next visit. They contain no personal data, do not identify you and are not sent to the Controller.

The key names correspond to version 1.0 of the application and may change as the Service develops. We describe changes to the scope of storage in the "Changes" section.

What we store in IndexedDB

IndexedDB is a database built into the browser, intended for larger sets of structured data.

We keep reader library data in the IndexedDB database named oatmeal-feed:

• feeds — the imported RSS and Atom addresses together with metadata such as the title or icon;
• articles — the fetched items with their title, excerpt, author, date and source address;
• read and saved markers — information about the state of each article.

Scope and nature of the IndexedDB data

Library data can be substantial, which is why we keep it in IndexedDB rather than localStorage. Like the settings, it stays only on your device and is not transmitted to the Controller.

This data is technical and necessary for the Service to function. Without it the reader would not remember your feeds or restore your settings after a page refresh.

It is data held on the user's device, accessible to the user and controlled by them. The Controller has no access to it and keeps no copies. It is not used to identify the user, to profile them or to personalise advertising.

Legal basis for storing information on your device

Storing information on a user's terminal equipment is governed by Article 399 of the Polish Act of 12 July 2024 — the Electronic Communications Law (PKE), which replaced Article 173 of the Telecommunications Law on 10 November 2024.

Under Article 399(1) PKE, storing information or accessing information already stored on terminal equipment requires prior, clear, easy-to-understand information and the user's consent.

Consent is not required where storing or accessing the information is necessary to deliver an electronic service requested by the user (Article 399(3)(2) PKE). Saving settings, feeds, articles and markers is necessary to deliver the Service you request by opening the reader. That is why we do not show a consent banner and instead provide this information.

We do not use local storage for purposes going beyond providing the Service — in particular not for advertising, cross-site behavioural measurement or profile building. If that scope were to change, we would ask for consent before starting such processing.

Analytics without cookies

The Service uses no analytics at all — neither cookie-based nor cookieless. We do not measure page views, collect visit statistics or create any visitor identifiers.

The site code contains no third-party analytics or advertising scripts. We embed no tracking pixels, players or third-party widgets.

If analytics were ever to be introduced, it would happen only after this document is updated and, where the law requires it, only with your prior consent. That situation does not currently exist and is not planned for this version of the Service.

That is why you will not see an analytics consent banner on this site: there is no tool requiring such consent.

How to delete local data

You can delete local data yourself, without contacting us.

In each of the browsers below, clearing site data for oatmealfeed.app is enough. Menu paths may differ slightly depending on the browser version.

• Chrome: Settings → Privacy and security → Delete browsing data → scope "Cookies and other site data", or Settings → Privacy and security → Third-party cookies → See all site data → oatmealfeed.app → Delete;
• Safari: Settings → Privacy → Manage Website Data → oatmealfeed.app → Remove. On iOS: Settings → Safari → Advanced → Website Data;
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Manage Data → oatmealfeed.app → Remove;
• Edge: Settings → Cookies and site permissions → Cookies and site data → Manage and delete cookies and site data → oatmealfeed.app → Delete.

Consequences of deleting local data

Clearing site data permanently deletes your feeds, articles, markers and settings. We hold no copies, so we will not be able to restore them.

If you want to keep your feed list, save the addresses elsewhere before clearing the data.

Deleting local data does not affect waitlist data. To remove your e-mail address from the waitlist as well, write to hi@zordonintelligence.pl.

How to block local storage

You can block local storage in your browser — for example by disabling JavaScript for the site, using private browsing or applying a configuration that blocks site data.

The consequence, however, is that you will not be able to use the reader: without localStorage and IndexedDB the application will not remember feeds or settings, and the data will disappear on page refresh.

We do not use mechanisms that circumvent browser settings, such as fingerprinting, which would let us recognise you after you clear your data.

Instructions for blocking site data are available in your browser vendor's documentation.

Changes

We may amend this notice when the storage mechanisms we use, our analytics tools or the applicable law change.

We announce material changes in the Service interface before they take effect.

The date of the last change and the version number appear at the top of this document.

Contact

General contact, data protection and security: hi@zordonintelligence.pl.

Controller: ZORDON INTELLIGENCE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, KRS 0001190915, NIP 7252358503, REGON 542545843.

All contact regarding this notice takes place electronically, using the e-mail addresses listed above.

The rules for processing personal data are set out in the Privacy Policy, and the rules for using the Service in the Terms of Service.