Forgeview / Play Console

Data Safety Summary

This public summary is written to match the current local-first Android implementation. The Play Console form and Google SDK disclosures remain the source of truth.

Data handled by Forgeview

• Model filesProcessed locally from files the user selects. Not collected by Forgeview servers.
• Recent-file metadataStored locally on the device for the recent-files list and preferences.
• Account informationNo Forgeview account, sign-in, cloud sync, or account deletion workflow.

Advertising services

The Android app includes Google Mobile Ads and the Google User Messaging Platform. Depending on region, consent, and ad settings, advertising services may process device or advertising identifiers, ad requests, diagnostics, and ad interaction signals. Forgeview uses a persistent banner placement and does not use analytics or crash-reporting SDKs in the current release.

Sharing and security

Forgeview does not upload model bytes to a Forgeview backend. Files are read through the browser or Android document picker, and Android-imported copies are released when the model is replaced or the session is cleared. Data sent to Google advertising services is governed by the consent choices shown in the app and Google's policies.

Deletion and choices

Users can clear local app data, uninstall the app, avoid selecting files, and change available advertising privacy choices through the Android privacy-options entry point. Because there is no Forgeview account, there is no server account-deletion request.