Contact BPMCalculator.site

The direct support route

To contact BPMCalculator.site, email support@bpmcalculator.site. The mailbox is intended for formula corrections, reproducible browser problems, accessibility feedback, privacy or legal requests, and proposals that fit the site’s narrow timing mission.

There is no contact form in the launch product. Clicking the address opens or hands off to the mail software configured on your device. That action is no longer an in-page calculation: your email provider, network provider, and the recipient’s mail systems process the message under their own terms.

Report a formula issue

The strongest correction report names the page, preserves the units, and shows the expected arithmetic. Include the exact input labels and values you used, the displayed result, the result you expected, and why. If the disagreement concerns a musical convention, explain which note value the BPM counts and how meter should be interpreted.

For example, “On the bar calculator, 60 BPM with a dotted-quarter reference in 6/8 and two bars should total four seconds” is actionable. “The bar time looks wrong” leaves the central convention unknown.

Please do not attach copyrighted audio, private session files, or large project exports. The tools do not analyze those materials, and support does not need them to review deterministic arithmetic.

Report browser behavior

For an interface defect, include the route, browser name and version, operating system, viewport or device class, and a short sequence beginning from a fresh page load. State whether the issue affects data entry, validation, results, copy behavior, reset, focus order, or visual layout.

A useful sequence might read: “Open the note-duration calculator, enter 85.5, select dotted eighth, press Calculate with the keyboard, then Reset; focus moves outside the tool.” Avoid sending browser profiles, extension inventories, IP addresses, or other unrelated diagnostics.

Screenshots can help with visual defects, but redact names, tabs, account identifiers, and unrelated applications before sending. A text description is often sufficient.

Accessibility feedback

We welcome reports about missing labels, keyboard traps, focus visibility, error announcement, heading order, color contrast, zoom behavior, motion, or ambiguous result language. Explain the expected interaction and the point where it fails. If you use assistive technology, naming the technology and version is helpful but optional.

Accessibility reports are product issues, not requests for a medical explanation. We will use the smallest necessary information to reproduce the behavior.

Privacy and rights requests

Use the same mailbox for a privacy question or request. Put “Privacy request” in the subject and identify the jurisdiction or right you believe applies. Because calculation fields remain in the browser and no account system exists, BPMCalculator.site generally cannot search for a calculation or profile.

Email correspondence itself is different. To help locate a prior message, write from the same address when practical and provide its approximate date and subject. Do not email identity documents unless support specifically explains why verification is necessary and provides a proportionate method.

Focused product proposals

A proposal is most useful when it begins with a known input, names a deterministic output, and describes why an existing route does not answer the question. State the mathematical convention and one worked example. Ideas requiring audio upload, remote lookup, a DAW connection, an account, or a catalog fall outside the launch architecture.

We may use general, non-confidential feedback to improve the service. Do not send trade secrets, unreleased music, contract material, or an idea you expect us to keep confidential.

What support cannot do

Support cannot retrieve erased fields, restore a prior result, identify a song, evaluate a mix, inspect a file that never reached the site, or guarantee a value will behave identically in third-party equipment. The mailbox is not emergency support and does not provide legal, financial, medical, or engineering certification.

Response times are not guaranteed. Sending a message does not create a professional-services engagement or a confidential advisory relationship.

Model support report

Subject: “Delay offset calculation at 127.5 BPM.” Body: “Route: /tools/delay-time-calculator. Browser: current Firefox on Windows. Inputs: 127.5 quarter-note BPM, dotted eighth, three taps. Observed second offset: 705.882 ms. Expected: 705.882 ms, but the copied summary rounds it to 705 ms despite three-decimal display. Reset restores correctly.”

That report separates formula correctness from formatting behavior and contains no sensitive media.

Frequently asked questions

Is there live chat?

No. The published support method is email.

Can support recover my last timing table?

No. The application does not keep a server-side calculation history.

Should I send a DAW project?

No. Reduce the issue to input values, units, expected formula, and observable behavior.

Where do I report a security concern?

Email the support address with a restrained reproduction. Do not access other people’s data or disrupt the service.

Send the smallest safe example that demonstrates the problem, and keep a copy of your message for your own records.