Skip to content

privacy.md

Latest commit

 

History

History
57 lines (33 loc) · 3.44 KB

privacy.md

File metadata and controls

57 lines (33 loc) · 3.44 KB
Raw

Privacy Policy

This page explains, in plain language, how WebFileTools handles privacy. WebFileTools is a collection of browser-based file and developer tools published as a static website. You can read this document on GitHub or the matching page on the site.

What this site is

WebFileTools is hosted on GitHub Pages as static HTML, CSS, and JavaScript. There is no WebFileTools application backend that receives your documents for conversion.

When you open a tool, the page runs in your browser on your device. You choose files or paste text, the tool processes them locally, and you download or copy the result.

File processing stays on your device

Files you select for tools are read and processed in the browser. There is no upload API operated by this project for conversion, so those files are not sent to WebFileTools servers for processing.

Processing uses browser APIs (for example File, Canvas, and Web Crypto) and open-source libraries shipped as static assets with the site.

  • Tool file contents and conversion payloads stay in the browser session on your device for that work.
  • Results leave your device when you download or copy them yourself, or when you share them through other apps.
  • If you clear the page or close the tab, in-memory working data for that session is typically discarded by the browser.

Load on your device

Some tools—especially large PDFs, many images, or heavy archives—may use a lot of memory or CPU on your computer or phone. That is normal for local processing: the work runs here instead of on a remote conversion server.

If a tool feels slow or the tab becomes unresponsive, try smaller files, fewer pages, or closing other heavy tabs.

Site metrics (separate from file tools)

Separately from the tools, the site may measure visits and page usage. Those metrics are about the website itself. Your files are not included—file contents, tool filenames, and conversion payloads are not sent as part of analytics.

Google Analytics

  • May be enabled via a measurement ID at build time.
  • May set cookies for analytics only (no ads, no login cookies from this project).

Visit counter (home page)

  • The home page may load a hit-counter image from count.getloli.com (Moe Counter / getloli).
  • Loading that image typically lets the counter service see normal HTTP request metadata (for example IP address, User-Agent, and referrer, depending on browser and Referrer-Policy).
  • We do not send your tool files to this service. The counter is for display and visit counts only.
  • Provider: count.getloli.com

What this project does not do

  • No advertising network on the site.
  • No application error telemetry that phones home when a tool fails.
  • No account system and no login cookies issued by WebFileTools for user accounts.

Hosting limits and this document

GitHub Pages serves static files. Features of that hosting (availability, caching, TLS termination at the CDN, and so on) are outside this project's direct control.

This document describes how the published site is designed to work. It is not formal legal advice for your situation, and it is not a warranty beyond what a static open-source site on GitHub Pages can reasonably provide.

Questions and reports

If something looks wrong, or you have a privacy-related question about the published site, please open a GitHub Issue. That is the main contact channel for this project.