Personal data is handled according to applicable institutional privacy requirements, data-minimization principles and applicable provisions of the Digital Personal Data Protection Act, 2023.
This Privacy Policy describes how the YT-QSEP™ CPD Portal handles information in the current local-first version. It is an institutional notice, not a certification mark, and it does not claim DPDP, ISO, HSSC, AYUSH or government certification.
Who provides this portal
Ayushya Mandiram (आयुष्य मन्दिरम्) is the institutional publisher of YT-QSEP™ — Yoga Teaching Quality & Safety Enhancement Programme. Centre For Yoga, Quality, Safety & Professional Standards.
This portal is an educational professional CPD/CEP tool. It is not a medical clinic, diagnostic service or treatment system.
Local-first architecture
YT-QSEP™ CPD Portal uses a local-first architecture. Programme records are primarily stored on the user's device/browser. The portal does not require an account or password.
Programme records are written to storage that belongs to this device or browser session (IndexedDB where available, with an in-session memory fallback if IndexedDB cannot be opened). A limited number of non-record preferences may also use the browser’s local or session storage.
The current version does not operate a required cloud account, does not synchronise candidate records to an application-owned remote database, and does not provide automatic cloud backup.
No account or password
The portal does not require a user account, username or password for local use. Local institutional candidate record verification matches Enrollment / Candidate ID and a verification code against a Candidate Master Register stored on this device. That process is not secure authentication, identity-proofing, government verification, HSSC authentication or AYUSH authentication.
Candidate information stored locally
When a Candidate Master Register is configured on this device, the portal may store institutional candidate fields such as name, Candidate ID, enrollment number, optional roll number, optional date of birth, batch code, programme name, centre, status and a verification code used only for local record matching.
After local verification, learning, assessment and portfolio records for that Candidate ID are stored under a candidate-scoped key so that one candidate’s local records are not mixed with another candidate’s local records on the same device.
Candidate ID, enrollment and roll information
Candidate ID, enrollment number and optional roll number are institutional identifiers. They are used on this device to locate the correct local record and to label exported JSON. They are not published into static assets, service-worker source or public cache manifests.
Programme progress
Unit completion, learning progress and related programme-progress markers for a verified Candidate ID are stored locally so that the dashboard and learning pages can resume on this device.
Assessment records
Practice, mock, theory, practical, case-audit, journal, capstone and related assessment artefacts for a verified Candidate ID are stored locally. Assessment and readiness records are institutional educational records. They are not a medical diagnosis, medical report, licence or official HSSC / NSQF credential.
Institutional Simulation Only — Not an official HSSC question paper.
केवल संस्थागत सिमुलेशन हेतु — यह HSSC का आधिकारिक प्रश्न-पत्र नहीं है।
Portfolio records
Portfolio and dossier forms completed for a verified Candidate ID are stored locally. Printed dossiers are internal institutional records. They are not official certificates, government credentials, medical reports or licences.
Local browser and device storage
Primary programme storage is IndexedDB in supporting browsers, using a versioned local database named for this portal. If IndexedDB is unavailable, records may remain only in session memory and can be lost when the tab is closed.
The service worker caches the application shell and static assets for offline use. Local candidate records live in IndexedDB, not in the service-worker cache manifest.
JSON export and import
You may export a JSON copy of records from this device. Candidate-scoped export (Data Management) includes records bound to the currently verified Candidate ID. A separate full-device backup is available from Data & device settings for controlled institutional use of everything stored on this device.
Import requires a valid schema and version. The portal does not silently overwrite existing records: you must choose merge or replace after the file has been validated. Malformed or incompatible files are rejected.
An exported JSON file never leaves this device unless you choose to save, copy or share it yourself. You are responsible for how you store exported files.
Local data deletion
You may clear candidate-scoped records or all local portal data from Data Management after explicit confirmation. Deletion on this device cannot remove a copy that you previously exported, printed or shared, because those copies are outside this application.
There is no remote deletion request in this version, because this version does not keep an application-owned server copy of candidate programme records.
Google Meet and Google Classroom
Optional Google Meet and Google Classroom links may be stored in Local Institutional Configuration so that a Live Classroom page can open those destinations. This portal does not call Google Meet or Google Classroom APIs, does not verify Google attendance, and does not transmit candidate records to Google.
If you open a configured Meet or Classroom link, that destination is an external service governed by its own provider terms and privacy policy.
External websites and services
This version loads web fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com) to display the institutional typefaces. As with any third-party font request, the font host may observe ordinary network request data such as IP address. Those font requests are not an analytics, advertising or tracking SDK added by this programme.
When the portal is hosted on a preview or app-builder platform, that host may inject its own branding or runtime script. That platform behaviour is not an advertising or analytics product of YT-QSEP™. This programme does not add advertising SDKs, analytics SDKs or tracking pixels.
Opening any external link is optional. This portal does not require those services in order to store local learning records.
Whether data is transmitted to a server
In this version, candidate programme records (progress, assessment, portfolio, register and related IndexedDB stores) are not uploaded to an application-owned cloud database by the portal itself.
Ordinary web hosting still delivers the application files (HTML, scripts, styles, icons and the service worker) over HTTPS. That file delivery is not a candidate-record backup.
This policy does not claim that “no data is ever collected” by every network path a browser may use (for example font hosts or a hosting platform). It describes the portal’s own local-first record handling as implemented.
Automatic cloud backup
There is no automatic cloud backup in this version. Local data may be lost if browser or application storage is cleared, the device is reset, or the application is removed. Export your data regularly. Recovery is not guaranteed.
Retention and deletion principles
Records remain on this device until they are cleared, overwritten by an import you confirm, or removed by the browser, operating system or uninstallation.
Data minimization: this version stores what the programme needs for local learning, assessment, portfolio and institutional candidate matching. It does not require a national identity number in full. Where a last-four identity field is used, it is masked in display.
Institutional privacy contact
Privacy and data queries should be directed to the institutional contact configured under Local Institutional Configuration and shown on the Support page.
If no contact value has been configured on this device, the Support page displays “Contact information not configured.” This portal does not invent an email address, telephone number or postal address.
Applicable privacy requirements
Personal data is handled according to applicable institutional privacy requirements, data-minimization principles and applicable provisions of the Digital Personal Data Protection Act, 2023.
In particular, this local-first version is designed around purpose limitation and storage minimization for educational programme records kept on the user’s device. It does not claim certification, audit attestation or a government mark under the Digital Personal Data Protection Act, 2023.
Installation is not access
Installing this application installs the application shell and permitted public content only. Installation does not grant access to candidate records, institutional records, confidential documents, fee information, assessment information, screening information or attendance records. Installation ≠ Access.
Public App ≠ Candidate Workspace. Public pages do not display candidate-specific personal, financial, screening, attendance or assessment records.
Candidate verification is not a login
Candidate Verification is not a login, sign-up, username/password account, or user-registration system.
Candidate Verification for controlled access to the candidate's institutional workspace.
Candidate Verification provides controlled access to the candidate's institutional workspace. It does not constitute Government, HSSC, Aadhaar, or other third-party identity authentication.
Local-first security limitation
Without conventional authentication, Candidate Verification provides controlled application-level access but should not be treated as a substitute for a full identity-management or server-side authentication system.
Local-first storage on this device is not tamper-proof, not cloud authentication, and not a substitute for institutional identity management.
The institutional access code is a device administrative lock for the Institutional Workspace. It is not a user-account password, OAuth login, or government identity credential.