Bug reports
Broken flows, missing data, visual issues, bad links, tracking problems, auth trouble, and page-specific errors are all useful reports. The more concrete the repro steps, the faster I can usually act on it.
Contact
Contact is the best place for rollout feedback, bug reports, feature ideas, privacy questions, policy concerns, and business inquiries. CardChart.Fun is a solo-dev project, so clear reports really do help shape what gets fixed, polished, or explained next.
What to send
Broken flows, missing data, visual issues, bad links, tracking problems, auth trouble, and page-specific errors are all useful reports. The more concrete the repro steps, the faster I can usually act on it.
If a rollout page feels unclear, a tool feels half-finished, or a feature needs one more push to become genuinely useful, I want to hear it. CardChart.Fun improves a lot through this kind of direct product feedback.
Questions about privacy, terms, affiliate links, partnerships, or how the project works behind the scenes are welcome too. If the site is public-facing, I would rather explain it clearly than leave people guessing.
Fastest path
For a bug or confusing flow, these four details usually turn a report into something I can act on quickly.
the page URL where the issue happened
the card, commander, debate thread, or feature involved
what you expected to happen and what happened instead
whether you were signed in, and if the issue was mobile or desktop only
Screenshots, exact error text, and “I clicked this, then this” notes are especially helpful. Specific reports make solo-dev debugging much faster.
Before you email
These are the quickest routes for common product, ranking, and policy questions.