Data Retention & Deletion Schedule

Our deletion commitment, in plain terms

We never promise unconditional, instant deletion from every backup medium — no honest vendor can. Our commitment is to hard-delete the record from the active database immediately on an authorized erasure request, subject to the hold and retention caveats above, or at its scheduled routine window. Before Attend handles real district data, we will enforce this coverage for every record class. Any database backups containing the record age out and are overwritten under our hosting provider's documented backup lifecycle rather than being editable on demand.

Routine retention windows

Before Attend handles real district data, we will enforce these windows through an automated daily purge and apply LEA-configurable retention to every Attend record class. The LEA must direct the windows for new classes before processing starts; no new numerical defaults are assigned here. The 60-day request/termination deletion obligation and the backup and legal-hold caveats below still apply.

Before Attend handles real district data, we will verify that its purge skips every record under an active legal hold and reports those records separately. Audit-trail and correction-history records are never auto-purged — they are retained per district and security policy, and are removed only through student erasure (below).

Attend record coverage

Before Attend handles real district data, we will record the LEA-directed retention window for each class below and verify its inclusion in export, student erasure, append-only audit, and student/school/district legal holds. Holds block deletion, never export. Records retain the same 60-day request/termination deletion protection; this mapping creates no longer retention allowance.

Legacy rows preserve deletion limits for any data retained from the earlier service. They do not authorize Attend to collect evidence uploads, communication inputs, or audio. All linked legacy records and stored file content remain subject to export, erasure, audit, and holds.

Student erasure (rights-based deletion)

Our erasure obligation covers every record linked to that student, including each Attend class mapped above, linked legacy records and stored file content, correction history, and the student record. Before Attend handles real district data, we will enforce complete hard deletion in a single transaction and append-only auditing using opaque identifiers and per-category counts only, never names or content.

On LEA request or contract termination, student data is exported if requested and deleted within 60 days (typically immediately), consistent with NDPA § 4.6, Texas Education Code § 32.156, and our LEA agreements. Legal holds and correction-record obligations can defer specific records, and backup deletion follows the rotation cycle. Parents and eligible students exercise rights through their LEA; we support LEA access/correction/deletion requests within 30 days. Before Attend handles real district data, we will enforce hold-based erasure refusal and audit every refusal.

One honest caveat: if the district's own roster source (its SIS connected through Ednition) still lists the student, a later roster sync may re-create the basic directory entry (name/email) from the district's own system of record. Erasure covers Agenteach-authored and derived records; it cannot remove a student from the district's own roster.

Student export

We provide, on LEA request, a complete, usable package of everything Agenteach holds about a student, including the full content of every linked record, correction history, and related audit metadata. Export is never blocked by a legal hold. Before Attend handles real district data, we will verify complete export coverage of each mapped class and record every export in the append-only audit trail using identifiers and counts only.

Legal holds

Districts can direct Agenteach to place a hold at three scopes — a single student, a whole school, or the whole district. A hold must block erasure, never export, for its scope until released. Before Attend handles real district data, we will enforce holds across every mapped record class and permanently audit each hold's creation and release, including who and when.

Roster data held by our integration partner

Through the district-approved Ednition connection (Privacy Policy §7), roster/directory data, daily attendance and absence codes, guardian contacts where shared, and course grades/credits when the district enables the counselor academic view are held in Ednition's US-hosted environment while the connection is active. Ednition never receives staff-created notes (including restricted notes), contact/home-visit logs, plans, meeting notes, draft messages/summaries, report worksheets, Agenteach audit trails, or AI requests/outputs. When a district disconnects or its agreement ends, we direct Ednition to delete all district data it processes for Agenteach. Its contractual maximum is 60 days after termination, inside our own 60-day commitment; destruction is confirmed as part of our exit process. Student erasures propagate to Ednition for all records it processes through the district-approved connection.

Backups

Production database backups are retained and expire under Microsoft Azure's documented backup lifecycle, independent of this schedule. A deleted record disappears from the live database immediately and from backups as they expire and are overwritten on rotation.