GRobotics

Privacy

What we hold, and what we refuse to

This page states what the platform already enforces. The rules below are not a policy layered over the product — they are how it is built, and most of them are enforced in the database rather than by promise.

Pending legal review. This policy is written by the team that built the platform and reflects how it works today. It has not yet been reviewed by counsel; wording may tighten, but the practices it describes will not loosen.

What we collect, and why

The enquiry form
Name, school, role, email, phone if you give one, and your message. Used to reply to you and for nothing else. Kept until the enquiry is resolved, or deleted earlier when you ask.
Student records, when your school runs the programme
The least the platform can hold and still answer “how do you know?”: enrolment, attendance, assessment evidence, and one guardian contact number. No home address, no photograph, no medical detail. Date of birth is collected only for open and adult registration, where age has to be established — a school-managed student’s record does not carry it.
Two functional cookies
A session cookie for signed-in panels and a language cookie for English/Nepali. There are no analytics cookies, no advertising trackers, and no third-party scripts on this site.

What never appears in public

No identifiable faces, anywhere
Any image we publish shows objects, builds, and hands. A mandatory reviewer checklist enforces this before anything goes public — it is a publication gate, not a guideline.
No surnames or contact details on public pages
A student’s first name appears on a published project or certificate only where a consent record covers it. Consent is a typed, timestamped, revocable record — revoking it unpublishes immediately.
No rankings
Students see their own growth. The platform produces no class rankings and no comparative leaderboards, so there is nothing of that kind to leak.
No cross-school visibility
One school’s people never see another school’s students — enforced in the database itself, not just the interface. Any benchmark that leaves our office is anonymized first.

Your data, your rights

Export, freeze, or anonymize
Every partner school can have its data exported, frozen, or anonymized on request — three explicit operations, each leaving an audit record of who asked and when.
An append-only ledger
Security- and privacy-relevant actions — sign-ins, credential changes, consent changes, exports — write to an audit ledger the running system cannot rewrite.
Parents
Parents receive a printed report each term, including the lab’s incident log. There are no parent accounts, so there is no parent login data to protect — and we hold one contact number per student, nothing more.

Third parties

The contact page embeds a Google Map of our Buddhanagar lab, so loading that page contacts Google under Google’s own privacy terms. That embed is the only third-party service on this site.

Questions and requests

Write to grobotics071@gmail.com — for deletion requests, consent questions, or anything this page leaves unanswered. GRobotics Pvt. Ltd., Buddhanagar, Kathmandu, Nepal.