Type or speak your request. Sign in to securely sync conversation history.
Q.Core CANDIDATE · Guest mode · conversations are not persisted
Sign in to sync history and language preference across sessions.
Your password is submitted only to the identity service for authentication; Q conversation tables do not store it.
—
Deleting the account removes the Q profile, locale preference, and conversation history linked to that member.
Voice input is transcribed by the browser/device speech service; Q.Core receives text, not raw microphone audio.
History is visible only to the authenticated member and is protected by Row Level Security.
Q's iOS digital subscription uses Apple StoreKit. The website does not invent products, prices, or purchase success.
Apple supplies product identifiers, prices, purchase results, restore results, and verified entitlements. Q remains fail-closed until those real products are configured.
This release uses StoreKit for iOS digital subscriptions and does not create a second web checkout channel.
Help with Q, Q.Core connectivity, generation, voice input, privacy questions, feedback, and feature requests.
If a request will not send, first make sure the Q.Core status is ready. If a request fails after sending, try again with a shorter request and keep any error text shown by Q.
Q does not fabricate a successful answer when the governed provider route is unavailable.
Voice input is optional. On iPhone, verify that Microphone and Speech Recognition permissions are enabled for Q. Text input remains available when voice permissions are denied.
The native Q client converts voice to text through Apple frameworks; raw microphone audio is not sent to Q.Core.
The native client uses HTTPS for Q.Core communication and does not ship the model-provider credential inside the iOS app. The full Privacy Policy is available from the Privacy Policy link on this website and from iOS Settings.
Do not send passwords, API keys, authentication secrets, payment data, or other sensitive credentials in a support request.
When suggesting a feature, describe what you were trying to accomplish, what you expected Q to do, and what would make the experience better. Screenshots are useful when they do not expose private information.
For product support, technical problems, privacy questions, feedback, or feature requests, contact Q using the approved information below.
This Privacy Policy explains the verified information-handling behavior of the Q iOS app, the Q website at chat.goqi.ai, and Q.Core.
This policy describes privacy-relevant behavior that is supported by the current Q product implementation. It does not publish unverified legal entity, jurisdiction, provider-identity, or numerical retention claims.
For privacy questions or requests, contact emerson@flyingtravel.com or call 917-843-0636.
| Category | Examples | Purpose |
|---|---|---|
| User-submitted content | Prompts, questions, instructions, and other text you intentionally send. | To perform the request and return a response. |
| Limited request information | Request identifiers, status information, and error details used by the governed request path. | To route requests, associate results, and diagnose failures. |
| Voice-derived text | A transcript created when you choose to use voice input. | To let you submit a request by voice instead of typing. |
| Local privacy acknowledgement | A local value showing that the first-use privacy notice was acknowledged. | To avoid repeatedly showing the same notice after acknowledgement. |
| Support information | Information you voluntarily provide when contacting Q Support. | To respond to support, privacy, feedback, or feature requests. |
| Account or history information where those website features are used | Information needed by the available registration or history experience. | To provide the feature requested by the user. |
Do not submit passwords, private API keys, authentication secrets, payment credentials, or other sensitive credentials in ordinary prompts or support requests.
Most content is collected directly from you when you type a request, use optional voice input, use an available account or history feature, or contact support. Q.Core also creates limited request identifiers and outcome information needed to complete and diagnose requests.
Q is an AI-enabled service. When you submit a request, Q.Core may send the text needed to answer that request to the AI provider mounted by the service so the requested output can be generated. This policy does not name an exact production AI provider unless that identity has been separately verified for the active deployment.
When you voluntarily use voice input, device microphone and speech-recognition services may process audio to create text. In the native iOS client, Q sends the resulting text to Q.Core rather than raw microphone audio.
The Q iOS app and website present a first-use privacy notice and keep the full Privacy Policy available afterwards. Voice input is optional; microphone and speech-recognition permissions can be denied or revoked through device settings, while text input remains available.
The current release does not use advertising or cross-app tracking. The privacy acknowledgement is stored locally so the same first-use notice does not repeat after agreement.
The verified local retention behavior is limited to what is stated here: the current native iOS visible conversation is kept in memory for the app session, and the privacy acknowledgement remains in local app or browser storage until that local storage is cleared or the notice is versioned again.
No fixed server-side or AI-provider retention duration is stated in this policy because no verified numerical schedule is being asserted. For deletion questions or requests concerning information associated with Q, contact Q using the privacy contact below.
You can stop submitting new content at any time, revoke optional device permissions, clear locally stored acknowledgement state, and use available deletion controls for features that expose them.
For access, correction, deletion, consent-withdrawal, or other privacy questions, email emerson@flyingtravel.com or call 917-843-0636. Describe the Q feature and the request so the relevant records can be located without exposing unnecessary information.
The current native client requires HTTPS for Q.Core communication, and the model-provider credential is not shipped inside the iOS application. Protected device features use the platform permission model. Q also preserves governed request and error-handling boundaries rather than fabricating successful results when a provider route is unavailable.
No internet-connected service can eliminate all risk. Do not submit secrets or credentials that are not required for the feature you are using.
This policy may be updated when verified product behavior, data flows, privacy choices, or support information change. If the first-use disclosure materially changes, Q can use a new versioned acknowledgement so the updated notice is presented again.
Privacy and support contact: emerson@flyingtravel.com · 917-843-0636.
Q processes the text you choose to submit and limited request identifiers to provide AI responses. Q.Core may send the text needed to answer your request to the AI provider mounted by the service. Optional voice input uses device microphone and speech-recognition services to create a transcript; Q sends the resulting text, not raw microphone audio, to Q.Core. The current release does not use advertising or cross-app tracking. By selecting “I AGREE,” you acknowledge this privacy notice and agree to continue. You can read the full Privacy Policy at any time using the Privacy Policy link in Q.