CONVERSATION PRIVACY POLICY
A little information.
A clear purpose.
Ask Jimmy answers questions about Jimmy’s approved professional experience. It is not Jimmy speaking live and cannot make commitments on his behalf.
Screened questions and temporary context
For an authorized AI conversation, the composer and verifier may receive the screened current question, up to three recent screened question/answer exchanges, approved public career facts and qualifications, and the proposed answer. Each turn is screened again before transmission. Screening is not infallible: do not enter personal, candidate, compensation, confidential or credential information. Suspected sensitive content is rejected rather than transmitted. Private documents and identity tokens are never model inputs. Cloudflare Web Analytics measures public homepage visits and page performance. The beacon is not installed on private operator or conversation-review pages. Questions and answers are not sent to Web Analytics; the private conversation archive described below is separate. Requests use store:false without provider conversation storage; standard provider abuse-monitoring retention may still apply, typically up to 30 days. This is not a promise of zero provider retention.
Access and storage
Public visitors complete a Cloudflare Turnstile check. Its verification runs server-side; Cloudflare processes the challenge under its own privacy terms. Administrative routes remain separately protected by Cloudflare Access. A Secure, HttpOnly session cookie expires within one hour; it does not contain your conversation.
Screened questions and exact released answers are saved in a private, session-grouped conversation archive for quality review for 30 days from each submission. Suspected sensitive questions have status-only records. Rejected drafts, credentials, identity tokens, raw IP addresses and model reasoning are not included. Screening is not infallible; please do not submit sensitive information. No public conversation activity events are stored. Durable request fingerprints, reservation counters and closure records survive restarts to prevent duplicate processing. The archive distinguishes a server-released answer from the browser confirming that it rendered the answer or withheld notice. This does not prove that a person read it. Jimmy alone can review or export the archive through protected routes. Exported copies are outside automatic retention and must be managed by Jimmy. Expired archive records are excluded from reads and deleted by a scheduled storage alarm. The archive is never used as model context; conversation tokens and rejected draft prose are not stored. Duplicate-prevention records retain only keyed fingerprints and accounting metadata. Diagnostics retain bounded error codes, constraint paths, usage and categorical verdicts for up to 30 days, not conversation text. The server uses the Cloudflare-supplied IP transiently to create an operating-period-specific keyed identifier for abuse limits. The raw IP is not stored in application records or sent to the model. Accounting and duplicate-prevention records retain that opaque identifier; it is not a claim of anonymity. Hosting security logs are managed separately by Cloudflare.
Recent context is an authenticated encrypted token held only in browser memory, with a ten-minute expiry and a maximum of three exchanges / 6,000 UTF-8 bytes. The server decrypts it transiently and sends only screened text to a provider when separately authorized, never the token or reviewer identity. Context clears on reload or page close. A failed turn is excluded; the last verified context is preserved. Submitted questions and answers stay visible in chronological order in temporary browser memory, including earlier messages when an attempt fails; reloading clears this on-screen transcript, but does not erase the separate 30-day review archive. Please do not enter candidate identities, private hiring materials, compensation, health information, credentials, or other sensitive details.
No open-ended paid access
This service has a fixed operating expiry and shared spending allowance, plus session, visitor and site limits. Reservations are retained even when a request fails or its charge is uncertain. Exhaustion, expiry, an operator stop or a security/accounting failure closes the authorization; restarting does not reopen it. A safely withheld answer does not automatically close other questions. Provider credentials stay server-side. The earlier trial remains closed, and simulation accounting remains separate.
The Contact link opens your email app. The Résumé button downloads Jimmy’s PDF résumé.
Link click counts
We keep daily and total counts of Résumé download clicks and LinkedIn clicks. These measure clicks, not completed downloads or profile views. Click analytics contain no conversation content, raw IP addresses or personal identifiers. Random per-click IDs are kept briefly to prevent duplicate counting. A short-lived, memory-only keyed rate limit and a global rate limit help reduce abuse. Administrator test clicks are counted separately.