Privacy

Account information

When you create an account, InterviewLayer stores your email address, display name, and an InterviewLayer account identifier. You can change your display name using the username setting, including choosing a randomly generated name. Changing your username does not change the email or sign-in methods associated with your account. For each sign-in method you connect, we also store the provider and its identity identifiers so we can recognize that method when you return.

We use these records to create your account, sign you in, show your account details, and connect sign-in methods to the same account. Connecting another method requires you to be signed in to the existing account.

We also store the times of your three most recent username changes to enforce a limit of three saved changes in any 90-day period.

You can optionally save your LinkedIn profile URL in your account. We use it to prefill the coaching application when you are signed in. You can change or remove it in your account. Saving it does not submit an application or grant permission to contact you; you choose contact consent when you apply.

Provider permissions

Google and OpenAI handle authentication for the sign-in method you choose. InterviewLayer requests basic identity information for sign-in. This flow does not request access to your Google Drive files, Gmail messages, or ChatGPT conversations.

You enter provider credentials with Google or OpenAI. InterviewLayer does not ask for your provider password, and Google access tokens are not persisted in the account database.

Cookies and temporary sign-in records

InterviewLayer uses browser cookies to keep you signed in and to connect a sign-in request to the browser that started it. The database stores hashes of application session tokens. An application session can last up to 30 days; signing out ends the current application session.

Temporary sign-in transactions expire after 10 minutes. Expiration prevents their use; expired session and transaction records are cleaned up during later sign-in activity.

Hosting and authentication services

InterviewLayer’s backend is hosted through OpenAI Sites and uses Cloudflare D1 to store account records. Authentication and hosting services process information involved in providing their services.

You can review the Google Privacy Policy, OpenAI Privacy Policy, and Cloudflare Privacy Policy for details.

Usage analytics

We collect first-party usage information for signed-in and signed-out visitors to understand which learning material people use and where they encounter difficulties. Records include public page paths, selected areas and reading levels, section visits, interactions with learning controls, page-engagement signals, search result counts, access errors, and the referring website’s hostname. We keep URL parameters, search terms, comment text, form values, and referrer paths out of analytics records.

Your browser stores a random visitor identifier for up to 90 days and a separate session identifier that renews after 30 minutes of inactivity. When you are signed in, the server can associate new activity with your internal account identifier. We do not use fingerprinting or session recordings. Usage events are stored in InterviewLayer’s Cloudflare D1 database and reports are restricted to the administrator.

Reports cover up to 90 days. Older event records are removed in bounded cleanup batches during later analytics activity. Browser counts are estimates: switching devices or clearing browser storage can make a returning visitor appear new. Reading activity does not establish mastery or interview readiness.

Usage analytics is disabled when your browser sends a Do Not Track or Global Privacy Control signal.

Administrator accounts are excluded automatically. The administrator can also exclude individual accounts from collection and reports, including earlier recorded activity associated with those accounts. An account exclusion applies while that account is signed in. The private admin dashboard also lets the administrator exclude their own browser’s future activity, including while signed out. This browser preference is stored separately in each browser and profile and is removed when site storage is cleared.

Cohort interest and coaching applications

When you register interest in a cohort or apply for mentorship or coaching, InterviewLayer stores your selected program, email address, LinkedIn profile URL, when you submitted the form, and a record of your consent to be contacted about that program. If you apply for both the cohort and 1:1 coaching, each has a separate interest and consent record. Daniyal uses this information to review your submission and contact you by email or LinkedIn. Submissions are stored in the site’s database and copied to a private Notion database for review. They are not displayed publicly.

Notion processes the application information stored there. You can review the Notion Privacy Policy for details.

Submitting this form does not create an InterviewLayer account or subscribe you to resource updates. To request a correction or deletion of your submission, contact ops@interviewlayer.com.

Resource updates

Creating an InterviewLayer account does not subscribe you to resource updates. The updates form is a separate choice with its own consent.

Article discussions and feedback

Discussion comments and replies are visible to other readers who can access the article. Posts are anonymous by default and receive a randomly generated name. If you uncheck “Post anonymously,” we use the username configured on your signed-in InterviewLayer account. Discussion records belong to the article. We do not attach your account ID, email address, or profile URL to them. Named comments contain a copy of your username at the time of posting; changing your username later does not rename existing comments. Question discussions follow the question’s existing reading-access requirements.

We store the comment text, its generated name or username snapshot, whether it was posted anonymously, the article and section being discussed, the selected reading level, and timestamps. A passage comment also stores the selected quote and a short amount of surrounding article text to locate it. Selecting text alone does not save or publish a highlight. Please avoid including personal or confidential information in a public comment.

Your browser stores a separate deletion key for each comment you post; the server stores a hash of that key. You can remove your post from that browser while the key remains available. Clearing browser storage removes this ability. Site administrators can also moderate discussions.

Temporary abuse-prevention records are separate from comments and accounts. These records limit repeated submissions and expire automatically. Hosting services may also process network information when serving requests.

Questions and account requests

For questions about account information, or to request a correction or deletion of your account data, contact ops@interviewlayer.com.