HINOMI Google Analytics

Privacy notice

Last updated: October 24, 2026. This notice covers HINOMI Google Analytics, a company-operated connector for approved team members.

Data we access

When you connect, we request your Google account identifier and email to identify your connection, and read-only access to Google Analytics. The service retrieves account and property metadata and the reports you ask for. Your existing Google Analytics permissions determine which properties and data are accessible. We do not request permission to edit Analytics.

How data is used and shared

We use this information to authenticate you and answer your Analytics requests. Report results are returned to the AI assistant you connect, such as ChatGPT (OpenAI) or Claude (Anthropic), to fulfill your request. That provider processes the results under your organization's account terms and settings. Connect only the company-approved workspace and request only data you are authorized to share with it.

HINOMI does not sell Google user data, use it for advertising, or use it to train general-purpose AI or machine-learning models. Google API data is used only to provide or improve this user-facing reporting feature. Human access is limited to applicable Google Limited Use exceptions, such as your explicit consent for a specific support request or security investigation.

HINOMI Google Analytics' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Storage and security

The connector runs on HINOMI-operated infrastructure hosted by OVHcloud in Singapore. OAuth credentials and authorization state are encrypted at rest. They are used to maintain your connection and renew access. Google access and refresh tokens are never included in tool results or sent to the AI assistant. Report content is not stored in a reporting database or shared result cache by this service. Your AI assistant may retain conversation results according to its own settings.

Retention and disconnecting

OAuth records have expiry times; expired records are purged by the service maintenance job. An unused MCP refresh token normally expires after 90 days; client registrations expire after 90 days without use. A Google authorization may expire or be revoked earlier. When an assistant calls our revocation endpoint, we block the local connection and attempt to revoke Google access. Temporary Google failures are retried for up to 24 hours, subject to a retry limit; successful Google revocation is not guaranteed. Disconnect the connector in your assistant and revoke its access from Google Account connections to stop Google access. Removing the connector from an assistant alone may not revoke the Google authorization. Contact us to request deletion of stored connection records.

Contact

For privacy questions, access or deletion requests: support_it@hinomi.co