Legal
Privacy Policy
CADcompiler is a desktop program that nests your parts on your own computer. Your drawings never leave it. This page sets out the small amount of data that does travel, why it has to, and how to get rid of it.
1. Who is responsible
The data controller for the processing described here is Fabrentis, Istanbul, Türkiye (“we”, “us”). You can reach us at any time at info@cadcompiler.com, and we answer from that address.
This policy covers both the CADcompiler desktop application and the website at cadcompiler.com, including the customer account area.
2. What the desktop application sends
The application contacts our licence server on exactly four occasions. Nothing else in it reaches the network.
2.1 When you activate a licence
| Data | Why |
|---|---|
| Licence key | To identify which licence you are activating. We store only a one-way hash of it, never the key itself, unless the key was issued through our admin panel — those are held encrypted so we can resend a key you have lost. |
| Machine identifier | A 64-character hash derived from your computer’s hardware signals. It is what lets one licence run on the agreed number of computers and no more. |
| Hardware signals | Motherboard UUID, BIOS serial, processor ID, disk serial, network adapter address, Windows installation GUID, volume serial, host name. Every one of these is hashed on your computer before it is sent. We receive fingerprints, not serial numbers, and cannot reverse them into an inventory of your hardware. |
| Computer name and Windows version | Sent in readable form, and only so that the device list in your account says “OFFICE-PC / Windows 11” instead of a row of hex. This is the one identifier here you may recognise as yours. |
| Application version | Support, and knowing which versions are still in use before we change something. |
2.2 When it re-checks the licence
Once at start-up, in the background: the machine identifier, the hardware signal hashes and the application version. No licence key is sent — the server recognises the computer without one. This is also what restores your licence after a reinstall, so you do not have to find your key again.
2.3 When you release a computer
The machine identifier and the signed licence file, so the server can verify the request came from that computer and free the slot.
2.4 The presence signal
While the application is open it sends a small signal roughly every thirteen minutes so that we can see how many installations are in active use. A signal is 62 bytes and contains an activation number and a token — nothing else. It carries no licence key and no machine identifier. The version and Windows version ride along only on the rare occasion that one of them has changed.
It counts installations, not people and not activity. There is no idle detection, no feature tracking, no count of jobs, and no timer on anything you do.
3. What the application never sends
This list is not an intention; it is a property of the program, and the four requests above are its whole network surface:
- your DXF drawings, or anything derived from their geometry;
- your Excel bill of materials, its contents, or your part numbers;
- file names, folder names or file paths;
- how often you run it, what settings you use, or how long jobs take;
- screenshots, crash dumps or usage analytics of any kind.
The application keeps a diagnostic log on your own computer
(%APPDATA%\CADcompiler\cadcompiler.log). It never leaves
your machine unless you choose to send it to us with a support
request, and it is written so that your licence key is never in it.
4. What the website collects
| Where | What | Why |
|---|---|---|
| Account registration | E-mail address, password (stored only as a hash), optionally your name and company | To create and secure your account and to attach your licences to it |
| Contact form | Name, e-mail address, your message | To answer you |
| Sign-in and activation | IP address, time and outcome of the attempt | Rate limiting. Without it, a licence key can be guessed at machine speed |
| Your devices | The activation records described in section 2 | So you can see and remove your own computers |
| Web server | Standard access logs kept by our hosting provider | Operating and securing the site |
5. Cookies and analytics
Session cookie. Signing in sets one cookie that keeps you signed in. It is strictly necessary, holds no personal data of its own, and expires when you sign out.
Google Tag Manager and analytics. The public pages load Google Tag Manager, which may set analytics cookies to measure how the site is used. This tells us which pages people read; it is not connected to your licence, your account or the desktop application. You can block it with your browser’s cookie settings or an extension, and the site works normally without it.
The desktop application sets no cookies and contains no analytics or advertising component.
6. Why we are allowed to process this
- Performance of a contract. Licence activation, the re-checks, the device list and your account exist to deliver the software you bought. They cannot be switched off and still leave a working product.
- Legitimate interests. Rate limiting and the hashed hardware fingerprint protect against licence abuse; the presence signal tells us how many installations are actually in use. In each case we chose the least revealing method that works — which is why the hardware signals are hashed and why the presence signal carries neither your key nor your machine identifier.
- Consent. Analytics cookies, and any e-mail you ask us to send you that is not about your licence.
- Legal obligation. Records we are required to keep, such as those relating to invoices.
7. How long it is kept
| Data | Kept |
|---|---|
| Account and licence records | While your account exists. Deleting it removes the personal data; see section 9 |
| Activation records | Until you remove the device, or the licence ends |
| Presence signals | Aggregated into per-period counts. Individual signals are not stored as an event history |
| Sign-in and activation attempts | Cleared automatically once they are past the rate-limit window |
| Contact messages | 24 months from your last message, then deleted |
| Invoices and payment records | For as long as tax and commercial law requires us to keep them — under the Turkish Commercial Code that is ten years. This is the one thing we cannot delete on request, and it is why section 9 says what it says |
8. Who else sees it
We do not sell personal data and we do not share it for advertising. It reaches only:
- Our hosting provider, which operates the servers this site and the licence API run on.
- Google, for the website analytics described in section 5.
- Microsoft, if you install CADcompiler from the Microsoft Store. Microsoft handles that transaction under its own privacy statement, and we receive no personal data from it beyond what you send us by activating.
- Authorities, where the law requires it.
9. Your rights
Under the GDPR and, in Türkiye, under KVKK (Law no. 6698) you may ask us to confirm what we hold about you, to correct it, to delete it, to restrict or object to its processing, and to provide it in a portable form. Where processing rests on consent, you can withdraw that consent at any time without affecting what was done before.
Two of these you can exercise yourself, immediately, without asking anyone: your device list at cadcompiler.com/account lets you remove a computer, and the application’s Settings › Licence › Release this computer button deletes the licence from that machine and frees its slot in one step.
For anything else, write to info@cadcompiler.com. We answer within 30 days. If you are not satisfied, you may complain to your local data protection authority.
One limit, stated plainly. A deletion request does not reach records we are legally required to keep — principally invoices and the accounting entries behind them (section 7). We will delete everything else and tell you exactly what had to stay.
10. Security
- All traffic between the application, the website and our servers is encrypted with HTTPS, and the licence API refuses to answer over plain HTTP.
- Passwords are stored as hashes and cannot be read back, by us or by anyone who obtained the database.
- Licence keys are stored as hashes. The exception is keys issued through our admin panel, held encrypted so that we can resend one you have lost.
- Hardware signals are hashed on your computer before transmission, so a breach of our database would not expose anyone’s hardware inventory.
- Licences are signed with a private key that never leaves the server; the application holds only the public half, which can verify a licence but cannot create one.
11. Children
CADcompiler is professional engineering software. It is not directed at children, and we do not knowingly collect data from anyone under 16.
12. Changes to this policy
If what we collect changes, this page changes with it and the date at the top moves. Changes that materially affect you will also be sent to the e-mail address on your account.
13. Contact
Fabrentis — Istanbul, Türkiye
info@cadcompiler.com