Privacy Policy

Last updated 2026-09-17

This page explains what FuckCaptcha (fuckcaptcha.top, "the Service") collects, why, who it is shared with, and how to have it deleted. The Service is operated by an individual, who acts as the data controller and can be reached at admin@fuckcaptcha.top.
This policy is published in several languages for convenience; the English version is the authoritative one.

1. What we collect

  • Sign-in: the account identifier returned by Telegram, Discord or Google (Telegram user id, Discord user id, or Google's sub), and the email the provider shares (Google always, Discord only when you allow it). Used only to identify your account, never for profiling.
  • API keys: the nsk_… key issued to you, its name, creation time and last use.
  • Recognition data: the CAPTCHA image or challenge you submit. It is forwarded to the upstream recognition provider solely to answer that request, and the page URL you supply is used for that request only — we do not store the page URL.
  • Usage records: the type, status, credits deducted and timestamp of each job. Used for billing, debugging and abuse prevention.
  • Payment: payments are processed by Stripe. We store only the Stripe session or invoice identifiers, amount, currency, plan and expiry — never card numbers.
  • Browser storage: your session token, language preference, a one-time key used for the post-login redirect, and your cookie choice (nsk_consent). We set no session cookie.

2. What we do not do

  • We do not sell or rent your data and do not run ads.
  • Telemetry beaconed by the browser extension is discarded inside our infrastructure.
  • We do not inspect any part of a submitted image or page beyond what the recognition request needs.

3. Who we share it with

  • Cloudflare: hosting and database (the Service runs on Cloudflare Workers + D1).
  • Stripe: payment processing.
  • The upstream recognition provider: receives the recognition request and the page URL, never your identity or email.
  • Google Analytics: only if you accept the consent banner — see section 8.
  • Telegram, Discord and Google: only when you choose to sign in with them, as that is how the sign-in handshake works.

This list is kept current; changing it updates this page.

4. How long we keep it

Keys and usage records are kept for as long as your account exists, and job records are not deleted automatically. Payment records are kept as long as accounting and tax rules require. You can ask us to delete your account and its data at any time.

5. Your rights

Write to admin@fuckcaptcha.top to access, correct, export or delete your data (account, keys and usage records), to object to or restrict processing, or to ask a question. You may also complain to the data protection authority where you live.

6. Children

The Service is not intended for children under 13, or under the higher age that your country requires for consent to online services.

7. Changes

Any change is published on this page with an updated date at the top.

8. Analytics and cookies

With your consent we use Google Analytics to measure traffic: which pages are visited, referrers, approximate region, and device and browser type. It sets cookies; the data is processed by Google and may be transferred outside your country. You can decline in the banner — if you decline it is not loaded. To change your mind later, clear this site's browser data and the choice is offered again. Google also offers its own opt-out browser add-on. These cookies are not required for the service to work.

9. How we protect your data

All traffic is served over HTTPS (TLS 1.2 or newer). Session tokens are signed and expire. API keys are shown in full only once, then only as a short prefix, and upstream credentials never leave our infrastructure.