Cookie policy.
Haunt keeps browser tracking minimal and uses cookies or similar storage only where needed for service flows.
Last updated: 3 June 2026.
Trust route
Legal and privacy questions go to support@hauntapi.com. Security reports go there too.
These pages are plain-English operating terms, not a badge saying a lawyer has blessed every comma.
Cookie position
Haunt does not currently use non-essential advertising cookies on the public website. The API authenticates with headers, not browser tracking cookies.
What may still be stored or requested
- Essential service logs and first-party activation events: request IDs, user agents, timestamps, routes, status codes, click/copy/signup event names, and rate-limit events may be logged for security, operations, and conversion debugging.
- Account or checkout flows may use necessary cookies or equivalent storage from Haunt or Stripe to complete login, signup, fraud prevention, checkout, and billing.
- Google Fonts are loaded from Google-hosted font endpoints, which may receive browser request metadata such as IP address, user agent, and referrer.
- Stripe checkout and billing pages are operated by Stripe and may use Stripe cookies and fraud-prevention technologies under Stripe's terms and privacy notices.
No tracking ads
Haunt does not sell advertising space, build ad-targeting profiles, or use third-party ad pixels by default. If that changes, this page needs updating before it ships. Tiny mercy.
Your choices
You can block non-essential cookies in your browser. Blocking essential cookies or storage used by checkout, login, or security systems may break those flows. API access through server-side requests should not need browser cookies.