Who is behind Agentic Tools
Agentic Tools is developed by NNet-Tech. Contact NNet-Tech support at support@nnet.tech. This policy covers this informational website and explains how the Calendar helper handles data when used with the self-hosted maintenance server. The server is being developed for publication through NNet-Tech on GitHub; users will download it and run their own installations.
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 current Calendar integration; additional integrations will be covered as they are introduced.
Google Calendar data the helper accesses
The integration requests these permissions:
- Calendar list, read only: information about the configured calendar, including its identifier, name, time zone and access role, to identify it and confirm the app can create events there.
- Calendar availability: free/busy time ranges for the calendars configured for conflict checking. Availability checks use occupied times rather than the titles or descriptions of unrelated appointments.
- 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 routine event operations to events it identifies as managed maintenance events. These implementation checks do not narrow the permission granted by Google.
The helper stores OAuth access and refresh tokens in your installation so it can continue working after the initial authorisation. Your installation talks directly to Google's APIs; this website does not receive or store those tokens.
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.
Agents and AI
An AI assistant configured by the installation's administrator can help review maintenance work and select suitable actions. Scheduling results, maintenance-event information and workflow records may be included in the assistant’s context, tool results, conversation history and retained operational memory. Human operators can inspect those records for support and troubleshooting. If the administrator selects an external model or memory service, that service may receive this information under the administrator's configuration and its own data-handling terms. The maintenance system checks the configured booking rules and records the resulting actions.
Google user data is used to provide this connected workflow. It is not used to develop, improve or train general-purpose or non-personalised AI or machine learning models. We do not sell Google user data or use it for advertising.
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.
Sharing and security
Google processes authorisation requests and Calendar API operations. Your installation processes scheduling and maintenance records on the infrastructure you choose. Its authorised administrators may access those systems to operate and support the integration. NNet-Tech does not automatically receive this information. Administrators must configure connected services consistently with the Google API Services User Data Policy, including Limited Use.
The current integration stores credentials and workflow state on the deployment's infrastructure, with filesystem access controls. Connections to Google use HTTPS. Credentials are kept separate from the public website and its source files. No storage or transmission method can guarantee absolute security.
If you contact NNet-Tech support by email, your message and address are processed by the email services involved in delivering and replying to that message.
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.