BotDetect CAPTCHA Generator

BotDetect™ CAPTCHA generator is a non-stalking form-security solution that uses a mix of measures, that are easy for humans but hard for bots, to prevent automated form posting.

BotDetect also provides an audio Captcha alternative to keep websites accessible to people with impaired vision, enabling you to make WCAG and Section 508 compliant websites.

CAPTCHA Generator Features

BotDetect CAPTCHA Box
  • Self-hosted • Licensable source-code
  • Works in China • No third-party server dependencies
  • Native .NET Core 1/2, .NET, Java & PHP backends
  • Works with Angular/JS, jQuery, etc, .js web frameworks
  • TestMode-enabled -- ready for your CI/CD pipelines
  • Localized Captcha generation, using various Unicode character sets and multi-language sound pronunciations
  • Custom Captcha style, image size, code length, css, icons, tooltips, and pretty much everything else
  • Produces legible images & audio; as well as XHTML 1.1 Strict, Section 508, and WCAG AAA compliant markup
  • Doesn't stalk your users; nor does it slurp the form data
  • From a vendor that has nothing to do with the NSA
  • Allows for EU's GDPR, Brazilian LGPD, and California's CCPA compliant sites!

Why BotDetect?

BotDetect Captcha vs. ReCaptcha

The years of Google’s relentless abuses of their organic and paid search monopolies, and the years of their equally relentless campaign of disinformation and FUD about captchas, took a toll among our former competitors -- there are only two viable players left. Ladies and gentleman, this is 'BotDetect Captcha' vs. 'Recaptcha the Stalker' fight. Please take your seats.

BREAKING NEWS:

2019/06/28: Give up Your Privacy, or Else

'If sites use [Recaptcha] to lock out users with high risk scores, they may wind up locking out users who ... refuse to allow Google ... to track their browsing history.'

2019/06/27: Recaptcha V3 Has a Dark Side

'Because reCaptcha v3 is likely to be on every page of a website ... there's a chance Google is getting data about every single webpage you go to that is embedded wi...'

2019/05/03: Googleminion blabbed that Recaptcha has been stalking you for years

'Goldstein: A few days after I talked with Malenfant, I spoke with a Google spokesman. And he was able to tell me that it still matters in reCAPTCHA whether or not a user has an active Google account. Ouch!

2019/04/18: International Trio Blew up a Hole in Recaptcha V3 Obfuscation Layer

'Our proposed method achieves a success rate of 97.4% on a 100 × 100 grid and 96.7% on a 1000 × 1000 screen resolution.'

Tracking mouse movements; what a joke! 96% is a bus-sized hole, indeed. We can't wait to see what kind of stuff will be jumping out of it :)

2019/02/26: A QUIC Look at Web Tracking

'...3rd-party ... can recognize users based on the token that the latter present during the 0-rtt connection attempt.' / 'a rejected 0-rtt handshake does not terminate a tracking period, because the server can link the...

QUIC, a Chrome-2-Google identity beacon, lets Google to stalk you across the web without ever asking for your id, and without ever confirming the identification. Brilliant, isn't it :)?

What Google confirmed so far:

  • 2.5 years after we sticked the 'the Stalker' label on it; Google spokesman confirmed that, if you have a Google Account, Recaptcha has been stalking you for all those years. The tip of the iceberg!

What Google didn't confirm yet:

  • Transport-layer stalking -- independent of cookies, or a Google Account status, or the existence of a Google Account.
  • Protocol audits by independent researches found built-in stalking capabilities in TLS Channel IDs, TLS v1.2 & 1.3, and in QUIC.
  • The Hamburg Uni Quartet audited the latter three protocols. Combining them with the Trio that just broke through the Recaptcha's 'tracking mouse movements' obfuscation layer might bring some interesting results.
  • But, somehow, they will have to make sure that the Stalker is not aware that it is being tested -- what is easier said than done!
  • Antitrust violations -- including burying this site on the Google Search -- over the last six years, at least.
  • Check by yourself! On your desktop, open an incognito mode browser window and try finding us with the single-keyword 'captcha' search. Do it -- it will explain many things!
  • The EU's Margrethe Vestager, who fined Google $2.7B over a similar issue, said that competitors were typically on the page four.
  • As we're more often on the page 14 than 4 -- maybe we're getting the VIP treatment :)
  • The role of the NSA and its vicarious fronts.
  • But you can't blame them for this particular one -- every country, including the US, has laws forbidding such kind of disclosures :)

