Google API
This document supplements AERA’s general Personal Data Policy and specifically describes access to Google data through OAuth and the Google Analytics APIs. The Russian text controls if the translations differ. Ask AERA answers are produced by Cloud.ru from verified Core facts. Google data is not used to train models. A separate raw GA4 export is not assembled for the Cloud.ru request.
AERA accesses Google data only after a user initiates the Google Analytics connection, signs in to Google and explicitly grants AERA permission through OAuth. The integration requests read-only Google Analytics access. AERA does not request the user’s Google password and does not receive permission to modify Google Analytics settings or data.
AERA may read the Google Analytics accounts and GA4 properties available to the user so the user can choose what to connect. After selection, AERA may read reporting data for that GA4 property, including ecommerce transaction identifiers and dates, purchase revenue, acquisition source/medium/campaign, manual UTM source/medium/campaign/content/term, landing pages, sessions, active and engaged users, new/returning user aggregates, and ecommerce-funnel aggregates for view_item, add_to_cart, begin_checkout and purchase. The actual data available depends on what is configured and present in the selected GA4 property.
Google Analytics data is used only for features the user expects from the connected AERA integration: synchronizing the selected GA4 property, business reporting, source and campaign attribution, funnel and revenue analysis, and generating summaries, signals and insights inside the user’s AERA workspace. AERA does not use Google API data for sale, independent advertising targeting or building advertising profiles of users.
After successful OAuth, AERA receives technical access credentials needed to operate the connection. OAuth tokens are kept server-side in a protected, access-controlled credential store and are not exposed in the product UI, repositories or analytics events. They are used only to call the permitted Google APIs for the connected user. The user can disconnect the source in AERA or revoke AERA access from their Google Account.
Synchronized Google Analytics data follows the connected-system retention rules described in AERA’s general Personal Data Policy. OAuth tokens are retained only while needed for an active connection and may become unusable after disconnection, revocation or expiry. A request to delete data associated with the user can be sent to support@aera-platform.ru.
AERA does not sell Google user data. Access is limited to infrastructure and other processors required to provide AERA functions and subject to appropriate data-protection obligations. AERA does not provide Google user data to third parties for their independent marketing, advertising targeting or resale.
AERA’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements. These restrictions apply to how AERA uses, transfers and protects data received through Google OAuth and Google APIs.
The user controls the connection and can stop future access by disconnecting Google Analytics in AERA and/or revoking AERA access in their Google Account. Questions about access, use or deletion of Google data: support@aera-platform.ru.