PRIVACY POLICY

1. Scope and test accounts

The server test covers Discord sign-in, Yunite Epic verification, solo queue, six-player 3v3 Draft, Matches, ratings, LFT, profiles and support. Real purchases, prize credits and withdrawals are disabled. Local Lab and synthetic sign-in are not enabled on this server, and local test accounts or balances were not imported. Separately operated local tests can use invented recipients and simulated financial data; do not submit real payment details to those tests.

External provider data is processed when a configured sign-in or connection flow is used. The Discord community and its support bot are separate services; publishing this policy does not start another bot or add new Discord permissions.

2. Account and connected-provider information

We process platform usernames and their history, avatar settings, account status, connection records, and document-acceptance versions and timestamps. Gameplay registration does not request a birth date or verify an 18+ status.

Discord sign-in supplies the Discord account ID, username and display name. The OAuth scope is identify; the current sign-in does not request your email address, Discord password or private messages. The access token is used on the backend for the profile lookup, not stored as a reusable linked-account token or sent to the frontend. Platform avatars are selected separately.

When you explicitly connect or refresh Epic through Yunite, the backend sends your linked Discord ID in the configured Discord-server context to Yunite's registration API. Yunite can return the verified Epic Account ID and current display name. PRIMEIT stores the verified connection, source and timestamps to preserve account continuity, prevent duplicate Epic ownership and support gameplay integrity. This is distinct from merely having a Discord tier role. Provider passwords are not collected. A provider outage is not proof of a different identity or permission to replace an existing connection.

Identity information is kept for the account and justified integrity/request handling, subject to the supported deletion and review process below. Earlier provider or test records, where retained, do not activate a retired sign-in flow. Epic Account Data is not sold or used for advertising.

3. Gameplay and platform records

Participation creates queue, accumulated-wait, Ready acceptance or miss, Draft captain and pick, roster, Match, result, seasonal ELO and calibration records. We also process submitted chat, evidence URLs and descriptions, reports, moderation findings, restrictions, support actions and audited corrections.

The all-six lobby Check In processes participant votes and withdrawals, quorum, launch and server deadlines, replies, closure reasons, confirmed misses and eligibility-based return-to-search outcomes. These are responses on PRIMEIT, not Fortnite attendance telemetry. Technical-pause timestamps, spectator agreements and bug evidence entered in Match Chat become part of that record. Host suggestions remain unsent local chat drafts until explicitly sent.

Historical records can reference retired features. Preserving those records does not make those features available in the current 3v3 test. A finding's expiry or a season reset does not erase the related audit history.

We do not automatically determine responsibility from the number of reports, browser inactivity or an automatic Draft pick. Server-confirmed events and reviewed evidence support the applicable decisions; review is available through official Discord support.

4. Public profiles, LFT and gameplay visibility

Public player surfaces can show a platform username, selected avatar, Premium styling and the current published search or eligible seasonal standings. Private initial ELO and calibration progress are not public Fortnite PR.

New LFT searches expire after 24 hours; editing does not extend expiry. Publishing or explicitly editing a search uses your linked Discord identity for contact. Contact is fetched separately by a signed-in user while the search is active and the author is available; public directory responses exclude Discord handles and provider IDs. Old private contacts are not automatically revealed.

Where a trusted tier integration is configured, linked Discord identifiers, allowlisted role observations, observation times and availability status can support temporary tier badges and filters. Private provider IDs and role snapshots are not public profile data. Stale observations do not qualify for current filters, and a failure does not create T6. This does not authorize collecting unrelated Discord messages or roles. Epic identity verification uses the separate explicit Yunite flow described above.

Draft participants receive the roster information needed to pick and play. Team Chat is limited to the relevant side and authorized review; Match Chat is limited to the relevant participants and authorized staff. Chat is part of the gameplay record, not a personal messaging service. Private evidence, support history, account settings and provider IDs are not public profile data.

5. Discord support and evidence services

If you use community support, the PRIMEIT bot processes your Discord identifier, the server and ticket-channel identifiers, category, supplied nickname, references, description, messages, timestamps and staff actions. A supplied nickname alone does not prove website account ownership.

