eR33t Gaming Team eR33t
PRIVACY / DATA NOTICE

Privacy Policy

AlexAI uses memory, voice, generated media, and live Discord context to be useful. This policy explains what may be collected, why it is used, where it may be shared, and how to request access, correction, or deletion.

Updated July 2026

Scope

This Privacy Policy covers the public website at eR33t.com, the AlexAI Discord bot, public connected services, generated blog/gallery content, pilot-interest intake, and any managed pilot instance if that program later opens, unless a separate agreement says otherwise.

Discord, AI model providers, analytics providers, hosting/storage providers, media/search providers, calculation APIs, fantasy or market-data providers, and other services used to operate AlexAI may process data under their own policies. Their policies govern how they process data they receive directly or as service providers.

Information AlexAI may collect

Discord identity
User IDs, display names, usernames, avatars, roles, guild/server context, channel names or IDs, and voice-channel presence where AlexAI is installed.
Messages and commands
Message content, command text, prompt text, URLs, attachments, generated responses, reactions, quotes, reminders, and context needed to respond or remember.
Voice data
Voice-channel participation state, speaker context, audio sent to realtime voice providers for transcription/response, and transcripts or summaries when voice memory features are active.
Memory and relationship state
Long-term memories, importance scores, relationship/affinity state, mood logs, sentiment history, thought logs, summaries, server-era signals, and generated editorial context.
Generated media
Prompts, source images or references, generated images, videos, filenames, gallery metadata, and gallery like counts.
Website and analytics
Server logs needed to operate the site, plus anonymous page views, bounded referral and campaign labels, button and section events, redacted browser error diagnostics, and a browser consent preference when you choose to allow PostHog analytics. We do not send form contents, Discord IDs, profile names, or raw browser error messages to analytics.
Pilot inquiries
Name, email, community size, requester role, message, timestamp, and request status when you register nonbinding pilot interest.
Contact requests
Name or Discord handle, reply email, selected context, required request type, message, source page, timestamp, and request status when you use the Contact form. The form does not ask for a Discord user ID.
DP3: Repainted updates
Email address, consent and confirmation timestamps, signup source, subscription status, and limited delivery or suppression events when you ask for development and release updates.
Dashboard data
Dashboard usernames, password hashes, roles, last login timestamps, admin actions, audit logs, and configuration changes for authorized operators.

Why the data is used

  • To run AlexAI in Discord chat and voice channels.
  • To remember relevant context, relationships, preferences, incidents, and community lore.
  • To generate images, videos, summaries, reminders, blog posts, telemetry, and dashboard views.
  • To moderate, debug, secure, rate-limit, and improve the bot, site, and selected managed pilots if that program later opens.
  • To route and respond to pilot interest, privacy requests, safety reports, site corrections, terms questions, support needs, and operator actions.
  • To verify request ownership where needed, investigate safety reports, document corrections, prevent form abuse, and maintain follow-up records.
  • To send a requested DP3: Repainted confirmation, a short onboarding sequence after confirmation, and later occasional development, playtest, or release updates.
  • To understand public website usage and whether visitors reach the pilot intake flow.

How information may be shared

AlexAI may share data with service providers only as needed to operate the product. Current provider categories include Discord APIs, AI model providers, hosting and storage providers, PostHog when anonymous analytics consent is granted, email delivery providers such as Resend, URL/video metadata providers, and operator notification channels.

We do not sell Discord API data. We do not disclose Discord API data to ad networks or data brokers. We may disclose information when required by law, platform policy, verified security response, or an appropriate request from the person connected to the data or an authorized server operator for that server context.

Website analytics and cookies

eR33t.com may offer PostHog for anonymous page views and a small allowlist of button, section, content, inquiry-funnel, and browser error events. The loader is off until you choose “Allow anonymous analytics”; “No thanks” prevents the third-party script from loading. Automatic interaction capture, session replay, heatmaps, console-error capture, and form contents are disabled, and browser Do Not Track or Global Privacy Control is respected.

After consent, unhandled browser errors on public eR33t.com pages and physics.er33t.com paper pages may include an allowlisted error type and public script location with line and column numbers when available. Raw error messages, form values, and private URLs are not sent. This diagnostic capture covers the main public website and the paper pages on physics.er33t.com, which use the same analytics loader and ask for your choice separately; it does not capture backend failures or other separately deployed apps.

