Back to Hub

Privacy Policy

This policy describes how tool inputs, aggregate analytics, and site resources are handled.

Tool-input processing

Core transformations for OpsecForge's sanitizers, formatters, encoders, decoders, and generators run in the loaded browser page unless a tool explicitly states otherwise.

  • Local execution: Tool input is processed in browser memory and is not submitted to an OpsecForge processing API.
  • No tool-input database: OpsecForge does not store user-pasted tool content in a backend database.
  • No input-level analytics: Tool input and generated output are not included in analytics events.

Analytics and advertising

OpsecForge uses Vercel Analytics for aggregate page-view measurement. Those events do not include tool input or output. At the time of this update, OpsecForge does not serve advertisements or load the AdSense ad-serving script. The public ads.txt file and publisher meta tag are ownership-verification signals; they do not by themselves display ads. This policy will be reviewed before advertising is enabled.

Contact

For questions about our privacy commitment, please contact us at admin@opsecforge.com.

Last Updated: August 21, 2026.