Tickets are accessible to the requester and authorized support roles; Discord server administrators can technically access private channels. The bot can retain private snapshots containing message text, actions, attachment metadata and links. After a closed ticket's history has been saved and verified, its Discord channel may be deleted without a seven-day wait. If archival fails, the channel is not deleted. Deleted messages cannot be recovered by this process.

Ordinary tickets preserve attachment metadata and links, not copies of the files; external attachment links may later expire. Tickets marked Save for review copy available attachment files before channel deletion, subject to archive safety limits. Applying a hold later cannot recover already deleted or expired material. Managed ticket content is retained for 30 days after the last closure, and the minimal ticket card for 365 days. A Save for review hold suspends this expiry until released; original deadlines then apply, not a new retention period. Failed archival/deletion cases may require longer retention for resolution. These managed-bot periods do not control Discord's own retention, staff-downloaded copies or independently managed backups.

Submitting an evidence link makes it available for the supported review. The link's host processes any visit under its own policy. Evidence sources include YouTube, Twitch, Streamable, Medal and Imgur under the platform's link policy. Do not include unrelated private information or credentials in evidence.

6. Security information, cookies and analytics

Essential cookies support sessions, temporary OAuth state and account-linking flows. Persistent session records use a one-way hash of the session token. Session expiry or revocation ends its authority. Technical processing can include network addresses, request times, routes, response status, User-Agent information and logs needed for security, rate limiting and troubleshooting.

The current website does not include third-party analytics counters, tracking pixels or session-replay integrations. The previous Yandex Metrica, Rambler and LiveInternet integrations have been removed. Operational server/security logs are separate from third-party visitor analytics. Any future analytics change requires a separate configuration and an updated disclosure, with consent where required; this policy does not enable tracking.

7. Purposes and recipients

We use information to authenticate accounts, verify connections, operate the test and Matches, calculate ratings, display supported public identity, support player discovery, review evidence, handle requests and protect security and integrity. The current server does not process real Shop payments or payouts.

Access follows participant, staff and account permissions. Infrastructure providers support operation and storage. Discord and Yunite process data for sign-in, community support and verification; chosen evidence hosts and email services process relevant visits and communications under their own policies. Their processing can occur in different countries; connected-provider data does not necessarily stay in one country.

Information may be provided where an applicable legal obligation requires it. The project does not sell personal information or use Epic data for advertising.

8. Storage, security and retention

Application records and operational state are stored on the project's service infrastructure. Recovery copies can have separate retention; deleting an application record does not promise instant erasure from every retained backup. Discord, Yunite, email and evidence hosts have their own storage locations and retention.

Safeguards include authenticated access, server-side validation, role checks, protected OAuth flows and audit records. Real payout-recipient collection is disabled on this server. Separate isolated local tests use encrypted fields and restricted, audited access for synthetic recipients. Do not send real payment details, card numbers or CVV, passwords, private keys or seed phrases.

Account and connection records are kept while needed for their account and supported request handling. Session authority ends at expiry or revocation; temporary verification state is time-limited. Match, chat, evidence, moderation, support, acceptance and test financial records can remain as audit history. The project has not adopted a blanket automatic deletion period for all of these categories; test closure does not itself promise immediate erasure. Retention must remain justified by its purpose and applicable requirements.

9. Access, correction and deletion requests

Contact contact.primeit@gmail.com or official PRIMEIT Discord support to request access, correction, deletion, or review of an account/data issue. Tell us which account and information your request concerns, without sending passwords or login codes. Ownership verification may be required before account-specific action.

The supported Epic Account Data deletion flow verifies ownership and can remove the connected Epic record and covered display-name copies. Active or disputed gameplay and integrity obligations may require review before completion. Deleting Epic data does not require deleting every non-identifying Match or audit record and does not promise unrestricted Epic relinking.

Other records are assessed by category, purpose and applicable requirements. If information must be retained, the response should explain the reason and available review route. Statutory privacy rights apply where the relevant law provides them. This test policy does not replace a separate consent where one is required or promise a request deadline the process has not established.

10. Updates and contact

New registrations record the active policy version. Historical accepted versions remain stored. A later document does not rewrite previous acceptance records. Material changes to processing or a future public/payment launch need an updated policy and any notice or consent required for that change.

The current policy is available at https://primeit.pro/privacy. Contact remains contact.primeit@gmail.com until a replacement is published. Operator and paid- service details will be addressed separately before any commercial launch.