Privacy Policy

PVE SERVER HUB is operated for the independent PVE DAYZ community. The PVE DAYZ community team handles personal-information questions and requests through the contact routes below.

For a privacy request or question, email pvedayzhub@outlook.com, use the private Support page or use the PVE DAYZ Discord ticket system. Do not post personal information in a public channel.

Public pages do not require an account. Hosting and security providers may process IP address, device/browser information, request time, requested path and security events to deliver and protect the service.

The Hub stores theme and accent preferences on your device, and stores the language preference in local storage and a first-party preference cookie.

If you choose Discord sign-in, Discord sends the account and community information required to verify you. We never receive your Discord password.

• Discord user ID, username, display name and avatar.
• PVE DAYZ Discord membership and relevant role IDs, including staff, trader, booster and server-role checks where configured.
• Sign-in, session, role-sync and security timestamps.
• Profile content and appearance, favourite server, privacy choices and selected unlocked badges.
• Friends, friend requests, blocks and private direct messages when you use those features.
• Website and eligible Discord messages, GIF activity, reactions, Chat XP, levels and community leaderboard facts.
• Reports, appeals, support requests, moderation outcomes and audit records.
• Event registrations, notification preferences and encrypted push-subscription details when enabled.
• Virtual wallet balances and ledgers, catalogue order contents, selected fulfilment server, delivery/collection status, Discord fulfilment message references and authorised staff actions on an order.
• Private X/Z map coordinates when you request automatic shop delivery. They are encrypted while the order is pending or needs recovery, never included in Discord Shop Orders and erased after you confirm receipt, staff records an evidence-backed delivery confirmation or the automatic subtotal is refunded.
• Monthly subscriptions and one-time Supporter Cash purchases create checkout, payment, entitlement and benefit-request records, including amounts, currency, status, paid dates and any selected server. Restricted provider references and encrypted payment callbacks, including unresolved refunds, are retained for duplicate prevention, recovery and disputes; raw callbacks, approval tokens and provider account bindings are excluded from member-facing history.
• Existing PayPal payments verified and recorded by authorised staff, including the tier, actual amount and currency, paid dates and any revocation. A fingerprint of the transaction reference prevents duplicate records; the original reference is not stored in this register. Staff reasons and attribution stay in restricted operational history.
• Private X/Z map coordinates, selections and notes supplied for an eligible supporter benefit. Exact request values are encrypted while queued, processing or needing recovery, excluded from public history and general logs, and erased from the request on fulfilment, cancellation, Discord disconnect or account-deletion handling.
• A delivered donation alarm retains its member identity, server, zone centre and private Discord channel reference to monitor the base and reuse the same alarm on renewal. The zone centre is available to authorised zone tools; location-enabled alerts appear in the alarm's private Discord channel. Monitoring stops when paid access ends or the member disconnects. Operational identity and location in Hub records are redacted when account deletion is finalised; delivery and payment receipts remain in restricted history. This does not delete existing Discord channels or messages.
• A personal vehicle spawn retains its selected vehicle, server and position so the same setup can continue on renewal. Authorised staff can see its operational details. When access ends, its future respawn settings are queued for removal and take effect at the next normal server restart; existing world vehicles are not forcibly deleted. Account deletion waits for outstanding vehicle-file cleanup or recovery. After safe cleanup, local personal setup and backup contents are redacted while restricted delivery receipts and verification hashes remain.
• A one-car reward-code prize keeps its claim, selected vehicle and server, automatic delivery progress and any receipt confirmation. Its private location and temporary server-file backups are encrypted and restricted to delivery and recovery. Disconnecting or requesting account deletion stops new delivery attempts. If a server-file write has already been attempted, final deletion waits for safe cleanup or recovery; cleanup can continue while the account is unavailable. Final deletion erases the private setup and ends any unused request while retaining a restricted delivery receipt. It does not make the code usable again or delete a vehicle already in the game.

The Hub processes Nitrado server state and DayZ administrative logs for PVE 20, PVE 32, PVE 50 and PVE 64. This can create information about a player even before that player links a Hub account.

Linking allows the Hub to associate that server activity with the verified member profile.

• Permanent server player identifiers, PSN Online IDs and recorded PSN-name history.
• Connections, disconnections, sessions, character lives and time played.
• Timestamps and validated in-game X, Z and Y coordinates, including derived nearby place and zone names.
• Hits, damage, weapons, body areas, unconscious events, kills, deaths, survival causes and supporting evidence.
• Building, dismantling, destruction, flags, placements, storage, traps and other logged server activity.
• Per-server statistics, Player XP, ranks, prestige, challenges and leaderboard records.
• Zone entries/triggers, automatic enforcement results, ignore/immunity checks and accepted duel participation/results.
• Short-lived raw ADM evidence, parser/correlation results and durable canonical event/evidence links.

We do not sell personal information and do not use it for third-party advertising. We use it to provide the requested community service, operate linked accounts and fulfil our agreement with members.

• To authenticate members, apply roles and provide profiles, chat, social, event and notification features.
• To operate server status, feeds, player statistics, ranks, challenges, leaderboards, zones and duels.
• To operate the virtual economy, confirm catalogue payments, route collection items to the Trader team, complete eligible automatic deliveries and keep the member's fulfilment status in sync.
• To enforce server/community rules, investigate abuse, prevent manipulation, protect accounts and keep reliable evidence/audit records. We rely on legitimate interests in operating a safe and fair community, balanced against member privacy.
• To answer support, privacy and appeal requests and correct inaccurate links, statistics or moderation outcomes.
• To comply with legal obligations or protect a person's vital interests where applicable.

