コンテンツへスキップ

このサイトの表示文は機械翻訳です。ゲーム内の名称は公式の日本語版に基づいています。

Privacy policy

最終更新日:2026年11月18日

このページはまだお使いの言語に対応していません。原文を表示しています。

The German version of this policy is the legally binding text; this English version is a courtesy translation.

1. Controller

The controller within the meaning of the General Data Protection Regulation (GDPR) is:

Marco Foof
Joachim-Friedrich-Straße 25
10711 Berlin, ドイツ
Email: [email protected]

HuntCodex (huntcodex.com) is a project of Skullrock Gaming. No data protection officer has been appointed because the legal requirements are not met.

2. Overview

We only process the data needed to run the site and the features you use. You can read the public content without an account. An account is optional and free. We only load optional third-party services if you agreed in the cookie settings (section 11).

3. Hosting, delivery and server logs

The application runs on servers of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (data centre in Germany). In front of the servers sits the content delivery network of Cloudflare (Cloudflare Germany GmbH, Rosental 7, 80331 Munich, for Cloudflare, Inc., USA), which provides DNS, caching, TLS and protection against attacks (WAF, DDoS). For technical reasons Cloudflare processes the IP address of every request. Cloudflare is certified under the EU-US Data Privacy Framework, and standard contractual clauses apply in addition.

For every request we process in server logs:

  • IP address of the requesting device,
  • date and time of the request,
  • requested URL, HTTP method and status code,
  • amount of data transferred and referrer URL (if sent by the browser),
  • browser type and version and operating system (user agent).

Purpose: technical delivery, stability and security (detecting attacks and faults). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in secure and reliable operation). Retention: logs are rotated by size and usually overwritten after a few days to weeks. They are only analysed when there is a reason.

4. Database and file storage

We store account and content data in a PostgreSQL database on servers of Hetzner Online GmbH in Germany. Uploaded files such as profile pictures are kept in non-public object storage (Cloudflare R2, EU region) and are only delivered through our website. Profile pictures are resized on the server when uploaded; metadata such as location data is removed. Database backups are kept encrypted within the EU.

5. Registration and user account

When you register with email and password we process:

  • email address (login, confirmation, password reset, notifications),
  • display name and username,
  • password only as a cryptographic hash,
  • time of registration and email confirmation status,
  • session data (session token, creation and expiry time, IP address and user agent of the login for account security),
  • if you enable two-factor sign-in, the data needed for it (encrypted secret, backup codes as hashes).

You can optionally add an avatar, a short bio and more to your profile. Username, display name and avatar are visible on your public profile page; your email address is never public.

Legal basis: Art. 6(1)(b) GDPR (contract for the account), and for the security data of the session also point (f). Retention: until the account is deleted. You can delete your account and export your data in the account settings at any time. Sessions expire after 30 days at the latest.

6. Sign-in with Google, Discord and Steam

Alternatively you can sign in with an existing account at Google, Discord or Steam. You are redirected to the provider. After you agree there, we receive:

  • from Google and Discord (OAuth 2.0): a provider-internal user ID, email address and display name, the address of the profile picture and an access token that we only use to confirm the sign-in,
  • from Steam (OpenID): the public SteamID and, if shared, the public profile name and picture. Steam does not provide an email address.

The provider learns that you sign in to HuntCodex. What data it processes itself is governed by its privacy policy:

Legal basis: Art. 6(1)(b) GDPR (the sign-in method you chose); the redirect happens at your request. Data may be transferred to the USA. Google and Discord are certified under the EU-US Data Privacy Framework or use standard contractual clauses; according to its statements the same applies to Valve. You can unlink connected provider accounts in the account settings as long as another sign-in method remains.

7. Sending email

