Last updated: October 2026.

HtaccessGen generates Apache configuration files inside your browser tab. This policy lists every category of data involved and what happens to it — which is mostly “nothing.”

1. What you type into the generator — never transmitted

Your domain, redirect paths, IP addresses, .htpasswd path, PHP values and every other field are read by JavaScript running on your own machine and turned into text in the output panel. There is no server-side component that could receive them — the page makes zero data requests after it loads. Open the network inspector and confirm: page assets in, nothing out.

2. Storage on your device

The generator writes nothing to cookies or browser storage. Toggle a setting, close the tab, come back — you’re at the defaults again. There are no accounts, no saved files, no draft history.

3. Server logs (Cloudflare)

Pages are served through Cloudflare’s edge network, which necessarily processes routine request metadata — your IP address, the URL fetched, timestamp, user agent — to deliver content, resist abuse and produce aggregate statistics. We hold no user data those records could be joined with.

4. Advertising

The site may show ads via third-party networks such as Google AdSense to cover hosting. Those networks can use cookies or similar identifiers to count impressions and, where permitted, personalize ads. Manage personalization in Google’s Ads Settings or block third-party cookies — the generator is identical either way, and ad systems cannot see your inputs (they never leave the tab).

5. Analytics

If we measure usage at all, it is aggregate page-view counting — no per-user tracking, and the generator’s fields are outside any measurement by design: the tool’s code has no telemetry channel.

6. Changes and questions

Revisions are posted on this page with a fresh date. Questions: hello@nxtolerance.com.