Security & Trust
Student data can stay on your server.
A self-hosted application with no cloud dependency, designed for FERPA-aligned deployment and institutional control.
Security and privacy controls
Concrete controls, clearly stated.
Authentication
Passwords use bcrypt. Session tokens are stored only as SHA-256 hashes and invalidated after password changes.
Authorization
Admin and Teacher/TA roles are enforced with row-level data scoping, not only hidden interface controls.
Application security
Parameterized queries, output escaping, CSP, HSTS, frame denial, server-side QR validation, and rate limits protect core paths.
Data control
AttendanceData does not track any location data for any user. Device collection can be disabled institution-wide, and retention rules can erase device details while preserving the attendance fact.
Audit and exports
Administrative changes are attributable. CSV exports are sanitized against spreadsheet formula injection.
Operations
Structured logs, a health endpoint, daily automatic backups, and configurable retention support institutional operations.
Location privacy
Attendance, not whereabouts.
AttendanceData does not collect or track any user's location. Check-in records attendance without GPS coordinates or a location permission request.
No external fonts, advertising trackers, or website analytics are required by the deployed product.
Assurance status
Honest about what is not claimed.
Independent testing
Third-party penetration testing is not yet complete.
Accessibility
A formal VPAT and third-party audit are not yet available.
Integrations
SSO and automatic LMS or SIS synchronization are not currently implemented.
Certifications
FERPA certification, SOC 2, and ISO certification are not claimed.
Data responsibility
Clear roles for education records.
Production agreements define access, deletion, hosting, support, and institutional requirements for attendance records.
Bring your technical requirements.
Review controls, deployment, assurance, and the production path with our team.