Tech Provider

Tech Provider

A secure OAuth 2.0 authorization broker that connects Google Workspace and YouTube APIs to authorized partner business applications — so independent SaaS products can integrate Gmail, Google Calendar, Google Drive, and YouTube into their customer-support, productivity, and video-publishing workflows.

Learn more Privacy Policy

What is Tech Provider?

Tech Provider operates a centralized OAuth 2.0 authorization broker available at oauth.techprovider.com.br. The platform acts as a trust layer between Google's identity systems and smaller partner applications — mostly multi-channel customer support, CRM, helpdesk, and video-publishing tools — that need to access their users' Gmail, Google Calendar, Google Drive, or YouTube account on the user's behalf.

Rather than each partner application maintaining its own Google Cloud project and going through OAuth verification individually, partners delegate the authorization handshake to Tech Provider, which holds verified credentials and forwards the resulting tokens back to the originating application.

Tech Provider is operated from Brazil. The legal entity, contact information, and data-handling practices are described in the Privacy Policy and Terms of Service.

How it works

  1. Initiate. A partner application redirects the user to oauth.techprovider.com.br with a partner-scoped state token identifying the originating application and the requested scopes.
  2. Consent. Tech Provider presents Google's standard OAuth consent screen, identified as Tech Provider, with the exact scopes requested by the partner application.
  3. Approve. The user reviews the permissions on Google's domain and grants or denies access. Tech Provider never sees the user's Google password.
  4. Exchange. Tech Provider exchanges the authorization code for access and refresh tokens.
  5. Forward. Tokens are returned to the partner application that initiated the request, over an authenticated and encrypted channel. The partner application stores and uses the tokens on the user's behalf.

Tech Provider does not maintain a long-term store of user content. Tokens transit the platform during the redirect and are not retained as plaintext beyond what is required to complete the authorization flow.

What data we access — and what we do with it

Depending on the partner application and the scopes selected during consent, Tech Provider may relay tokens authorizing access to the following Google APIs:

  • Gmail (gmail.send, gmail.modify, gmail.readonly) — allows partner customer-support and CRM applications to send and read emails on the user's behalf, so customer conversations can be unified inside the partner's helpdesk inbox.
  • Google Calendar (calendar.events) — allows partner applications to read and create events on the user's calendar, typically to schedule meetings with the user's contacts.
  • Google Drive (drive.file) — allows partner applications to upload or read files the user explicitly opens or creates within the partner application.
  • YouTube (youtube.readonly, youtube, youtube.upload, yt-analytics.readonly) — allows partner video-publishing and social-media tools to list channels, upload videos, manage metadata and comments, and read analytics on the user's YouTube account. Use of YouTube data is additionally governed by the YouTube Terms of Service.
  • Profile / email (openid, profile, email) — identifies the user to the partner application by name and primary email address.

You may revoke a partner application's access to any Google or YouTube scope at any time at Google security settings » Apps with access.

Limited Use disclosure

Tech Provider's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Specifically, Tech Provider does not:

  • Sell Google user data;
  • Use Google user data for advertising;
  • Use Google user data to train generalized or generative AI/ML models;
  • Allow humans to read user data, except (a) with the user's affirmative consent for a specific purpose, (b) for security investigations or to comply with applicable law, (c) for limited operational debugging where data is aggregated and anonymized whenever possible.

Trust & security

HTTPS-only transport

All OAuth flows and partner callbacks are served over TLS. Tokens are never exposed in cleartext on the wire.

Stateless relay

Tech Provider does not persist user content (email bodies, calendar entries, file content) on its own infrastructure. Authorization tokens are forwarded to the partner application that initiated the request.

LGPD aware

Tech Provider is operated from Brazil and observes the Lei Geral de Proteção de Dados (LGPD). Users may exercise data access, correction, and deletion rights via the contact below.

Scope minimization

Partner applications request the narrowest scope that satisfies their use case. Sensitive scopes are reviewed before a partner is approved on the platform.

Contact

Questions about Tech Provider, this platform, or how your data is handled?

Email: admin@zdg.com.br
Operated from: Brazil

For data-protection requests under LGPD or GDPR, please email the address above with the subject line "Data request" and we will respond within 30 days.