Privacy Policy
QuickerConvert is designed around local processing for supported workflows. Browser tools run in the tab, and accurate desktop workflows use QuickerConvert for Windows on the same device.
Local processing
- Supported PDF tools avoid unnecessary upload steps.
- The original file remains on your device.
- The app creates a new downloadable result for the task you choose.
- Large, encrypted, scripted, or unusual files may need more time and should be reviewed after processing.
Advertising, cookies, and consent
Essential first-party operational events may contain the tool or public route, a coarse status or error category, file count, bounded duration, release mode, a daily random session identifier, and coarse browser, operating-system, and device families. This event design excludes file names, types, exact or bucketed sizes, bytes, page text, extracted data, previews, signatures, document metadata values, query parameters, and raw errors. Ordinary network requests still expose connection data such as an IP address to the server and hosting provider. The ingestion endpoint uses the Cloudflare-provided connecting IP briefly in isolate memory for abuse limiting; application code does not write it to monitoring rows or alert webhooks.
Optional public-page measurement is off until a visitor accepts it. Before acceptance, or after rejection, QuickerConvert does not load its Google Tag Manager container or Meta Pixel. These vendors are always disabled on active /app document workflows and admin routes.
- Google Tag Manager delivers QuickerConvert-controlled measurement tags. The approved public page-view payload contains the public path, public URL without query or fragment, and title. Google tags may also receive browser, device, network, cookie, or advertising-identifier information.
- Meta Pixel receives a standard public-page PageView after acceptance and may receive the public URL, browser, device, network, and identifiers such as _fbp or _fbc.
The disclosed purposes are audience measurement, public-page usage analysis, marketing attribution, and advertising measurement. Google and Meta may treat connection or identifier data as personal data and process it according to their policies.
Storage, retention, and withdrawal
Files are not stored in browser storage. Limited first-party storage remembers interface or native onboarding preferences, a daily random operational session identifier, and the optional-analytics choice. The consent record remains until changed, cleared, or superseded by a new consent version.
Google documents a default two-year lifetime for _ga and 2- or 14-month Analytics user/event retention options for standard properties. Meta documents typical 90-day lifetimes for _fbp and _fbc. Vendor periods and settings can change.
Visitors can use Privacy choices to reject or withdraw at any time. Withdrawal prevents future optional tracking and starts a clean page load. QuickerConvert attempts to clear readable analytics cookies on its domain, but cannot erase information already received by a vendor or cookies controlled on another domain. Browser site-data controls and vendor opt-out settings remain available.
Advertising and regional consent
If ads are enabled, they belong only on public content and not beside upload, preview, edit, export, or download controls. Google and selected ad technology providers may use cookies for advertising subject to visitor choices and applicable law.
The current privacy-choice control covers the optional Google Tag Manager and Meta measurement described here; it is not presented as a Google-certified advertising CMP. Before Google ads requiring consent are served in the EEA, UK, or Switzerland, QuickerConvert must implement a Google-certified CMP using the IAB Europe Transparency and Consent Framework. Legal review is required before treating this policy as final compliance certification.
Contact
For privacy or advertising questions, contact [email protected] or visit the contact page.