1. Scope and roles
This policy applies to Google-related information handled through Naronim Platform. Naronim may handle business account and support information for its own service administration. For customer Google data, Naronim generally acts for the customer under the customer’s instructions and contracted service scope.
The organization that owns the Google account or property controls its users, ownership, manager relationships, and authorization decisions.
2. Information we handle
Depending on the connection and the permissions you approve, Naronim Platform may handle:
- Authorization information: Google account identifiers, approved scopes or roles, connection status, access or refresh tokens, and service-account authorization needed to operate the connector.
- Google property information: account, property, profile, site, advertising, merchant, or other resource identifiers and settings within the approved scope.
- Reporting and performance data: for example, Search Console query and page metrics, Google Analytics dimensions and metrics, and other service data expressly included in the customer scope.
- Operational records: synchronization times, run status, errors, access changes, audit events, security events, and records used to troubleshoot or verify the service.
- Support records: business contact details and communications submitted when asking for help, disconnection, export, correction, or deletion.
Naronim does not ask customers to provide Google passwords, one-time codes, recovery codes, OAuth client secrets, or private keys through these public pages or ordinary support messages.
3. How we use information
We use Google-related information to authenticate an approved connection; retrieve, normalize, and present customer-authorized data; provide reporting and managed services; perform actions separately authorized by the customer; maintain tenant and access boundaries; troubleshoot failures; prevent abuse; document changes; respond to support requests; and meet contractual or legal obligations.
We request access that is relevant to the configured feature. A broader role or write permission is not treated as permission to perform every action available under that role.
Our use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.
5. Retention and deletion
Different records have different retention needs. Authorization credentials are kept only while needed for the approved connection or another documented requirement. Google-derived customer data, connection metadata, support records, audit events, security records, and backups may follow different documented schedules based on the service agreement, recovery cycle, security needs, and legal obligations.
No single deletion period applies to every data class. When you submit a verified request, Naronim will identify the data in scope, explain any information that must be retained, and confirm the applicable deletion process. Revoking Google access stops future access through that authorization but does not automatically erase copies already held by Naronim.
6. Security
Naronim uses administrative and technical safeguards designed for the nature of the service, including access controls, customer and tenant boundaries, separation of credentials from public web files, scoped connectors, audit records, controlled changes, and recovery procedures. No online service can guarantee absolute security.
7. Your choices and rights
You can review or remove Naronim Platform’s access from your Google Account’s third-party connections page. Your organization’s Google administrator may also manage users, service accounts, manager relationships, and property roles.
Depending on applicable law and Naronim’s role, you may request access, correction, export, restriction, objection, or deletion. If Naronim handles data for a customer that controls the data, we may refer the request to that customer or ask for confirmation of your authority.
8. International processing and changes
Naronim LLC is a Delaware limited liability company in the United States. A customer service may involve processing in the United States and other locations approved for that deployment. We may update this policy when the service or legal requirements change. The effective date at the top identifies the current version.
9. Contact
For privacy questions or a Google data request, reveal the support address below. State the organization you represent and the Google connection concerned. Do not send credentials or verification codes.