Privacy Policy

Unfinished, and it says so rather than pretending otherwise. The sections below describing what this site stores are accurate and complete — they are derived from what the code actually does. The controller is named below. Two things are still missing and only the operator has them: the hosting provider, and how long that provider keeps its server logs. Until those are filled in and the whole page is reviewed by a lawyer, this is not a finished privacy policy (GDPR / ePrivacy), and this site should not be operated commercially.

The short version (intended setup)

This website sets no cookies for visitors and uses no third-party trackers.
All fonts, scripts and styles are self-hosted — no third-party CDNs receive your IP address when the page loads.
First-party, anonymous usage statistics: each page load sends the page path, referrer domain, language, screen-width bucket and coarse browser/OS class to this site's own server. The visitor identifier is a truncated SHA-256 hash of IP address, browser signature and a salt that rotates daily — raw IP addresses and user-agent strings are never stored, and identities cannot be linked across days. Legal basis: legitimate interest (Art. 6(1)(f) GDPR) in privacy-preserving reach measurement (to be confirmed in legal review).
The hosting provider processes IP addresses in server logs for security and delivery (provider name, log retention period and legal basis — Art. 6(1)(f) GDPR — to be inserted).

What this site keeps in your own browser

Several things here remember what you did — the saved list, the learning record, your notes, the theme switch, and an offline copy of the whole site if you ask for one. All of it lives in your browser and none of it is ever sent anywhere. There is no account, no server-side profile and no copy elsewhere: clearing your browser data for this site erases every item below and there is nothing to restore it from. That is the design, not a gap.

Storing something on your device needs your consent unless it is strictly necessary for a function you asked for (§ 25 TDDDG, ePrivacy). Everything listed here is written only after you press a button, answer a question, write a note or change a setting — which is why the offline copy in particular is opt-in and says so before it stores a byte, and why nothing at all is written on a first visit to a page you only read.

Stored as	What it holds	Written when
`sy-saved`	The instruments you saved: slug, name, asset class, when.	You press Save on a product page.
`sy-learned`	The instruments you marked as learned.	You press Mark as learned.
`sy-notes`	The notes you wrote, keyed by the page you wrote them on.	You type in a note box.
`sy-cards`	The flashcard schedule: which box each card is in and when it is next due.	You grade a card.
`sy-answers`	Per question, how often you got it right and wrong, and the question's first 160 characters.	You check a quiz or an exam.
`sy-calib`	Three counts of right-and-total, one per confidence level.	You rate your confidence before checking.
`sy-quiz-…`	Which answers you selected in one category's quiz, so a reload does not lose them.	You answer a category quiz.
`sy-exam-best`	One number: your best exam score on this device.	You grade an exam.
`sy-ktest`	Which subject areas and which round length you last selected on test your knowledge, so the picker comes back as you left it.	You choose areas and start a round.
`sy-round`	Where you got to in the mock product round: which questions have been dealt and which you have already turned over.	You start a mock round.
`sy-path`	Which pages you ticked off on a reading path — the addresses only. The path itself is in the link and is never stored here.	You tick an item on a path.
`sy-theme`	Light or dark, when you have chosen explicitly rather than following your system.	You press the theme switch.
`sy-simple`, `sy-plain-only`	Whether you asked for the simpler wording, and whether the atlas shows only the plainest instruments.	You turn either on.
`sy-atlas-open`	Which asset classes you left open on the front page.	You open one.
Cache storage `sy-…`	A complete copy of this site — every page, the calculators and the search index — so it opens with no connection.	Only when you press Store the site on this device on the saved page.

How to remove it. The offline copy has its own Remove the stored copy button, which also removes the service worker that serves it. The learning record has Forget everything on this device. Everything else goes when you clear this site's data in your browser. None of it is readable by us at any point, because none of it leaves your device.

The announcements page, and the one request that leaves this server

Your browser never talks to another host, on this page or any other. That has always been true here and it still is: every script, font and image is served from this domain, and there is no analytics provider, no advertising network, no font CDN and no embedded video.

The announcements page at /news is the one place where this server makes an outbound request. It fetches a fixed list of central bank and regulator press feeds — the ECB, the Bundesbank, the BIS, the Federal Reserve, the SEC, ESMA, the EBA and the Bank of England — caches the result on disk, and serves it to you from here.

It runs on its own clock, not on yours. The fetch happens at most every thirty minutes and is shared by everybody; it is not triggered by your visit. Those institutions therefore learn nothing about you: not your address, not your browser, not that you looked.
Nothing about you is sent. The request carries only this site's own identifier. There is no visitor data in it because there is none to send.
Nothing is stored on your device by that page. The list is fetched and rendered; no key is written.
Following a link is your choice. The headlines link to the source. If you click one you are visiting that institution's site under its own privacy terms, exactly as if you had typed the address.

If you pay for Pro

Nothing on this site currently takes payment, so nothing in this section is happening today. It is written now rather than later because the code for it is in place and switched off, and a privacy policy that falls behind the code is the one failure this page has already had once. What follows describes exactly what would happen the day the switch is turned.

There is no account, no password and no profile. Paying works through a licence key, and the architecture is the privacy promise rather than a paragraph about it:

The payment happens at Stripe, on Stripe's own pages. Card details, name and billing address are collected and held by Stripe as processor under its own terms. None of them ever reaches this server.
This server stores one record per licence, and only these fields: a SHA-256 hash of the licence key (never the key), whether it is active, the date the paid period ends, the Stripe customer id, and how many seats it covers. No e-mail address, no name, no address, no card data, no IP address. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).
The licence key lives in your browser under sy-licence, with the last verification result under sy-licence-ok so the site keeps working offline for about a day. Both are written only after you paste a key, and both are removed by Forget everything on this device.
Your learning record is still never uploaded. Pro adds the button that hands it to you; it does not send it anywhere. There is no server-side copy of what you have read, answered or saved, before or after paying.
Invoices, cancellation and card changes happen in Stripe's own customer portal. Stripe's privacy notice governs that relationship, and Stripe is where a request about your billing data belongs.
Erasure: because the row holds no identifier of you, deleting it means deleting a hash and a customer id. Ask via the contact in the legal notice, and ask Stripe separately for the data it holds as processor.

The point of storing a hash rather than the key is worth stating plainly: somebody who obtained this server's licence file could not unlock anything with it, and could not learn a single subscriber's name from it either.

If advertising is enabled

Should third-party advertising (e.g. Google AdSense) be activated, this policy must be extended before activation: consent management (a consent banner meeting TCF requirements), the ad provider's data processing, cookie details, and opt-out mechanisms. Advertising is not active until this section is completed.

Your rights

Under the GDPR you have rights of access, rectification, erasure, restriction, portability and objection, and the right to lodge a complaint with a supervisory authority. Requests: see the contact details in the legal notice.

Controller

DELISORIA GbR
c/o Smarvo 295
Südstraße 31
47475 Kamp-Lintfort
Germany
E-mail: contact@delisoria.com

Requests to exercise any of the rights above can be sent to that address. The legal notice carries the same details.