wordradar

This policy explains what wordradar collects, why, and what you can do about it. The short version: an email address, a login, the usage logs needed to run a metered API, plus an anonymous page-visit count. No ad delivery, no cross-site tracking.

What We Collect

Account data: your email address, display name, and password hash (or a Google account identifier if you sign in with Google). Invite codes used at signup.
Usage logs: which endpoints your keys call, timestamps, request outcomes, and credit consumption. These exist for metering, abuse prevention, and debugging.
Service emails: transactional messages (signup, key management, security notices). No marketing emails during the beta.
Traffic analytics: the site runs Google Analytics anonymously to learn which pages are useful; it is not used for ad profiling.

What We Do Not Collect

No ad delivery and no cross-site tracking; analytics exist only to improve the product.
No payment data ever touches our servers — checkout is processed by Stripe, card details never pass through us, and we store only the resulting entitlement.
We do not sell or share personal data with anyone.

Cookies

One session cookie keeps you logged in. That is all. No tracking pixels, no cross-site identifiers.

Where Data Lives

The service runs on our own server in the United States; pages are served through Cloudflare's global network. Backups stay within the same infrastructure.

Retention and Deletion

Usage logs are kept while your account is active (metering and dispute resolution). If you delete your account, we remove your account data and keys; anonymized aggregate usage rows may remain for accounting.

Your Rights

You may request access to, correction of, or deletion of your personal data: email [email protected] (or simply reply to any wordradar email) and we will handle it and get back to you.

Changes

If this policy changes materially, we will note it in the changelog and update the last-updated date above.