Security
Vulnerability Disclosure Policy
CoreValueTec, Inc. makes RedactIQ. We welcome reports of security vulnerabilities from anyone, and we want to hear about anything you find.
How to report
Email security@corevaluetec.com. Tell us what you found, where, how to reproduce it, and what you think an attacker could do with it. You may report anonymously. Please don't share the details publicly until we've fixed the problem.
What we promise
- We acknowledge your report within 3 business days.
- We give you an initial assessment within 10 business days, and keep you informed until it's resolved.
- We fix confirmed vulnerabilities within 14 days if they are known to be exploited (they appear in CISA's Known Exploited Vulnerabilities catalog), 15 days if Critical in an Internet-facing service, 30 days for other Critical and High findings, 90 days if Moderate and 180 days if Low.
- We credit you for the discovery if you'd like.
Authorization
If you make a good-faith effort to follow this policy, we consider your research authorized. We will work with you to understand and fix the problem quickly, and we will not recommend or pursue legal action related to your research. If anyone else takes legal action against you for research that followed this policy, we will make it known that your research was authorized.
Scope
The RedactIQ software, including its source code and releases, and this website. Our customers run RedactIQ in their own environments: test a customer's installation only with that customer's permission, and report flaws in the software to us.
Guidelines
- Tell us as soon as you find a possible vulnerability.
- Avoid privacy violations, harm to users, disruption of systems, and destruction or change of data.
- Use an exploit only as far as needed to confirm the vulnerability. If you reach someone else's data, stop, tell us, and don't keep it.
- Give us reasonable time to fix the problem before you disclose it; we ask for 90 days.
Not allowed
- Denial-of-service testing, social engineering (including phishing), and physical testing.
- Testing systems you don't own or have permission to test.
First published October 2, 2026. Machine-readable contact: security.txt.