Gameroom Gallery Ads MCP Privacy Policy
Effective upon publication.
This policy describes how the private Gameroom Gallery Ads MCP desktop application accesses, uses, stores, and shares Google user data.
Information accessed and its use
With your authorization, the application accesses Google Ads account identifiers, campaign settings, budgets, bidding information, ads, keywords, search terms, targeting criteria, and performance metrics. It uses this information to provide reports, prepare previews of requested changes, apply confirmed changes, and verify the results.
The application requests the Google Ads authorization scope, which permits reading and managing Google Ads data available to the authorizing Google user. The installed server limits account queries and changes to its configured target account.
Local storage and retention
OAuth client credentials and a refresh token are stored in an owner-only configuration file on the operator’s Mac, outside the source repository. The refresh token allows continued access until it expires or is revoked. Credentials are retained until removed by the operator.
The application keeps a local audit log recording timestamps, customer identifiers, requested changes, before-and-after values, verification results, and Google request identifiers when available. Audit records are retained until the operator removes them. Proposed changes are held temporarily in server memory and expire after ten minutes.
Sharing and processing
The application sends authorized API requests to Google. Reports, previews, and tool results are returned to the connected AI assistant and may be processed or retained by its provider under the operator’s selected product terms and settings. Operators should review those settings before connecting the tool.
The application has no feature for selling Google user data, advertising-data brokerage, or model training. Google user data is used to provide the requested account-management functions. Access by people is limited to authorized operators and any support access they explicitly permit.
Security and your choices
The application uses Google’s OAuth flow and Google’s authenticated API connections. Its credential file and audit log use owner-only file permissions. Security also depends on the operator’s Mac, connected assistant, and account access settings.
You can revoke the application’s Google access through your Google Account’s third-party connections settings. Stop the local server and remove its local credential files to clear stored authorization from the Mac. Audit records must be removed separately. Information already held by Google or an assistant provider is subject to that provider’s retention controls.
Google API data requirements
The application’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.
Contact and changes
For questions about this application, access revocation, or removal of locally stored application data, contact lansingjason@gmail.com. Updates to this policy will be published on this page.