QuickQ Data and Privacy Information

QuickQ account access, website use and client connections are part of the same service environment, but they do not involve identical types of data. The login interface uses an email account and password and asks users to acknowledge the Terms and Privacy Policy before signing in.

QuickQ is associated with Airui Technology Co., Ltd. under its current public Terms. The privacy material focuses on the difference between browsing activity that is not recorded and service information used to support the operation of the service. See About for brand background.

The current public Privacy Policy does not publish an independent privacy audit, jurisdiction-specific certification or proof of absolute anonymity. Privacy claims should therefore stay within the categories and purposes that QuickQ actually discloses.

The public policy describes the following browsing and user-activity categories as not recorded. This is different from saying that no service or connection information is used at all.

• Browsing history and the websites visited
• Visited destinations, online trails or similar traffic-destination information
• DNS queries and the user-activity examples listed in the Terms, including email activity
• Browsing-activity records used to reconstruct the content or destinations of a user session

These categories should be distinguished from service-support information. QuickQ’s Privacy Policy separately lists VPN connection date, data status, purchased package information and connection errors as information used to provide service and support.

QuickQ’s Terms also state that access attempts to its servers are recorded for security and troubleshooting. For that reason, “no logs” should not be interpreted as meaning that no connection or operational data exists under any circumstances.

VPN connection date

The Privacy Policy states that QuickQ uses the date on which a user connects to the VPN service and explicitly says this is the date, not the specific time. It does not publish a retention period or a more precise timestamp field for this item.

Data status

The Privacy Policy lists “data status” as service-support information but does not define the underlying technical fields. That wording should not be expanded into device fingerprinting, precise location, full traffic logs or other categories that the policy does not expressly disclose.

Purchased package information

QuickQ states that information about purchased data packages is used in connection with providing service and support. The public Privacy Policy does not separately describe card numbers, full payment credentials or detailed transaction records in this section.

Connection errors and server access attempts

The Privacy Policy lists connection-error information as service-support data, while the Terms state that access attempts to QuickQ servers are recorded for security and troubleshooting. Users can contact support at [email protected], but should not send full passwords or verification codes in normal support messages.

QuickQ’s Terms state that third-party services may be used and that users may also be subject to those third parties’ terms. Data handling by app stores, payment services, advertising providers or other external services is governed by the relevant provider’s own policies.

The current public Privacy Policy does not provide a complete inventory of third-party service providers, analytics tools or the data fields associated with each external service. It should therefore not be interpreted as proof that no third-party requests or external data handling can occur.

QuickQ’s Terms state that personal information is not provided to third parties unless QuickQ is ordered to do so by a court with jurisdiction. Any disclosure would still be limited by the information actually held and by the applicable legal process.

The current QuickQ login interface uses an email account and password and asks users to acknowledge the Terms and Privacy Policy before signing in. Public content, account login and VPN connection data should not be treated as a single undifferentiated category of personal information.

When installing QuickQ, verify the application source, app-store listing or desktop package details. Software from unknown sources may have its own data-collection behavior that is not part of QuickQ’s published privacy rules. Installation information is available under Download.

The published policy therefore does not support a fixed number of retention days, an automatic deletion schedule, a support-ticket retention period or a stated order-record retention term. What it does disclose is the use of connection date, data status, purchased package information and connection errors for service and support.

The Terms additionally state that server access attempts are recorded for security and troubleshooting and that usage restrictions may be enforced to protect users and the service. The public policy does not publish a specific account-closure deletion workflow or data-storage location.

The current public Privacy Policy does not list a specific security certification, encryption-at-rest standard, independent audit framework or incident-notification process. Security claims should therefore remain within the controls and data practices that are actually disclosed.

The current public Privacy Policy does not list a detailed workflow or fixed response period for access, correction, deletion, export or objection requests. How a request is handled will depend on the account, the data actually held and applicable law.

The public Privacy Policy also does not publish a specific child-age threshold, parental-consent mechanism or separate child-data policy. Any legal age or consent requirements therefore depend on applicable law.

QuickQ’s Terms state that agreements may be modified, changed or revised and that users are responsible for checking the current terms. Privacy information should likewise be read in its latest published form together with the Terms.