Privacy notice
Last updated 16 November 2026
Classyn is an app for course updates at universities, starting in Nigeria: lecturers and approved course reps post, and students get them on time. This notice explains what we collect, why, who it goes to, how long we keep it, and what you can do about it. We wrote it to match what the app actually does.
Who we are
Classyn is run by its student team: Owamokele Joshua Okikidayo, Adewale Adeola Samuel, Fasiku Victor Adebola and Ganiyu Abdulrasheed. Questions, requests or complaints about your data: [email protected].
What we collect
| What | Details |
|---|---|
| Your account | Name, email address (and any extra addresses you add), password (stored only as a one-way hash), university, school, department and level. Students: matric number. Staff: staff ID and title (Dr., Mrs. and so on). Optional: date of birth. |
| Your profile | Only what you add: photo, cover photo, bio, skills, links, a contact email, what you are open to, and which of these classmates may see. |
| What you do in Classyn | Courses you enrol in; which posts you have opened, when, and whether you tapped "Got it"; notices you acknowledge or flag; community questions, replies, vouches and reports; office-hour bookings; your own deadlines, timetable entries and GPA records; your notification settings. |
| What you post (lecturers and reps) | Announcements, corrections, deadlines, class times, course files and notices, with who posted them and when. |
| Messages | What a class or course rep and a lecturer write to each other, what a lecturer and their school's admin or the university's registry write to each other, what a school admin and the registry write to each other, and room-clash chats between lecturers: the text, who sent it and when, and when each side last opened the conversation. |
| Session chat | What students, reps and lecturers of a class write in that class's chat while it runs: the text, who sent it and when, and who a lecturer or rep muted for that class. It is erased 24 hours after the class. |
| Collections (when a rep collects for something) | Reps: what it is, the price, and the bank, account number and account name to pay into. Students who open one: your payment code, whether and when you said you paid, any size or choice, and anything you add about the transfer (sender's name, amount and time). The money goes straight from you to the rep: Classyn never takes, holds or sees it, and never reads your bank. Bank alerts a rep pastes in to confirm payments are read on their own device and never sent to us. |
| Student ID check (if your university turns it on) | Students who signed up with a personal email: a photo of your student ID card (freshers: an admission letter, JAMB result slip or course registration form) and a short selfie: five photos of your face, looking straight and then turning your head in an order the app picks at that moment. Both are taken with your camera in the app, never chosen from your gallery. When you take them, each photo is checked automatically for blur, darkness and glare so you can retake an unclear one at once; that check looks only at sharpness and light, never at who you are, and keeps nothing. If your camera doesn't work, you can instead show your card to your class rep in person: then no photo is taken at all, and we keep only that you asked. We also keep which document it is and when you sent it. Once someone decides, the photos are deleted; we keep only the decision, who made it, when, and any reason given. |
| Your devices | When you sign in: device name, browser or app version, IP address and time. For notifications: a push token from your phone or browser. If you turn on two-step sign-in: the devices you chose to trust. |
| Emails we send you | Sign-in, verification and reset codes, and invitations, sent to your email. |
| Requests to bring Classyn to your university | What you write in the form at classyn.org/request: your name, whether you are a student, rep, lecturer or staff, your university, faculty or department, email, and optionally a phone number and message, with your browser's description of your device. It is emailed to our team inbox so we can get in touch, not stored by the website, and we delete it on request. |
| Feedback you send us | What you write in the form at classyn.org/feedback, the details you choose to add (role, device, app version, email) and your browser's description of your device. It is emailed to our team inbox, not stored by the website, and we delete it on request. |
We do not use advertising, sell data, or put tracking or analytics tools in the app or on this website.
Why we use it
- To run Classyn for you: showing your courses' posts, sending notifications, reminders and calendar exports, and keeping your account working.
- To keep posts trustworthy: only verified lecturers and approved reps can post, and every post and admin action is recorded in a tamper-evident log.
- To keep accounts safe: sign-in records, rate limits and two-step sign-in help us spot and stop misuse.
- To measure whether it works: our one-semester pilot measures how quickly posts reach students (see "Research" below).
The legal basis for the first three is providing the service you signed up for; for the research, it is your consent. If you are in the UK, the EU or the EEA, the bases under those laws are set out below.
Who can see what
- Students in your courses see your name and the profile parts you allow. Everyone sees your department's short code (two to four letters, such as IFS).
- Your lecturers also see your matric number.
- A course's lecturers, its approved reps, and your school's and university's admins can see whether you have seen or confirmed a post, by name.
- Your own deadlines, timetable entries and GPA records are visible to you alone.
- Messages are seen only by the two people in the conversation. Nobody outside the conversation can read them: not classmates, not other lecturers, and not an admin who isn't one of the two.
- A session chat is seen only by that class: its enrolled students, its reps and its lecturers, each by their real name. Admins can't read it. A lecturer or rep of the class can remove a message or mute someone for that class, and that is written to the audit log, without the message's text.
- A lecturer's staff details (Staff ID, sign-in email, school and department) are shown on their profile to their own school's admin and to the university's registry, and to nobody else.
- A student's record can be looked up by their own school's admin and by the university's registry, to act on a report: name, email, matric number, department and level, whether they are confirmed as a student, the courses they are enrolled in, any rep role and when they were last active. It does not show posts, messages, grades or their profile. Every time a record is opened, it is written to the audit log. An admin can also sign a student out of all their devices, with a reason that is kept.
- Your name can be corrected by you in Edit Profile. Each change, with the old and the new name, is kept in the audit log, and a verified lecturer's school admin is told.
- A sign-in on a new device sends an email to your sign-in address saying which device it was, when, and the country the network was in. The country comes from our network provider; your address is not sent to any location service, and the email shows a network address only with its last part hidden.
- A rep running a collection sees the name, matric number and payment details of everyone on its list. Classmates see only how many have paid, and the account details the rep gave.
- Your student ID photo and selfie are seen only by your class rep or their assistant, and, if they wait more than 3 days or your class has no rep, by your department's primary lecturer (or your school admin if there is none). They are stored privately, never at a public address, and deleted the moment they decide. A reviewer sees them blurred until they hold a button, each copy carries that reviewer's name, and every viewing is recorded.
- Profile photos are stored at a web address that anyone holding the link can open, so don't upload anything you would not show your class.
Who we share it with
We use these services to run Classyn. They handle data only to provide their service to us, and most are outside Nigeria:
- Render: runs our servers (in Frankfurt, Germany).
- Supabase: our database, which stores your account and activity (in Frankfurt, Germany).
- GitHub: keeps an encrypted copy of the database each night, as a backup, for 35 days. Only our team holds the key that opens it.
- Cloudflare: delivers classyn.org and app.classyn.org (it sees your IP address).
- Cloudinary: stores profile photos and course files.
- Resend: sends our emails.
- Expo and Google (Firebase Cloud Messaging): deliver notifications to Android phones. Your browser's own push service (Google, Apple, Microsoft or Mozilla) delivers them to browsers.
- Google Fonts: this website and the web app load their typeface from Google, so your browser connects to Google.
We share nothing with anyone else unless the law requires it.
Research
Classyn is also a student research project. During a one-semester pilot in one department, we measure how long it takes for a post to be seen, using the "seen" and "Got it" records above. Results are analysed with each student replaced by a code, never by name, and published only as totals.
Before the pilot starts, students in that department will be asked in the app whether they agree to take part. You can say no, or opt out later at any time by emailing us, and your records are then left out of the results.
How long we keep it
- Your data is kept while your account is open.
- When you delete your account, you are signed out everywhere at once, and your name, email and profile are removed. Seven days later the rest is erased.
- Backups: the database is copied, encrypted, each night and each copy is kept for 35 days. So anything erased also disappears from every backup within 35 days. Backups are only ever used to restore Classyn after a failure.
- A few records must outlive an account so that course histories stay complete and checkable: posts a rep made, class deadlines and times they set, and the admin audit log. These remain under "Deleted user".
- Sign-in records (device, IP address and time) are kept while your account is open, and erased with it.
- Phone notification tokens unused for 75 days are switched off. Course notifications are archived when their semester ends. A notification held for your quiet hours, or while you are in class, is kept only until it is delivered or stops being useful.
- Student ID photos and selfies are deleted as soon as they are accepted or turned down, or when you replace them or delete your account. While they are being sent they wait on our server for a few seconds, and are deleted from it the moment the request ends. The decision itself is kept while your account is open.
- Messages are kept while the accounts in the conversation are open. When a student in one deletes their account, their conversations are erased with the rest of their data seven days later.
- A session chat is erased, with every message in it, 24 hours after its class ends. It is not part of a course's verified announcements.
- A collection's list (names, payment codes and payment details) is erased 30 days after its last pickup time, or after it closed if it never had one. Only its totals stay.
Your rights
Under the Nigeria Data Protection Act 2023 you can:
- Get a copy of your data: Settings › Privacy › Request My Data (it is emailed to you).
- Correct it: edit your profile and academic details in the app.
- Delete your account: Settings › Danger Zone (students). Staff, email us.
- Object or withdraw consent, for example to the research: email us.
- Complain to us, or to the Nigeria Data Protection Commission.
We will answer requests sent to [email protected] within 7 to 14 days.
If you are in the UK, the EU or the EEA
Classyn is on Google Play in every country, so the UK GDPR and the EU's General Data Protection Regulation can apply to you. Everything above still holds; this section adds what those laws ask us to tell you.
We use your data on these legal bases:
- To run Classyn for you (your account, courses, posts, notifications, reminders and calendar exports): it is necessary for the service you signed up for (contract).
- To keep posts trustworthy and accounts safe (checking who may post, the tamper-evident record, sign-in records, rate limits and two-step sign-in): our legitimate interest, and every user's, in posts that can be trusted and accounts that are hard to break into. You can object to this.
- The student ID check, if your university turns it on: the legitimate interest of your university and your classmates in knowing that a classmate really studies there. You can use your school email or show your card in person instead of sending photos.
- The research: your consent, which you can withdraw at any time.
- When the law requires it, for example to answer a lawful request: our legal obligation.
Where your data goes. Our database and servers are in Frankfurt, Germany. Some of the services listed under "Who we share it with" work outside the UK and the EU, for example in the United States. Where your data goes to a country the UK or the EU has not found to protect it adequately, we rely on the safeguards in those services' data processing terms, such as the Standard Contractual Clauses. You can ask us about them.
On top of the rights above, you can:
- Take your data with you: Request My Data sends it as a file other services can read (JSON).
- Ask us to restrict how we use your data while a question about it is settled: email us.
- Object to anything we do on the basis of legitimate interests: email us, and we stop unless we have a compelling reason to continue.
- Not be subject to automated decisions. We make none about you: the ID check's photo check only advises you to retake a blurred photo, and a person decides.
- Complain to your local data protection authority (in the UK, the Information Commissioner's Office).
We answer within the 7 to 14 days above, and in any case within one month.
Students under 18
Classyn is for every student at a participating university, including those under 18. If you are under 18, please make sure your parent or guardian agrees to you using Classyn.
Deleting your account
- Students: in the app or at app.classyn.org, go to Settings › Danger Zone › Delete Account and confirm with your password.
- Lecturers and admins, or anyone who can't sign in: email [email protected] from the address on your account, with "Delete my account". We will confirm it is you and delete it within 7 to 14 days.
- Deleting signs you out everywhere straight away and removes your name, email and profile. Seven days later the rest of your data is erased, apart from the few records under "How long we keep it" that keep course histories complete, which then show "Deleted user".
Keeping it safe
Connections are encrypted. Passwords are stored only as one-way hashes. On the web, you stay signed in with a cookie your browser cannot hand to other sites or scripts. You can turn on two-step sign-in, and end any session from Settings in the app.
Cookies and storage
The web app uses only what it needs: sign-in cookies; one that remembers this browser so two-step sign-in can recognise it (kept up to 400 days); and your browser's storage for your preferences and recent data, so it opens quickly on a weak connection. This website stores nothing about you.
Changes
If we change this notice, we will update the date above, and tell you in the app if the change matters.