What this site stores, and what it asks you first.

This website

sitereal.app needs no cookies to work. There is no tag manager, no advertising pixel, no A/B testing tool and no session identifier. What it does store is listed below, split by whether it needs your consent.

What your browser keeps is its own cache: the HTML, the stylesheet, the fonts and the images, so that the next page loads without fetching them again. That is the browser’s own housekeeping, it is not readable by us, and clearing your cache removes it.

Strictly necessary, no consent needed

• sitereal.consent (local storage): your answer to the cookie banner and when you gave it, so you are not asked on every page. Kept for six months.
• sitereal_account (cookie): set only if you sign in at account.sitereal.app. It holds the value 1 so the header here can link to your account. Expires when your session ends.

Only with your consent (Statistics)

• _ga (cookie, Google Analytics): tells visits by the same browser apart. Expires after two years.
• _ga_VM86L0QYTH (cookie, Google Analytics): keeps track of the current visit. Expires after two years.

Statistics and your consent

§ 25 (1) TDDDG — the German implementation of the ePrivacy directive — requires consent before information is stored on your device or read from it. It is a rule about the storage, not about cookies as such: local storage, session storage and device fingerprinting are all caught by it.

So statistics wait for you. Until you choose Accept all, or switch Statistics on under Settings, the Google Analytics script is not loaded at all: it sits in the page as inert text, and nothing is sent to Google. Reject all is as easy as Accept all.

What the application stores

The sitereal application is not a website and does not use cookies either. It does keep things on your own computer, because that is what a desktop application is:

• Your projects — pages, styles, media and the project file — in the folder you chose, under your own git repository.
• Application settings and the list of recent projects, in the standard application-data folder for your operating system.
• Thumbnails of your projects, rendered locally so the project manager has a picture to show.
• A cache of the icon sets you installed, inside the project.
• A runtime folder holding the port and process id of the local engine while the application is running.

All of it stays on your machine. None of it is synchronized, uploaded or visible to us. Deleting a project folder deletes its half; the application’s own data lives in the application-data folder and goes when you remove the application.

Other sites, other rules

Following a link off this site takes you somewhere with its own policy. GitHub, in particular, sets cookies and requires them for signing in. What happens after you leave is governed by that operator, not by us.

The full picture of the data this site processes, including Google Analytics, the server log, email and the application’s connections, is in the privacy policy.

The documents

Everything we publish about how this site and this application work.