What this page says
Haunt collects the minimum data needed to run accounts, process extraction requests, enforce plan quotas and feature gates, debug failures, prevent abuse, bill paid plans, and answer support requests.
What we collect
- Account details such as name, email address, password hash, API key hash, plan, and account status.
- Request metadata such as endpoint, timestamp, response status, latency, usage counts, redacted URL and prompt previews, and encrypted request history for support/debugging.
- URLs, prompts, optional headers/cookies, and notes you submit to the API or support forms.
- Payment and subscription events from the payment provider. Card details are handled by the payment provider, not stored by Haunt API.
How we use it
We use this data to provide the API, prevent abuse, measure quota, enforce plan access such as authenticated extraction on Pro and Scale, process payments, debug failures, improve reliability, and respond to support requests.
Security and retention
API keys are stored as hashes. Sensitive request history is encrypted or redacted where appropriate. Request history is retained only as long as needed for support, debugging, abuse prevention, and business records.
Deletion and questions
For privacy questions or deletion requests, email support@hauntapi.com. We may need to keep limited records when required for fraud prevention, billing, legal obligations, or security.