Privacy

Account information: the email address and identity details provided when you sign up, handled through our authentication provider.

Content you publish: the HTML documents you send, along with the metadata attached to them such as titles, project names, visibility settings, and expiry times.

Usage records: which API keys were used, when artifacts were published or updated, and activity events shown in your dashboard.

Technical records: server logs and error reports generated when the application handles a request or fails.

Optional analytics: product usage events, collected only if you accept analytics cookies.

We do not store card numbers or payment credentials. Payment details are entered with and held by our payment processor.

We do not sell personal information, and we do not share it with advertisers.

We do not read your published HTML for advertising, model training, or profiling.

The HTML source you publish is stored in object storage. The metadata describing the artifact is stored in a Postgres database. Both are hosted by the sub-processors listed below.

Artifact and project share pages are unlisted and carry a noindex directive. An unlisted link is unguessable and excluded from search indexes, but anyone who receives the URL can open it. It is not access control, and you should not treat it as such.

The following services process data on our behalf in order to run BinHTML.

Essential cookies are used for authentication, session handling, and recording your cookie choice. These are required for the service to function.

Analytics cookies are optional and are only set after you accept them. You can change your choice at any time using the cookie settings control in the site footer. Declining analytics does not restrict any feature.

Published artifacts are retained according to the retention window on your plan. Builder artifacts expire after three days. Pro artifacts can be permanent or given a custom expiry.

When an artifact expires or is deleted, the scheduled retention process removes both the stored HTML source and its metadata. Expired artifacts are not recoverable.

Account records and billing records are retained while the account is active, and afterwards only for as long as needed to meet legal and accounting obligations.

You can download the source of any artifact you own, delete individual artifacts, revoke share links, and delete your account from the dashboard. Deleting your account removes your artifacts and their stored source.

Depending on where you live, you may also have rights to access, correct, export, or erase personal data we hold, and to object to certain processing. Contact us to exercise them.

Published HTML renders in a sandboxed context, isolated from the application, so a generated document cannot act with the privileges of the surrounding page. Access to artifacts is scoped to the owning account, and publishing requires an API key or an authenticated session.

No system is perfectly secure. Do not publish credentials, secrets, or sensitive personal data. If you discover a security issue, report it to us directly rather than disclosing it publicly.

BinHTML is not directed at children and is not intended for use by anyone under 16.

If this policy changes materially, the effective date above is updated and the change is noted in the changelog. Continued use after a change means you accept the updated policy.

For any privacy question, data request, or security report, email help.binhtml@outlook.com.