Privacy
Privacy policy
This policy covers the hawkeye.systems website, the Hawkeye application, our community calls, and the newsletters we send. It is written by Hawkeye Systems, run by Marshall Kirkpatrick in Portland, Oregon. Questions go to marshall@marshallk.com. The What’s Up With That browser extension has its own privacy policy, published with the extension. Last updated September 16, 2026.
What this website collects
Our web server keeps standard logs: your address on the internet, the pages you request, and the browser you use. We keep them for 30 days to diagnose problems and to detect abuse. The site also uses Google Analytics, which sets cookies and assigns your browser an identifier so that Google can tell us how many people visited, which pages they read, and where they came from. We do not run advertising pixels, a Meta pixel, session recording, or any tracker beyond that one. You can stop Google Analytics by blocking cookies in your browser or with Google’s opt-out add-on. If you register for a community call, Luma collects your name and email on our behalf. If you book a call, Calendly does the same.
What the application holds
When you use Hawkeye, we hold your account email, the sources you monitor, the links you save, your drafts, published issues, editorial guidelines and point of view, any newsletters you forward to Hawkeye, and logs of what the application did for you. We use it for one purpose: to run the service you signed up for. We do not sell it, share it for advertising, or use it to train models. Drafting, summarizing, and analysis run on Anthropic’s API, and under Anthropic’s published API terms your content is not used to train its models. The application uses a session cookie to keep you signed in and nothing else.
People who appear in what we monitor
Hawkeye reads publicly available sources: websites, feeds, public newsletters, and public video. When a person is named in those sources, their name, role, and what they said in public may appear in briefings and in an index that connects people, organizations, and topics. This is public information, processed so that our clients can follow their fields. We do not combine it with private data, we do not sell it, and if you would rather not appear, write to us and we will remove you.
Newsletters
If you subscribe to a newsletter published with Hawkeye, your email address is held for that publication and sent through Resend or Mailchimp. Every message carries an unsubscribe link. Unsubscribing removes you from that publication; it does not affect any other list you chose to join.
Services we rely on
DigitalOcean hosts the application and this site. Anthropic provides AI drafting and analysis. Cloudflare reads websites that publish no feed. Resend and Mailchimp send email. Google provides company mail and website analytics. Luma handles event registration and Calendly handles scheduling. Each holds only what its job requires, under its own published terms. Adding a service that would handle client content requires the founder’s approval and an update to this page.
How long we keep things
Application data stays as long as your account is active. When you ask us to delete your account, everything in it is removed within 30 days and we confirm in writing. Server logs are kept for 30 days. Google Analytics data is kept by Google for up to 14 months. Newsletter subscriptions last until you unsubscribe.
Your rights
You can ask to see what we hold about you, correct it, export it, or have it deleted, and you can object to our processing of it. In the application, subscriptions export as OPML and writing as Markdown or HTML at any time. For anything else, write to marshall@marshallk.com and you will have an answer within 30 days. If you are in the European Union or the United Kingdom, these are your rights under the General Data Protection Regulation, and you may also complain to your local data protection authority. Hawkeye is not intended for anyone under 16, and we do not knowingly collect information from children.
Security and changes
How we protect this data is described on our Security page, including what we do if something goes wrong. This policy is reviewed every September alongside our security policy, and whenever we add a service or a way of collecting data. Changes are posted here with a new date at the top.