Intro: Recaptcha Versions

At present, the Stalker exists in the following three variants:

  • Invisible Recaptcha (v2) -- the Invisible Stalker -- whose release Google kinda regretted.
    That gradual disappearance of the word 'Invisible' from its homepage was fun to watch :).
  • Recaptcha (v3) -- released after Google spent like 20 months applying lipstick on the Invisible Stalker pig -- hoping no one will notice that the pig with a lipstick is still a pig :).
  • Nocaptcha / Checkbox Recaptcha (v2) -- the original Stalker. It appeared, for a while, as if it was being taken behind the shed -- but no gunshot was ever heard. It seems that Google had a change of heart and decided to keep it -- likely following the Invisible Stalker fiasco.

The presence of multiple versions makes maintenance of this article more difficult than it should be; but you will figure it out. It is the same stalker after all -- just dressed in three different outfits.

Let's see how we stack up against each other:

2019/01/03:

Recaptcha audio cracked -- with 90% hit ratio this time! Surprised? We are not :)!

'Thx to the changes to the audio challenge, ... ReCaptcha is easier than ever before.'

Google learned nothing out of those 2017/03 and 2017/10 breaches of the Recaptcha audio.

2018/05/30: Recaptcha Bypass! Ouch :)

2017/10/31:

The Stalker's audio is broken again!

'Whatever Google has in mind to replace its reCaptcha had better be ready soon: ...'

unCaptcha: A Low-resource Defeat of reCaptcha's Audio Challenge

2017/10/26:

Vicarious broke Recaptcha, BotDetect, Yahoo and PayPal captchas.

Vicarious , funded with $122m, couldn't find anything more useful to do. The timewasters :)!

2017/03/02:

Recaptcha the Stalker audio cracked!

This time around with a little help from Google's own Speech Recognition API :)

2016/04/07:

Recaptcha broken by Columbia Uni Trio!

Automatically solved 70.78% of the time through what looks like multiple inherent design flaws. This is the biggie that is going to haunt Recaptcha for years to come.

1) BotDetect Is Secure

BotDetect is unique among Captcha generators in offering many Captcha image and sound styles. While each of them is easily comprehensible to human users, randomly using multiple Captcha generation algorithms makes the generated Captcha challenge extremely difficult to pass automatically.

This approach to Captcha security is validated by the BotDetect track record: since 2004, we have over 3000 paying customers and only a single confirmed case of automated Captcha breaking by ordinary spammers.

2) BotDetect Works in China

BotDetect Captcha works in China -- while Recaptcha does not!

With its 1.3B people China has approximately 20% of the world population and outputs like 16% of the world GDP. The size of China's economy is second only to the size of the US'.

Even if you do not actively target the Chinese market, the chances are that some of your visitors, users, and customers sometimes venture or even reside there. It helps not having Recaptcha breaking your website for them.

However, if you, or your users, do target the Chinese market, making your website fully functional for the visitors from China should be one of the top items on the 'minimum requirements' check-list. Make sure to check it!

3) BotDetect Is Multinationals Friendly

New Localizations Arrived:

With more than a hundred world languages already supported in the code, and 56 different audio localizations being just a download away, BotDetect Captcha will ensure that your interaction with every local market is done to that particular local market's familiar combination of script and language.

4) BotDetect Lets You Meet Regulatory Requirements

Recaptcha is a 3rd-party stalking service delivered from the cloud that you have no control over; and due to its obfuscation and encryption you can only guess what payload your users get.

2019/04/08: BDC NET v4.4.1

2018/11/06: BDC NET v4.4.0

2018/10/23: .NET

  • Added iOS 12+ audio support

2018/09/20: Java, PHP

  • Added iOS 12+ audio support

'Plug & Pray', one might say :).

BotDetect is self-hosted on your own servers, and its source code is available; thus enabling you to easily meet whatever regulatory or security requirements that are, or might be, imposed on your application or website!

