Privacy
This website handles information you choose to submit through enquiry forms or live-test controls, plus standard server logs required to operate and protect the site.
Policy
Do not submit secrets, passwords, private keys, classified material, or sensitive attachments through this website.
Secure enquiry submissions may include organisation name, contact details, sector, country, project type, budget range, and your written requirement. The guide's optional reply form asks for name, email, discussion type, and optionally organisation, city/country, and a short message.
Server logs may include IP address, user agent, request time, and URLs requested for security and troubleshooting.
Data is used to respond to enquiries, assess access, protect the site, and decide whether a confidential discussion is appropriate. Contact details are never inferred from chat text or enriched with precise location data.
Questions sent to QE1 Guide are processed by a local site model. The application does not intentionally add question text to the lead inbox; submit personal details only through the separate consent-based reply form.
Reply requests created inside QE1 Guide are stored in owner-only server files for less than 30 days. The server queues a notification to the site owner; acceptance by the sending server does not guarantee final inbox delivery. Any delivered mailbox copy follows the owner's mailbox retention and may remain while the enquiry is handled or legal records are required. Security rate-limit records use a one-way network identifier and do not add an inferred location to the lead.
If you explicitly enter an IonQ API key in a live-test control, the site sends it through the server only to make the requested IonQ call. It is not intentionally written to the QE1 lead files. Provider processing is also governed by the provider account and terms.
Privacy questions can be sent to shaf@talktoai.org.