Last Updated: September 15, 2026

This notice explains how www.naomijnguyen.com and the Bootwitch Portfolio interactive demo handle visitor information. The public portfolio is separate from private notebooks, development workspaces, credentials, cloud resources, logs, and other non-public materials.

The site may process information you choose to provide, including simulated terminal commands, assistant questions, contact submissions, and transcript data when you choose to export or submit it. Processing means information may pass through the system as needed to provide a feature. It does not necessarily mean that information is stored.

The site is designed to retain only limited operational data needed for security, abuse prevention, debugging, rate limiting, and reliability. Logs may include timestamps, features used, event classifications, generalized browser or platform information, and limited numeric metadata. Routine logs are not intended to retain full assistant conversations, transcript contents, contact-message bodies, passphrases, credentials, API keys, private project data, or other secrets.

When the portfolio assistant is enabled, a visitor's question and relevant curated public portfolio content may be processed through OpenAI API services to generate a response. The assistant may use extra reference notes that are not shown in the site's file browser; those notes are limited to material already public on the website or in Jennifer's published repositories. Hiding them from the interface keeps the exhibit readable and is not a secrecy boundary. Private notebooks, credentials, private files, workspace exports, and other non-public materials are not intended to be included in assistant context. Third-party service providers may separately process or retain technical information under their own applicable terms and privacy practices.

During an unlocked session, the browser keeps the complete structured conversation so the guide can respond naturally. For each answer, the browser sends a bounded rolling summary and a small number of recent turns back to the portfolio Worker. That context is treated as untrusted conversation continuity, not as evidence about Jennifer or her work. Complete conversations are not routinely written to the site's D1 database or R2 storage.

After an eligible completed answer, a visitor may type contribute <1-5> to rate it from incomplete or unhelpful to complete or helpful. Submitting that command explicitly contributes only the most recent question and answer, the rating, answer mode, and cited public-page identifiers for routing and answer-quality evaluation. The contribution begins as an unreviewed evaluation candidate, not training data. Failed or interrupted answers and privacy-boundary refusals are not eligible. If the visitor does not run the command, the verbatim exchange is not stored by this feature.

Contact information is retained only when a visitor chooses to submit it. Transcript and generated summary exports are visitor-initiated. The generated summary passes the conversation through the Worker and model once to create an inert HTML file; its contents are not intended to be retained by the portfolio solely because an export was generated. Operational records may note that an export occurred and its approximate size without storing the exported text.

The clear command removes the browser-held conversation, rolling summary, visible terminal history, and any in-progress answer for that session. It does not revoke the current one-hour passphrase or delete files the visitor already downloaded. A refreshed or closed page also loses browser-held conversation context.

Operational information is retained only as reasonably necessary for security, debugging, reliability, and site administration. Routine long-term storage of complete visitor conversations is not part of the intended operation of the portfolio. A deliberately contributed single exchange is the narrow exception described above.

The simulated terminal is a demonstration interface and does not execute commands on a visitor's computer or modify local files. Visitors should not submit passwords, API keys, confidential information, or other sensitive information through portfolio features.

Questions about this notice may be directed to Jennifer Nguyen using the contact information provided on the site.