Privacy Policy
What the kitchen knows about you, and why.
Effective and last updated:
1. Who is responsible
This policy covers the Panic! At The Pantry website and Discord Activity, operated by Mauricio Hollando, an independent game developer and the controller of the game information described here. Contact the developer using the existing support form for Mauricio’s games. The form is currently branded Unalived; begin your message with “Panic! At The Pantry”. For privacy requests, choose Privacy or data request.
Discord and Cloudflare also process information under their own policies. This policy describes Pantry’s current implementation, including browser play and Discord integration.
2. Information we process
- Browser play: your chosen nickname, a generated player identifier, room code, connection status, and session credential used to join or reconnect. No separate email account is required.
- Discord play: the basic profile returned by Discord’s
identifypermission. We use and retain your Discord user ID and display name or username for your room session. We also verify your membership in the current Activity instance using its identifier and participant list. - Authentication: Discord authorization codes and access tokens are used to sign you in and authenticate the Activity. The game does not intentionally persist Discord access tokens in its room database. The server stores a hash of the game’s own session credential.
- Gameplay: room membership, inputs, positions, carried items, station contents, table orders, recipe-book access, dispatch assignments, scores, customer state, connection timestamps, and other state required to run or resume a kitchen.
- Purchases: in Discord, the game checks your user ID against Discord entitlement records, including SKU identifiers, status, and validity dates. We temporarily cache the restaurant access result in your room session to restore purchases and share restaurant access with your crew. Discord handles checkout, receipts, payment information, and refunds. We do not receive your card or bank details.
- Technical data: Cloudflare processes network and request information, which may include IP addresses, request URLs, device or browser metadata, timing, and error information, to host, secure, and troubleshoot the Service.
- Support: if you use the linked shared support form, we receive your email address, category, message, reference number, and submission time. The form uses a temporary hashed network identifier to limit spam. It does not attach your raw IP address to your support message.
Pantry does not request your Discord email, friends list, message history, microphone, or camera. It does not capture, record, transcribe, or measure the loudness of voice calls. Discord or your chosen voice provider handles audio. NPCs are simulated characters; the game does not send player conversations to an AI service.
The current game has no advertising or third-party analytics SDK. Optional restaurant purchases are processed by Discord; Pantry does not collect card or bank details.
3. Why we use information
We use the information above to run multiplayer rooms, verify access, reconnect players, distribute the right information to each player, prevent abuse, diagnose problems, and respond to support or privacy requests. We do not sell personal information, share it for cross-context behavioral advertising, or use Discord information for advertising.
Where a legal basis is required, necessary game data is processed to provide the Service you request; security, troubleshooting, and support data is processed for our legitimate interests in operating a reliable service; and some processing may be necessary to comply with legal obligations. Where consent is required, we will request it and you may withdraw it.
4. What other people and providers receive
Your crew: other players in the same room can see your chosen name, pawn, connection status, carried items, team score, and shared gameplay. They can see which restaurants the crew can play and the player sponsoring the selected restaurant, which may reveal ownership of that pack. Orders and delivery destinations are sent only to the players entitled to see them under the game rules. For example, a disconnected dispatcher’s outstanding destinations can transfer to the connected head chef. The server necessarily processes all game state.
Private game notes are a gameplay feature, not confidential communications. Players may repeat what they learn in voice chat or capture their screens. Avoid nicknames or support messages containing unnecessary personal information.
Service providers: Cloudflare hosts the website and room storage and handles infrastructure logs. Discord provides identity, purchases and entitlement records, the Activity platform, and its voice service. Support submissions are available to the operator through the private hosting account. We may reply using the email address you provide. We may also disclose information when required by law or reasonably necessary to protect people or the Service.
Provider information: Discord Privacy Policy and Cloudflare Privacy Policy.
5. Device storage
The game uses local storage to remember your chef name and session storage to hold your room code, player identifier, and reconnect credential. These are functional storage features, not advertising trackers. Leaving a kitchen clears the current reconnect details, but your remembered name remains until you clear the site’s data.
You can remove this information through your browser or device’s site-data controls. Clearing it may prevent reconnecting to your previous player. Your browser may restore session storage when restoring tabs. Discord and hosting providers may separately use storage under their own policies.
6. Retention
- Rooms and game sessions: the server checkpoints room state while it is in use. Rooms expire after approximately two hours without activity. Live stored state is scheduled for deletion after that inactivity period once no connections remain; cleanup timing can vary. An active room may keep state across rematches.
- Disconnected players: abandoned seats and associated session records may be removed when someone joins after the reconnect grace period. Remaining records follow the room’s lifecycle.
- Purchase access: cached restaurant access follows the temporary room lifecycle and is refreshed from Discord on restore, restaurant selection, or the start of a paid shift. Discord maintains its own purchase and entitlement records under its retention policies.
- Device data: your nickname remains until cleared; session details follow the browser session or are cleared when you leave.
- Support: the shared support inbox removes submissions older than 90 days when a new request arrives or the operator opens the inbox. Resolved requests may be removed earlier. Follow-up email or records needed for a legal obligation or dispute may be retained separately while needed. Expired hourly spam-limit records are removed during subsequent submissions.
- Logs and recovery copies: standard Cloudflare Workers logs currently have retention of three days on its Free plan or seven days on its Paid plan. Other provider security records, backups, and recovery copies follow the relevant service lifecycle and may outlast deletion from the live game.
We do not maintain a permanent player profile or global score history in the current game. We may retain specific records longer if needed to address a security incident, resolve a dispute, or comply with law.
7. Security and international processing
We use encrypted connections, authenticated room sessions, server-side access checks, and restricted access to hosting accounts. No online system can guarantee absolute security. Do not share reconnect credentials, account passwords, or access tokens.
Our providers operate internationally, so information may be processed outside your country. Applicable provider agreements and legally required safeguards govern relevant transfers.
8. Your choices and privacy requests
You may play through a browser without connecting Discord, stop playing, clear site data, and revoke Pantry under Discord’s Authorized Apps settings. Revoking access does not itself delete existing room or support records.
Use Support to request access, correction, deletion, or other rights available where you live, including restriction, objection, portability, or withdrawal of consent where applicable. Identify the game as Panic! At The Pantry and include enough information to locate your record, such as your Discord user ID or your nickname, room code, and approximate play time. Never send passwords or session tokens.
We may ask for reasonable verification before disclosing or deleting information. Some data may already have expired; some records may need to be retained under law. We will respond within applicable legal time limits. You may also raise a complaint with your local data-protection authority.
9. Age requirements
The Service is intended for people aged 13 or older who meet any higher minimum age required by local law and, for Discord play, Discord’s rules. We do not knowingly collect personal information from children below that age. If you believe a child has provided information, contact us so we can investigate and take appropriate action, including deletion.
10. Updates
We will update this page when our practices change and revise the date above. We will provide appropriate notice of material changes and request consent where required before using information for a new purpose.