Effective Date: 17 March 2026 | Last Updated: February 2026 | Operated by: Scikraft
This policy covers TiQer Web App and TiQer Mobile Apps (Android & iOS).
TiQer (the "Service") is a classroom engagement and assessment platform designed for educators, trainers, and educational institutions. It enables creation of quizzes/polls, classroom sessions, attendance workflows, and real-time response analytics using TiQer cards (ArUco markers).
This Privacy Policy explains how Scikraft ("Scikraft", "we", "us", "our") collects, uses, shares, stores, and protects information when you access or use the Service, including any websites, mobile applications, and support channels that link to this policy.
This policy applies to: (a) teachers/trainers/facilitators; (b) school or organizational administrators; (c) students/participants whose data is entered by educators; and (d) anyone accessing TiQer web or mobile applications.
Where the Service is deployed by a School/Institution, the School/Institution is typically the "Data Controller" and Scikraft acts as a "Data Processor" for student/participant data. A separate School Data Processing Addendum (DPA) may apply.
"Personal Data" means information that identifies or relates to an identifiable individual.
"Participant Data" means minimal student/participant identifiers used for classroom participation (for example, name and roll ID).
"Processing" means collection, storage, use, transfer, disclosure, deletion, or other handling of data.
"Sensitive Personal Data" includes categories that may require higher safeguards under applicable law. TiQer is designed to avoid collecting such categories.
4.1 Account and Registration Data (Educators/Administrators)
Full name
Email address
Role type (teacher/trainer/facilitator/admin)
Organization name and type (if registering as an organization)
4.2 Classroom and Participant Data (Entered by Educators)
First name
Last name
Roll number / participant identifier
Class/group or activity room association
We do not require student phone numbers, email addresses, precise addresses, or government IDs.
4.3 Session, Quiz, and Usage Data
Quiz/poll questions created and session configuration
Attendance status and participation logs
Response selections, correctness results, and aggregated statistics
Teacher dashboards and session analytics
4.4 Camera, Image Capture, and Geo-tagging Data (Mobile App)
The TiQer mobile app uses device camera functionality for:
Scanning TiQer cards (ArUco markers) for attendance and response capture
Optional capture of trainer/classroom images for attendance verification and audit purposes
For this enhanced feature:
Images of the trainer and classroom may be captured at the time of session or attendance
Such images may be associated with session records for verification, reporting, and compliance purposes
We do not use these images for facial recognition or biometric identification
Additionally:
Approximate or precise location (geo-tagging) may be collected at the time of image capture to validate session authenticity and attendance context
Location data is used strictly for operational and audit purposes and is not used for tracking users outside the app
We ensure that:
Image and location data are accessed only by authorized personnel (e.g., institution admins, trainers)
Data is securely stored and protected using industry-standard safeguards
Data is retained only as long as required for academic, audit, or compliance purposes
4.5 Device, Diagnostic, and Log Data
Device type, OS version, app version
Crash reports, performance diagnostics, and error logs
Basic network/connectivity indicators
4.6 Cookies and Similar Technologies (Web App)
We use essential cookies/session tokens for authentication, session management, and basic performance. We do not use advertising cookies for behavioral advertising.
TiQer may request the following permissions:
Camera: Required for scanning TiQer cards and capturing optional attendance verification images.
Location (GPS): Required to geo-tag attendance sessions for validation and audit purposes.
Network/Internet: Required to sync sessions, attendance, and analytics.
TiQer does not access contacts, microphone, or unrelated personal data.
We process information to:
Provide and operate the Service (accounts, sessions, quizzes, attendance, analytics)
Improve reliability, usability, and performance (diagnostics, bug fixes)
Maintain safety and security (fraud prevention, abuse detection, access control)
Provide customer support and respond to requests
Comply with legal obligations and enforce our Terms/Content Policy
We process personal data for lawful purposes, with appropriate notice, security safeguards, and rights mechanisms.
Where an Individual or School/Institution controls student data, the School determines the lawful basis/consent requirements for student participation.
7.1 Consent for Image and Location Data
By registering and using TiQer, and by explicitly accepting this Privacy Policy, users (teachers/trainers/administrators) consent to:
Capture of images for attendance and session verification
Collection of geo-location data at the time of such capture
Where required, the institution or organization deploying TiQer is responsible for obtaining any necessary consent from participants or guardians.
We do not sell personal data. We share data only as needed to operate the Service:
8.1 With Authorized Users
Teachers/trainers can view participant attendance and responses for their own sessions/classes.
Organization administrators may access reports for authorized users under their organization.
8.2 With Service Providers (Processors/Sub-processors)
We may use vetted vendors for hosting, monitoring, analytics, and support. They are contractually required to protect data and process it only for service delivery.
8.3 For Legal, Safety, and Enforcement
We may disclose information if required by law, to protect rights/safety, to investigate security incidents, or to enforce our Terms.
We apply reasonable technical and organizational measures to protect data, including:
Encryption in transit (HTTPS/TLS)
Role-based access controls and least-privilege principles
Secure authentication and session management
Monitoring/logging for security events
Backups and resilience controls (as applicable)
We retain information only as long as necessary for the purposes described in this policy:
Active educator accounts: retained while the account remains active
Session and reporting data: retained to support academic reporting and institutional review
Inactive accounts: may be deactivated and scheduled for deletion after a reasonable period of inactivity (e.g., 3 years).
Legal/abuse records: may be retained where necessary to comply with law or prevent misuse
Schools may request export or deletion of school-controlled data subject to verification and contractual terms.
Images and geo-tagged attendance data are retained only for operational, reporting, and audit purposes and are deleted or anonymized after a defined retention period or upon valid deletion request.
TiQer is intended for supervised educational use. Student/participant data is entered by educators or authorized school staff.
We collect minimal participant identifiers (e.g., name and roll ID) to enable classroom participation.
We do not knowingly collect direct student contact details unless explicitly provided by a School as part of an approved deployment.
The School/Institution is responsible for obtaining parental/guardian consent where required by law.
Parents/guardians may request access/correction/deletion through the School or by contacting Scikraft at info@scikraft.com (verification may be required).
To submit a request, please contact: info@scikraft.com
Requests may include:
Access to stored data
Correction of inaccurate data
Deletion of personal data
Export of data (where feasible)
We will acknowledge and respond to such requests within a reasonable timeframe (typically within 7–15 working days), subject to verification.
For student data, requests may be routed through the respective School/Institution.
The Service may contain links to third-party websites or services. This policy does not apply to third-party practices. Please review their policies before use.
We maintain an incident response process to investigate, contain, remediate, and document security incidents. Where required, we will notify affected institutions and/or users in accordance with applicable law and contractual commitments.
We may update this Privacy Policy from time to time. If changes are material, we will provide reasonable notice through the Service or other appropriate channels. Continued use after the effective date indicates acceptance.
For privacy requests, grievances, or inquiries, contact: info@scikraft.com
If you are an institution, please include your school name and deployment details for faster processing.