Think: GDPR, eff. 2018/05/25, or the California Consumer Privacy Act of 2018, eff. 2020/01/01, or whatever else might come in your direction.

5) BotDetect Is Accessible and Legal on US Government Websites

BotDetect Captcha is both Section 508 and WCAG compliant, and as such legal on the US federal agencies' websites -- unlike Recaptcha, that is just lame-ducking there while awaiting for its Section 508 lawsuit by a disgruntled employee or a user to throw it away.

Why is it like that? It is simple. When you block cookies in your browser, or go into incognito mode, Recaptcha reverts back to the old 'two-words Recaptcha' , or to various 'pigs, dogs, and street signs' pictures. And a few things aside from a miracle will make your application using either the 'two-words Recaptcha', or those 'pigs, dogs, and street signs' pictures, able to satisfy this particular Section 508 requirement.

6) BotDetect Will Not Get You Sued Over
the 578 Patent Infringement

As BotDetect does not use those 'pigs, dogs, and street signs' pictures at the center of the Confident Technologies vs. Ticketmaster case we couldn't be bothered to waste money on lawyers' fees in order to check the merit of the case -- that is on the Ticketmaster's plate.

But, the Confident Tech is not a patent troll; those guys had a product back then; so we opt to assume that they know what they are doing -- albeit we are perplexed that they went after the Recaptcha users, instead of after Google itself.

Note that settling such a suit might cost a small fortune; what is still peanuts compared with how much it would cost to defend it. For Ticketmaster, the Stalker turned out to be an expensive joke.

Ensuring that neither you nor your customers get sued over the 578 patent infringement should be the next item on that 'minimum requirements' check-list. Isn't it?

7) BotDetect Is Both Privacy and National Security Friendly -- It Does Not Spy

Unlike Recaptcha, BotDetect does not operate under 'if it can stalk you then you are human' principles; and will not make your application rejected by the majority of world governments on the grounds of national security; be it on their own websites, or on the websites of their sensitive institutions and industries.

2017/11/22: GoogleBorg Caught in SIM-less & Seamless Android Location Slurp!

'If Google was a person, it would have had a restraining order for stalking slapped on...'

2015/02/20: AdTruth's Privacy Research of the Original NoCaptcha ReCaptcha Stalker

'This is a way for Google to indirectly link activity outside of Google’s properties – collected under the guise of security – to Google's knowledge of that individual...'

The Nocaptcha Recaptcha, recently renamed as Checkbox Recaptcha, is the oldest of the Stalker's three contemporary variants.

Eric Schmidt, Google's Then-CEO:

2010/10/04: 'We don't need you to type at all. We know where you are. We know where you've been. We can more or less know what you're thinking about.'

2010/09/07: 'A near-term future in which you don’t forget anything, because the computer remembers. You’re never lost.'

2009/12/11: 'If you have something that you don't want anyone to know, maybe you shouldn't be doing it in the first place ... it is possible that that information could be made available to the authorities.'

Those quotes predate the original Stalker! Thx Eric, we appreciate your directness; we couldn't have explained GoogleBorg better ourselves :).

If you have a privacy or national security sensitive website or application and are considering the Stalker, think again:

  • Recaptcha the Stalker refuses to work 'as advertised' if you switch your browser into incognito mode, block cookies, or use Tor Browser. It gets annoyed when prevented from stalking. Why?
  • It is owned by Google who already knows who you are; think Gmail, Search, Docs, Play, YouTube, etc. And now, Google can cross-match that data with your activities on all Stalker armed websites.
    Kiss goodbye to both your users' privacy and national security.
  • Its client-side is a .js payload; obfuscated, encrypted, and delivered from the cloud by the party who knows your identity (Google); straight into your browser; completely bypassing servers of the Stalker armed website you are visiting.
    Hm, what could possibly go wrong :)?

In short, Recaptcha is not a captcha, but a stalker disguised as a captcha. By default, it does not check your humanity at all, but fingerprints your browser and cookies and matches it with your past activities across the web. It is a sort of 'Login by Google' -- just a way more dangerous one.

8) BotDetect Means No Post-GDPR EU Legal Murkyland

