Contact

Questions, feedback, or suggestions? We’d love to hear from you.

Email us at: everydayroyalties@gmail.com

We typically respond within 1–3 business days.

Contact & Help

We’re here to help with tool questions, bug reports, accessibility issues, and content suggestions. The fastest way to reach us is by email. We read every message and prioritize issues that block access or accuracy.

DMCA & Copyright

If you believe something on this site infringes your rights, email the address above with:

  1. Your contact information.
  2. Identification of the copyrighted work.
  3. URL(s) of the material you believe is infringing.
  4. A statement of good-faith belief that the use is not authorized.
  5. A statement under penalty of perjury that the information is accurate and you’re authorized to act.

How We Triage Requests

We prioritize issues that affect access, accuracy, or privacy. If the readability tool produces a result you suspect is incorrect, include a short text sample and your expected outcome. For bug reports, add your browser, OS, and steps to reproduce.

Feature requests are welcome. Tell us the job you need to do and why the current workflow falls short. Real examples help us design options that stay simple for most users while unlocking power when needed.

Common Questions

  • How are Flesch and FK Grade calculated?
  • Why might my score differ from other tools?
  • Can I request a new feature or improvement?

How We Can Help

We support writers, editors, educators, and developers who want fast, privacy-friendly text analysis that leads to clearer results. If you have a question about a score or you suspect a counting error, send a short excerpt (100–300 words) and tell us what you expected to see. We’ll replicate the scenario and explain what the algorithm is doing under the hood.

For bug reports, include your browser and operating system, the exact steps to reproduce the issue, and any error messages you see in the console. This information helps us fix issues quickly and prevents regressions in future releases.

Response & Escalation Policy

What to Include in Your Message

Help us help you: share the purpose of your text (blog, help doc, email), your audience, and any constraints like word count or reading level requirements. If you’re improving a document for a specific reading level, tell us the target band so we can suggest the best edits.

Common Topics

  • Differences between Flesch and FK Grade
  • Sentence boundary edge cases (abbreviations, decimals)
  • Syllable heuristics and known limitations
  • How to lower grade level without losing meaning

Feature Requests

Tell us the job you’re trying to do. For example, “Ignore hyphenated brand names” or “Treat code blocks as single tokens.” Use cases guide our roadmap and help us keep the interface simple.

Privacy Notes

Analysis runs locally in your browser. We don’t store the text you paste. If you email us content for debugging, remove sensitive data or replace it with realistic placeholders.