Privacy Policy

Welcome to Web To APK Builder & Monetize ("we," "our," or "us"). We are committed to protecting your privacy. This Privacy Policy explains how we handle your data when you use our application. By utilizing our services, you agree to the practices described in this document.

1. Data Minimization & Authentication

To ensure maximum privacy and minimize data footprints, we strictly enforce the following:

• Optional Sign-In: You can use the core builder anonymously as a guest by default. We offer an optional Google Sign-In (powered by Firebase) for seamless session and subscription management. You retain full control, including a 1-click "Delete Account" feature inside the app's Account Menu to instantly erase your profile data. For a step-by-step visual guide on how to securely delete your account, please watch our video tutorial. For more details on how Firebase secures authentication data, visit Firebase Privacy Support.
• Source Code Security: Whether you provide a public URL or upload an Offline HTML5 App (.zip), we do not permanently host, read, or distribute your source files.

2. Resource Allocation, Usage Limits & Server Protection

While our core features are available to all users anonymously, compiling Android applications is a highly resource-intensive process. To maintain server stability and prevent abuse, we implement tiered restrictions and strict fair-use policies:

• Guest (Anonymous): File uploads (.zip) are limited to 5MB. Mobile IDE Editor is limited to 3 Projects. Compilation is restricted to generating Debug APKs only.
• Signed-In (Free Account): File uploads (.zip) are increased to 10MB. Mobile IDE Editor is increased to 10 Projects. Unlocks the ability to generate both Debug APKs and Release Builds (APK/AAB).
• PRO (Premium Subscription): File uploads (.zip) are expanded to 50MB. Mobile IDE Editor is expanded to 50 Projects. Full access to all builds alongside advanced monetization configurations.
• Server Protection Rules: Our service strictly operates on a 1-User-to-1-Device rule. Any attempts to overload our builder servers, including DDoS attacks, the use of auto-clickers, multi-device abuse, or generating abnormal automated traffic, will result in an automatic block (temporarily or indefinitely) without prior notice.

3. Data Collection, Cloud Storage & Offline Usage

We temporarily process minimal data strictly required to deliver our core functionality. It is important to understand how and where your data is stored:

• Device Identifier & UID: We use an anonymous Device ID or a secure Firebase UID (if signed in) to securely link your device to your build session.
• Cloud Storage (Builder App Configs): Your basic App Configurations (JSON object data and app icons) are synced to our Cloud storage if you are signed in. This data can also be downloaded and re-imported manually as a ZIP backup.
• 100% Offline Storage (Mobile IDE Code): Source code written inside the Mobile IDE code editor is saved strictly locally on your device's memory (LocalStorage/IndexedDB). Warning: This local data will be permanently destroyed if you uninstall the application, clear app data, or use the "Delete Account" feature.
• Source Inputs: The URL or .zip file you provide is solely used by our server engine to compile the Android container.

4. Cloud Data Access (Google Drive & Dropbox Backups)

To prevent local data loss, we offer an optional 1-Click Cloud Backup feature for your Mobile IDE Projects, Keystore files (.jks), and Keystore Metadata (.txt). If you choose to authenticate and link your Google Drive or Dropbox Account, you must explicitly grant us permission to use their respective APIs. Our application enforces strict boundaries regarding this access:

• Restricted Scope Constraint:
  • Google Drive: We strictly request the drive.file scope. This means our application can only access, edit, create, and delete files that were created by our app itself.
  • Dropbox: We utilize the highly restricted "App Folder" access architecture. Our application can only see and modify files isolated within its own specific folder (Apps/Web To Apk Builder/).
• Zero Personal Data Access: We categorically cannot access, read, search, or modify any of your existing personal photos, documents, or other files stored outside the scope of files created by our app in your Google Drive or Dropbox.
• Direct Client-to-Cloud Architecture: Your project source code and Keystore backups are transmitted directly from your mobile device's memory to your personal cloud storage accounts via REST API. We do not intercept, cache, host, or process your backups on our backend servers.
• Secure Native Browser Flow: When authenticating your cloud accounts (e.g., Dropbox), the app launches your device's native system browser (Chrome/Safari) using a secure backend relay. This ensures that you authenticate directly with the provider, protecting your credentials in full compliance with modern security guidelines.
• Ownership & Revocation: You retain 100% ownership of your backup files. You can manage or revoke our app's access at any time via your Google Account Security Settings or your Dropbox Connected Apps Settings.

📘 Feature Documentation: For a detailed visual guide on how this backup and restore functionality operates within our application, please refer to our Mobile IDE Editor Documentation.

5. Data Destruction & Immediate Purge Policy

Security and data minimalization are our top priorities. All processing occurs on secure Cloudflare R2 Storage environments. We enforce strict deletion protocols:

