Clear, concise answers about ByteQuant
Answers about how the tools work, privacy, output limitations, and site policies.
01Where does tool input go?+
Input is processed in the active browser tab and is not sent to ByteQuant servers. Tools do not store input in localStorage. Theme and tool-usage counts are separate local values with no personal content; the usage count only ranks personal home-page shortcuts.
02Are the tools really free?+
Yes. All core tools are free and require no account. The site may later be supported by clearly labeled advertising, which will not influence tool output.
03Why are some scores estimates?+
Token and readability measures vary by model or language. Transparent estimates are intended for planning, not as an exact model tokenizer or expert linguistic assessment.
04Does the KVKK/GDPR masker guarantee compliance?+
No. It finds common patterns but cannot catch every name, rare event, or indirect identifier. Human review and, when appropriate, expert advice remain necessary.
05Does ByteQuant call an AI model?+
No. Current tools do not call a remote LLM or AI API. Prompt tools use rule-based structure checks, while NLP tools use explainable text statistics.
06Can I use very large files?+
The tools are designed for small and medium text. Input limits protect browser memory. Desktop or command-line tools may be better for very large or deeply nested data.
07Which browsers are supported?+
Current Chrome, Edge, Firefox, and Safari are recommended. Password, UUID, and SHA-256 features need Web Crypto in a secure context. Some features may fail in old browsers.
08How do I report a bug or correction?+
Email bytequant@yahoo.com with the page link and a non-sensitive example. X: @byte_quant; Instagram: @byte.quant. Use email for privacy requests.