Privacy Policy — noco-ai-tools

This Privacy Policy describes how the noco-ai-tools NocoBase plugin ("the Plugin") handles data when users connect their Google accounts. The Plugin is open-source software distributed under the MIT License.

Google API Services User Data Policy: The Plugin's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

What data we collect

When a user connects their Google account, the Plugin stores the following in the NocoBase database (googleConnections table), encrypted at rest:

Field	What it is	Why it's stored
`googleEmail`	Gmail address of the connected account	Displayed to the user to confirm which account is connected
`accessToken`	Short-lived OAuth 2.0 access token	Authorises calls to Gmail and Calendar APIs
`refreshToken`	Long-lived OAuth 2.0 refresh token (encrypted)	Obtains new access tokens without requiring re-consent
`tokenExpiresAt`	Expiry timestamp of the current access token	Triggers automatic refresh before the token expires
`scopes`	OAuth scopes granted by the user	Records exactly what permissions were consented to
`status`	`active` or `error`	Surfaces token revocation errors to the user

The Plugin does not store the content of emails or calendar events. Email bodies and event details are returned to the AI employee during a tool call and are subject to the data-handling policy of your NocoBase instance and its AI provider.

Google OAuth scopes requested

openid, email, profile — identifies the connected account.
https://www.googleapis.com/auth/gmail.modify — read, send, modify, and label emails. Does not include permanent deletion.
https://www.googleapis.com/auth/calendar — read and write the user's calendars and events, including shared calendars.

How data is used

Stored credentials are used exclusively to:

Make Gmail and Google Calendar API calls on behalf of the specific user who granted consent.
Refresh access tokens automatically before they expire.
Revoke tokens when the user disconnects their account.

No data is shared with third parties, advertising networks, or analytics services. Credentials are never transferred outside your NocoBase instance.

Data isolation between users

Every API call is scoped to the individual NocoBase user who initiated the request. The Plugin verifies the caller's identity before each API call and uses only that user's stored tokens. No user can access another user's email or calendar data through the Plugin.

Data storage and security

Tokens are stored using NocoBase's encrypted field type (AES encryption at rest).
OAuth Client ID and Secret are stored in NocoBase Variables & Secrets, separate from application data.
Transport between your NocoBase server and Google APIs uses HTTPS.
The Plugin does not log token values or email content to application logs.

Data retention and deletion

User disconnect: Clicking "Disconnect" revokes both tokens with Google and deletes the row from the database.
Plugin disable: All tokens are revoked with Google and deleted from the database.
Plugin uninstall: All tokens are revoked and the googleConnections table is dropped.

Your rights

You may revoke the Plugin's access to your Google account at any time:

Within NocoBase: Use the "Disconnect" button in the Connect Google block.
Directly with Google: Visit myaccount.google.com/permissions and revoke access.

Third-party services

The Plugin communicates exclusively with Google APIs (accounts.google.com, www.googleapis.com). No other external services are contacted.

Children's privacy

The Plugin is not directed at children under 13. It is intended for deployment within enterprise or personal NocoBase instances administered by adults.

Changes to this policy

Material changes will be reflected by updating the "Last updated" date and noted in the GitHub repository's release notes.

Contact

For questions or data deletion requests, open an issue on the GitHub repository.