Agentic Tools home

Privacy policy

This website and the Google account connector: what they access, why, and the choices you have.

Last updated 9 October 2026

Who is behind Agentic Tools

Agentic Tools is a collection of projects from NNet-Tech, including Maintenance, nnet-tools, the feedback tool, docx-mcp and docidx. Contact NNet-Tech support at support@nnet.tech. This policy covers this informational website and the Google account connector, which connects self-hosted Agentic Tools software to Google services. Its current integration is Google Calendar for Maintenance. The server is being developed for publication through NNet-Tech on GitHub; users will download it and run their own installations.

The Calendar permissions and maintenance retention periods described here apply to that integration. They do not describe every tool in the collection. Data-handling information for other tools will accompany their documentation.

Your deployment's administrator controls its connections, infrastructure, access policies and data retention. Requests about information held by that deployment should go to its administrator. NNet-Tech support handles project questions and requests about information held by NNet-Tech, such as support correspondence. Installing the software or connecting Calendar does not send your credentials or maintenance records to NNet-Tech or this website.

Connecting a Google account happens through Google’s authorisation process. This website does not collect Google passwords or provide hosted account registration. This policy describes the connector's current Calendar functionality. Other Google services, such as email or Drive, may be supported in future; their data handling will be disclosed and any additional permissions requested through Google's authorisation process before they are used.

Google Calendar data the connector accesses

The integration requests these permissions:

  • Calendar list, read only: identifiers, names, time zones and access roles for calendars available to the connected account, so you can select a calendar and confirm the app has permission to create events there.
  • Calendar availability: free/busy time ranges for the calendars configured for conflict checking and connection checks. The server can also read events on configured calendars to calculate conflicts. Those responses may include other event details, but the availability cache stores busy time ranges, not unrelated appointment titles or descriptions.
  • Calendar events: permission to read and edit events. The current workflow creates, retrieves and updates its own maintenance events, including their titles, descriptions, scheduled times, status and identifiers. Event readback may include notes added to those maintenance events.

Google’s events permission can permit broader access to events on calendars accessible to the connected account. The current implementation restricts its event creation and updates to events it identifies as managed maintenance events. These implementation checks do not narrow the permission granted by Google.

The connector's local setup tool obtains OAuth access and refresh tokens, which your administrator stores privately in your installation so it can continue working after the initial authorisation. Your installation talks directly to Google's APIs. NNet-Tech and this website do not receive or store those user tokens through the integration.

How information is used

Calendar data is used to find suitable maintenance windows, avoid conflicts, create and update maintenance bookings, and check that calendar entries match the reported state of the work. Operational records link event identifiers, times and outcomes to maintenance jobs so administrators can investigate failures and avoid duplicate bookings.

Maintenance event descriptions may include the system being maintained, the work planned and its reported outcome. These details are sent to Google when the event is created or updated and are visible according to the selected calendar’s existing sharing settings.

Who receives Google user data

The Google account connector exchanges Google user data directly between Google and your own self-hosted installation. It does not send Calendar records or user OAuth tokens to NNet-Tech or this public website.

The recipients and circumstances of sharing, transfer or disclosure are:

  • Google: Google handles account sign-in, consent, token exchange and Calendar API requests. Your installation sends Google the requests and maintenance-event details needed to check availability and create, read or update bookings. Google returns the authorised Calendar data and tokens.
  • Your installation and its authorised users: the administrator you choose operates the software and controls access to locally stored tokens, Calendar identifiers, availability information and maintenance records. People you authorise to use or administer that deployment can access the information made available to them for operating and supporting the integration.
  • People with access to the selected Google calendar: maintenance events stored at Google are visible to calendar owners and collaborators according to that calendar's existing sharing permissions. The integration does not change those sharing permissions.
  • Optional services chosen by your administrator: if your administrator gives other tools or providers access to the installation, those services may receive the information made available to them. Examples include an agent or AI service receiving permitted scheduling or maintenance-event information, or a hosting or backup provider storing deployment data. These recipients depend on that installation's configuration; NNet-Tech does not select a required external agent or AI provider. Ask your administrator which services are connected, what they receive and how long they retain it.

NNet-Tech does not sell Google user data or disclose it to advertisers, data brokers or information resellers. Optional sharing with administrator-chosen services must be limited to the disclosed, user-facing maintenance features, with the user's consent and in accordance with Google's Limited Use requirements. Administrators must apply those requirements to the services they connect.