The Hub automatically checks Discord membership/roles, parses game logs, correlates related events, calculates statistics/progress and evaluates configured zones. A configured zone may trigger an automatic temporary or permanent server ban after immunity, ignore-list, nested-zone and active-duel checks.

Log evidence can be incomplete or ambiguous. Automated classifications and enforcement can be challenged through a private appeal.

A staff member reviews the stored evidence and configuration; the system is not used to make solely automated decisions that produce legal or similarly significant effects.

Public profile fields, public chat, selected badges and leaderboard results are visible according to the feature and your profile choices. Gameplay feeds may publish PSN names and event details, including approximate coordinates, to configured community Discord channels.

Authorised staff may access information needed for support, moderation, server operation or security. Routine private direct messages are available only to their participants through the normal Hub interface; a participant may submit relevant messages as evidence.

We use Vercel for the web application, Neon for PostgreSQL, Railway for background workers, Discord for identity and community automation, Nitrado for game servers, and KLIPY for GIFs and emoji. Supporter payments are handled by the payment provider shown at checkout: Stripe or PayPal.

These providers handle information under their own terms and data-protection arrangements; contact us for details of processing locations and applicable international-transfer safeguards.

The payment provider receives the payment and payer information you provide to it under its own privacy notice. The Hub uses verified payment records to apply benefits, reconcile refunds and investigate disputed or interrupted purchases.

We may disclose information where required by law or reasonably necessary to protect people, investigate fraud/abuse or respond to a security incident. Private cases, account-security records and staff-only attribution confidence are not published.

We keep information for the periods below or while needed for its stated purpose. A legal hold, active dispute, safeguarding matter or security investigation may require longer retention.

• Browser theme, accent and language preferences remain in local storage until changed or cleared. The language cookie lasts up to one year and is refreshed when the preference is applied.
• Sessions stop granting access at expiry, sign-out or revocation; their database records become eligible for deletion seven days later. Sign-in security events normally become eligible after 180 days, unless their retention deadline is extended for an investigation; cleanup runs on sign-in and in the background maintenance cycle, so outages or a backlog can delay removal.
• Parsed or ignored raw DayZ ADM records normally become eligible for cleanup six hours after ingestion. Unparsed records and raw evidence linked to a canonical death remain for processing or investigation; canonical events, identity and name history, character lives and permanent statistics remain operational server history.
• Reports, appeals and support cases are scheduled for review seven years after closure; staff and system audit records are scheduled for review seven years after the event. These reviews are manual, and records needed for an unresolved matter may be retained longer.
• Public chat history and context: retained as a continuing community record unless removed or anonymised for privacy, safety, moderation or legal reasons.
• Chat/Player XP ledgers, ranks, prestige, completed challenge records and leaderboard records: retained while the progression service operates, subject to published reset rules and account-deletion handling.
• Profile customisation choices are kept while the profile exists. Earned or discovered cosmetic unlocks are permanent and remain linked to the pseudonymous record after account deletion; access supplied by a paid membership or a verified Discord boost lasts only while its eligibility conditions are met.
• Reward-code claims keep a permanent record of the reward, claim time, any Chat XP boost start/end times and a car prize's delivery status to prevent duplicate grants and calculate earned XP. After safe account-deletion handling, claim history remains linked to the pseudonymous account record; private car locations and file backups are erased and unused requests cannot begin delivery. Redeemable code text is not stored in this history.
• Virtual economy ledgers, paid catalogue order snapshots and fulfilment history: retained while needed to reconcile balances, resolve delivery disputes and preserve the operational audit trail.
• Automatic-delivery X/Z coordinates: encrypted only while the delivery is pending or needs recovery, then permanently erased when you confirm receipt, staff records an evidence-backed delivery confirmation or its automatic subtotal is refunded.
• Supporter order, entitlement and safe request history: retained while needed to reconcile payments, benefits and disputes. Encrypted private request details are kept only while queued, processing or under active recovery, then permanently erased on fulfilment, cancellation, Discord disconnect or account-deletion handling.
• Friends, blocks, direct messages, event registrations and notification records: retained as described by the feature until removal, expiry or account deletion.
• A linked PSN ID: until replaced, unlinked, removed after a verified dispute or handled through account deletion; permanent server identity/name evidence may remain where necessary for server integrity, moderation and anti-evasion history.
• Protected backups: removed through the normal provider/logical backup rotation.

The Hub uses strictly necessary session/security storage and local preference storage for requested features. It does not currently use third-party advertising cookies.

We will explain and request any consent required before adding non-essential analytics, advertising or tracking storage.

Depending on where you live, you may request access, correction, deletion, restriction, portability or object to processing. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.

You can change profile/privacy/message settings, replace or unlink a PSN account, disable push notifications, request an export and request account deletion. We may need to verify your identity and may retain limited information where required for security, moderation, disputes or law.

If UK data-protection law applies and you are not satisfied with our response, you may complain to the UK Information Commissioner's Office.

Discord-linked features are available only to people who meet Discord's minimum age for their country. If you are below the age of majority where you live, a parent or legal guardian must agree where required.

We will update this policy before materially changing how information is used or introducing a new payment service, optional tracking or multi-community rental services. Material changes receive a new effective date and, where appropriate, an in-service notice.