Skip to main content

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.

Last updated: July 30, 2026

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.
  • OCR may download public recognition-model files after it starts, while PDF pages and recognized text remain in the browser.
  • 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 (readiness)

Current ad-serving state

Advertising is not active on QuickerConvert today. The site does not load AdSense code or send advertising requests, and its current public-page privacy control covers optional analytics only.

No advertising cookie, local-storage entry, or ad request is sent by QuickerConvert while advertising is disabled. The current privacy control remains available for optional analytics and keeps future advertising consent separate.

Google and third-party advertising

If advertising is authorized later, Google and the ad partners selected in the publisher account may place or read cookies, use web beacons, or receive IP address, browser, device, page, and similar identifier information as a result of ad serving on public content pages.

Personalized, non-personalized, and limited ads

Personalized ads may use consented activity or interests to choose ads. Non-personalized ads use contextual information such as the current page or broad location, but may still use cookies or similar storage for purposes such as frequency capping, aggregated reporting, and fraud prevention where consent and law allow. Limited ads use more restricted data and storage where Google supports that mode.

Vendor choices and data use

The MetaRealms / QuickerConvert publisher-account owner must approve the AdSense ad-partner list. The consent message must identify the selected partners and link to information about their data use. No advertising-vendor list is active on this site while advertising remains disabled.

Consent modes

  • Analytics (implemented): Optional public-page analytics are controlled by the current privacy choice and remain off by default.
  • Advertising (disabled): Advertising consent is separate from analytics consent. No advertising choice or ad request is active until the selected CMP and ad architecture are configured and tested.

Selected CMP and responsibility

Google Privacy & messaging CMP is the selected consent platform. Google-provided, Google-certified CMP path selected. The MetaRealms / QuickerConvert publisher-account owner must configure and approve it before advertising is activated for visitors in:

  • EEA
  • UK
  • Switzerland

Required framework: IAB TCF v2.3. Use only the AdSense ad partners approved in the publisher account and disclosed by the CMP. Advertising remains disabled until that list is reviewed.

Advertising consent modes

  • Personalized ads only after the CMP records the consent signals required for that use.
  • Non-personalized ads only when the applicable consent and regional rules allow the storage and data uses involved.
  • Limited ads only where supported and configured; limited ads are not treated as a substitute for required consent.

How we test ad-readiness before launch

  • Open representative public pages from an EEA country, the UK, and Switzerland and confirm the certified CMP message appears before any advertising request or storage.
  • Test accept, reject, manage-options, and later withdrawal paths; confirm the stored TCF v2.3 consent state and resulting ad mode match the choice.
  • Inspect network requests, cookies, and local storage before a choice, after rejection, after acceptance, and after withdrawal.
  • Confirm active /app workflows never load the advertising CMP, AdSense requests, advertising cookies, or ad placements.
  • Repeat the checks on a desktop browser and a 390 by 844 phone viewport, including keyboard and screen-reader labels.

External activation checklist

  • Configure the selected Google Privacy & messaging CMP in the QuickerConvert AdSense account.
  • Approve and disclose the AdSense ad-partner list, purposes, and regional choices.
  • Keep ad code behind the disabled-by-default advertising feature gate from Task 15.
  • Complete the documented regional, network, storage, accessibility, desktop, and phone tests.
  • Obtain appropriate legal review before treating the production configuration as final compliance readiness.

Reference external controls

Learn how Google uses information from sites and apps that use its services at Google partner sites. Review personalized-ad controls at adssettings.google.com and broader opt-out tools at aboutads.info/choices.

Legal review is required before any consent-dependent advertising configuration is treated as final compliance readiness.

If ads are enabled, they belong only on public content and not beside upload, preview, edit, export, or download controls.

Contact

QuickerConvert is operated by MetaRealms. For privacy or advertising questions, contact [email protected] or visit the contact page.

Read the FAQ or browse PDF tools.