SiteCheckPrivacy
The current website preview processes HTML and imported reports in your browser. It does not upload the selected files or fetch the page URL you enter. Parsing does not execute supplied scripts or load supplied images, fonts or other resources.
What is saved
The site saves only the light/dark theme preference in local storage. It does not save HTML, audit reports or input URLs to an account, local storage or IndexedDB. The active document and report stay in page memory until you clear the workspace or leave the page. This is not a promise of forensic memory erasure.
Exported files remain in your browser's download location under your control. Findings can contain page text, selectors and filenames, so review exports before sharing them. Displayed target URLs omit query strings and fragments; content excerpts can still include private information. New browser reports retain a SHA-256 fingerprint of full requested/final URLs and scope to prevent mismatched comparisons. A hash is not encryption or a promise of anonymity.
Hosting requests
Your browser fetches this site's public application files. The host handles normal request metadata such as IP address and browser information to serve the website. This build contains no advertising, third-party analytics, remote fonts or GPT API calls.
Separate browser runner
The local browser runner visits authorized targets and approved public resource origins from the machine running it. Those target servers receive the runner's requests. It stores generated reports, screenshot manifests and optional baseline copies/diff images in a local reports folder. Local report.html files have no scripts, block external resources and are marked noindex. Do not publish private report folders; indexing directives do not provide access control. It does not send them to this website. Browser extensions, the local operating system and any tools you use to share reports are outside SiteCheck's control.
Future services
Hosted URL scanning, account sign-in, history, scheduling and payments are not active in this preview. They require verified account ownership, isolated execution, quotas, retention controls and real integration testing before release.