MepoCAD is architectural drafting software you install and run on your own computer. This page explains, plainly, what our website and the desktop app send back to our server, why, and for how long we keep it. If anything here is unclear, write to hi@mepocad.com.
Our web server (nginx) keeps an access log of requests to mepocad.com: timestamp, the page or file requested, the
HTTP status code, your browser's User-Agent string, the referring page, and a truncated network — the first three
octets of an IPv4 address (e.g. 203.0.113.0/24) or the first four groups of an IPv6 address
(e.g. 2001:db8::/64). Your full IP address is discarded before anything is written to disk; it is
never logged, even temporarily.
If the download link you used included a language code, the log also records which language you picked. Raw logs are kept for 35 days and then deleted automatically. A separate daily summary — counts of page views, downloads, and app version numbers per day, with no machine-level detail — is kept indefinitely so we can see trends over time; it cannot be used to identify a visitor.
The app generates one random identifier the first time it runs — 16 random hexadecimal characters, stored in
%APPDATA%\MepoCAD\ma-may.txt on your own computer. It is not derived from your hardware, your Windows
account, or your name, and there is no way for us to turn it back into who you are. Its only purpose is to let us
count how many distinct installations are in use, separate from how many times the app happened to check for
updates.
Each time the app starts, it asks mepocad.com whether a newer version is available, sending: the
current app version, your Windows architecture (e.g. windows-x86_64), and the identifier above. That
request is what appears as one line in our server log, with the same truncated network described above.
mepocad.com in your firewall — the app will simply fail to reach the server
and let you keep working on the version you have. We plan to add an in-app switch for this in a future release.
If the app crashes, it writes a small note to its own folder before closing. The next time you open the app, it
sends that note to mepocad.com/loi/<version>: the app version and the .NET exception type name
only — for example System.NullReferenceException. We never receive the error message, the stack
trace, a file path, or any drawing content; the server does not store the request body at all, only that a crash
report for that version arrived.
You can turn this off today by creating a text file at %APPDATA%\MepoCAD\quyen-rieng-tu.txt containing
the line bao-loi=0. There is no in-app switch for this yet either; we are aware that a text file is
not a friendly way to do it, and it is on our list to fix.
The aggregated statistics described above are visible on an internal dashboard restricted by a password only the project owner holds. Nobody else — no advertising network, no analytics company, no outside contractor — has access to our server logs or this dashboard.
If what we collect changes, we will update this page and its "last updated" date above. We do not expect to start collecting drawing content, file names, or full IP addresses — if that were ever proposed, it would need a separate, clearly-announced policy change, not a quiet edit here.
Questions, requests to be added to the local "internal machine" exclusion list (used only for our own development machines, never for excluding real customers), or anything else: hi@mepocad.com.