We send confirmation, password and notification emails through the service provider Resend (Resend, Inc., 2261 Market Street #5039, San Francisco, CA 94114, USA). Resend processes the recipient address, subject, content, delivery status and time. A data processing agreement is in place; for the transfer to the USA we rely on the EU-US Data Privacy Framework or standard contractual clauses.

Legal basis: Art. 6(1)(b) GDPR (performance of the contract) and point (f) (account security).

8. Error tracking (Bugsink)

To detect errors we run a self-hosted error tracker (Bugsink) on our own servers at Hetzner in Germany. No external error service is used and no data is passed on to third parties. When an error occurs we store technical details such as the error message, the affected page, browser type, time and possibly a user ID. Legal basis: Art. 6(1)(f) GDPR (interest in error-free operation). Retention: until the configured retention period ends.

Bug reports

With "Report a bug" you can send us bugs and ideas. We store title, description, type of report, the page you were on (without credentials in the address), window size, language, browser and operating system (name only), app version and, if you are signed in, your account. We forward the report, its metadata and any attached screenshots to our private team ticket system. If you are signed in, your user ID and name are included so we can follow up when permitted. Screenshots are also stored in our file storage. When you delete your account, we remove its link to the local report and delete its local screenshots; the team ticket must be handled separately on request. If you ask for it, we list you as a tester on the supporters page; you can withdraw this consent with your next report or by deleting your account. Legal basis: Art. 6(1)(f) GDPR (interest in an error-free service); for being listed as a tester, Art. 6(1)(a) GDPR.

Comments and reports

If the site offers comments, we store what you write (text as you entered it plus the rendered version), the time, the item it belongs to and your account. Comments are public: everyone who can see the item can read them together with your username. You can edit a comment for 15 minutes and delete it at any time; deleted comments leave an empty placeholder so that replies keep their place. Moderators can hide or delete comments; each such action is recorded in an audit log with the acting moderator. If you report content, we store the report (reason, optional note, time, your account) for the moderators only; the reported person does not see who reported. If a comment is deleted by its author while a report about it is still open, we keep a copy of the original text for the moderators until the report is decided. When you delete your account, your comments stay as an anonymous placeholder with the text "[deleted]"; your reports are deleted, except open ones, which stay without your name and note until they are decided. Legal basis: Art. 6(1)(b) GDPR (providing the comment function) and Art. 6(1)(f) GDPR (protection against illegal content and abuse).

9. Protection against abuse

Registration and sign-in are protected by rate limiting. IP addresses are kept briefly in memory or in the database for this. If we use Cloudflare Turnstile on individual forms, proof from your browser is sent to Cloudflare to detect bots. Legal basis: Art. 6(1)(f) GDPR (protection against abuse and attacks).

10. Audience measurement

Our own page-view count

We count how often public pages are viewed. We store only totals per page template (for example "blog post", not the specific address), country and hour. The country comes from information Cloudflare adds to every request. No IP address, browser identifier, referrer, account or session is stored for this, and nothing is read from or stored on your device. Views by bots, prefetches, account, sign-in and admin pages are not counted. Purpose: measuring the reach of the site. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in audience measurement); because the totals cannot be linked to a person, no personal data remains once they are stored (recital 26 GDPR). Retention: the totals are kept indefinitely.

Our own event counters

We count per day how often certain actions happen, such as "build published" or "farming goal finished". We store only the action's name and the daily sum, no IP address, account or session. To limit abuse, the IP address is processed briefly for rate limiting (see above) but is not stored with the sums. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving the features).

Cloudflare traffic statistics

Cloudflare (see section 3) provides us with aggregated figures about the requests to this site for a given period: number of requests and page views, estimated unique visitors, countries, status codes, cache share and data volume. We only receive these totals, no individual IP addresses. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in running the site and monitoring its load).

Cloudflare Web Analytics

In addition, we use Cloudflare Web Analytics, a service from Cloudflare (for the provider and data transfers see section 3). For this, Cloudflare adds a small script to our pages that measures page views and loading times in the browser. The script sends the page address and referrer, browser data and measurements to Cloudflare; for technical reasons Cloudflare also processes your IP address. According to Cloudflare, the script sets no cookies, uses no local storage and does not create a fingerprint from your IP address or browser identifier for the statistics. We only evaluate aggregated figures, such as page views per page, and no information about individual people. The script runs without consent. Purpose: measuring the reach and loading times of the site. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in audience measurement and a fast site).

Audience measurement (SkullRock Analytics)

To measure the site's reach we also use "SkullRock Analytics", our own audience measurement that we run ourselves on our own servers. No third-party tracking is involved. A small script loaded from t.skullrock-gaming.com reports page views and a few events of our own to our server. All we get from it are totals (page views, where visits come from, events), no profiles and no recognition of returning visitors.

