Privacy Policy
How AI Rank Watch handles checker data, reports, analytics, Google OAuth/account sessions, Creem billing data, retention, deletion, and unsubscribe.
Privacy Policy
AI Rank Watch is an independent AI visibility checker operated by a personal operator. This Privacy Policy explains what information we collect, how we use it, how long we keep it, and how to contact us about privacy, deletion, or unsubscribe requests.
This policy is not a promise that every feature is available in every environment. If a source, report delivery method, or monitoring feature is not approved or configured, AI Rank Watch may show demo/sample output, queue a request, or record a waitlist request instead of running a live source check.
Information we collect
- Information you submit in the checker, such as brand or company name, optional website/domain, selected competitors, selected prompt pack, and custom prompts.
- Email address if you ask us to email a report, join the beta/waitlist, receive weekly monitoring, receive product updates, sign in, or use paid checkout.
- Account and login information, including email address, hashed email, Google account identifier, user ID, session ID, login/callback timestamps, session expiration, and logout or revocation status when Google OAuth or account sessions are enabled.
- Payment, subscription, and billing metadata when paid checkout is enabled, including Creem customer ID, checkout/order ID, subscription ID, product ID, plan key, subscription status, current period dates, cancellation status, refund/dispute status, webhook event ID/type, payload hash, entitlement snapshots, and customer portal state needed to operate billing.
- Consent choices, including report delivery consent, weekly monitoring consent, beta/waitlist consent, Terms acceptance, Privacy Policy acceptance, source availability acknowledgement, and analytics/cookie choices where applicable.
- Generated report data, including report ID, report status, source mode, source coverage, timestamp, prompt count, competitor count, score components, limitations, and short approved evidence excerpts or demo/sample text where allowed.
- Technical and usage data needed to run and protect the service, such as request time, page path, generic event names, source mode/status, report status, error codes, coarse referrer/UTM, hashed or truncated IP/session identifiers where used for rate limiting, and browser/device information collected by analytics providers.
- Logs needed for security, abuse prevention, debugging, reliability, billing integrity, and compliance checks.
Please do not submit passwords, API keys, confidential prompts, regulated personal data, secrets, private customer data, or other sensitive information into the checker or prompt fields.
How we use information
- Generate, save, display, and, if configured, email AI visibility snapshot reports.
- Show demo/sample, queued, limited, unavailable, or approved-source results with the correct limitations.
- Operate beta/waitlist and weekly monitoring requests when you separately opt in.
- Authenticate accounts, protect signed-in sessions, gate checkout/account access, sync billing status, and manage paid entitlements.
- Create checkout sessions, process subscriptions, support customer portal access, reconcile Creem webhook events, handle cancellation/refund/dispute workflows, and answer billing support requests.
- Remember consent choices and unsubscribe/deletion states.
- Prevent abuse, enforce rate limits, troubleshoot errors, and protect the service.
- Understand site usage and improve product pages through Cloudflare Web Analytics, Google Analytics 4, and Microsoft Clarity, subject to the cookie/analytics controls described below.
- Respond to privacy, deletion, unsubscribe, support, billing, or compliance questions sent to the contact email.
We do not sell personal information as a product. We do not use user-submitted prompts or reports to claim official platform rankings. We do not intentionally store raw full AI/provider outputs, screenshots, credentials, full card numbers, payment credentials, or secrets unless a later source/payment method and legal review specifically approve that behavior.
Reports and source outputs
AI Rank Watch reports are observed snapshots tied to selected prompts, selected source coverage, method, timestamp, and limitations. Generated report URLs should be opaque and unlisted or access-controlled where appropriate. Generated report pages must be noindex and excluded from sitemap by default.
If no approved live source is configured, a report may be demo/sample output only. Demo/sample output is not live AI platform data and should be labeled clearly.
Account and login information
If you sign in, AI Rank Watch may use Google OAuth to authenticate your account. We may process and store your email address, hashed email, Google account identifier, user ID, session ID, login/callback timestamps, session expiration, and logout or revocation status. Login cookies such as OAuth state and account session cookies are used to keep you signed in, protect checkout/account access, prevent abuse, and support account security. These cookies are essential for account and billing functionality.
Payment, subscription, and billing information
If paid checkout is enabled, AI Rank Watch uses Creem to process checkout, subscriptions, billing, invoices, taxes where applicable, customer portal access, refunds, chargebacks, disputes, and related payment lifecycle events. We do not store full card numbers or payment credentials.
We may store billing metadata needed to operate the service, such as Creem customer ID, checkout/order ID, subscription ID, product ID, plan key, subscription status, current period dates, cancellation status, refund/dispute status, webhook event ID/type, payload hash, and entitlement snapshots. We may share account email, hashed email, plan key, product ID, user/account identifiers, and checkout metadata with Creem as needed to process billing and sync entitlements.
Retention
Free/demo report retention is currently up to 1 week unless deleted earlier or retained longer for security, abuse-prevention, debugging, or legal/compliance reasons.
- Saved reports: retained for up to 1 week, then deleted, expired, or no longer rendered unless a paid plan explicitly provides longer history.
- Email/report delivery records and waitlist records: retained for up to 1 week unless a longer period is required to honor an unsubscribe, deletion, support, security, abuse-prevention, or legal/compliance obligation.
- Account/session records: retained as needed to keep the account secure, maintain login/session state, support checkout/account access, process logout/revocation, prevent abuse, resolve support requests, and comply with legal or security obligations.
- Paid account, subscription, invoice, tax, refund, dispute, security, and entitlement records may be retained longer to provide account access, comply with tax/accounting/legal obligations, prevent abuse, resolve disputes, and honor cancellation/refund/deletion requests.
- Logs and technical diagnostics: retained for up to 1 week unless needed for security, abuse, debugging, billing integrity, or legal/compliance reasons.
- Source outputs or approved excerpts: retained for up to 1 week, and raw full outputs should not be stored by default unless a later source method and legal review specifically approve that behavior.
If paid plans launch, actual retention periods or the criteria used to determine them must be kept aligned with the live billing, account, and source systems.
Third-party services
- Cloudflare for hosting, routing, security, and Cloudflare-first runtime/storage infrastructure.
- Cloudflare Email Routing/forwarding for the public contact path if a domain alias is configured.
- Cloudflare Web Analytics for privacy-oriented site analytics.
- Google Analytics 4 for site analytics.
- Microsoft Clarity for session analytics/behavior insights.
- Google OAuth for account sign-in when login is enabled.
- Creem for checkout, subscriptions, invoices, taxes where applicable, customer portal, refunds, chargebacks, disputes, webhook events, and billing lifecycle processing when paid checkout is enabled.
- Email/report delivery or waitlist handling may be recorded through Cloudflare-first infrastructure unless a separate email provider is later selected and disclosed.
Do not add or name additional providers such as new payment processors, email platforms, error logging vendors, live AI/search data providers, advertising pixels, or CRM tools unless they are actually configured and this policy is updated.
Cookies and analytics
AI Rank Watch uses essential cookies for security, OAuth state, signed-in account sessions, checkout/account access, and abuse prevention when those features are enabled. AI Rank Watch also uses Cloudflare Web Analytics, Google Analytics 4, and Microsoft Clarity to understand aggregate usage, diagnose product issues, and improve the site. These tools may collect device, browser, interaction, page-view, referral, and approximate location information. GA4 and Clarity may use cookies, local storage, or similar technologies depending on configuration and visitor location.
Analytics must not receive plaintext emails, raw custom prompts, full raw provider outputs, credentials, tokens, confidential business details, or report IDs that expose user information.
If you visit from a region that requires consent before non-essential analytics, AI Rank Watch should ask for consent before GA4 or Clarity run. If consent mechanics are not implemented for those regions, GA4/Clarity should not be enabled for those visitors. Users may also use browser privacy controls, cookie blocking, and available Google/Microsoft opt-out tools.
Email, waitlist, deletion, and unsubscribe
Report delivery, beta/waitlist, product update, and weekly monitoring are separate purposes. Weekly monitoring must require a separate opt-in and must not be pre-checked.
If recurring monitoring or marketing emails are sent, each such email must include an unsubscribe link or clear unsubscribe instructions. You may also unsubscribe or ask us to remove your email by contacting shenyanying33 [at] gmail [dot] com.
If no email provider is configured, AI Rank Watch may record a report/waitlist request for beta follow-up but should not claim that an email was sent.
You can request deletion of a saved report, email record, waitlist entry, or other personal information by contacting shenyanying33 [at] gmail [dot] com. If a self-serve report deletion endpoint or unsubscribe endpoint is available, it should be linked from the report page or email. We may need enough information to locate the record, such as the report link, report ID, email address, or request timestamp. Do not send secrets or passwords in privacy requests.
Children and changes
AI Rank Watch is intended for business and marketing users and is not directed to children. Do not use the service to submit children’s personal information.
We may update this Privacy Policy as the product changes. If we add paid plans, accounts, new providers, longer retention, live source collection, ads pixels, or material new data uses, this policy must be updated before those features are made public.