What all we store
Once the selected identity provider verifies your user and gives the necessary information back to Playground, we store some basic information. In essential information, we specifically store Firstname, Lastname and Email Address.
This information is being used to set up your user at the time of signup and also matching your user at the time of login only.
Sign-in records
Playground keeps a login history so admins can see and report on sign-ins:
| Stored | Why |
|---|---|
| Time of the attempt, and whether it succeeded | Audit and reporting |
| Sign-in method used (Google, Salesforce, SAML 2.0, OpenID Connect) | Audit and reporting |
| IP address | Detecting unusual activity |
| For failed attempts: the email that was tried and a short reason | Helping admins fix sign-in problems |
Settings admins save
When an admin connects Playground to other systems, we store what is needed to make the connection work:
| Stored | Protection |
|---|---|
| Identity provider details for single sign-on: entity ID, sign-in URL and signing certificate | Public values, stored as they are |
Allowed email domains (for example company.com) | Stored as they are |
| Single sign-on identity link: the identity provider's issuer and the person's stable ID, saved at their first single sign-on sign-in | Used only to recognise the same person at later sign-ins |
| OpenID Connect client secret, request-signing private key | Encrypted, never shown again |
| Bitbucket username, API token and its expiry date | The token is encrypted and never shown again. The expiry date is stored so it can be shown and flagged before it expires |
What we don't store
- Your passwords. Sign-in happens at your identity provider.
- Any other information from your identity provider or Salesforce orgs.
note
We don't store any other information or use/share your necessary information anywhere without your consent.