Information we process
Account identifiers, role claims, contact details, tenant configuration, enrollment records, assignment submissions, grading decisions, clinical-hour logs, CMS 22 skills sign-offs, guardian consent records, document metadata, uploaded eligibility documents, support messages, and security or audit events.
How the information is used
The platform uses records to operate tenant training programs, enforce role access, show student progress, support guardian consent, retain inspection evidence, export completion packets, investigate security events, and provide platform support to the tenant — operational assistance, troubleshooting, and compliance and security response by Ascendant Road Holdings LLC as the platform operator.
Data minimization
AscendantCare collects only the data needed to operate a tenant's training program and meet its regulatory obligations. We do not sell personal information, do not use student data for advertising, and do not build commercial profiles. Communications honor each person's consent profile and age category, and records are retained only as long as the tenant's retention policy and applicable law require, then deleted or de-identified.
Who can access records
Access is limited by tenant and role. Tenant owners and administrators can operate their tenant. Instructors access assigned instructional workflows. Students access their own records. Guardians access linked minor status and allowed consent or document actions. ARH superadmins access tenant data only for platform support, QA, security, and compliance operations.
AI assistance and automated processing
Some features use a third-party AI processor to assist instructors — for example, drafting feedback on a quiz attempt or proposing a rubric-based score on a written response. AI output is assistive only: a human instructor reviews and remains responsible for the final grade or decision, and AI is never used to make a final eligibility, disciplinary, or completion decision on its own. Only the minimum content needed for the feature is sent to the processor, and tenant and student data are not used to train its models.
Regulatory compliance
AscendantCare is built to support tenant compliance with student-privacy and health-information law, including the Family Educational Rights and Privacy Act (FERPA), the Children's Online Privacy Protection Act (COPPA), and the Health Insurance Portability and Accountability Act (HIPAA). Consent workflows capture FERPA education-record and COPPA verifiable-parental-consent requirements for minors, and the PHI boundary keeps patient-identifiable clinical data out of the platform to limit HIPAA exposure.
Data retention and exports
Tenant audit settings define hot, warm, and cold retention periods. Completion packets, audit verification manifests, clinical-hour exports, document-gate reports, and skills reports can be generated for tenant compliance review. Deletion or correction requests are handled through the tenant administrator unless law requires a direct ARH response.
Security controls
AscendantCare uses Firebase Authentication, role claims, tenant-scoped Firestore rules, server-side privileged APIs, hash-chained audit logs, and least-privilege operational practices. Live student data should not be entered until the v1 launch checklist, backup proof, legal review, and incident runbook are complete.
Contact
For privacy, access, or deletion requests, contact the tenant program administrator first. ARH platform privacy support can be reached at privacy@ascendantroadholdings.com.