How I read your GAUR data without storing it anywhere
The whole import happens inside the phone, and why that changes what can go wrong.
The first question everyone asks when they see Nexo is the same one: "so I hand my university login to your app?" It's the right question. This is the long answer.
Where the import happens
Inside your phone. You sign in with your university account from a screen in the app itself, Nexo reads the timetable, the enrolment, the groups and the transcripts, and builds the week, the planner and the record from that. All of that work happens on the device.
The point isn't that it's fast — it is — but what it implies: there is no server of mine in the middle. Your credentials never travel to me, your grades are never copied into any database, and your academic record doesn't exist outside your phone.
Why it's built this way
Because the safest design for a piece of data is not to hold it.
If I stored academic records, I'd have to answer for them: encrypt them, back them up, decide how long they're kept, have a procedure for when someone wants them deleted and another for the day someone gets in where they shouldn't. None of that is impossible, but it's an enormous weight for a free app built by a student. Taking the server out of the equation takes the whole problem out.
And there's a second, less noble and more practical reason: an app that stores nothing can't leak anything.
What this approach breaks
It isn't free. There are things this design makes harder, and I'd rather say them:
- If you switch phones, you start over. There's no cloud backup to restore; you import again.
- If GAUR changes on the inside, the import breaks. When that happens, I fix it and write it up here with the date, so you know whether the fault is yours or mine.
- I can't see your case. If something goes wrong on your phone, I have nothing to look at. I have to reproduce it, not query it.
Three real drawbacks in exchange for your academic record not sitting anywhere I can reach. It seems like a good trade to me, and that's why it's written on the app's first screen instead of in the small print.