Privacy Policy
Last updated: 3 October 2026
1. Data controller
Nicolas Janos Pashalisc/o GartenLand Schneider
Hasselsstraße 91
40599 Düsseldorf
Germany
Email: contact@dokkanapi.com
2. Technical request data and server logs
When the website is requested, DokkanAPI and technical service providers involved in operating the server may process the IP address, date and time, requested URL, referrer, browser and device information, transferred data volume, and HTTP status. This processing is necessary to deliver the website, maintain security, diagnose failures, and prevent abuse.
The legal basis is Article 6(1)(f) GDPR. The legitimate interests are reliable delivery, IT security, troubleshooting, and abuse prevention. Operational server logs are normally retained for up to 15 days, unless a security incident or legal obligation requires longer storage.
3. Local browser storage
DokkanAPI stores the selected Performance Mode preference, the interface-language preference, and locally saved Team Builder state in your browser. Performance Mode and Team Builder data remain in local browser storage and are not transmitted to DokkanAPI merely because they are stored. The interface language is stored in a host-only functional cookie containing only en or de. That cookie is created only after you actively select a language flag and is sent with requests to DokkanAPI so that language-neutral team links can open in the language you last used; no server-side language profile is created.
This storage is used only to provide functionality requested by the user. No advertising or cross-site tracking purpose is attached to it. The language preference is replaced when you choose another language and otherwise expires after six months. You can remove it directly from the language menu. The other values can be removed through the corresponding reset controls or your browser settings.
4. Website usage statistics
DokkanAPI counts filtered, successful page requests on its own server to understand which website areas are used and to improve its content and operation. These statistics use only information already contained in ordinary requests needed to serve the website, including requests made when navigating between pages. DokkanAPI does not count unique visitors or sessions and does not measure visit duration.
Only aggregate counters by UTC hour and day are retained. Requests are grouped by allowed public page paths, referrer categories or source hostnames, browser families, operating-system families and device classes. These categories are counted separately, rather than combined into profiles. The statistics database does not store raw IP addresses, user-agent strings or exact request times. It stores no records of individual page requests, visitor or session identifiers, navigation histories, geographic location, screen dimensions or form inputs.
No analytics script, tracking pixel or additional analytics request is used. The measurement creates or reads no analytics cookies, local-storage entries or visitor identifiers on your device. It does not access additional information on your device, so no separate device-access consent is requested for these server statistics. The functional browser storage described in section 3 is separate.
Query strings and URL fragments, including encoded teams, are excluded from the statistics. Referrers are reduced to known source categories or hostnames. Full referrer URLs, paths and query parameters are not retained. The statistics are not used for advertising or tracking across websites. There is no session recording or heatmap collection. The counters remain on the operator's server and are not sent to external analytics services. Access to the statistics and monitoring dashboard is restricted to the operator.
Where personal data is processed to form the counters, the legal basis is Article 6(1)(f) GDPR. The legitimate interests are understanding demand for website content and improving its operation through limited, aggregate statistics. The right to object is explained in section 6.
Aggregate statistics are retained for up to 90 days and then automatically deleted. Operational server logs are handled separately as described in section 2. Requests carrying a Do Not Track or Global Privacy Control header requesting exclusion are not counted. The statistics also exclude recognised bots, marked prefetch requests, API and asset requests, failed responses and HEAD requests. Cached pages, filtering and collection outages can cause undercounting; unrecognised bots can cause overcounting. These are filtered page-request counts, not complete usage totals.
The public website does not provide permanent user accounts or display personalised advertising. DokkanAPI does not expose a public API; internal endpoints operate the website.
5. Sharing teams
The Team Builder can encode the selected card identifiers into a shareable URL. Sharing is initiated by you through the browser's native sharing or clipboard function. DokkanAPI does not receive a list of the people with whom you share that URL. When somebody opens the URL, its path and query string, including the encoded card identifiers, may be included in the operational server log described above.
Draft Battle lobbies
When you create or join a Draft Battle, your chosen display name, card selections, team and readiness are stored on the operator's server for the shared game. Use a nickname; a real name is not required. Names and drafted picks are visible to people with the invite link. Completed teams become visible to them once all participants are ready. Unfinished teams are only available to their owner.
Each browser tab has its own participant session. A random tab identifier is stored in session storage; a functional cookie identifies your participant in that lobby so you can return after a reload. It expires after 24 hours, is inaccessible to scripts, and is limited to that lobby's internal endpoints. The server stores only a hash of its random secret. Lobby-specific Team Builder state may also be stored locally in your browser. This storage serves the multiplayer function you requested and is separate from website statistics. Lobbies expire after 24 hours and expired lobby data is automatically removed.
6. Rights relating to request and analytics data
These rights concern the technical request data described in section 2 and the analytics data described in section 4, to the extent that personal data is processed. The stored usage statistics contain no visitor or session identifiers and cannot be used by DokkanAPI to retrieve your browsing history.
To the extent that the applicable legal requirements are met, you may request access to, rectification or erasure of, and restriction of processing of personal data concerning you. Under Article 21 GDPR, you may object at any time, on grounds relating to your particular situation, to processing based on legitimate interests. You may also lodge a complaint with a competent data-protection supervisory authority.
If request or analytics data has already been deleted or cannot be linked to you, DokkanAPI may be unable to identify data relating to you and is not required to collect additional information solely for that purpose. Requests can be sent to contact@dokkanapi.com.
7. Required data and automated decisions
Providing request data such as an IP address is technically necessary to retrieve the website. You are not legally or contractually required to save a team or Performance Mode preference, or to participate in usage measurement. DokkanAPI does not use this data to make automated decisions with legal or similarly significant effects on you.
8. Changes to this policy
This policy will be updated when the website, hosting arrangement, or processing activities change. The current revision date is displayed at the top of this page.