hyperlabsEffective date: November 2, 2026
HyperLabs AI operates HyperLabs Search Review Hub, a private tool for reviewing the search visibility, advertising performance, and keyword opportunities of authorized websites and advertising accounts. This policy describes the tool's handling of Google data and related reports.
Information accessed
With authorization, the tool accesses Google Search Console property information, search queries, page URLs, clicks, impressions, click-through rates, average positions, sitemap information, and stored URL indexing results. It accesses Google Ads account identifiers and settings, campaign and landing-page performance, spending and currency information, and conversion definitions and reported metrics. When Google approves planning access, it can request keyword suggestions and historical search and advertising estimates.
The tool also reads public website HTML for requested checks. Information provided in support requests may include your contact details and the information you choose to send. Do not include credentials, customer records, or sensitive personal information in support messages.
Purpose and use
We use this information to produce requested reports, identify website and advertising opportunities, compare performance, and support authorized troubleshooting. Access is limited by the Google account's permissions and the installation's configured properties and advertising accounts. The tool does not read Gmail messages, Google Drive documents, or Google Calendar contents.
HyperLabs does not sell Google user data or use it to serve or target advertisements. Reporting on advertising performance does not involve sharing Google user data with advertising networks for targeting.
Google authorization and credentials
Sign-in takes place through Google. The tool does not receive or store your Google password. The current local installation stores OAuth access and refresh credentials in a private file outside the source-code repository. File access is restricted to the operating-system user where supported. Tokens allow the tool to refresh access without repeating sign-in until access expires, is revoked, or Google requires reauthorization. Device owners remain responsible for device security and backups.
Local reports and AI clients
During a request, results are processed by the MCP and returned to the authorized client, such as Codex. When an operator exports a report, copies may be stored on the machine in JSON, Markdown, HTML, or other selected formats. Operators may also save research in their own project documentation.
If an AI assistant is used, requested report data is sent to that client and may be processed by its service provider according to the account's settings, agreements, and privacy policy. Conversations, exported reports, and device backups may contain retained copies. Operators must select and configure clients consistently with their authorization to use the business data and Google's applicable data-use requirements. Do not connect a shared installation to users who are not authorized to access the entire configured portfolio.
The MCP does not train AI models. It does not provide an independent public database or a public feed of connected business data.
Sharing and access
Google receives the API requests needed to provide the connected services. The authorized MCP client and its service provider receive the results requested through that client. Authorized HyperLabs personnel may access information when needed to provide requested support or operate an authorized installation. We may disclose information where required by applicable law. We do not make connected account data publicly available through the application home page.
Retention and deletion
Local credentials remain until they are removed or replaced. Exported reports and project documents remain until their owners delete them. The tool does not automatically delete exported reports, client conversations, or backups after a fixed number of days.
To stop future Google access, remove the application's authorization in your Google Account’s third-party connections settings. Remove the local credential file to remove the installation's stored tokens. Revoking access does not automatically delete previously exported reports or client conversations; delete those copies separately, including backups where applicable. To request assistance with information held by HyperLabs, email info@hyperlabsai.com. We may need to confirm that you are authorized to make the request.
Google API Services User Data Policy
HyperLabs Search Review Hub'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.
Changes and contact
We will update this policy when the tool's data practices change. The effective date identifies the published version. Questions about this policy or Google data access can be sent to info@hyperlabsai.com.