Nimbo knowledgebase

Nimbo   >   Knowledgebase   >   My account   >   Privacy Policy

Privacy Policy

This Privacy Policy explains how Nimbo handles account information and information used by its optional automatic Google Search Console connection. For privacy enquiries, contact us through Nimbo's contact page or Help & Support in your account.

Account information

We collect your name and email address to create and manage your Nimbo account. For paid services, we also collect the contact and billing information needed to provide the service and arrange payments. We use this information to administer your account, process payments and respond to support requests.

Nimbo also processes the website content and other information you choose to store through its services. Our website uses Google Analytics to help us understand website usage. This is separate from the Google Search Console connection described below.

Optional Google Search Console connection

The automatic connection, currently labelled Google Search Console, lets you ask Nimbo to verify your website with Google, add it to Google Search Console and submit its sitemap. Connecting is optional. You sign in directly with Google and choose whether to grant permission. Nimbo does not receive your Google password.

This automatic connection is separate from any existing Google integration in your Nimbo account. Its behaviour and Disconnect control are described below.

Google information accessed and stored

For this connection, Nimbo receives and stores:

These details are linked to the relevant Nimbo account and website. Connection errors may also be recorded in technical logs using the website identifier, setup stage and response status. The connection's application error logger does not intentionally record Google authorisation tokens or response bodies.

The automatic connection requests Search Console management permission and the permission to verify new websites. Although Google's Search Console permission allows broader access, this connection uses it for property setup and sitemap submission. It does not currently retrieve search-performance reports or request access to Gmail, Google Drive, contacts or calendars.

How the Google information is used

Nimbo uses the connection details to obtain a verification token, publish it as a DNS record or website verification tag, ask Google to verify ownership, add the website to Search Console and submit its sitemap. Tokens also allow the setup to continue or retry without asking you to sign in at every step.

A DNS verification record or website verification tag is public by design. It is different from the private access and refresh tokens used to authorise requests to Google.

Sharing and permitted use

We send the information needed for these requests to Google. Where verification uses DNS, the verification value is also sent to the hosting or DNS service that manages the record. Google handles information it receives under its own Privacy Policy.

Service providers supporting Nimbo may process information where needed to operate the service. Google user data may be shared only as necessary for the connection you authorise, for security purposes, or where required by law. It is not sold, provided to advertising platforms or data brokers, used for targeted advertising, or used to train general-purpose AI models.

Human access to Google user data is restricted to your specific consent, necessary security investigations, legal requirements, or permitted aggregated internal operations. Nimbo's handling of Google user data is subject to the Google API Services User Data Policy, including its Limited Use requirements.

Storage and protection

Google connection details are stored server-side in Nimbo's database. The connection uses HTTPS when communicating with Google. Its account and website checks restrict connection actions to the relevant Nimbo account, and its request checks protect the authorisation flow. Access and refresh tokens are not published in the website or DNS records.

Connection records remain stored while the connection is present, including after setup has completed. They are not automatically removed just because the sitemap has been submitted.

Disconnecting and deleting Google connection data

Select Disconnect in the Google Search Console section of the relevant website's settings to delete that website's connection record, including its stored access and refresh tokens, from Nimbo's active connection database. If you have connected several websites, disconnect each one that you no longer want connected.

Disconnecting does not remove the Search Console property or its data from Google, remove the public DNS verification record or website verification tag, revoke permission in your Google Account, or disconnect a separate existing Nimbo Google integration. Backup copies and technical logs are separate from the active connection record and may remain after disconnection.

You can separately revoke the application's access through your Google Account's third-party connections. This prevents further authorised access under that grant, but does not itself delete Nimbo's stored records. Revoking access can also affect other websites connected using the same Google authorisation.

To ask about, obtain or request deletion of remaining connection information, logs or backup copies, contact Nimbo through Help & Support or our contact page. Include the website domain and explain which information your request concerns. Do not send passwords or authorisation tokens.

Access, correction and account deletion

You can ask Nimbo to provide access to, correct or delete your personal information using the contact options above. You can request closure of your Nimbo account through My account > Delete my account. Account closure is separate from revoking Google's permission; contact us about any remaining information and retention requirements.

Changes to this policy

We will update this policy when our practices change. Before using Google user data for a new purpose or accessing additional types of Google user data, we will explain the change and obtain the consent required for that use.