• Immediate Source Purge: Uploaded .zip source files, Target URLs, and uploaded Keystore (.jks) files used for signing are governed by ultra-strict rules. They are instantly and permanently destroyed the exact moment your build process finishes (regardless of whether it succeeds or fails). You can verify this action in your build terminal via the system log: "Source file Cleanup process completed."
• Generated Artifacts (1-Hour Rule): All compiled APKs, AABs, and newly generated Keystore files (created via our "Create Keystore" tool) are automatically deleted via Cron Jobs 60 minutes after creation.
• Build History: Download links provided in your app's "History" tab will expire and become invalid after 1 hour.
• Zero Leftovers: After these automated windows, absolutely no files or build traces remain on our storage buckets or servers.

6. Keystore Generation & User Responsibility

If you use our tool to generate a Release Keystore for Google Play Console submission, please note the following responsibilities:

• We do not keep backups of your Keystore files or passwords. For your privacy, the generated files are purged from our temporary servers in exactly 1 hour.
• Once generated, it is your sole responsibility to securely store your Keystore (.jks) and its metadata (alias/passwords).
• Tip: We highly recommend using the built-in "Backup to Google Drive / Dropbox" buttons inside the Build History menu to securely save these files before the 1-hour server deletion window expires.
• If you lose your Keystore, we cannot recover it, and you will lose the ability to release updates for your app on the Play Store.

7. Optional Monetization & Native Utility Plugins

Our app provides strictly optional (opt-in) configuration tools for you to inject native features, including your own AdMob Unit IDs and In-App Purchase (IAP) Product IDs, into the generated app. Because these features are entirely optional and controlled by you, we guarantee and clarify the following:

• 100% Revenue Ownership: We do not take a cut, hijack traffic, or inject our own ad units into your compiled application. 100% of the revenue generated belongs to you.
• End-User Data Liability: If you explicitly choose to enable the AdMob plugin or hardware sensors (such as Camera or Geolocation) for your generated app, you become the data controller for your app's end-users. You are solely responsible for obtaining any necessary user consents (e.g., GDPR, CPRA) and maintaining your own valid Privacy Policy for your generated application.
• Open-Source Transparency: The monetization and native utility modules injected into your app rely on transparent, open-source Cordova plugins:
  • cordova-plugin-admob-nextgen
  • cordova-plugin-purchase
  • cordova-plugin-camera
  • cordova-plugin-geolocation
  • cordova-plugin-network-information
  • cordova-plugin-screen-orientation
  • cordova-plugin-statusbar

📚 Developer Resources: To learn how to implement these monetization and native features into your website's source code, please read our Native API Bridge Docs

8. Subscriptions & Google Play Billing

If you choose to upgrade to the PRO version of "Web To APK Builder & Monetize", the transaction is handled entirely by Google Play Billing.

• We do not process or store your credit card information.
• Your subscription status is tied directly to your Google Account (the account logged into the Google Play Store), not to your specific mobile device.
• Account Deletion Disclaimer: Using the 1-click "Delete Account" feature inside our app will permanently erase your profile data from our authentication servers. However, it will not cancel your active Google Play subscription. Subscriptions must be managed or canceled directly through your Google Play Account settings.

9. Children's Privacy (COPPA Compliance)

Our application is a developer tool and is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe that your child has provided us with any personal information, please contact us. Because our system automatically purges source data instantly and artifact data within 1 hour, any inadvertently submitted data is destroyed rapidly by default.

10. App Store Compliance & Disclaimer of Liability

Our service provides a technical utility to convert your website into a mobile application container. By using our builder to publish on platforms like the Google Play Store, you acknowledge and agree to the following:

• Website Ownership & Legality: You represent and warrant that you are the legitimate owner or have explicit legal authorization to convert and distribute the content of the provided Target URL or uploaded ZIP file. You are solely responsible for proving ownership (e.g., via Google Search Console, Digital Asset Links, or legal documentation) if requested by app store reviewers.
• Google Play Policies: You are fully responsible for ensuring that your application complies with all Google Play Developer Policies, including but not limited to the Webviews and Affiliate Spam policy.
• Native Functionality Requirement: App stores often require WebView-based apps to include native features. While our platform provides optional native modules (such as AdMob and In-App Purchases) to help enrich your app, the strategic implementation of these features to pass store reviews is your responsibility.
• No Guarantee of Approval: We do not guarantee that the APK/AAB generated by our service will be approved or published by Google Play or any other app store.
• Zero Liability for Suspensions: App rejections, policy strikes, application suspensions, or developer account terminations are enforced strictly at the discretion of the app store reviewers and are completely beyond our control. We shall not be held liable for any damages, loss of revenue, or business interruption resulting from such actions.
• User Negligence & Local Data Loss: Because the Mobile IDE code editor and app configurations rely heavily on LocalStorage, any loss of source code resulting from user negligence, device damage, app uninstallation, or account deletion is entirely your responsibility. We are not liable for any business, financial, or data loss caused by a failure to back up your projects.

11. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or how your data is handled, please contact us at:

Email: [email protected]
Website: https://dropcore.net