Dweav AppForge Android Privacy

Plain-language summary

This product uses the Altru.dev standard privacy structure. Update this page with product-specific behavior before publishing externally.

Data collected

AppForge processes the files and information required to complete the requested build, including:

- Uploaded PWA project files
- App name and package ID
- Version and build configuration
- Application icons and artwork
- Android signing materials
- Build status and technical error information

AppForge does not collect advertising profiles, browsing histories, contacts, location histories or behavioural analytics from users of generated applications. Submitted project information is used to generate the requested Android package.

Local storage

Update this with the exact local storage behavior.

Network requests

Secure network requests are used to upload the PWA and build configuration, initiate the Android build and return the completed APK, AAB and signing files. Build tools may contact Android, Capacitor, Gradle and package repositories during compilation.

Generated apps do not contact AppForge and do not include AppForge analytics or telemetry. Runtime network requests depend entirely on the submitted PWA. Fully local applications can operate without external runtime requests.

Third-party services

Generated applications do not require a continuing connection to AppForge or Altru.dev and do not include third-party advertising or analytics services unless those services were already included by the customer in the submitted PWA.

Permissions

AppForge does not add unnecessary Android permissions. Permissions are declared according to the submitted app’s actual functionality. Offline projects can be built without Android internet access, while device capabilities such as the camera are included only when required by the application.

Retention

Update retention rules before final deployment.

Deletion

Update deletion instructions before final deployment.

Contact

hello@altru.dev