Access and purpose
The console is for its owner’s app-development operations. Connections are configured deliberately; browsing this information page does not connect an account or grant access to the console.
AdMob: account identifiers, reporting currency/timezone, app names and identifiers, ad-unit identifiers and formats, and aggregated advertising estimates such as earnings, impressions and clicks. These support app mapping and advertising-performance views.
Google Play: configured app packages, track/release summaries, billing-product and subscription configuration, and available recent reviews, including returned author names, text, ratings and version information. These support release tracking, billing checks and customer support. The owner can separately import financial reports; buyer addresses and order identifiers are discarded during that import.
Authorization: OAuth client details and refresh tokens, or an owner-provided service-account key, allow the selected connection to continue reading data. Access tokens are obtained when needed. A local console account and session protect the workspace.
Use and sharing
Google data is used to display and maintain the console’s visible app-operations features. The console does not sell this data, use it for advertising targeting, or use it to train general-purpose AI or machine-learning models. Google API data handling follows the Google API Services User Data Policy, including its Limited Use requirements.
Provider requests are sent to Google for authorization and the selected API operations. A Play review reply is sent to Google only after the owner reviews and confirms its exact text. No Google Play publishing endpoint is exposed.
The owner controls exports, backups and any access granted to the host. App-scoped agent briefs can contain relevant Play release, billing and review evidence, task text and repository context. They exclude vault secrets, AdMob snapshots and imported financial-report snapshots. If the owner gives an exported brief to an outside agent or tool, that is a separate owner-directed disclosure. Access is not granted automatically to visitors of this website.
Storage and protection
Provider snapshots and operating records are stored in the local console database, protected by the host’s file permissions and console login. The database itself is not fully encrypted. Credential values are encrypted at rest in a separate vault; on Windows its key is wrapped for the current Windows user. Portable console backups are encrypted with a passphrase chosen by the owner and include credentials inside that encrypted envelope.
Connections to Google use HTTPS. The default browser connection is on the same machine through loopback. Access from another device requires a configured HTTPS origin. Security also depends on the owner’s host, account, network settings and backup handling.
Retention, disconnection and deletion
Saved snapshots remain until the owner removes or replaces the relevant local data; a failed refresh preserves the last successful snapshot with its original date. Portable backups remain wherever the owner saves them and must be removed separately when no longer needed.
OAuth authorization attempts expire after ten minutes and are discarded on logout or restart. Encrypted client setup records persist for retries. Saved account credentials can be deleted through Credential vault. Removing a credential stops that console connection from using it, but does not delete cached snapshots or revoke the grant at Google.
The owner can review or revoke a Google grant in Google Account connections. Revocation does not erase data already stored on the console host or in backups. For help removing local data or handling a privacy request, contact info@totaldevel.com.
Public information pages and updates
These static information pages do not embed the owner’s account data or console credentials and contain no analytics scripts. Website hosting and network providers may process ordinary request information under their own policies. Changes to the console’s Google-data handling will be reflected here and in the connection disclosure before new uses are enabled.