GDPR bans 'forced consent' -- while Recaptcha the Stalker forces your users to accept being stalked by Google even just to open your form -- not to mention to fill it, or to use your service.

A legal Murkyland, or outright illegal?

Google mismarkets the Stalker as a captcha. Now imagine a convicted serial arsonist who mismarkets his setting-your-farm-alight urge as a pest-control service -- no difference!

Google might argue that stalking is necessary for providing its stalking service. That would be a valid point -- as a stalker it has to stalk -- if it was not mismarketed as a captcha service.

But, who knows, Google might go googlish and even argue that the stalker named reCAPTCHA was not marketed as a captcha. Any takers?

What stance the EU DPAs will take, and then the judges, is anyone's guess -- but, see those enormous fines; feel like betting the farm on it?

Did anyone mention Brazil :)?

9) Captcha, Inc. Eats Its Own Dog Food

While Google, since 2009, mostly avoided using Recaptcha on its own properties. Why?

A cynic would argue that on its own properties Google already knows who you are so Recaptcha the Stalker was not needed there -- and it does not thwart bots that well anyway.

2017/06/27: EU Fined Google Then-Record $2.7B for Manipulating Search Results!

'The company demoted rivals and unfairly promoted its own services', says the EU.
'What Google has done is illegal under EU antitrust rules,' said Margrethe Vestager.

Whenever it was about its organic and paid search monopoly abuses, Google showed its catch-us-if-you-can attitude. The EU did the job.

2018/02/20: The Case Against Google

2018/05/21: How Did Google Get so Big?

2018/07/18: Google Slapped a Record $5B for Android Antitrust Abuse! Thanks EU!

2018/07/18: Gary Reback, Legendary US Antitrust Lawyer Involved in Both Cases:

'On one hand, the EU deserves ... praise and credit for what they've done,' Reback said. 'But man, they only look good because we're totally absent.'

Kinda whenever Google's antitrust violations do expand its stalking abilities -- the FTC vanishes into thin air. Gone! A kind of magic, or what?

10) Captcha, Inc. Does Not Break
Antitrust Laws

While Google exposed itself to huge legal risks by breaking every rule in the antitrust book, in order to force-feed you Recaptcha the Stalker through the nose.

A 'captcha' product that:

  • has no known revenues; losing them a fortune each quarter; year after year.
  • does not work in China; and will break your website for everyone there.
  • might get you, and/or your users, sued over the 578 patent infringement in the US.
  • will drown you, or your users, in the murky legal waters of the post-GDPR EU.
  • is deliberately designed to be inaccessible; a no-no for the US Federal Agencies' sites.
  • and is broken so often and so thoroughly; that over the last ten years even Google itself mostly refused to use it.

That is weird, isn't it?

11) Captcha, Inc. Lives Off BotDetect License Sales

But where the Recaptcha money is coming from, in amounts large enough to justify taking the risk of breaking the antitrust laws, is a sort of mystery.

A cynic might ask you to pick your preferred scenario:

  • It does not come; and at some point Google will pull the plug on Recaptcha completely, as they did with Google Reader and other such products resting in the Google Graveyard.
    BotDetect Team: OK Google, that is called 100% enterprise-ready; a CIO's wet dream :).
  • Some undisclosed parties license the Stalker's data-feed and pay Google a fortune, and then some, so Recaptcha is actually profitable -- and the Stalker is watching you!
    BotDetect Team: OK Google, who are they? And, what do they use the data-feed for :)?

Which scenario do you prefer?

2018/03/19: Raleigh Police Went to Court ... And Got a Warrant Requiring Google to Share the Details of Any Users That Were Close to Crime Scenes During Specific...

'...the data haul is not limited to users of Google hardware i.e. phones running Android but also any phone that ran Google apps – which encompasses everything...'

GoogleBorg complied; and left us wondering if the list was sorted by name, immigration status, NRA card number, or just by sexual kinkiness.

Welcome to Surveillance Capitalism!

The moral of the story here is that once such a data-trove is allowed to exist -- even small town cops can figure out where the 'search box' is -- and, how to google it!

While the G-Men Knew It Since Forever:

FBI: https://tips.fbi.gov/ (since at least 2015)

Note that your details are 'optional' -- of course -- and, guess what 'captcha' is on the page :)?

