Privacy Policy

Effective date: July 2, 2026. Legal version: legal-v0.0.3-ca-us-public-playtest-20260704-ai-transparency. This Privacy Policy explains how Dirty Rebirth - Protocol Link handles information for Discord onboarding, role sync, Warden review, moderation, launcher updates, game playtests, playtest routing, and owner controls. The Advancement Protocol is the public operator brand; the owner account and legal-contact handle remain account-level identity details during migration.

Information We Collect

• Discord user ID, username, display name, avatar reference, server membership, roles, bot/human status, and ban status.
• Onboarding state, Field Code acceptance, Terms and Privacy acceptance timestamps, faction choice, role changes, and website session metadata.
• Review cases, Warden notes, breach tickets, moderation items, owner actions, panic-lock state, and audit records.
• Messages or text you submit through onboarding review, lobby chat, Warden help, breach tickets, feedback, or moderation forms.
• Game build version, launcher/update status, local display name, account role, tutorial progress, queue actions, match/lobby actions, shots, hits, downs, and similar video game profile/stat tracking. Crash/report data and gameplay telemetry should be disclosed before being enabled in later builds.
• Project provenance records, including Terms/Privacy acceptance timestamps, build IDs, public playtest availability records, public announcements, Discord onboarding events, bug reports, support tickets, moderation records, release hashes, and archive records that may help document project chronology, first public use, authorship, and ownership claims.
• If Discord recruitment/authentication is declined in the game boot gate, the game may send Protocol Link the build ID, local display name label, local role label, local lock state, and decline reason so Wardens can see an unauthenticated support signal. No Discord account is linked until the player authenticates through Discord OAuth.
• Basic technical data such as request time, route, browser/session cookies needed to keep you logged in, and Cloudflare/host security metadata where available.

Children's Privacy

Dirty Rebirth is not directed to children under 13 and does not knowingly ask for personal information from children under 13. Because Discord is the current identity layer, users must also be old enough to use Discord. If you believe an under-13 child submitted information, contact SplashControlDevLegal@proton.me so the project can restrict access and delete or de-identify the information where reasonably possible.

Information We Do Not Intentionally Collect

• Discord passwords, payment card numbers, government IDs, home addresses, or real-name requirements.
• Long-term Discord OAuth access tokens.
• Private direct messages outside bot flows, unless you voluntarily send information to the bot or staff.
• Clipboard contents, desktop screenshots, screen recordings, or files from your computer in the current pre-alpha game build.

How We Use Information

• Authenticate Discord identity and confirm server membership.
• Assign and switch SCRIPTERS or VULTURES roles.
• Require onboarding before protected site or server access.
• Show Wardens and the owner onboarding status, cases, faction selections, moderation items, and safety signals.
• Operate lobby chat across the game, launcher, and website, block links/invites, keep moderation history, and let owner/Wardens review or hide abusive messages.
• Prevent abuse, enforce bans, preserve audit history, operate panic lock, and protect the project.
• Preserve project chronology, authorship evidence, build provenance, public-use records, and legal-defense records for Dirty Rebirth, The Advancement Protocol, and related studio/project names where legally allowed.
• Improve onboarding, playtest organization, bug reporting, and community operations.

Sharing And Access

Relevant information may be visible to The Advancement Protocol, the configured owner account, Firewall Wardens, infrastructure providers, and Discord as needed to operate the project. Public pages avoid raw Discord IDs where practical, but internal systems may store IDs because Discord requires them for role sync, bans, and moderation.

Sale, Sharing, Advertising, And Do Not Track

The current pre-alpha does not sell personal information, share personal information for cross-context behavioral advertising, run targeted ad profiles, or knowingly sell/share information of users under 16. Browser Do Not Track signals are not used because the current site does not run cross-site ad tracking. If advertising, analytics expansion, sponsorship tracking, or data sale/share behavior is added later, this Policy must be updated first and the project must add any required California opt-out links and controls.

California Privacy Rights

The Advancement Protocol project is operated from California. The project may not meet the current CCPA/CPRA threshold for a covered "business" during a small pre-alpha, but the project should still treat California privacy requests seriously. California residents may contact SplashControlDevLegal@proton.me to request access, correction, deletion, portability, limitation of sensitive information if any is later collected, or information about disclosure practices. Some records may be retained for security, anti-abuse, legal, audit, Discord role sync, or moderation reasons.

California "Shine the Light" style questions about sharing personal information for third-party direct marketing can also be sent to SplashControlDevLegal@proton.me. The current playtest does not share personal information with third parties for their own direct marketing.

Identity Protection

Dirty Rebirth uses Discord identity for onboarding and role sync because Discord requires stable account IDs for server access. Public-facing player UI should prefer display names and role labels instead of raw IDs. Wardens and owner tools may see account identifiers only where needed for moderation, support, audit trails, bans, or role repair.

AI-Assisted Operations

Some support, bug, moderation, onboarding, and archive records may be reviewed with AI-assisted tooling so the project can diagnose issues, summarize work, and document decisions. Do not submit private personal information, secrets, credentials, or content you do not have permission to share in places where staff or AI-assisted tooling may review it.

AI-assisted review does not make an AI system the project owner, moderator, employer, contractor, legal witness, or final decision-maker. The Advancement Protocol, the configured owner account, and authorized staff remain responsible for project operation and human review.

Cookies And Sessions

Protocol Link uses session cookies to keep your browser signed in. Clearing browser data or using the logout/clear session action removes the local session. Banned Discord accounts have website sessions revoked.

Retention

Operational data may be kept while your account participates in the project. Moderation records, bans, audit logs, safety-related records, release records, Terms/Privacy acceptance timestamps, public-use records, build/version records, and project provenance records may be retained longer where needed to prevent abuse, document decisions, protect the community, prove project chronology, or defend ownership/IP claims. The project should not collect real names, home addresses, government IDs, payment data, screenshots, clipboard contents, or desktop recordings solely for provenance.

Security

Reasonable safeguards are used for a small community project, including Discord OAuth, signed sessions, server-side role writes, access checks, owner-only controls, same-origin checks, public-build hash manifests, Cloudflare protections, and optional Cloudflare Turnstile human verification for high-risk support forms. No system is perfectly secure, and you should not submit sensitive personal information through onboarding or tickets.

If a security incident creates a legally required notice obligation, The Advancement Protocol should investigate, preserve evidence, reduce harm, and provide notices required by applicable law. Security reports can be sent to SplashControlDevLegal@proton.me.

Your Choices

You may leave the Discord server, clear your browser session, or contact Protocol Link support or Firewall Wardens for access, cleanup, or moderation questions. Some records may remain if needed for legal, safety, anti-abuse, or audit purposes.

Contact

Legal, privacy, copyright, security, or California rights questions can be sent to SplashControlDevLegal@proton.me. Do not send passwords, payment details, government IDs, home addresses, or other unnecessary sensitive information.

Changes

This Policy may be updated as Dirty Rebirth, Protocol Link, Discord features, or legal requirements change. Continued use means you accept the updated Policy.