Files you process here
Twenty-four of the twenty-six tools on this site run entirely in the browser. A selected local file is read into memory in the browser tab with FileReader, worked on by JavaScript and WebAssembly running on your own device, and handed back as a blob URL that exists only until the tab closes. No request is made. You can verify this yourself: open your browser’s network panel and use any of them.
There is no upload, so there is no retention period, no storage bucket and no deletion request to file. There is nothing to delete because nothing was ever received.
Network-assisted tools
PDF to Word needs a full office-document engine to reconstruct an editable file, and that cannot run in a browser tab. When you use it, and only when you use it, the file is sent over TLS to a converter that runs pdf2docx in an isolated process with no persistent storage attached. The .docx is streamed straight back to you and the source file is deleted when that process exits — seconds after the response is sent.
HTML to PDF sends the public webpage URL—not a file from your device—to a guarded reader endpoint. It accepts public HTTP and HTTPS addresses, blocks local and private networks, removes executable page content, and returns readable text for PDF layout. It does not sign into websites or retain a browsing history.
Uploaded converter files are not written to a database, copied to a backup or used to train anything. Their names and contents are not logged. The tool page says all of this before the file picker opens rather than in a policy you have to go looking for. If it is not acceptable for a particular document, the merge, split and compress tools do the same class of work without touching the network.
Text and numbers you type
Nothing typed into a calculator or a text tool is transmitted, stored in a cookie, written to local storage or included in an analytics event. Loan amounts, invoice figures, draft copy and the contents of a QR code all exist in the page while the page is open and go when you close it.
Nearby file sharing
Share Files connects to a WebSocket signaling service while its page is open. The service sees the network address required for the connection, a random device name, a broad device type and the browser name. It uses a keyed hash of the network address to introduce nearby browsers, keeps that information only in memory and removes it when the socket disconnects. The signaling service relays WebRTC connection descriptions but does not receive file names, file metadata or file contents.
After the receiver accepts, file contents travel directly between the two browsers through an encrypted WebRTC Data Channel. No TURN relay or cloud-storage fallback is configured. The chosen display name is stored locally under ott-share-name; it can be changed from the sharing page and disappears when site data is cleared.
What is stored on your device
Your theme choice is saved under ott-theme so the site does not flash the wrong colours on your next visit. If you open Share Files, its random editable device name is saved underott-share-name. There is no account or cross-site identifier. Clearing site data removes both values and nothing else is affected.
The background-removal tool caches its segmentation model in the browser’s HTTP cache after your first run where the browser chooses to keep it, so a later run may not re-download it. That is a cached file, not data about you.
Analytics
Google Analytics 4 records page views and four events: that a tool was started, that it completed, that it errored and what type of error, and that an ad slot came into view. None of those events carries a filename, a file’s contents, a calculator amount or any text you typed. The completion rate per tool is the only number worth having, and it needs none of that. Google Search Console receives no user data at all — it reports on queries that reached the site.
Advertising
This site is free and paid for by advertising. Ad slots are served by a third-party network which may set cookies and use them for ad measurement and personalisation under its own policy, over which we have no control. Ads appear only below the tool interface and inside the article, never above the tool and never inside the interactive area. There is no interstitial, no cookie wall over the tool and no app-install overlay.
Contact
The site is maintained by Bindu S. M.; the about page says who that is and how to get in touch. If something here is unclear or turns out to be wrong, that is worth telling us about, and the page will be corrected rather than reworded.