Qbit OPS Staff Privacy Policy

Qbit OPS may collect Roblox account identifiers provided through OAuth2, including Roblox UserId, username, and display name when available.

The system may also collect session identifiers, authentication events, permission decisions, requested routes, staff actions, timestamps, request IDs, device and browser metadata, masked network metadata, approximate region from security providers, rate-limit events, security events, audit records, and deployment or health metadata.

When using staff tools, you may provide reasons, case IDs, review notes, form fields, search filters, game identifiers, player identifiers, moderation context, CMS content, export requests, or other operational inputs.

Do not enter secrets, private credentials, unnecessary personal data, or unrelated sensitive information into Qbit OPS fields.

Qbit Games uses staff and operational data to authenticate users, authorize access, enforce permissions, secure staff accounts, investigate incidents, prevent abuse, maintain service reliability, support audits, process staff actions, operate Roblox game integrations, and satisfy safety, legal, and operational obligations.

The server is the source of truth for staff identity, permissions, object access, action results, and audit records.

Access and actions may be logged, monitored, reviewed, retained, and audited. Logs are designed to capture useful operational facts while avoiding secrets, cookies, raw tokens, connection strings, private keys, and unnecessary sensitive payloads.

Some pages may show last updated or stale states from server timestamps so staff can understand data freshness without exposing private implementation details.

Staff data and operational records are available only to authorized Qbit Games staff, approved service providers, and systems that need the information for security, operations, support, compliance, or maintenance.

Qbit Games may disclose information if required to protect users, enforce policies, respond to legal obligations, investigate abuse, or maintain platform integrity.

Qbit Games keeps audit, security, compliance, and operational records for as long as needed for safety, legal, reliability, abuse-prevention, financial, moderation, and business purposes.

Low-value technical rows may be cleaned up or aggregated to reduce storage overhead. Records subject to security review, audit requirements, legal hold, active incidents, or compliance needs may be retained longer.

Qbit OPS uses role-based access, object-level checks, session validation, origin and request validation, rate limits, audit records, and operational monitoring. These controls reduce risk but do not replace your responsibility to use the system safely.

Questions about this policy, access records, or staff data handling should go through the approved Qbit Games staff leadership or security channel.

This policy may be updated when Qbit OPS changes, security requirements change, or privacy and operational requirements change. Updated versions may require acceptance before the staff system opens.