Short version: DevRegex runs entirely in your browser. We store no personal data, use no cookies, run no analytics, and track nothing. The only network request DevRegex ever makes is when you use the optional Share feature — and even then, your content is AES-256-GCM encrypted before it leaves your device.
DevRegex is a free online regular expression tester operated by DevStudioAl (devstudioal.com). When this policy says "we", "us", or "our", it refers to DevStudioAl.
If you have any questions about this policy, contact us at: [email protected]
DevRegex is a fully client-side application. This means:
The DevRegex server does only one thing: deliver the HTML, CSS, and JavaScript files to your browser. After that initial load, your browser does all the work independently.
The following table describes every category of data we handle:
| Category | Details | Stored by us? |
|---|---|---|
| Regex patterns | Processed locally in your browser | Never |
| Test strings | Processed locally in your browser | Never |
| Substitution text | Processed locally in your browser | Never |
| Unit tests | Processed locally in your browser | Never |
| Share content | AES-256-GCM encrypted before leaving your device — forwarded to DevPaste. We cannot read it. | Encrypted ciphertext only, on DevPaste |
| IP address | Seen by the web server when delivering files (standard HTTP). Not stored in any database. | Not stored |
| Cookies | None set, none read | Never |
| Analytics / telemetry | None implemented | Never |
We do not store your name, email, browser fingerprint, device ID, location, or any identifier linked to you personally.
DevRegex includes an optional Share feature that lets you share your regex, test string, substitution, and unit tests via a link. Here is exactly how it works:
The Share feature is entirely optional. If you never click Share, no data of any kind leaves your browser beyond the initial page load.
Share links are stored on DevPaste and subject to DevPaste's Privacy Policy. Links expire automatically (DevPaste default expiry applies).
DevRegex loads fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). When your browser requests a font file, Google may receive your IP address and browser User-Agent as part of the standard HTTP request. This is governed by Google's Privacy Policy.
No other external resources are loaded. DevRegex has no social media buttons, embedded iframes, third-party scripts, CDN-hosted JavaScript, or external API calls beyond Google Fonts and the optional Share feature.
The following technical security controls are in place for DevRegex:
If you are located in the European Economic Area (EEA), you have rights under the General Data Protection Regulation (GDPR), including the right to access, correct, erase, restrict, or port your personal data.
In practice, because DevRegex stores no personal data and has no user accounts, there is nothing for us to access, modify, or delete on your behalf. Your regex activity never reaches our server — it exists only in your browser.
To exercise any GDPR rights or raise a concern, contact us at [email protected].
If you are a California resident, the California Consumer Privacy Act (CCPA) grants you rights regarding your personal information. Because DevRegex does not collect, sell, or share any personal information, there is no personal information to disclose, delete, or opt out of selling.
We do not sell personal information. We do not share personal information with third parties for cross-context behavioral advertising.
DevRegex is not directed at children under the age of 16. We do not knowingly collect any personal data from children. Since we collect no personal data from any user, we collect none from children either. If you have concerns, contact us at [email protected].
We may update this Privacy Policy from time to time. Changes will be reflected by an updated "Last updated" date at the top of this page. Continued use of DevRegex after a change constitutes acceptance of the updated policy. We will not make changes that reduce your privacy rights without clearly communicating those changes.
For any privacy-related questions, requests, or concerns: