OHORUS HUB
HomeContact us ↗

ORUS HUB / Privacy Policy

GMAIL API · INTERNAL USE

Privacy Policy

How ORUS HUB accesses, uses, stores, and protects information through its owner-authorized Gmail integration.

Effective date: October 25, 2026 · Version 1.0

On this page

1. Operator and contact2. Google data accessed3. Purpose and use4. Storage and retention5. Sharing and transfers6. Revocation and deletion7. Security and changes
Current integration: read-only

The Gmail account owner authorizes the ORUS HUB integration. The current implementation retrieves inbox metadata; it does not send emails or access message bodies in its implemented workflow.

1. Who operates this integration

ORUS HUB is an owner-operated, internal business research and commercial-workflow project. Questions or requests concerning this Gmail integration may be sent to orushub.br@gmail.com.

This policy applies to the ORUS HUB application using Google OAuth 2.0 and the Gmail API. It does not describe unrelated Gmail connections or external services that may be used independently.

2. What Google data we access

The application requests the https://www.googleapis.com/auth/gmail.readonly permission. Under Google's permission model, this is a restricted scope that can technically allow viewing Gmail messages and settings. The currently implemented integration uses the permission in a narrower way:

  • Verifies the authorized Gmail account email address through the account profile.
  • Retrieves up to 20 recent inbox message identifiers and related thread identifiers.
  • Retrieves selected message headers (From, To, Subject, Date), internal date, and read/unread labels.
  • Does not request, download, or store message bodies or attachments as part of its current connector workflow.
  • Does not send, draft, modify, or delete Gmail messages.

If we add Gmail features in the future, we will review the scope requirements, update this policy as needed, and obtain the necessary consent before using new permissions or data.

3. Why we use this information

We use the limited information above solely to verify that the email integration is functioning, review inbox state, and prepare internal business correspondence workflows subject to human control. No automatic prospect outreach is enabled through this connector.

ORUS HUB's current Gmail connector does not transmit Gmail-derived metadata to generative AI models or external marketing tools. We do not use information obtained from the Google APIs for targeted advertising, selling personal information, or generalized AI model training.

4. Storage and retention

The connector stores a local snapshot of inbox metadata on a privately administered server, in a restricted-access JSON file. Each manual synchronization replaces the previous snapshot. At present, there is no automated retention/deletion schedule; data may remain until replaced or manually deleted.

OAuth client credentials and authorization tokens are kept in restricted-access files on the operator's local computer and/or server. File-system permissions limit access to authorized administrators. Server-side encryption of these existing token files is not yet implemented; this remains a security-hardening requirement before broader production use.

Mail messages remain in Gmail and are not changed by the read-only integration. Once these pages are made public, standard web-server access logs may record technical connection data (such as IP address, requested URL, timestamp and user agent) for operational and security purposes.

5. Sharing, providers, and transfers

Google supplies the authentication and Gmail API services. The system runs on infrastructure operated by a hosting provider, which processes data as necessary to host the server. The current connector does not disclose Gmail-derived metadata to sales prospects, advertisers, data brokers, or other external recipients.

We follow the Google API Services User Data Policy, including the Limited Use requirements applicable to data obtained through Google APIs. Access, use, disclosure, or transfer of Google user data will remain limited to the features and purposes described here, unless the authorized user provides additional consent or disclosure is required by applicable law.

6. Access revocation and deletion requests

The account owner can revoke ORUS HUB's access at any time from Google Account third-party connections. Revoking access prevents further authorized requests once existing access tokens expire or are invalidated, but does not automatically remove previously stored local metadata or local credential files.

To request deletion of local inbox snapshots, stored OAuth credentials, or other information associated with this integration, contact orushub.br@gmail.com. Requests are handled manually by the operator; no automatic self-service deletion mechanism is currently provided.

7. Security, children, and changes

This integration is intended for the authorized operator's business use, not for children or public user registration. The current connector operates with read-only access and restricted file permissions. Additional safeguards, including token encryption at rest and operational retention controls, remain to be completed before expanding production usage.

We may revise this policy when the application's functionality, permissions, data processing, or operational controls change. Any new use of Google user data that was not disclosed when authorization was originally granted will require an updated disclosure and, where applicable, new user consent. The effective date and version will be updated when changes are published.

OperatorORUS HUB (owner-operated internal project)
Contactorushub.br@gmail.com
Current Gmail scopegmail.readonly (restricted)
© 2026 ORUS HUB · Internal operations
HomeContact