← Back to SchlenderlischlenderliPrivacy policy
EN ▾

Privacy policy

Contents

Translation for information. The German version is legally binding. German version

Language settings

The NEXT_LOCALE cookie remembers your explicitly chosen language on this device for one year. It applies only to this website and contains no identity. It is set when you choose a language, visit a /de address or sign in; for signed-in members, it is aligned with the saved Member Language. A language in the URL alone does not change the setting. The Member Language is stored in your account and included in the data export. Storage serves your requested language choice under § 25(2) no. 2 TDDDG; the legal basis is Art. 6(1)(b) or (f) GDPR.

Organiser contacts and letters

We store voluntarily supplied organiser contacts, conversation notes and confirmed public business addresses to handle specific enquiries and invite organisers to use our free correction service. The legal bases are Art. 6(1)(b) and (f) GDPR. We do not automatically research individuals or share these contact details.

Contacts are deleted twelve months after the last actual contact. Retention may be extended only for a specific open case with a documented review date. Enquiries, postal addresses and free-text notes are deleted after twelve months at the latest. A minimal, cryptographically derived suppression identifier is retained solely to respect an objection.

You may object to being contacted at any time, particularly to further letters. Use the form in the letter or write to impressum@schlenderli.de. You may also request access, rectification and erasure there. These contacts are not covered by the exception for publicly collected event data.

Manager access, submissions and usage analysis

For Manager access, we store the verified email address, approved scope, organisation represented, stated role, permissions and acceptance of the terms, including their wording and the time of acceptance. Changes, submissions, review decisions, correction requests, measures and objections are stored with their processing history. This provides access and makes decisions traceable. The legal basis is Art. 6(1)(b) GDPR.

Images you upload are kept in object storage and served after approval. We also store the rights declaration and review status. Text and images may be checked automatically using AI; objections are handled by a person. The recipients listed below for publicly available event data apply to this processing. Website jobs store the URL, requester, permission, timestamps, status and events found. We send acceptance and termination confirmations through Brevo, transmitting the email address, scope and contract version, or the reason and time of termination.

Ending Manager access does not delete the member account. When an account is deleted, final deletion is scheduled after 30 days; permissions and acceptances are deleted then. Historical website jobs and review and action logs may be retained without their member association. There is currently no fixed automatic deletion period for these records. Approved images remain stored until removed. Technical deletion is requested for rejected, removed or blocked images; where there is a documented open dispute, the stored image is retained until it is resolved. Confirmation emails are deleted from our delivery history with the associated permission.

To improve the Manager area, we analyse activation, changes, uploads, website jobs and processing times. Reports show aggregate values for seven and 30 days; administrator usage is reported separately. Page views are counted by day and access type, without a member or event identifier. This analysis is based on our legitimate interest in a usable service under Art. 6(1)(f) GDPR. No external analytics services are integrated.

AI assistants and public interfaces

The public MCP and Agent API answer anonymous queries of public event data without sign-in. They process search arguments and an IP-derived key; the address may be shared by many users of an assistant provider. No account or OAuth grant is created, and your profile, home location and selected interests are not read. The requesting assistant receives the public facts; its privacy rules govern further processing. Older Assistant Connections, if any, remain included in data export and end on account deletion. New connections are not currently offered.

For the Agent API and MCP, we store request ID, call time, transport, operation, result and error code, HTTP and cache status, all validated search arguments including search text and search coordinates, short cursor digests, result IDs and count, duration, response size, a pseudonymous caller key, session assignment and unverified origin fields (client identifier, User-Agent, Origin host and protocol version). An assistant may pass text entered by a user as search text. The caller key is derived from the IP address (an IPv6 /64 network) and client identifier using a secret replaced every 90 days; the IP address itself is not stored. Sessions group calls and are heuristic without a supplied MCP session identifier; they prove neither one person nor one chat. The purpose is operating and improving the service and measuring how assistants use it. Retention is 90 days; queue and daily limits or failures may leave entries missing. Sec-GPC: 1 or DNT: 1 prevents an entry. You can object via the privacy contact named above and in the legal notice. For load limiting, IP keys remain temporarily in memory: after ten idle minutes they become eligible for eviction on later requests; a process restart removes all entries. The hosting recipient is Hetzner in Germany. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in operating, protecting and improving the service). Public browser search retains its separate daily-key rule described below.

Event images and image reports

