Privacy policy
HypeDar collects the account, billing, usage, and product data needed to operate the AI signal radar and protect the service.
Launch draft. Last updated: July 5, 2026. This policy should be reviewed before production billing launch.
HypeDar is a product by CodePawl.
Data we collect
When you create an account or sign in, we may store your email address, display name, authentication provider, password hash for email/password accounts, OAuth profile data provided by Google or GitHub, session state, and failed-login attempt metadata used for abuse protection.
When you use Pro features, we may store saved items, predictions, XP events, user stats, analysis requests, prompts you submit, generated reports, source metadata, quota usage, estimated and actual feature costs, and queue status.
Billing and providers
If paid checkout is enabled, we may store plan, subscription, entitlement, provider customer, and payment records needed to activate access, handle billing status, and reconcile provider events. Payment providers may process payment details under their own policies.
How we use data
We use data to authenticate users, provide public and Pro research features, enforce quotas, prevent abuse, operate billing, generate requested AI analysis, improve reliability, and respond to support or privacy requests.
Cookies and similar storage
HypeDar currently uses essential authentication cookies for session management and OAuth safety. We do not currently configure analytics, replay, advertising, or non-essential tracing cookies. See the Cookie policy for details.
Sharing
We do not sell account data. We share data only with service providers needed to operate the product, such as hosting, authentication, queueing, storage, billing, and email providers when those integrations are enabled.
Your choices
You can choose not to create an account, avoid submitting sensitive prompts, sign out to clear active session access, and contact us to request access, correction, deletion, or export of account data where applicable.
Security and retention
We use signed HTTP-only session cookies, password hashing, provider secrets in private environment configuration, and quota/abuse checks. We retain records while needed to provide the service, meet billing or security obligations, resolve disputes, or maintain operational logs.
Contact
For privacy questions, contact [email protected]. This address must be routed before launch.