Effective 9 September 2026

Privacy policy

This policy applies to Akra MCP Analytics, AkraDev Studio's private reporting connector. It does not replace the policies of our consumer apps.

Data we access

With the operator's authorization, the connector accesses their Google account email to confirm identity; Analytics accounts, properties and aggregate usage metrics; AdMob account, app, ad-unit and performance reports; and, when separately authorized and available, Google Ads account and campaign reports. We request the read-only Analytics and AdMob scopes. Google's Ads OAuth scope also permits management operations, but the current Ads MCP exposes read-only operations.

Purpose and sharing

We use this information to produce operator-requested app, monetization and acquisition reports for accounts the operator is entitled to access. We do not sell Google user data, use it for targeted advertising, or combine it with individual app users' identities.

The MCP servers make requests to the relevant Google APIs from the operator's computer. Selected query results and the operator's instructions are returned to Codex and processed by OpenAI to provide the requested assistance. OpenAI's applicable account settings, terms and privacy controls govern its processing and retention. An operator-directed export may also place a report in a destination the operator chooses.

The connector itself does not train AI models. Operators must use AI-provider settings that exclude connected Google data from generalized model training and are consistent with Google's requirements. Akra MCP Analytics'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.

Storage and retention

OAuth credentials are stored outside source repositories in an access-restricted folder on the operator's computer. They are not intentionally included in reports or published website files. API results are processed as needed for requested queries. Saved reports and AI conversations can remain in the operator's chosen local files or AI service until deleted under those systems' controls; the connector does not impose an automatic retention period on those records.

These public documentation pages have no sign-in form, analytics script or advertising code. The website host may process ordinary connection information to serve the pages.

Control, revocation and deletion

Operators can revoke the connector in their Google account connections. Revocation stops future authorized API access but does not delete reports or conversations already saved. Remove local credentials and exported reports from the computer, and use the AI provider's controls to delete conversations. For assistance with connector-held records, contact akradev001@gmail.com.

Access and updates

The connector is for the account owner and authorized internal operators, not a public service. The operator is responsible for granting access only to accounts and data they are entitled to use. We update this page when the connector's data practices change and identify the effective date above.

Contact: AkraDev Studio, akradev001@gmail.com.