If you voluntarily include Google-related information in a support request, NNet-Tech support and the email providers delivering that message receive what you send. This is separate from the Google account connector. Send only the information needed for support and redact private Calendar content; never send passwords or OAuth tokens. NNet-Tech has no automatic or remote access to your installation's Google data.

GitHub Pages and Cloudflare serve this informational website. They may process website request information as described below; the Google account connector does not send them Calendar records or user OAuth tokens.

Agents and AI

Maintenance provides interfaces, including MCP, that let tools and assistants request maintenance scheduling and inspect permitted workflow information. The installation's administrator chooses and authorises those tools. The software does not require a particular assistant, model provider or external memory service. Any provider receiving Google-derived information is covered by the optional-service disclosure above and must be identified by that installation's administrator.

The Google account connector currently uses Google user data to provide the connected maintenance workflow, not to develop, improve or train general-purpose or non-personalised AI or machine-learning models. NNet-Tech does not receive that data through the integration and does not use it for model training. Google user data must not be used for advertising or model training by administrator-connected services contrary to Google's Limited Use requirements.

Agentic Tools’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Data security

The current integration stores user-specific OAuth tokens and workflow state on the deployment's infrastructure, with filesystem access controls. Connections to Google use HTTPS. User tokens are kept separate from the public website and distributed source files. No storage or transmission method can guarantee absolute security.

Retention and deletion

Retention is controlled by each installation's administrator. OAuth credentials remain in that environment while the connection is enabled, until replaced or removed there. Revoking access at Google and removing the local credentials are separate steps.

The maintenance server's automatic diagnostic cleanup uses configurable defaults: 30 days for detailed execution-event payloads and successful notification delivery history, and 90 days for confirmed Calendar readback observations of completed or cancelled work. A daily sweep runs while the server is operating; execution payloads also have size limits. Older installed versions need an update to use these settings.

This cleanup does not erase the entire maintenance history. Jobs, Calendar references in job or agent history, signed approvals, source reports and recovery or audit evidence remain until the administrator retires those records or removes the installation. Active work and unresolved Calendar failures are excluded from Calendar observation expiry.

Agent conversations, memory services, diagnostic log files and backups are managed by the software and infrastructure selected by the administrator. They have separate retention settings and are not erased by deleting server records. Ask your administrator for the periods configured in your environment and to remove associated copies when requesting deletion.

To request deletion from your installation, contact its administrator. NNet-Tech cannot remotely erase data held in your environment. For information you have separately provided to NNet-Tech, such as a support email, contact support@nnet.tech. NNet-Tech will confirm the affected records, remove information that can be deleted, and explain any records or backup copies that must be retained and why. Avoid sending passwords, tokens or other credentials in your request.

Calendar events are also stored in your Google Calendar. Removing the connection or deleting the app’s local records does not automatically delete those events. You can manage them directly in Google Calendar.

Disconnecting the app

You can revoke access through your Google Account connections. Select Agentic Tools and remove its access. If the OAuth app has not yet been renamed, it may still appear as agentic-calendar.

Revocation prevents the app from obtaining further access through that authorisation. It does not automatically erase previously stored records, delete calendar events, or cancel work already approved in the maintenance system. Contact your deployment's administrator if you also want to pause maintenance or remove stored application data.

This website

The informational website does not set application cookies, use analytics or advertising scripts, embed third-party content, or run a Calendar connection in your browser. Fonts and visual assets are served with the site. Following an external link takes you to a service with its own privacy practices.

This website is hosted on GitHub Pages. Cloudflare provides DNS for the domain and may also provide website delivery and protection when its proxy is enabled. Hosting and delivery providers process routine request information, including IP addresses, to deliver and secure the site. Their handling is described in the GitHub General Privacy Statement and Cloudflare Privacy Policy. Their own retention practices apply to those hosting records; the maintenance server's local cleanup settings do not control them.

Changes and contact

This policy will be updated when data handling changes or a new integration is introduced. Material changes will be communicated to affected users before they take effect, and additional Google permissions will be requested through Google’s authorisation process when needed. The date at the top identifies the current version.

For privacy questions, corrections or requests, contact NNet-Tech at support@nnet.tech.