ActivityLockCookie Policy
This Policy explains how ActivityLock uses cookies, local storage, session storage, indexed browser storage, and similar technologies to keep the platform reliable and secure.
1. Technologies used
ActivityLock may use browser cookies, Firebase authentication persistence, local storage, session storage, IndexedDB, cache storage, and similar technologies. These may store login state, exam session state, device checks, settings, language preference, legal acceptance state, activity progress, security tokens, or temporary files needed by the app.
2. Essential storage
Some storage is essential for authentication, exam continuity, anti-abuse protection, monitoring sessions, student attempt recovery, and security. Disabling browser storage may prevent ActivityLock from working correctly and may cause loss of progress or failed submission.
3. Analytics and performance
ActivityLock may use limited analytics, logs, and performance data to understand errors, usage, loading issues, device compatibility, and reliability. We aim to avoid unnecessary tracking and use data to operate and improve the educational service.
4. Third-party services
Firebase, Google, Microsoft, Stripe, AI providers, email providers, or other integrations may set or rely on their own cookies or storage when used for sign-in, cloud storage, checkout, analytics, or embedded services. Their use is governed by their respective policies.
5. Controls
Users can control cookies and storage through browser settings, but blocking them may break sign-in, monitoring, exams, file uploads, payment checkout, or student submissions. Schools and institutions should test managed browsers before high-stakes activities.