Privacy Policy
Effective date: April 15, 2026 — Last updated: April 15, 2026
1. Who We Are
RegexPro is a product of Abel Solutions LLC, a limited liability company organized under the laws of the State of Minnesota, USA. This Privacy Policy describes how we collect, use, and protect your personal information when you use RegexPro at regexpro.dev.
2. Data We Collect
We collect the following categories of information:
Account Information
When you sign in with Google via Auth.js, we receive your email address and display name from Google. We store your email to identify your account and associate your saved patterns and subscription with you.
Saved Patterns & History
Pro users can save regex patterns and access pattern history. This content is associated with your account and stored in our database.
Billing Information
If you subscribe to Pro, your payment details are collected and processed directly by Stripe. We do not store your credit card number or full payment information on our servers. We receive a Stripe customer ID and subscription status from Stripe.
Usage Data
We may collect technical usage data such as pages visited, features used, error events, and general interaction patterns. This data helps us improve the Service and diagnose technical issues.
3. How We Use Your Data
We use the information we collect to:
- Provide, maintain, and improve the Service.
- Authenticate your account and maintain your session.
- Process payments and manage your subscription via Stripe.
- Associate saved patterns and history with your account.
- Diagnose and fix technical errors.
- Communicate with you about your account or subscription when necessary.
We do not use your data for advertising or sell it to third parties.
4. Third-Party Services
We work with the following third parties who may process your data as part of providing the Service:
Stripe
Payment processing. Stripe collects and processes payment information on our behalf. Your payment data is governed by Stripe's Privacy Policy.
Sentry
Error monitoring. Sentry captures application errors to help us diagnose and fix issues. Error reports may include technical context such as browser type, page URL, and stack traces.
Vercel
Hosting and infrastructure. The Service is hosted on Vercel's platform. Vercel may process standard web request data (IP address, request headers) as part of serving the application.
Google (Auth.js)
Authentication. If you sign in with Google, Google provides your email and display name to our application. Your use of Google Sign-In is governed by Google's Privacy Policy.
5. We Do Not Sell Your Data
We do not sell, rent, or trade your personal information to third parties for their own marketing or commercial purposes. Data shared with third parties listed above is solely for the purpose of operating and improving the Service.
6. Data Retention
We retain your account data and saved patterns for as long as your account is active. If you request account deletion, we will delete your personal data within a reasonable timeframe, subject to any legal obligations to retain certain records (e.g., billing records for tax and compliance purposes).
7. Your Rights
You have the right to:
- Request a copy of the personal data we hold about you.
- Request correction of inaccurate personal data.
- Request deletion of your account and associated personal data.
- Withdraw consent where processing is based on consent.
To exercise any of these rights, contact us at support@regexpro.dev. We will respond within a reasonable timeframe.
8. Cookies
We use session cookies to maintain your authentication state. These cookies are necessary for the Service to function and are set by Auth.js when you sign in. We do not use tracking cookies or third-party advertising cookies.
You can disable cookies in your browser settings, but doing so will prevent you from staying signed in to your account.
9. Governing Law
This Privacy Policy is governed by the laws of the State of Minnesota, USA. If you have concerns about our data practices, you may contact us directly or, where applicable, lodge a complaint with a relevant data protection authority.
10. Changes to This Policy
We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page. We encourage you to review this policy periodically. Continued use of the Service after changes are posted constitutes acceptance of the revised policy.
11. Contact Us
If you have questions or concerns about this Privacy Policy or our data practices, please contact us at: