Privacy
This page explains the intended handling model for code submitted to the online obfuscator and the role of standard operational logging.
Code submitted through the obfuscation form is processed to generate output for the current request. If you later add analytics, storage, or logging around request bodies, this policy should be updated to reflect that operational reality.
The application may write internal error details to server logs for debugging and operational safety. Sensitive production environments should keep those logs access-controlled.
This site should avoid unnecessary third-party scripts for an obfuscation workflow. If third-party analytics or external media are added later, they should be disclosed here.
If this site is deployed publicly, access logs, error logs, backups, and any analytics tooling should be reviewed to confirm they do not retain sensitive request content longer than intended.