Support
One address, and honest expectations
VigPulse is a small research project, not a company with a support desk. There is one email address, no ticketing system, no guaranteed response time, and no account to be locked out of. What there is: a genuine commitment to fix anything wrong in the published record.
Expectations
What you can expect, stated plainly
- Support hours
- None published
- Guaranteed reply
- No
- Phone or live chat
- None
- Ledger corrections
- Always actioned
What actually happens
Current- Email arrives at one address and is read by one person.
- There is no queue, no ticket number, and no automated acknowledgement.
- Messages pointing at a specific error in the published record are handled first, because they are the ones that affect other readers.
- A message may not get a reply. That is a real possibility rather than a disclaimer, and saying so is more useful than an unmet promise.
How to get a useful answer
Current- Link the page you are talking about.
- Quote the exact number or sentence that looks wrong.
- Say what you expected instead, and why.
- For calculators, include the exact inputs you used.
- One subject per email. Threads that cover four things get one answer.
Contact
Reasons to write, with the subject line already set
| Reason | Priority | What to include | Write |
|---|---|---|---|
| A ledger row looks wrong | Highest | The most useful message this project receives. Include the entry date and market, what looks wrong, and what you think it should be. | Ledger correction → |
| A calculator returns a wrong answer | High | Include the exact inputs and the output you got. The math module is covered by deterministic tests, so a genuine failure is worth a test case. | Calculator bug report → |
| Something on the site is broken or unreadable | High | Broken links, unreadable contrast, keyboard traps, screen-reader problems, or a page that will not render. Include your browser and whether you use assistive technology. | Site issue → |
| A question about the method | Normal | How something is measured, why a field is missing, or why a page says what it says. Questions that point at a specific page get better answers. | Methodology question → |
| Data, API, or research enquiry | Normal | What you would use and what for. There is no key to issue and no service deployed, so specifics matter more than interest. | Data and enterprise enquiry → |
| Privacy request | Normal | The only data this project holds is email you have sent. A deletion request is honoured by deleting the correspondence. | Privacy request → |
| Security disclosure | High | This is a static product site with no customer accounts. The early-access waitlist stores only submitted email records in a dedicated Cloudflare KV namespace; report any security or privacy issue involving it immediately. | Security disclosure → |
Corrections
Reporting an error in the published ledger
What to send
Highest priorityCopying this outline into an email is enough. Nothing here needs to be formatted or complete — a partial report about a real error is far more useful than a perfect one that never gets sent.
Entry date 2026-08-__
Market e.g. MLB moneyline, TEAM
Field entry price / closing price /
result / units / CLV / phase
Published value what the site currently shows
Expected value what you believe it should be
Source where your figure comes from,
if you have oneWhat happens next
Commitment- The row is checked against the source record.
- If it is wrong it is corrected in the underlying data and the site is rebuilt, so every derived figure updates together rather than one page at a time.
- A correction is never made silently in a way that changes a published headline figure without saying so.
- If a field was never captured it stays Not recorded. It does not get filled in retrospectively with a plausible value.
Known gaps, before you report them
Two fields are null on all 33 published rows and are already documented rather than being errors: the book each entry came from, and the model version that produced it. Both render as Not recorded.
Closing line value is deliberately not reported on the 27 in-play rows, where it would measure innings elapsed rather than price discovery. Those show n/a* by design.
Limits
What support cannot do
Tell you what to bet
Not availableNo picks, no plays, no opinions on a specific market by request. BET, WAIT, and PASS are analytic labels on demo data, not recommendations, and none of them will be given out privately either.
Help with a sportsbook account
Not availableVigPulse has no relationship with any operator. Disputes about a settled bet, a limited account, or a withdrawal go to the sportsbook first and its licensing regulator second.
Help with a VigPulse account
Not availableThere are none. No login exists anywhere on this site, nothing is for sale, and no subscription can be started or cancelled.
Provide financial or legal advice
Not availableNothing this project publishes is financial advice, tax advice, or legal advice, and no email from it becomes advice by being sent to one person.
Offer counselling for gambling harm
Not availableThis project is not equipped for it and pretending otherwise would be dangerous. The responsible gambling page lists services that are.
If gambling is causing harm
Do not write here first. The responsible gambling page lists services staffed by people trained for it, available around the clock and free to use. This project publishes research and is not a substitute for any of them.
Privacy
What happens to an email you send
What is collected
CurrentWhatever is in the message you send, and the address you send it from. This site sets no tracking cookies, runs no analytics, and has no form that submits anywhere — the mail links open your own mail client.
What it is used for
CurrentAnswering you, and fixing whatever you reported. Nothing is added to a mailing list, because there is no mailing list. Nothing is sold or shared.
Deletion
CurrentAsk and the correspondence is deleted. There is no user record to delete alongside it, because there are no accounts.