1. Commercial account information
We process the Discord user identity used to sign in, servers that account can manage, selected server identifiers, authorization roles, session metadata, policy acceptance, TOTP enrollment state, and security audit events. OAuth credentials, TOTP secrets, recovery codes, bot tokens, and license keys receive separate protections and are never intentionally exposed in customer interfaces or routine logs.
2. Server operations
TRINITY processes the Discord events and identifiers required for enabled features, including messages that invoke commands or automations, tickets, moderation actions, voice-state events, member and role identifiers, channel routing, configuration, and delivery outcomes. Enabled modules send customer-facing records to configured Discord channels and retain only bounded operational state, safety invariants, and delivery metadata unless Cloud History is active.
3. Cloud History
If Cloud History is enabled, detailed ticket, moderation, staff, voice, and automation history is retained for up to 90 days within a 250 MiB compressed archive allowance per licensed server. Bounded aggregate statistics may remain longer. Active settings, open tickets, unresolved cases, schedules, entitlements, and security audit records are not treated as disposable archive data.
4. Security Intelligence
If a server subscribes to Security Intelligence, affected members must first open a short-lived page bound to that server and affirmatively consent. The service may then create a secret-keyed device identifier unique to that server, coarse browser, operating-system, language, timezone, screen, graphics, memory, processor, touch, cookie, and Do-Not-Track metadata, network-prefix correlation digests, and bounded risk signals. Customer servers never receive raw IP addresses, cross-server device matches, Discord credentials, or the owner server's private Security Identity Profiles. Detailed observations are retained for up to 30 days and are visible only to the server owner or an explicitly appointed Security Reviewer after recent TRINITY 2FA.
5. Private home-server security data
The owner's private verification system remains separate from this commercial dashboard. Customer activation does not grant access to its raw IP addresses, cross-context fingerprints, Security Identity Profiles, private security channels, or owner-only security commands. The commercial Security Intelligence module uses a separate tenant-scoped data path and cannot query the home-server data.
6. Service providers and access
TRINITY uses infrastructure providers to host the website, gateway, database, cache, and Discord integration. Customers do not receive direct database or cache credentials. Access is limited by server, role, session assurance, and operational need. We may preserve evidence required to investigate abuse, tampering, security incidents, disputes, or legal obligations.
7. Choices and requests
Server managers can disable features, change routing, export eligible Cloud History records, remove the bot, or contact support about access and deletion. Members may decline Security Intelligence collection; declining may prevent completion of a security-gated workflow but does not authorize hidden collection. Some records may be retained where necessary for license binding, fraud prevention, security, dispute handling, or legal compliance. Removing TRINITY from Discord does not automatically invalidate an activated license.
8. Security
We use encryption, keyed hashes, tenant isolation, short-lived reservations, mandatory dashboard 2FA, rate limits, audit trails, and secret-redaction controls. No system can guarantee absolute security; report suspected compromise through the official support route.