Last updated on July 10th, 2022.
At FirstWho, we respect the privacy rights of our users and recognize the importance of protecting the personal information we collect about you. Our Privacy Policy is designed to help you understand what information we collect and how we use and share that information. This Privacy Policy applies to our Websites and Services.
Registration and Contact Information. We collect information about you when you (a) register to use the Services and (b) otherwise provide contact information to us via email, mail, or through our Service. This information you provide may include your username, first and last name, email address, and time zone.
Technical, and Usage Information. We automatically collect information on how you interact with the Service, such as the IP address from which you access the Service, date and time, and referrer website (if available).
Other Information. We may collect other information from you that is not specifically listed here. We may use any such information in accordance with this Privacy Policy or as otherwise permitted by you.
We use your information in the following ways:
We do not sell, trade, share or transfer your personal information to third parties.
FirstWho "refresh", "token" We use these cookies for authentication and preserving preferences when logged out.
We allow users to connect their calendars to make scheduling of candidates faster and more accurate. When connecting, we will save API tokens so we can reuse them when requesting future information from these Apps. All API tokens are encrypted at rest in our application's database, and are never shared outside the application.
Google When connecting your Google Calendar, we will save the{" "} access token, refresh token, authorization scopes , expiration date/time of access token, and a{" "} primary calendar ID. We use the access/refresh tokens and authorization scopes to communicate with Google on your behalf. During scheduling we might ask Google's Calendar API when you are busy (Note: We never ask for details of events in your calendar.). And once you have determined a date/time to meet a candidate, we will use Google's Calendar API to create/update events in your primary calendar.
Microsoft When connecting your Outlook Calendar, we will save the access token, refresh token,{" "} authorization scopes,{" "} expiration date/time of access token, and a{" "} primary calendar ID. We use the access/refresh tokens and authorization scopes to communicate with Microsoft on your behalf. During scheduling we might ask Microsoft's Outlook Calendar API when you are busy (Note: We never ask for details of events in your calendar.). And once you have determined a date/time to meet a candidate, we will use Microsoft's Outlook Calendar API to create/update events in your primary calendar.