Privacy
What happens to what you type here.
Short version: the two forms on this site send what you write to the support system so I can reply. Nothing is sold and nothing is shared for advertising. The site uses a self-hosted analytics tool (Matomo) without cookies to see which pages are read, and keeps daily totals of a few clicks and submissions. Neither is linked to what you type in a form, and you can switch analytics off; details below.
Last reviewed 15 October 2026
What the forms collect
The contact form asks for your name, email address and message, and optionally your company and phone number. The booking form asks for your name, company, email address and a description of the problem you want to discuss, and optionally your phone number and the approximate size of your business. Your browser's timezone is sent with a booking so the appointment can be shown in your local time.
Both forms are submitted by POST. That means what you type is sent in the body of the request and never appears in the page address, your browser history, the server's access log, or a referrer header passed to another site.
Where it goes
Submissions are passed to the support ticket system, which is the system of record. The website does not write your message, name, email address or phone number to its own database, to a log file, or send them on by email.
A booking additionally records the date and time of the appointment, a reference to the ticket, and a random key your browser generates so that pressing the button twice, or retrying after a dropped connection, cannot create two bookings. That record holds no personal information — no name, no email address, no message.
Once a message or booking has reached the support system, the site adds one to a daily total: messages by inquiry type (general, sales, hosting or consultation), and bookings. If you arrived through a link carrying a campaign tag (for example from a LinkedIn post), the total also records that tag. Nothing you typed goes into that total.
What else the server keeps
- An IP address and a counter, to enforce rate limits on the forms. This is what stops the forms being used to send bulk submissions. It is not linked to your message.
- A session cookie, holding the answer to the CAPTCHA you are shown and a token that protects the form against cross-site request forgery. It is deleted when the submission completes.
- Daily totals for a few steps: clicks on the booking and contact buttons, the products directory and links to the other sites listed on the products page; each step of the booking form (started, details accepted, times shown, a time picked, and a failed attempt with a one-word reason such as “slot taken”); and a checklist being opened or a guide being read. Each row is a date, which step or link, the page it was on, a label for where on the page, a campaign tag if the link you arrived on had one, and a count. No IP address, cookie, browser details or anything else that could tell one visitor from another, and nothing you typed. The campaign tag is kept in your browser’s session storage for up to a day and is deleted when you close the tab. Nothing is counted from automated browsers or test copies of the site, and adding
?notrack=1to any page address stops counting in your browser (?notrack=0turns it back on). - A font request to Google. The site's typeface is loaded from Google Fonts, so your browser fetches it from Google's servers, which see your IP address and browser details as with any web request. No cookie is set and nothing else is sent. This is the only request a page makes to a server not run by the site’s owner.
- Standard web server logs, which record the address of the page requested, your IP address and your browser's user-agent string, as almost every web server does.
Analytics
Since 15 October 2026 the site uses Matomo, an open-source analytics tool, to see which pages are read and where people stop on the booking form. It runs on a server operated by the owner of this site (analytics.agit8or.net), not by an analytics company, and the data is not shared with anyone.
- No cookies. Matomo is set up not to store anything in your browser, so it does not recognise you from one visit to the next.
- What each page view sends: the page address (only the path and any campaign tag such as
utm_source; nothing else from the address), the page title, the page you came from, your browser and operating system, screen size and language, and your IP address, which reaches the analytics server with the request the way it reaches any web server. - Your IP address is shortened before it is stored. The analytics server removes the last two parts of the address, so 203.0.113.5 is stored as 203.0.0.0. The full address is used only while the visit is being processed, for example to estimate the country.
- Events: the same steps listed in the daily totals above (booking form steps, a time picked, a failed attempt and its one-word reason, a confirmed booking, a checklist opened, a guide read, a click to one of the other sites on the products page). Never your name, email address, company, phone number, what you wrote, or a ticket reference.
- Switching it off: if your browser sends a Do Not Track or Global Privacy Control signal, Matomo is not loaded at all. Adding
?notrack=1to any page address switches off both Matomo and the daily totals in that browser (?notrack=0turns them back on).
What this site does not do
- No visitor profiles across visits, no session recording, no heatmaps.
- No advertising or tracking cookies, and no third-party tracking scripts.
- No selling or renting of your information to anyone.
- No newsletter sign-up hidden inside a contact form.
- No Facebook scripts or embeds. Posts featured on the updates page are plain links with summaries written here, so reading them sets no Facebook cookie unless you choose to click through.
Getting your information removed
Email help@mspreboot.com and ask. If you have a ticket number, include it — it makes the request much quicker to action.
Still to be confirmed
This notice describes what the software does, which I can state accurately. The following need a decision from the business, and in places from a lawyer, before this page is complete:
- How long support tickets and booking records are kept before deletion.
- How long rate-limit records and server logs are kept.
- The legal entity acting as data controller, its registered address, and which privacy regimes apply — GDPR, UK GDPR, CCPA or none.
- The identity and location of the support ticket system provider, which processes this data on the business's behalf.
- How long analytics data is kept. At present the analytics server does not delete visit records or reports automatically.
Nothing above is a placeholder for something already decided — these are genuinely open questions, and inventing answers would make this notice worse than having none.
