What happens to what you send me.

What is collected when you read this, and when you get in touch.

Reading a page here records exactly one thing: my own server adds one to a count of how many times that page was asked for that day, Raleigh time. It is a single number per page per day, sitting in the database on the server that just sent you this page. Nothing about you goes into it.

The one script on this page draws the animations. On this page it makes no request and stores nothing on your machine. The front page carries two more scripts: one sends the form when you press Send, and one controls the comparison drawing. Neither stores anything on your device.

The work page is the only page with a recording of the software on it, and on the work page the script that draws the animations does ask for two files, both of them from this server and from nowhere else. On a narrow screen it fetches the still picture that stands in for the recording, whatever your settings. On a wide screen it fetches the recording itself, unless you have told your device you want less motion or fewer bytes. If you press play yourself it fetches the recording whatever the screen, and that one is you asking rather than the script.

There is no advertising pixel, no analytics company, no embedded video from anybody else, and no cookie set on any page you can read without signing in. The internet address your request came from is not stored. Nothing about your browser is stored. Nothing on that row could tell two people reading a page apart from one person reading it twice. It counts automated visitors too, the crawlers and the link checkers. They look the same to a count as you do, and I would rather the number said so than quietly leave some of them out. Reading takes nothing else from you at all.

The front page has one contact form. It sends what you enter only when you press Send. Existing customers can sign in through Go to portal.

The form on the front page

Four boxes, and three of them are the ones you have to fill in: your name, your email address, and your answer to the one question about a job somebody at your company still does by hand. The fourth is your phone number and it is optional. If you leave it empty nothing is stored in its place. When you press the button, those go into the database on the same server that sent you this page, with the time they arrived, and the only person who can read them back is me, behind a passcode. The server also tries to send two emails about it there and then: one to my own inbox so that I see it, and one back to you saying it arrived. The internet address you sent it from is not stored; it is held in memory for a few minutes so one machine cannot flood the form, and it is never written down. Nothing about your browser is stored either.

It is kept until it is deleted. Nothing on this site deletes itself after a set number of days, so what you send stays in that database until you ask me to remove it or I remove it myself. The section on how long things are kept says how to ask.

One thing happens that you did not type, and it is worth saying out loud. If the address you leave is at your own company’s domain rather than at Gmail or the like, my server asks that website’s front page for itself, once, to see whether you are already running one of the big trade software packages. It keeps a note of what it found beside your message. That is one request for one page, made by this server with my business named in it, and nothing you sent me is handed to anybody in the making of it.

Existing calendar bookings

For an existing calendar booking, the information collected was four boxes and the time you picked. Three of them are the ones you have to fill in: your name, your email address, and a note of two or three lines about what you want to talk about. The fourth is your phone number and it is optional. That panel is only there when booking is open; when it is not, the whole band is gone rather than sitting there refusing you. When you press the button, all of it goes into the database on the same server that sent you this page, along with the time you chose and the time you sent it.

Then three things leave this server, and that is the difference between booking a call and filling in the form. A meeting is created on my Google calendar carrying your name, what you wrote, your email address and your phone number if you gave one. You are named on it as the other guest, which is what makes Google send you the invitation and produce the video link. The server also tries to send two emails through Resend in the same moment: one to you with that link and what you wrote, and one to me. Tries, because if the sending key is not set on the server it sends neither and says so in its own log. The meeting itself is real either way, and Google’s invitation reaches you from Google. Google and Resend are both named in the section on who else can see it, and nobody else is involved.

I am the only person who can read the bookings back, behind the same passcode as everything else here, and they are kept until they are deleted. Nothing on this site deletes itself after a set number of days. If you ask me to cancel, the meeting comes off the calendar first and the invitation in your own calendar goes with it. If you ask me to take the booking out altogether, there is a control behind that same passcode that does exactly that. The meeting comes off the calendar first in the same way. Then the row itself goes from the database, with nothing kept in its place and no copy of it left on this server.

Booking AI training, and the feedback after it

The booking form at the foot of the AI training page asks which session you want, your company, your name, your email address and how many people, and optionally your phone number, where it would happen, dates that work and a note. All of it goes into the database on the same server that sent you this page, with the time you sent it, and one email about it goes to me through Resend. Nothing is sent back to you automatically.

After a session I send the company its own private link. That page carries the session materials once I release them, and a feedback form: a rating from 1 to 5, what was most useful, what you would change, and your name if you want to give it. Feedback goes into the same database. I am the only person who can read bookings and feedback back, behind the same passcode as everything else here, and they are kept until they are deleted.

Opening an account, and signing in

Behind the Go to portal button there is a sign-up for the beta. It asks for the name of the business, your own name, your email address, the username you pick, and the beta code I gave you. It does not ask you for a password. That door is only open while I am handing out codes; the rest of the time the address answers with nothing there. When you press the button, an account for that business is opened in the database on the same server that sent you this page, your login is made, and you are signed in.

You choose your password afterwards, from a link. The server tries to send you an email with your username in it and a one-time link to a page where you type the password you want; the link works once and stops working two days after it was sent, and you can ask the sign-in page for a fresh one at any time. Tries, because if the sending key is not set on the server it sends nothing and says so in its own log. That email goes through Resend, which is named in the section on who else can see it, and it goes to the address you typed and nowhere else.

No email from me ever contains your password, and none ever will. Up to Sep 8, 2026 one did: the sign-up asked you to invent a password and then mailed it back to you so you had it somewhere, which left the only readable copy of it sitting in your inbox for good. Both halves of that are gone, the box and the email, and this paragraph stays here because a page that quietly stopped mentioning it would be telling you less than the version that admitted it.

Your password is not stored. What is kept is a scrambled version of it, made together with a random value that is kept beside it, and there is no way back from that to the password itself. Signing in scrambles what you type the same way and compares the two results. So nobody can read your password out of that database, and that includes me.

Signing in afterwards takes the username and the password and nothing else. If you ask for a new password, that box takes your username or your email address, and my server writes down a scrambled copy of a one-time link and emails you the link; that one stops working an hour later or the moment it is used, whichever comes first. The page says the same sentence back whatever you typed, so asking cannot be used to find out whether a login exists. Once you are signed in, what you write and what you upload in the account is stored the same way and read by the same one person.

An account is kept until it is deleted. Nothing on this site deletes itself after a set number of days, so it stays until you ask me to remove it or I remove it myself. The section on how long things are kept says how to ask.

An email you send me

Your address, the name your mail program puts on it, the subject, what you wrote, and anything you attach. That is the job you want looked at, and it is the part the whole conversation starts from.

The time it arrived

Stored so I can tell you honestly how long you have been waiting.

A phone call

Nothing at all. The number at the top of every page is my direct number, and this site never sees it. Later on, if we get as far as the week where I watch the job being done, that call is recorded, and I ask you first, every time.

How long it is kept, and how to have it deleted.

Kept while there is a live conversation, and afterwards as a record of work quoted or done. If you want it gone, email hello@mizellsoftware.com and say so; you do not have to give a reason, and I will delete it, attachments included, and confirm it in writing. If you would rather not put anything in writing at all, the phone number at the top of every page reaches the same person and stores nothing.