Exact under stated rules
Calendar and arithmetic tools can often produce exact outputs once the input and convention are defined. Example: days between two Gregorian dates.
TRUST · TRANSPARENCY · METHOD
How EgoTools decides what a number is allowed to mean.
We build playful tools, but we do not want playful presentation to blur the difference between an exact calculation, a rough estimate, a browser measurement and a made-for-fun score.
Why this page exists
EgoTools mixes exact calculators, browser performance games, probability demonstrations and entertainment quizzes. Those categories do not deserve the same level of certainty. Our job is to make the difference visible instead of dressing every result up as scientific truth.
1. We classify every result before we write about it
Estimated
Some outputs depend on assumptions. Lifetime heartbeat counts, for example, require an assumed average heart rate unless the user provides better data.
Measured in-browser
Reaction, clicking and typing games record events in the browser. The measurement is real, but it includes device, display and software latency.
Entertainment score
Personality-style quizzes use transparent game scoring. We do not present those scores as diagnoses, clinical assessments or population percentiles unless a real dataset supports that claim.
2. We keep the conclusion narrower than the measurement
If a game records your time to click after a visual signal, we call it a browser reaction-time score. We do not jump from that result to claims about intelligence, neurological health or athletic potential. If a quiz adds points from answers, we explain that the output is an entertainment score.
3. We expose scoring logic and important assumptions
Where practical, each tool explains how the result is produced. For calculations this includes formulas or calendar conventions. For games it includes what starts and stops the timer, whether lower or higher is better and how false starts or errors are handled.
4. We distinguish first-party calculation from external data
Many EgoTools experiences run entirely from user input in the browser. When a tool relies on an external public source — for example historical events or public knowledge data — the page should identify that dependency. External data can be incomplete or change over time.
5. We use sources where a factual explanation benefits from them
Technical articles link to standards and documentation such as W3C and MDN when describing browser timing. Psychology explainers may link to classic or review literature when discussing established effects. A source link does not turn a mini-game into a standardized research instrument; it supports the explanation around the game.
6. We write for humans before search engines
A page should still be worth publishing if search traffic did not exist. That means the text must answer a real question, explain a tool, reveal a limitation, teach the mechanism or help someone interpret a result. We do not target a fixed word count, and we do not add paragraphs only to make a page look long.
7. AI-assisted production is reviewed, not blindly published
Software and language models can assist with drafting, coding, structure and quality checks. EgoTools remains responsible for the final page. Claims, formulas, links, tool behavior and user-facing limitations are reviewed before publication. Automation is a production aid, not an excuse to publish unverified filler.
8. Corrections are part of the product
If a formula, factual explanation, link or technical statement is wrong, we want to fix it. Send the page URL and the issue to contact@egotools.fun. Material corrections may also be reflected in page modification dates.
9. What EgoTools deliberately does not claim
- Mini-games are not medical or psychological diagnoses.
- Entertainment quizzes are not validated clinical personality tests.
- Browser timing scores are not laboratory-grade measurements.
- Estimated life statistics are not exact personal histories unless the inputs genuinely support exact calculation.
- Public-data tools may inherit gaps or errors from their source.
10. The editorial test before a new page ships
- Does the page have a clear user question or purpose?
- Does it contain information that is specific to this tool or topic?
- Can the scoring/calculation be explained plainly?
- Are the important limitations visible near the claim?
- Would we publish it even if it brought no Google traffic?
- Does it link to a useful next step rather than trapping the user in a thin page?
When the answer to those questions is no, the page needs more work or should not exist.