Privacy and data use
Sign-in and public contributions
Google sign-in supplies a profile identifier and display name. The application derives an internal account identifier and uses a secure sign-in cookie. Google access tokens are not saved by the application. Questions, answers, comments, display names and optional profile details you publish can be visible to other visitors. Do not share confidential or sensitive personal information.
Browser storage
Saved question identifiers and practice confidence are stored in local storage on your browser. They are not a private account-synced backup. Clearing browser storage removes that local progress. Shared browsers can expose saved preparation to other people using the same browser.
Measured visits
The footer measures browser-tab sessions starting when the counter launched. A random identifier in session storage prevents repeat counting on reload. The server stores that random identifier as a deduplication receipt and updates an aggregate count. Visit receipts do not include IP addresses, account identities or browsing history. They remain stored to prevent repeat counting; closing the tab does not remove the receipt. Totals are not an exact count of unique people. If session storage is unavailable, the application reads the counter without registering that session.
Hosting and operational data
Microsoft Azure and Cloudflare deliver the application and process connection information needed to serve and protect requests. The application uses operational logging and moderation records for reliability, security and content management. This notice does not promise a fixed deletion period for hosting-provider logs or backups.
Privacy questions and requests
Contact Raviindra Wadile through the Contact page with the relevant public page URL and your concern. Do not send passwords or sign-in tokens. Requests about public contributions or account data require review; clearing browser storage alone does not delete published contributions or server records.