Privacy — MSP Zero

Reading the site

Analytics. Page views are measured with Matomo, which we run ourselves at analytics.agit8or.net. For each page view it receives the page address, the referring page, your screen size, your browser’s user agent and your IP address, which it uses to estimate an approximate location. It is configured not to set cookies. Since 11 October 2026 the IP address is stored with its last two bytes removed, so 203.0.113.45 is kept as 203.0.0.0; the location is estimated before that happens. Visits recorded before that date still hold the full address, and raw visit data is not deleted automatically.

The page address sent to Matomo is trimmed first: only the path, plus the topic and project on the contact form and any campaign label (utm_ or mtm_) in a link we published, each shortened and anything containing an @ dropped. While a page is in front, Matomo is also told every 15 seconds that it is still open, so time on page means reading time. Visits are not recorded from browser automation, from page-speed testers, or from any address but mspzero.com.

Opting out. Open any page with ?mz_notrack=1 on the end of its address and this browser stops sending analytics to us. That choice is kept in your browser’s local storage under mz-notrack, the only thing this site keeps there; ?mz_notrack=0 removes it.

Server logs. The web server records each request in an access log: your IP address, the time, the page requested, the status code, the referrer and the user agent. It is used to diagnose faults. It is not currently rotated or deleted on a schedule.

Browsing the site sets no cookies. There is no advertising, no tag manager and no embedded social media content. The MSP Zero tools contain no analytics. Several ask GitHub whether a newer release exists, and Depl0y asks deploy.agit8or.net, our own server, when GitHub does not answer; that request is not tied to this site and we do not count it. A click to a repository or an install guide is all this site sees, and it is never counted as an installation.

Cookies

One, and only when you open a form — the contact form, or the rating or suggestion form. A session cookie named mz_form, which holds a random session identifier and nothing else. On the server, that session holds one security token that shows a submission came from this site’s form. What you type is not stored in the cookie or the session: if a submission cannot be accepted, the page is sent back with your text still in the form.

The cookie is marked HttpOnly, is sent over HTTPS only, and is deleted when you close your browser. The server-side session file is deleted after a day.

Using the contact form

The form collects what you type into it:

Your name and email address, both required.
Your company and phone number, if you give them.
What the enquiry is about, and optionally which project.
Your message.

When you submit it:

It is checked for spam The form carries a signed, single-use token that expires, a hidden field that people never fill in, and a short arithmetic question. Your browser also solves a small computational puzzle, ALTCHA. It is open source and runs entirely from this server: the puzzle comes from this site, your browser solves it with a script also served from this site, and the answer is checked here. Nothing is sent to ALTCHA or to anyone else, and the puzzle contains no personal data. The answer can be used once, and it expires after 20 minutes. Because the puzzle needs JavaScript, the forms cannot be sent with JavaScript switched off; email is the way in then. A few other signals, such as a long message submitted within seconds, are weighed together. No third-party anti-spam service is used. Submissions, and requests for a new puzzle, are also rate-limited by IP address, and submissions by email address too.
It is saved on this server A copy of the submission is written to a file outside the public web directory before delivery is attempted, so a network failure does not lose it and a retry does not file it twice.
It becomes a support ticket The submission is sent over HTTPS to MSP Reboot’s support system at cp.mspreboot.com, which opens a ticket with your name, email, company, phone, subject, project and message. MSP Reboot staff read and reply to it there.
You are told what happened The page only says your message was filed once the support system confirms the ticket exists. If that confirmation does not arrive, the page says so, and the saved copy is delivered later.

The ticket does not include your IP address, your browser’s user agent or the page you came from.

Rating the site and suggesting improvements

The “Rate this site” and “Suggest an improvement” forms collect what you choose to give: a rating from one to five and, optionally, what was helpful, what could be better and your role; or a category, optionally a tool, and your suggestion. An email address is optional on both and only for a reply. No account is needed.

Each goes through the same checks, the same local copy and the same delivery as the contact form, and becomes a private message in MSP Reboot’s support system with the page you were on and the time. Nothing is published: there are no public reviews, ratings or averages, and a rating is of this website, not a review of any software. If you give an email address, it is recorded on the message so somebody can reply by hand; the support system does not send anything to it automatically.

Volunteering to test or contribute

