Feedback

Help improve the public beta

Share private, practical feedback about StriveMatch workflows. Feedback helps improve the platform without creating public comments, ratings, likes, or social feeds.

Learning loop

Feedback stays private and useful

StriveMatch uses feedback to improve proof submission, Player Passport clarity, scout workflows, club needs, trial journeys, sponsorship guidance, and admin moderation.

Private and operational

Tell us what you understood in 10 seconds

Name the first role or route you clicked

No public comments or ratings

Used to improve public beta clarity

Specific enough for human review

Avoid unnecessary personal data

Useful feedback examples

Submitting Performance Proof

Reading Player Passport context

Using Scout Workspace

Applying for trials or club needs

Understanding trust and moderation labels

Reporting broken proof, privacy, or safety concerns

Understanding Learning Hub and Global Cricket Guide boundaries

Trying Cricket Tools and checking whether overs, balls, and results make sense

Checking whether Rain Interruption, field positions, or match scenario learning would help beginners

For safety, privacy, impersonation, or misleading proof concerns, use profile reports where possible or see our conduct guidelines.

Where your feedback goes

Product clarity

Use this form for confusing copy, route flow, beta expectations, and missing guidance.

Usability notes

Share mobile, accessibility, loading, empty-state, or form issues with enough context to reproduce.

Safety concerns

Use profile reports where possible for proof, privacy, impersonation, youth safety, or misleading player context.

Feedback submission is not connected to Supabase yet. Use it for product clarity, broken public pages, accessibility notes, or general issue context while backend storage is designed with privacy, moderation, and admin review in mind.