PRIVACY & DATA USE
IETA Connector Privacy Policy
This policy explains how IETA Pvt. Ltd. processes personal data when parents, legal guardians and students use IETA Connector and related Connector web services.
IETA Login verifies your account. Connector then uses active relationships supplied or approved by participating institutions to show only the children, services and updates you are authorised to access. IETA does not sell personal data or use Connector child records for targeted advertising.
1. Who we are
IETA Connector is operated by IETA Pvt. Ltd. (“IETA”, “we”, “us” or “our”). Our registered postal address is A2, 103, Marion Residency, Dumas, Surat, Gujarat, India. Connector is a family access and communication service that brings authorised information from participating institutions, Campus and RideOS into a private parent, legal guardian or student experience.
For privacy questions or grievances, contact our Grievance Officer, Mr. Akash Patel, at grievance@ieta.in. General product support is available at support@ieta.in.
2. Scope
This policy applies to connector.ieta.in, Connector sign-in and authorisation, the Connector dashboard, AURA features within Connector, Telegram delivery settings, support features and related technical services. Participating institutions remain responsible for the accuracy and administration of the education, training, transport, payment and student records they originate. Their own privacy notices may also apply.
3. Personal data we process
| Category | Examples |
|---|---|
| Identity and account data | Name, IETA account identifier, email address, mobile number, sign-in method, session and authentication information. |
| Family and authorisation data | Parent, legal guardian or student role, child–adult relationship, institution membership, permission status and access history. |
| Child and institution data | Child name, institutional identifiers, institution, class, programme, campus, vehicle or route association, and relevant branding. |
| Campus and RideOS information | Authorised attendance, timetable, learning, training, pickup, drop, route, vehicle, operational and service updates supplied by the responsible institution. |
| AURA interactions | Questions, instructions and responses generated from records that the signed-in account is authorised to access. |
| Telegram delivery data | Connection status, delivery destination identifier, subscription choices and message-delivery status when Telegram delivery is enabled. |
| Payment and support data | Payment action or status references, support requests, correspondence and information supplied when seeking assistance. Payment providers process card, bank or payment-instrument details under their own notices; Connector should not require full card or banking credentials. |
| Technical and security data | IP address, browser and device information, timestamps, request identifiers, audit events, error reports and security logs. |
4. Why we process personal data
We process personal data to authenticate users; verify active parent, guardian or student relationships; display only authorised child and institution records; switch safely between authorised children; provide Campus, RideOS and AURA features; deliver requested Telegram notifications; support payment actions; answer support requests; prevent misuse; maintain security and availability; comply with law; and establish, exercise or defend legal rights.
Where consent is required, the notice presented at collection should describe the data and purpose in clear language and provide a practical way to withdraw consent. Withdrawal does not affect processing already lawfully completed and may prevent a feature from continuing where its data is necessary.
5. Children’s and student data
Connector is designed for authorised parents, legal guardians and students. Successful identity sign-in alone does not grant access to a child’s records. Access depends on an active relationship supplied or approved by the responsible institution.
Where applicable law requires parental or lawful-guardian consent before processing a child’s personal data, IETA and/or the responsible institution must obtain or verify that consent before enabling the relevant processing. Connector must not use children’s data for targeted or behavioural advertising and must not process it in a way likely to harm a child’s wellbeing.
6. Sources of data
We receive data directly from users; from the central IETA identity service; from participating institutions and their authorised administrators; from Campus and RideOS; from AURA interactions; from Telegram when a user links delivery; from payment or support providers; and automatically from security and service operations.
7. Sharing and service providers
We disclose personal data only where needed for the purposes in this policy, including to the participating institution responsible for the record; IETA identity, Campus, RideOS and AURA services; Telegram when delivery is requested; payment providers when a payment action is initiated; hosting, security, logging and support providers acting under appropriate obligations; professional advisers; and public authorities where disclosure is legally required.
We do not sell personal data and do not use Connector child records for targeted advertising. Access by IETA personnel is limited to authorised support, security and service duties through separate administrative tools and does not create eligibility for a family Connector account.
8. International processing
Some service providers may process data outside the user’s state or country. Where cross-border processing occurs, IETA will apply contractual, organisational and technical safeguards and any transfer restrictions required by applicable Indian law.
9. Retention
We retain personal data only for as long as needed for the stated purposes, while the relevant account or institution relationship remains active, for legitimate security and audit periods, and as required by law or an institution’s lawful retention obligations. When an institution removes or expires an authorisation, Connector access to the affected child should end. Deletion or de-identification may be delayed where retention is required for security, dispute resolution, legal compliance or protection of rights.
10. Security
IETA uses measures intended to protect Connector data, including encrypted transport, access controls, product-managed authorisation, child-context separation, signed service events, audit logging, security monitoring and restricted administrative access. No online service can guarantee absolute security. Users should protect their devices and sign-in methods and report suspected misuse promptly.
11. Your choices and rights
Subject to applicable law, you may ask for information about processing; access to personal data; correction, completion or updating of inaccurate data; erasure where retention is no longer required; withdrawal of consent where processing relies on consent; and grievance redressal. Requests involving institution-originated records may need to be verified or fulfilled with the responsible institution.
To exercise a privacy right or raise a grievance, email grievance@ieta.in with enough information to identify the account and request. Do not send passwords, one-time passwords, full payment credentials or unnecessary child records by email. We may request proportionate verification before acting.
12. Cookies and sessions
Connector uses cookies or similar storage required for secure sign-in, session continuity, child context, security and essential preferences. Essential authentication and security technologies cannot be disabled without affecting the service. Connector does not require public advertising cookies for its family dashboard.
13. Security incidents and complaints
Where a personal-data breach or security incident triggers a legal notification obligation, IETA will provide notices to affected persons and relevant authorities in the form and time required by applicable law. Complaints should first be sent to the Grievance Officer at grievance@ieta.in. This does not remove any right to approach a competent regulator or authority where available.
14. Changes to this policy
We may update this policy when Connector features, participating services or legal requirements change. The updated version will state a new effective date. Material changes may also be communicated through Connector or the contact details associated with the account.
15. Contact details
IETA Pvt. Ltd.
A2, 103, Marion Residency
Dumas, Surat, Gujarat, India
Grievance Officer: Mr. Akash Patel
Email: grievance@ieta.in
Support: support@ieta.in