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.
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.
If you are reporting a bug or a confusing flow, it helps a lot to include:
Screenshots, exact error text, and “I clicked this then this” style notes are all excellent. Solo-dev debugging gets much easier when the report is specific.
If your question is about how ranking, matchmaking, progression, or debates work, the Method page may already answer it.
If your question is more general, the FAQ is the quickest overview.
If your question is about privacy, data, or terms, the Privacy Policy and Terms should give the current baseline.