Privacy

What this site knows about you.

This site counts its own visits, without cookies and without knowing who you are. What it holds about anyone personally comes from the contact form. This page says what both of those are. Clients invited to the private library have a short section of their own.

What's collected

When you submit the contact form, I receive and store:

  • What you typed: your name, email address, company if you gave one, the kind of engagement you selected, and your message.
  • Any files you attached.
  • Your IP address and your browser's user-agent string, recorded with the message.

What it's used for

Your details and message are used to reply to you, and for nothing else. I don't add you to a mailing list, and I don't sell or share what you send.

The IP address and browser details exist to tell real inquiries from automated spam, and to limit how many messages one address can send in an hour.

Who handles it

The site runs on Google Cloud in the United States. Your message and any attachments are stored there, and Google Cloud keeps routine server logs of requests to the site, which include IP addresses.

A copy of your message is emailed to me through Resend, a mail delivery service, and arrives in my inbox.

The contact page loads Google reCAPTCHA to screen out automated submissions. reCAPTCHA runs when that page loads, before you submit anything, and sends Google information about your browser and device; it may set Google cookies. Google's own Privacy Policy and Terms of Service cover what Google does with that. If your browser blocks reCAPTCHA, the form still works.

No other page loads anything from a third party: the visit counting below runs from this site's own code. There is no advertising and no tracking across other sites.

Counting visits

This site counts its own visits. Page views, and a few actions — opening the contact form, sending it, clicking the email address, downloading a file, following a link off the site — are recorded in Google Cloud, where the site itself runs. No analytics company is involved. Nothing sets a cookie or stores anything on your device, and none of it is used for advertising.

For each of those, the site keeps the page's path, the website that linked you here if there was one, the campaign tag on the link if it had one, whether your screen is phone, tablet or desktop sized, how far down the page you scrolled and for how long, and — when you send the contact form — which kind of engagement you picked from its list, never anything you typed. It does not keep your IP address or your browser's user-agent string. Those two are combined with a random key to make a code that's the same for all of your visits in one day, so I can count visitors and not only page views. The key is replaced every day and deleted within a few days, after which the code can't be traced back to you, and today's visit can't be linked to tomorrow's.

Anything after a “?” in a page's address is removed before it's sent, except those campaign tags. Visit records are deleted automatically after about 13 months. If your browser blocks the counting, nothing else on the site changes.

The client library

Clients I'm working with can be invited to a private library of articles and videos on this site. If you've been invited, the site holds your email address on its invite list for as long as you have access.

Signing in works by emailed link, sent through Resend like the contact form's messages. When you sign in, the site sets one cookie in your browser. It does nothing but keep you signed in, for 30 days or until you sign out, and it is only ever sent to the library's own pages. It is the one cookie this site sets itself, and nobody who hasn't signed in gets it.

The site keeps a record of that signed-in session, and of each sign-in link for the few minutes it is valid, both stored as a scrambled value rather than the secret itself. It keeps no record of which articles you opened or which videos you watched under your name. Pages in the library are counted the way every other page is, with nothing connecting the count to you. The videos are stored in Google Cloud and played from this site, not from a video company.

The client portal

Clients with library access may also have a private message thread with me on this site. What you write there, and any files you attach, are stored in Google Cloud alongside your email address and the time you posted. If someone on the thread records a message as a decision, the site also stores who recorded it and when.

A thread can be read by the people invited from your company for that engagement, and by me. Your address is shown beside your messages to those people. Nothing in a thread is used for anything but the engagement it belongs to.

When someone posts, the other side is sent an email through Resend saying that there is a new message. That email never contains the message or its files.

How long it's kept

Stored messages and attachments are deleted automatically two years after they arrive.

For clients with library access: a sign-in link's record is deleted once it is used or expires, a session's after 30 days, and your address comes off the invite list when your access ends.

Messages and files in the client portal are deleted automatically 2 years after they are posted, or sooner if you ask.

Your requests

To see what I hold about you, correct it, or have it deleted sooner — including the copy in my inbox — email hello@lystadworks.com.

Last updated November 2026.