Privacy
We count downloads and active suites so we know what people use. We do not track you, set no cookies for visitors and store no full IP addresses.
Last changed 19 October 2026.
Who is responsible
suitecraft.app and the SuiteCraft builds are published by [CONTROLLER]. Questions about privacy: [EMAIL].
In short
- No cookies for visitors, no tracking scripts, no advertising, and nothing loaded from other companies (fonts and images come from this site).
- We count which downloads are chosen and how many suites are in use. The counts can't be linked to a person.
- Full IP addresses are not stored. The web server's log keeps a shortened address only.
When you visit the website
Your browser sends the usual request information to our server. The web server writes a log line for each request with:
- a shortened IP address: the last part of an IPv4 address is set to 0 (for example 203.0.113.0), and an IPv6 address is cut to its first three groups;
- the time, the address of the page or file, the answer code and size;
- the browser's own description of itself (the "user agent").
We use the log to keep the site running and to find faults. It is kept in rotating files that are overwritten as they fill, usually within a few days. The server's error log only records serious server faults. To stop floods of requests, the server briefly keeps a count per full address in memory; this is never written down.
When you start a download
The page tells our counter what you chose: the whole suite, your own pick of apps or a customised suite, for which system, which apps, and the update choices you made in "Customise". It sends no identifier, and no cookie is involved. We also count how many zips are delivered per system.
When UpdateCraft checks for updates
UpdateCraft asks suitecraft.app for the latest suite version. With that request it sends:
- its own version number and the system it runs on;
- a random suite id: a number made on your computer when UpdateCraft first runs. It is not derived from your computer, your name or anything else.
We don't store the id itself. We keep a short fingerprint of it (the first 16 characters of its SHA-256 hash) for 35 days, and count how many different suites were active per day, week and month, per version and per system. A copied suite folder counts as one suite. We also count which app versions are downloaded.
We mainly use these numbers to judge how much server capacity we need, and to spot misuse of the server, such as an unusual number of requests.
To prevent misuse, the number of requests each suite id can make per minute is limited. For that, the id is held briefly in the server's memory, but never written down.
You can see the suite id, and switch sending it off, in UpdateCraft's settings. Updates still work without it, but requests are then limited more strictly per network address, so an update can take a little longer where many people share one address.
Why we may do this
We count downloads and active suites, and keep a short log, because we have a legitimate interest in running the service securely and knowing which builds are used (GDPR article 6(1)(f)). We collect as little as we can for that.
Sharing
We don't sell or share the data. The server is run by us; no analytics or advertising company receives anything.
Your rights
You have the right to access, correct and delete personal data about you, and to object to its use. Because we store nothing that identifies you, we usually can't find data about you. If you send us your suite id, we can remove its fingerprint from the counts. Write to [EMAIL].
If you think we handle personal data wrongly, you can complain to the Norwegian Data Protection Authority, Datatilsynet.
Settings in your browser
A few choices you make on this site (such as light or dark mode) are kept in your own browser. They are listed on the cookies and storage page.