This tool use random numbers to hide your text from search engines finding your internet activity. It has been deployed online:

• https://hide-text.com/ (Official Domain)
• https://hide-text.vercel.app/ (Original deployment URL, fully compatible)

Both domains point to the same project. Any existing links created using the Vercel domain remain fully functional.

Use Case

Suppose your email address is “my_special_name@example.com”.

You can use hide-text.com to generate multiple random addresses:

• https://hide-text.com/?c=F0ouRxQuBlwbXy5aBSYAdR9LEFkUJwAbGVwc&k=z3q4dKe5 (Random Address A)
• https://hide-text.com/?c=GAMzNCMLCgYUFjMpMgMMLxACDSojAgxBFhUB&k=uzlGSnio (Random Address B)

Clicking on any of these distinct random addresses reveals your actual address: “my_special_name@example.com”.

You can post “Random Address A” on Sub-A and “Random Address B” on Sub-B.

Scenario 1: The random address cannot be retrieved from your real email address

If someone searches for your real email address—”my_special_name@example.com”—on Google, they will not see the “Random Address A” you posted on Sub-A.

This is because your real email address was not made public on Sub-A, and Google does not link “Random Address A” to your real email address.

Scenario 2: A leak of one random address does not expose the other

If someone learns of “Random Address A” and searches for it on Google, they will only see the record you left on Sub-A. They will not be able to discover “Random Address B,” which you posted on Sub-B.

This is because it is impossible to derive “Random Address B” from “Random Address A.”

Privacy

HideText is designed with a privacy-first approach. All text processing is performed entirely within your web browser.

For more details, please see our full Privacy Policy.

How HideText Works: XOR + Base64

HideText uses two simple steps to turn readable text into URL-safe, random-looking links.

XOR — reversible transformation

XOR (exclusive OR) has a useful property: (A XOR B) XOR B = A.

Example:

• Plaintext: HELLO
• Key: 12345
• HELLO XOR 12345 → u8#kP // get ciphertext
• u8#kP XOR 12345 → HELLO // restore plaintext

XOR makes text look random but can be recovered with the same key.

Base64 — make data URL-friendly

The XOR result is arbitrary bytes and may include characters that break URLs (for example a+b/c=d). Base64 (or URL-safe Base64) converts those bytes into URL-safe characters.

Example:

• Raw: a+b/c=d //will break URL
• URL-safe Base64: YS1iL2MrZA //URL-safe
• Link: https://hide-text.com/?c=YS1iL2MrZA

Summary

XOR obscures content; Base64 makes the result safe for URLs. Together they produce many different links that reveal the same original text when the correct key is provided.

URLs can carry sensitive data. HideText uses two simple, practical measures so those links don’t become searchable.

1) HTTP-level noindex

• When a URL contains a ciphertext parameter (?c=), the server adds X-Robots-Tag: noindex, nofollow to the response header.
• This tells crawlers not to index the URL before they parse the page, which is more reliable for parameterized links than an HTML meta tag.

2) Canonical pointing

• Each ciphertext page includes a <link rel="canonical" href="https://hide-text.com/">.
• Crawlers are instructed to treat the encrypted URL as part of the main site, preventing separate indexing or ranking for each random link.

Summary

• Random links are not indexed: URLs containing ciphertext parameters (for example ?c=...) are prevented from being indexed and should not appear in search results.
• The domain is indexed: The root site (https://hide-text.com/) remains indexable and will be treated normally by search engines.
• Practical effect: You can create many random-looking links that reveal the same content without creating searchable traces.

To verify the tool’s effectiveness in preventing search engine indexing, we compare search results to demonstrate that—while the page itself is indexed—the random links within it are not, and the sensitive content contained within those random links remains invisible.

Experimental Steps

1. Provide a publicly crawlable page, such as this blog post.
2. Place Marker A on the page: a unique plain-text string that Google will naturally index.
3. Place Marker B on the page: a random link generated by HideText from a piece of sensitive content.
4. Wait 1–2 weeks to allow search engine crawlers (such as Googlebot) to crawl and index the page.

Verification Steps

1. Search for Marker A; this should return this blog post. This proves the page has indeed been indexed.
2. Search for Marker B; this should return zero results. This proves that search engines ignore this random link.
3. Search for the sensitive content hidden within the random link; this should return zero results, proving that the tool effectively hides the content.

Test Data

Marker A: Plaintext_237495434

Marker B: https://hide-text.com/?c=GlwbESIQASIsagEQIgoPC30LQVV4UVpjeg1C&k=I9ubKdhT (Clicking this random link will reveals the sensitive content)

1. Client-Side Only: This is a purely static webpage. The encryption and decryption happen entirely within your browser memory. Your plaintext is never transmitted to, or stored on, any server.
2. Zero Data Footprint: There is no backend database, no sessions, and no cookies. We do not use any third-party tracking or analytics scripts (like Google Analytics).
3. Link-Based Security: All encrypted data and the decryption key are contained within the generated URL. Privacy is maintained as long as you keep the link secure.
4. Anti-Indexing: The application uses noindex and canonical tags to instruct search engines not to index or display the ciphertext URLs in search results.
5. Open Source: Our code is fully transparent and available for public audit, ensuring no “backdoors” or hidden data leaks.