OpenParty Privacy Policy

Effective date: July 27, 2026

OpenParty is a ChatGPT-native multiplayer party game app operated by Brandon Brooks. This Privacy Policy explains what information OpenParty collects, how we use it, who receives it, how long we keep it, and the controls available to users.

OpenParty currently lets users host and join family-friendly Mafia games inside ChatGPT. The app keeps shared game state on OpenParty servers and keeps player-specific private role information separate from public room state.

Contact

For privacy, support, or safety questions about OpenParty or BambooSnow, use our private contact form.

Information We Collect

OpenParty collects only the information needed to run shared multiplayer games, protect private player state, support safety reports, and operate the hosted service.

App and Authentication Information

When OpenParty is used through ChatGPT or another compatible MCP host, we may receive and process:

• A verified user or session identifier from the host or OAuth provider.
• Provider and provider-user identifiers when available.
• App session identifiers needed to reconnect a ChatGPT conversation to the correct game player.
• OAuth token claims needed to verify the user, such as issuer, audience, subject, expiration, and scope.

OpenParty verifies OAuth access tokens for hosted MCP requests. We do not intentionally store OAuth access tokens.

OpenParty also maintains a stable, pseudonymous openai-reviewer account used only by OpenAI's app review team. Its password is stored only as a salted scrypt hash, and the account is mapped to a seeded sample lobby so reviewers can test the app across ChatGPT conversations.

Gameplay Information

To run a multiplayer game, OpenParty stores:

• Room codes and invite codes.
• Player display names chosen by users.
• Player IDs and server-side player-session mappings.
• Game phase, public room state, public narration, and public game logs.
• Submitted game actions, such as votes, night actions, phase changes, and family-friendly public speech actions.
• Whether a room uses family-friendly mode.

Room codes and invite codes are meant to be shared with other players. Player display names and public game actions may be visible to other players in the same room.

Private Game State

Some games require private player information, such as hidden Mafia roles or a player's private role card. OpenParty stores this private game state server-side so the game can function.

OpenParty is designed so private role information is returned only to the authenticated or mapped player session. Public room state and public widgets should not include hidden role maps, player secrets, recovery phrases, seer checks, private role text, or other players' private state.

Player Secrets and Legacy Recovery Phrases

OpenParty uses server-side player-session credentials to map a ChatGPT app session to the correct player. These credentials are stored as hashes.

The hosted ChatGPT app does not ask users for recovery phrases. Legacy API clients may optionally provide a recovery phrase for advanced account recovery. If a legacy recovery phrase is provided, OpenParty hashes it immediately with a salted slow hash and stores only the hash. OpenParty should not store, return, render, or log plaintext recovery phrases.

Moderation and Safety Reports

Authenticated users may submit safety or moderation reports. These reports may include:

• The verified reporter identifier.
• Optional room code.
• Optional reported player ID.
• Reason and details provided by the reporter.
• Report status, resolution notes, and timestamps.

Operators use these reports to review abuse, harassment, minor-safety concerns, and other policy or safety issues.

Technical and Security Information

OpenParty and its hosting providers may process technical information needed to operate and secure the service, such as:

• Request timestamps.
• Endpoint paths and response status.
• Request IDs and correlation IDs.
• Authentication failures and security-related events.
• Hosting, database, and infrastructure logs.
• IP address, user agent, and similar network metadata processed by hosting providers.

OpenParty aims to redact player secrets, recovery phrases, private role fields, and unnecessary personal information from application logs.

For abuse prevention, OpenParty temporarily stores a keyed cryptographic hash derived from the request's network address, optionally scoped to a room code. The rate-limit table does not store the raw network address. These hashes expire with the active fixed rate-limit window and are deleted after expiration.

Website Forms

If you apply for BambooSnow early access or contact us through the support page, we collect the information you choose to provide, such as your name, email address, organization, shared objective, participants, product interest, workflow challenges, support topic, message, timing, and additional details.

Information We Do Not Intentionally Collect

OpenParty does not intentionally collect:

• Payment card information.
• Government ID numbers.
• Precise location data.
• Contact lists.
• Passwords for unrelated services.
• Sensitive personal information unrelated to gameplay.
• Full ChatGPT conversation history outside the tool calls and app interactions needed to run OpenParty.

OpenParty does not sell personal information and does not use OpenParty data for cross-context behavioral advertising.

How We Use Information

OpenParty uses information to:

