KillNoDeby Trefnio
FeaturesBeta TermsPrivacy
Dashboard ↗

KILLNODE / BETA 1.0 · 6 NOVEMBER 2026

Privacy Policy

How KillNoDe handles Discord account details, DayZ player events, server configuration and data-protection requests.

Beta TermsPrivacy PolicyBack to homepage

☠️ KillNoDe — Privacy Policy

Version: Beta 1.0
Effective date: 6 November 2026
Service: KillNoDe — killnode.app and app.killnode.app
Brand: Trefnio
Operator and privacy contact: EpicFailWinner (KillNoDe by Trefnio) — hello@trefnio.co.uk

This notice explains how personal information may be used when someone visits KillNoDe, signs in with Discord, administers a connected server or plays on a DayZ server whose community uses KillNoDe. The amount of information we handle depends on which features a server administrator enables.

1. Who is responsible for your information?

EpicFailWinner operates KillNoDe under the Trefnio brand and is the contact point for privacy requests relating to the service. For account, website, security and support information, the KillNoDe operator decides how and why that information is used.

For player monitoring, Discord event feeds and other tools configured by a community, the community administrator also makes important decisions about which information is collected and published. The respective responsibilities of KillNoDe and a community depend on the processing arrangement. Community administrators must provide their players with any privacy information required of them.

Questions about KillNoDe data can be sent to hello@trefnio.co.uk. For information posted in a particular community's Discord channels, you may also need to contact that community's administrators.

2. What information may we handle?

Depending on how the service is used, this may include:

  • Discord account and community details: your Discord user ID, username, display name, avatar, Discord server IDs, the communities you can administer and relevant permission information obtained when you sign in or use bot commands.
  • DayZ player and event information: gamertags or character names, joins and leaves, player sessions, kills, deaths, weapons, hits, building activity, server events, timestamps, and reported in-game positions or map areas.
  • Statistics and community tools: leaderboards, heatmap inputs, faction memberships and other records needed for enabled features.
  • Server configuration and integrations: Discord channel identifiers, server names and identifiers, Nitrado service details, preferences, schedules and credentials or access tokens needed to operate authorised integrations.
  • Website and operational information: session identifiers, service requests, IP addresses and technical log information that may be processed by our hosting, security and delivery services.
  • Support and safety enquiries: information you choose to send when requesting help, reporting a problem, appealing an action or exercising a data-protection right.

KillNoDe does not need your Discord password. Do not send passwords, bot tokens or Nitrado credentials by ordinary email or in public Discord channels.

3. Why do we use information, and on what basis?

We use information for the purposes below, where the stated UK data-protection basis is appropriate to the particular activity:

  • Authentication and administration: to identify authorised administrators, show permitted servers and provide the requested dashboard or bot service. This is generally necessary for our service arrangement with an administrator and/or for legitimate interests in secure operation.
  • Community event tracking: to receive and process DayZ and Discord events, calculate statistics, display maps or feeds, and carry out settings chosen by administrators. This may involve the legitimate interests of the operator and community in running and protecting their game servers; responsibilities and lawful bases must be assessed for each arrangement.
  • Security and preventing misuse: to verify permissions, detect misuse, investigate incidents and protect the service and its users, generally relying on legitimate interests or applicable legal obligations.
  • Support and service improvement: to respond to messages, troubleshoot failures and improve beta functionality, generally relying on legitimate interests or steps needed to provide the requested service.
  • Legal requests: to comply with a legal obligation when required.

Where we rely on legitimate interests, the relevant interests are keeping the service secure, supporting server administration and operating community features without unnecessary disruption. These interests must be balanced against individuals' rights and expectations. We do not treat a visitor opening this page as consent to optional processing.

4. Discord sign-in and necessary cookies

The web dashboard uses Discord OAuth sign-in to request basic account identity (identify) and information about the Discord communities you can manage (guilds). The application uses a secure, HTTP-only session cookie named killnode_session to maintain sign-in. In the reviewed dashboard implementation, this cookie has a seven-day maximum age; temporary OAuth state used to protect login expires after approximately ten minutes.

