Use this page for reports about freecell.plyyard.com , accessibility feedback, privacy requests, and content suggestions. Ply Yard handles these messages. You need not finish troubleshooting first; if an issue is not repeatable, describe what happened.
Email and Subject Line
Feedback is handled by email, not phone or live chat. The button opens your email app with report fields filled in; you review and send the message yourself.
Suggested subject: freecell.plyyard.com - issue type and specific result
Example: Daily Deal progress does not match the current UTC date after refresh.
Write a ReportNo email app configured? Write directly from your usual email service.
Six Details to Include
These help establish the layout, the actions, and the environment.
- Page and mode: Send the page URL and say whether you were on a numbered deal or the Daily Deal.
- Deal state: Give the deal number, the move count, and whether you had just used Hint, Undo, or Auto-collect.
- Steps taken: List clicks, drags, and buttons in order before the issue. You do not need to redeal in order to report it.
- Actual and expected result: Separate what the page displayed from what you expected. Keep any hint or error text in its original wording.
- Device and browser: Include device model, operating system, browser and version, and whether you opened it in a browser or from the home screen or Dock.
- Time and evidence: Include the date, time, and time zone. Attach a board screenshot with private information redacted if available.
Evidence for Each Issue Type
Move or Collect Ruling
Say which card you tried to move where, how many free cells and empty columns you had, and whether the table refused the drag, collected only some cards, or left a position you did not expect. If the run limit is involved, say whether the landing column was empty.
A finished-layout screenshot may not reconstruct the middle. Attach an existing recording if you have one; otherwise describe what you actually saw, without guessing unseen steps.
Hint, Undo, or Auto-collect
Say how many times you pressed Hint, whether the first press only marked origin and landing, and whether the second played that step. For Undo, say whether Auto-collect had just run. For Auto-collect disputes, list which cards went home and why you think they should not have.
Deal Restore or Daily Deal
Say which number appeared after refresh or reopen, whether the unfinished position came back, and whether you were on the main table or the Daily Deal. For the Daily Deal, include your time zone and whether the page's UTC date matched the day you expected.
There are no live rooms. Sending someone a deal number only opens the same starting layout; it does not carry your move count or scores.
Display, Sound, or Installation
For obscured text, unusable buttons, or layout issues, attach the relevant area and include orientation and browser zoom. For sound or installation, include permissions, mute state, and how you opened the site.
Safe Attachments and Privacy Requests
Redact notifications, email addresses, other people's names, and other private details unrelated to the issue. Do not send passwords, identity documents, payment details, addresses, or other sensitive information. There is no account recovery and no room credential to attach.
Use ordinary screenshots, necessary screen recordings, and plain-text notes. Do not send executables, macro-enabled documents, or archives from unknown sources.
Put “Security report” in the subject for a security issue. Email details privately; do not publish exploit instructions or send attack traffic to reproduce it.
For access, correction, or deletion requests, specify the data category, relevant time range, and requested action. The privacy policy explains how reports and attachments are used and retained.
How Reports Are Handled
Rulings that affect play, lost hints or progress, and unavailable features are prioritized for checking. We may ask for a browser version, deal number, or steps, but not a password.
There is no guaranteed reply time or promise to implement every suggestion. Reply in the same email thread with new findings or changes to preserve the report history.
For a feature suggestion, describe the specific difficulty and the outcome you want. For unclear existing copy, point to the page and wording involved. We cannot provide live support, one-on-one coaching, device repair, browser-vendor support, or rulings on outside competitions.
Before Sending
- Separate actual and expected results.
- Include device, browser, deal number, and time.
- Redact private details unrelated to the issue.
Mark uncertain details as uncertain. Do not repeat risky actions just to complete a report.
Write a Report