• Create and manage game rooms.
• Let players join rooms through invite codes.
• Keep shared game state synchronized across players.
• Show each player only the private game state that belongs to them.
• Process game actions such as votes and phase changes.
• Run family-friendly safety checks and moderation workflows.
• Investigate abuse, security issues, or service reliability problems.
• Provide privacy export and deletion tools.
• Maintain, debug, secure, and improve the app.
• Review and respond to BambooSnow early-access applications and product-interest requests.
• Comply with legal obligations or enforce applicable terms and safety rules.

How Information Is Shared

OpenParty shares information only as needed to provide and operate the app.

Other Players in the Same Room

Other players may see room codes, display names, public game state, vote counts, public narration, and public game actions. Other players should not receive hidden roles, private role cards, player secrets, or private player state.

OpenAI and ChatGPT

When you use OpenParty inside ChatGPT, your interaction with ChatGPT is also governed by OpenAI's terms and privacy practices. ChatGPT may process your prompts, app interactions, and tool results so it can connect you to the OpenParty app and display OpenParty widgets.

OpenParty receives the app/tool-call information and authentication context needed to run the game. OpenParty does not control OpenAI's processing of data inside ChatGPT.

Service Providers

OpenParty may use service providers for hosting, database storage, logging, security, and infrastructure. Current infrastructure may include providers such as Vercel for hosting and Neon/Postgres for database storage. These providers process data on our behalf to operate the service.

BambooSnow early-access and website contact submissions are relayed through FormSubmit to the publisher's email inbox. FormSubmit processes submitted form fields for delivery and spam prevention.

Safety, Legal, and Security Reasons

We may disclose information if needed to:

• Investigate abuse, harassment, minor-safety concerns, fraud, or security incidents.
• Comply with applicable law, legal process, or governmental requests.
• Protect users, OpenParty, OpenAI, service providers, or the public.
• Enforce applicable terms, rules, or safety policies.

Retention

OpenParty keeps data only as long as needed for gameplay, safety, debugging, and legal or operational purposes.

Default hosted retention windows are:

• Finished rooms: 30 days after the last update.
• Game events: 30 days.
• Inactive app sessions and player-session mappings: 30 days.
• Unused invites: 7 days.
• Expired invites: deleted after a 1 day grace period.
• Hashed rate-limit identifiers: retained only for the active rate-limit window and short cleanup period.

Moderation reports may be kept longer when needed to investigate safety issues, prevent abuse, document resolutions, or comply with legal obligations.

Early-access inquiries and website messages may be retained in the publisher's email account for as long as needed to evaluate and respond to the request. You may ask us to delete an inquiry through the private contact form.

Backups, security logs, and infrastructure logs may persist for a limited period according to provider retention settings and operational needs.

Export, Deletion, and User Choices

Authenticated users can request an export or deletion through OpenParty's privacy endpoints:

• GET /privacy/export
• DELETE /privacy/delete

Export returns app-session, player-session, and invite metadata associated with the verified user where available. Export responses should not include player credential hashes.

Deletion removes app-session mappings and invite records associated with the verified user and anonymizes matching player names in stored room state. Shared game rooms, public game logs, and actions may remain until the room retention period expires so the multiplayer game state is not corrupted for other players.

You may also use the private contact form to request access, correction, deletion, or help with privacy questions.

Depending on your location, you may have additional rights to access, correct, delete, port, restrict, or object to certain processing of your personal information.

Security

OpenParty uses technical and organizational safeguards designed to protect user data, including:

• HTTPS for hosted app traffic.
• OAuth bearer-token verification for hosted MCP requests outside development.
• Scope enforcement for hosted tool calls.
• Server-side validation of tool inputs and game actions.
• Hashed player-session credentials.
• Salted slow hashes for legacy recovery phrases.
• Separation of public room state from private role state.
• Secret and private-state redaction in telemetry where applicable.

No service can guarantee perfect security. Users should not enter passwords, financial information, government identifiers, or sensitive personal information into OpenParty game rooms.

Children and Family-Friendly Use

OpenParty is designed as a family-friendly party game, but it is not directed to children under 13. Users should only use OpenParty if they are old enough to use ChatGPT and the relevant app platform under applicable terms.

OpenParty does not knowingly collect personal information from children under 13. If you believe a child has provided personal information to OpenParty, use the private contact form so we can review and delete the information where appropriate.

Reports involving minor safety, exploitation, grooming, or sexualized content involving minors should be escalated immediately.

International Processing

OpenParty and its service providers may process and store information in the United States or other countries where they operate. By using OpenParty, you understand that your information may be processed outside your state, province, or country.

Changes to This Policy

We may update this Privacy Policy as OpenParty changes. If we make material changes, we will update the effective date and make the revised policy available through the same privacy-policy URL.