Privacy
Your data, in plain words
Short version: we don't sell anything, there are no ads, and the only personal thing we touch is your registration number — because that's how a result gets fetched.
The short version
- No ads. No data selling. No ad trackers. Ever.
- Your registration number is used to fetch your result, and nothing else.
- Analytics get a hash of your number, never the number.
- There's no account and no password. Almost everything stays on your phone.
- You can switch analytics off, and you can email us to delete anything.
Who runs this
BEUConnect is a student project, built and run by one person — Prit, at GEC Sheikhpura. It is not official, not affiliated with Bihar Engineering University, and not run by a company. That also means there's no legal team and no growth department: just one inbox.
Contact for anything in this page:pritform@gmail.com.
What we actually handle
This is the whole list. If something isn't here, we don't have it.
| What | Why | Where it goes | How long |
|---|---|---|---|
| Registration number | To fetch your result, rank, merit standing and class routine. Its digits also tell the app your batch, branch and college, so screens open on the right one. | Our server (beu.prit.eu.org), then the BEU result portal. Saved on your phone so you don't retype it. | On your phone until you clear it. On our server: not stored — it lives only for the length of the request. |
| Guardian's mobile number (attendance only) | It's the login the GEC Sheikhpura attendance portal uses. We pass it through so the portal can answer. | The college's attendance service (Supabase). | Not stored by us, not logged, not in any error message. |
| Feedback you send | To read it and reply. | Our server, then a private Telegram channel. Includes the page you were on, your IP and browser string, which the server sees anyway. | Until the issue is closed. |
| Usage analytics | To know which screens people actually use, so we stop building dead ones. | Google Analytics 4, through our own server. | 14 months (Google's default). |
| Stuff saved on your phone | Offline access: saved results, cached papers, theme, attendance you logged, reminders. | Only your device. We never see it. | Until you clear the app's storage. |
What we never collect
Location, contacts, camera, microphone, photos, files, health data, financial data, messages, call logs, your advertising ID, biometrics. We don't have an account system, so there's no password to leak. The app asks for no permission it doesn't visibly need.
Analytics, specifically
The site sends events with Google's gtag.js. The app does the same job without the script: it batches events and hands them to our own server, which forwards them to Google with a secret the app never sees. One property, one vocabulary, so the two can be compared.
An event can carry:
- the screen you opened and the feature it belongs to;
- the action you took (opened a paper, saved a result, marked attendance);
- your branch, college and batch as codes;
- a 10-character hash of your registration number — so we can count distinct students;
- app version, platform, and a random client id.
An event never carries:
- your registration number, name or phone number;
- anything you typed. Search sends the word count, not the words. Feedback sends its type, not its text.
On the website, the page address sent to analytics has its query string removed, so a?reg=… in a URL never reaches Google.
Turning it off: in the app, Settings → About → Send anonymous usage. It clears whatever is queued and every later event is a no-op. On the site, an ad blocker does the same job.
Cookies and local storage
No ad cookies, no third-party tracking cookies, no cookie banner because there's nothing to consent to. The site uses local storage for your theme and for attendance you log, and a service worker caches pages and PDFs so they open offline. The app keeps its data in local storage under beu. keys. Clearing site data or app storage wipes all of it.
Public data we republish
Result tables, merit lists and the student register are built from BEU's own published result pages. That data is already public — we just make it searchable, sortable and readable on a phone. We don't add anything to it: no phone numbers, no email, no date of birth, no gender, no category.
If your row is here and you want it gone, email us with the registration number and we'll remove it. You don't have to explain why.
Who else touches the data
| Service | What it does for us | What it sees |
|---|---|---|
| Cloudflare | Hosts the site and the API. | Requests, including IP addresses. |
| Google Analytics | Counts usage. | The events described above, with a hash — never your number. |
| Supabase | Backs the GEC Sheikhpura attendance portal. | The registration number and the guardian mobile you enter. |
| Telegram | Delivers feedback to us. | Your feedback text, optional contact, IP and browser string. |
| GitHub | Serves app updates. | Nothing personal — it's a public download check. |
| BEU result portal | The university's own system. | The registration number you ask us to look up. |
We don't sell data, share it for advertising, or hand it to anyone else.
Some of these run outside India — Google and Cloudflare may store data on servers elsewhere. They're the only ones that do, and the analytics they hold is aggregate and hashed, never a registration number.
Your rights
Under India's Digital Personal Data Protection Act, 2023 — and just as a decent default — you can:
- ask what we hold about you;
- get it corrected if it's wrong;
- get it deleted — including your row in a published table;
- withdraw consent by switching analytics off;
- complain, first to us, and then to the Data Protection Board of India.
Email pritform@gmail.com. We answer within 30 days, usually much faster. Because there are no accounts, most of what we'd delete is already only on your phone — clearing app storage removes it instantly.
If you're under 18
BEU students are normally 18 or older. If you're younger, please use BEUConnect with a parent or guardian's permission, and don't send us anyone else's personal details.
Security
Everything runs over HTTPS. We don't store passwords or payment details, and the app carries only publishable keys. We collect as little as possible on purpose, because the safest data is the data you never collected. No system is perfect, and we won't pretend otherwise.
Changes
Last updated 31 October 2026. If this page changes in a way that matters, the date changes and the app's About screen says so. We won't quietly rewrite it.
Still reading? Ask us anything.
Unofficial student project. Not affiliated with Bihar Engineering University.