About Student Privacy in Handshake

Why Syncing Data into Handshake Matters

In order to get the most out of Handshake, and to ensure your students are accurately qualified, it’s critical to sync in data to Handshake. This student data import is a vital step in implementation and ensures that:

• Data is is up to date.We will be exporting this information directly from your student information system (SIS).
• Your students have the best shot at the amazing jobs and internships. Students with University mapped majors, GPA, work authorization, and coursework are much more likely to be contacted by an employer. Most students don’t want to enter this themselves.
• Employers can trust student qualifications. Major, GPA, education level, and school year are all functionally tied to requirements on job postings in Handshake. Importing this information will ensure that students are qualified for positions, and Employers can quickly rely on the accuracy of application. This in turn increases employer engagement across the platform.
• Students have a great experience upon their first login. Since many student fields are tied to job qualifications, importing this information will ensure that students are qualified for positions that they should be qualified for - and aren't confused when they don't seem to meet the requirements. This first experience is crucial for long term student engagement.
• Analytics and reports are relevant. Schools that don’t sync a robust dataset see less students engaged and have a much harder time reporting on their impact.  Importing even the most basic required fields empowers you to build reports and explore activity by particular cohorts.

Profiles & Data

Explore a few key principles around how students use Handshake and what data is shared:

• Students can use all features of Handshake, including applying to jobs and scheduling appointments, without making their profile public.
• Student profiles are automatically set to private, whether they are uploaded by the school or created by the student.

In the account onboarding process, students are clearly and explicitly given the option to make their profile public to employers that are approved by their university. Students can have four states they can be in regarding sharing their data. They are outlined below.

 

Hidden (default upon data sync)	Activated Student (agreed to TOS) but hidden profile.	Activated Student (agreed to TOS) opted to make profile public.	Activated Student (agreed to TOS) opted to make profile public. Additional opt in for GPA.
No information is shared or visible outside the University	Student can see their own information University can see profile data Profile shared with employers when student explicitly applies to a job.	Student can see their own information University can see profile data Employers can search for student and see profile without application Other (non alumni) students can search for individual public, student profiles	Student can see their own information University can see profile data Employers can search for student and see profile without application GPA shared with employers.

 

Throughout this process, the student is in full control of their information. Explore the deep dive below to see what students see when opting in.

Imported Data Fields:

Even thought students are in control of this data, we know that GPA, demographic, and identifying information can be sensitive. We have a variety of measures in place to ensure this is protected from employers or other students. Review our documentation on the Student data fields here.

Additionally, here is a quick refresher on the required fields:

Email

First name

Username

Auth ID

School Year Name

GPA

Major

Education Level

 

GPA in Particular:

A student's GPA is never public unless the student expressly opts-in to make it public. If a student does choose to make their GPA public, this information is visible to employers only. Other students or alumni will not be able to view another student's GPA, even if the GPA is visible by employers.

Explore the GPA deep dive below for more information!

 

Data Ownership:

Students own the data that they upload and enter into Handshake. We only use data as described in our Privacy Policy and Terms of Service, and in accordance with the agreements we have with our University Partners. Data and IT teams might also be particularly interested in our Security site. Explore these links to learn more.

 

Onboarding Deep Dive from the Student Perspective:

Explore this article to review (with screenshots) a student's journey through the onboarding process, and where they can enable the different privacy settings in Handshake.

When a student is invited by their school to join Handshake, they will log in, set a password, and be prompted through the onboarding process.  

 

Onboarding Deep Dive: If a student does NOT have GPA imported:

If a student does not have GPA initially imported in their file, when they initially go to apply for a job (where they would otherwise meet the GPA requirement) it will show like this on the side of the job posting:

The student will then have to navigate back to their profile:

To set GPA in the education field in order to show as "fully qualified' on a job posting:

The GPA field specifically:

From there, the student would have to navigate back to the job posting where they will then show as qualified. This can be very confusing from the student perspective - and seem like yet another barrier to entry.

Again, this field is important to ensure that students are qualified for positions, employers can rely on the data. In turn, this initial application and posting experience is crucial for long term student and employer engagement.

 

Additional Resources:

Explore these article to take a closer look at the next steps:

• Importer Overview: Upload Data Into Handshake
• Student Sync: How to Import Student Data
• Student Data Formatting FAQs
• Handshake Implementation Guide
• Handshake Privacy Policy
• Handshake ToS
• Handshake Security