Who this policy covers
This policy explains how Animweb Technologies ("we") processes personal data in connection with Presence. It covers:
| You are | What applies |
|---|---|
| A visitor to this website | Sections 3, 6, 8, 9, 10, 12 and 13 |
| Someone who books a demo, sends a query or requests a quotation | The whole policy, for your contact details |
| A student, teacher or staff member using Presence through your institution | The whole policy - and your institution's own privacy notice |
| An institution administrator or billing contact | The whole policy |
Our role
- For data inside an institution's workspace - accounts, attendance, location readings, face templates, leave requests - the institution is theData Fiduciary under the Digital Personal Data Protection Act, 2023 ("DPDP Act") and decides why and how it is processed. We are its Data Processor and act only on its instructions, under our Terms of Service.
- For website visitors, demo requesters, sales contacts and billing contacts, we are the Data Fiduciary.
If you are a student or staff member, please contact your institution first about your data; we will help them respond.
What we process
Website forms: demo bookings, queries and quotation requests
- Name, work email, phone number, designation, institution name, city and state, and the number of users you expect.
- For a demo booking, your preferred date, time and format for the demo. For a quotation request, the plan details you ask about and, if you give it, your GSTIN.
- Messages you send us through the website forms or by email.
- Website account: to send a website form you sign in with Google. We receive and keep your name, email address, profile picture link and Google's identifier for your account, when you signed in, and which forms you sent. We never receive your Google password. You can see this information, sign out on all devices and delete the account yourself under My account. This account is separate from any Presence app account.
- Bot check: the website forms use Cloudflare Turnstile to tell people from automated spam. Turnstile looks at signals from your browser to do this; it does not use cookies for advertising.
- Website form submissions are emailed to our inbox through Web3Forms, a form-to-email service (see section 9).
- Technical data needed to deliver and protect the site: IP address, browser type and request logs.
Inside the Presence service
- Account data: name, email, roll number or employee ID, phone (optional), role, department, section, year and semester. Passwords are stored only as salted bcrypt hashes.
- Attendance data: classes joined, check-in and check-out times, verified minutes, status, presence-check responses, corrections and their reasons.
- Location data: see section 4.
- Device data: a one-way hash of device characteristics used to bind a student's attendance to their own phone, and the app's install state.
- In-class integrity signals: while a student is checked in, events such as leaving the app, opening the class in several tabs or pasting into the code field.
- Face templates: only if enabled; see section 5.
- Room sound check: when a teacher enables it, the phone listens to the microphone for a few seconds while joining or answering a presence check, to hear the classroom's signal. The audio is analysed on the phone and discarded; only the decoded number (which identifies the class, not the person) is sent. Nothing is recorded.
- Account security data: if you turn on two-factor authentication, an encrypted authenticator key and hashed recovery codes; a list of your signed-in devices (browser type, a shortened network address and last activity); one-time password-reset tokens, stored only as hashes and valid for 30 minutes.
- Sign in with Google: only if your institution turns it on and you choose to use it. Google confirms your email address and we keep only Google's permanent identifier for your Google account, to make sure later Google sign-ins come from the same account. We do not receive your Google password and do not request access to your mail, files or contacts.
- Leave requests and documents students choose to submit (for example scanned medical certificates), approval decisions and the health centre's verification. Documents are stored in the institution's own database, photo metadata (including where a photo was taken) is removed on upload, and only the student, their mentor, the approving dean or head of department and health officers can open them. Each opening by staff is logged.
- Health centre records, if the institution uses this module: blood group, allergies, medical conditions, an emergency contact and health-centre visits. These are visible only to the institution's health officers and the student; administrators see totals only.
- Transport and hostel records, if used: bus route, stop, fee status and boarding register; hostel room and roll call.
- Fees and dues, if used: the fees raised for a student, payments recorded by the institution (amount, date, method and reference) and receipts. Presence does not take or store card or bank details; payments are made to the institution directly.
- Marks, if used: assessment marks entered by teachers and the Examinations department. Students see their own marks once published; across classes only the Examinations department sees them, each office limited to its own school or department.
- Placement records, if used: the drives and notices shown to a student, and their applications (answers to the placement form, status). Only the placement cell and the student see them.
- Library records, if used: books borrowed, due and returned, reservations and fines. These are visible to the library and the reader; administrators see totals only.
- Staff records, for staff: arrival and departure at the gate (marked by an encrypted face template, never a photo), staff leave and balances, and employee details kept by HR such as designation and joining date.
- Help & Safety reports a person chooses to make: complaints (encrypted for the department that handles them), incident and SOS reports with location, and lost-and-found posts.
- Campus network check: if the institution turns it on, the network address a student's phone uses when marking attendance is compared with the campus address ranges. Only the result is kept with the attendance record.
- Audit logs of administrative actions, and security logs (sign-ins, IP addresses, failed attempts).
Billing
- Billing contact, institution legal name, GSTIN and address, invoices, receipts and payment references.
- Payment is only by bank transfer against our GST invoice, so we receive only the bank-transfer reference (such as the UTR) that comes with each payment. We never collect card details or online-banking credentials.
Location data
- A student's location is read only while they have a live class or event open on Mark Attendance, or are checked in to it: every few seconds on the joining screen so they can see whether they are inside, then while checked in the phone checks it against the classroom and campus boundaries on the phone itself and reports a position about once a minute (every 15 seconds while outside or unsure), to confirm they are still inside.
- For each class we keep the most recent reading, its accuracy and the distance from the classroom. We do not store a route or movement history.
- Teachers capture the classroom's coordinates when they start a class. Administrators set the campus boundary.
- Nothing is collected when the app is closed, when no class is live, or when the student is not on the Mark Attendance screen of a live class.
Face verification
- Face verification is off unless the institution or a teacher turns it on.
- When a student registers, the camera image is analysed on their own device to produce a numeric template (128 numbers). The image is never uploaded or stored.
- The template is encrypted with AES-256-GCM before storage and is compared only with fresh templates from the same student at class check-in.
- Biometric data is sensitive. Institutions must inform students and obtain any consent required before enabling the feature. A student or administrator can reset a Face ID at any time, which deletes the stored template.
Why we process it
| Purpose | Basis |
|---|---|
| Recording and verifying attendance; leave and reporting workflows | The institution's instructions; the institution's own lawful basis (consent or a legitimate use under the DPDP Act) |
| Setting up and running demo workspaces after a booking, sending sign-in details and reminders | Your consent when you submit the demo booking form |
| Answering a query or quotation request, and following up on a demo | Your consent; you can opt out at any time |
| Billing, invoicing and tax records | Performance of the contract and legal obligations (GST and accounting laws) |
| Security, fraud prevention and keeping logs | Legitimate uses and legal obligations, including CERT-In directions |
We do not sell personal data, use it for advertising, build marketing profiles of students, or use Customer Data to train machine-learning models.
When a new password is chosen, we check it against known data breaches using the Have I Been Pwned "range" service: only the first five characters of a one-way hash of the password are sent, so neither the password nor its full hash ever leaves our servers.
Students under 18
Some students may be under 18. Institutions that onboard them are responsible for obtaining verifiable consent from a parent or lawful guardian where the DPDP Act requires it, or for relying on an exemption available to educational institutions. Presence limits monitoring to attendance during classes and events, and never targets advertising at anyone.
Sharing
- Within your institution, according to roles: teachers see their classes; mentors and heads of department see their sections and departments; administrators see the institution.
- With our sub-processors listed below, only to run the Service and under written obligations at least as protective as this policy.
- When required by law, such as a valid order from a court or authority. Where lawful, we tell the institution first.
- In a business transfer, to a successor bound by this policy, with notice to customers.
Sub-processors and locations
| Provider | Purpose | Location |
|---|---|---|
| Railway Corporation | Application hosting (API, background jobs, cache) | Singapore (Railway Southeast Asia region) |
| MongoDB, Inc. (Atlas) | Managed database | Mumbai, India (default region) |
| Cloudflare, Inc. | Website and app delivery, DDoS protection, Turnstile bot checks, and the website account database (D1) | Global edge network |
| Google LLC | Sign in with Google on the website, and in the app where an institution turns it on | Global |
| Web3Forms (Web3Creative, Kerala, India) | Form-to-email delivery of website form submissions (demo bookings, queries and quotation requests) | United States (servers in the US-East region) |
| Resend, Inc. | Transactional email (sign-in details, demo reminders, receipts) | United States |
Some providers process data outside India. We transfer data only to countries not restricted by the Government of India under section 16 of the DPDP Act, and with contractual safeguards. Institutions on their own domain can choose where their database is hosted.
Retention
| Data | Kept for |
|---|---|
| Paid workspace data | For the subscription, then 90 days for export; deleted from backups within a further 35 days |
| Demo workspace data (not converted) | Deleted 30 days after the demo ends |
| Website accounts (name, email, Google identifier) | Until you ask us to delete them, or 2 years after your last sign-in |
| Demo bookings, queries and quotation requests | Up to 2 years after our last contact, or until you ask us to delete them |
| Invoices and payment records | 8 years, as required by tax and accounting laws |
| Security and access logs | 180 days |
Institutions decide how long their attendance records are kept and can delete users or export data at any time.
Security
- HTTPS everywhere with HSTS; strict Content-Security-Policy on the website and app.
- A separate database for each institution; role-based access enforced on the server.
- Short-lived access tokens with rotating, http-only refresh cookies; login lockout after repeated failures.
- Face templates encrypted with AES-256-GCM; workspace exports encrypted with a one-time passphrase.
- Audit logs of administrative changes; least-privilege access for our staff.
If a personal data breach affects a workspace, we notify the institution without undue delay and support its notifications to the Data Protection Board of India and affected people. Where we are the Data Fiduciary, we make those notifications ourselves. Read more on our Security page.
International standards
Our handling of personal data follows the privacy principles of ISO/IEC 29100 and the guidance of ISO/IEC 27701 (privacy information management) and ISO/IEC 27018 (personal data in the public cloud), alongside the security practices ofISO/IEC 27001/27002 described above. In practice:
- Purpose and legitimacy: data is used only for attendance and the campus services the institution turns on, never for advertising or profiling for sale.
- Collection limitation and data minimisation: location only during a class the student has open, one latest position per class, face templates instead of photos.
- Use, retention and disclosure limitation: each role sees only what it is responsible for (for example only the Examinations department sees marks across classes, and only the placement cell sees placement applications); data is kept only as long as section Retention allows.
- Accuracy and quality: people can see their own records, and corrections are made with a reason that is kept in the audit log.
- Openness, transparency and notice: this policy, the institution's own notice and the sub-processor list explain what is processed and why.
- Individual participation and access: the rights in the next section, handled with the institution as the Data Fiduciary.
- Accountability: written processing terms with each institution, an audit log of administrative actions, and breach notification without undue delay.
- Information security: the measures listed under Security, reviewed when the Service changes.
These references describe how we design and operate the Service; they are not a claim of certification by an accredited body unless a contract says so. In the language of these standards, the institution is the PII controller and Animweb Technologies is the PII processor.
Your rights
Under the DPDP Act you have the right to:
- obtain a summary of the personal data processed about you and the processing activities;
- have inaccurate or incomplete data corrected or completed, and data you no longer want processed erased, unless it must be kept by law;
- withdraw consent where processing is based on consent - as easily as you gave it;
- nominate a person to exercise your rights in the event of death or incapacity;
- have a grievance addressed, and then complain to the Data Protection Board of India.
Students and staff should make requests to their institution, which can act through Presence. For website, demo or sales data, write toanimwebtechnologies@gmail.com. We may need to verify your identity before acting.
Cookies and storage
- This website uses no analytics or advertising trackers. When you sign in it sets two strictly necessary cookies: an http-only session cookie that keeps you signed in (30 days, or until you sign out), and a cookie holding only "signed in: yes" so the header can show your account icon. Cloudflare Turnstile may store what it needs for the bot check on the forms. When you submit a form, what you type is sent to Web3Forms, which emails it to us.
- The Presence app uses one strictly necessary, http-only cookie to keep you signed in securely, and browser storage for your session, offline app files and preferences. These cannot be switched off because the app does not work without them.
Changes
We will update this policy when our processing changes and change the "last updated" date above. For material changes we notify institution administrators in advance by email or in the app.
Grievance Officer
In accordance with the DPDP Act and the Information Technology Act, 2000 and rules made under it, our Grievance Officer is:
Pushpendra Singh Yadav (Founder & CEO)
Animweb Technologies, SCO 24 (Basement), District One Market, Sector 68, Mohali, Punjab, India
Email: animwebtechnologies@gmail.com
We acknowledge grievances within 48 hours and aim to resolve them within 30 days.
Questions about this document? Write to animwebtechnologies@gmail.com. Data-protection requests and grievances go to our Grievance Officer atanimwebtechnologies@gmail.com.