Talk to the founder building it.

What to include

For support, send the account email, device, browser, and the action that failed. For product feedback, send the session type, what you expected, what happened, and whether it blocked logging. For partnerships or press, say who you are, the audience, and the exact ask.

Do not send private hand histories, full bankroll screenshots or sensitive player notes unless they are needed to explain a bug. If a screenshot is useful, crop it to the smallest area that proves the issue.

For product ideas, the most useful format is one sentence for the moment, one sentence for the problem, and one sentence for the outcome you wanted. For example: I was ending a 2/5 session on mobile, I wanted to add tips and travel quickly, but I could not find the field without leaving the cash-out flow. That kind of note is easier to act on than a broad feature request.

For data or deletion questions, say whether you mean export, account deletion, newsletter unsubscribe, or a specific session record. Overshove is intentionally small, so support should feel direct: no ticket maze, no canned reply when a real answer is needed.

If the problem involves a total, include the smallest reproducible example: the session date, stake, buy-in, cash-out, hours and the number you expected. Do not edit old rows simply to make the headline agree. A clear mismatch can usually be traced faster when the original record is left intact.

Security reports are welcome at the same email address. Describe the affected page or action without accessing another person's data, changing an account you do not own or publishing sensitive details. Tom will acknowledge a useful report and agree a safe route for any follow-up evidence.