Contact and Feedback for Online Air Hockey

Email us

contact@plyyard.com

We accept reports by email, not phone or live chat. Include the site and a specific symptom in the subject, such as "airhockey.plyyard.com - Right mallet will not move in Two-Player".

The link fills in fields in your email app; it does not send anything automatically. If no email app is configured, write to the address above using your usual email service.

Six useful details

1. Page and mode: Say whether you used AI, Two-Player or Play Online. Remove room codes and invite, host and seat credentials from the page URL.
2. Score and match state: Include the point target, left and right scores, and whether the issue happened at the start, during a serve, in a rally or after the match. For AI, include the difficulty.
3. Steps: Describe clicks and mallet movements in order. Mention any pause, refresh, screen lock or tab switch before the issue.
4. Actual and expected result: Explain what you saw and what you thought should happen. Include the exact text of any error or status message.
5. Device and browser: Include the device model, operating system, browser and version. Say whether you used mouse, touch or keyboard, and opened the site in a browser or through a Home Screen shortcut.
6. Time and evidence: Include the date, time and time zone. A goal log, screenshot or existing screen recording can help. Mark anything you did not see clearly rather than guessing.

Details for common reports

Goals and scores

Say which goal the puck entered, which score changed, and whether an automatic serve had just occurred. A screenshot of the puck near a goal may not show whether it went in. An existing recording can help; without one, describe what you observed.

Mallet movement and pausing

Say whether you controlled left green or right red, where a touch drag began, or which keys you used. With keyboard controls, mention whether the mouse pointer was inside the table. Include the mode for pause reports, so we can distinguish local controls from the state seen by both online players.

Creating, joining and reconnecting

Include public or private, host or guest, whether you were watching, the connection message, and whether the opponent was connected. List browser changes, new tabs, network switches or returns from the background in order.

If we need to identify a room, you can email its code and the time of the issue. Do not send a full invite, host credential or seat reconnection token, or publish a private room code in a public post.

Display, sound and shortcuts

For covered text or hard-to-click buttons, send a screenshot of the area and note screen orientation, zoom and theme. For sound or Home Screen issues, mention system mute, permission messages and how you opened the site.

Attachments, security and privacy

Before sending, hide notifications, personal details, and room links or credentials in the address bar. We do not need passwords, identity documents, payment details, home addresses or unrelated information about other people. Use ordinary screenshots, necessary recordings or plain-text logs, not executable files or archives from unknown sources.

For a security issue, put "Security report" in the subject and report it privately by email. Do not publish exploitable details, test someone else's room or send attack traffic to verify a problem.

For a privacy inquiry or a request to correct or delete data, include the site domain, data category, time range and requested action. The privacy policy explains how emails and attachments are handled.

After you send

We may ask for more steps or environment details, but will not ask for passwords or full room credentials. We do not promise a fixed response time or implementation of every suggestion. Reply to the original email with updates so the history stays together.

For a feature suggestion, explain which task was difficult and what outcome would help. For a wording issue, include the page URL and the original sentence. You do not need to restart a match just to complete a report.