Using the inquiry form
Submitting the LaneCert inquiry form is optional. The form is hosted by Google Forms, and Google's service processes the information submitted through it.
Information the form may collect
The form may collect your name, phone number, email address, education or background information, military or veteran category where voluntarily provided, and funding-interest information.
How inquiry information is used
LaneCert uses submitted information to review and respond to inquiries about programs, the campus, and individual questions.
Information not to submit
Do not submit passwords or unrelated sensitive account information through the inquiry form.
Website analytics
LaneCert uses Google Analytics to understand how visitors use the website and to help measure and improve website performance and content. Google Analytics may collect technical and usage information such as browser or device information, pages viewed, approximate location derived from network information, and similar website interaction data. LaneCert does not intentionally send inquiry-form field contents, passwords, or other form-entered personal information to Google Analytics. Google may process analytics information under Google's own privacy and data-processing terms.
Updates to this notice
This privacy notice may be updated as LaneCert's inquiry and information-handling processes change.
Ask LaneCert
Questions you type into Ask LaneCert are sent to LaneCert’s server and an external AI provider with the selected language, recent conversation context and approved LaneCert information to generate a response. Guided quick answers run in your browser without sending a question to the AI service.
Your tab uses sessionStorage for a random conversation identifier, recent activity time, usage count and contact-prompt state. It does not store the full conversation transcript there. A session cookie connects requests to temporary server-side state.
Temporary server-side state includes recent questions and answers, cached responses, usage counters and contact-prompt state. The current Ask service uses PHP session storage for temporary conversation context. Separately, LaneCert keeps persistent server-side admission timestamps and successful-answer counts keyed by normalized, HMAC-derived IP and conversation identifiers. Each IP may admit up to 10 new AI conversations in a rolling 24-hour window; each conversation may receive up to 3 successful AI answers. Only the first successful answer admits a conversation. Guided topics, deterministic handoffs and failed provider requests do not use admission slots. Slots roll off after 24 hours. This state is not stored in browser cookies or cache and contains neither conversation text nor the plain IP address. People sharing one public IP share the admission limit.
A conversation expires after 30 minutes of inactivity. Expired entries are cleaned up when later requests check that browser session. New conversation creates a new identifier and clears the visible chat; it does not reset the rolling server-side IP admission limit or immediately erase the earlier server-side records. The idle limit is not a deletion schedule for all technical logs or external-provider records.
The Ask audit records a check result and hashed identifiers derived from the question and answer, rather than their full text. These identifiers are not a promise of anonymity. Hosting logs, audit records and external-provider data handling have separate operational and retention arrangements.
External AI processing follows the applicable service-provider arrangements. Please avoid passwords and unrelated sensitive personal or account information. Contact LaneCert through the Contact page with questions about information handling.
