Privacy Policy
This Privacy Policy explains how Jumich Systems handles personal information and, specifically, how its AGUM deployment accesses, uses, stores, shares, and deletes Google user data.
AGUM requests standard account identity scopes (openid, email) and the Google Drive drive.file scope. It does not request Gmail, Calendar, Contacts, or unrestricted access to all files in Google Drive as part of this deployment.
1. Who we are and what this policy covers
Jumich Systems designs and deploys AI agents and operational systems. AGUM is an Executive Operations and Implementation Agent used as an internal Jumich Systems deployment and proof of capability.
This policy applies to the Jumich Systems website and to Google user data accessed through AGUM's approved Google OAuth connection. If Jumich Systems later introduces materially different products, scopes, or data practices, this policy will be updated before those practices are used.
2. Google user data we access
| Permission/data | What it permits | Why it is used |
|---|---|---|
| openid and email | Basic Google account identity information, including the connected account's email address and account identifier. | To verify that the intended Google account has been connected to AGUM. |
| https://www.googleapis.com/auth/drive.file | Per-file access to Google Drive files and folders created by the application or explicitly made available to it. | To create and operate approved production trackers, folders, documents, and other files used in Jumich Systems workflows. |
Depending on the user-authorized file and feature being used, AGUM may process file metadata (for example, file names, IDs, locations, modification timestamps, and links) and file contents required to perform the requested workflow.
AGUM is not designed under this scope to browse or discover a user's entire Google Drive. Existing files outside the app-authorized set are not treated as accessible merely because they exist in the connected account.
3. How we use Google user data
Jumich Systems uses Google user data only to provide, secure, verify, and improve the user-facing operational features that the connected user has requested or approved. Current uses may include:
- verifying the identity of the connected Google account;
- creating approved Google Drive folders, Google Sheets trackers, or Google Docs;
- reading or updating app-created or explicitly authorized files as necessary for the requested workflow;
- retrieving file IDs, links, metadata, and status evidence;
- maintaining approved operational records and audit/change logs;
- detecting failures, preventing unauthorized actions, and troubleshooting the integration.
Google user data is not used for advertising, sold to data brokers, or used to build unrelated user profiles.
4. Storage and security
Google files created through AGUM remain in the connected user's Google account unless a user-approved workflow creates another authorized copy. The public Jumich Systems website does not itself store Google Drive file contents.
For the current deployment, OAuth credentials are stored server-side in a restricted credential location and are not exposed through this website. Access tokens, refresh tokens, authorization codes, and OAuth client secrets are treated as confidential authentication material and are not intended to appear in ordinary chat, public logs, or webpage content.
Jumich Systems applies least-privilege design, approval boundaries, credential access controls, and verification checks appropriate to the deployment. No security measure can guarantee absolute security, but we work to reduce unnecessary access and exposure.
6. AI processing and Google data
AGUM is an AI-assisted operational system. When an approved workflow requires analysis, drafting, classification, extraction, or another AI-enabled operation on Google user data, only the data reasonably necessary for that requested feature should be processed.
Google user data obtained through Google APIs is not used by Jumich Systems for advertising or to train a generalized Jumich Systems model unrelated to the user's requested functionality.
Jumich Systems' use and transfer of information received from Google APIs is intended to comply with the Google API Services User Data Policy, including its Limited Use requirements.
7. Retention and deletion
We retain Google user data only for as long as reasonably necessary to provide the approved workflow, maintain required operational records, meet legal obligations, or resolve security issues.
- OAuth credentials: retained while the connection is active and removed locally when the approved revocation process is completed.
- Google Drive files: remain in the user's Google account until the user or an explicitly authorized workflow changes or deletes them.
- Operational/audit records: may be retained where reasonably necessary to preserve accountability, verification history, or legal/security records.
Revoking Google access stops future API access but does not automatically delete Google files that were previously created in the user's account.
8. Your choices and controls
A connected user may revoke Jumich Systems/AGUM access through their Google Account's third-party access or security controls. Users may also request assistance with disconnecting the integration or deleting data controlled directly by Jumich Systems.
Where a file lives in the user's own Google Drive, the user retains normal Google Drive controls over that file, subject to Google's platform behavior and any permissions the user has set.
9. Website data
The initial Jumich Systems website is a static informational website. At launch, it does not include advertising trackers, behavioral analytics, account registration, or a web contact form. It may be delivered through infrastructure providers that process ordinary technical request data such as IP address, request headers, timestamps, and security signals as necessary to deliver and protect the site.
If we later add analytics, forms, accounts, cookies, or other data collection, this policy will be updated before those practices are used where required.
10. Children
Jumich Systems' business and operational services are not directed to children. We do not knowingly design AGUM's Google integration for use by children.
11. Changes to this policy
We may update this policy as our services, legal obligations, or Google API usage change. Material changes affecting how Google user data is accessed, used, stored, or shared will be reflected here before the new practice is relied upon where required.
The effective date at the top of this page identifies the current version.
12. Contact
For privacy or Google-data questions, contact:
Jumich Systems
Email: privacy@jumichsystems.com
Website: https://jumichsystems.com/
For additional information about Google's own API data requirements, see the Google API Services User Data Policy.