Platform trust
Built for organizations responsible for young people
Procurement, IT and safeguarding teams need to understand what a platform does with student data before students ever sign in. This page describes how StudentRecruit is designed, in plain language, and states plainly which certifications it does and does not hold.
Connecting Students to Opportunities.
Open the demoAccess control
Every person acts inside one role: student, guardian, mentor, staff, organization administrator, employer, college recruiter, verifier or platform administrator. Screens, records and actions are filtered by that role, and a role can never widen its own permissions.
Your students stay yours
Each district, center, nonprofit, college and employer sees only its own people and records. Nobody browses another organization's students.
Youth safeguarding
Student media is private by default. Mentor and employer contact is scheduled, monitored and logged, and unrestricted adult-to-minor private messaging or meetings are not offered. A Safety Center is reachable from every authenticated screen and routes concerns to the organization's own safeguarding staff.
Purpose limitation and retention
Your organization decides how long records are kept and whether students take an export with them when they leave. Export and deletion requests are tracked until they are done.
Interoperability roadmap
Credentials travel with the student, student lists import from the systems you already run, and sign-in works with your existing school accounts. Your IT team gets the technical detail during onboarding.
Accessibility target
WCAG 2.2 AA is the design target: keyboard operation, visible focus, labeled controls, adequate target sizes, colour contrast, reduced-motion support, and caption and transcript hooks on media. StudentRecruit has not completed an independent audit and does not claim conformance.
Auditability
Verifications, sharing changes, mentor and employer contact, safeguarding decisions and data requests are all recorded, and your staff can review that history for your own organization at any time.
What we do not claim
- No certification, conformance or audit badge is displayed anywhere in the product.
- No customer outcomes, logos or testimonials are shown. Examples in the product tour are illustrative.
- No live third-party integration is implied before credentials are configured and tested.
- No emotion, facial, accent or personality inference is performed on any student recording, ever.
Procurement evaluation packet
What an IT, legal or procurement reviewer typically asks for during an evaluation, and where it lives today.
Where is data hosted and who can reach it?
Records are held in a managed cloud service, reachable only by the organization they belong to. Our own staff reach them only for support or an incident, and that access is recorded.
Do you sell or advertise to students?
No. There is no advertising, no data sale, and no third-party behavioural tracking on student surfaces.
Who owns the records?
The sponsoring organization owns its institutional records; the student owns their portfolio and can export it. Both pathways are tracked as requests with an auditable status.
What happens at contract end?
Your retention choice applies: an export on exit where you enable it, then keep or delete. Nothing is quietly held longer than you asked for.
Is there an SLA?
Availability and support commitments are agreed in the order form for the purchased plan.
Can we run a security review?
Yes. Role model, data flows, retention configuration and integration posture are all reviewable with your IT and legal teams. We display no certification badge we have not earned.
Data flows in plain language
- 1. An organization invites or imports its students. That list stays with that organization.
- 2. Students create evidence: reflections, artifacts, simulation attempts, credentials, media. It is private by default.
- 3. A student, with consent where required, chooses what to share and with whom, for how long.
- 4. Employers, colleges and verifiers only ever see what was shared with them, and the share is logged.
- 5. On exit, your organization's own choice decides what is exported, kept or deleted.
Reporting a concern or a vulnerability
Safeguarding concerns raised inside the product route to the responsible organization's own staff first. Security researchers and institutional partners can reach the StudentRecruit team through their organization contact.