WebEXE icon WebEXE.cc

WebEXE privacy policy

Understand the information involved in app creation and launch, its purposes and privacy considerations.

1. Scope

This policy explains how information is handled when you visit WebEXE.cc, create and download Windows apps with HTML to EXE Converter, and when those apps send launch events to the website. Third-party services in your pages and features offered by downloaded apps may have separate privacy notices.

2. Information we process

  • Web pages and supporting files: When you submit a request, selected HTML, entered HTML or pages, images, styles and other project files are uploaded to create the app.
  • App settings: These include the app title, window width and height, and file type information needed for creation.
  • Order records: These include the order number, a randomly generated app identifier (app_id), creation time, status, download file name and related app settings.
  • Request source: Creation orders record the request IP address and browser identification (User-Agent) to troubleshoot creation issues and understand the request source.
  • Generated app launch events: Apps with an app identifier send one launch event to WebEXE.cc each time they start. On receipt, the website records the app identifier, launch event, receipt time, request IP address and client identification (User-Agent). Being offline or a failed request does not prevent opening the app. Older results without an app identifier do not send this request.

Review your project before uploading. Remove passwords, private credentials, sensitive personal information and material unsuitable for sharing. Submit only content you are authorized to use and process.

3. How information is used

Web files and settings are used to create apps and generate and provide downloads. Order records and request source information help verify results, handle feedback and troubleshoot issues. Generated apps contain your submitted content; confirm it is suitable for sharing before distribution.

Launch records help understand app launches, link them to creation orders and troubleshoot usage. Events contain no web page content and do not record clicks or input within pages. Received launch counts are not unique user counts. Explain launch-event data processing to users when distributing apps.

4. File and record retention

The website stores generated ZIP downloads and order records to provide results and troubleshoot issues. Web content is included in the app inside the package, so protect the download according to the sensitivity of the original project.

Information is kept as needed for creation, downloads and troubleshooting. No fixed automatic deletion period for ZIP files or order records is currently published. Download and back up results promptly; links are not long-term storage.

App launch records are stored as separate daily text logs to summarize launches and troubleshoot issues. No fixed automatic deletion period for launch logs is currently published.

Keep order numbers and download links private and do not share them with unrelated parties.

5. Browser storage

The website stores a random visitor identifier and whether a language suggestion has been shown in browser local storage. This distinguishes the current browser and avoids repeated prompts. You can clear site storage in browser settings; a new identifier or language prompt may then appear.

6. External resources and links

Pages may load public resources from external services and link to third-party websites. Those providers may receive your IP address, browser details and other connection data and process them under their own policies. Online images, external services and other connected content in uploaded pages are also subject to their providers’ rules.

7. Security and user requests

Network transmission and storage cannot be guaranteed risk-free. Keep backups, share results carefully and do not include passwords or other secrets in pages or apps intended for distribution.

For questions or data-processing requests, use the communication channel through which you obtained this service. Provide the order number, creation time and request details so records can be verified. Do not include passwords or complete sensitive files. Learn about the website on the About us page.

8. Policy updates

This page will be updated when features or data handling change. Before creating an app, review this policy and the terms of service. For creation and usage questions, see the FAQs.