HTML to App HTML tools for your own Mac
Privacy Policy

Privacy policy

This policy covers the website, the HTML to App macOS app, and the exported app bundles created with it.

Website analytics

This website uses Plausible Analytics for privacy-focused traffic measurement. It does not use cookies for analytics, and it is configured to avoid storing personal data such as full IP addresses.

HTML to App macOS app

Project creation, source editing, and export work offline. The project list and app settings are stored locally on your Mac. HTML to App does not collect usage analytics or send your project files to a server. A project running in Preview may load remote resources referenced by its own HTML or JavaScript.

Exported app bundles

Exported apps also send no data and collect no analytics on their own. If the HTML project you wrap contains JavaScript code, embedded internet resources, or external APIs, that content may still load network resources because it is part of the HTML project itself.

Sandboxing and file access

The main app and exported app bundles are sandboxed. When you create or add a project folder, you authorize the workspace to work with that location. Saving source edits writes to the original folder. Export destinations are selected through a standard macOS save dialog.

Besides its own app container, every exported app includes read-only permission for the Downloads folder by default, even when individual Downloads files have not been selected. That permission does not grant write access to Downloads. macOS privacy protections still apply.

Reference-mode apps also receive read-only access to the selected source folder. Open and save dialogs authorize additional locations. With the Open With role set to Editor, the JavaScript bridge can write back within the specific file or folder opened into the app. Exports do not receive unrestricted access to the rest of your disk.

Optional local-launch script

You can review and explicitly install the optional approval script from the export completion screen. It runs outside the App Sandbox to remove quarantine from the specific app you exported. Once installed and up to date, it runs automatically after later exports. It does not send data, change the app's signature, grant privacy permissions, or disable Mac-wide security settings.

Remove the script through Scripts Folder to disable automation. See the first-launch documentation for installation, manual handling, and the limits of local approval.