# This is an implementation of the GDPR.txt specification: https://gdpr-txt.org/
# -
# This file lists the processing purposes and data gathered by
# Team Fortress 2 Classic's Sentry integration.
# -
# Everything listed here is **opt-in** and will not be gathered unless
# you agree to send us crash reports upon first starting the game. Hence,
# the "required" field is universally "no".
# -
# If you change your mind later, you can also opt-out by setting
# tf2c_send_error_reports to 0 in your game's developer console.

purpose: Provide developers with crash information to identify and resolve issues.
lawfulness: consent
# We believe that this field could equally be "legitimate interest", however we
# ask for consent regardless (even though it may be unnecessary) so it provides
# the strongest case for lawfulness.

data: backtrace
required: no
visibility: developers
description:
    The backtrace is processed out of your crash dump, containing "a
    hierarchical trace of the function calls made by a program, used in
    debugging", and is essential in identifying the cause of a crash.
mitigation:
    Since this includes absolute paths to library and executable names, our
    processor (Sentry) automatically filters out usernames from these paths,
    since these could feasibly be real and unique names.

data: user
required: no
visibility: developers
description:
    The Steam ID is used to verify that reports are legitimate, identify the
    number of unique users encountering a specific crash, and locate specific
    crashes as reported by users.

data: os
required: no
visibility: developers
description:
    Your OS version (Windows release number, or Linux kernel version) is used
    to track whether or not crashes are operating system-specific, and whether
    they're connected to any particular versions. Linux kernel versions can
    typically also be linked to specific distribution releases, e.g., Ubuntu
    22.04.

data: server-ip
required: no
visibility: developers
description:
    This is the IP of the game server you're connected to at the time of
    crash. This is necessary as some disreputable servers will actively
    attempt to disrupt clients by setting problematic cvars, pushing malicious
    files, or otherwise causing havoc. Being able to identify crashes caused
    by one server disproportionately helps us pin down the issue, help the
    server owner change settings that are causing client issues, or blacklist
    servers intentionally causing harm.

data: current-map
required: no
visibility: developers
description:
    This is the map you're playing on whenever your client crashes. A large
    number of crashes are ultimately caused by map behavior which Team
    Fortress 2 Classic handles incorrectly. A map name helps us find and test
    the map ourselves and find what the exact issue is, in cases where a
    backtrace alone may not be helpful.

data: release
required: no
visibility: developers
description:
    The version of Team Fortress 2 Classic that crashes. This is essential
    information for determining exactly which versions of the game a crash is
    present in, and to assist in internal beta testing which uses numerous
    release candidate builds.