Who this policy applies to

Edkin is a school-management platform used by schools and their authorised users. A school decides which people receive accounts and which school records are entered into Edkin.

The school is responsible for giving its community appropriate notices and obtaining any consent required for the information it asks Edkin to process.

Information we process

Account and identity details, including name, email address, profile information, role, school membership, and Google sign-in identifiers.
School records such as attendance, marks, homework, announcements, fees and receipts, transport assignments, library activity, documents, PTM records, and authorised health or safety information.
Location information when an authorised transport user shares a bus location, or when a user enters a pickup address or landmark or chooses a pickup reference on a map.
Photos, videos, receipts, documents, and barcode scans that an authorised user uploads or captures for a school workflow.
Photos, questions, and topics that a user submits to Animate, the lesson text and videos Animate creates from them, and questions typed into the Ask Edkin pilot.
Device information needed for notifications, security logs, diagnostics, and protecting accounts and services.
The school name and contact details that a visitor enters in the pilot-request form on edkin.in.

Bus location sharing

When an authorised driver starts a bus trip and grants location permission, Edkin collects the location of the driver’s phone to share the active bus location with linked parents and authorised school transport staff. During that trip, collection continues in the background, including while the phone is locked or another app is open.

Drivers see an explanation before the location permission request. Sharing stops when the driver ends the trip or signs out; drivers can also revoke location permission in their phone settings. Other users are not continuously tracked to use attendance, marks, fees, or school notices. Bus location is not used for advertising.

How we use information

To provide the school features requested by the school and its authorised users.
To authenticate users, enforce roles, protect school boundaries, and investigate misuse or service problems.
To deliver notifications and school communication, calculate reports, and maintain backups and service reliability.
To improve Edkin using aggregated or de-identified operational information where reasonably possible.

Where information is stored

Edkin’s servers, including its main database, run on Amazon Web Services (AWS Lightsail) in Mumbai, India.

Files that users upload, such as photos, documents, and receipts, are stored in Cloudflare R2, along with the videos Animate creates. Every night, Edkin also saves a backup copy of the full database, including school records, to Cloudflare R2. R2 does not offer a storage location in India, so this storage is in Cloudflare’s Asia-Pacific region, outside India.

The edkin.in website and the app.edkin.in web app are delivered through Cloudflare’s global network, which also checks visits for signs of automated abuse.

Sharing and service providers

We do not sell personal information or use school records for third-party advertising. Information is shared only with the relevant school and its authorised users, with vendors that help operate Edkin, when a school directs us to share it, or when required by law.

Edkin uses the service providers below. They may process information outside India, including in the United States, under their own security and privacy terms. Providers that your phone or browser contacts directly, such as map, notification, and book-lookup services, also receive its IP address and basic device information.

Amazon Web Services and Cloudflare: hosting, file storage, and backups, as described in “Where information is stored”.
Google: Google sign-in; maps in the Android app and the bus map in the iPhone app; notification delivery to Android phones and Chrome; the narration voice for Animate; and optional YouTube videos, described below.
Apple: notification delivery to iPhones and Safari, and the pickup maps in the iPhone app.
Expo: passes app notifications to Apple and Google for delivery. A notification contains only a generic message, such as “Open Edkin to read your school update”, a reference number, and the device’s push token. The notice itself is shown only inside Edkin, to the signed-in recipient.
Google, Mozilla, and Apple browser push services: deliver notifications to the web app. They receive the same generic message, encrypted so that they cannot read it.
OpenStreetMap Foundation: when someone searches for a pickup address, Edkin’s server sends the address and landmark text they typed to OpenStreetMap’s public Nominatim service to find matching places. Map images in the web app also load from OpenStreetMap.
Internet Archive (Open Library): when someone adds a library book by ISBN, the app looks up the book’s title and author on Open Library.
Hostinger: email, including verification codes and messages sent to support@edkin.in.
OpenRouter, AI model providers, and typesafe.ai: see “Animate and other AI features”.

Animate and other AI features

Animate turns a photo of a school problem, or a typed question or topic, into a short narrated explainer video. Students, teachers, principals, and school administrators can use it.

Animate uses third-party AI services, which process requests outside India. Edkin sends the photo and any question or note the user typed to OpenRouter, Inc., whose servers are in the United States. OpenRouter passes the request to a company that runs the chosen AI model. That model reads the photo or question and writes a short lesson script. A second AI model receives the script, which restates the problem in words but does not include the photo, and writes the code that draws the animation. Edkin’s server then sends the narration sentences to Google Translate’s text-to-speech service to create the voice.

The AI models can change. At present, standard requests use Google’s Gemini model to read the photo or question and Alibaba Cloud’s Qwen model to write the animation. Harder requests and retries use Qwen and DeepSeek models. Depending on the model, OpenRouter may choose among several companies that run it, including companies based in the United States and China.

Edkin does not add the user’s name, account details, school, or other records to these requests. The services do receive everything shown in the photo or written in the question, so photograph only the problem, without names, faces, or other personal details. Each service handles the content under its own terms.

Edkin keeps the photo, the lesson text, and the finished video with each Animate request, stored as described in “Where information is stored”.

Ask Edkin is an optional navigation helper that Edkin is piloting with selected adult users. It is not available to student or alumni accounts. When it is turned on for an account, the question typed into it, up to 300 characters, and a list of the Edkin features available to that account are sent to typesafe.ai, an AI service, to suggest where to go in the app. The question is sent without the user’s name, account, school, or records.

Optional YouTube learning videos

Edkin uses YouTube API Services for learning-video references. Where playback is enabled, the YouTube player loads only after you choose to load a video. YouTube may then receive your IP address, device and browser information, the app or website origin, the video identifier, and playback interactions. It may access or store cookies or similar information on your device and display third-party content, including advertisements, under Google’s policies.

Edkin does not add your school records, learning question, Edkin access token, or student identifier to the player request. This feature does not request access to your YouTube account, subscriptions, or watch history. Choosing to load a video does not make playback anonymous or replace any privacy agreement or permission required for a child account.

Google Privacy Policy

Children and school accounts

Edkin is not an open social network and does not invite children to create unrestricted public accounts. Student access is created or authorised through a school. Parents or guardians should contact their school about a child account, linked records, or consent.

Students can use Animate, so a photo or question a student submits is processed outside India by the AI services described in “Animate and other AI features”. Schools should cover this in the notices they give parents and obtain any consent required before students use Animate.

Retention, security, and choices

We keep information for as long as the school account or applicable service requires it, and longer only where security, legal obligations, or dispute resolution require it. Nightly database backups are deleted after 30 days. Schools can ask us to export, correct, restrict, or delete information subject to applicable obligations.

We use access controls, encryption in transit, tenant separation, backups, and operational monitoring. No online service can promise absolute security, so users should protect their sign-in account and report suspected misuse promptly.

The edkin.in website

When you request a pilot through the form on edkin.in, the school name and contact details you enter are saved to the Edkin team’s enquiry spreadsheet and emailed to the team, using Google services. We use them to respond to your request.

The website loads its fonts from Google Fonts, so Google receives your IP address and basic browser information when you visit.

Cloudflare Web Analytics counts visits to edkin.in without cookies and without identifying individual visitors.

Contact and updates

For a student record or school account question, contact the school first. For Edkin privacy or security questions, email support@edkin.in.

We may update this policy as Edkin changes. The current version and effective date will remain available on this page.