M87 Hub privacy policy

Google information accessed and its purpose

With the owner’s authorization, Hub reads release information for Google Play apps and tracks explicitly configured in its registry. This can include app package identifiers, release names, version codes, lifecycle status, release metadata, and observation timestamps. It displays and retains the results locally to help the owner monitor and prepare app releases.

Hub requests the Android Publisher scope, https://www.googleapis.com/auth/androidpublisher. That scope has broader Google account-management capabilities than this app currently uses. The current implementation uses read-only release-status requests; it does not upload artifacts, create or commit Play edits, submit app reviews, or publish releases. Hub does not request Google profile, email, Gmail, contacts, payment, or order data for this connection.

Authorization and credential protection

The owner imports a downloaded Desktop OAuth client file locally and completes consent in the system browser. Google issues the authorization and may receive the client identifier, requested scope, authorization code, token requests, and app/track requests needed for the connection. Hub does not collect the owner’s Google password.

Client secrets and refresh credentials are encrypted at rest with Windows DPAPI CurrentUser under the owner’s Windows profile. Access tokens are held in service memory while needed. Credentials are not intentionally returned in dashboard or MCP responses, public pages, logs, or retained text evidence. Imported source files and user-created backups are separate copies under the owner’s control.

A separately configured service account can be used instead of user OAuth. Its private key is protected in the same local vault, and its existing Play Console app permissions still determine access.

Local developer data and device evidence

Hub stores the app registry, project paths, configured connection metadata, device identifiers and current transports, reservations, job inputs and results, artifact snapshots and hashes, approvals, exports, and history on the owner’s PC. The default location is %LOCALAPPDATA%\M87Hub.

Device jobs may retain installed-package information, screenshots, bounded app-process logs, and test evidence. Screenshots and app logs can contain personal or confidential information visible on the selected device. Review that evidence before sharing it. The local dashboard uses a session cookie for authentication; it is not a public website account.

Sharing, MCP clients, and AI processing

Hub has no telemetry, advertising, or automatic upload of its registry, artifacts, logs, screenshots, or evidence to an M87Studios server. Authorized Google requests go to Google to provide the connection described above.

When the owner configures an authenticated MCP client and requests data or work, Hub returns only the results permitted for that client’s apps, devices, and operations. These results can include Google release observations and local job or device information. The client may pass results to an AI service; that processing is governed by the client’s settings and provider terms. Enabling MCP therefore does not mean every result remains exclusively on the PC.

Standard human-dashboard OAuth clients and AI-agent/MCP OAuth clients are kept separate. Configured workflow labels do not grant new Google scopes or Play permissions. The owner chooses which clients receive access and can revoke their local Hub credentials.

Google API data use

M87Studios uses Google API information to provide the user-requested release-status and related local developer features described here. It does not sell that information, use it for advertising, or use it to train generalized AI models.

M87 Hub’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, revocation, and deletion

Local records and evidence remain until the owner removes them. Hub does not currently apply an automatic retention period. Backups and exported files can retain separate copies until the owner deletes them.

The owner can revoke M87 Hub’s Google authorization through the Google Account connections page, and can revoke local MCP clients in Hub. Revoking access prevents future authorized reads but does not erase existing local history or exports. To remove local Hub records and its protected credential copies, stop the service and remove the relevant Hub data and backup copies. Contact support if you need help identifying those local records.

This public website and support

This informational website does not receive the local Hub’s Google credentials, app registry, or device evidence. Cloudflare hosts and protects the website and may process normal connection information, such as IP address, browser information, requested pages, and security logs. The website has no application account signup, analytics scripts, or contact-form submission.

If you email support@m87studios.com, M87Studios receives your address and the information you choose to include. Support correspondence is handled through Cloudflare and Google Gmail, used to answer the request, and retained only as needed for that request and applicable obligations. Ask the same address to delete support correspondence. Never send credentials or unreviewed private evidence.

Changes and contact

The effective date changes when this policy is updated. New Google data uses or materially different sharing require an updated disclosure and any consent required by Google. For privacy questions, contact M87Studios at support@m87studios.com.