Social Login
Social Login & OAuth
Sign in to Contextium securely using your existing Google or GitHub account.
Supported Providers
Contextium supports the following OAuth providers:
Sign in with your Google account:
- Personal Gmail accounts
- Google Workspace accounts
- G Suite accounts
GitHub
Authenticate with your GitHub account:
- Personal GitHub accounts
- GitHub Enterprise accounts
- GitHub organizations
Benefits of Social Login
Convenience
- No need to create and remember another password
- One-click sign-in
- Automatic email verification
- Profile information imported automatically
Security
- OAuth 2.0 industry-standard protocol
- No password stored on Contextium servers
- Two-factor authentication inherited from provider
- Reduced risk of password reuse
- Provider-level security protections
Account Management
- Centralized access control
- Easy account recovery
- Automatic profile updates
- Unified security settings
How Social Login Works
First-Time Sign Up
- Visit contextium.io/signup
- Click Continue with Google or Continue with GitHub
- You'll be redirected to the provider's login page
- Log in to your Google or GitHub account (if not already logged in)
- Review the permissions Contextium requests
- Click Authorize or Allow
- You'll be redirected back to Contextium
- Your account is created automatically
- Complete your profile setup
Subsequent Sign Ins
- Visit contextium.io/login
- Click Continue with Google or Continue with GitHub
- You'll be signed in automatically (if still logged in to provider)
- Or briefly redirected to provider to confirm
Permissions Requested
Contextium requests minimal permissions from OAuth providers.
Google Permissions
Contextium requests access to:
- Email address - To create and identify your account
- Basic profile information - Display name and profile picture
- Email verification status - To confirm your email is verified
Contextium does NOT access:
- Your Google Drive files
- Your Gmail messages
- Your Google Calendar
- Your Google Contacts
- Any other Google services
GitHub Permissions
Contextium requests access to:
- Email address - To create and identify your account (including private email if primary is hidden)
- Basic profile information - Username, display name, and avatar
Contextium does NOT access:
- Your repositories (public or private)
- Your code
- Your organizations
- Your followers/following
- Any other GitHub data
Linking Accounts
Add Social Login to Existing Account
If you created your account with email/password, you can add social login:
- Navigate to Settings → Connected Accounts
- Click Connect Google or Connect GitHub
- Authorize the provider
- Social login is now enabled
You can now sign in with either:
- Your email and password
- Your connected Google account
- Your connected GitHub account
Multiple Accounts
- Each email address can only be associated with one Contextium account
- If your Google email differs from your GitHub email, you can link both to the same Contextium account
- If you try to sign in with a provider email that matches an existing account, you'll be prompted to link accounts
Unlinking Accounts
Remove Social Login
- Navigate to Settings → Connected Accounts
- Find the provider you want to remove
- Click Disconnect
- Confirm the action
Important:
- If social login is your only sign-in method, you must set a password before unlinking
- Navigate to Settings → Security → Set Password first
Security Considerations
Provider Security
Your security depends on your OAuth provider:
- Enable two-factor authentication on your Google or GitHub account
- Use a strong password for your provider account
- Review authorized apps regularly in your provider settings
- Revoke access if you suspect unauthorized use
Revoking Access
You can revoke Contextium's access from your provider:
Google:
- Visit myaccount.google.com/permissions
- Find Contextium in the list
- Click Remove Access
GitHub:
- Visit github.com/settings/applications
- Find Contextium in the Authorized OAuth Apps
- Click Revoke
Note: Revoking access will not delete your Contextium account, but you won't be able to sign in via that provider until you reauthorize or set a password.
Switching Between Providers
You can switch your primary sign-in method:
- Link the new provider in Connected Accounts
- Test sign-in with new provider
- Optionally unlink old provider
- Or keep both linked for flexibility
Account Deletion with Social Login
Deleting your Contextium account:
- Removes your account data from Contextium
- Does NOT affect your Google or GitHub account
- OAuth authorization is automatically revoked
- No data is shared back to the provider
See Account Security for details.
Email Address Changes
If you change your email in your OAuth provider:
Google:
- Contextium will use the new email on next sign-in
- Update may take up to 24 hours
GitHub:
- Contextium will use your primary GitHub email
- If you've hidden your email, we'll use your GitHub-provided proxy email
Troubleshooting
"Email Already in Use"
This means a Contextium account already exists with that email:
Solution:
- Sign in with email and password
- Navigate to Settings → Connected Accounts
- Link the social account
Or use password reset if you forgot your password.
"No Email Found"
Your OAuth provider account must have a verified email:
Google:
- Verify your email in Google account settings
- Ensure email verification is complete
GitHub:
- Add and verify an email in GitHub settings
- Set it as your primary email
- Or ensure your private email feature is enabled
"Authorization Failed"
Common causes:
- You clicked "Deny" or "Cancel" on the provider page
- Your provider account lacks a verified email
- Network connectivity issues
- Browser blocking third-party cookies
Solution:
- Try again and click "Allow" or "Authorize"
- Ensure you have a verified email
- Try a different browser
- Allow third-party cookies for contextium.io
"Account Not Found After Sign-In"
If you signed in but can't access your account:
- Clear your browser cache and cookies
- Try signing in again
- Contact support@contextium.io if issue persists
Privacy & Data Protection
What Contextium Stores
From social login:
- Email address
- Display name
- Profile picture URL (not downloaded, linked)
- OAuth provider name (Google or GitHub)
- OAuth provider user ID (for account linking)
What Contextium Does NOT Store
- Your provider password
- OAuth access tokens (discarded after verification)
- Any data from your provider account
- Your provider account activity
- Your contacts or connections
GDPR Compliance
- You can request your data at any time
- You can delete your account and all data
- OAuth tokens are not stored long-term
- Minimal data collection principle applies
See Privacy Policy for complete details.
Best Practices
For Individuals
- Enable 2FA on your OAuth provider - Protects both accounts
- Review provider permissions regularly - Audit authorized apps
- Use strong provider passwords - Foundation of security
- Link backup sign-in method - Set a password as backup
- Monitor sign-in activity - Review login notifications
For Teams
- Require SSO instead - Use enterprise Single Sign-On (Business plan+)
- Enforce 2FA - At provider level if using OAuth
- Review member accounts - Ensure appropriate sign-in methods
- Centralized identity management - Consider SSO for better control
- Security policies - Align with organization standards
Enterprise SSO vs. OAuth
For business teams, consider Single Sign-On instead of OAuth:
OAuth Social Login:
- Individual accounts
- Personal Google/GitHub accounts
- No centralized control
- Free on all plans
Enterprise SSO:
- Organizational accounts
- Company identity provider
- Centralized access control
- Requires Business or Enterprise plan
See SSO Configuration for details.
Need Help?
Documentation
Support
- Email: support@contextium.io
- Live chat: Available in-app
- Status: status.contextium.io (for OAuth provider issues)