We want our puzzles to be fair, understandable, and enjoyable. If a clue seems wrong, a control fails, or an explanation creates confusion, your report can help us find and fix the problem. This policy describes how to submit feedback, how different issues are reviewed, and what we can and cannot promise.
What you can report
Corrections are not limited to spelling mistakes. We welcome reports about the quality of clues, puzzle answers, wording, technical errors, accessibility problems, broken links, and misleading statements about the website. You can also suggest a new type of word or logic challenge, provided your idea is described in your own words.
Relevant concerns may include:
- Ambiguous clues: A definition reasonably fits more than one answer, but the game offers no way to understand the intended one.
- Incorrect answers: The published solution contains a spelling error or does not follow the rules stated in the instructions.
- Unaccepted alternatives: A plausible variant or regional spelling is rejected even though the clue does not make the distinction clear.
- Broken interactions: Submit, hint, reset, undo, or navigation controls do not function as expected.
- Accessibility barriers: A player cannot read a clue, operate a control with a keyboard, understand feedback, or use a game at a practical zoom level.
- Editorial inaccuracies: Supporting text, FAQs, or policy explanations describe functionality that is not available.
- Copyright or attribution questions: A rights holder identifies a specific part of the Site that may need review.
How to send a useful correction
Please email contact@infipuzz.com or use our Contact page. We do not require an account to report an issue. Include the following details when relevant:
- Page and game: Provide the URL or the name of the game, such as Oddity Orchard or Sentence Switchyard.
- Exact clue or action: Quote the short clue, describe the round, or identify which button caused trouble.
- Expected result: Explain what you think the answer, wording, or behavior should have been.
- Actual result: Describe what you saw. For example, a valid-looking word was rejected or a message did not appear.
- Helpful technical context: Mention your browser and device type when reporting a layout, performance, or interaction issue.
A screenshot can help with a visual bug, but you do not need to send one to be heard. Remove personal information from screenshots before sharing them. Please do not send passwords, account credentials, payment information, or unrelated private material.
How we assess reports
Understanding the problem
We aim to identify whether the report involves a factual error, a legitimate alternative answer, a usability barrier, or an intended rule that needs better explanation. A report that a word was rejected is not automatically proof of a bug, because some games have deliberately limited accepted-answer sets. Conversely, a fixed answer list is not a reason to ignore an ambiguous clue.
Checking the rules and supporting context
Where appropriate, we compare the report with the published instructions, underlying game data, ordinary language usage, and the behavior of the relevant feature. If a word’s meaning or spelling is disputed, a reputable reference can help evaluate it. A technical issue may need reproduction in the affected browser or screen size.
Choosing a proportionate fix
For minor mistakes, a direct wording edit may be enough. Ambiguous prompts may need a more specific definition, another accepted answer, or a changed explanation. A faulty game control may require a code adjustment and additional testing. Not all reports will lead to a change; sometimes clearer guidance about the existing rule is the appropriate response.
How corrections may appear
We may implement fixes directly on the affected page or in the game code without publishing an individual announcement for every minor typo. We aim to make substantial changes understandable, particularly when they alter the expected answer, instructions, scoring, or availability of a feature.
Puzzle databases may be finite, and an update may change which rounds appear. That can affect a player’s current game or previously familiar solution. We cannot guarantee that saved progress, scores, or previous rounds will remain identical after a correction.
We do not maintain a public revision history for each individual clue at present. If we introduce a change log, it should reflect actual changes, not a fabricated record of previous reviews.
What happens after you contact us?
Messages sent through the website contact form or email can help us identify problems. We aim to review clear, actionable reports, especially those involving a broken game or an accessibility barrier. However, we cannot promise an individual reply, specific resolution time, or acceptance of every suggested correction.
Sometimes a report lacks enough information to reproduce the issue. We may ask for clarification, but you are free to omit details you are uncomfortable sharing. If you send multiple identical reports, combining them into a single clear description is usually more helpful than repeated submissions.
We may prioritize a widespread functionality problem over a minor stylistic preference. The seriousness and impact of an issue, the clarity of evidence, and the time needed to investigate can all affect the order in which problems are addressed.
Fairness, disagreement, and language variation
Word games often allow legitimate disagreement. A compound word may be more common in one region than another, while a category puzzle may appear to have two possible odd items depending on how a group is defined. Our standard is to clarify the clue and explain the intended rule, not dismiss a good-faith alternative without consideration.
We may keep a challenge intentionally limited to one answer for consistent gameplay. In that case, the instructions and explanation should make the constraint understandable. We do not claim that every rejected answer is linguistically incorrect or that every puzzle has only one possible interpretation outside its particular rules.
Copyright and content concerns
We aim to publish original puzzle wording, designs, and code. If you believe a specific page includes content that infringes your rights, identify the relevant URL, the material at issue, a description of the rights you hold, and a reliable way for us to respond. Do not send lengthy copies of copyrighted works when a link or brief description would suffice.
We will review appropriately supported notices under applicable law. This page is not a substitute for our Terms of Use or a promise to follow a particular foreign legal process regardless of jurisdiction. The website is operated from India, and applicable legal obligations depend on the circumstances.
Accessibility-related corrections
Barriers affecting keyboard input, focus visibility, contrast, readable instructions, or compatibility with assistive technology are meaningful quality concerns. Our Accessibility Statement explains our accessibility aims and how to describe problems in a useful way.
An automated accessibility score is not a complete measure of a real player’s experience. Please contact us even if an automated tool has reported that a page passes.
Privacy and revisions
We use the contact details you provide to review and, where possible, respond to your message. Our Privacy Policy explains how contact information and website data may be processed. You may request deletion of identifiable correspondence where applicable law allows it.
We may update this policy if our games, review practices, or contact channels change. The last-updated date identifies the revision of this policy page; it is not a promise that every reported issue has been resolved by that date.
Report a problem or suggest a correction
Give us the game name, the clue or feature involved, and what you believe should change. Specific reports make a practical review possible.
Go to the Contact page or email contact@infipuzz.com.
