How ORDODAY handles your files

When you add a file, your browser reads it into memory and converts it in a background thread (a Web Worker) inside the same tab.

Results are created in memory too. Downloading saves them from your browser to your disk; no copy is sent anywhere.

Closing or reloading the tab discards everything. ORDODAY keeps no history of your files.

Every ORDODAY page is served with a Content Security Policy that only allows network connections back to ORDODAY itself, and ORDODAY has no endpoint that accepts files for these tools.

The page requests its own code and supporting data, such as the font files used to render PDFs, and sends the aggregate usage events described below to ORDODAY itself. Document files and their contents are not sent.

To check: open your browser's developer tools, go to the Network tab, and run any tool. You'll see no request carrying your document.

ORDODAY is in public beta and records aggregate usage events to understand which tools are used and where work succeeds or fails: which page was opened, which tool was chosen, whether a conversion produced a result, and whether a download was initiated. These are event counts, not counts of people, and a download event does not confirm that a file was saved.

Each event can carry only coarse, predefined labels: page language, device type (phone, tablet or computer), the family of your operating system and browser (iOS, Android, macOS or Windows; Safari, Chrome, Edge or Firefox — never a version number or device model), file type (such as PDF or CSV), a size range (such as under 1 MB), a page-count range, a duration range, an error category or the reason a file could not be used (such as empty, password-protected or an unsupported format), the country estimated from the network, and where the visit came from (such as Google, or direct).

Page speed (Core Web Vitals): load and responsiveness timings, so slow pages can be fixed.

After you finish reading an invoice with Smart Extract, ORDODAY may show one optional question with printed options: how often you do this kind of work, roughly how many invoices that is in a month, and what most of them arrive as. It has no text box, it is never required, and it stops appearing once you answer or dismiss it.

Invoice Register records whether you start with samples or your own selected files, coarse file and exported-row ranges (1, 2-5, 6-20, 21-50), read outcomes, failure or cancellation steps, and XLSX/CSV download initiations. An export records only yes/no for whether any fields are blank or any rows carry warnings; no field names, field counts or values are sent. A separate local counter increases once per own-file batch that reaches its first download initiation, not for samples or each output format. Only its coarse repeat range is sent.

Your browser keeps a small counter of completed own-file Smart Extract runs in local storage on your device. The exact counter is never sent. ORDODAY sends only one of four ranges (first time, 2-3, 4-10, or 11 or more), with no identifier. These ranges describe repeated runs in a browser, not returning people. If your browser blocks storage or sends Global Privacy Control, these counters and the optional survey are not used.

Usage events contain no user ID or IP address. ORDODAY uses no tracking cookie or third-party tracking script. Events are sent to ORDODAY itself and stored in the analytics service of Cloudflare, ORDODAY's hosting provider, for about three months. Cloudflare receives network request metadata, including IP addresses, when it serves the website; that is separate from the product event data ORDODAY stores.

Client workspaces save only the names and export/mapping preferences you choose in IndexedDB in this browser. They do not save documents or extracted values, are never uploaded or sent as statistics, and remain available with Global Privacy Control. You can delete them or export/import a settings JSON backup. Clearing browser data removes these settings.

Saved PDF recipes also store only your chosen name, ordered steps and options in a separate IndexedDB database. JSON backups contain configuration only; document bytes and results are never persisted.

"Recently used" remembers up to six tool names (for example merge-pdf) in this browser's localStorage after a finished download, so you can find them again. It holds no file names or contents, is never sent anywhere, and can be cleared with its × button.

The only cookie ORDODAY sets is ordo-locale, which remembers the language you chose. If your browser sends a Global Privacy Control signal, ORDODAY sends no statistics at all.

File names, document content, text read from files, values read by Smart Extract, tax IDs, invoice numbers, company names, amounts, spreadsheet cell values, and file hashes.

The statistics endpoint accepts only predefined event names, labels and bounded performance measurements. Other properties and values are discarded in your browser and again on the server. Document contents and names are not accepted analytics properties.

The “helped / didn't help” buttons after a result record only which one you pressed. There is no text box.

You can use the tools without creating an account.

ORDODAY does not currently offer server processing of your documents. Any future feature that sends documents to a server would need a separate notice explaining what is sent, why, who processes it and how long it is kept, plus an explicit choice before any upload.