Privacy & Consent
When you use SingleSign to sign in to an app, you're in control of what information that app can access. This article explains how consent works and what you can do to protect your privacy.
What is consent?
Consent is the step where you approve what an app can access. The first time you sign in to an app with SingleSign, you'll see a consent screen listing the specific categories of data (called "scopes") the app is requesting. You can choose to allow or deny the request.
What are scopes?
Scopes are categories of data that an app can request access to. Each scope corresponds to a specific type of information. An app can only access the scopes you approve.
Here's what each scope means:
| Scope | What the app receives |
|---|---|
| openid | Your unique identifier (a random ID — not your password) |
| profile | Your display name |
| Your email address | |
| phone | Your phone number |
| address | Your mailing address |
What can apps see?
Apps can only see the information you explicitly approve. For example:
- If an app requests
emailandprofile, it will receive your email address and display name — nothing else. - If an app only requests
openid, it will receive a unique identifier that confirms your identity, but no personal details.
Apps never receive your SingleSign password.
How to revoke access
If you no longer want an app to have access to your information:
- Sign in to your SingleSign account.
- Go to Account → Privacy → Connected Apps.
- Find the app you want to disconnect.
- Click "Revoke" next to the app.
- The app will immediately lose access to your data.
If you sign in to that app again in the future, you'll be asked to re-approve permissions. Learn more about managing connected apps.
Tips for protecting your privacy
- Only approve scopes you're comfortable with. If an app is asking for more information than you think it needs, you can deny the request.
- Review connected apps regularly. Go to your Connected Apps page periodically to make sure you recognize and still use all the apps listed.
- Revoke access for apps you no longer use. There's no downside to revoking — you can always re-authorize later.
Data safety
Here's what you can count on with SingleSign:
- SingleSign never shares your password. Your password is securely hashed and never transmitted to any app.
- Apps only get what you approve. No app can access data beyond the scopes you consented to.
- You can revoke access at any time. Revoking is instant and permanent until you re-authorize.
Last updated: 2026-02-16
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- the Scopes & Consent docsHow to request scopes, what data each scope grants, the consent UI, and the principle of least privilege.
- Google Sign-In alternativeSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- Managing Connected Apps, step by stepHow to view, review, and revoke the apps connected to your SingleSign account.
- Secure sign-in for every platform.SingleSign is a free identity provider with OAuth 2.0 and OpenID Connect for developers, and per-app consent and instant revocation for everyone signing in.
- Identity provider features, in fullThe identity provider features SingleSign ships: OAuth 2.0 and OpenID Connect endpoints, PKCE, scopes and consent, MFA, and instant revocation.
- Privacy PolicyHow SingleSign collects, uses, and protects your personal information.
- free identity providerSingleSign pricing in one line: sign-in is free, with no monthly-active-user meter. See exactly what is included, and what SingleSign Mail costs for businesses.
- Identity provider alternativesIdentity provider alternatives, by the provider you are leaving: what actually has to change in your code, and what does not.
- SingleSign vs Auth0SingleSign vs Auth0 compared on the difference that matters: who owns the account. A side-by-side table, then the three cases where each one is the right call.
- Okta comparisonSingleSign vs Okta: Okta is built for workforce identity inside a company, SingleSign for consumer sign-in across applications.
- Firebase Auth comparisonSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.