Twist a bit that warrant mentioned above -- and get the 'details' of all the users who were on some Stalker armed site, during a specific time!

2017/04/19: If A Warrant Is Needed At All

We're spying on you for your own protection, says NSA, FBI • Except we're not, of course, because that would be illegal.

12) Captcha, Inc. Does Not Manipulate
the Captcha and Recaptcha Articles
on Wikipedia

Do you find it strange that as of 2018/03/26 the 'Security' section of the 'Recaptcha' article on Wikipedia has no Stalker's vulnerabilities listed that are less than five years old?

Which is actually an improvement -- because not that long ago, there weren't any listed there that were less than almost eight years old :).

It is not like no one was complaining that it looks like a Recaptcha marketing brochure -- exactly how the 'Captcha' article looked before the separate 'Recaptcha' article even existed.

Unfortunately, a truly independent review of all the IP addresses, entities, bots, and humans involved in all the edits of both 'Captcha' and 'Recaptcha' articles -- following both the money and the data-feed -- is still left to be desired.

Who is behind the Wikipedia issue?

But, there are other entities; far better adept at concealing their activities -- whose interest in the Stalker's data-feed cannot be overestimated -- who come to our minds as the primary suspects.
BotDetect Team: OK Google, that Wikipedia job -- was that you guys, or the G-Men's 'pals' :)?

Any favorites?

2017/01/13: TLS Channel IDs: Google's Crypto-Cookies are tracking Chrome users

'But if you use Chrome, your requests ... are no longer stateless. Google can follow you from one website to the next, without using conventional tracking cookies'

Depending if you're GoogleBorg or an user the English term for this would be akin to 'TokBind Stalking-capable (or vulnerable) browser' -- but the Googlish-for-suckers term 'more secure browser' is preferred and used by Google.

Tracking Users across the Web via TLS Session ResumptionACSAC 2018

'Google with its various hostnames is ... on nearly 80% of the Alexa Top 1M Sites...' / 'The largest shared TLS state within the ... Top 1k counts 84 sites and belongs to Google'

The Hamburg Uni study of TLS v1.3/v1.2 built-in stalking abilities and shared-TLS-state exploits!

Shared TLS state; on 80% of the Alexa Top 1M sites; with a ticket lifetime of 28hrs -- as just a part of the story! Hm, does it ring any bells :)?

Tracking Users across the Web via QUIC Session ResumptionPETS 2019

'...3rd-party ... can recognize users based on the token that the latter present during the 0-rtt connection attempt.' / 'a rejected 0-rtt handshake does not terminate a tracking period, because the server can link the...

QUIC, a Chrome-2-Google identity beacon, lets Google to stalk you w/o asking credentials, and w/o confirming identification. Brilliant, isn't it :)?

To make things worse, the upcoming HTTP/3 is supposed to use a QUIC-variant as a transport.

See the pattern emerging here. If a transport protocol was designed or influenced by Google
-- it has a stalking mechanism built in it. Ouch!

That Dual-use RFC & IETF Drafts of the NSA-Would-Not-Be-Ashamed-Of Class:

Step 1a - IETF Draft: TLS Channel IDs

Is that the original 'advanced risk analysis' :)?

Step 1b - IETF Draft: QUIC Transport Proto...

Since 2012. The IETF dates are misleading.

Step 2 - IETF Draft: TokBind Protocol v1.0

Were the third-parties (ab)used as fig leaves?

Step 3 - RFC 8446: The TLS Protocol v1.3

n-RTT; did the stalking sneak into the TLS v1.3?

2013/12/21: The BSafe 'Random' Made It

'...the NSA arranged a secret $10m contract with RSA, one of the most influential firms in the computer security industry...'

2018/04/25: But 'Simon' and 'Speck' Didn't

'That's when things seemingly turned nasty and the NSA started attacking the reputations of those experts who were advising against approving the standards.'

13) How Recaptcha Works? A Dummy's
Guide To 'Advanced Risk Analysis'!

A few things about Google are as annoying as their sense of antitrust impunity in the US -- but their firm conviction that the general public is 'just a bunch of suckers' is surely one of them.

