Privacy Policy
Last updated: 6 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.
What it keeps on your computer
Signing in leaves three small files in ModTamer's own folder on your machine: the signed permit that says which plan you have, your licence key so tomorrow's renewal does not ask you to type it again, and the email address you signed in with — kept only so the app can tell you which account you are using.
None of the three is sent anywhere. Signing out deletes all three, and so does deleting your account from inside the app.
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 | Identifying your mods, and downloading the files you accept in a repair or an update. Identifying one sends a fingerprint of the file — see below. |
| 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. |
The rest of that list is downloads, with one exception on each end. Identifying a mod on Modrinth works by sending the fingerprint (a SHA-1) of the file, because that is the only way to know exactly which mod a jar is instead of guessing from its name. Done across a folder, that tells Modrinth which mods you have — and it reveals your IP address, the same way opening their website would. What is never uploaded is the content: your world, your configuration files and your logs stay on your machine.
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. That sample names things — the mods in the pack and the classes inside them — and the upload reveals your IP address to spark's service. What it does not carry is your world, your player data, or your identity as a ModTamer customer. 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. If you tick Keep me signed in on the account page, your browser stores your licence key so you do not have to ask for a code every time. It stays on your computer, it is never sent anywhere we would not have sent it anyway, and Sign out deletes it.
- 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. Hosting, traffic delivery and the one email we send. 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 tell them who you are — no account, no name, no licence key. What they do see is what any website sees when you visit it: your IP address, plus whatever the request itself has to carry (for Modrinth, the fingerprint of the file you are identifying).
This is enforced in code, not just promised here: the site declares a content security policy naming every host a page is allowed to load anything from, 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.
That list has exactly one entry: Paddle, and only for its checkout. We cannot take a payment without loading their script — the alternative is handling your card details ourselves, which is the thing we are paying them to do instead. Everything else is still refused, including analytics, fonts and anything a network in between might try to inject.
Their script does not load until you click to subscribe. If you read this site and never start a purchase, your browser never contacts Paddle at all.
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 |
| Resend | Sends the mail we have to send you: the confirmation link and code, your licence key, the message confirming a purchase, and — if you joined the waiting list — the one launch announcement. Sees the address and what the message says | United States |
| 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. Three different things are available through Paddle: what Paddle holds, the smaller set received by webhook, and the smaller set still that is stored.
Your account, field by field
The account system now exists, so this section says exactly what a row about you contains. It is written from the database schema, and a test compares the two — if a column is added and this table is not updated, the build fails.
| What | Why it is there |
|---|---|
| Your email address | It is your account. Nothing else identifies you to us. |
| When the account was created, and when the email was confirmed | An unconfirmed address cannot get a licence, so we have to know which is which. |
| A confirmation token and a six-digit code, with when they were sent and how many times the code was got wrong | They expire in 24 hours and are erased the moment they are used. The counter is what stops someone guessing a six-digit code. |
| Whether you have used your free run, and whether you have had a refund or a chargeback — each as a single date | They are once per person. Without them, "one free run" and "fourteen days, no questions" would be promises that reset with every new install. |
| Your licence: its key, the plan, whether it is active, and the identifiers Paddle uses for your customer record and subscription | It is what the application checks to know what you paid for. |
| The date of your next payment, and the date your subscription ends if you have cancelled | So your account can tell you when you will be charged, instead of sending you to look for the receipt. Both come from what Paddle tells us; we do not calculate them. |
| A pending plan and the date you asked for it, when you have asked to move down a plan | Moving down starts at your next payment, because the period you are in is already paid at the higher price. Until then we have to remember two things: what you have, and what you asked for. |
| The computers using it: a random identifier per installation, an optional name you choose, the dates it was activated and released, and the last date each one checked in | Plans cover a number of computers. The identifier is a random number generated on first run, not a fingerprint of your hardware. No disk, motherboard or BIOS serials are collected. The last check-in is not extra tracking: your copy already asks us to renew its permit about once a day, and we now write down when it last did. It tells us how many people are actually using ModTamer, and it tells you which of your computers is the one you stopped using. |
| The raw body of each billing message Paddle sends us | Kept whole because the day a payment has to be reconciled with Paddle, a summary is not enough. |
There is no password and no username. There is nothing to steal from us that would open your account elsewhere, and we do not ask for a display name because there is nowhere in ModTamer it would appear.
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.
- Confirmation links and codes: 24 hours, and erased the moment they are used — whichever comes first.
- Your account and licence: for as long as you have an account. Delete it and it goes, along with your licence and the list of your computers.
- Billing messages from Paddle: 12 months. Long enough to settle a disagreement about a payment. Longer only while a payment dispute is still open, or where the law requires it.
Deleting your account
There is a button. It is at the bottom of Your account inside ModTamer, and it deletes your email address, your licence and the list of your computers. We send a six-digit code to your address first — deleting has to require what creating required, which is control of the mailbox, and not merely sitting at an unlocked computer.
The licence goes with the account and cannot be passed to anyone. That is the normal rule for subscription software and it is there so that deleting is not a way to resell.
If you have a paid subscription, cancel it in Paddle first. We will refuse to delete until you have, and the reason is in your favour: deleting here does not cancel anything there. You would still be charged, with no account left to complain from.
One thing survives, and this is the honest version of it. Three dates — whether you used your free run, whether you took the fourteen-day refund, and whether there was a chargeback — are copied to a separate record, along with the date of deletion, and kept under a fingerprint of your address rather than the address itself. Otherwise "one free run" and "fourteen days, no questions asked" would reset every time somebody deleted and signed up again, and a promise that resets is not a promise.
That fingerprint is pseudonymisation, not anonymity. It is an HMAC-SHA-256, which means a secret key is mixed in, and that key is not kept in the database. It matters which way round that protects you: this record is about people who deleted, so their address is no longer written down anywhere. With a plain hash, anyone holding a copy of the database and a list of addresses to guess could work out which of them had deleted, offline and at their leisure. With the key held separately they cannot.
This page previously said the opposite, and the reasoning was wrong in a way worth naming: it argued a key would protect little because whoever held the file would also hold everyone's address in plain text. That is true of the table of people who are still here, and this one is about the people who left. What the record can answer is "has this address already spent its free run?". What it cannot do is produce a list of addresses to write to.
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. Two of these you do not have to ask anybody for: the waiting list has a removal link in its own email, and deleting your account is a button in the application.
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.