Contact Us

The ClearHire contact page is the canonical entry point for support, partnership inquiries, press, bug reports, and feature requests. ClearHire is independently maintained, so the same developer (aoneahsan@gmail.com, +923046619706 on WhatsApp) handles all incoming channels. Typical first reply within 24 hours on weekdays. Security issues are acknowledged within 72 hours per the policy at /.well-known/security.txt. Different channels have different latency: the contact form is best for general support, email for longer issues, WhatsApp for time-sensitive ones, and the security email for vulnerability reports. Picking the right channel saves a round-trip.

Use cases

• Reporting a bug. Use the contact form and tag as "bug report". Include a screenshot, the exact URL where the issue occurs, your browser + OS, and the steps to reproduce. Reproducible bugs get prioritized; vague ones get clarification questions first.
• Requesting a feature. Tag as "feature request" and include the problem you are trying to solve, not just the solution. Feature requests are reviewed weekly. Common, well-explained requests ship faster than rare or vaguely-described ones.
• Partnership or press inquiries. Email is faster than the form for these. Include the specific ask up front (interview, integration, distribution, etc.) so the response can be substantive on the first reply.
• Security disclosures. Follow /.well-known/security.txt rather than the public form. Email or address listed there. Acknowledged within 72 hours; please do not open public GitHub issues for security findings.

How it works

1. Pick the channel matching the urgency and topic. Form for general support and bugs. Email for partnership, press, longer issues. WhatsApp for time-sensitive issues. Security email for vulnerability reports.
2. Include reproducible context for bugs. Screenshot, URL, browser + OS, steps. The first reply on bugs without these is always a request for them — saving a round-trip helps everyone.
3. Allow up to 24 hours for the first reply. Weekdays are fastest. Weekend / holiday replies are slower; urgent items via WhatsApp jump the queue.

Examples

• A user finding a UI bug on the resume builder. Opens the form, attaches a screenshot, lists the URL and browser, and gets a first reply within 6 hours with a fix ETA.
• A potential partner exploring an integration. Emails aoneahsan@gmail.com with the integration goal and target use case clearly named. First reply lands the same business day with concrete next steps and any technical requirements.
• A security researcher disclosing a vulnerability. Reads /.well-known/security.txt, emails the listed contact privately. Acknowledged within 24 hours, fix shipped within the disclosure window agreed in the reply.

Frequently asked questions

Tips

• Tag your message — "bug", "feature", "partnership", "press" — so it routes correctly.
• For security findings, never open public GitHub issues; use the private channel.
• Feature requests with a clear problem statement get prioritized over feature requests phrased only as solutions.
• Include browser, OS, and exact URL on every bug report — this saves a clarification round-trip.
• Mention urgency and ideal response time in your message; the developer can route accordingly.

Author: ClearHire Editorial · Last updated: 2026-05-06