Summary

Today, SecondChair.dev is built as a static site. We do not require an account to read lessons. We do not operate our own comment or login system yet. Some features store preferences only on your device (in the browser’s storage), not on our servers—because there is no per-user database for general browsing.

Information we process

Browsing and reading lessons

When you load pages, your browser sends standard technical data to whichever host serves the site (for example, a hosting provider’s web servers and, like most sites, basic access logs on that side). We do not combine that with a profile of you on SecondChair.dev unless we later add services that require it and describe them here.

Data stored locally in your browser

To improve the experience without accounts, the site may use browser storage (typically localStorage, and in some cases sessionStorage). This can include, for example:

  • Prep track progress and “day completed” markers
  • Optional lesson feedback (reactions) tied to a lesson URL
  • Reading display preferences (for example, reading mode)
  • Drafts in the coding practice editor, if you use it

This data stays on your device unless you clear site data for SecondChair.dev or use another browser. We do not receive a copy of that storage simply because you visited the site.

Cookies and similar technologies

Cookies. We do not use third-party advertising cookies on this site as described in this policy. If we introduce analytics or other tools that set cookies, we will update this policy and, where the law requires it, ask for your consent before non-essential cookies are used.

Local storage. Features that remember progress or preferences rely on storage APIs in your browser. Under privacy laws, these can be treated similarly to cookies when they store identifiers or choices; you can remove them by clearing site data for this origin in your browser settings.

Third-party resources

Some pages may load optional third-party resources when you take an action—for example, running Python or SQL in the practice area may load runtimes or WebAssembly from a public CDN. Those providers receive technical requests needed to deliver files (similar to any website). Their privacy practices are governed by their own policies.

Site search (where available) uses an index bundled with the site; it does not send your search queries to a separate analytics service by default.

Future features: analytics, accounts, and comments

We may add features such as usage analytics (to understand traffic), authentication (sign-in), or comments (for example, via a service like Supabase). If we do, we will:

  • Update this Privacy Policy to name the service, the categories of data collected, and the purpose
  • Where required by law, provide consent or opt-out mechanisms for non-essential processing
  • Describe any new cookies or similar technologies and retention

Until those features launch and this page is updated, you should assume they are not active for SecondChair.dev unless stated on the relevant page.

Your choices and rights

Depending on where you live, privacy laws may give you rights to access, correct, delete, or restrict processing of personal data, or to object to certain processing. For information stored only in your browser, you can often exercise control by clearing site data or using private browsing modes.

If we process personal data on our systems in the future (for example, because you create an account or post a comment), we will describe how to exercise your rights and how to contact us.

Children

SecondChair.dev is aimed at adults preparing for professional interviews. It is not directed at children under 13, and we do not knowingly collect personal information from children.

Changes

We may update this policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the site after changes means you accept the updated policy, except where the law requires a different process.

Contact

For privacy-related questions about this policy, please reach out through the contact channel you use for SecondChair.dev (for example, the project repository or email published on the site when available).