Privacy Policy

How bitlist handles data, browser storage, and external service requests.

1. Processing Model

bitlist is primarily a browser-side application. Most tools process data locally on your device and do not require account creation. This includes tools such as password generation, JSON formatting, text comparison, hashing, and many conversion workflows.

2. External Requests for Specific Features

Some network-oriented tools make requests to third-party services to produce results. These calls go directly from your browser to the provider โ€” bitlist does not proxy or log them. The table below lists every external service used, what data is sent, and why.

Tool Service Data sent Purpose
My IP Address freeipapi.com Your IP (implicit in request) Primary IP detection with ISP and location data
My IP Address ipify.org Your IP (implicit in request) Fallback IPv4 / IPv6 detection
DNS Lookup Cloudflare DoH Domain name you query DNS resolution via DNS-over-HTTPS
DNS Lookup Google DoH Domain name you query DNS resolution via DNS-over-HTTPS
Website Status URL you enter HTTP request to the URL you provide Reachability probe โ€” no data extracted

Each provider operates under its own privacy policy. bitlist does not share, store, or forward data obtained from these requests beyond rendering it in your browser.

3. Local Storage and Preferences

bitlist may use browser Local Storage for product preferences such as selected theme and layout options. These values stay in your browser and can be cleared at any time through browser settings.

4. Data You Submit via Contact Channels

If you submit feedback or bug reports through external forms or social channels, the information you share is processed by those platforms under their own policies. Avoid including sensitive credentials, personal identifiers, or confidential business data.

5. Security and Good Practices

  • Prefer local processing tools when handling sensitive technical payloads.
  • Review output before sharing or exporting.
  • Do not paste secrets into public channels when reporting issues.

6. Policy Updates

This policy can be updated as tools and integrations evolve. Material changes will be reflected on this page with updated language for transparency.