Geofenced attendance
A configurable radius around every venue. Only devices physically present inside the perimeter can punch in — enforced on the server via Haversine distance, not guessed on the client.
“Presence is a coordinate, not a signature.”
Presence,
precisely.
Animweb Presence is the attendance platform that knows where you are, knows who you are, and stays out of your way. Geofenced. Face-verified. Privacy-first. Built in India for every campus in India — by Animweb Technologies.
Geofenced presence
Face-verified, privacy-first
PWA · Background tracking
Admin console · CSV export
Institution-owned data
§ 00
What is Presence?
A plain-English overview
Presence is the quiet, intelligent layer that answers a single question every institution asks, every single day: “Who is actually here, right now?”
Taking attendance on paper is slow. Roll-calls waste minutes of every lecture. Biometric scanners queue two hundred students in a corridor. QR codes get screenshotted and passed around. Presence replaces all of that with a single, precise signal — anchored to the student's location and the student's face.
A student walks into the venue. Their phone quietly confirms they are inside the GPS perimeter. A two-second face check verifies identity. The record lands in the admin console. No queues. No fraud. No paper.
That is Presence. Everything else — the dashboards, the CSV exports, the automatic on-duty leaves, the student profiles, the department pages — is built on that one honest signal.
Three facts
- Presence is not a face database. It stores 128 irreversible numbers per student — never an image, never a photograph, never a biometric you can look at.
- Presence is not yours to lose. Your institution owns every row of attendance, every profile, every export. Animweb Technologies owns only the platform it runs on.
- Presence is not an experiment. It ships today. It has a live demo. It has pricing. It has a three-year roadmap with the next two quarters already in development.
Built for
Annual techfests · department symposia · orientation weeks · placement drives · sports meets · cultural festivals · hackathons · workshops · — and, by Q2 2026, daily classroom attendance.
§ 01
Present — What Ships Today
Deployed · v0.9 · Production
Face verification, privacy-first
We never store photographs. Each enrolled face becomes a 128-dimension mathematical descriptor — an irreversible fingerprint used strictly for 1:1 verification. Descriptors are hidden from admin listings, CSV exports, and every response except the client-side match handshake itself.
“The face never leaves the camera — only the numbers do.”
Auto punch in & out
Cross the perimeter, you are in. Leave it, you are out. A background tracker (PWA) watches the boundary and closes sessions precisely, without hand-waving.
Admin operations panel
Live headcount, event roster, CSV exports (present & absent), mass punch-out, venue & radius control, core-team management. Built for coordinators, not engineers.
Event lifecycle, done right
Ending an event de‑registers participants — it doesn't delete them. Their face data is preserved so returning students re-register next time without re-enrolling. Zero duplicates, ever.
Security without theatre
JWT auth with rotating secrets, rate-limited login, CORS allow-listed, HTTPS-only cookies, admin-only dashboard. Pushed through a hardened deployment pipeline on India-proximate infrastructure.
Ledger-grade CSV export
Download present or absent rosters as UTF-8 CSV (Excel-ready, with summary rows). Filtered by date and event — inactive participants from old events never bleed in.
§ 01·B
Why Presence — the honest case
For decision-makers
Built in India, for India's campuses.
Our infrastructure sits India-proximate. Our team is in Chandigarh. Our price is quoted in rupees. Support is during IST working hours — by a human who knows your event schedule, not a ticket router three time zones away.
Your data. Full stop.
Rosters, attendance, marks, departmental data — all of it remains the property of your institution. We operate under a written data-processor engagement. On exit, we export and delete. We don't mine, we don't resell, we don't “anonymise and benchmark.”
Face data that can't betray you.
We never keep a photograph. A 128-dimensional descriptor is a one-way street — you can verify a face against it, you cannot reconstruct the face from it. Descriptors are excluded from listings, CSVs, and responses. DPDPA 2023 is in the wiring, not the fine print.
No queues, no paper, no theatre.
A coordinator spends less time pushing a clipboard. A student spends two seconds on a phone. A dean gets a spreadsheet that reconciles with the venue's actual attendance. That's the entire pitch — and it's already working.
Honest pricing, honest stage.
We are early. Our price reflects that. ₹10,000 to run an event. ₹12,000 for the full set-up-and-train engagement. If you are going to pay us, you should know what you are paying for — and what you are not.
A platform, not a plug-in.
Presence is the foundation. On top of it land on-duty-leave automation, classroom WiFi attendance, marks, department profiles, parent portals — each shipped from a roadmap you can see, not a PowerPoint you can't cite.
§ 02
Connect — The Direction
In Development · 2026
Attendance is not an island. It is a signal about where a student was, why, and what that means for every classroom downstream.
The next release stitches event attendance into the rest of a student's day — so missing a lecture for a valid campus event is handled automatically, not with a printed form and three signatures.
Student marks attendance at a campus event
Geofence verifies presence. Face descriptor verifies identity. One tap, one record.
System checks the student's timetable
If the event overlaps with a scheduled class, an on-duty (OD) leave request is generated automatically — no separate form, no chasing signatures.
Faculty approves from a single inbox
Teachers see the OD, the venue coordinates, the punch‑in/out times, the student's history. Approve or deny in one click.
Classroom attendance is corrected automatically
The period the student missed is reclassified as OD. No cross-system double-entry. No end-of-semester reconciliation meetings.
WiFi indoor attendance (beta)
GPS loses resolution indoors. We pin presence to the classroom itself via WiFi SSID/BSSID fingerprints — accurate to the room, not the building.
§ 02·B
Use Cases — Where Presence earns its keep
Campus scenarios
The flagship techfest
Two thousand students, forty events, three days, one central lawn. Presence geofences each sub-venue, verifies each entrant, and gives organisers a live headcount that reconciles with the vendor's food count — without a single spreadsheet being e-mailed around.
2,000 participants · 40 events · 3 days
Departmental symposium
A two-day CSE or ECE symposium with a narrow participant list. Presence limits registration to the department, face-verifies on entry, exports a clean attendance certificate roster. Credits — CRT, NPTEL, professional society — flow without manual tallying.
Role-scoped · certificate-ready
First-year orientation
Incoming batches enrol in minutes. A self-enrolment flow, a quick face capture, and they are good for every welcome session, campus tour, and orientation lecture — with parents and wardens able to confirm attendance from a read-only portal.
Self-enrolment · parent read-only
Placement drives & interviews
A drive with eligibility cut-offs and tight timing windows. Presence verifies only eligible candidates arrive, logs their slot, and exports a TPO-ready sheet for the recruiter — with no room for proxy attendance and no manual ID checks at the hall.
Eligibility-gated · TPO-exportable
Sports meets & cultural events
Outdoor grounds, multiple sub-venues, messy attendance. Presence sets a perimeter per ground, supports mass punch-out at day's end, and tracks participation across the whole meet for points, badges and inter-college rankings.
Multi-venue · mass punch-out
Hackathons & hands-on workshops
Overnight hackathons need continuous presence — judges must know who is still on site at 3 a.m. Presence tracks perimeter entries and exits in the background, without waking participants or interrupting work.
Continuous · background tracking
§ 03
Demo — Try the Platform
Pre-coded · Self-contained
Animweb Presence, running in a box.
Both panels. No backend. Seeded data only — everything you click is real UI wired to local state.
TechFest 2026 — Live Console
Central Lawn · 30.7333°N, 76.7794°E · Radius 80m · Day 2 of 3
Present now
163
▲ 12 in last 10 min
Absent
37
Registered · not in fence
Total registered
200
Active participants
Face-enrolled
192
96% coverage
| Participant | Roll | Department | Face | Status | Punched In |
|---|
Showing 8 of 200 · Auto-refresh every 5s
Synced · 00:00:00
TechFest 2026
24 Apr · Day 2 · Central Lawn
Inside the perimeter
Scanning face…
Recent activity
- Punched in · Central Lawn09:42
- Punched out · Break11:18
- Punched in · Central Lawn11:46
TechFest 2026
24 Apr · Day 2 · Central Lawn
Inside the perimeter
✓ Verified · conf 0.91
Recent activity
- Punched in · Central Lawn09:42
- Punched out · Break11:18
Live Console
Day 2 · Radius 80m
Present
163
Absent
37
Total
200
Faces
192
| Name | Roll | Status |
|---|---|---|
| ASAarav Sharma | 22109... | In |
| PMPriya Menon | 22110... | In |
| RKRahul Kumar | 22111... | Out |
| ISIsha Singh | 22112... | In |
| NVNikhil Verma | 22113... | Verify |
Demo · Synthetic data · No persistence
Talk to us → for a live deployment
§ 04
Horizon — The Roadmap
2026 — 2028
Phase 01 · Now
Event & geofence attendance
Shipping today. Deployed at our first partner institutions across India.
a
Geofenced check-in
GPS perimeter, admin-configurable radius, venue switching.
b
Face verification
Privacy-first 128‑dim descriptors, no images stored.
c
PWA with background tracking
Auto punch in / out across venue boundary.
d
Admin console + CSV export
Present, absent, summary, mass punch-out.
Phase 02 · Q2 2026
Classroom integration
Bridging campus events to the daily timetable — no more printed OD slips.
a
Automatic OD leave requests
Event attendance triggers leave requests across overlapping classes.
b
WiFi indoor localization
Classroom-resolution presence via trusted SSID/BSSID pairs.
c
Teacher approval inbox
A single, timestamped queue — no emails, no chasing.
d
Timetable-aware attendance
The system knows the period, not just the day.
Phase 03 · Q3–Q4 2026
Student & department profiles
A unified identity per student, owned by the university, available across every module.
a
Student profiles
Roll, department, semester, attendance history, OD ledger, co‑curricular record.
b
Marks & assessment module
Internal, external, lab & practical marks with semester rollups.
c
Department pages
Curriculum, faculty, notices, performance dashboards per department.
d
Skill & activity badges
Machine-verifiable participation records for every event attended.
Phase 04 · 2027
Institutional suite
From single-college deployment to a university-wide, multi-campus spine.
a
Multi-university tenancy
Isolated, per-institution data realms with shared platform economics.
b
Parent & guardian portals
Read-only, consented views of attendance & performance.
c
Institutional analytics
Department-level engagement, event ROI, attendance anomaly detection.
d
LMS & ERP integrations
Open APIs for Moodle, Google Classroom, ERPs already on campus.
Phase 05 · 2028+
Autonomous operations
As Animweb grows, booking a meeting becomes optional — the platform sets itself up.
a
Self-service onboarding
Institutions provision their own tenant, upload rosters, go live.
b
Automated venue & event setup
Coordinator pastes a venue link; the fence, the event, the roster are configured.
c
Anomaly & fraud signals
ML on descriptor distances, location patterns & timing flags — with human review.
d
Open white-label SDK
Build on top of Animweb: partner colleges extend, we maintain the spine.
§ 05
Pricing — Early-Stage Honesty
INR · GST Extra
Starter
₹
10,000
starting · per event
A compact engagement for one event, on our shared infrastructure. You bring the roster; we bring the system.
▸Full Presence platform access for one eventIncl.
▸Geofence + face verificationIncl.
▸Admin dashboard & CSV exportIncl.
▸PWA with background trackingIncl.
▸Email support during eventIncl.
○Custom domain & brandingAdd-on
Build & Setup
₹
12,000
one-time · setup complete
We build it, we deploy it, we sit with your team until it runs. Everything in Starter, plus the full onboarding.
▸Everything in StarterIncl.
▸Dedicated deployment on your own subdomainIncl.
▸Admin onboarding & training sessionIncl.
▸Custom venues, radius & event profilesIncl.
▸Brand colours & institution logoIncl.
▸Priority support through the eventIncl.
Scale EngagementsMulti-college, multi-event, year-round deployments are priced separately. Write to us — we'll draft a scope with you.
What's not includedGST at prevailing rates, domain registration, third-party SMS gateways, custom LMS integrations.
What stays yoursStudent data, department data, attendance records and institutional branding remain the property of your institution — always.
§ 05·B
FAQ — The questions we actually get
Plain answers
01 What exactly is Animweb Presence?
Presence is a face-verified, geofenced attendance platform for Indian colleges, universities and campus events. Students punch in inside a GPS perimeter after a one-tap face check; coordinators run everything from a live admin console with CSV exports. It ships today as v0.9 — with a public roadmap running through 2028.
02 Do you store photographs of students?
No. Presence never stores a photograph. Each enrolled face becomes a 128-dimensional mathematical descriptor — an irreversible fingerprint used only for 1:1 verification. You cannot reconstruct a face from a descriptor, and descriptors are hidden from admin listings, CSV exports and every API response except the client-side match itself.
03 Can we use Presence for regular classroom attendance?
Yes — classroom integration is the next release. GPS falls off indoors, so Presence pins classroom attendance to specific WiFi SSID and BSSID fingerprints registered by the institution. The system also checks the student's timetable; if they are at a valid campus event, an on-duty (OD) leave request is generated automatically, so the missed period is reclassified without anyone chasing a printed form.
04 Who owns the student data and the attendance records?
The institution does. Every roster, every attendance row, every CSV, every marks record — all of it is the property of the institution. Animweb Technologies operates as a Data Processor under a written engagement. On exit, we export and delete. We do not mine, resell, or “anonymise for benchmarks.”
05 Is Presence compliant with India's data protection law?
Presence is designed around the Digital Personal Data Protection Act, 2023 (DPDPA). The institution is the Data Fiduciary for student information; we are the Data Processor. Students are given notice at enrolment, face data stays as one-way descriptors, retention is defined contractually, and the institution's Grievance Officer handles rights requests. Our privacy policy spells this out, section by section.
06 What happens when an event ends or a student graduates?
Ending an event de-registers participants instead of deleting them. Their face descriptor is preserved so they re-register next semester without re-enrolling — and so you never end up with duplicate records. Inactive participants never appear in active CSV exports or listings. On graduation, the institution decides whether to retain or purge; we execute that decision, we do not set it.
07 What does it cost?
Starter — ₹10,000 per event on shared infrastructure, for one event. Build & Setup — ₹12,000 one-time for a dedicated subdomain deployment, onboarding, training and priority support. Multi-college, year-round and multi-campus engagements are priced separately — we'll scope it with you. GST is extra at prevailing rates.
08 Does Presence work without a strong internet connection?
Presence is a Progressive Web App, so the interface is cached and survives connectivity dips. Face verification and perimeter check do require connectivity at the moment of the punch — but the app queues events on flaky networks and reconciles them when the device comes back online, so students on patchy campus WiFi are not penalised.
09 Do you offer multi-college or multi-campus deployments?
Yes — multi-university tenancy is on the 2027 roadmap, and we already run bespoke multi-campus deployments as scoped engagements. Each institution gets its own isolated data realm, its own admin role hierarchy, and its own branding. Platform economics are shared so the per-campus cost scales cleanly.
10 How fast can you deploy for our next event?
Our standard Build & Setup lead time is 5–7 working days from contract. Starter (shared infrastructure) can be live in under 48 hours for a well-scoped event. Annual techfests booked a month out get dedicated rehearsal time and a pre-event dry run. Request a meeting and we'll map it to your date.
§ 06
Begin — Request a Meeting
Response within 48h
Your draft email is open. Hit Send from your mail client and a real person will reply within two working days — from animwebtechnologies@gmail.com.