Skip to the page
Hesper
  • Students
  • Universities
  • Pricing
  • Guides
  • Students
  • Universities
  • Pricing
  • Guides

Data Processing Agreement

Template version: October 22, 2026

Back to Your data and security

How to use this template

This is Hesper's standard Data Processing Agreement for schools, colleges and universities. Fill in the blanks, sign, and email a copy to info@hespercareers.com; we countersign and send it back. If your institution has its own data agreement or a state-required addendum, send that instead and we will review it. Where this template and your institution's required terms conflict, tell us and we will work it out with you before signing.


Data Processing Agreement

This Data Processing Agreement ("DPA") is between [School legal name] ("School") and Arav Patel d/b/a Hesper ("Provider"), and takes effect on [date] ("Effective Date"). It adds to the Hesper Terms of Service (hespercareers.com/terms) and Privacy Policy (hespercareers.com/privacy) as they apply to the School and its students. If this DPA conflicts with those documents on how Student Data is handled, this DPA controls.

1. What this DPA covers

1.1 The Service. Hesper is a job search service. Students tell it the job and city they want; it finds companies hiring, finds people at those companies, and sends job-search emails from the student's own Gmail or Outlook account on a schedule the student sets. The School's career center uses a staff dashboard to see the progress of students who choose to share it, post jobs and events, and report graduates' outcomes.

1.2 Student Data means personally identifiable information about the School's students or alumni that Provider receives:

  • (a) from the School, such as a class roster (student ID, name, email, expected graduation term and year, degree, major) or an alumni list (name, employer, title, and where the School has it, a work email or LinkedIn profile); or
  • (b) from a student because that student joined the School's career center in the Service, including the profile, job search activity and outcomes listed in Exhibit A.

Information a person gives Provider while using the Service on their own, without joining the School, is governed by the Privacy Policy and is not Student Data under this DPA.

1.3 Staff Data means the names and email addresses of School staff who use the staff dashboard, and the record of their actions in the access log.

2. FERPA: Provider as a school official

2.1 To the extent Student Data includes education records under the Family Educational Rights and Privacy Act (20 U.S.C. 1232g; 34 CFR Part 99, "FERPA"), the School designates Provider as a school official with a legitimate educational interest under 34 CFR 99.31(a)(1)(i)(B), because Provider performs an institutional service (career development and first-destination outcome reporting) that the School would otherwise use its own employees for.

2.2 Provider agrees that, for Student Data:

  • (a) it is under the School's direct control with respect to the use and maintenance of education records;
  • (b) it uses Student Data only to provide the Service to the School and its students, as described in Exhibit A, and for no other purpose;
  • (c) it will not disclose Student Data to anyone other than the School, the student it is about, and the subprocessors in Exhibit B, except as FERPA allows (34 CFR 99.33) or as required by law; and
  • (d) if it receives a subpoena or court order for Student Data, it will tell the School promptly, before responding where the law allows, so the School can respond or seek protection.

2.3 The School is responsible for having the right to share any Student Data it uploads (for example under the school-official exception or as directory information), and for its annual FERPA notice describing the use of school officials.

3. What Provider will not do

  • Sell, rent or trade Student Data.
  • Use Student Data for advertising, including targeted advertising based on a student's activity.
  • Build a profile of a student for any purpose other than providing the Service to that student and the School.
  • Share one school's Student Data with another school or its users.
  • Use Student Data or Gmail or Outlook data to train artificial intelligence or machine learning models.
  • Read a student's inbox. The Service asks Google only for permission to send (the gmail.send scope) and Microsoft only for Mail.Send.

Provider may use de-identified, aggregate information (for example, how many emails were sent across all users in a week) to run and improve the Service, provided it cannot reasonably be used to identify a student or the School.

4. Student consent and visibility

4.1 Joining the School's career center in the Service is the student's choice. Sharing progress with staff is a separate, recorded choice. Staff see nothing about a student who has not agreed to share, other than a count.

4.2 A student can stop sharing or leave the School in the Service at any time, and staff stop seeing that student immediately.

