Contact
One email address, read by a person. Corrections, bug reports, feature requests and press enquiries all welcome.
- Email, no form to fill in
- Corrections read first
- Bug reports get reproduced
- Never send personal data
Quick answer
Email hello@timecalculator.ca. That is the only way to contact the site, and it goes to a person. There is deliberately no contact form, because a form needs a server and this site has none. Corrections and bug reports are acted on fastest, and a good bug report includes the page, your exact inputs, the result you got and the result you expected.
Email hello@timecalculator.ca Best for corrections, bugs, feature requests, press Include page URL, browser, exact inputs, result vs expected Never payroll records, personal or confidential dataHow to reach us
Everything comes to one inbox. No ticketing system, no chatbot, no phone line: you write, a person reads it, and if the site is wrong it gets fixed.
The most useful messages are specific. "The overnight total looks wrong" is hard to act on. "On the hours calculator, 22:00 to 06:00 with a 30 minute break gave 7:30 but the decimal said 7.30" can be reproduced in a minute.
What we reply to
Four kinds of message get a proper answer.
Corrections
A wrong figure in a table, a formula stated incorrectly, or an explanation that teaches the wrong method. The most valuable messages we get.
Bug reports
A calculator that returns the wrong answer, refuses a valid input, breaks on your browser, or lays out badly on your screen. Include enough detail to reproduce it and it is usually fixed quickly.
Feature and tool requests
A calculation the site does not handle, an output format you need, or a whole calculator that should exist. Tell us the task, not just the feature, so we can work out the right shape for it.
Press and citation
Journalists, teachers and writers wanting to quote a page or confirm a method. Say what you are writing and your deadline.
We cannot answer questions about your own payroll, employment rights or medication schedules, or anything else needing professional advice. See the terms of use.
How to report a bug we can reproduce
A bug we can reproduce is usually fixed the same week.
Because every calculator runs inside your own browser, we cannot see what happened on your screen. There is no server log of your calculation, no session to replay and no error report sent back. That is deliberate and good for your privacy, but it means a bug report has to carry all the information itself.
Four things make almost any report reproducible: the page you were on, the browser and version, the exact values you entered, and the result you got next to the result you expected. That last pair matters, because many reported bugs turn out to be a disagreement about method rather than a fault in the code, and your expected figure tells us which it is.
What to put in the email
Copy this list into your message.
| Item | Why we need it | Example |
|---|---|---|
| Page address | Tells us which calculator to open. | timecalculator.ca/hours-calculator/ |
| Browser and version | Some faults appear in one engine only. | Safari on iPhone, or Chrome on Windows |
| Exact inputs | Lets us reproduce the run. | In 22:00, out 06:00, break 30 min |
| Result you got | Confirms we see the same fault. | 7:30 and 7.30 decimal |
| Result you expected | Separates a code fault from a method dispute. | 7:30 and 7.50 decimal |
| Screenshot | Helpful for layout problems. | Optional, crop anything private |
| What you were doing | Sometimes the sequence causes it. | Optional, one sentence |
If the tool did not load at all, say whether JavaScript is enabled and whether an extension might be blocking scripts. That one line resolves a surprising number of reports.
Corrections to what a page says
Wrong prose is worse than a wrong result: it teaches the mistake.
If an explanation, a table value or a worked example is wrong, tell us which page, quote the sentence or cell, and say what it should be. Include a source if you have one; if not, we will check it ourselves.
Corrections are made to the page itself rather than appended as a footnote, and the last updated date changes when they are. Where an error was significant enough that someone might have relied on it, we flag the change. The standard we hold ourselves to is on the about page.
Asking for a calculator that does not exist
Describe the job, not the button.
The best requests describe a recurring real task: "I total shifts for eleven people every fortnight and have to subtract two different unpaid breaks" tells us far more than "please add a break field". Include what you would type in, what you want out, and what you do instead now.
Check first that an existing page does not already cover it. The Time Calculator handles mixed addition and subtraction of durations, the Time Card Calculator covers a week of punches, the Date Calculator handles days between dates, and the Time Zone Converter deals with times across regions. The about page lists all twelve.
Why there is no contact form
A form needs a server. This site has none.
Every page here is a static file and every calculator runs as JavaScript in your browser. There is no backend application, no database and nothing that could receive a form submission. Adding a form would mean adding exactly the server side processing the rest of the site avoids.
So the contact method is a plain email address: hello@timecalculator.ca. Click the link to open it in your mail application, or copy the address by hand. Using your own client also means you keep a copy of what you sent, which a form never gives you.
Do not send personal or payroll data
We never need it and would rather not have it.
To investigate anything here we only need the numbers involved, not the people they belong to. A description of the inputs is always sufficient. Please do not attach timesheets, payroll exports, rosters, employee names, client records or other people's dates of birth.
If the values are sensitive, change them first. Replace a real pay rate with 20.00 and names with "employee A". As long as the pattern that triggers the fault survives, an anonymised example reproduces the bug just as well.
Email is not a secure channel. Anything you send passes through mail servers we do not control, so treat it as you would a postcard. Emails are used only to answer you, and are never added to a mailing list, shared or sold. If a message arrives containing personal data we did not ask for, we delete it. See the privacy policy for how the rest of the site handles information, which is to say it collects none.
How long a reply takes
Every message is read, but not instantly.
Messages are normally answered within a few business days. Reports of a wrong result come first, because a fault in the arithmetic affects everyone using that page, and a clear correction is often fixed before the reply is sent. Feature requests may be acknowledged briefly and then sit while we work out whether they fit.
If your message is time sensitive, say so in the subject line with your deadline. If you hear nothing within a couple of weeks, send it again: spam filtering catches more legitimate mail than anyone would like.
Two things worth trying first
These answer most questions that arrive by email.
Open the working. Every calculator has a panel listing what it did and the intermediate values it used. When a result looks wrong, that panel usually shows where your expectation and the calculation part company, and it is often a break, a rounding rule or a midnight crossing rather than a fault.
Read the page under the tool. Each calculator page explains its method in full, including the awkward cases, and ends with frequently asked questions. For decimal conversion, see the Decimal Hours Converter; for the 24 hour clock, the Military Time Converter; for counting days, the Date Calculator. If the answer is genuinely not there, that gap is worth an email.
Frequently asked questions
Direct answers to the questions people ask most about this calculation.
How do I contact Time Calculator?
Email hello@timecalculator.ca. That is the only contact channel for the site and it is read by a person. There is no contact form, no live chat and no phone line. Corrections, bug reports, feature requests and press enquiries are all welcome at the same address.
Why is there no contact form on this page?
A contact form needs a server to receive the submission, and this site does not have one. Every page is a static file and every calculator runs in your own browser, which is what keeps your inputs private. Adding a form would mean adding the server side processing the rest of the site avoids, so we use a plain mailto link instead.
What should I include in a bug report?
Four things: the page address, your browser and version, the exact values you entered, and the result you got alongside the result you expected. Because calculations run on your device, we have no log of what happened, so the report has to carry everything. A screenshot helps for layout problems.
Can I send you my timesheet so you can check it?
Please do not. We never need real data to investigate a problem, only the numbers that trigger it. Replace names with "employee A" and real pay rates with a made up figure. Do not send payroll exports, rosters, dates of birth or medical information. An anonymised example reproduces a bug just as well as a real one.
How long will it take to get a reply?
Usually a few business days. Reports of a wrong calculation are prioritised, since a fault in the arithmetic affects everyone using that page. Feature requests may get a short acknowledgement and then take longer. If you have not heard anything after a couple of weeks, send it again, because spam filters catch more legitimate mail than they should.
Can you help with my payroll or employment question?
No. We can explain how a calculation on this site works and fix it if it is wrong, but we cannot advise on whether a break should be paid, what overtime you are owed, or how a rule applies to your contract. Those questions need someone qualified who knows your jurisdiction and your circumstances.
Can I suggest a new calculator?
Yes, and requests that describe a recurring real task are the most likely to get built. Tell us what you would enter, what you would want back, and what you do at the moment instead. Check the list of the twelve existing tools on the about page first, in case the calculation is already covered.