Philipp Decker - Videogame and Software Development (referred to as "we", "us",
"our" below) is a small business operating from Germany. We primarily focus on the
development of resources for "FiveM" by Cfx.re, a
modification for "Grand Theft Auto V" by
Rockstar Games.
Disclaimer: kiminaze.de, its
subdomains and its content is not approved, sponsored, or endorsed by Rockstar
Games.
Owner and person responsible for the domain kiminaze.de, its subdomains and content
is:
Philipp Decker
Rathausstr. 19
66802 Überherrn
Germany
E-Mail: kiminaze@yahoo.de
We provide comprehensive technical documentation and guidance for our FiveM
resources.
Use of this service is free of charge.
The documentation is available at
docs.kiminaze.de.
We operate a Discord server to facilitate community interaction, technical support
and official announcements.
A dedicated Discord Bot is also provided to ensure seamless integration with the
support process.
Use of this service is free of charge.
The server can be accessed at
discord.kiminaze.de.
We provide an optional telemetry service that allows our resources to share
diagnostic data with us. This data helps with debugging, technical support, and
improving the stability and reliability of our resources.
Use of this service is free of charge.
Telemetry is available only in selected resources. It is opt-in by default,
except in experimental versions where it defaults to opt-out.
Controller: Philipp Decker - Videogame and Software Development (German
small business)
Email: kiminaze@yahoo.de
To request deletion of your data, please contact support via
our Discord server or by reaching out to
kiminaze@yahoo.de directly.
Requests are processed as soon as possible.
Please note that deletion may result in temporary loss of access to certain
services until consent is provided again.
Our documentation does not directly collect personal data. However, cookies are
used to enable specific website features.
Embedded videos are provided through YouTube for demonstration and
visualization purposes. When viewing these videos, YouTube may collect data in
accordance with its
Privacy Policy.
If cookies are declined, only external links to the videos will be available
instead of embedded playback.
We use Discord, a third-party communication platform provided by Discord Inc., to
operate our community server, provide technical support, facilitate community
interaction, and publish official announcements.
When using our Discord server, Discord may process personal data in accordance with
its own privacy policy and terms of service. We do not control the processing of
personal data carried out independently by Discord.
For information about how Discord processes personal data, please refer to
Discord's Privacy Policy.
Our Discord Bot may additionally process certain identifiers as described in
Section 3.5.2. of this Privacy Policy.
The Discord Bot processes identifiers where necessary to provide purchase
verification and contractual support services, pursuant to Article 6(1)(b) GDPR.
Where consent is required for optional functionality, such as claiming roles linked
to purchases from our store, users provide consent by pressing a clearly labeled
button indicating the purpose of the processing. Consent may be withdrawn at any
time; withdrawal does not affect the lawfulness of processing carried out before
withdrawal.
All other processes only handle and then immediately discard the user's identifier.
The identifiers are used to verify purchases where necessary to provide contractual support services for resources acquired through our store and for future purchase verification.
Identifiers are stored in a password-protected database on our server. The database
is not accessible from external networks, and external connections are blocked
entirely.
Access to the identifiers is restricted to the Discord Bot for its intended
operation and to authorized administrative and support staff directly on the
server. Access to the server itself is protected by authentication and is
restricted to authorized personnel.
The identifiers are not shared with third parties.
Identifiers are retained only for as long as purchase verification remains necessary. Users may request the deletion of their data; however, deletion may affect our ability to provide future purchase verification or support where the retained identifiers are necessary for those purposes.
Telemetry data ("data") is collected when telemetry is enabled through the provided
configuration variable ("convar"). The default telemetry setting depends on whether
the resource is a stable or experimental version, as described below.
For stable releases, telemetry is disabled by default and is opt-in. Users may
enable or disable telemetry at any time at their discretion. Where telemetry is
voluntarily enabled for a stable release, the processing is based on the user's
consent pursuant to Article 6(1)(a) GDPR.
Once enabled, data is transmitted under the following conditions:
Experimental versions are versions of the resource that are still under active
development and may contain unresolved issues or defects. For these versions,
telemetry is enabled by default because a continuous and timely flow of diagnostic
data is necessary to efficiently identify, reproduce, diagnose, and resolve issues
during development.
Manual issue reports are often delayed, incomplete, or unavailable. Automatic
collection of diagnostic data allows us to identify issues that may otherwise
remain undetected and enables faster and more reliable iteration during
development.
For experimental versions, telemetry is therefore processed on the basis of our
legitimate interests pursuant to Article 6(1)(f) GDPR. Our legitimate interest is
the development, maintenance, debugging, and improvement of the resource. The
telemetry is limited to diagnostic information necessary for these purposes.
The telemetry data does not contain personal data apart from the Cfx.re identifier
of the server owner, which is used to identify the source of the telemetry on our
backend. The logs and diagnostic information generated by the resource do not
contain personal data.
Users can disable telemetry at any time by changing the corresponding configuration
variable. Users have the right to object to processing based on legitimate
interests in accordance with Article 21 GDPR.
Data is collected to:
Data is transmitted via HTTPS and stored as text files on our server.
The files are stored on the server and are not accessible from external network.
External access to the server is blocked, and access to the telemetry data is
restricted to the Discord Bot for its intended operation and to authorized
administrative and support staff directly on the server.
Access to the server itself is protected by authentication and is restricted to
authorized personnel.
Data is generally not shared with third parties.
In support cases, data may be used to illustrate issues to the user or their
developer.
Support tickets are visible only to users who have access to the corresponding
resource section on
our Discord server. This does include
other users who have legally acquired the resource.
Collected data is retained for a maximum of 8 days, after which it is
automatically and permanently deleted.
If telemetry is disabled, previously collected data is also erased within a
maximum of 8 days or until the user requests deletion of their data.