'Tracking mouse movements - over the captcha widget,' and 'advanced risk analysis.' That is what they said about Recaptcha. Didn't they?

Very googlish; an absolute lack of respect; only the 'suckers' word is missing -- so the people can know what Google overlords think of them!


Consider the SCID & Source-address Token / n-RTT session resumption of the QUIC, PSK / n-RTT session resumption of the TLS v1.3, Session Ticket and SessionID session resumption of the TLS v1.2, cross-domain Shared TLS States, Token Binding, as well as TLS Channel IDs ways of user tracking.

Note that this isn't the final list yet! A few other protocols are still awaiting for the long overdue independent audits of their stalking abilities.

To simplify, we coined the temporary umbrella term TokBind Stalking to refer to both the list and the cryptological foundation under a part of it. While technically imperfect -- it suffices. Will it last or not depends on what will emerge later.


Their first try was the old 'Login by Google'; but both its name and users' affirmative actions required were the obvious 'shortcomings'.

Then TokBind converted it into something like 'Drive-by Check-in by Google'; or by a fair legal extrapolation: 'Involuntary Check-in by .......' -- fill in the blank!

An Identity + TokBind Stalking play!

When you open a Recaptcha-infested page -- spies weep. No need for the old-school browser fingerprinting; nor for the cookies; nor to click or type; nor for one of Google's sites in another tab -- nor, in some scenarios, even the Stalker itself has to fully load and execute.

As the stalking leapt from the app layer to the transport layer; your request of the Stalker's URL itself -- can now be that 'Check-In'. Got it?


Why they disguised it as a 'captcha'? We do not know; they do not stop by to confess -- did someone assess that such a disguise will let it stalk on the sites where no other tentacle can?

In that light, Google's nonsensical sense of antitrust impunity in the US might not be such an utter nonsense after all -- maybe they do have a deal of some sort indeed -- time will tell.

We can't wait to see Google's attempts to fit its TokBind Stalker-enabled mass-surveillance into a GDPR frame. It would be a hilarious comedy -- despite them never reaching a happy end.

The next time you hear our Google overlords bullshitting the terms like 'advanced risk analysis', 'tracking mouse movements', or 'more secure browser'; tell them to stick it; and where.
BotDetect Team: OK Google, six plus years, that's perseverance -- did the 'pals' offer help :)?

Did they?

2013/07/15: The Crux of the NSA Story: Gen. K. Alexander Wanted to Slurp It All

'Collect it all, tag it, store it. ...And whatever it is you want, you go searching for it...'
'...Gen. Keith B. Alexander, wanted more than mere snippets. He wanted everything...'

2014/09/16: U.S. Government to Yahoo: Comply with PRISM, or ... Go Bankrupt

'...threatened to fine Yahoo $250k/day...' / '... doubled each week until Yahoo complied.'

2013/06/07: Snowden Files: NSA PRISM Taps Into Apple, Google and Others

'The NSA has obtained direct access to the systems of...' / 'Google ... in 2009; YouTube in 2010; and finally Apple ... in 2012.' Slides!

2019/03/12: Senate Judiciary Committee: J. Hawley (R-Mo.) vs. Google's Will DeVries

'Do you think an average consumer ... fully understands Google builds a profile about her ... tracks where her boyfriend lives...'

'Americans have not signed up for this. They think that the products ... are free. They're not free. They think they can opt out of the tracking that you're performing. They can't meaningfully opt out.' / 'Btw, this is just the phone. We're not even talking yet about Search or Internet tracking,' Hawley said.

2019/04/13: Google's Donkey-run Dragnet Made the NSA Keith Look Amateurish

In Arizona ... police received data six months after...' / 'In a different Minnesota case ... it came in four weeks' / 'Sensorvault ... includes detailed location records involving at least hundreds of millions of devices worldwide and dating back nearly a decade.'

Slurp it all -- that modus operandi sounds so familiar! Google wants you to understand that a decade old data is a perfect fit for 'advertising' -- but that googling it is slow coz the data is sifted through by donkeys -- what can take a while :)

2018/03/31: The Trump Administration: US May Tie Social Media to Visa Applications

'Applicants would also be asked for five yrs of their phone numbers, emails, and travel history.' / 'the US state department proposal could affect around 14.7m people a year'

