Waitloop
Features How It Works Pricing Docs Documentation Sample Code AI Prompt Instructions Masterclass 5-Day Masterclass (1:1 for founders) AI for Leaders (workshops for teams) Contact Log in
Back to Home

Cookies Policy

Effective date: September 27, 2026

This Cookies Policy explains how Waitloop.io ("Waitloop", "we", "us", or "our") uses cookies and similar technologies (such as browser local and session storage) across our public website, our dashboard, and our embeddable form widget. It should be read together with our Privacy Policy.

In short: Waitloop does not use advertising or cross-site tracking cookies. We rely mainly on a small amount of browser storage that is strictly necessary to keep you signed in to the dashboard, a first-party analytics cookie from PostHog on parts of our public website so we can see how the site is used, and a few cookies set by trusted providers (such as our payment processor and bot-protection service) when those features are used.

On this page
  1. What These Technologies Are
  2. How We Use Them
  3. Technologies We Use
  4. Third-Party Cookies
  5. The Form Widget
  6. Managing Cookies
  7. Do Not Track
  8. Changes & Contact

1. What These Technologies Are

A cookie is a small text file stored on your device by a website. Local storage and session storage are similar browser technologies that let a site save small amounts of data in your browser; session storage is cleared automatically when you close the tab or browser. We refer to all of these together as "cookies and similar technologies." They can be set by the site you are visiting ("first-party") or by another service the site uses ("third-party").

2. How We Use Them

We use cookies and similar technologies for a limited set of purposes:

  • Strictly necessary. To operate the dashboard, most importantly to keep you securely signed in during a session. Without these, core features such as logging in would not work.
  • Security. To help protect forms and accounts against bots, spam, and abuse (for example, when bot protection is enabled on a form).
  • Payments. When you subscribe to a paid plan, our payment processor uses cookies to process the transaction securely.
  • Analytics. On parts of our public website we use PostHog, a product analytics service, to understand how visitors use the site (for example, which pages are viewed and which buttons are clicked) so we can improve it. PostHog stores a random identifier in a first-party cookie and in local storage. It is not used for advertising or to track you on other websites.

We do not use cookies for advertising or to track you across other websites.

3. Technologies We Use

Technology Type Purpose Duration
Session sign-in storage First-party, strictly necessary Keeps you signed in to the dashboard during your session Cleared when you close the browser or log out
Preferences storage First-party, functional Remembers interface preferences where applicable Until cleared
Bot-protection cookies Third-party (hCaptcha), security Distinguishes humans from bots when enabled on a form Set by provider
Payment cookies Third-party (Stripe), strictly necessary Secure checkout and fraud prevention during payment Set by provider
Product analytics (PostHog, name starts with ph_) First-party, analytics Records page views and clicks against a random identifier so we can see how the site is used Up to 1 year
Referral and booking storage (names start with wl_) First-party, functional Remembers a partner or referral link's code so the person who referred you gets credit, keeps your booking details while you pay, and remembers that you opened the prompt pack Referral code 60 days; booking details until you close the tab; prompt pack until cleared

The exact names and lifetimes of third-party cookies are controlled by those providers and may change.

4. Third-Party Cookies

Some features rely on trusted third parties that may set their own cookies, governed by their privacy policies:

  • Stripe: payment processing and fraud prevention during checkout.
  • hCaptcha: bot and spam protection when enabled on a form.
  • Google / GitHub: if you choose to sign in with one of these providers, they may set cookies as part of their sign-in flow.

Our website also loads fonts and styling from content-delivery networks. These do not set tracking cookies but, like any web request, your IP address is visible to the provider delivering the file. The analytics data described above is sent to PostHog, which processes it on our behalf; its cookie is set on our own domain.

5. The Form Widget

Our embeddable widget is designed to be lightweight and privacy-respecting. By itself, it does not set advertising or cross-site tracking cookies on the websites where it is embedded. A Waitloop Customer may separately choose to connect their own analytics (for example, Google Analytics) to their form; if they do, that analytics provider's cookies and policies apply, and the Customer is responsible for disclosing them in their own cookie and privacy notices.

6. Managing Cookies

You can control and delete cookies and clear browser storage through your browser settings. Most browsers let you block or remove cookies and see what is stored. Please note that blocking strictly necessary cookies and storage will prevent you from signing in to and using the dashboard. Blocking or deleting the analytics cookie (its name starts with ph_), or using a content blocker, stops analytics without affecting how the site works. Helpful instructions are available in the support pages of major browsers (Chrome, Firefox, Safari, and Edge).

7. Do Not Track

Because we do not track users across third-party websites for advertising, we do not respond differently to browser "Do Not Track" signals. We will treat your data in accordance with our Privacy Policy regardless of any such signal.

8. Changes & Contact

We may update this Cookies Policy from time to time. When we make material changes, we will update the effective date above. Questions about this policy can be sent to:

Waitloop.io
Email: support@waitloop.io