4.3 Students can see exactly what staff see about them ("What my counselor sees" on their School page), download everything Provider holds about them, and delete their account in Settings.

4.4 Requests from parents or eligible students to inspect or correct education records the School provided will be handled by the School. Provider will help within ten (10) business days of the School's request.

5. Students under 18

The Service is for people 16 and older. A student under 18 may use it through the School under this DPA. The School will not invite students under 16.

6. Security

Provider will keep reasonable administrative, technical and physical safeguards, including at least those in Exhibit C, and will not reduce them during the term of this DPA.

7. Security incidents

7.1 If Provider confirms unauthorized access to, or disclosure of, Student Data, it will notify the School's contact below within seventy-two (72) hours of confirming it.

7.2 The notice will say what happened, when, which data and how many students were affected (as far as known), what Provider has done about it, and who to contact. Provider will update the School as it learns more, cooperate with the School's investigation, and, where the law requires or the School reasonably asks, help notify affected students. Provider pays its own costs of investigating and fixing the incident.

8. Subprocessors

Provider uses the subprocessors in Exhibit B. Provider will bind each to data protection terms at least as protective as this DPA where that subprocessor's standard terms allow, and remains responsible for them. Provider will give the School at least thirty (30) days' notice by email before adding a subprocessor that receives Student Data; the School may object, and if the objection cannot be resolved, the School may end this DPA and have its data deleted under Section 9.

9. Retention and deletion

9.1 Provider keeps Student Data only as long as needed to provide the Service.

9.2 School uploads. The School can replace or delete its class roster and alumni list from the staff dashboard at any time.

9.3 On termination or on written request, Provider will delete the School's account, class roster, alumni list, staff accounts and access log within thirty (30) days, and confirm the deletion in writing on request. Student accounts belong to the students: when the School's account is deleted, students stop sharing with the School, and each student keeps their own account unless they delete it.

9.4 Copies in encrypted backups are removed as the backups expire, within ninety (90) days. Provider's current backups are kept fourteen (14) days.

9.5 Return. On written request before deletion, Provider will give the School its uploaded data (class roster, alumni list, employer partner rules, posted jobs) and the first-destination report as CSV files within thirty (30) days.

10. Reviews

Once a year, on request, Provider will complete the School's reasonable security questionnaire (such as the HECVAT) and answer follow-up questions, and provide its current self-assessed Accessibility Conformance Report. Provider does not currently hold a SOC 2 report or ISO 27001 certification, and has not had an outside penetration test.

11. Term

This DPA lasts as long as the School uses the Service. Either party can end it with thirty (30) days' written notice. Sections 2, 3, 7 and 9 continue until all Student Data is deleted.

12. Law

This DPA is governed by the laws of the State of Indiana, unless the School is a public institution whose state law requires its own state's law, in which case that state's law applies. Nothing in this DPA waives any immunity the School has under its state's law. If a state student privacy law applies to the School and requires more than this DPA, Provider will comply with that law for the School's Student Data.

13. Contacts and signatures

SchoolProvider
Organization[School legal name]Arav Patel d/b/a Hesper
Contact for notices and incidents[Name, title, email]Arav Patel, Founder, info@hespercareers.com
Signature
Name and titleArav Patel, Founder
Date

Exhibit A: Student Data and how it is used

