PRIVACY POLICY
How this site handles data. Plain English, no dark patterns. Last updated 3 May 2026.
THE SHORT VERSION
This is a personal site. I do not run ads, I do not sell data, I do not have a marketing automation platform behind the scenes profiling you. The only personal information that touches this site is what you choose to send via the contact form, and the only thing I do with it is read it and reply to you.
If you want the longer version, the rest of this page covers exactly what is collected, where it goes, and how to remove it.
ANALYTICS AND COOKIES
This site uses no third-party analytics. No Google Analytics, no Mixpanel, no Segment, no Hotjar. There is no cookie consent banner because there are no marketing or analytics cookies to consent to.
The only cookies (or LocalStorage entries) the site sets are functional ones you triggered yourself: your preferred theme (default versus 1995 mode), your language preference if you switch locales. These are stored in your browser only, never sent to a server, and you can clear them anytime from your browser settings.
The hosting provider, Netlify, may keep aggregated edge-server access logs for security and abuse-detection purposes. Those logs are out of my reach and rotate on Netlify's schedule. They contain IP addresses and request paths, no personal information.
THE CONTACT FORM
If you fill in the contact form on /contact/, the message goes to my inbox at gautam@seahawkmedia.com via the form provider. The data sent is the name, email address, and message you typed. Nothing else.
I keep the email until I have replied and a reasonable follow-up window has passed (typically 6 months). After that I delete the thread unless we have an active project.
If you want me to delete a message earlier, email me asking for it and I will. No forms to fill, no support ticket, just a reply.
EMBEDDED CONTENT
Some pages embed content from other sites: YouTube videos on /wplegends/, Calendly links to my booking page on service pages, X / Twitter and LinkedIn links in the footer.
When you click an external link or play a YouTube embed, the destination site sees you and may set its own cookies under its own privacy policy. I do not control what they collect. If you want to read the source policies: Google / YouTube, LinkedIn, X / Twitter, Calendly.
SUPABASE AND CONTENT STORAGE
The blog posts, guides, and other published content on this site are stored in Supabase, my hosted Postgres provider. Supabase is the database, not the visitor analytics layer. It does not see who you are when you read a post.
The content stored in Supabase is the same content you see rendered on the page. There is no shadow database of visitor data behind the scenes.
AI CRAWLERS
I explicitly allow GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, and Google-Extended to crawl this site so that the writing here can be cited in AI search surfaces. Their crawler activity is request-shaped, not visitor-shaped, and does not involve any of your personal data.
If you are reading this because an AI tool surfaced one of my posts, the underlying model has my publicly published content as training context. It does not have anything you submitted via the contact form or anywhere else.
YOUR RIGHTS
Under UK GDPR and equivalent regimes, you have the right to:
- Ask what personal data I hold about you
- Ask me to delete it
- Ask me to correct anything that is wrong
- Object to specific uses
- Complain to the UK Information Commissioner's Office (ico.org.uk) if you think I have mishandled it
To exercise any of those rights, email gautam@seahawkmedia.com. I will reply within a reasonable window, usually a few working days.
DATA CONTROLLER
The data controller for this site is:
Gautam Khorana
Office 77, 22 Notting Hill Gate
London W11 3JE
United Kingdom
gautam@seahawkmedia.com
If you reached this page from a Seahawk Media engagement and your question relates to that work specifically, the Seahawk privacy notice covers it: seahawkmedia.com/privacy-policy.
CHANGES TO THIS POLICY
If anything material changes (a new analytics tool, a new third-party embed, a new data flow), I will update this page and bump the date at the top. The git history of this file is public on GitHub, so previous versions are auditable.