Information needed to provide connections
Techrace uses developer identity, project membership, customer identifiers and encrypted provider credentials to deliver authorized integrations. Connected email data is accessed only for the functions requested by an authorized application.
Google account data
Google sign-in requests basic identity permissions only. Gmail access uses a separate consent flow. Google user data is not sold, used for advertising, or used to train generalized AI models. Our intended production use is limited to the user-facing integration features authorized by the user, consistent with Google's API Services User Data Policy and Limited Use requirements.
Control and deletion
Customers can disconnect integrations through their software provider; developers can offboard customer records and revoke keys. Disconnect removes locally stored credentials. Provider-side consent revocation is a separate control in the Google or Microsoft account. Queued mail bodies are cleared after terminal operation status; operational metadata follows the retention policy selected for production.
Production requirements
The operating company must publish its identity, legal basis, regional rights, subprocessors, retention periods and privacy contact before launch. This pre-launch page is not a finalized legal notice.