subprocessors data sharing · Privacy Policy
Trata policy finding
“ If you sign in to the Services using “Sign in with Google” , Google acts as an identity provider and we use Supabase Auth to complete sign-in. This section describes how we access, use, store, and share Google user data for that purpose, as required for applications that use Google OAuth. Data accessed: Through Supabase’s Google OAuth integration, we receive the categories of information Google makes available for sign-in and account linking. This typically includes your Google account subject identifier, email address, name, profile image URL, and email verification status. We use Google solely for authentication and account creation; we do not use this sign-in flow to access your Google Calendar, Gmail, Google Drive files, contacts, or other Google product data. Data usage: We use the Google-provided information to authenticate you, create and maintain your Trata account, associate your session with your identity, secure access to the Services, recover or manage your account where applicable, and communicate with you about your account in line with this Policy. We do not use Google sign-in data for unrelated advertising profiling by third parties. Data sharing: Google processes sign-in according to Google’s terms and privacy policy. Supabase provides authentication infrastructure for us and may process OAuth tokens and profile attributes on our behalf as described in Supabase’s documentation and privacy practices. ”
- Document
- Privacy Policy
- Captured
- 2026-09-25
- Location
- § 3 (Google sign-in and Google user data)
- Snapshot SHA-256
- 210a3773009b7a8cab6681e75a37842bae19a39564a2edf3ce478430d5f5a222
Informational only, not legal advice. Terms change; verify the source and capture date.