Privacy Policy
Thank you for visiting our web site. This privacy policy tells you how we use personal
information collected at this site. Please read this privacy policy before using
the site or submitting any personal information. By using the site, you are accepting
the practices described in this privacy policy. These practices may be changed,
but any changes will be posted and changes will only apply to activities and information
on a going forward, not retroactive basis. You are encouraged to review the privacy
policy whenever you visit the site to make sure that you understand how any personal
information you provide will be used.
Cookies
Browsing this site sets no cookie at all. We do not use advertising, profiling or cross-site tracking cookies, and there is no analytics tag on these pages.
Three cookies exist, and only when you do something that needs one. Signing in sets JSOv2Auth, the authentication cookie that keeps you signed in; it is removed when you sign out. Requesting a verification code sets CheckCode for the life of that request. The live chat widget, which appears on every page, sets its own anonymous identifier on mylivechat.com so a conversation survives moving between pages; MyLiveChat is operated by Richscripts Inc., the same company that operates this site, so no data leaves our organization. None of these is linked to your browsing history.
Do you keep my JavaScript source code?
Submitted JavaScript is used only to fulfill the obfuscation request you make. If you paste code into the online tool, it is sent to the server so the obfuscated output can be generated and returned to you. If you upload a file, the upload stream is read for processing and the temporary upload file is removed after completion.
If your workflow requires fully local handling of source code, use the desktop application instead of the online obfuscator.
Which workflow should I use?
The online obfuscator is intended for quick evaluation, lightweight scripts, and one-off jobs. WinUI Local Standard keeps basic ES5 .js offline. Paid WinUI Local Advanced keeps modern .js/.jsx and mixed HTML/server-script source on the workstation after a source-free online entitlement check. Windows Forms and WinUI hosted mode send selected JavaScript to the service, as does the npm CLI unless it is run with --local; VM bytecode remains hosted-only, and the protection report is written on the workstation.
Information Collection, Use, and Sharing
We are the sole owners of the information collected on this site. We only have access to/collect information that you voluntarily give us via email or other direct contact from you. We will not sell or rent this information to anyone.
We will use your information to respond to you, regarding the reason you contacted us. We will not share your information with any third party outside of our organization, other than as necessary to fulfill your request, e.g. to ship an order.
Unless you ask us not to, we may contact you via email in the future to tell you about specials, new products or services, or changes to this privacy policy.
Privacy Contact Information
If you have any questions, concerns, or comments about our privacy policy you may
contact us using the information below:
By e-mail: [email protected]
We reserve the right to make changes to this policy. Any changes to this policy
will be posted.