DataWhere it comes fromUsed forWho at the School can see it
Name, sign-in email, major, class year, graduation term, degree levelStudentRunning the student's job search; showing the student on the staff dashboard if they shareStaff, only for students who share
School email address the student confirmed with a codeStudentProving the student belongs to the School; matching to the School's roster; free plan and Student plan eligibilityNot shown to staff
Job searches (job title, city, running or paused)StudentRunning the searchStaff, for students who share
People emailed, their work emails, email textStudent and public business sourcesSending the student's emailsNever shown to staff
Reply excerpts (first 280 characters), only if the student set up reply detectionRecipients' repliesUpdating the student's searchNever shown to staff
Totals: people reached (7 days, 30 days, all time), replies, applications, interviews, offers, date of last emailServiceStudent's own progress; staff dashboardStaff, for students who share
Interviews, offers and accepted offers the student logs, with company and job titleStudentStudent's tracking; staff dashboard and outcomes reportStaff, for students who share
Where the student landed (employer or school, title or program, salary if entered)Student, or entered by staff with a source labelFirst-destination reportingStaff, for students who share
Notes from staff, and whether the student read themStaffAdvisingStaff and that student
Resume, saved application answersStudentApplications the student asks forNever shown to staff
Class roster (student ID, name, email, expected term and year, degree, major)SchoolCounting the class for the knowledge rate; adding student IDs to the School's reportStaff
Alumni list (name, employer, title, work email or LinkedIn where provided)SchoolRanking alumni first in that School's students' searches onlyStaff
Weekly staff email: the week's totals, names of sharing students who sent nothing that week, and sharing students' new interviews and offers with the companyServiceAdvisingStaff
Jobs posted by the career center that a student marked interest in; the student's name, major, class year and email go to the employer only if the student ticks the box to let that employer see themStudentConnecting students with employersStaff; the employer only with the student's tick
Staff access log (who opened a student, downloaded a report, sent a note, changed a list, and when)ServiceAccountabilityStaff

The School can also turn on a public outcomes page. It shows anonymous totals only, nothing until 10 or more students share, and names an employer only when at least two students are counted there.

Exhibit B: Subprocessors

SubprocessorWhat it doesData it handles
SupabaseDatabase and sign-inAll Service data
VercelWeb hosting and server codeAll Service data in transit
GoogleSign-in and sending email from the student's GmailSign-in identity, outgoing emails
MicrosoftSign-in and sending email for students who use OutlookSign-in identity, outgoing emails
CloudflareReceiving replies a student forwards, if they set that upForwarded replies (kept only as excerpts)
BrevoService emails (daily summary, school email codes, staff digests)Name, email, email content
StripePayments (and the free plan card check for accounts that used it before November 13, 2026)Payment details (Provider keeps only a card fingerprint)
TwilioTexting the free plan's one-time codePhone number (Provider keeps only a one-way hash)
AnthropicAI writing and coaching the student asks for, and reading forwarded repliesOnly what each feature needs: resume text without email or phone, profile facts, job postings, drafts, practice answers, reply text; not used to train models
PostHogProduct analyticsInternal user ID, pages and buttons used; email and sign-up source at sign-up
SentryError monitoringError reports, browser and device type
Serper, Hunter, MillionVerifier, ClearbitFinding and checking public business contact details of the people students emailCompany names, names and work emails of people to be contacted (not Student Data)

Exhibit C: Security measures

  • Encryption in transit (HTTPS/TLS) for every connection, and encryption at rest in the managed database.
  • Row-level security separating each user's data in the database; privileged server access used only by the application's own server code.
  • Staff access only after a person at Hesper verifies the School, only for staff signed in with an email on the School's domain, and only after an existing staff member approves each colleague.
  • An access log of staff actions on student data, which staff can review and export.
  • Gmail and Outlook access tokens kept on the server only, never sent to the browser or included in data exports.
  • Resumes in a private storage bucket, shared only through short-lived signed links.
  • Report downloads protected against spreadsheet formula injection.
  • Students can see exactly what staff see, download their data, and delete their account themselves.
  • Production access limited to the founder, with two-step sign-in required on every administrative account.
  • Company administrator actions (verifying schools, changing licenses, exporting account lists) recorded in a log the administrator can't edit.
  • Data stored in the United States (Supabase on AWS us-east-2).
  • A nightly encrypted backup of the database, kept fourteen (14) days.

Hesper

Product

  • For students and job seekers
  • For universities
  • For employers
  • Pricing

Learn

  • Career guides
  • Blog
  • Build experience first

Trust

  • Security and privacy
  • Data processing agreement
  • Security questionnaire
  • Accessibility

Company

  • Support
  • Talk to us
  • Work at Hesper
  • Privacy policy
  • Terms

© 2026 Hesper

Appearance