We do not store automatically discovered event images. When requested, they are temporarily transferred through our server from the publicly accessible original source so that your IP address does not reach the image provider. To report an image or event content, write to impressum@schlenderli.de and include the event ID, the image concerned, your contact details and the reason for the report. We handle justified notices promptly, usually within 24 hours.

1. Controller

Adrian Mehmke
c/o IP-Management #11202
Ludwig-Erhard-Str. 18
20459 Hamburg
Email: impressum@schlenderli.de

2. Membership and login

Public event search can be used without signing in. If you voluntarily sign in as a member using Google, we store your verified email address and Google account identifier. We use these data to sign you in and provide your membership. The legal basis is Art. 6(1)(b) GDPR. Google receives the login data. Further information is available in Google's privacy policy.

Alternatively, you can request a login link by email. Only after your confirmation is a member account created or linked to an existing account with the same verified address. We use Brevo for delivery, transmitting your email address and login link. The link is valid for 30 minutes and can be used once. Login requests, including address, timestamps and a daily rotating salted hash of the IP address, are stored for seven days to prevent abuse and diagnose errors. The IP address is not stored in plain text. The legal basis is Art. 6(1)(b) GDPR for login and (f) for protection against abuse.

Filter settings on your device

We set the cookie only when you actively select a city or filter: schlenderli_filters. It contains your chosen city, radius, price, time, date range and companion-map setting, but no identifier. The topic is not saved for later visits. Its sole purpose is to remember these settings for your next visit; it is stored for one year and is not used for tracking. Storage is necessary for the convenience feature you requested under § 25(2) no. 2 TDDDG; a further legal basis is Art. 6(1)(f) GDPR. No consent banner is therefore required for this.

3. Required session cookie

For signed-in members, we set the cookie schlenderli_session. It is technically necessary to keep you signed in and identify your session. The cookie is not set for advertising or analytics. The existing session may be used on the server to associate the activity data described in section 7. The legal basis is Art. 6(1)(b) GDPR. As no unnecessary information is stored on or read from your device, no consent banner is displayed.

Interest discovery for members

When you discover interests as a member using free text, that text is sent for semantic analysis to Jina AI GmbH, Berlin, as a processor. Processing may take place on infrastructure in the USA. The transfer is based on the EU-US Data Privacy Framework or standard contractual clauses. Jina does not store the free text or use it for training.

5. Approximate city using GeoIP

To suggest a suitable city on your first visit, your IP address is compared on the server with a self-hosted GeoIP database. The IP address is not stored for this purpose. The legal basis is our legitimate interest in a helpful location suggestion under Art. 6(1)(f) GDPR.

6. Self-hosted maps

Map tiles are loaded from our own service at tiles.schlenderli.de . No third-party map CDN is integrated for this purpose.

7. Searches, event clicks, page views and the Eventtinder trial

When you search, we store the search term, city, radius, date range and result count on the server. For event clicks we store the event, click type and surface; active filters apply only on Map and List. Source links on Event Pages immediately redirect through Schlenderli to the stored original source. A source opening proves neither arrival at the provider nor attendance. This helps us improve event search. The legal basis is our legitimate interest under Art. 6(1)(f) GDPR.

When you visit an event or city page, we record a page view with the event or city and date range, plus a broad referral category (ChatGPT, Google, Bing, Perplexity, internal, other or none). We do not store the full referrer URL. This helps us assess whether publicly discoverable fact pages help people find events. These records follow the same objection, export and deletion rules as searches and are retained for no more than 365 days. Prefetches do not count as page views.

All requests to the Browse server at schlenderli.de, including bots, prefetches, files and error pages, also contribute to daily totals by URL class, unverified browser/bot category, request type and response status. We store no IP address, full paths, query parameters, referrers or identities for this. Browser-like does not mean human. GPC, DNT and the activity setting also apply to bots; invalid or unresolvable credentials prevent counting. The legal basis is Art. 6(1)(f) GDPR.

Historical bot and crawler totals are retained for no more than 90 days. Daily totals and collection diagnostics are retained for 90 UTC days. Broad monthly totals are retained for 36 months including the current month: website requests by URL class, user-agent category, request type and status class; edge operational counters by router and status class; completed and empty search requests excluding internal usage; search breakdowns only by price, date range, device class and presence of a topic; page views only by page type, without event, city or referral source. Small search breakdowns with fewer than ten requests are grouped into other; if there would be only one value, the next smallest is included. An existing other value counts towards this. This reduces disclosure but does not guarantee anonymity. Collection is best effort and may have gaps.

