User-written code and imported files
HTML, CSS, JavaScript and project assets entered or imported into the editor are processed in the browser. HTML Viewer does not upload those project contents to an application database or provide cloud project storage. Browser memory, local object URLs, client-side storage and download APIs support editing, preview and export.
Browser storage
The application can store preferences such as theme, split-panel size, locale and cookie choices in local storage. This information stays in the browser profile until the user clears site data or changes the preference. The editor may also use service-worker and cache APIs to support project previews and offline behavior.
Third-party resources
The page may request Google Fonts and the Monaco editor from externally hosted services. Those providers receive normal web-request information such as IP address, user agent and referrer according to browser behavior and their own policies. Loading an external library is separate from uploading the contents of a user’s project.
Analytics and consent
Google Tag Manager and analytics are loaded only when analytics or marketing consent has been granted. Consent preferences are stored locally and can be changed from the cookie settings. When consent is denied, HTML Viewer does not intentionally load the analytics container.
Accounts and personal profiles
The editor does not require registration and does not maintain an account database. If a user contacts the project by email, the email provider processes the message and address for the purpose of replying.
Control and deletion
Users can clear local site data through browser settings, remove imported files from the editor and reject optional cookies. Because project contents are not stored as hosted projects, there is no remote project record to delete from an HTML Viewer account.
Contact
Privacy questions can be sent to guillemball09@gmail.com. This policy was last updated on June 21, 2026.