Privacy Policy & Data Privacy Framework
Effective Date: June 18, 2026 · Document Version: 2.1.0-PRIVACY
This Privacy Policy (the "Policy") describes how our platform, its operators, and administrative team (collectively, the "Company", "Site", "We", "Us", "Our") collect, protect, utilize, and manage the data generated during your interaction with our storefront, support systems, messaging channels, and payment wrappers (collectively, the "Services").
We are committed to operating a secure commercial ecosystem. By accessing our Site, opening an administrative support ticket, maintaining an active monthly subscription tier, or completing a virtual asset acquisition, you explicitly acknowledge and agree to the data collection protocols outlined below. If you do not consent to these data processing rules, you must cease using our Services immediately.
1. Data Categorization & Methods of Collection
We categorize the information processed during your session into two distinct vectors: information you actively provide to us, and systemic data captured passively by our infrastructure.
1.1 Voluntarily Provided Information
During the execution of a commercial transaction or account initialization, you may actively transmit specific identifying data sets, including:
- Account Identifiers: Discord User IDs, usernames, and associated alphanumeric profile markers.
- Transaction Metadata: Transaction identification numbers, receipt copies, billing email addresses, and crypto-wallet public keys.
- Communication Logs: Text-based inquiries, chat logs, and media submissions generated within our ticket modules.
1.2 Automated Infrastructure Telemetry & Network Protocol Logging
To maintain absolute operational stability and fulfill corporate compliance standards, our servers utilize automated background auditing systems. Similar to enterprise-level network architectures, our system logs real-time device signatures and network behaviors. This passive collection framework continuously tracks:
- Network Identifiers: Full Internet Protocol (IP) addresses (including IPv4 and IPv6 variants), Subnet masks, and Internet Service Provider (ISP) hostnames.
- Geographic Telemetry: Macro- and micro-level geolocation metrics derived automatically from standard border gateway routing paths.
- Hardware & Environment Profiles: Browser user-agent strings, system display resolutions, operational operating system (OS) builds, and device hardware signatures (browser fingerprinting).
- Clickstream Analytics: Time-stamped sequences of pages accessed, session durations, exit links, error logs, and transactional completion rates.
- Proxy/Mask Detection Data: Telemetry checking for the presence of Virtual Private Networks (VPNs), Tor nodes, commercial proxies, or residential relay scripts.
2. The Legal & Operational Basis for Data Processing
We do not harvest data for third-party monetization or broker marketing lists. All automated data compilation — specifically regarding network topology and IP address recording — is processed under the strict legal framework of Legitimate Interest and Contractual Execution, serving the following precise goals:
[User Action: Visit / Purchase]
│
▼
[Automated Telemetry Shield] ──► Logs IP, Hardware, and Geolocation
│
├─► 1. Anti-Fraud Analysis (Cross-references payment vs origin)
├─► 2. Cyber Defense Network (Blocks DDoS and Bot Arrays)
└─► 3. Chargeback Mitigation (Provides legal proof of delivery)2.1 Commercial Fraud Prevention & Risk Mitigation
The primary catalyst for maintaining continuous network logging is the identification and destruction of financial exploitation patterns. By cross-referencing incoming network IP coordinates with the physical origin of the payment method, our security array isolates card-not-present fraud, identity theft, and unauthorized secondary subscription access attempts.
2.2 Network Infrastructure Defense
Our web properties and transaction nodes are subject to continuous malicious exploits. Passive logging allows our automated firewalls to identify, rate-limit, and permanently drop connections originating from malicious bot networks, scraping arrays, credential-stuffing engines, and Distributed Denial of Service (DDoS) vectors.
2.3 Contractual Verification & Dispute Resolution
Because digital item delivery and monthly role distribution occur instantaneously, we require definitive system proofs to counter fraudulent chargebacks. Your IP logs, session durations, and ticket records serve as an unalterable digital receipt proving that the individual who authorized a payment is identical to the entity that extracted the digital value.
3. Data Sharing, Pipelines, & Third-Party Exposure
We maintain strict internal boundaries regarding data handling. We do not sell or rent user information. Your data is routed through third-party pipelines only under the following explicit operational conditions:
- Payment Wrappers & Processors: Financial information is transmitted directly through encrypted channels to our third-party payment gateways (e.g., Stripe, PayPal, cryptocurrency networks) to finalize checkout requirements.
- Fraud Prevention Agencies & Chargeback Disputes: In the event that a user violates the Terms of Service by filing a fraudulent chargeback or transaction reversal, the Company reserves the unchallengeable right to forward full communication logs, system telemetry, and matching IP addresses to the disputing bank, card processor, or legal representatives to successfully challenge the claim.
- Legal Compliance & Law Enforcement: We will disclose captured identity details and network logs to external authorities only if compelled to do so by a legally binding subpoena, court order, or valid regulatory mandate.
4. The Data Eradication Loophole Patch (Retention & Rights)
4.1 Data Retention Timelines
Operational data, security logs, and transaction fingerprints are stored within our secure cloud databases for as long as is contractually necessary to safeguard our business interests. Standard operational metadata is periodically cleared; however, telemetry associated with financial transactions, account blacklists, server bans, and fraud vectors is retained indefinitely.
4.2 Exclusion to Data Deletion Requests
THE ANTI-FRAUD ERADICATION EXCLUSION: While users may request the modification or erasure of their personal profiles, the Company explicitly retains the right to DENY data deletion requests regarding IP addresses, transaction footprints, and ban records if that data is actively utilized for ongoing fraud prevention, defending against financial disputes, maintaining server safety, or ensuring compliance with active contracts.
You cannot use "the right to be forgotten" or privacy deletion requests as a tool to wipe out your transactional history prior to initiating a fraudulent chargeback.
5. Reinforced Security Protocols
We utilize industry-standard cryptographic techniques to safeguard the data stored within our server arrays.
- All network logs and identity vectors are encrypted at rest using AES-256 protocols and are encrypted in transit via Transport Layer Security (TLS) pipelines.
- Physical access to administrative panels and data storage tools is heavily restricted, relying on Multi-Factor Authentication (MFA) and granular, permission-based access structures limited solely to core system operators.
6. Children's Privacy & Integration of External Platforms
6.1 Strict Compliance Safeguards for Minors
Our services are designed for individuals who possess full legal capacity or operate under absolute parental guardianship. We do not knowingly compile data from children under the age of thirteen (13). If a minor has initialized an account pipeline without parental consent, the parent or guardian may submit a request through our ticketing framework to have the associated cache purged, provided it does not conflict with our anti-fraud retention needs.
6.2 External Platform Interactivity Disclaimer
Our Services operate in close coordination with external software ecosystems, including Roblox Corporation and Discord Inc. This Privacy Policy applies strictly to data pipelines native to our proprietary storefront and ticket configurations. We possess zero authority or oversight regarding the data collection mechanics, privacy settings, or tracking algorithms managed by external corporations. We encourage users to audit the respective privacy frameworks of those platform environments independently.
7. Unilateral Modifications and Privacy Acceptance
We reserve the absolute right to alter, update, expand, or completely rewrite this Privacy Policy at our sole discretion, at any given moment, and without delivering direct notifications to individual user endpoints. The updated operational version will always display a revised "Last Updated" timestamp at the apex of the document.
Your continued navigation of our Site, submission of currency, or active utilization of monthly paid tiers following structural adjustments indicates your unconditional, retroactive acceptance of the updated Privacy Policy framework.