Privacy Policy

HTML2Liquid handles only the information needed for the feature you choose. Account creation and sign-in use an email address, password credential handled by the authentication provider, session information, and an internal account identifier. The AI fair-use counter stores a usage count and last-call date for signed-in accounts.

The contact form sends the name, reply email, subject, and message you submit. Do not include store passwords, customer records, private theme credentials, API keys, or other secrets.

Manual conversion posts your HTML to this site's conversion route, where it is parsed to produce Liquid and schema. That route does not write the submitted HTML or result to the project database. Hosting infrastructure may still process ordinary request metadata needed to deliver and secure the service.

If you explicitly choose AI-assisted conversion, the submitted HTML is sent to the configured Google Gemini service so it can generate a response. Do not use AI mode for confidential code or data you are not authorized to share.

The site uses browser local storage for theme preference and tool state such as schema-builder drafts, cheatsheet favorites, recently viewed snippets, mock data, and preview CSS. This data remains in your browser until you clear it or the feature replaces it.

Authentication uses cookies or equivalent session storage supplied by Supabase. Browser controls can clear local data and cookies, but doing so can sign you out or remove saved tool preferences.

• Supabase provides account authentication and account-profile storage.
• Google Gemini processes HTML only when AI-assisted conversion is requested.
• Resend delivers messages submitted through the contact form.
• Google Analytics measures page and device usage to understand site operation and content use.
• The hosting provider processes requests, logs, and network information needed to serve and secure the website.

These providers process data under their own terms and privacy documentation. Their infrastructure can involve processing outside your country.

The site contains an AdSense publisher-verification meta tag and an ads.txt seller record, but it does not currently render visible ad units. If ads are enabled later, this policy will be updated to describe the active advertising technology and controls. Visible units are intended only for substantial editorial articles, not tool interfaces, generated output, account pages, contact pages, legal pages, or error states.

Information is used to provide requested tools, authenticate accounts, enforce fair-use limits, answer messages, troubleshoot failures, secure the service, and understand aggregate usage. HTML2Liquid does not sell personal information.

Account and service-provider records are retained only as needed for those purposes, provider operation, security, and legal obligations. The account page provides an account-deletion control. Contact messages may remain in the recipient mailbox until they are no longer needed for support or recordkeeping.

You can use manual conversion, the schema builder, the cheatsheet, and tutorials without creating an account. You can avoid sending code to Gemini by not selecting AI mode, clear browser storage through browser settings, use browser privacy controls for analytics, and delete a signed-in account from the account page.

Depending on applicable law, you may request access, correction, deletion, or information about personal data associated with you. A request may need reasonable identity verification.

This policy will be revised when the data flow materially changes, including before visible advertising or a new paid service is introduced. The date at the top identifies the current version.