Privacy

What we collect, why we collect it, where it lives, and how to make us delete it. Short, because we do not collect much.

Last updated 20 August 2026

The short version

Openhour Solutions LLC is a small studio in Charleston, South Carolina, and is the company responsible for the information described here. This site counts page views and a handful of button clicks with Vercel Web Analytics, which sets no cookie and uses no cross-site identifier, and it carries a Meta pixel that records a page view so we can measure our own ads. Neither is used to follow you around the internet after you leave.

The only information we hold is what you typed into a form and chose to send us.

What we collect, and only when you send it

  • Newsletter signupYour email address and the date, plus a note that it came from this website rather than somewhere else. Every issue carries a one-click unsubscribe link that works without an account and without asking us.
  • Book a call with usYour name, email address, and — if you fill them in — your business name and a description of the work you want off your plate, plus which button on the site you opened the form from. Aaron reads it before the call.
  • AnalyticsWhich pages were viewed, which of our buttons were clicked, and a rough screen size, counted by Vercel Web Analytics without a cookie or a cross-site identifier. The Meta pixel records that a page was viewed; Meta’s own policy governs what it keeps.
  • EmailIf you email us, we have your email. That is not a system, it is a mailbox.
  • Client dashboardIf you are a client with a login, your account and session are handled by Supabase. That is the only part of this site that sets a cookie, and it is set only on the dashboard and login pages.

There is no other collection. We do not build a profile, we do not enrich what you send with data bought from anyone else, and we do not have a “marketing platform” that would let us.

Booking a call goes to Google

Picking a time uses Google Calendar’s booking page. Whatever you enter there goes to Google under Google’s privacy policy, not ours — the same as it would if you booked with us any other way. What you typed on our side before that is covered by this page.

The “ask an AI about us” buttons

Some pages carry a row of buttons that open ChatGPT, Claude, Perplexity, Grok or Gemini with a question about Openhour already written. Those are ordinary links. Nothing is sent anywhere until you click one, and we are not told that you did.

If you do click, you land on that company’s own site and what happens next is covered by their privacy policy, not ours. The question we prefill contains no information about you — it is the same sentence for every visitor.

Where it is stored, and who can reach it

  • SupabaseNewsletter signups and call requests — the only two tables anything you send us lands in. Neither is readable or writable with the key that ships to your browser: row-level security is on with no policies at all, so every request from the public key is refused. The only way in is our own server, which validates first. The same database also holds our own business records — clients, invoices, the work we have in flight — but nothing there comes from a form on this site.
  • VercelHosting. Vercel keeps standard server request logs, as any host does.
  • Google WorkspaceOur email. If you write to us, that is where it sits.

Newsletter issues are written by our own agent and published to a separate build host. Reading one here does not send your browser to that host: this server fetches the text, and the artwork is re-served through this domain. As far as your browser is concerned, the whole newsletter is this site.

Fonts are served from this site, not from Google. The typeface is downloaded when we build the site and shipped with it, so reading this page does not tell anyone else that you did.

How long we keep it

Newsletter subscribers are kept until you unsubscribe. We keep the row after that, flagged, rather than deleting it — it is what stops you being re-added by accident and starting to receive issues again. If you want it gone entirely, ask and it will be.

Call requests are kept while there is a live conversation and for a reasonable period after, in case you come back. Ask, and we will delete yours.

Getting your data, or getting rid of it

Email [email protected] and ask for a copy of what we hold, or ask us to delete it. There is no form and no portal. A person reads it and does it, normally the same week.

Depending on where you live you may have a formal right to access, correct, export or delete your data, or to object to how it is used. We do not ask where you live before honoring a request, so the practical answer is the same either way: ask us.

Children

This is a business-to-business site. It is not directed at children and we do not knowingly collect anything from anyone under 13.

Changes

If we start collecting something new, this page changes in the same release as the code that collects it, and the date at the top changes with it. We will not quietly widen it.

What’s taking up your team’s time?

This first call is about what your team needs and how Openhour works. We won’t discuss pricing on this call.

Add phone and business (optional)

On our first call

  • Walk us through the work your team needs help with.
  • Get to know Openhour and how we build.
  • Schedule a second call to review a proposal.

Between calls, our development team prepares a proposal. On the second call, we go over the plan and the price together.

Built on

  • Vercel
  • Docker
  • Sentry
  • Langfuse
  • GitHub
  • Railway