Privacy Policy

Effective date: 16 October 2026 · master.inventory-gateway.com

i-Gateway Gen3 connects Google Drive files with inventory, audit, and customs document processing for authorized organizations and users.

This policy explains how this deployment handles Google account information, files, and related processing records. Access to business data is managed by your organization's application administrators.

1. Information accessed and collected

Application accounts: names, usernames, account identifiers, and assigned permissions. Passwords are stored as hashes, and session cookies support sign-in and form security.
Google account information: the connected account's email address and Google account identifier, used to verify the account authorized by the administrator.
Google Drive data: file and folder identifiers, names, file types, folder membership, and the contents of files used for configured data loaders.
Authorization credentials: OAuth access and refresh tokens used to maintain the authorized Drive connection without repeatedly requesting sign-in.
Operational records: file names, processing times, row counts, results, error details, and application user identifiers associated with these operations.

2. How the information is used

The application uses this information to verify the configured Google account, count and list pending files, save files to configured Drive folders, retrieve files for processing, import business records into configured databases, move source files to configured archive folders, and maintain processing history and troubleshoot failures.

The Drive permission requested allows broad file access because configured folders may contain files created outside i-Gateway. The integration uses that access for the file and loader operations described here. Google account authorization is separate from signing in to an i-Gateway application account.

3. Storage and security

OAuth access and refresh tokens are encrypted in the application's database. Application access is controlled through authenticated accounts and configured permissions. Production OAuth uses HTTPS and validates the authorization request and the connected Google account.

Downloaded files may be held on the application server for processing or retry. Imported business records and processing histories are stored in the application's local database or the organization's configured cloud database, according to the module being used.

4. Sharing and permitted use

Data is processed by Google Drive, the application's hosting infrastructure, and the organization's configured databases as needed to provide these features. Business records and histories are available to authorized application users and administrators according to their permissions.

Google user data is not sold or used for advertising. Google Workspace data is not used to develop, improve, or train generalized artificial intelligence or machine-learning models. Administrative access to data is limited to supporting the requested service, security, and applicable obligations.

Google API data is handled under the Google API Services User Data Policy and its Limited Use restrictions. Use of Google Workspace data also follows the Google Workspace user data and developer policy.

5. Retention and deletion

Working files may be retained while an operation is pending or requires a retry. Imported records, archived Drive files, and processing histories remain until an authorized administrator removes them under the organization's retention requirements. Repeated processing of the same file does not automatically delete earlier history.

To request removal of stored authorization credentials or application-held data, contact the administrator using the address below. Identify the account or records concerned; do not send passwords, tokens, or confidential file contents in your initial request. Records that must be retained for operational or applicable legal obligations are handled with the responsible organization.

6. Revoking Google access

You can revoke i-Gateway's access through your Google Account connections. Revocation stops further authorized Google API access once existing access credentials are no longer valid. It does not automatically delete files already in Drive or records previously imported into the application's databases. Contact the administrator to request deletion of those records or stored credentials.

7. Contact and policy updates

For privacy questions, access requests, or deletion requests, contact the integration administrator at v2.validates@gmail.com.

This page will be updated when the application's data handling changes. The effective date above identifies the current policy.