Privacy
This page says what happens to data when you visit Museum of Ages. In short: you need no account, we set no cookies, and we keep nothing that lets us recognise you on your next visit. We count for ourselves how often pages are opened and some of their buttons and links are used, without recognising you. If you come through one of our free ads on Google, we ask whether we may tell Google that the ad brought you in. Only a yes sends Google anything.
As of 22 October 2026
Who is responsible
Museum of Ages is run by ChipMates gemeinnützige GmbH, Schusterstr. 50, 79098 Freiburg im Breisgau, Germany. You reach us at contact@museumofages.org. The full details are in the legal notice.
We have not appointed a data protection officer, because the law does not require one for us (Art. 37 GDPR and § 38 BDSG, the German Federal Data Protection Act).
When you open a page
To show you a page, your browser asks our host for it. The host's servers then process your IP address, the address of the page, the date and time, and what your browser says about itself, such as which browser it is, its language and the page you came from. Without your IP address no page can reach you. The other details your browser sends along with every request.
Our host is Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. Cloudflare delivers this site for us under a data processing agreement. To protect its own network, Cloudflare also evaluates connection data on its own responsibility, as its privacy policy describes.
The legal basis is Art. 6 (1) (f) GDPR. Our legitimate interest is to deliver the site reliably and to protect it against attacks.
We keep no server logs of our own. Cloudflare keeps the request records it shows us for up to 31 days. For its own logs, Cloudflare's privacy policy names the rules it deletes by and no fixed number of days.
What we can see
Cloudflare shows us totals for the site: how many requests arrived, for which pages, and how much data they moved, about how many different visitors there were, from which countries the requests came, and how many Cloudflare stopped. These totals name no one.
Cloudflare also shows us a sample of single requests from the last 31 days. Each one has its IP address, the address of the page, the country and the name of the browser. The sample holds requests Cloudflare let through as well as those it stopped or checked. We use it to find attacks and faults.
This site shows no advertising and loads no analytics tools, counting pixels or scripts from other companies. What we count ourselves is in the next section.
What we count ourselves
We count how the museum is used ourselves, without cookies and without recognising anyone. When one of the steps below happens, the page sends a short count to an address of this site's own, at the same host, into a datastore of our own. Cloudflare runs it for us, under the data processing agreement. Each count becomes at most one row there. From the count, nothing goes to any other provider. The page does not read what the server answers.
In the wing there are six steps. The arrival: a wing is opened. The welcome: you move on from the wing's opening card and the walk begins. A stop: you reach one. A close look: you look closer at a work. The use: a visit was more than a glance, that is, you reach the second stop or open the first close look. A skip: you skip the walk to a stop and arrive there at once. Each row holds which wing it was, which language the wing is showing, and how the screen stood: upright, sideways or wide. A stop adds its number (1 to 17), a skip adds the number of the walk it skipped (0 to 16, where 0 is the walk to the first stop), and a close look adds the kind of work: painting, machine, sheet, book, film or place, never which work. The arrival, the use and stop 3 also carry the source word that the next section explains.
On the site's pages there are three steps: a page is opened. The middle of its text comes into view. A link into the wing is pressed. Each row holds which page it is, from a fixed list (the home page, the page on Leonardo, the inventions, "What this museum is", privacy, the legal notice, and each page that is added), and which language the page is showing. Opening adds whether the visit began on this page, and if so, the source word. So does the middle of the text coming into view. The link adds where it stood on the page: at the top, at an entry or at the end.
Where a page asks the question for visitors from our ads, two more things are steps: that the card was on screen, at least half of it for one second, and the answer to it, which is yes, no or closing the card. Closing works like a no and is counted as its own word. Each of these steps carries the page and its language and nothing else. None carries the click number. Unlike the other rows, they get no country and no device class from the server.
On the pages about animals, two more things are steps: you open the answer to a guess with "Show the answer", or you follow the link to the page of an open wing. Each of these steps carries the page and its language. As on opening, each adds whether the visit began on this page, and if so, the source word. They carry nothing more: like the steps of the question for visitors from our ads, they get no country and no device class from the server.
To every other row the server adds two details: the country as a two-letter code that Cloudflare derives from the connection, and a device class, phone, tablet or desktop, worked out from what your browser says about itself. It keeps neither your IP address nor what your browser said. The moment a row was written is stamped by the datastore itself.
Each step counts at most once per page load: a wing once, its welcome once, each stop once, each skipped walk once, each work once, a page once, an answer once. The page remembers this only while it is open and writes nothing to your browser for it. If you reload it, it counts again. No row carries an identifier or an IP address. We do not join rows with each other or with other data, and we only read totals. If a detail is not on its fixed list, that detail or the whole row is dropped. The datastore deletes the rows by itself after three months. Totals we make from them hold no single row.
For the counting, nothing is stored on your device and nothing stored there is read. The one exception is a mark meant for our own test browsers, described under "Cookies and storage in your browser". That is why we do not ask for consent for the counting (§ 25 TDDDG, the German law on data protection in digital services). The legal basis is Art. 6 (1) (f) GDPR. Our legitimate interest is to know whether the museum is used and whom it reaches.
Where a visit came from
When a visit begins, the count notes in one coarse word what kind of place it came from. The word comes from a fixed list of sixteen, and all visits of the same kind get the same word: "direct" (no linking page), "search" (a search engine), "ad through Google's program for nonprofits", "paid ad", "paid ad in a forum", "forum", "code platform", "educational institution", "wiki", "news site", "e-mail", "award" (the site of a prize or a gallery), "AI assistant", "social network or messenger", "other website" (any other linking site) and "reload" (the page you came from is the wing itself, as when the wing reloads itself). On the page where the visit began, the word sits on the rows for opening and for the middle of the text, and on the pages about animals also on those for "Show the answer" and for the link "To the Leonardo wing". In the wing it sits on the rows for the arrival, the use and stop 3. The word "reload" sits on these three rows only. Only that word is kept.
It is worked out once, when the visit begins, in this order:
- Links we place ourselves, for example in an ad or under a post of our own in a forum, have an address of their own on this site. That is how the count knows an ad or a post brought the visit.
- If you go from one of our pages into the wing, and the visit began on that page, the page passes its word along with the link, at the end of the address after the hash sign. The wing reads it once and stores nothing.
- For every other visit, the word is worked out as the page is delivered, on the server, from the detail of which page you came from. Your browser sends that with its request by itself, as described above under "When you open a page". The page reaches you with that one word. No script looks up in your browser where you came from. If the detail is missing, the word is "direct". If you come from another page of this site, the visit did not begin here, and the rows get no word. If the page you come from is the page you open, at the same address up to its question mark, the word is "reload". In the wing it sits on the three rows named above. Every other page counts such a visit as one from this site, and its rows get no word.
For the counting, we never read, store or send what stands after the question mark of an address, the part where services attach extras to a link. The exceptions are the extra probe=1 for our test browsers and the language the wing takes from its own address. If an ad platform attaches a click number to its link, the count never takes it in. The count keeps no full address of the linking page, no name of its host and no search words. The one part of the site that reads a click number is the question for visitors from our ads, in the next section.
If you come from one of our ads
We run free ads on Google through its program for nonprofits, Google Ad Grants. If you click one of them, Google adds a click number to the address of our page (gclid). Google can link this number to your click and possibly to your Google account, so we treat it as personal data.
Only then, and only on the page you arrive at, a card at the foot of the screen asks one question: "May we tell Google that our ad brought you here?" That means telling Google that your click on our ad led to a visit. Google shows our ads more often when it sees that they lead to visits. The card never comes as the page opens. It waits until you have scrolled to the middle of the page's text or the page has been in view for 45 seconds in all, whichever comes first. If you click or tap a link into the museum before then, it does not come at all. We ask no one else. Visitors from our paid ads or from a forum are never asked, and our pages never read their click number. The overview page of the animals asks no one either. It never reads the click number, so it does not take it out of the address bar either. A browser that sends the Global Privacy Control signal is never asked either, and nothing is sent for it. The question is meant for people aged 16 or older. With a yes, you confirm that you are. If you are younger, please say no, and nothing is sent. We do not run the ads that lead to our pages about animals on searches for children's content, and we have asked Google not to show them to accounts it recognises as a child's. We cannot rule out that a child still sees one, which is why we ask the above.
Until you answer, the click number stays in the page's memory only. The page takes it out of the address bar at once, so it is not shared or bookmarked with the address. Like every address, the one you arrive at, click number included, is in the host's request records described under "When you open a page". If you say no or close the card, nothing is stored and the click number is sent nowhere. We do not remember your answer: a new click on one of our ads asks again. Before you answer, we use the click number only to decide whether to ask and to take it out of the address bar. The legal basis is our legitimate interest in asking you and in keeping the number out of addresses you share (Art. 6 (1) (f) GDPR).
If you say yes, the page sends our server, right away and once, the click number, the time of your yes, and that it is a visit. On the pages about animals, from which no wing can be entered yet, that is all: we store nothing in your browser. On every other page your browser also keeps two things for this tab only (sessionStorage): the click number and the time of your yes. No cookie, and nothing that outlasts the tab. When you then enter the museum and a wing opens, the wing sends both to our server, together with the name of the wing, and deletes them from the tab. So one click counts at most twice: once as a visit at your yes, and once as a visit inside the museum when a wing opens. A kept yes older than six hours is deleted and not sent.
Each time, our server sends Google, through the Google Ads API: the click number, the kind of event (a visit, or a visit inside the museum), the time, an order number made from the click number and the kind of event or the wing, so that the same click never counts twice for the same event, and a consent signal (use for measuring the ad allowed, use for personalised advertising not allowed). Nothing else about you goes to Google: not your IP address, not your country or device, not the pages you read. Our server keeps none of it and writes no click number into any record. No script and no pixel of Google runs on our pages.
Our own count notes only that the card was on screen and your answer as a word (yes, no or close), as described under "What we count ourselves". It never holds the click number.
Recipient: Google Ireland Limited and Google LLC (USA). Google then uses the click number as a controller in its own right. You can also exercise your rights over what Google received with Google. A transfer to the USA can take place. Google is certified under the EU-US Data Privacy Framework. How Google uses data from partner sites: business.safety.google/privacy.
How long: in your browser, until you close the tab or until the entry is sent, then it is deleted. A yes on a page about animals keeps nothing in your browser. On our server, not at all. Like every address, the one you arrive at stays in the host's request records for up to 31 days, also after a no. At Google, under Google's own rules for advertising data.
The legal basis is your consent (Art. 6 (1) (a) GDPR), and for reading the click number to send your yes, for keeping it in your tab and for reading it when a wing opens, also § 25 (1) TDDDG. Saying no costs you nothing: the museum is open either way.
Your yes goes to our server and on to Google as a visit right away. What stays in your tab for entering the museum, you can take back at any time before you enter: with the button the card shows right after your yes, with the button below, or by closing the tab. The button below works in the tab where you said yes. Taking it back deletes the entry, and nothing more is sent. You can also withdraw a yes given on a page about animals at any time. There, though, it has already sent everything. Nothing is left in your browser, and with us only the host's request records described above. Once a wing has opened, the entry has been sent and deleted, and nothing more is ever sent for that click. Taking a yes back does not touch what was sent lawfully before (Art. 7 (3) GDPR).
Cookies and storage in your browser
We set no cookies. The pages of this site store nothing in your browser, with two exceptions in the list below: a mark meant for our own test browsers, and, only after a yes to the question for visitors from our ads on a page from which you can enter the museum, one entry for the open tab. One case is the host's: if Cloudflare's protection checks your browser before it lets a request through, Cloudflare sets a cookie named cf_clearance so that it does not check you again at once. The cookie serves only that.
The wing you walk through keeps a few short notes in your browser's storage so that it works the way you left it. To these come the mark of our test browsers and the entry after a yes:
- Your sound setting, on or off, and your walking pace if you chose one.
- Your language, if you chose one in the wing.
- A mark that your device gets one scene as a film. It is set once if the device is too slow for the live scene.
- For the open tab only: that the opening and two hints have already been shown, which of the walk's tips have already come up, and a time mark if the wing had to reload once after a graphics error.
- For the open tab only: which works you opened, which stops you reached and on which day, so the wing can show them to you in a list and leaves out the tip on close looks once you have opened one. The list is never sent anywhere.
- A mark meant only for our own test browsers. It is set when an address of this site is opened with the extra ?probe=1. The count reads only this one mark from storage and notes on its rows that it is there, so that we can take our own visits out. If you set it yourself, we take your visits out like ours.
- Only after a yes to the question for visitors from our ads on a page from which you can enter the museum, and only for the open tab: the click number of the ad and the time of your yes. When a wing opens, it takes the entry out of the tab and sends it once. Closing the tab deletes it too.
These notes stay on your device until you clear them. The notes for the open tab go when you close it. None of the wing's own notes is sent to us or to anyone else. The entry after a yes is the one note that leaves your device: once, to our server and on to Google, as described under "If you come from one of our ads". Of the test browsers' mark, only that it is there is noted. You remove all of it by clearing this site's data in your browser.
We do not ask for consent for the wing's notes, because they are needed for a function you use (§ 25 (2) no. 2 TDDDG). The same rule covers the host's cookie: without it a checked browser would be checked again on every page. The test browsers' mark is meant only for our own devices. On yours the count finds nothing, unless you set it yourself. The entry after a yes is kept only with your consent (§ 25 (1) TDDDG).
Nothing from other companies
Fonts, pictures, films and scripts come from this site and from our own storage at the same host. The pages load no fonts, maps, videos or buttons from other companies.
Links to other websites
Some pages link to other websites, for example to the museums, libraries and collections that hold the originals, and to our source code. When you follow such a link, you leave this site and the other site's rules apply.
When you write to us or call us
If you send us an e-mail or call us, we use your address or number and what you tell us to answer you. The legal basis is Art. 6 (1) (f) GDPR, our legitimate interest in answering. Our e-mail runs with a mail provider in Switzerland that handles it on our behalf. The European Commission has recognised Switzerland as a country with adequate data protection. We delete the exchange when the matter is closed, unless the law obliges us to keep it longer.
Data outside the European Union
Cloudflare is a company in the USA and answers requests from servers around the world, as a rule from one near you. For transfers to the USA, Cloudflare is certified under the EU-US Data Privacy Framework, which the European Commission recognised as adequate protection on 10 July 2023. Our agreement with Cloudflare also contains the EU's standard contractual clauses, for any transfer the framework does not cover. The agreement is public: Cloudflare's data processing addendum.
After a yes to the question for visitors from our ads, the click number goes from our server to Google and may reach the USA on the way. Google is certified under the EU-US Data Privacy Framework, as described under "If you come from one of our ads".
Your rights
Under the GDPR you have the right to learn which data about you we process (Art. 15), to have wrong data corrected (Art. 16), to have data erased (Art. 17), to have its processing restricted (Art. 18) and, where the law grants it, to receive data you gave us in a common format (Art. 20).
Where we rely on your consent, you can withdraw it at any time with effect for the future (Art. 7 (3)). How to take back a yes to the question for visitors from our ads is described under "If you come from one of our ads".
You can also complain to a data protection authority (Art. 77). The one responsible for us is the Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, Heilbronner Straße 35, 70191 Stuttgart, www.baden-wuerttemberg.datenschutz.de.
To be plain about it: we hold almost nothing that we could look up for you. There are no accounts, the wing's notes are on your device, not with us, and the count carries no identifier by which we could find your rows. After a yes, the click number of our ad passes through our server to Google and is not kept.
We make no automated decisions about you and build no profiles.
Your right to object
You can object at any time, for reasons that arise from your particular situation, to processing that rests on our legitimate interest (Art. 21 GDPR). Write to the address at the top of this page.
You can also object to the count without writing to us: if your browser sends the Global Privacy Control signal, the count writes no row for it. Some browsers send it on their own, others let you turn it on in their settings or with an extension. Even then the page sends its count, but the server drops it. The same signal keeps the question for visitors from our ads away: it is never asked, and nothing is sent to Google.
When this page changes
This page describes the site as it is today. If something changes, this page is changed first.