Skip to Main Content

Privacy Policy

Effective Date: October 23, 2026

This Privacy Policy describes how your information is collected, used, and safeguarded when you use the contact form on jeffliffick.com.

  1. Information Collected

    When you submit the contact form, the website handles and logs the following information:

    • Email Address
    • Message Subject
    • Message Content

    Because jeffliffick.com is a personal website and does not utilize user accounts, user registration, or tracking cookies, this is the only personal information gathered from you.

  2. How Your Information is Used

    Your information is used strictly to respond to your inquiries, comments, or requests.

    The logged submissions are processed directly by the backend application logic and are never used for marketing, newsletter subscriptions, or behavioral tracking.

  3. Data Sharing and Infrastructure

    Your personal information is never sold, rented, or shared with third parties for commercial or marketing purposes.

    The website is built using the open-source Laravel framework. Form submissions are processed securely on our own self-hosted server environment and stored in the private application database. No third-party form-building platforms, tracking scripts, or data brokers have access to your submissions.

  4. Data Retention

    Contact form submissions are only retained in the database for as long as necessary to fulfill the purpose of your inquiry or to maintain a record of past correspondence to assist with ongoing conversations.

  5. Your Rights

    Depending on your location, you may have rights under regional privacy laws (such as the GDPR or California privacy laws) regarding your data. This includes the right to request access to or permanent deletion of your contact form history and email address from the database logs. To exercise these rights, you may submit a request directly through the contact form.

  6. Changes to This Policy

    This privacy policy may be updated occasionally to reflect changes in the hosting environment, server infrastructure, or legal obligations.