What this site collects, and why.
A plain-language account of the information markfasel.dev handles. It is short because the site does very little: there are no accounts, no advertising, and one form.
August 2026
Who runs this site
markfasel.dev is operated by Mark Fasel, LLC, a Florida limited liability company based in Palmetto, FL. Throughout this page, “I” and “we” refer to that company.
This is a small professional site. It has no user accounts, no logins, no advertising network, and no e-commerce. The only place it asks for information is the contact form.
Information you provide
The contact form collects:
- Name
- Email address
- Company (optional)
- Role (optional)
- Project type
- Budget range
- Timeline
- Your message
There are no hidden fields collecting anything else. If you email me directly instead, I receive whatever your message contains.
How that information is used
What you submit through the form is used to:
- Reply to your inquiry
- Evaluate a potential consulting or project engagement
- Respond to an employment, recruiting, or speaking opportunity
- Continue the conversation that follows
Submitting the form does not subscribe you to anything. There is no marketing list behind it. The newsletter is a separate, opt-in service you join yourself on Substack — the form and the newsletter share no data.
Email delivery (Resend)
Contact-form submissions are delivered by email using Resend, a transactional email provider. Two messages are sent: a notification to my inbox containing what you submitted, and an acknowledgement to the address you gave so you have a record that it went through.
Resend processes that message content in order to deliver it, and is governed by its own privacy policy. Delivered mail then lives in my email account like any other correspondence.
Server logs and abuse prevention
Two things happen server-side when you submit the form, and both are worth stating plainly rather than burying:
- Rate limiting. Your IP address is read from the request in order to limit how many messages can be sent from one source in a short window. It is held in server memory for the length of that window and is not written to logs or stored anywhere.
- Diagnostic logging. When a submission is processed, a log entry records the event along with the name and email address on it, so that a delivery failure can be traced and fixed. These logs are retained by the hosting platform and are visible only to me.
Analytics (Google Analytics 4)
This site uses Google Analytics 4 to understand how it is used — which pages people read, and whether anyone finds what they came for. At a high level, Analytics collects:
- Pages viewed and how you moved between them
- Session and activity information, such as visit duration
- Approximate geographic location, derived from IP address
- Browser, device, and operating-system information
- How you arrived at the site, such as a search engine or a link
Analytics is used in aggregate. I am interested in whether an essay was read, not in who read it, and I do not attempt to identify individual visitors or connect analytics data to a contact-form submission. Google’s handling of this data is governed by its own privacy policy.
Hosting (Vercel)
The site is hosted on Vercel. As the infrastructure provider, Vercel processes requests to the site and retains operational logs, which is what makes the diagnostic logging described above possible. Its handling of that data is governed by its own privacy policy.
Links to other services
The site links out to Newsletter, LinkedIn, GitHub, X — including the Designing Modern Systems newsletter on Substack. Those are third-party services with their own privacy policies and their own data practices. Once you follow a link off this site, nothing here applies to what happens next.
Questions, corrections, and removal
If you want to know what I hold about you, have it corrected, or have it deleted, email hello@markfasel.dev and say so. This is a one-person practice — the request comes to me directly, and I will act on it.
Changes to this policy
This page describes the site as it works today. When the tools behind it change — a new service, a removed one — this page is updated in the same change, and the date at the top moves with it.