Information we store
When you sign in with Discord, we store your Discord user ID, username, display name, avatar reference, verified email address when available, email-notification preference, account creation time, and latest sign-in time. We also store a hashed session identifier and session expiry so you can stay signed in and sign out.
The Servers page checks your Discord server list and permissions to show servers you can manage where Collective is installed. An encrypted sign-in cookie lets the website request that list until the Discord access expires. We do not store your server list in the account database.
If you send a support request, we store its topic, subject, message, creation time, status, selected support department, and conversation replies with your account. This includes formatted message text and any image files you upload. Support-team and management-team applications also store the experience and availability you submit. Moderation appeals store a reference and a snapshot of the selected action’s public reason, issue date, expiry, and lifted status at submission; this record remains attached to the ticket if the action is later updated. Application fields and moderation snapshots are available to you and authorized support staff, and are excluded from AI context. Authorized support staff can access conversations in their assigned departments. Staff with the necessary permission can add private notes, assign or transfer conversations, and escalate them to the Core Team. Internal notes are not shown to customers. Please avoid including sensitive information or credentials.
Account notices and moderation
We store account notices, warnings, suspension or ban reasons, issue dates, expiry dates, revocations, and the staff account that issued each action. Private member notes are visible only to staff with the relevant permission. We also record staff permissions, support-department access, and an audit of management changes. These records help us explain and review decisions, enforce restrictions, and protect the service.
Suspended and permanently banned accounts can still sign in to view the reason and expiry and contact support to appeal. Signing someone out revokes their current website sessions; it does not remove them from Discord.
Images
Uploaded images are stored in the same database used for support. Image endpoints require a signed-in session and check access to the conversation or account notice. Images in private notes require the corresponding staff permission. Files are kept as uploaded and may contain embedded metadata. Do not upload credentials, payment-card details, or information you are not authorized to share. Unused draft images become eligible for cleanup after 24 hours and are removed during subsequent uploads.
How we use it
We use this information to identify your account, maintain your session, display your profile, show your requests, and handle support. We don’t sell account or support data or use it for targeted advertising.
Discord and other providers
Sign-in requests Discord’s identify and email permissions. We use the verified address Discord provides for welcome emails, support-ticket notifications, account notices, moderation updates, and permission or support-access changes. We don’t request your server list, Discord messages, or password. Discord access tokens are used on the server to retrieve your profile during sign-in and are not saved to our account database or browser session.
Discord processes authorization and serves avatar images. Supabase stores our account, support, moderation, and status records, including private uploaded images. Hosting and database providers process the information necessary to run the website, and may maintain operational logs such as request timestamps and IP addresses under their own policies. This website does not add an analytics or advertising tracker.
AI support
When enabled, new tickets can receive clearly labeled AI assistance while waiting for staff. OpenAI processes a limited selection of public text from that ticket together with relevant published knowledge articles to generate replies. Authorized staff maintain the knowledge base; articles marked as published may be used or quoted in customer answers. Unpublished drafts are excluded. We exclude internal staff notes, images, private contact details, credentials, and other customers’ records, and remove recognized email addresses, links, and credential patterns before sending text. To prepare action proposals, AI may receive the current ticket owner’s relevant public moderation records and current access settings. Private moderation instructions are checked by the server and are not sent to AI. AI proposals and a separate AI recheck are stored for review. No proposed action is executed until one authorized staff member approves with the required permissions. Private instructions can prevent AI-generated changes. This filtering cannot identify every sensitive detail; do not include secrets. We request that generated responses are not stored through the API; OpenAI may retain service or abuse-monitoring data under its own policies. AI replies are stored in your ticket and can be wrong. Select human support when opening a ticket, or request a human during the conversation. Only an explicit request for a human, including a written request, or a manual staff claim or assignment ends AI assistance. Human requests and claims are recorded in the chat. Authorized staff receive portal alerts for pending human requests and AI proposals in their assigned departments. Errors or usage limits may pause replies without transferring your ticket. AI cannot approve its own proposals or execute changes without staff approval. Financial and application-acceptance decisions remain with authorized humans.
Support email
Resend processes welcome emails, ticket confirmations, staff-reply notifications, account notices and moderation updates, permission and support-access changes, and incoming replies. Outgoing messages use noreply@collectivebot.xyz. Each ticket has a unique reply address and email message identifiers to keep its conversation together. A reply from your current verified address is checked for sender authentication and added to your ticket as a customer message. Private staff notes are never sent as customer email notifications.
We store a delivery queue, provider/message IDs, thread-routing tokens, and processing results to prevent duplicate notifications and repeated imports. Sent queue entries discard their body copy; pending entries retain the message until delivery is confirmed. Incoming email is stored as plain-text conversation content with a source label. Quoted email history is trimmed where possible. Email attachments are not imported; use the portal for images. Resend may retain processed email under its own service and retention settings.
Welcome and ticket emails are sent automatically to your verified Discord address. Account notices, warnings, session revocations, suspensions, bans, lifted actions, and individual permission or support-access changes also trigger account emails. These account notifications are sent independently of ticket-email preferences. Private staff notes are never emailed to the member. You can reply to an existing ticket email to continue the conversation in the portal. Old accounts without a verified address must sign in with Discord again to connect email. Copies already delivered to a mailbox or processed by the provider cannot be recalled by deleting your website account.
Cookies and sessions
A necessary HttpOnly cookie keeps you signed in for up to seven days. A short-lived cookie verifies the Discord sign-in request and is cleared when the callback completes. Production sessions are shared between trusted thecollective subdomains. Signing out revokes that session in the database and clears its cookie.
Retention and deletion
We keep your account and support requests until you delete the account or ask us to remove them. Expired session records are cleaned up during subsequent sign-ins. You can delete your account in the portal; this removes your profile, sessions, staff permissions, support access settings, owned tickets, queued emails, email-thread routing records, uploaded images, and all replies you wrote from the active database. Notices and private member notes are also removed, except for an active suspension or permanent ban: its Discord ID, reason, staff ID, issue date, and expiry are retained to enforce the restriction if you sign in again. Once that restriction expires or is revoked and there is no account, the record is removed during the next daily cleanup. Management audit entries are retained for up to 180 days and removed during daily cleanup when the service is used. Replies in tickets owned by other customers are also removed when you delete your account. Copies in hosting backups or operational logs may remain according to the provider’s retention settings.
Signing in again after deletion creates a new account. Deleting an account does not remove an active restriction or provide a way around a ban. Deleting your account here does not delete your Discord account.
Questions or corrections
Your public profile is refreshed when you sign in. For other questions, corrections, or a privacy request, contact the team. If you can’t sign in, you can try signing in again or check the service status page. Web tickets require a signed-in account.
Changes
We will update this page when our data handling changes. The date above shows the latest update.