Privacy notice
This page says what happens to what you send through the contact form, and what the company hosting this site records when you only read a page. Short version: the form is the only thing here that asks you for anything, and the rest is the ordinary record any web server keeps.
What this site collects. When you use the contact form, you send three things: your name, your email address, and the message you write. The IP address you sent them from is recorded alongside them, and the paragraphs below say where all four end up. The pages you read here set no cookies and read none, so nothing on them follows you from one page to the next.
What the host records anyway. None of the pages you read here carries an analytics script, a tracking pixel, or an ad tag, and Netlify's own analytics product is switched off, so nobody here is counting your visit. That is still not the same as leaving no trace, and the difference is worth being straight about. Every page here is delivered by Netlify's servers, and a server cannot answer a request without knowing where to send the answer, so Netlify logs your IP address and a line describing your browser and operating system every time a page loads, whether you fill in the form or not. Netlify's own documentation calls both of those personal information, and its dashboard lets a site's owner search recent requests, including by IP address. This is how the web works rather than something this site chose: it happens on every site you visit. We cannot switch it off, we cannot see all of it, and we cannot delete it; the paragraph below on what deleting does not reach says why.
Why. Your name and email address are used to write back to you. Your message is read by Mandy so she knows what you are asking about or sharing.
Where it goes. This site is hosted on Netlify, and the contact form is handled by Netlify Forms. When you press send, your name, email address, message, and that IP address are stored in the Netlify account this site runs on, and Netlify emails the message to Mandy, so there is a copy in her inbox as well as one in the store. Before it reaches her, the message is checked by Akismet, an automated spam filter, to catch obvious junk submissions. Akismet's own policy says the check involves the message and technical details such as the IP address it came from. Netlify has not published exactly what it hands over, so this notice cannot give you a complete list, and it would rather say that than guess.
Who holds it. Your message is addressed to Mandy. She is the person who reads it and the person who answers it. It is stored in a Netlify account that the developer who built this site and keeps it running operates on her behalf, rather than in an account of her own, so he has technical access to what is stored in it: anyone who can sign in to an account can open what is kept there. He is not the person it is written to, and answering it is not his to do. The one time he has to handle your message is when you ask for it to be deleted, which the section below describes. This is the ordinary arrangement between a small practice and the person who builds its website, and it is written here because you should not have to assume it.
How long it is kept. Your message stays in that Netlify account until it is deleted, and the emailed copy stays in Mandy's inbox until she deletes that one. There is no automatic expiry on Netlify's side that we can promise you a date for. The copy Akismet keeps for the spam check is deleted on Akismet's own schedule, which its policy puts at somewhere between two weeks and ninety days. Akismet also says it keeps a small part of what it receives for longer than that, and neither Mandy nor this site has any way to reach it.
Asking for it to be deleted. Use the contact form on the Bookings page and say that you want your earlier message deleted. If you can, send it from the same email address you used the first time, so she can find the right one. She deletes the emailed copy from her own inbox. The stored copy is in a Netlify account she has no sign-in for, so she passes the request to the developer who runs it, and he opens the account, finds your message and removes it. That means a second person carries out that part of your request. The IP address stored with your message goes when the stored copy goes.
What deleting does not reach. Not everything can be deleted, and this is the part most notices leave out. Netlify's own record that your browser asked for a page, described above, is not something Mandy or the developer who runs the account can delete: there is no button for it and no request that produces one. Akismet keeps a small part of its spam-check copy longer than the rest, as the paragraph above says, and the only way to ask about that part is Akismet's own contact form, on their site rather than this one. Netlify does not say what happens in its backups after something is deleted, and this notice cannot speak for what the company carrying her email keeps once she has deleted a message there, so nobody here can honestly tell you a message is gone from every copy everywhere. What can be said plainly is which copies are deleted and which are not: the copy stored in the Netlify account and the copy in Mandy's inbox are deleted, and the records inside Netlify's and Akismet's own systems are not.
Asking for anything to be deleted means sending another message through the same form, with your name and email address in it, and that request is spam-checked like every other message. It is the only route this site offers, it is an awkward one, and we would rather say so than let you find out afterwards. That request can be deleted the same way, once it has done its job.
What this site does not do. This is about the pages you read here. No analytics and no ad trackers, anywhere. This site sets no cookies of its own. Nothing is loaded from another company except the booking calendar on the Bookings page, which is described below, and every other page loads nothing from anyone but this site. The maps here are pictures, not embedded widgets, for the same reason: an embedded Google map would report your visit to Google the moment the page loaded, whether you touched it or not, so this site does not use one.
The booking calendar. The Bookings page shows a calendar so you can choose a time. It is provided by a company called Calendly, and it is the one thing on this site that is loaded from somewhere else. Opening that page contacts Calendly, so Calendly can see that a browser opened it, and Calendly may set its own cookies in your browser. No other page on this site does that. If you go on to book a time, the details you type into the calendar go to Calendly and to Mandy; they do not pass through this site's contact form.
The maps. The pictures of the streets around the office are still images, made in advance and served from this site along with everything else on the page. Making them used Geoapify's map service and map data from OpenStreetMap contributors, which is what the small credit under each one is for. Your browser does not contact either of them: it loads a picture from this site, the same as any other image here. Clicking a map opens Google Maps in a new tab, which is a visit to Google, made at the moment you choose to make it.
The one page this does not cover. Mandy writes blog posts through an editing tool, and that tool has a sign-in page at /admin/. It is not part of what you are reading and there is nothing on it for a visitor: it exists so she can sign in and write. It is the only page here that loads anything from another company. Opening it makes three requests to two of them: two to unpkg, where the editing tool checks its own version, and one to GitHub's status service, which tells it whether GitHub is up. We would rather it made none. Removing them means changing code that belongs to someone else, so they stay, and they are written down here instead of being left out. Reading the pages of this site sends nothing to either company.
More detail. Netlify's own privacy policy is at netlify.com/privacy. Akismet's is at akismet.com/privacy. Calendly's is at calendly.com/privacy.
Questions. Anything on this page, including a deletion request, goes through the contact form on the Bookings page, and reaches Mandy. The practice address is Mandy Spanier, 5319 S Lewis Ave, Suite 200, Tulsa, OK 74105.
