Encrypt
Send a short value to the existing encrypt endpoint and receive an opaque value.
A small privacy utility
Let people read it.
Give scrapers a speed bump.
Sorta Secret requires a valid reCAPTCHA token before revealing semi-secret text—useful for sharing an email address without publishing it as easy-to-collect plaintext.
Live demo
A message behind the check
Protected text
Hidden until the token check
The service checks for a valid Google reCAPTCHA token.
How it works
A speed bump for scrapers, not an access-control system.
Sorta Secret encrypts a short piece of text for embedding on a public page. When a visitor asks to reveal it, the service checks whether the submitted reCAPTCHA token is valid before returning the plaintext.
That adds friction to automated collection, but it does not make the text private. The current service does not evaluate reCAPTCHA v3 score, action, or hostname, and a determined scraper may still succeed. Do not use Sorta Secret for passwords, credentials, private keys, or information that needs authorization.
Embed
Place that value in your page and load the Sorta Secret script.
Reveal
A visitor's browser obtains a reCAPTCHA token before the service returns the text.
Use the API
The original routes remain available.
Create an encrypted value with /v1/encrypt?secret=…, or open a complete reveal page with /v1/show?secret=… using that encrypted value.
Because the create endpoint accepts plaintext in the URL, browsers, proxies, and logs may retain it. Use only text that fits the semi-secret threat model described above.