Traefik separately counts operational metrics by router and response status, including map tiles, HTTP redirects and requests rejected at the edge. These counters contain no identity, path or browser identifier; GPC, DNT and member settings cannot be applied there. They are never added to the Browse figures.

For members, these records are associated with the member account and deleted when the account is deleted. You can turn off storage at any time under Activity data in your profile. GPC and DNT suppress Search, event-click, public Event/City Page View and Eventtinder trial analytics even for signed-in members. Present but unresolved session credentials produce neither activity records nor an anonymous substitute. Explicitly saved interests and functional Eventtinder state, including URL replay, remain independent; separately disclosed Manager processing is unaffected.

Without a session cookie, we use only a daily rotating pseudonymous key derived from the IP address and browser identifier. The random daily secret required for this is irreversibly replaced at the UTC day boundary; the IP address and browser identifier are not stored. Records from different days therefore cannot be linked. GPC and DNT prevent this analytics collection, but do not prevent all functional storage.

We also count completed map and list result requests in daily UTC totals: surface, empty result, estimated device class (mobile, desktop or unknown) and broad filter context (city, interests, price, time window and whether a topic is set). We analyse these separate breakdowns to improve search; they do not form complete search profiles. We estimate device class from browser information already received, without requesting new information. These totals are deleted after 90 days. The objection options described above also apply to this collection. Content-free technical counters and a heartbeat indicate whether collection works; they contain no IP address, browser identifier, search terms or user identifiers and are also retained for 90 days.

All searches and event clicks are automatically deleted after no more than 12 months. Earlier deletion with a member account is unaffected.

In the unlisted Eventtinder trial, we investigate whether a short selection leads to useful activity suggestions. We record confirmed day and hour ranges, radius, price preference and broad location source, plus optional mood answers solely for evaluation. For the time window, we store selection type, a bounded day offset from 0 to 29, whole hours, the matching time-window preset and whether today's query start was limited to now; no absolute visit date or effective start/end timestamps. The UI version also groups trial starts before a selection is confirmed. An unanswered optional question is recorded as unanswered only on confirmation. It does not affect suggestions. We also record visible cards, reactions, visible time capped at 300 seconds, result displays and deliberate clicks to the provider's website. A click does not prove booking or attendance; missing signals do not prove abandonment.

A random trial identifier remains in page memory, is sent only in the request body and is replaced without linkage at the UTC day boundary. There are no additional cookies or persistent browser storage. Answers and learned preferences are lost on reload. Pseudonymous measurement data are retained for no more than 30 days. For members, they are included in the data export and also deleted on account deletion. GPC and DNT prevent detailed collection even for signed-in members; the activity setting in the profile also applies. Content-free technical counters are retained for 90 days.

An explicitly submitted address is processed by our self-hosted Photon service. No new geocoding recipient is added. The address and starting coordinates remain in request processing and page memory; they are stored neither in measurements nor in logs. External providers receive a normal browser request only when deliberately opened, without added trial identifiers. The basis is Art. 6(1)(f) GDPR, with limited collection, objection options and short retention. We do not infer sensitive personal characteristics from reactions or mood answers. The TDDDG assessment also considers processing without persistent storage on the device.

Processing publicly available event data

We collect information about events and venues from publicly accessible websites. This may include third-party personal data, such as organiser and artist names or business contact details. We process these data to operate event search on the basis of our legitimate interest under Art. 6(1)(f) GDPR.

Recipients and processors are Anthropic PBC in the USA (transfer based on the EU-US Data Privacy Framework and standard contractual clauses), Jina AI GmbH and Hetzner. We store the data while the relevant event is displayed or for the operating lifetime of the service.

Data subjects have, in particular, the rights listed in section 10, including the right to object. Individual notification would be disproportionate given the large number of publicly available sources and people concerned; we therefore provide this information in this privacy policy under Art. 14(5)(b) GDPR.

8. Hosting

This website is hosted by Hetzner in Germany. Hetzner processes data on our behalf as a processor.

9. No external analytics or advertising services

We do not use third-party analytics or advertising services or share activity data with such services. We use no advertising networks or embedded external scripts.

10. Your rights

Subject to the legal requirements, you have the rights of access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR), data portability (Art. 20 GDPR) and objection (Art. 21 GDPR). You may withdraw consent at any time with effect for the future.

You also have the right to complain to a data protection supervisory authority.