Skip to main content
AttendanceData

Legal

Privacy

Last updated: September 14, 2026

Institutional agreements define FERPA responsibilities, student data handling, subprocessors, retention, and deletion requirements.

This website sets no cookies, so it shows no cookie banner.

No tracking cookies, no advertising pixels, no consent dialog to dismiss. If we use analytics, it is a cookieless, privacy-respecting service that does not identify individual visitors. Privacy-first design begins with the AttendanceData website.

1. What we never collect

No GPS coordinates and no location permission request. No Bluetooth scanning or beacon proximity. No Wi-Fi network monitoring. No biometrics. No student activity outside the check-in itself.

Check-in is an affirmative act a student takes. There is no passive monitoring of any kind.

2. Student data in the product

Production agreements define what is stored, retention periods, and authorized access.

3. FERPA and education records

Institutional agreements define how attendance records are handled under applicable education-record requirements.

4. This website

Form submissions on the demo and ROI pages are stored so we can reply to you. We record which page and campaign a submission came from.

We do not sell or rent any information, and we do not run advertising pixels.

5. Subprocessors

Production subprocessors are reviewed during institutional contracting.

6. Retention and deletion

Institutional agreements define retention, deletion, and end-of-contract data handling.

7. Security

Encryption in transit and at rest, role-based access, audit logging, and tenant isolation. We hold no SOC 2, ISO, or FERPA certification today and do not claim one.

8. Contact

Privacy inquiries can be submitted through the institutional pilot request form.