Privacy Policy
Last updated: 4 August 2026
Short version: the log analyser does not store your logs, we do not run analytics or advertising of any kind, the desktop application does its work on your own machine, and if you gave us your email you can delete it yourself with one click.
Who we are
ModTamer is provided by Arturo von Senger, an individual based in Chile. For any question about your data, write to contact@modtamer.com.
The free log analyser
When you paste a log on the home page, the text is sent to our server, analysed in memory, and discarded. It is never written to a database or to a file. We do not create an account for it, and we do not attach it to any customer record.
We will not claim more than that. Delivering the request at all means our hosting and network providers handle ordinary connection metadata — an address, a timestamp, a page — for as long as it takes to route and protect the traffic. That is true of every website, and saying otherwise would be the kind of absolute promise this page exists to avoid.
Crash logs frequently contain absolute paths that include your operating system username
(C:\Users\yourname\...). Before returning anything, we
replace those paths. We do this because the result is what you are likely to
copy into a public Discord to ask for help, and your username is not a cost you should pay
for using the tool.
The waiting list
If you give us your email address to be told when ModTamer launches, we store:
- the address itself, in lowercase;
- the date you signed up;
- which page you signed up from;
- a random token that makes your removal link work.
That is the whole record. We use it for one message, when the product launches. No newsletter. We do not sell or rent it, and we do not hand it to anyone to advertise to you. It sits in our own database, on the server listed further down.
Every message we send carries a link that removes you, with no account and no password. That link also offers full deletion — not just "stop writing to me", but "delete the address entirely". They are different requests and we treat them as different. You can also just email us.
The desktop application
ModTamer is local-first by design. Reading your mods, building the dependency graph, booting test servers, isolating the mod that breaks a pack and measuring performance all happen on your own computer. There is no upload step, and no copy of your server on our side.
It does reach the network, though — a tool that builds a working test server has to fetch the pieces that server is made of. This is where it connects and why:
| Where | What for |
|---|---|
| modtamer.com | Asking which version is current, so we can tell you yours is old. It sends nothing about you or your servers. |
| Modrinth | Looking up mods and downloading the files you accept in a repair or an update. |
| Mojang | The public version manifest, to know which Java version a given Minecraft version needs. |
| Adoptium | Downloading that Java runtime, so you do not have to install one by hand. |
| Forge / NeoForge | The installer for the loader your pack uses. |
| spark.lucko.me | Only if you turn on per-mod profiling. See below. |
Everything on that list is a download, except the last one. Your mod list, your world, your configuration files and your logs are not uploaded anywhere.
The one thing that does get uploaded
Measuring what each individual mod costs uses spark, a profiler that runs inside the test server. When spark stops, it uploads its measurements to its author's own service to make them readable — in this version there is no way to read them locally. So that feature, and only that feature, sends data out.
What goes up is a performance sample of the disposable copy ModTamer built and drove itself: which code ran and for how long. Not your world, not your player data, not your identity. It is off unless you switch it on — the application refuses to run it without an explicit acceptance, and that refusal is a check in the code, not a habit.
If usage telemetry ever exists, it will be opt-in on the same terms and clearly described. It will not be switched on quietly in an update.
What we do not do
- No advertising, and no advertising identifiers.
- No analytics or tracking scripts. Not ours, and not anybody else's.
- No cookies for tracking. The site works without setting any.
- No selling or renting of personal data, and no disclosing it for advertising or profiling.
- No profiling and no automated decisions about you.
What we cannot honestly say is "nobody else ever touches it". Running a service means other companies are involved — and they are not involved in the same way, so listing them in one block would be its own kind of inaccuracy. There are three kinds:
- Companies that run our infrastructure. They handle data on our instructions and for no purpose of their own.
- Paddle, once we are selling. Not a contractor of ours: as merchant of record it is the seller, and it decides on its own account what it does with your purchase data, under its own privacy policy and its own legal duties.
- Services the desktop application connects to — Modrinth, Mojang, Adoptium, Forge, NeoForge, spark. These are nobody's contractors. They are independent projects your copy of ModTamer talks to, on your machine, the same way your browser talks to a website. We do not send them anything about you.
This is enforced in code, not just promised here: the site declares a content security policy that forbids loading any script from another host, and asks intermediaries not to modify our pages. When our own CDN tried to inject an analytics script, the policy blocked it and we removed it.
Server logs
Our web server keeps ordinary access logs to diagnose faults. Visitor IP addresses are truncated before being written — the last part of the address is thrown away, so what is stored points at a network, not a person. That is a line of configuration on the server, not a policy we remember to follow.
Who else touches the data
| Who | What they get | Where |
|---|---|---|
| Hostinger | Runs the machine holding the site, the database and the truncated logs | United States |
| Cloudflare | DNS and traffic delivery. Being in front of us, it necessarily sees the full connection — address, time, page — before we do | Global network |
| Paddle | Payments, once ModTamer is on sale. Takes your payment details; passes us the purchase, never the card. Acts on its own account, not on our instructions | Global |
| spark | Only if you switch on per-mod profiling. Receives the performance sample of the disposable test copy, so it can be read back. Run by the author of spark, under their terms, not ours | Their own service |
spark is on this table and also further up, in the list of places the application connects to. That is deliberate: it is the only one that appears in both, because it is the only one that receives something instead of just handing something over.
Because the server is in the United States, data from the waiting list is stored there.
What Paddle will pass back to us
Being merchant of record means Paddle is the seller and handles the card — but it does send us what we need to actually give you the product and support it. When paid plans start, that may include: your name, the email you bought with, your country, a billing address where one is given, which plan you bought, Paddle's own customer and transaction identifiers, your purchase history with us, and the status of the subscription (renewed, cancelled, refunded, charged back).
"May include" is doing real work in that sentence, and we would rather explain it than let it pass. Three different things are available to us through Paddle, we receive a smaller set by webhook, and we store a smaller set still. When the account system exists, this page will say which fields we keep and for how long — that is a promise about code that is not written yet, so it gets made when the code is.
We never see or store your card number. That part is true and stays true. But "Paddle handles payment" does not mean no purchase data reaches us, and this page should not have implied it did.
How long we keep things
- Logs you paste: not kept at all.
- Waiting list: until you remove yourself, or until the launch message has been sent and the list is no longer needed.
- Access logs: 30 days, already truncated when written. Not "a short period" — thirty days, set in the server's configuration, so the number is checkable rather than reassuring.
Accounts, licences and purchase records will need their own periods. They are not listed here because that system does not exist yet, and inventing a retention period for it would be describing a decision nobody has made. They go on this page when they are built, before anyone can buy.
Your rights
You can ask to access, correct, delete or export your data, or object to its use. Write to contact@modtamer.com and we will answer. For the waiting list you do not have to ask anybody — the link in the email does it immediately.
Depending on where you live you may also have the right to complain to a data protection authority.
Age
Let us be realistic about this: it is a Minecraft tool, and plenty of people who run modded servers are teenagers. So rather than declare that children are not here, we say what actually applies.
Buying a plan is a contract, and that requires being 18 or the age of majority where you live — see the terms. A younger person can use ModTamer with a parent or guardian's permission and under their supervision, with the adult holding the purchase. We do not knowingly collect personal data from a child where the law requires a parent's consent and we do not have it; if you believe we have, write to contact@modtamer.com and we will delete it.
Changes
If this policy changes we will update the date at the top. If a change actually affects what we do with your data — rather than just wording — and we have your email, we will tell you.