Base measurement (without consent). The script sends the address you opened (the path; of the query parameters only utm_source, utm_medium, utm_campaign and utm_term), the referring page and, for our own events, their name with at most 10 short values. When you move between pages of this site, the referring page is the previous page without query parameters. For other sites only the host is stored, for this site only the path of the previous page; this gives totals per transition ("from → to") only, never paths across several pages. If the visit comes from outside or directly, the script sends one closing note when you leave the tab: the visible time in the tab (at most 30 minutes), the number of page views in that tab (at most 50), whether a link to this site was clicked or a form was submitted, and whether one of our own events occurred. Of this, only the visible time and "interaction yes/no" are stored, without linking them to a person or to other visits. The server derives the country (from a header set by the upstream proxy, not from a stored IP address), the device class (desktop, mobile, tablet) and the browser family as a rough category. To filter out bots, the script reads in the browser whether it is automated (navigator.webdriver) and whether the page is visible. Not stored: IP address, the full browser identifier (user agent), the fragment and any other query parameters, path and query of other referring sites, and visitor or session IDs. The script sets no cookies and stores nothing in browser storage (localStorage, sessionStorage). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in anonymous audience measurement) and Section 25(2) No. 2 TDDDG.

Extended data (only with consent). If you agree to the category "Statistics (audience measurement with consent)" in the cookie settings, the measurement also records your browser language (the primary language only, for example en), your operating system family (derived by the server from the browser identifier, which itself is not stored) and the size class of your browser window in four levels (no exact size). Even then there are no cookies, no browser storage, no visitor or session ID and no stored IP address. Legal basis: your consent (Art. 6(1)(a) GDPR, Section 25(1) TDDDG). You can withdraw it at any time via "Cookie settings" in the footer; the withdrawal takes effect from the next page view. Totals recorded before cannot be linked to any person.

Retention: individual events for 30 days in the database, then 6 months as archive files, after which they are deleted. Daily and hourly totals without any personal reference are kept permanently. Recipients: our own servers at Hetzner Online GmbH in Germany, and Cloudflare (see section 3) as the upstream proxy and for the archive files (Cloudflare R2). Objection: content blockers can prevent the script; the data collected cannot be linked to any person.

If you agree to the "Statistics" category in the cookie settings, we measure visits with DataFast. DataFast works without cookies. Your browser stores a session and a visitor identifier in session storage (sessionStorage, deleted when you close the tab) and a queue of events not yet sent plus an opt-out flag in local storage (localStorage). Transmitted are the page viewed (without query parameters; pages with personal address parts only as a template), the referring domain without its path, screen size, language, time zone, browser and operating system and, for technical reasons, your IP address. DataFast derives a visitor identifier from these that changes daily. Admin, account and sign-in pages are never reported. Legal basis: your consent (section 25(1) TDDDG, Art. 6(1)(a) GDPR), which you can withdraw at any time via "Cookie settings" in the footer. Without consent DataFast is not loaded.

We set as few cookies as possible. Necessary cookies need no consent (section 25(2) no. 2 TDDDG, Art. 6(1)(b) and (f) GDPR):

Name Purpose Duration
mhw.session_token (and mhw.session_data) sign-in (session), HttpOnly, SameSite=Lax up to 30 days
mhw_stepup confirms a repeated password or code check for sensitive actions, HttpOnly 12 hours
mhw_banned shows the notice on the login page after a ban, HttpOnly 10 minutes
mhw_locale_hint_dismissed remembers that you closed the language hint 1 year
mhw_consent stores your cookie choice 180 days

The language comes from the address (for example /de/...) and is not stored in a cookie. There is no light/dark switch and therefore no theme cookie.

So that the tools work without an account, the site keeps some data in your browser's local storage (localStorage, or sessionStorage, deleted when you close the tab). This data stays on your device and is not sent to us; it has no expiry date, and you can remove it at any time in your browser settings ("clear site data"). The legal basis is section 25(2) no. 2 TDDDG, because you explicitly use these features.