The volunteer form on Help MSP Zero grow collects what you choose to give: how you would like to help, which tool, your name or an alias, your role, what you could test on or offer, and whether you would run pre-release builds. An email address is required here, because the point is a reply, and you must agree to be emailed about the offer before it is sent.

It travels and is kept exactly like a suggestion: a private message in MSP Reboot’s support system. Nothing is sent to you automatically and there is no mailing list, so there is nothing to unsubscribe from; replies are written by a person, about your offer. Ask, and what you sent is deleted. Your name appears on this site only if you ticked “credit me publicly”, as the name you gave, and is removed when you ask.

The figures and feature requests on that page are read once a day from GitHub’s public API by this server. Your browser does not contact GitHub to show them. A feature request title shown there is public on GitHub already.

Feature requests and voting

Requests sent with the request form and votes on the roadmap are tied to a confirmed email address, so that each person counts once. We email a 6-digit code from noreply@mspzero.com to check the address is yours. The address is stored encrypted, with a keyed hash of it used to recognise it again; it is never shown on the site, never shared, and not used to send anything except those codes. An address that is never confirmed is deleted after 14 days.

Once confirmed, your browser keeps a cookie (mz_voter, up to 180 days) so you can vote without another code; “Forget it on this device” on the roadmap removes it. With each vote the server keeps a keyed hash of your network address, never the address itself, to spot one machine voting as many people. Votes are shown as totals, never one by one. You can take a vote back at any time.

What you write in a request is published only after a person approves it, and without your email address or company. Your name is shown only if you tick “show my name”. Requests that are rejected or caught as spam are deleted after 180 days; the record of what the spam filters refused is kept for 90 days. The request form and the email step run the same spam check as the other forms, which sets the same form-session cookie.

If you also tick “contact me about beta testing other (commercial) products” on the volunteer form, that choice travels with your offer, the same way, and nowhere else.

The share buttons are ordinary links and copy buttons. Nothing is sent to Facebook, LinkedIn, Reddit or anyone else unless you click one; clicking opens that service’s own share screen, where you decide what, if anything, to post. The email button opens your own mail app with a draft. The links handed to those services carry utm_ parameters saying which button was used, so a visit that arrives through one is counted as such. The Facebook page link is a plain link: no Facebook script, pixel or embed loads on this site.

When Matomo is running, it also records which of these buttons was used — “link copied”, “rating submitted” and so on — with the page, and for a rating the number of stars. When a contact enquiry is filed it records that it was, with the topic and project you picked. It also records clicks on a tool page’s install guide, repository, documentation, issue tracker and update notes, the first time you type into the contact form (with the topic and project selected, not the text), and how far down a tool page or guide you read. Each is counted once per page view. It never records an email address or anything you wrote.

Anti-spam records

Refused submissions are logged with the time, the reason, and a keyed, truncated hash of the IP address and of the email address. The hash lets repeat attempts from one source be grouped without storing the address itself. The log never holds your message, your name, your IP address or your email address.

Who receives it

MSP Reboot, through its support system at cp.mspreboot.com — your contact-form submission, rating or suggestion.
Our Matomo installation at analytics.agit8or.net — the page-view details listed above. It runs on our own server.

No other service receives data from this site. Facebook, LinkedIn or your mail app are involved only if you click one of the share buttons, and then only with the page’s address. We do not sell data, and we do not use it for advertising.

How long things are kept

The local copy of a delivered enquiry, rating or suggestion: deleted 90 days after delivery. The support ticket is the lasting record.
An enquiry that could not be delivered: kept until it has been dealt with.
The support ticket: kept in MSP Reboot’s support system until staff delete it. It is not deleted automatically.
Anti-spam log: 14 days.
Rate-limit counters: 48 hours.
Used spam-check answers: a random identifier for each answer that has been used, kept until it expires (about 20 minutes), so that it cannot be used twice.
Form session: a day on the server; the cookie ends with your browser session.
Analytics and access logs: no automatic deletion at present, as described above.

Asking about your data

Email support@mspreboot.com to ask what is held about you or an enquiry, or to have it deleted.

The projects

The six projects listed here are software you download and run on your own servers. Nothing in them reports to this site, and your use of them is not visible here. Some installers and update checks download from GitHub or a project’s own download server; each project’s First deployment section lists what it needs to reach.

What this site does with data