Contact
Last updated: April 27, 2026
StatLine is built and maintained by one person, so all email lands in the same inbox. The fastest way to reach me is by emailing [email protected]. Below are the kinds of messages I'm most likely to act on quickly, with a couple notes on what to include.
Corrections and data issues
If a stat looks wrong, a player is listed on the wrong team, a record is out of date, or a game is missing entirely — please send it. Include the page URL, the specific row or value that looks wrong, and what you believe the correct value should be. Most data anomalies are caused by upstream issues with the league feeds rather than StatLine itself, but I'd still rather hear about them so I can either fix the mapping or chase the source.
Feature requests
Have a stat, view, or comparison you wish the site supported? Tell me what you want and roughly how you'd use it. Concrete requests are much easier to act on than abstract ones — "I'd like to filter player stats by month" is something I can build; "make it more useful" is harder. I read every request even when I don't act on it.
Partnerships and licensing
For sponsored content, partnership inquiries, or interest in the underlying data pipeline, email me with a sentence or two about what you have in mind. StatLine accepts a small amount of relevant sponsorship and affiliate placement, but only if it actually fits the readership. If you're pitching a product that has nothing to do with sports, please don't bother — I'll pass.
Takedown and content requests
StatLine displays publicly available statistics aggregated from public league sources. If you're a rights-holder who believes specific content on the site infringes on rights you control, send me an email identifying the page and the content in question and I will respond promptly. If you're a player, agent, or team representative and a biographical detail is incorrect, I'm happy to update or remove it.
Press and interviews
Happy to talk about the build, the design philosophy, or the broader independent-stats-site space. Email is the right channel; please include the publication and a sentence or two about the angle.
Response time
I aim to reply within a few business days. Corrections and clear bug reports usually get faster turnaround than feature requests because they're easier to triage. Please be patient if you don't hear back immediately — there's no support team behind this, just one person reading email between writing code.