This policy explains what information is processed when you visit bytequant.org and how the in-browser tools work. In the current version, tool inputs are not sent to ByteQuant servers.
This policy covers the ByteQuant site, tools, guides, and contact channels. Privacy questions and data-subject requests can be sent to bytequant@yahoo.com. Only information needed to verify and answer a request may be requested.
ByteQuant is an independent web project. This notice provides transparency; specific legal duties depend on actual operation and establishment.
Prompt, text, JSON, CSV, Regex, password, and similar inputs are processed in your browser. They are not sent to ByteQuant servers, linked to an account, or stored in localStorage by default. Refreshing or closing the page removes active-session input.
Copying or downloading creates a new copy on your device. Clipboard history and downloaded files on shared devices remain under your control.
The light/dark theme may be stored under bq-theme, while tool-page visit counts may be stored under bq-tool-usage-v1 in localStorage. Usage records contain only a tool slug, count, and last-used time; they contain no tool input, file, password, or generated output and are not sent to a server.
These local values power the personal 'Most Used Tools' shortcuts and theme choice. You can remove both by clearing site data. The current version does not set non-essential analytics or advertising cookies; if that changes, this policy and any required consent controls will be updated before activation.
The site is designed for static hosting on GitHub Pages. Hosting and network providers may process standard connection records—IP address, timestamp, request path, and user agent—for security and delivery under their own policies. Tool input is not included in those requests.
Independent processing by GitHub, domain, or network providers is governed by their current privacy notices.
The layout includes clearly separated reserved advertising areas; the delivered source package contains no active ad identifier or ad script. Before Google AdSense or another service is activated, cookies, personalization, consent management, vendors, and refusal options must be documented here.
Tool input should never be shared for advertising, and ad components should remain technically separated from the workbench.
Where applicable, you may have rights to information, access, correction, deletion, restriction, objection, and portability. Because ByteQuant does not retain tool input on a server, it cannot centrally access or delete that text; it remains on your device.
Requests can be emailed to us, and you may complain to a competent supervisory authority. Exact rights depend on location and legal context.
Static architecture and minimization reduce risk but cannot guarantee absolute security. Avoid sensitive work on shared devices, keep your browser updated, and manage copied output carefully.
The service is not directed specifically to children. Material policy changes will be posted here with a new date and clear explanation.