Name Purpose
hc.loadouts.v1 your loadouts while you are not signed in
hc.loadout-drawer.v1 (sessionStorage) remembers whether the loadout drawer is open
hc-build-draft (sessionStorage) draft of a build while you switch between the form and the editor
hc.owned.v1 the decorations and talismans you own, in the planner
mhw:hc:owned:… the material amounts you own, per data version
hc.goals.v1, hc.favorites.v1 your farming goals and favourite monsters
hc.route-goals.v1 farming routes you saved as a goal (address and title)
hc.route-run.v1 stops ticked off on your current run, per route
hc.map.v2 gathering points and camps marked as found on the map (when signed in, also in your account)
hc.recent.v1 recently used monsters, tools and weapon type for the home page
hc.search.recent.v1.… your recent search results, per language

For all other services, apart from the consent-free audience measurement described in section 10, we ask for your consent through the cookie notice (section 25(1) TDDDG, Art. 6(1)(a) GDPR). Your choice applies for 180 days or until the list of services changes; then we ask again. We treat a "Global Privacy Control" signal from your browser as a refusal. You can change your choice at any time via "Cookie settings" in the footer and withdraw consent with effect for the future.

Optional services

広告

Google AdSenseの広告です。Googleは広告の配信、測定、パーソナライズにCookieを使用する場合があります。同意がない場合、広告枠は空のままになります。

プロバイダー:Google AdSense

統計

DataFastによるCookieなしの訪問統計です。ブラウザのストレージにセッション識別子とイベントのキューが保持されます。個人を特定できるアドレス部分を含むページは、テンプレートとしてのみ記録されます。同意がない場合、DataFastは読み込まれません。

プロバイダー:DataFast

統計(同意に基づくアクセス解析)

SkullRock Analyticsは自社サーバー上で運用する独自のアクセス解析で、Cookieやブラウザのストレージを使わずに常にページビューを数えます。同意いただいた場合は、ブラウザの言語、OSの種類、ウィンドウサイズの区分(4段階、正確なサイズではありません)も記録します。訪問者IDやIPアドレスは保存しません。

プロバイダー:SkullRock Analytics

12. Recipients and transfers to third countries

We only pass personal data to the service providers named above (Hetzner, Cloudflare, Resend, the sign-in providers you choose and, with your consent, DataFast; SkullRock Analytics is run by ourselves) or when we are legally obliged to. Data processing agreements under Art. 28 GDPR are in place with our processors. For transfers to third countries we rely on the EU-US Data Privacy Framework or standard contractual clauses.

13. Retention

Unless stated otherwise above, we only keep data as long as the purpose requires: account data and content until the account is deleted, sessions up to 30 days, server logs until rotation. After an account is deleted, data may remain in backups for the backup retention period; backups are not used productively.

14. Your rights

You have the following rights against us:

  • access (Art. 15 GDPR),
  • rectification (Art. 16 GDPR); you can change most account data yourself,
  • erasure (Art. 17 GDPR); you can delete your account yourself at any time,
  • restriction of processing (Art. 18 GDPR),
  • data portability (Art. 20 GDPR); a data export is available in the account settings,
  • objection (Art. 21 GDPR) to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation,
  • withdrawal of consent (Art. 7(3) GDPR) with effect for the future.

An email to [email protected] is enough to exercise them. Please use the address registered with us.

15. Right to lodge a complaint

Without prejudice to other remedies you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR), in particular in the member state of your habitual residence, place of work or place of the alleged infringement.

16. Data security

All connections to huntcodex.com are encrypted with TLS. Passwords are stored only as hashes using a modern method, and session cookies are HttpOnly. Access to servers and the database is limited to the operator. We keep adapting our measures to the state of the art.

17. No automated decision-making, children

There is no automated decision-making including profiling under Art. 22 GDPR. The service is not aimed at children under 16; an account may only be created by someone who is at least 16 or has the consent of their legal guardians.

18. Changes

We update this policy when our processing or the legal situation changes. The version published here applies; the date of the last update is shown at the top of the page.

Cookie設定

利用を許可する任意のサービスを選択してください。選択内容はCookieに180日間保存されます。

ログインセッション、言語、同意の選択内容です。サイトの動作に必要なため、常にオンです。

現在、任意のCookieやサードパーティのサービスはありません。