How SurePass handles information used to provide learning, account and communication features.
This policy describes the main categories of information SurePass may process, why that information is used, how it can be stored or shared, and the choices available to users.
Summary
SurePass uses information needed to operate learner accounts and study features, keep the service secure, answer messages, understand platform use and improve learning experiences. Users should never submit passwords, one-time codes, payment-card details or other highly sensitive credentials through public forms or comments.
1. Information provided by users
When an account or learner profile is created, SurePass may receive information such as a name or display name, email address, learner class, selected subjects and other profile choices needed to personalise the learning experience. The exact fields depend on the feature being used.
Information can also be provided when a user sends a support message, submits a correction, leaves a comment where comments are enabled, or otherwise communicates with SurePass. Those submissions can include contact details and the content of the message.
2. Learning and app activity
Signed-in learning features may record activity such as saved lessons, lesson progress, quiz or Flashcard attempts, scores, completion state, rewards, selected subjects and other information required to continue learning across sessions or supported devices.
Where offline-capable app features are available, some learning data may be stored locally on the device and synchronised when a connection becomes available. Notification features may use a device or push-notification token when the user enables notifications.
3. Technical, security and usage information
SurePass can process limited technical and first-party usage information such as page views, sessions, referrers, device or browser characteristics, browser timezone and coarse location information when an infrastructure provider supplies it. Server and security systems may temporarily process network information, request headers and diagnostic logs to deliver pages, prevent abuse, investigate errors and protect accounts.
Hosting, caching, content-delivery, anti-spam, firewall, bot-protection or CAPTCHA providers may process additional technical information as part of providing their services.
4. Cookies, local storage and similar technologies
Cookies or local storage may be used to keep users signed in, remember interface preferences, preserve study state, support WordPress or SurePass functionality, measure first-party usage and protect the service from abuse. Some optional browser or device features may also store local information to support offline use or faster loading.
Browser and device settings can be used to control cookies, local site data and notification permissions. Blocking essential storage may prevent sign-in, saved progress, preferences or other requested features from working correctly.
5. How information is used
Information may be used to provide and personalise requested features; authenticate accounts; save and synchronise learning progress; answer enquiries; deliver enabled notifications; detect abuse; diagnose technical problems; maintain service reliability; understand which content and tools are useful; and meet reasonable legal, security or record-keeping obligations.
Normal learning features do not require a learner’s study record to be publicly visible to unrelated visitors. Public comments or other intentionally public submissions are different and may be visible according to the feature’s design.
6. Service providers and external services
SurePass may rely on service providers for hosting, security, caching, email delivery, notifications, analytics, app distribution and other operational functions. Those providers may process information necessary to perform the service they provide and are governed by their own terms and privacy practices.
SurePass may also link to examination bodies, schools, universities, government websites, app stores and other external services. Their collection and use of information are governed by their own privacy policies, not this one.
7. Retention and security
Retention depends on the type of information and why it exists. Account and study records may be retained while an account is active or while needed to provide the learning service. Support correspondence, security logs and analytics can have different retention periods. Operational data may be removed according to configured retention practices.
No internet service can promise absolute security. SurePass uses reasonable access controls, software updates, backup practices and security systems appropriate to the platform, while users remain responsible for protecting their own account credentials and devices.
8. Children and young learners
SurePass is designed for education use and some learning experiences are relevant to children. Parents, guardians and schools are encouraged to guide younger learners when creating accounts or providing personal information online. Public forms and comments should not be used to send passwords, one-time codes, financial credentials, government identification numbers or similar sensitive information.
Where a parent, guardian or authorised school representative requests an account-level change concerning a learner, SurePass may request enough information to verify the person’s authority before acting.
9. Access, correction and deletion requests
Users can contact SurePass about personal information they directly submitted and may request reasonable access, correction or deletion where applicable. A request may be subject to identity verification, technical limitations and information that must be retained for legitimate security, fraud-prevention, record-keeping or legal reasons.
10. Changes to this policy and contact
This policy may be updated when SurePass features, service providers, security practices or applicable requirements change. The version published on this page is the current website policy.
Privacy questions or requests can be sent through the SurePass contact page. Do not include passwords or one-time security codes in a privacy request.