CAMPUS · FOR INSTITUTIONAL BUYERS
This page separates the protections already in CareerCaptain from the contractual, privacy and service arrangements that still need to be settled for a particular university, college or students' union.
Learners, staff and administrators have different levels of access.
An institution can pay for Free, Pro or Executive access without taking over a learner's personal account.
Campus join codes expire, can be limited in how many times they are used and are not kept in readable form after issue.
Institutions can set a limit on the number of learner places and review membership and invitation activity.
Staff reporting shows overall use, with activity information hidden for groups smaller than the institution's privacy threshold. That threshold can never be below five learners.
Campus staff cannot use the staff area to open an individual learner's private career information, files, questions or generated work.
Staff can see how many learner places are active and limited information about overall use. They do not get an individual employability score, a feed of a learner's questions or generated work, access to CVs, or a way to open the learner's private CareerCaptain information.
CareerCaptain has privacy controls for Campus. The institution and CareerCaptain must still agree their respective legal roles, any data-processing agreement and any deployment-specific privacy assessment before rollout where required.
CareerCaptain is designed and tested towards WCAG 2.2 Level AA. It does not currently claim that an independent auditor has certified full conformance.
Campus currently uses CareerCaptain accounts and invitation codes. Sign-in through an institution's own single sign-on service is not yet available.
Different staff roles have different access, learner membership is checked, join codes are protected and important membership actions are recorded. CareerCaptain does not claim ISO 27001, SOC 2 or an equivalent certification.
The core service does not infer or require age for ordinary accounts. Any deployment covering minors requires the institution-specific safeguarding, support and contractual position to be agreed before rollout.
Support arrangements, response-time commitments, incident contacts and business-continuity commitments for a particular institution should be set out in its contract rather than assumed from the public website.
This page does not claim a certification that CareerCaptain does not hold. A contracting institution should ask for the evidence it needs for its own procurement, privacy and security process, and that evidence should be kept current as the service changes.