Organizational publisher with no invented personal credentials.
CONTACT
Send bugs, suggestions, and corrections directly to us
Use email or our social channels for tool bugs, accessibility issues, content corrections, and collaboration ideas. Do not include sensitive text or real personal data in your message.
WHO · HOW · WHY
See the publisher, method, and correction route at a glance
Method, examples, errors, and acceptance checks are reviewed before release.
Reports arrive by email; confirmed fixes link tests and Git history.
General support, privacy requests, and content corrections: [email protected]. Include the relevant page, browser type, and steps needed to reproduce the issue.
Do not send passwords, API keys, identity numbers, customer records, or confidential files. Describe the issue with anonymous sample data.
Social media
For short announcements and tool updates, follow @byte_quant on X and @byte.quant on Instagram. Account or privacy requests should be sent by email rather than social media.
Writing a useful bug report
Briefly explain what happened, what you expected, and what actually occurred. Use a non-sensitive sample when possible and mask personal data in screenshots.
- Page or tool name
- Browser and device type
- Reproduction steps
- Expected and actual result
- A non-sensitive example
Content corrections and source suggestions
If a guide contains outdated information, a translation problem, or a claim you cannot verify, identify the paragraph and page URL. When possible, support the proposed correction with a primary or institutional source.
Editorial review compares the report with the source, its scope, and the product’s observable behavior. When a correction is needed, related tool copy, structured data, and other language versions are reviewed together rather than changing one isolated sentence.
Accessibility and usability support
For keyboard focus, screen-reader labels, colour contrast, mobile overflow, or unreadable text, include the assistive technology and viewport size you used. That context helps reproduce the same issue under realistic conditions.
ByteQuant does not need personal data, files, or tool output to investigate a support request. If a workflow must be described, remove the real record and use a synthetic example that preserves only the relevant shape.
Response approach
We aim to review messages within a reasonable period but do not promise a fixed response time. Security reports are prioritized. Spam, abuse, and unlawful requests may not receive a response.
Is anything unclear?
Send email →