Privacy

This page describes exactly what DatumParser collects, why, and what it doesn't — written to match what the code actually does, not a generic template.

Your files

Uploaded Excel files and generated drawings are processed entirely in memory. They're never written to disk, never saved to a database, and never persist anywhere past the single request that processes them. Once your download is sent, nothing about your file's content remains.

Your download's filename is derived automatically from the name of the file you uploaded (so Tabla.xlsx produces Tabla.dxf) — you don't choose it, and the original filename itself is never stored anywhere beyond that.

What we do keep

Each time you use a conversion tool, we record a small usage entry:

• File size and how long the conversion took
• Number of sheets processed
• Whether it succeeded
• Your account (if you're signed in) — and your IP address at the time of the request, which is recorded either way, though it's only used to enforce the daily limit when you're not signed in

This is used for rate limiting (so the free daily limit works) and to understand how the tool is actually used. We never record your filename or anything from inside your file. These entries are currently kept indefinitely — we don't yet have an automatic deletion schedule, though that may change as the product matures.

If you sign in with Google

Signing in stores your Google account ID, email address, and display name, so we can recognize your account and apply your higher daily limit. We don't retain any Google access token beyond the sign-in process itself.

Where things run

DatumParser is hosted on Railway, which also hosts our database. Like most web hosts, Railway's infrastructure logs basic request information (like your IP address) as part of normal server operation — this is standard hosting behavior, governed by Railway's own policies, not something DatumParser adds on top.

Cookies

DatumParser uses a small number of cookies:

• A session cookie, if you sign in — this is what keeps you signed in as you move between pages. Necessary for the site to work if you're logged in; nothing works without it.
• Analytics cookies, from Google Analytics — used to understand general site usage (which pages get visited, roughly how). Not used to identify you personally.
• Tally's own cookies, only if you open the feedback form — governed by Tally's own practices, not ours.

We don't use cookies for advertising, and we don't sell data to advertisers.

Third-party tools we use

• Google Analytics — standard, anonymized-where-possible page-visit analytics (which pages are viewed, general location, browser type). It does not receive your filename or file content. Governed by Google's own privacy practices.
• Tally — powers our feedback form. If you submit feedback, whatever you enter is handled under Tally's own privacy policy, not stored in our own systems.

What we don't do

• We don't sell or share your data with advertisers.
• We don't run ads, and we don't build advertising profiles.
• We don't look inside your uploaded files for anything beyond the conversion itself.

Questions

If anything here is unclear, or you want a specific answer about your own data, reach out through our feedback form — a real person reads it.

This page reflects DatumParser's current, actual behavior — it will be updated as the product changes, not written once and forgotten.