Privacy

Overview

This Privacy Notice explains what information PVERSE may process through the Platform, why that information may be used, how it may move through platform systems, and how account, security, payment, and activity data may be handled inside PVERSE.

PVERSE is an evolving crypto-native platform built around account-based participation, persistent mining gameplay, internal balances, internal marketplace systems, guild structures, trust-based anti-abuse controls, and related platform functions.

Platform Scope

This Privacy Notice applies to information processed through PVERSE in connection with:

• the PVERSE website
• account registration and sign-in
• password, passkey, OTP, and recovery-related security flows
• mining, progression, balance, and reward systems
• guild, treasury, voting, karma, and contribution systems
• marketplace and user-to-user item exchange systems
• crypto-native payment and settlement flows
• trust score, anti-bot, and account integrity systems
• operational monitoring, abuse review, and security review

This Notice is about how information is handled inside PVERSE platform systems.

No Email-Based Accounts

PVERSE does not currently use email as a standard account identifier.

PVERSE does not currently require email for:

• account creation
• sign-in
• standard recovery flow
• ordinary platform access

At this time, PVERSE is designed around platform-native account credentials rather than email-based identity.

• no standard email signup
• no standard email login
• no standard email recovery flow

Account Information

PVERSE may process account-related data such as:

• username
• display name
• password hash
• passkey status or passkey-linked registration state
• recovery code state or recovery-related verification state
• OTP-related status
• account status flags
• internal account integrity signals

PVERSE is built to operate without standard email-based accounts.

Device and Session Information

PVERSE may process technical and session-related information such as:

• IP address
• browser type
• operating system
• device-related signals
• session identifiers
• login timestamps
• request logs
• access environment signals
• device continuity signals

This information may be used to keep sessions stable, protect accounts, and detect abnormal access patterns.

Security, Trust, and Anti-Abuse Signals

PVERSE may process or derive platform integrity signals such as:

• repeated failed login patterns
• multi-login attempt patterns
• suspicious activity indicators
• abnormal session behavior
• VPN, proxy, relay, or TOR indicators
• recovery abuse indicators
• account risk flags
• device continuity indicators
• anti-bot signals
• trust score inputs
• enforcement or review history

These systems exist to protect platform integrity, reduce automation abuse, reduce manipulation, and keep long-term participation more stable.

Platform Activity Information

PVERSE may process records of in-platform activity such as:

• mining activity
• refining or processing activity
• reward and progression activity
• internal balance changes
• guild participation
• guild treasury activity
• contribution records
• karma and participation-linked activity
• voting-related activity
• marketplace actions
• listings, exchanges, and internal trade events
• referral or participation-linked identifiers
• system event history

Crypto-Native Payment Information

Because PVERSE is crypto-native, PVERSE may process payment-related information such as:

• wallet addresses used in supported payment flows
• supported chain or network selection
• token type
• transaction hashes
• deposit or settlement status
• confirmation state
• quote timing data
• mismatch indicators
• payment review signals
• verification and settlement logs

PVERSE does not currently use standard fiat-based account payment as part of its normal platform flow.

Support, Security, and Review Information

Where needed, PVERSE may also process records related to:

• support requests
• abuse review
• suspicious account review
• security incident review
• payment mismatch review
• enforcement review
• platform integrity review

Why PVERSE Uses Information

PVERSE may use processed information to:

• create and maintain accounts
• authenticate users
• support login, passkey, OTP, and recovery systems
• operate mining, reward, balance, guild, marketplace, treasury, and platform systems
• verify crypto-native payment flows
• maintain platform stability and security
• detect bots, fraud, manipulation, automation abuse, or unauthorized access
• evaluate trust and account integrity signals
• enforce platform rules and internal platform integrity standards
• review suspicious actions, accounts, payment flows, or marketplace behavior
• maintain logs, audit internal events, troubleshoot issues, and improve performance

Cookies and Similar Technologies

PVERSE may use cookies and similar technologies for purposes such as:

• keeping sessions active
• maintaining sign-in state
• supporting security protections
• protecting against repeated abuse attempts
• preserving technical preferences
• improving reliability and performance

Some of these technologies may be necessary for the platform to function correctly.

How Information May Move Through Platform Systems

PVERSE may use information inside its own platform systems and with limited technical providers that support platform operation.

Depending on the system, information may move through:

• hosting and infrastructure systems
• security and integrity systems
• payment verification or settlement infrastructure
• blockchain node or monitoring infrastructure
• performance and reliability tooling
• abuse review and operational tooling

PVERSE aims to keep information movement tied to platform operation, security, verification, and technical maintenance.

Trust Score and Automated Integrity Review

PVERSE may use automated and manual systems to evaluate account integrity and platform risk.

These systems may consider signals such as:

• login behavior
• device continuity
• session irregularity
• recovery behavior
• network-level indicators
• suspicious repetition
• anti-bot signals
• payment anomalies
• marketplace behavior
• account activity patterns

These systems may affect:

• access to features
• withdrawal eligibility
• marketplace access
• guild or voting eligibility
• reward treatment
• review timing
• delay, restriction, or suspension of actions

PVERSE does not necessarily disclose all internal logic, thresholds, detection methods, or trust heuristics behind these systems.

Retention and Platform History

PVERSE may retain information for as long as reasonably needed to support:

• active account operation
• security and recovery functions
• platform integrity
• abuse detection and review
• payment verification
• marketplace history
• treasury and guild event history
• internal audit and troubleshooting
• dispute review
• long-term platform continuity

Public and Platform-Visible Information

Some information may be visible inside platform systems depending on how features are designed.

For example, the Platform may display or expose certain internal information such as:

• usernames or display names
• guild affiliation
• guild roles
• contribution indicators
• leaderboard placement
• marketplace listings
• treasury or participation-related outputs
• wallet-linked transaction states where relevant to platform function

Users should understand that participation in platform systems may cause limited information to become visible within those systems by design.

User Control and Account Responsibility

Users are responsible for:

• protecting account credentials
• protecting recovery information
• protecting device and browser access
• using secure wallet practices where applicable
• reviewing visible platform actions connected to their account

Because PVERSE does not currently use standard email-based identity, account recovery and verification may depend on platform-native account data and internal verification methods.

Children

PVERSE is not intended for users who are not legally permitted to access or use the Platform in their environment.

If PVERSE becomes aware of clearly improper account use in this area, it may restrict or remove the relevant account data or platform access.

Security Approach

PVERSE uses platform-native technical and operational measures intended to protect accounts and platform systems.

These may include:

• password hashing
• passkey support
• recovery code architecture
• OTP-linked security states
• session protections
• trust score systems
• anti-bot systems
• device continuity checks
• payment verification logic
• internal logs and review controls

No system is perfect or risk-free. Users remain responsible for protecting their own access environment and credentials.

External Services and Public Networks

PVERSE may depend on or interact with external technical systems such as:

• blockchain networks
• wallet software
• node infrastructure
• monitoring infrastructure
• hosting providers
• performance tooling

PVERSE does not control public blockchains or third-party wallet environments.

Users should assume that some blockchain-related actions may be independently visible on public ledgers outside the Platform.

Changes to This Privacy Notice

PVERSE may update this Privacy Notice over time.

If the platform structure, data flow, payment systems, security systems, or account systems change, this Notice may also change.

The effective date and last updated date may be revised accordingly.