Last updated: 1 May 2026
Security and trust
ClearUPSC Oracle is built as a serious learning product, not a casual content site. The security posture focuses on account-based access, protected backend credentials, source visibility, AI-quality discipline, and separation between student-facing experiences and operational tooling.
Account protection
Student accounts use OTP-based authentication where enabled. Saved briefs, recall attempts, answer feedback, and progress signals are associated with the authenticated account so learning history is not treated as a shared browser-only state.
Infrastructure safeguards
The public site and app are served over HTTPS. Backend services use environment variables for sensitive credentials, server-side API boundaries for privileged operations, and managed infrastructure for hosting, authentication, database, and deployment workflows.
Data access discipline
Student-facing pages are separated from admin and quality-console surfaces. Administrative tools should remain restricted to authorized operators, and production secrets should not be embedded in client-side code or public repositories.
AI safety and reliability
AI features are designed with source trails, factual-safety language, quality audits, and explicit limitations. Important educational outputs should be verified against primary sources, especially for laws, policies, schemes, dates, and official notifications.
Operational monitoring
The product may use logs, diagnostics, job states, and quality signals to detect failed generations, ranking drift, slow APIs, missing explanations, and other reliability issues that could affect student experience.
Responsible disclosure
If you discover a security issue, avoid public exploitation or data access. Report the issue through the support or operator channel available in the product so it can be investigated and fixed responsibly.
Security limitations
No online service can guarantee absolute security. ClearUPSC Oracle aims to reduce risk through careful architecture, least-privilege habits, managed infrastructure, and rapid correction of known issues.