← DevTools/📖Documentation
🔍 Verify🧰 Workbench

Privacy, local processing and sharing

Everything runs in your browser. What is never put in a share link, how fields are classified, and what an export contains.

🔒

Privacy & local processing

LIVE

Parsing, formatting, hashing, comparison and every verifier run entirely in your browser. The only tool that makes a network request is APITester, and only for the request you explicitly send.

How your input is classified

  • Safe — public regex patterns, cron expressions, formatting preferences, colour values. May be serialized into a share URL.
  • Sensitive — JSON payloads, API responses, request bodies, URLs with identifiers, .env key names. Withheld from a share URL unless you explicitly opt in.
  • Secret — JWTs and their signing secrets, Authorization headers, cookies, webhook signing secrets, .env values, generated passwords. Never serialized into a URL, never included in Copy Findings, never sent to analytics — there is no option that changes this.

Analytics

Product events carry categorical properties only — a tool id, a mode, a verdict, a finding count, whether the input was a built-in fixture. Artifact content, tokens, URLs, headers, regex test data and request bodies are filtered out by an allow-list before any event is sent, and the filter is covered by tests.

🔗

Sharing safely

LIVE

Every verifier has a Share result action next to the verdict. What it copies depends on what your input contains.

1

Safe state copies immediately

A cron expression, a regex pattern or a formatting preference goes straight into the URL. Existing share links keep working — the parameter names have not changed.
2

Sensitive input asks first

If the link would carry your artifact, a dialog opens with two options. The default is Share findings only: the link reproduces the verdict and the evidence at /verify?r=… without the artifact itself.
3

Secrets are never included

Tokens, signing secrets, Authorization headers, cookies and .env values are stripped before the URL is built, on every path, whichever option you choose. Automated tests fail the build if a seeded secret marker ever reaches a generated URL.
4

Long links degrade gracefully

If a link would exceed the length browsers and chat clients truncate at, the largest sensitive fields are dropped and the confirmation says so — rather than handing you a link that breaks when pasted.
🔗

Share & Export

Every tool encodes its state in the URL. No account needed to share your work.

URL sharing

When you use any tool, the URL updates automatically with your current state. Copy the URL from your browser and share it. Your recipient opens the same tool in the same state — pattern loaded, test text included, flags set.

URL format
RegexLab:
      /tools/regexlab?p=%5Ed%7B3%7D&f=g&t=123-456-789

    CronBuilder:
      /tools/cronbuilder?cron=*/5+*+*+*+*

    Parameters:
      p  = URL-encoded regex pattern
      f  = flags (g, i, m, s, u, y)
      t  = URL-encoded test text
      cron = cron expression

Code export

RegexLab generates working code snippets in 4 languages:

JavaScript
const regex = /^\d{3}-\d{3}-\d{4}$/g;
    const matches = text.match(regex);
Python
import re
    pattern = r'^\d{3}-\d{3}-\d{4}$'
    matches = re.findall(pattern, text)
PHP
$pattern = '/^\d{3}-\d{3}-\d{4}$/g';
    preg_match_all($pattern, $text, $matches);
Go
re := regexp.MustCompile(`^\d{3}-\d{3}-\d{4}$`)
    matches := re.FindAllString(text, -1)

DevTools by Hakeemify — 16 tools live

PricingTermsPrivacySecurityContact← All tools