Privacy Policy

WE BLAST PRIVACY POLICY Operator: Christian Turner Privacy requests: christianturnerelectric@gmail.com 1. Scope We Blast is a private, nonprofit community app for friends. This policy covers information handled by its Discord app and associated dashboard. The operator identified above is responsible for this processing. Discord and other external services also process information under their own policies. 2. Information we handle and why Discord identity and access. We use Discord user and server identifiers, display names, avatars, relevant membership and role information, and channel/message identifiers to recognize users, enforce permissions and deliver features. Some features also use voice-channel membership or member-join events. Dashboard sign-in. Discord sign-in requests the identify permission. The dashboard exchanges the authorization code with Discord and uses the resulting identity to check access. It stores a session-token hash, user ID, display name and expiry. The login flow does not request your Discord password or the email OAuth scope. The web service also handles connection information, including an address used for short-lived login rate limiting. Community tools. We store information you submit or create through the app, such as character names, classes and levels; professions, skills, recipes and availability; crafting requests and replies expressed through request status; group membership; raid signups, roles and attendance; and event descriptions, schedules and RSVPs. These records support organization, display, updates and action history. Reports and moderation. Reports can contain a reporter ID, reported member ID, title, description and Discord message link. Staff actions can add status changes, internal notes, reasons, decisions, actor IDs, timestamps and delivery outcomes. We use these records to handle reports, administer server rules, review actions and investigate problems. Avoid submitting unnecessary sensitive information about yourself or others. Participation features. When enabled, XP and rewards use eligible message events, qualifying voice participation and staff-verified awards. The ordinary chat-XP handler does not read message bodies or attachments. Stored information includes member-linked XP totals, daily and seasonal records, achievements and eligible collectible records, plus aggregate activity counts. Voice participation features use presence/state information rather than recordings of members' conversations. Operational information. We keep command/action records, identifiers, timestamps, results, errors and security records to operate and troubleshoot the app. Current bot I/O diagnostics use a limited metadata projection rather than command arguments or private response bodies. This does not establish that historical logs, other operational logs or backups contain no personal information; these require separate review. Reusable DM tools retain delivery identifiers and may inspect a bounded portion of the bot conversation to recover a previously sent bot card. Music DJ is currently unavailable. Previously retained Music records and credentials have not been erased merely by disabling the feature. Privacy requests and notification choices. The privacy-control feature stores your request type and text, Discord identity, current review status/version, latest reply and operator response, timestamps and audit metadata. Only you and the authorized operator can read your request through the feature; operator audit metadata stays restricted. It also stores your optional moderation-DM choice, notice revision and change history. Optional moderation DMs default off and can be enabled or withdrawn by the recipient. They contain the case action and member-facing reason; moderation enforcement and restricted staff records remain in place regardless of this choice. Already-sent messages are not recalled. 3. Who can receive or access information Discord receives bot messages, interactions and other API actions needed to provide the service. Profiles, event/raid/group cards and public posts can be visible to their Discord audience or authorized dashboard viewers. Ordinary access to targeted crafting requests is limited to their participants. Reporters can access their own submitted report and status; authorized staff can access the queues, notes and records allowed by their roles. The operator and authorized infrastructure maintainers may also access stored records and operational logs to run and support the service. “Private” in the interface does not mean end-to-end encrypted or inaccessible to the operator. The We Blast bot, dashboard and application storage are hosted only on an OVHcloud VPS. OVHcloud processes information needed to host and operate that infrastructure. Support and privacy email is handled through Google Gmail. Google processes messages and associated information sent to the support address under its own service terms and privacy practices. The operator also keeps an encrypted backup copy off the VPS for recovery. That copy is part of the backup and deletion review described below. Game-reference features may contact Wowhead and ForeverDB for game data. Opening an external link or loading an externally hosted image can disclose connection information to that provider. Reference-index updates can also obtain public datasets from GitHub. 4. Cookies and browser storage The dashboard uses a secure, HttpOnly, SameSite=Lax session cookie with an eight-hour lifetime and a five-minute sign-in state cookie. Expiry ends validity; it is not a promise that every associated database row or backup is erased at that instant. Signing out removes the current server session. Browser storage also retains interface preferences, such as reduced motion, until cleared or replaced. 5. Retention We use manual review and deletion, not automatic pruning or a fixed-day retention promise. The operator reviews both valid correction/deletion requests and information that is no longer needed for the app's stated purposes. Encryption does not justify retaining unnecessary information. Saved characters and professions are kept while used for guild activities. Completed crafting, raid and event histories, closed reports and moderation details, privacy-request records, delivery markers, sessions, diagnostic logs and backups require review of continuing need. Shared or active records are reviewed individually to protect other people's information and ongoing activities. Any retention exception needs a specific purpose or legal requirement, a limited scope and a review point; moderation records do not have a blanket exception. For a valid API-data deletion request, guild convenience or a continuing business purpose alone does not override the request; any retention exception must meet applicable law and Discord requirements. Deleting, canceling, hiding or closing an item does not necessarily erase its underlying information. Ticket Trash is recoverable. Expiry of an authorization or session is not proof that all related rows or copies are deleted. Log compression and storage encryption are not deletion. Manual handling must account for controlled databases, caches, bot-owned Discord messages, queued deliveries, logs, exports, support email, any historical hosted copies and backups. A necessary retained recovery copy must be restricted and tracked; deletion decisions must be reapplied before restored data returns to normal use. Copies outside our control and unresolved locations are reported honestly. Historical plaintext/log coverage and complete retention enforcement remain under review. We do not claim that all unnecessary data has already been removed. 6. Your choices and requests You can update or remove supported profile entries and choose available notification settings. If XP is enabled, /xp privacy opt_out:true removes the active XP records covered by that feature and retains a minimal opt-out preference to prevent future automatic tracking. Installed collectible privacy handling also removes the associated collectible records. This is not deletion of every record We Blast holds about you, nor automatic deletion of Discord posts or backup copies. For access, correction or deletion requests, contact christianturnerelectric@gmail.com. You can use this contact after leaving the server. Provide your Discord user ID and enough information to locate the relevant records; do not send passwords, access tokens or identity documents. The operator verifies requests using the authenticated Discord account where available. If you cannot use it, contact the operator to agree on proportionate verification without passwords, tokens or identity documents. Valid requests are handled promptly and independently of routine retention review, with any applicable legal deadlines considered. The response explains completed work, remaining controlled copies, justified exceptions and unresolved coverage; a receipt or closed review alone is not proof of complete deletion. Depending on your location, applicable law may provide additional rights. Privacy & support, /privacy and the private /gui panel accept correction/deletion requests for operator review. Email remains available after leaving the guild or when sign-in is unavailable. Separately reviewed and explicitly confirmed owner actions can erase supported saved profile fields, XP records and dashboard sessions, subject to safeguards. These tools retain specified shared records and do not cover all of a person's information. Other applicable records and copies require manual handling; unsupported or inaccessible data must not be reported as erased. “Review closed” is not confirmation of complete erasure. A staff-only privacy log may contain fixed event labels and times, without request text, member identifiers or case links. Request details remain accessible only to the requester and authorized operator through the privacy feature. Staff logging is operational accountability, not member notification of policy changes. 7. Security and updates The app uses server-side permission checks, session controls and restricted administrative tools. These measures do not eliminate all risk. Encryption at rest has been verified for the configured live application data, external erasure ledger and newly generated database backups. Recovery and unattended restart have been tested. This is a limited coverage statement: historical plaintext copies, logs, provider snapshots and other locations are not all verified as encrypted or erased. Encryption is not end-to-end protection and does not prevent authorized operator access. This policy is available at /privacy on the existing dashboard. Material changes will have a member-visible notice on the dashboard privacy page with the revision, effective date and summary. A staff-only log is not a substitute for that notice. No announcement-channel posts are used. Questions and privacy concerns can be sent to the contact at the top of this policy.