Privacy
Privacy: what happens to a loss run you upload
A loss run names the people who made claims, and its descriptions can include injuries. This page says plainly what LossRun Pro does with the file, what it does not do, and who else touches it. Last updated October 28, 2026.
In short
What this policy says in four lines
Files are processed in memory and deleted after conversion; files are not retained. Claimant masking is not applied, so names appear in your schedule as the carrier printed them. Uploads are not used to train models. A page that needs a second look may be sent to Google's Gemini API, which can keep it for up to 55 days under Google's terms.
Steps
What happens to a file, step by step
From the moment you choose a file until the schedule is on your screen.
- You choose a fileYour browser sends it over HTTPS to this site's conversion function, along with a random device identifier that it keeps in local storage and, if you have entered one, your page code.
- The function relays itIt passes the file to the conversion service, which runs on Modal, with the device identifier, the page code if there is one, and your IP address so the free allowance and the pages left on a code can be counted.
- The service reads it in memoryThe text and tables are extracted. Pages that need a second look, such as a scan, may be sent to Google's Gemini API.
- The text comes back and becomes a scheduleThe function maps the columns, builds the claims schedule and the tie-out, and returns them to your browser. It does not store the file or the result.
- The file is deletedAfter conversion the file is deleted. The schedule stays on your screen until you download it, start over or close the page.
What we handle
What is collected, and why
| Item | What happens to it | Why |
|---|---|---|
| The loss run you upload | Read in memory, then deleted after conversion. Not retained. | To build your claims schedule. |
| Claimant names and claim details in the file | Not masked. They appear in the schedule exactly as printed. | They are part of the loss run, and the schedule needs them. |
| A random device identifier | Kept in your browser's local storage and sent with each upload. | So the conversion service can count the free allowance for your device. It is not linked to your name. |
| A page code, if you enter one | Kept in your browser's local storage and sent with each upload. You can remove it from the page at any time. | So the conversion service can check the code and count the pages left on it. |
| Your IP address | Passed to the conversion service with each upload. Cloudflare, as host, also sees it. | To count the free allowance fairly, and to keep the service running. |
| Cookies | None are set by this site. | Not applicable. |
| Analytics | No analytics script is running on this site. | To see which pages are read, not who reads them. |
| Payment details | Handled by the payment provider. This site does not receive or store card numbers. | To take payment for Pro and Agency. |
| Emails you send us | Kept as long as needed to answer you and to keep a record of billing questions. | To reply and to resolve problems. |
Sub-processors
Who else handles your file
These are the services LossRun Pro uses to run. None of them is given your file for any purpose other than producing your schedule.
| Provider | Role | What it does here |
|---|---|---|
| Modal | Compute | Runs the conversion service that reads your file and returns its text. |
| Vision check | Pages that need a second look may be sent to Google's Gemini API. Google can keep them for up to 55 days under its terms. | |
| Cloudflare | Hosting | Serves this site and runs the function that relays your file and builds the schedule. |
| Payment provider | Payments | To be named here when online checkout is switched on. Until then, subscriptions are handled by email. |
Claimant names
No masking is applied
LossRun Pro does not remove or mask claimant names, claim descriptions or any other text on a loss run. The schedule you download has them as the carrier printed them, and so does the file the conversion service reads. If a client agreement or a privacy duty of your own means names must not reach a third-party processor, redact the PDF before you upload it, or do not use the service for that file. Redacting names is a different act from changing amounts or dates, which the terms forbid.
Comparison
Where your claim data goes: re-keying, a generic converter, or LossRun Pro
Every route to a spreadsheet puts the claim data somewhere. These are the differences that matter for a privacy review.
| What you need | Manual re-keying | Generic PDF-to-Excel | LossRun Pro |
|---|---|---|---|
| Who sees the claimant names | You, and whoever types the data in. | The tool's operator and its processors. Varies by tool. | Names are not masked. The conversion service reads the file in memory and, for some pages, Google's Gemini API does. |
| How long the file is kept | Wherever you save it. | Varies by tool. Read each tool's policy. | Deleted after conversion and not retained. Google can keep pages sent to Gemini for up to 55 days under its terms. |
| Training on your files | Not applicable. | Varies by tool. Check before you upload. | No. |
| Account or sign-up | Not applicable. | Varies by tool. | None for the free allowance. |
| Masking of names | Up to you. | Varies by tool. | Not applied. |
FAQ
Questions about privacy and your loss runs
Do you keep my loss run?
No. The file is processed in memory and deleted after conversion, and files are not retained. The claims schedule exists in your browser until you download it or close the page. One exception sits outside our control: a page sent to Google's Gemini API for a second look may be kept by Google for up to 55 days under Google's terms.
Are claimant names masked?
No. Masking is not applied. A loss run names the claimants, and the schedule shows the names as printed. If your agreements or your own privacy duties require names to be removed before a file goes to a third party, redact the PDF before you upload it or do not use the service for that file.
Is my loss run used to train AI models?
No. Uploads are not used to train models. The file is read to produce your schedule and for nothing else.
Does my loss run go to Google?
Only pages that need a second look, for example a scan the reader cannot resolve, may be sent to Google's Gemini API for a vision check. Google can keep what it receives for up to 55 days under its terms, so do not upload a file you are not willing to have handled that way.
Who are your sub-processors?
Modal (compute), Google (vision check), Cloudflare (hosting) and a payment provider, which will be named on this page when online checkout is switched on. The table above says what each one does.
What do you store in my browser?
Up to two values in local storage. One is a random device identifier, used to count the free allowance. The other, only if you enter one, is your page code, which is sent with each upload so the conversion service can count the pages left on it. Neither is your name, your email or anything from your files. Clearing your browser data removes both, the Remove link next to the page code field removes the code, and the site makes a new device identifier when it needs one. This site sets no cookies.
Do you sell or share uploaded data?
No. Uploaded data is not sold and is not shared for advertising. It is passed only to the sub-processors listed above, to produce your schedule.
Is it appropriate to upload a loss run with injury details?
Workers' compensation and liability loss runs can describe injuries, and that is sensitive. The service handles them like any other loss run: in memory, deleted after conversion, not masked. Whether you may send them to a third-party processor depends on your agreements and the law that applies to you. This page is not legal advice, so check before you upload.
Is what I type into the request letter form sent anywhere?
No. The letter form and the summary template are built in your browser. Nothing you type there is sent to a server.
How do I ask a question or raise a concern?
Write to [email protected]. Because uploaded files are not retained, there is no file we can look up or delete on request. For billing questions use [email protected].