These are essential authentication and security mechanisms, not advertising cookies. Discord and infrastructure providers may use their own cookies and collect technical information subject to their own notices. If optional analytics or advertising cookies are introduced later, this notice and any applicable consent controls will need updating first.

5. Where information comes from

Information may come directly from you; Discord's OAuth and bot APIs; game-server logs and events made available through authorised integrations; community administrators configuring KillNoDe; and our service or hosting logs.

Player event information can be collected even where a player has not registered on the KillNoDe website, because it comes from a connected DayZ server. Community administrators should make that monitoring clear to their players.

6. Who can receive information?

Where relevant to the features enabled, information may be processed or disclosed through:

  • Discord, to authenticate administrators and send event notifications into channels chosen by server administrators. People who have access to those channels may see the information posted there.
  • Nitrado, where a server administrator authorises server-management integration.
  • Cloudflare, which hosts and delivers the public site and dashboard and may process authentication-session data and network requests.
  • OVHcloud / hosting infrastructure, used to operate the KillNoDe backend and store its service data.
  • Authorised community administrators, who can access server data and controls relevant to their permissions.
  • Relevant authorities or advisers, where legally required or appropriately necessary to respond to a claim or security incident.

We do not sell KillNoDe player records to advertisers. This list should be reviewed if additional providers are enabled during beta.

7. How long do we keep information?

Retention varies by data type and feature:

  • Web sign-in: the reviewed dashboard's login-session record is set to expire after seven days; temporary OAuth sign-in state expires after approximately ten minutes. Logging out ends the current session.
  • Player events, server logs, statistics and configuration: these may remain while a community is connected and while needed for the features enabled, service troubleshooting, security investigations or relevant legal obligations. A single fixed retention period has not yet been established for every category of historical beta data. Do not assume that removing the bot automatically removes every historical record.
  • Support and security correspondence: kept for as long as reasonably needed to respond to a request, handle a dispute or meet a legal obligation.
  • Backups and provider logs: may have separate technical retention cycles. Any deletion request will be assessed in light of these systems and applicable requirements.

Community administrators may request disconnection and data review at hello@trefnio.co.uk. Where an individual asks about personal information appearing in a community-controlled Discord channel, the community administrator may also need to act on that request.

8. International data processing

Services such as Discord and Cloudflare may process personal information outside the UK. The specific locations and any relevant international-transfer mechanisms depend on the provider and processing arrangement. We assess international transfers and any safeguards required by applicable data-protection law. You can contact hello@trefnio.co.uk to ask about relevant providers and safeguards.

9. Your data-protection rights

Depending on the circumstances and the relevant lawful basis, you may have rights to request access to, correction of, erasure of, or restriction of your personal information; to object to particular processing; and, where applicable, to data portability.

You may object to processing based on legitimate interests. We will assess the objection under the applicable rules. Where processing is based on consent, you may withdraw that consent.

To make a request, email hello@trefnio.co.uk with enough information to help identify the relevant record or server. We may ask for reasonable evidence to verify your identity or authority before disclosing or changing records.

If you are unhappy with how your information is handled, you can contact the UK Information Commissioner's Office (ICO) at ico.org.uk. We encourage you to contact us first so we can investigate.

10. Security, monitoring and automated activity

We use access controls, role and permission checks, service authentication and other safeguards to help protect KillNoDe. No online system can be guaranteed completely secure.

The service may generate automatic alerts, scores, feeds or administrator-configured actions. These are intended to support DayZ server administration and are not intended as decisions producing legal or similarly significant effects on individuals. If you believe a feature has affected you unfairly, contact the relevant community administrator or hello@trefnio.co.uk.

11. Updates and contact

We may revise this policy as KillNoDe changes. Material changes will be brought to affected users' attention where required, and the current version and effective date will appear at the top.

Operator: EpicFailWinner (KillNoDe by Trefnio)
Email: hello@trefnio.co.uk
Beta Terms: killnode.app/terms

KillNoDe by Trefnio

© 2026 KillNoDe · Operator: EpicFailWinner

Beta TermsPrivacy PolicyContactDashboard