This product sets no cookies. Not a first-party one, not a third-party one, not an analytics one. It does store things on your device, because a till that forgot your sales would be useless, and this page names every one of them.
On this page
1. Why there are no cookies
A cookie exists so a server can recognise a returning browser. It is a small value that the browser attaches to every request it sends back to that server.
EDEN Kesef has no server. There is no account, no session, no login and nothing to recognise you to. So the thing a cookie is for does not arise, and none is set. There is also no advertising identifier, no tracking pixel, no fingerprinting script and no third-party tag of any kind, because the policy the app enforces in the browser permits it to load nothing but its own files.
What it does instead is keep your records in the browser’s own storage on your device. Nothing in that storage is transmitted with a request. No other website can read it. It is closer to a notebook in a drawer than to a cookie.
2. Everything the app stores, by name
This is the complete list. If you look in your browser’s developer
tools under storage for edenkesef.app, this is what you will
find, and nothing else.
| Name | Kind | What it holds, and why | How long |
|---|---|---|---|
kesefstore: events |
IndexedDB | Your records. Every event you enter: sales and how they were paid, stock taken in and used, batches and what they produced, losses and their causes, credit given and settled, loyalty stamps, prepaid orders, and the products you have named. Everything the books show is computed from this and from nothing else. It is the product. | Until you delete it |
kesef.device |
Local storage |
A short random identifier the device makes up for itself the first
time the app runs, such as d-3f7a1c94. It exists so
that if you run the till on two of your own phones, each entry
knows which phone made it and the two books can be merged without
colliding. It is not derived from you, from the handset, or from
anything about the phone, and it is never sent anywhere by the app.
|
Until you clear site data |
kesef.cred |
Local storage | The reference to the fingerprint credential, once you have put the books behind your fingerprint. It is the handle the browser needs in order to ask the sensor. It is not a fingerprint and it is not a copy of one: the fingerprint itself never leaves the phone’s own secure hardware and no application can read it. Present only if you have set this up. | Until you clear site data |
kesef-shell-2 |
Cache Storage | A copy of the application’s own files: the page, the stylesheet, the scripts and the icons. This is what makes it open at a stall with no signal. It holds no records and nothing about you, which is precisely why it is allowed to be cached at all. The number on the end changes when the app is updated. | Replaced on update, removed on clearing site data |
One more thing, which is a request rather than a stored item. The app asks the browser to treat its storage as worth keeping, so the records are not quietly discarded when the phone runs short of space. The browser decides, and the books report the answer it gave rather than assuming it said yes.
3. Why there is no consent banner
Consent banners exist because of storage that serves somebody other than the person using the device: measurement, advertising, profiling, or recognising a visitor across sites. None of that exists here.
Everything in the table above is the thing you asked the app to do. The records are the product. The device identifier is what lets your own two phones agree. The credential reference is what puts your books behind your fingerprint. The cached files are what makes it open with no signal. A banner asking whether you consent to the till remembering your sales would be a piece of theatre, and we would rather give you an exact list.
The one thing that genuinely is a choice is sending figures to somebody else. That has a real consent, it is off until you switch it on, it is scoped to one named recipient, it expires, you can revoke it, and every send is logged. It is described on the privacy page.
4. Seeing it and clearing it
In your browser’s settings, find site settings or site data, look up
edenkesef.app, and you can see the storage and delete it. If
you added the app to the home screen, deleting it and clearing its data
does the same.
Clearing it destroys your records, including who owes you money. There is no copy anywhere else and nobody can restore it. Make a backup first if you want to keep the book.
5. This website
These marketing and policy pages set no cookies either, and they store nothing on your device. There is no analytics, no tag manager, no session recorder, no embedded video, no social widget, no webfont and no form.
The pages are plain HTML and one small script whose only job is to let each section rise into view as you scroll. It reads nothing, writes nothing and sends nothing, and if it fails to load the page simply shows everything at once.
A hosting platform can inject a page-view measurement script into a site it serves. The content security policy on these pages permits scripts from this site only, so if one were injected the browser would refuse it before any request left your device. Either way, nothing is measured here and nothing is sent to a measurement service.
The host still has to receive your request in order to answer it, and that request carries your IP address. That is how the web works rather than something we collect, and nothing on this site builds a profile from it or follows you between pages.
EDEN Kesef is owned and operated by EICCIO Advisors. This page describes
how the product works and is written for transparency. It is not legal
advice.
Back to EDEN Kesef ·
Privacy ·
Security ·
Terms of use