Privacy Policy
Privacy Policy
Sri Sathya Sai Future Talent is a free, educational and seva-oriented initiative. We are committed to using personal information only for clearly defined educational, authentication and programme-related purposes, while maintaining reasonable privacy and security safeguards.
1 Scope and Purpose
This Privacy Policy explains how Sri Sathya Sai Future Talent may process information when a user signs in, attempts a mock test, views results, uses the leaderboard, accesses attempted-test history or otherwise uses personalised features of the platform.
Personal information is intended to be processed only for lawful, specified and programme-related educational purposes.
2 Information We Use
Depending on the feature used, the platform may process the following information:
- Student name;
- Google Account email address;
- State / Union Territory;
- Test name and Test ID;
- Date and time of test attempt;
- Answers submitted by the student;
- Correct, wrong, attempted and unattempted question counts;
- Marks, percentage and rank;
- Preferred test language;
- Time taken for a test and question-wise timing information;
- Pause/resume information necessary for test continuity; and
- Other limited technical information necessary to operate the test platform.
3 No Mobile Number, OTP or Password Collection
Google Sign-In is used for authentication. Any security verification that Google independently requires for the user's Google Account is handled directly by Google and is separate from Sri Sathya Sai Future Talent.
We do not operate our own mobile-number-based or OTP-based login system.
TRAI Reference: Telecom Commercial Communications Customer Preference Regulations (TCCCPR), 2018 concern commercial telecom communications and protection against Unsolicited Commercial Communications (UCC). The present website does not use a mobile-number/OTP login system or operate promotional SMS/voice communication as part of its login process.
4 Google Sign-In and Authentication
Users may sign in using Google authentication. The platform may receive limited account information required to identify the authenticated user, such as name, email address and the unique authenticated account identity.
Authentication credentials and Google Account security remain under Google's authentication system and the user's own Google Account security settings.
5 Why We Use This Information
Information may be used for the following specified purposes:
- Authenticating and identifying a logged-in student;
- Maintaining individual test history;
- Recording and displaying test results;
- Providing attempted-test history and answer review;
- Calculating marks, percentage and rank;
- Displaying appropriate leaderboard information;
- Providing educational performance analysis;
- Supporting pause/resume and test continuity;
- Troubleshooting errors and maintaining platform functionality;
- Preventing misuse or unauthorised manipulation; and
- Maintaining reasonable security and programme administration.
6 Platforms and Services Used
The programme currently uses or may use the following services to operate the educational platform:
- Google Blogger / Blogspot for the website;
- Google Sign-In / Firebase Authentication for account authentication;
- Firebase Firestore for limited authenticated profile information, where applicable;
- Google Apps Script for backend processing;
- Google Sheets for test/result records;
- Google Drive for authorised programme files, resources and backups; and
- Google Cloud / Firebase project services required for authorised technical operation.
These services may process information only to the extent technically required to provide, maintain or secure the relevant platform functionality.
7 Firestore and Account Security
The current Firestore user-profile structure is designed so that an authenticated user may access only the user document associated with that user's own Firebase UID.
Firestore access controls are separate from Google Sheets and Apps Script permissions; those backend systems are protected through their own access and deployment controls.
8 Google Sheets, Apps Script and Drive
Mock-test and performance records may be stored in restricted Google Sheets and processed through Google Apps Script. Google Drive may be used for authorised educational material, technical files, programme documents and backups.
Backend Sheets and internal Drive resources are not intended to be publicly editable. Administrative access should be limited to persons authorised for programme or IT responsibilities.
9 Browser Storage and Cookies
The website may use browser local storage, cookies or similar browser functionality where necessary for login/session behaviour, test caching, pause/resume, temporary test progress, profile continuity and other technical functionality.
The programme does not intentionally use such browser storage to build advertising profiles of students.
Google, Blogger, Firebase and other service providers may use their own technical cookies or storage in accordance with their applicable service and security practices.
10 Leaderboard Privacy
A leaderboard may be used for educational motivation and performance comparison. Student-facing leaderboard information may include:
Email addresses, passwords, authentication credentials and other private account information are not intended to be displayed publicly on the leaderboard.
11 No Sale, Rental or Targeted Commercial Profiling
Sri Sathya Sai Future Talent is a free educational seva initiative. Personal information is not intended to be sold, rented or commercially traded to advertisers or data brokers.
The platform does not intend to use student personal information for targeted commercial advertising or unrelated commercial profiling.
12 Data Security
Reasonable technical and organisational safeguards should include, as applicable:
- Organisation-controlled administrative accounts;
- Two-Step Verification for administrative accounts where available;
- Restricted Google Sheets, Drive and Apps Script permissions;
- Restricted Firebase / Google Cloud administrative permissions;
- UID-based authenticated Firestore access;
- Protection of passwords, recovery codes and administrator credentials;
- Periodic review and removal of unnecessary access;
- Backups of important data and technical configuration; and
- Appropriate action in response to suspected security incidents.
Cyber-Security Reference: CERT-In Directions dated 28 April 2022 issued under Section 70B(6) of the Information Technology Act, 2000, relating to information-security practices and prevention, response and reporting of cyber incidents, where applicable.
13 Personal Data Breach / Security Incident
If unauthorised access, accidental disclosure, loss, compromise or another significant security incident affecting personal information is identified, appropriate technical and organisational steps may be taken to contain the incident, secure affected systems, review access and take other action required under applicable law.
14 Data Retention
Personal information should be retained only for as long as reasonably necessary for the educational programme, test history, performance analysis, legitimate programme administration, security, continuity, or compliance with applicable legal requirements.
Information that is no longer reasonably required may be deleted or anonymised in accordance with applicable requirements and programme policy.
15 Correction, Updating and Deletion Requests
A user may contact the programme regarding correction, updating or deletion of personal information associated with the platform, subject to applicable legal, security and legitimate retention requirements.
Reasonable verification may be requested before modifying or deleting account information to help prevent another person's data from being changed without authority.
16 Children / Users Below 18 Years
The programme is educational in nature. Where personal data of a person who falls within the definition of a child under applicable Indian data-protection law is processed, applicable requirements relating to children, parents or lawful guardians should be followed.
The platform does not intend to undertake targeted commercial advertising directed at children or commercial behavioural profiling of children.
17 TRAI / SMS / Voice Communication
The present Future Talent login and mock-test system does not require a mobile number or operate a mobile OTP system.
If bulk commercial/promotional SMS, automated voice calls or other regulated telecom communications are introduced in future, applicable TRAI requirements should be reviewed before implementation.
18 Consent and User Choice
Where processing is based on consent, the consent request should be presented clearly and should require an affirmative action by the user. A consent checkbox, where used, should not be pre-selected.
19 Privacy / Grievance Contact
Questions concerning privacy, correction, deletion, security or use of personal information may be raised through the official Organisation contact below.
Pragati Vihar, Bhisham Pitamah Marg
New Delhi - 110003
20 Changes to This Privacy Policy
This Privacy Policy may be updated where website functionality, technology, programme practices, applicable law or regulatory requirements change. The latest version may be published on this website with a revised effective date.
21 Government / Regulatory Frameworks Considered
This policy has been prepared with reference to the Indian legal and regulatory frameworks relevant to the platform's present functionality, including:
- Digital Personal Data Protection Act, 2023 — Government of India;
- Digital Personal Data Protection Rules, 2025 — MeitY, Government of India;
- Information Technology Act, 2000 — including Section 70B relating to CERT-In;
- CERT-In Directions dated 28 April 2022, where applicable; and
- TRAI Telecom Commercial Communications Customer Preference Regulations, 2018, where applicable.
Comments
Post a Comment