Effective date: 21 October 2026
Summary
- KinderLynk is a school communication and management app provided by Codenius Tech. Schools buy the service and create every account. There is no public sign-up.
- For student records, the school is the controller and Codenius Tech is its processor. For the limited data we handle for our own purposes (accounts, support, security), Codenius Tech is the controller.
- We use your data only to run the school services described here. We do not sell data, show ads, use advertising IDs, or use analytics or crash-reporting SDKs.
- Location is collected only from the bus driver or caretaker app, only while a trip is running and the app is open, and is deleted after 60 days.
- Traffic uses HTTPS/TLS and passwords are stored hashed.
- You can ask us for access, correction or deletion at support@kinderlynk.com, or delete your account in the app.
1. About this policy
This policy explains how KinderLynk handles personal data. It applies to the KinderLynk mobile apps (Android and iOS) and the website kinderlynk.com. The apps are available in English, Hindi, Marathi and Gujarati. The service is provided by Codenius Tech ("Codenius Tech", "we", "us").
Related pages: Terms of Service, Account Deletion and Child Safety Standards.
2. Who is responsible for your data
- The school decides what student information is entered and why. It is the controller of student records (for example attendance, homework, results, fees, health records and day-care logs). Codenius Tech processes this data on the school's behalf and on its instructions.
- Codenius Tech is the controller for the limited data we handle for our own purposes: operating user accounts, providing support, keeping the service secure and meeting legal obligations.
If your question is about a school record, please contact your school first. We will help the school respond.
3. Who uses KinderLynk
Accounts are created by the school. Roles are parent or guardian, student (view-only access to their own records), teacher or staff, school administrator, and bus driver or caretaker. A person can belong to more than one school; each school's data is kept separate and this separation is enforced on our servers. KinderLynk is intended for adults (parents, guardians and school staff). Student logins are issued by a school at its discretion.
4. Data we handle and why
| Category | What it includes | Why |
|---|---|---|
| Account data | Name, email, phone, optional profile photo, password (stored hashed), chosen language, role and school links, push notification token for each device, notification inbox | To sign you in, show the right information for your role, and send alerts |
| School records about students | Class and section, roll or admission number, guardian links, attendance, homework, timetable, exam results and report cards, fee ledger, receipts and dues, library loans, school-store orders, transport route and stop, day-care log (meals, naps, diaper, mood, incidents, medication), health records (vaccinations, height and weight, allergy, blood group), concerns and tickets, incident reports, consent and questionnaire responses, transfer-certificate requests, certificates | Entered by the school and shown to parents, students and staff according to role, to deliver school services |
| Messages | Text and attachments (photos or PDF) between parents and teachers or staff, and notice-board posts. Stored on our server and delivered live over a secure WebSocket | To let members of the same school communicate |
| Photos and camera | Pick and Drop photos of the person dropping off or collecting a child; profile photos; visitor photos taken by staff at the gate; attachments to messages and incident reports. For authorised pick-up persons: name, relation, phone, photo, date of birth and gender, entered by the parent | Gate safety, identification within the school, and communication |
| Location | Bus driver or caretaker app only: precise GPS point and speed during a trip (see section 8) | To show parents where the school bus is |
| Live CCTV | Live video from school cameras, where the school enables it (see section 9) | To let authorised parents and staff watch the school's cameras live |
| Payments | Order id, payment id, amount and status for school fees and school-store orders. Card, UPI and bank details are entered with Razorpay and never reach or are stored by KinderLynk | To record fee payments and orders |
| Device and technical data | IP address and request logs on the server, app language, notification token | To run, secure and troubleshoot the service |
We do not use data for tracking, behavioural monitoring, profiling or targeted advertising.
5. Legal basis and consent
We process personal data on the following bases, depending on the law that applies:
- Consent. Under India's Digital Personal Data Protection Act, 2023 (DPDP Act), the personal data of a child may be processed with the verifiable consent of a parent or guardian. Schools obtain this consent from parents and guardians as part of admission and enrolment, so verifiable consent flows through the school. Adults who use the app, such as parents and staff, are also asked to consent where the school or law requires it. Consent can be withdrawn through the school or by writing to us.
- Providing the service. We process data to provide the school services that the school has contracted us to deliver and that you use.
- Legitimate interests and legal obligations. For account security, preventing misuse, support, and meeting tax and legal requirements such as payment records.
We process children's data only to provide school services. We do not track children, monitor their behaviour, or show them targeted advertising.
6. Children and COPPA
KinderLynk is not directed to children. Parents, guardians and school staff are the intended users. Accounts, including any student logins, are issued by schools. We do not knowingly allow a child to create an account on their own or give a child any public profile. Parental consent for children's data is obtained by the school. If you believe a child's data has been provided without proper authority, contact support@kinderlynk.com and we will act promptly. See also our Child Safety Standards.
7. Permissions we ask for
| Permission | Purpose | When it is used |
|---|---|---|
| Camera | Pick and Drop gate photos, profile photo, visitor photo at the gate, attachments | Only when you choose to take a photo |
| Location (precise and approximate) | Bus trip tracking | Bus driver or caretaker app only, while a trip is started and the app is open in the foreground |
| Notifications | Alerts such as messages, notices and updates | When the school or another member sends you something |
| Photos (photo library, iOS) | Choosing an existing photo for a profile picture or attachment | Only when you choose to attach a photo |
| Microphone (iOS) | Declared only because the system camera component asks for it. Audio is never recorded | Not used for recording |
| Internet | Connecting to the service | Whenever the app is used |
8. Location
- Location is collected only by the bus driver or caretaker app.
- It is collected only while a trip has been started and the app is open in the foreground. There is no background tracking.
- A precise GPS point and speed are sent to the school's server about every 10 seconds while the trip runs.
- Location data is stored for 60 days and then deleted.
- Parents see the bus position on a map. Map images come from OpenStreetMap. Parents' own location is never collected.
9. Live CCTV
Where a school enables it, authorised parents and staff can watch the school's cameras live. The video is relayed through our server as short temporary segments and is not kept as a recording. Parents can only see cameras for their child's branch or class.
10. Photos and on-device face detection
For Pick and Drop, the parent photographs the person dropping off or collecting a child at the gate. Face detection runs on the device using Google ML Kit, only to check that a face is visible in the photo. The photo is then uploaded and is visible to the school. Staff can also photograph visitors at the gate. We do not use these photos for anything other than the school's gate and safety records.
11. Third-party service providers
We share data only with the processors below, and only as needed to run the service.
| Provider | What it does | What it sees |
|---|---|---|
| Google Firebase Cloud Messaging | Delivers push notifications | Device push token and notification content needed for delivery |
| Razorpay | Payment checkout for school fees and school-store orders | Payment details you enter, which are handled by Razorpay and not by KinderLynk. We receive order id, payment id, amount and status |
| Google ML Kit (on device) | Checks that a face is visible in a gate photo | Runs on your device |
| OpenStreetMap tile servers | Map images for bus tracking | Device IP address and the map area requested |
| Google Fonts | Fonts downloaded when needed | Device IP address |
| Cloud hosting provider | Hosts our servers and stored data | Data stored on our servers, as a hosting provider |
We do not sell personal data. We do not show ads. KinderLynk contains no analytics SDK, no crash-reporting SDK, no advertising identifier and no cross-app tracking. We may disclose data if required by law or to protect safety, as described in our Child Safety Standards.
12. How long we keep data
- School records: kept for the period set by the school's contract with us and the school's own policies. The school decides how long its student records are held.
- Location data: 60 days.
- Live CCTV: not retained as a recording.
- Backups: roll off within 90 days.
- Payment records: kept as required by tax and accounting law.
- Account data: removed or anonymised when you delete your account (see Account Deletion).
13. Security
We use the following measures:
- All traffic uses HTTPS/TLS.
- Passwords are stored hashed.
- Role-based access, so each person sees only what their role allows.
- Separation of each school's data, enforced on the server.
- Signed, time-limited links for downloads.
- Card details are handled by Razorpay and do not reach KinderLynk.
No system is perfectly secure. If a personal data breach affects you, we will notify the school and the people concerned as required by applicable law.
14. International processing
Our service providers, such as cloud hosting, push notifications and fonts, may process data in countries other than the one where you live. Where this happens we rely on them only as processors for the purposes in this policy and take steps appropriate to the applicable law.
15. Your rights and how to use them
Depending on the law that applies to you, you may have the right to:
- access the personal data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- object to or restrict certain processing, and withdraw consent;
- receive your data in a portable format; and
- nominate someone to act for you, and make a complaint.
To exercise these rights, write to support@kinderlynk.com from your registered email address. For school records about a student, please contact the school, which is the controller; we will support the school in responding. You can also delete your account in the app under Account → Account Actions → Delete Account, or use the form on our Account Deletion page. We may need to verify your identity before acting. If you are not satisfied with our response, you may complain to the data protection authority that applies to you.
16. Grievance contact
Grievance / Data Protection contact: Codenius Tech, support@kinderlynk.com
17. Changes to this policy
We may update this policy from time to time. We will post the updated version on this page with a new effective date and, for material changes, tell schools or users through the app or by email. Please check this page regularly.
18. Contact
Questions about this policy: support@kinderlynk.com, Codenius Tech.