Your institute's records, looked after.
An institute runs on its records: admissions, fees, attendance, results. This page says plainly who owns them, how they're protected, and what you can do with them, across GIMS, Grawity Classroom and Grawity Events.
In short.
It's your data
Your institute's records belong to your institute. Grawity uses them only to run the products for you. We don't sell data or show ads.
Kept apart
Every record belongs to one institute, and every request is checked on the server against the institute and role of the person making it.
Nothing quietly lost
Students are archived, not deleted, and a wrong payment is reversed with a reason, so the history always adds up.
You can take it with you
An institute's admin can export all its GIMS data at any time, and can ask us to delete the institute's account and data.
Each person sees only their part.
- Roles enforced on the server. Admin, teacher and student permissions are checked on every request, so typing a URL can't open a screen someone isn't allowed to see.
- Teachers see their own. In GIMS a teacher works with the batches assigned to them; in Classroom with the courses and batches they teach. The admin sees the whole institute.
- Event volunteers see the minimum. In Grawity Events, volunteers and gate scanners never see emails, phone numbers, payment history or the attendee list.
- Aadhaar kept to four digits. GIMS stores only the last 4 digits of an Aadhaar number, never the full number.
How accounts are protected.
- HTTPS everywhere. Every connection to the products is encrypted.
- Passwords never stored. Only a one-way hash is kept. In GIMS, a new password needs 8 or more characters with upper and lower case, a number and a symbol.
- Short-lived codes. Sign-in and password-reset codes are stored hashed, expire after 10 minutes and allow only a few tries.
- Sessions that end. In GIMS, changing a password signs that account out everywhere else. Repeated sign-in attempts are rate-limited.
- Email you can trust. Emails come from Grawity's own domain, authenticated with SPF, DKIM and DMARC so they're harder to fake.
History that stays accurate.
- Archive, don't delete. An archived student leaves the active lists, but their admissions, fees, attendance and results stay exactly as they were.
- Corrections, not deletions. A wrong payment is reversed with a reason. It stays visible and stops counting towards the totals.
- Protected from accidents. A course or batch that students' records point to can't be deleted.
- Who did what. GIMS keeps a record of important actions, such as who admitted, edited or collected what and when, and shows recent activity on the dashboard.
Your copy, whenever you want it.
- Export any time. In GIMS, Settings → Data Backup downloads the institute's complete data as a JSON backup, or as an Excel copy to open yourself.
- Results and grades out. Classroom's gradebook and progress reports download as Excel or PDF, and Events exports attendees as CSV.
- Leaving is your choice. An institute can ask us to delete its account and all its data. Students and staff who want their information seen, corrected or removed should start with their institute, which manages those records, and we'll help it respond.
The services we rely on, named.
They handle data only to provide their part of the service.
Hosting & databases
MongoDB Atlas stores the GIMS and Classroom databases. Render runs the GIMS service behind Cloudflare, and Vercel hosts the websites and Classroom. Grawity Events keeps its data in a managed Postgres database.
Files & email
Cloudinary stores student photos and institute logos. Google Workspace sends the products' emails: receipts, reminders, sign-in codes and admission confirmations.
AI in Classroom
Classroom's AI features (drafting questions, suggesting marks and the lesson tutor) use Google's Gemini. Only the text a request needs is sent, a teacher approves anything AI drafts, and each institute has daily limits.
Payments in Events
Online payments in Grawity Events go through Razorpay. Card and UPI details are entered with Razorpay, not Grawity, and a ticket is marked paid only once Razorpay confirms the payment.
GIMS records the fees an institute collects, but doesn't take payments itself. The full details are in the GIMS privacy policy and the terms.
A person, not a ticket queue.
Questions about your data, a problem in a product, or a request to export or delete: write or call, and the Grawity team answers.