Website privacy
Byte-Case.com is a public website for ByteCase by Forensics Byte. It does not provide user accounts or accept case evidence. Hosting, security, and traffic-measurement services may process limited technical information such as IP address, browser type, requested pages, timestamps, and security events.
Product feedback should describe software behavior or workflow needs without case material, passwords, credentials, or protected investigative information. The website feedback form is separate from license requests and does not accept .bcreq attachments or issue licenses.
Hub license requests
License requests are sent by email using the instructions on the Hub licensing page. Forensics Byte uses the request and reply address to review the installation and examiner details, clarify the request, and issue an approved license.
The .bcreq contains a random installation ID, ByteCase version, agency and configured examiner identity, timestamp, and nonce. It does not contain cases, evidence, findings, file paths, network identifiers, hardware inventory, or credentials. Do not attach case records or evidence to a licensing email.
The signed .bclic is imported locally. Hub activation and normal case work operate offline; license requests are not automatically submitted by Hub.
ByteCase desktop tools
ByteCase tools keep case records in user-controlled local storage. No ByteCase module should silently transmit case information. Release documentation should identify any network connection, telemetry, update check, crash reporting, recent-case history, temporary files, or external-service access that applies to that version.
Users remain responsible for reviewing the release and following agency policy before using it in an operational workflow.
GitHub downloads and reporting
The Hub installer and verification records are hosted in the public GitHub release repository. GitHub applies its own privacy practices when a visitor opens a release or downloads an asset. Standalone tools may also link to public source and issue repositories; Hub source remains private.
The download reporting page reads GitHub’s public installer download count. It does not add telemetry to Hub, identify individual downloaders, or record license activations. The count includes repeat, test, and automated downloads and is not a count of unique users.
Do not place license request attachments, evidence, passwords, or protected information in a public GitHub issue.
Questions
Use the ByteCase contact page to raise a privacy question without including sensitive details. Use the security reporting guidance for a security concern.