OpsecForge FAQ
Verifiable boundaries for local processing, analytics, assurance, and tool output.
Data privacy and local processing
Does OpsecForge receive the text I paste into a tool?
Core tool inputs are processed in the loaded page and are not sent to OpsecForge analytics or a tool-processing backend. The site does use aggregate page-view analytics and may load advertising resources.
Can I inspect the implementation?
Yes. The public repository and browser developer tools let you inspect the implementation and network activity. Review the exact tool you plan to use; public source is evidence, not a substitute for your own security assessment.
Can I use a loaded tool while disconnected?
Core transformations are designed to run in the browser after the required page assets have loaded. Advertising, analytics, navigation, fonts, or a fresh page load may still require network access, so OpsecForge does not claim complete offline availability for the whole site.
Assurance and compliance
Does browser-local processing make a workflow compliant?
No. It reduces one data-transfer path, but compliance depends on your organization, data, jurisdiction, controls, retention, vendors, and documented procedures. OpsecForge does not claim GDPR, ISO 27001, or SOC 2 certification.
What should I review before using a tool for sensitive work?
Check the tool limitations, inspect network activity, use synthetic data first, and follow your organizationās approved software and data-handling policies. Do not paste a production secret merely to test whether a redactor detects it.
Tool limitations
Does decoding a JWT prove that it is valid?
No. Decoding only reveals the token structure. Validity depends on cryptographic verification, the expected issuer and audience, relevant time claims, key selection, and application policy.
Does Env Sanitizer make a file safe to share?
No automated redactor can prove that. Env Sanitizer heuristically masks common patterns and may miss unusual secrets or flag benign text. Review every line of the result and prefer synthetic placeholders.