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. We record a distinct member account to report the registered-member total. Public profiles can show your chosen name, photo, role, company, experience, location, bio, skills, and published questions and answers. You can hide your profile in Profile settings; this does not erase attribution on previously published contributions. Profile photos are resized and metadata is removed. Following a member stores your follow choice and contributes to public follower and following totals. Do not share confidential or sensitive personal information.
Persistent sessions and articles
Sign-in persists across browser restarts, with a 30-day renewable session by default. Encrypted session tickets and an account session version are stored on the server so sign-out and sign-out-all-devices can revoke access. Browser data removal, session expiry and security changes may require sign-in again. Expired session records do not grant access; server records are retained until administrative cleanup. Blog drafts and feedback are private to the author and authorized reviewers. Approved articles, author names and publication dates are public. Approved revision snapshots and moderation history are retained. Draft autosave writes to the server; downloaded JSON backups are files you control on your device.
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.
Private Interview Challenges
Interview Challenge plans, submitted answer notes, self-assessments and revision dates are stored under your authenticated account. They are not public profile contributions and are not indexed. The two most recent attempts per question, the last 100 session summaries and up to 366 distinct practice dates are retained in your current challenge. Use Clear challenge to remove the active stored plan and notes; hosting backups may retain prior data under provider retention policies. Downloaded private backups and completion PDFs remain files you control. No recording or AI evaluation is used.
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. The historical session total is preserved. Eligible public pages also record page views, including reloads and repeat navigation, and distinct tab sessions per canonical page. Page totals begin with the page-tracking rollout; earlier page views cannot be reconstructed. Query strings and fragments are not stored. Random event receipts and hashed per-page session receipts prevent duplicates and remain stored until administrative cleanup; closing a tab does not remove them. Analytics records contain no IP addresses or account identities. Private account pages, errors, preview traffic and recognized automation are excluded. JavaScript-disabled visits and blocked or failed tracking requests are not counted. 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.