Built to pass your data and IT checks.
Plain answers, for the people whose job is to check them.
Your data.
What you send us
Nothing, to start. Each offer-holder joins from a personal link in your own acceptance email, which carries only your applicant ID for them. They give us their own name and email when they sign up.
Where data is held
In London: the database, sign-in, file storage and the servers that run the platform. Email is sent from Dublin. Course video streams through a worldwide network, with no names attached.
Who is responsible
For your students, you are the data controller. We process their data on your behalf, under our data processing agreement.
Who sees what
Each university sees only its own students. Your central team sees progress and arrival steps, never what a student asks Ari or the documents they keep. Someone in one office, such as accommodation, sees only that office's steps and who has done them, by name.
Team access
Your team signs in with its own accounts, as an owner, a manager or a viewer, for the whole university or for one office. Only owners and managers change things, and an office changes only its own part.
Ari, plainly
A student’s question goes to Anthropic in the United States to write the answer, without their name or email. We don’t keep conversations, except an answer a student reports, which we keep to review.
Students’ own documents
Students can keep private copies of their passport, visa and other documents. Only the student can open them. We never ask you for documents, and never collect financial details.
Wellbeing check-ins
Optional for each university. A check-in on its own is anonymous. It reaches your team with the student’s name only when they ask you to get in touch, and only the office you choose sees it.
Deleting data
A student can delete their account at any time, and everything goes with it, including their documents.
Who else handles it.
Every service that handles your students’ data, and where. We tell you before adding a new one.
| Service | What it does | Where |
|---|---|---|
| Supabase | Database, sign-in and file storage | London |
| Vercel | Runs the website and platform | London, delivered through a worldwide network |
| Resend | Sends email | Dublin |
| Anthropic | Writes Ari’s answers | United States |
| Bunny.net | Streams course videos | Worldwide network, no names or emails |
| Apple and Google | Deliver app notifications, once the app is in the stores | United States and worldwide |
| Cloudflare and Vercel Analytics | Website analytics, without cookies | Worldwide, no names or emails |
How it fits into your university.
Three phases, from offer to the end of the first year. No student data shared and no IT project. Nothing connects to your systems unless you want it to.
1From offer to arrival
Admissions
Every offer-holder gets a personal Arrival link in the acceptance email you already send.
- What you do
- Add one line to your acceptance email. Your CRM fills in each student’s applicant ID, the way it fills in their name.
- What we do
- Set each student up when they tap the link, and match them to your records by applicant ID. Each ID can be claimed once.
2Arrival and enrolment
Enrolment
Students keep the account they made, so nothing changes for them when they enrol.
- What you do
- Nothing. If a student’s plans change, withdraw them in the portal.
- What we do
- Flag the students who may not arrive, weeks before enrolment day: no visa, no flight, or gone quiet.
3The first year
Every office
Accommodation, IT, fees, the students’ union and wellbeing, all in one place.
- What you do
- Give us what each office already sends new students: emails, PDFs and web pages.
- What we do
- Set it up as steps and messages timed to each student’s arrival, and give each office its own login.
Applicants through UCAS.
The same link works. Put it in the email you send when a student makes you their firm choice, again at Confirmation, and in your Clearing confirmation, with their UCAS Personal ID or your own applicant number. International students who firm late in the summer get their visa, housing and travel steps the moment their place is confirmed.
Want it connected? Full integration.
For universities that want Arrival joined up with their own systems. Set up with your IT team as an add-on to your licence, and built with the first university to ask for each connection.
How it’s quoted- Phase 1Your CRM sends each accepted student to Arrival automatically, and gets back a personal link nobody can guess.
- Phase 2Students sign in with your university login.
- Phase 2Enrolment status and student numbers come straight from your records system.
- Phase 3Office systems tick off steps automatically, such as a room accepted or an IT account activated.
- All yearUpdates land in your CRM as they happen: joined, gone quiet, at risk of not arriving.
Every connection uses the same student data feed, whatever your systems: SITS, Banner, Salesforce, Dynamics, Slate or your own. You send to us, and we never need access to your systems. Everything comes back out too: export every student and their progress at any time. The two-page version for your team