Privacy information
This page explains what happens to your information when you visit MAAAT or use its editorial area.
Details we still need to provide
This page is incomplete. It does not yet tell you the full legal name and privacy contact of the organisation responsible for your data, the legal basis for each use, how long your data is kept, which companies provide all services to MAAAT, or whether any data is sent outside the EU. There is no confirmed contact for privacy requests yet. Please do not assume that other contact details on this site reach the person handling those requests.
Visiting the site
When you visit, the services that deliver and protect the site receive your IP address and information about your browser request. MAAAT measures how quickly pages load; those measurements do not include full page addresses or raw IP addresses. This page cannot yet tell you how long hosting and security logs are kept. A cookie remembers your language choice. The current site does not use advertising, visitor profiling, or visitor analytics tools.
Editors and published material
Editors sign in with a passkey. MAAAT keeps the details needed for their accounts and sign-ins, including a record of access events. Published catalogue entries, images, and documents may include people’s names, images, and credits.
External services and links
If you choose “Show on map”, your browser contacts OpenStreetMap, which can receive your IP address and request information. If you follow an external link, your browser contacts that site. The separate catalogue site may set a session cookie when you open it. This page does not yet name all companies that provide hosting, backups, and other services to MAAAT or say where they process data.
Application error reporting
When optional application error reporting is enabled, MAAAT sends a minimized error event to the hosted Bugsink service operated by Bugsink B.V. The application limits the event to a generic error label, first-party application-code frames, a code-location fingerprint, release, environment, and runtime. It does not intentionally include error text, full URLs or query strings, cookies, user fields, form values, breadcrumbs, replay, analytics, or session tracking. The browser still makes an HTTPS request to Bugsink, so the provider and network operators may process transport information such as an IP address. Bugsink says hosted application data is stored and processed in the EU. MAAAT still needs to publish the final legal basis, retention, contact, and processor details.
Your data rights
You can ask to see or correct your personal data. Depending on the situation, you can also ask for it to be deleted, ask MAAAT to limit its use, or object to its use. You can complain to a data protection authority. MAAAT still needs to publish a confirmed contact and instructions for making a privacy request.