SAARTHI Terms of Use
These terms explain roster-managed access, developmental-use boundaries, trusted records, user responsibilities, and support.
Data & Account Deletion
For account and data deletion requests, as governed by these terms, use one of these options:
1. About these terms
These terms explain public use of SAARTHI, roster-managed account access, developmental-use boundaries, and user responsibilities. Official institutional use is also subject to the applicable written agreement, State instructions, and active legal notices.
2. Roster-managed access
SAARTHI accounts are created through an authorized institutional roster, invitation, identity-correction, or exception process. Public email, phone, or social self-registration cannot create or attach an institutional account.
3. Developmental use
Assessment, observation, portfolio, mentoring, and growth outputs are developmental unless the applicable authority approves another use. An incomplete or unreleased result is not a proficiency decision. SAARTHI does not claim certificate or external-system eligibility without an authorized rule and integration.
4. Standards, assessments, and content
Official work uses the applicable versioned competency framework, assessment, rubric, translation, scoring rules, and report template. State competency models and national references remain distinct even when an authorized mapping connects them.
Material changes to standards, scoring, reporting, privacy, or accessibility controls follow documented authority, version history, impact review, and an effective date.
5. User responsibilities
Users must verify roster information through the correction route, protect credentials, complete privileged multi-factor authentication where required, stay within assigned scope, and avoid sharing item keys, private evidence, coaching notes, passwords, or one-time codes. Unauthorized access, scope manipulation, malicious uploads, disruption, and security-control bypass are prohibited.
6. Evidence, reports, and exports
Submitted evidence and assessment attempts retain provenance and audit history. Official reports are produced from authorized data and carry their applicable status and context. Test and provisional outputs must be visibly marked and cannot be treated as official records.
7. AI-supported features
AI-generated summaries or suggestions must be labelled, tied to source evidence, and confirmed by an authorized human. AI cannot independently assign an official proficiency, release a score, or make an employment or punitive decision.
8. Access restrictions
Access may be restricted to contain a security incident, enforce a valid role or scope boundary, comply with an applicable authority, or respond to misuse. Material service changes remain subject to the applicable agreement, continuity arrangements, and advance notice where required.
9. Privacy, retention, and security
Use of SAARTHI is subject to the active data and privacy notice, applicable retention and processor instructions, role and scope controls, security safeguards, and request or correction process.
10. Accessibility and alternatives
SAARTHI targets WCAG 2.2 Level AA for essential journeys and generated documents. Current limitations and the assisted-use route are published in the accessibility statement.
11. Support, incidents, and appeals
Users may submit account, correction, privacy, accessibility, score-appeal, or operational support requests through the available support routes. A support operator receives only the minimum information required for an assigned case.
12. Applicable documents
Signed agreements, approved State instructions, the active data notice, framework records, and authorized operating rules take precedence where they apply. This page does not alter procurement, payment, liability, intellectual-property, or jurisdiction terms set by signed instruments.
13. Updates
The active version identifies its version, effective date, and review date. Material changes are published through the applicable notice and authority process.
14. Support and requests
Do not include passwords, one-time codes, assessment answers, or private evidence in a support email.