When you sign up through the fan signup form at /fans, you submit an email address and an optional name. That data is stored locally in the fan_signups table on our Postgres database (hosted by Neon) and is also forwarded to MailerLite (connect.mailerlite.com) so Sean can send newsletters to you through the MailerLite platform.
Every newsletter email MailerLite sends on Sean's behalf includes an unsubscribe link, and you can also request removal directly via the privacy contact below. Removing yourself removes the row from fan_signups and MailerLite suppresses further sends to that address.
When you submit a booking or press inquiry at /contact, we collect the following fields and store them in the contact_inquiries table on the same Postgres database:
On submission you automatically receive a confirmation email. That email is sent from noreply@griffinrocks.com (the address is configurable via the CONTACT_AUTOREPLY_FROM environment variable) so you have a record that your inquiry was received. Sean reads and replies to inquiries manually; no automated marketing is sent to inquiry submitters.
We collect a small amount of anonymous usage data in a page_views table to understand which pages are visited. For each request to a tracked page we record:
The hash cannot be reversed to recover your IP. We do not use third-party analytics on the site itself
— there are no Google Analytics, Facebook Pixel, or similar trackers that follow you across other
websites. The only outbound request is a single-pixel Polsia analytics beacon that assigns
a random per-browser UUID stored in localStorage; it does not collect your email or
any identifier that links to your fan or inquiry records.
You can request at any time, free of charge:
Inquiry rows are retained for a reasonable period so Sean can refer back to past bookings and press conversations; once that period elapses, or earlier on your request, rows are deleted. Fan signup rows are retained until you unsubscribe or ask for removal.
For any privacy-related request — access, correction, deletion, or a question about this policy — reach out via the address below.