This page explains how JAMz AI uses Google Sign-In. It is public so prospective users, customers and Google reviewers can understand our identity, the information requested at sign-in and the purpose of that information.
1. JAMz AI identity and service
JAMz AI Connect is a casting-technology service for professional casting teams. It helps users organise projects, roles, applications, talent profiles, auditions, shortlists, client sharing, websites and related casting workflows. JAMz AI is headquartered in Dahisar, Mumbai, Maharashtra, India.
2. Why we offer Google Sign-In
Google Sign-In lets a user authenticate with their existing Google Account instead of creating and managing a separate JAMz AI password. It helps us establish the user's account, protect access and associate the correct user with the correct JAMz AI workspace.
3. Sign-In scopes and purpose
| Scope | Information received | Why JAMz AI uses it |
|---|---|---|
openid | Google OpenID identifier | To establish a unique authenticated identity and maintain a secure session. |
email | Primary Google email address | To create and identify the account, send essential service/security messages and provide support. |
profile | Basic profile information, such as name and profile image where made available | To display a recognisable user profile within JAMz AI. |
JAMz AI does not use Google Sign-In to access Google Drive, Gmail, Google Calendar, Google Contacts or other Google data. We do not describe any sensitive or restricted Google API scope on this page. If that changes, we will update our product notices and Privacy Policy before requesting the additional permission.
4. How Google user data is handled
Authentication only
Google identity data is used to authenticate, create and maintain a JAMz AI account.
No sale or advertising use
We do not sell Google user data or use it for interest-based advertising.
Clear disclosure
Our Privacy Policy explains access, use, storage, sharing, retention and deletion practices.
Google user data is disclosed only where necessary to provide the Service, comply with law, investigate a security incident, or where a user directs or consents to that disclosure. The full details are in our Privacy Policy.
5. Your choices
You can choose whether to use Google Sign-In. If you create or access a JAMz AI account with it, you can request access, correction or deletion of your personal data by emailing jamz.techconnect@gmail.com. If you believe your Google Account or JAMz AI account has been compromised, secure your Google Account immediately and contact us.
6. Public policy links
JAMz AI maintains public pages describing its service and data practices. These links should be used consistently in the production OAuth consent screen configuration:
7. OAuth verification status
JAMz AI does not claim to be Google-certified, Google-approved or OAuth-verified unless Google has confirmed verification for the applicable production Google Cloud project. This website provides the public documentation needed for review; verification must still be completed in Google Cloud Console by the project owner or editor, using a verified authorised domain and the final production consent-screen configuration.
8. Review readiness
Before submitting the production app, the JAMz AI team should confirm that the app name, logo, support email, homepage, Privacy Policy, Terms, authorised domains, redirect URIs, JavaScript origins and scopes in Google Cloud Console match the live product. Any material product or scope change should be reviewed before it is released.
For authentication questions or a verification-related enquiry, contact jamz.techconnect@gmail.com.
9. Related policy documents
Read the Privacy Policy for our personal-data practices, read the Terms and Conditions for Service rules, and visit Trust & Security for our broader security and privacy commitments.
10. Statement of accuracy
JAMz AI intends this page to accurately describe the live product. If the live Google Sign-In implementation or requested scopes differ from this description, the product configuration and this page must be updated before production verification is requested.
Verification-ready public information: Homepage, Privacy Policy, Terms and Conditions, support contact, data-request route and Google Sign-In data-use disclosure are available without sign-in.