Five years of phone numbers, email addresses, and travel history; 14.7m times a year -- what a strange coincidence! No way that the submitted info will be cross-checked against the Google's Sensorvault data -- Google just can't have that many donkeys :). That policy went live, btw.

2018/04/19: But Unlike Google's Donkeys, the NSA Keith Was Aware of Palantir

'When whole communities are algo-scraped for pre-crime suspects, data is destiny' / 'One woman in the system, for example, who wasn’t suspected of committing any crime, was identified as having multiple bfs'

Stay mum! Google shouldn't know about this :)

2019/03/04: How Google got away with it?

'The rhetoric of the pioneering surveillance capitalists, and just about everyone who has followed, has been a textbook of misdirection, euphemism, and obfuscation.'

2013/06/10: PRISM Exposed: Data Surveillance with Global Implications

Gus Hunt, the CIA's CTO, made a forthright admission in March: 'We fundamentally ... collect everything and hang onto it forever.'

14) Captcha Isn't a Part of PRISM. How
about Recaptcha; and its data-feed?

One might argue that as a US company Google didn't have a legal way to avoid becoming a part of PRISM. Well, neither Apple had -- but that is the point where all the similarities end.

Confronting the reality, Apple went into 'what happens on your iPhone, stays on your iPhone' mode; slurping the least they can. No law can force them to provide the data they did not get!

While Google was opportunistic -- there were synergies. With a NSA implant sticking out of its back -- it morphed into an obsessive stalker -- and went on a data-slurping perma-spree!


The English is an amazing language; see this:

If one, by the undisclosed means, meticulously collects the data about a dozen officials of a particular country; their friends, family, health, finances, locations, sex lives, what they wrote, read, or said, etc -- that is called 'espionage.'

But, if one, by the same undisclosed means, meticulously collects the same data about the entire population of that country; including the same officials, their friends and family -- that is called 'advertising'. It is amazing, isn't it?

And then, if by the same means, one collects the same personal data about everyone in your own country; to the level that one has the data where your teenage daughter's bf lives; and, with whom, when, and where she had one night stands -- that is also called 'advertising'. Is it :)?


Our Google overlords like to crap about privacy & 'organizing the world's information'; but what they made stinks a hell lot as the world's first publicly-traded signal intelligence organization.

Regardless, on 2019/05/07, the Google's CEO, Sundar Pichai; who presides over the Android and the TokBind Stalker; a nation-state class mass-surveillance technologies; volunteered to show off his Googlish-for-suckers at its finest:

'Privacy cannot be a luxury good offered only to people who can afford to buy premium products and services. Privacy must be equally available to everyone in the world.'

Sundar, with skin thick enough to withstand an arrow, was so confident that in no time -- he will be done placating 'that bunch of suckers'. Wow!

No one told him that that train is gone :)

His first sentence is a distraction; ostensibly a salvo aimed at Apple; while in fact the magician just drew your attention toward irrelevant stuff.

The English translation of his second sentence would be akin to: 'The privacy from Google [and the 'pals'] will not be given to anyone.'

He did not offer the privacy from Google at all; and privacy is equally available if it is not given to anyone. You see, he was not lying -- shame on you for getting it all wrong! Skillful, right :)?

Still, a due credit should be given.

Aside from making the world's first listed sigint agency ever, our Google overlords managed to take corporate doublespeak to a completely new, language-dialect level -- all while enriching themselves immensely in the process. Neat!


However, it won't enrich your teenage daughter.

Does her bf have all that info? No! Do you? No! With the reason -- it is none of your business!

But, Google think that teens' one night stands are their business -- and, they got the data!

Now, sit down and guess -- who will make sure to have a copy? Forever! Got it?

Hence, it might be wise to sit her down; and, gift her an iPhone -- while carefully explaining how the English language works -- with an emphasize on its Googlish-for-suckers dialect peculiarities!


Captcha, Inc and BotDetect CAPTCHA have nothing to do with the NSA PRISM. How about Google Recaptcha -- and its data-feed? Btw, just imagine Sundar's stand-up gig on the topic :)
BotDetect Team: OK Google, was Keith learning from you guys -- or you learned from him :)?

Think for yourself!

.