Only what the platform needs
Student profile fields, subject and batch enrolment, fee records, quiz and assignment scores, doubts asked and their responses. Nothing else is collected by default.
Security
Student data is treated as student data, not marketing fuel.
Apneeds is used inside classrooms, next to fee ledgers. That means we treat the data with the seriousness it deserves - clear scope, real access controls, encryption in transit and at rest, and honest posture on compliance.
What we collect, and why
A tight scope. No incidental collection.
Retention with an end date
Active data is retained while a student is on your roster. Archived data is retained for a defined period after a student leaves, then deleted. Owners can request earlier deletion in writing.
Encryption in transit and at rest
All connections use TLS. Data at rest is encrypted using industry-standard key management. Backups are encrypted with the same discipline as the primary store.
Role-based access, three clean roles
Owner, Teacher and Admin views are separated - each with a specific scope. A teacher does not see fee history. An admin does not see academic doubts. An owner sees the whole picture.
Access, plainly
Who sees what. Written down, not implied.
| Data | Owner | Teacher | Admin | Parent |
|---|---|---|---|---|
| Student profile | Yes | Yes | Yes | Own child |
| Fee history and ledger | Yes | - | Yes | Own child |
| Attendance | Yes | Yes | Yes | Own child |
| Quiz and assignment scores | Yes | Yes | - | Own child |
| Doubts asked and answers | Yes | Yes | - | Own child, summarised |
| Multi-branch roll-ups | Yes | - | Yes | - |
Compliance posture, honestly
Where we are today. And what we’re not overclaiming.
Applicable law
We handle personal data under Indian data protection law as it applies to education platforms, and act as a processor for the institute that operates on Apneeds. Where local rules layer on top, we work with owners to honour them.
Formal certifications
We do not currently claim ISO 27001, SOC 2 or similar third-party certifications. We’ll say so plainly here until we can point to a real report - that’s the honest bar for anyone reviewing us on trust.
Sub-processors
A short list of sub-processors is maintained and shared on request with institute owners. Any change is communicated in advance so the institute has room to review.
Data location
Primary storage is inside India. Backup regions are selected with legal and latency considerations, and shared with institute owners during onboarding.
Ask a specific question
Institute owners reviewing us on security can request our sub-processor list, retention schedules and incident-response outline.