Use “Analytics preferences” in the footer to change your choice at any time. Declining stops future collection; events already received cannot be recalled from your browser. Browser Do Not Track and Global Privacy Control take priority over an earlier opt-in.

When our first-party proxy is active, analytics requests use t.er33t.com and pass through Cloudflare to PostHog's US service. Cloudflare may process this traffic in multiple geographic locations. This routing does not override your consent choice. We strip query strings, form contents, and identity details from analytics events and disable IP-based location enrichment. PostHog is not used to sell Discord API data or build advertising profiles.

What can become public

Some surfaces are intentionally public: eR33t.com pages, public-facing Team eR33t profiles, gallery media, blog-style posts, high-level service status, and a live log feed limited to selected event categories. The homepage does not fetch or render recent-member activity, Discord member IDs, member names from activity endpoints, or live channel topics.

The public log path applies a server-side category allowlist and sanitization for common IDs, URLs, paths, email patterns, and quoted text, plus client-side link masking. Filtering reduces exposure risk; it is not a promise that every possible identifier can never appear. Other intentionally public features may include approved display names, avatars, relationship summaries, gallery filenames, generated media, and reviewed snippets. Report anything that should be removed or corrected.

Server owners and admins should not enable AlexAI in channels or voice spaces where members expect zero bot processing. Members should not submit secrets, private keys, sensitive personal data, or content they do not have rights to share.

Retention

Retention depends on the data type and the configuration of the origin server or pilot.

  • Long-term memory: retained according to the origin server or pilot's configuration, with correction and deletion requests reviewed by authorized admins. Archive exceptions may apply for safety, audit, or public artifacts that still need review.
  • Voice memory: retained only when voice memory or recap features are active for the server or session; raw audio is used for realtime processing and should not be treated as a silent recording archive.
  • Operational logs: kept as needed for debugging, audit, security, and uptime monitoring.
  • Contact requests and pilot interest: kept while routing, responding, evaluating possible future fit, and following up, then as reasonably needed to document resolution, prevent abuse, or meet safety, audit, or legal obligations. There is no published fixed deletion period today; you may request deletion, subject to the exceptions described below.
  • DP3: Repainted subscriptions: pending confirmations expire; confirmed consent and suppression records are retained while needed to honor the subscription or prevent mail after an unsubscribe. Delivery-event metadata is kept only for operations, abuse prevention, and deliverability review.
  • Dashboard accounts: kept while the account is active or needed for audit/security records.
  • Public blog/gallery artifacts: kept until removed, replaced, archived, or made unavailable by the storage provider.

Correction, deletion, and access requests

You may ask for AlexAI memories or records about you to be corrected or deleted. If you are in the eR33t Discord, contact a server owner or admin. If you are not in the Discord, use the Contact page or the pilot form and start the message with "Privacy Request."

Every DP3: Repainted marketing email includes an unsubscribe path. Unsubscribing suppresses future marketing sends; a minimal suppression record may remain so that preference continues to be honored.

To protect people and communities, we may need to verify that you are the person connected to the Discord identity or content in question. Some records may be retained where necessary for security, legal compliance, abuse prevention, audit history, or backup integrity.

Children and age limits

AlexAI and eR33t Gaming are intended for adults and are not directed to children. Do not use the public site, Discord bot, or pilot instances if you are under 18. If we learn that we collected personal information from a child where we should not have done so, we will delete or disable that information as appropriate.

Security

AlexAI uses role-based dashboard access, hashed passwords, JWT-based sessions, protected admin routes, server-side storage, and operational safeguards. No system is perfectly secure. Report suspected unauthorized access, leaked credentials, or unsafe bot behavior through the Contact page or to an eR33t admin.

Contact

For privacy, deletion, safety, or support requests, use Contact. For pilot communities, the community owner or admin should collect member concerns and route them to the operator responsible for that pilot.

If this policy does not answer your question, use the Contact page and begin your message with “Privacy Request.” Do not include passwords, tokens, private keys, or other secrets.