The Giant Tiny App Factory
Privacy & cookies
Updated 11 October 2026. This policy covers Giant Tiny PDF, QR, Text, Images, Audio, HEIC, OCR, Background, Video and Subtitles, browser tools from The Giant Tiny App Factory.
Your files and text
The workbenches process the files or text you choose in browser memory. Selected files, names, document previews, pasted text, website addresses and Wi-Fi details are not uploaded or passed to the surrounding advertising page. Original files stay unchanged. Downloads are saved where you choose.
PDF uses self-hosted PDF libraries and workers to prepare pages and previews. QR creates static codes locally. Text counts and transforms your input locally. Images uses browser image decoding and canvas; Audio uses browser audio decoding and a self-hosted MP3 encoder. HEIC uses a local image codec. OCR and Background download self-hosted recognition or segmentation models when requested. Video uses a local video codec, and Subtitles converts timed text locally. Library, codec and model assets can be large; their download is described before processing.
The utilities do not save your content to an account or browser database. Reloading or closing the workbench clears its session; local downloaded files remain. Text Reset can be undone while its bounded session history is retained. They do not request camera, microphone, location or cloud-storage access.
QR codes contain their information
A QR code encodes the information you enter, including a Wi-Fi password if supplied. Anyone with the exported code can read those details. We do not operate redirect links or track scans. Opening a website QR contacts its destination, whose own privacy policy applies.
Website requests
Your browser requests these websites and their static assets from the hosting provider. The provider receives ordinary request information, including IP address, browser details and requested URLs, and may retain server logs. These requests do not contain the content you process. No analytics service has been added.
Google consent and advertising
Google consent messaging is connected on the public tool pages. Display-ad requests are disabled while site approval and consent behavior are being verified. This privacy page and the isolated processing workbenches load no Google advertising script.
When enabled, third-party vendors including Google and participating ad networks may use cookies and similar technologies to select ads based on prior visits to these sites or other websites, subject to applicable consent choices. Google services can receive ordinary web and device information. They run on the surrounding public page, on a different origin from the processor; the app sends only a layout-height message between those pages.
Where the consent message is available, use its choices or the public tool page’s Privacy choices control to review or change them. Declining consent does not block the tools. The message lists participating vendors and their privacy information.
You may manage personalized Google ads in Google Ads Settings, or use participating vendors’ own opt-out controls and Digital Advertising Alliance choices. Opting out of personalization does not necessarily remove ads. Read how Google uses information from partner sites.
Processing boundaries
Advertising belongs to the public tool subdomain pages, including images, audio, pdf, qr, text, heic, ocr, background, video and subtitles. The processors run at the root domain’s corresponding workbench paths, with restrictive browser policies and no advertising scripts. There is no remote conversion service or URL file import.