Privacy Policy
This Privacy Policy explains how PGuardian handles information used to provide Discord community management, moderation, analytics, tickets, and workflow features.
Last updated: 28 August 2026
Privacy Policy ยท Terms of Service
Scope and Information PGuardian Processes
PGuardian is a Discord community management, moderation, protection, ticket, and dashboard service. This policy describes information processed by the PGuardian bot and dashboard.
PGuardian processes Discord server or guild identifiers, channel IDs, role IDs, user or member IDs, usernames and display names, membership and role state, join and update timestamps, and server configuration selected by authorized server administrators when needed to provide enabled features.
Depending on enabled features, PGuardian may process moderation and warning records, Guardian and Shield events, ticket data and transcripts, member-role snapshots for recovery and protection, invite and webhook metadata, activity aggregates, dashboard OAuth and session-related data, and operational records used for abuse prevention and reliability.
Message Content and Member Data
PGuardian processes ordinary server message content only where an administrator has enabled features that must inspect messages as they are posted, including AutoMod, anti-spam, repeated-content, mention-abuse, invite, link, scam, anti-raid, protection, configured logging, template, ticket, transcript, and support workflows. A bounded in-process cache may temporarily hold recent message details for edit and deletion logging. Protection records may include a content preview of up to 500 characters, and staff-facing Discord logs may include relevant before, after, or deleted content.
Ticket transcript generation reads a bounded channel history and uses a temporary workspace that is removed after delivery. Transcript and log copies delivered to Discord remain subject to the destination server's administrator controls and Discord's retention practices.
PGuardian uses Guild Members data for join, leave, ban, and member-update workflows; Anti-Raid and welcome behavior; role connections; permission checks; member-role snapshots; and role recovery or protection. It does not request or use members' Presence data.
Message content and other Discord API data are not used to train machine-learning or artificial-intelligence models. If a server separately enables an AI reply feature, selected conversation content may be sent to an AI inference provider to answer that request; broad Message Content access is not justified by that feature.
How Information Is Used
Information is used to operate moderation and server-protection features, enforce configured AutoMod rules, support anti-raid detection, recover role or channel state where supported, maintain configured staff logs, operate ticket workflows, provide dashboard settings and access control, and keep the service reliable.
Authorized server administrators may see configured logs, ticket transcripts, moderation records, dashboard summaries, or recovery data according to their Discord permissions and the destinations and features their server has configured.
PGuardian does not sell personal data, use server data to build unrelated consumer profiles, or send marketing direct messages. Discord API behavior and Discord-side data remain subject to Discord's own terms and policies.
Retention
Retention is feature-specific. The recent-message cache is process-local and bounded by entry count. Temporary transcript workspaces are removed after delivery. Dashboard administrative audit records default to 30 days. Dashboard activity projections have separate configurable defaults, including 90 days for raw activity events, 180 days for member events and hourly counters, and 730 days for member snapshots.
When PGuardian leaves a server, its current configuration lifecycle marks that guild for a 30-day retention period. Legacy moderation, warning, protection-preview, activity-aggregate, ticket-runtime, and member-role snapshot stores do not yet share one automatic cross-store deletion schedule. After identity and guild-scope verification, relevant PGuardian-held records in those stores are removed promptly through a reviewed, confirmation-bound administrative deletion procedure or an applicable feature-specific control. PGuardian does not claim universal automatic expiry, and will not represent removal of the bot by itself as immediate deletion from every store.
Logs and transcripts delivered into Discord may remain until deleted by an authorized server administrator or retained by Discord. Backups and provider systems may retain limited copies for their normal recovery, security, or legal periods.
Access, Correction, and Deletion Requests
An individual Discord user may request access to or deletion of PGuardian-held data associated with that user by contacting the support server and providing the relevant Discord user ID and guild context. A server owner or authorized administrator may request guild-scoped deletion after authority over the guild is verified.
Server administrators can reduce future collection by disabling features, narrowing exempt users, roles, or channels where supported, changing log or transcript destinations, and deleting Discord-side logs or transcripts they control. Removing PGuardian stops new guild events from being received, but does not by itself complete the legacy cross-store deletion described above.
Requests are handled promptly after identity and scope verification through a reviewed user-and-guild or whole-guild deletion procedure. A request may be limited where a documented security, abuse-prevention, or legal retention obligation applies, or where copies are controlled by Discord or another provider; support will explain the applicable status and scope rather than silently retaining user-identifiable data or promising a universal automated deadline.
Security and Access Controls
PGuardian uses encrypted network transport, guild and tenant scoping, Discord permission checks, restricted dashboard sessions, CSRF protections, secure cookie settings, and service-specific database roles. Operational access is limited to authorized service or owner/operator paths.
Durable AI conversation content, when that separately gated feature is enabled, uses application-level encryption. Some legacy JSON and SQLite product stores are not application-encrypted and instead rely on restricted hosting, filesystem, service, and operator access. No security measure can guarantee absolute protection.
Sharing, Providers, and International Processing
PGuardian depends on Discord APIs and may use hosting and database infrastructure such as Render. Dashboard login, billing, or other optional features may involve the applicable OAuth or payment provider. If a server separately enables an AI reply feature, the minimum selected request context may be processed by OpenAI for inference under that feature's controls.
PGuardian does not sell personal data. Information may be processed in countries where Discord, Render, OpenAI, OAuth, payment, or other necessary service providers operate, subject to their contractual and legal safeguards. Authorized server administrators may also receive data in the Discord destinations they configure.
Policy Updates
This policy may be updated when PGuardian's features, providers, or data practices change. The public page will identify its latest update date. Material changes should be reviewed before affected functionality is enabled or expanded.
Contact
For questions about this page or help with PGuardian, join our support server: Join our Discord support server.