Privacy policy

This policy sets out the boundaries QuickQ observes when handling your information, and why we are deliberate about collecting as little as possible. The short version: we do not retain anything that could reconstruct your access behaviour.

Effective 6 November 2025 Last updated 13 October 2026

1. Our data principle

QuickQ collects only what is required to run an account and a subscription. We have neither the data nor the ability to reconstruct which services you reached, when, or what you transferred.

This is a property of the system rather than a marketing line: payloads are ciphertext between your client and the node, nodes do not parse content, and session state is never persistently linked to an account identity.

2. What we never collect

  • Access records: which domains and addresses you reach, and over which protocol.
  • Transferred content: message bodies, uploaded and downloaded files, request and response payloads.
  • DNS queries: which domains you resolve. Lookups are handled by an encrypted resolver inside the tunnel.
  • Connection timing: the exact times you were online or disconnected.
  • Address mapping: the correspondence between your real address and the tunnel address. It exists only in memory and is destroyed when the session ends.

3. What the account system retains

Only the following categories are stored, each with a defined purpose and retention period:

Account information, purpose and retention
TypePurposeRetention
Email addressSign-in, password recovery, subscription and security noticesDeleted within 30 days of closure
Password digestAuthentication (salted hash, not reversible)Deleted within 30 days of closure
Subscription stateEntitlements, renewals and refunds5 years as required by tax rules
Device countEnforcing concurrency limits and releasing devicesDeleted within 30 days of closure
Aggregated traffic countersCapacity planning (not traceable to individuals)90 days

We do not store full card numbers, expiry dates or security codes. Payment processing happens entirely inside a PCI-DSS compliant third-party gateway and we receive only the transaction result.

4. Encryption and key management

  • Mobile devices default to ChaCha20-Poly1305; desktops can switch to AES-256-GCM. Both provide integrity checking.
  • Key exchange uses X25519 with a fresh key per session, giving forward secrecy.
  • Session keys rotate hourly, so a single compromised key does not expose earlier sessions.
  • Internal access follows least privilege, with multi-factor authentication and audited operations.

5. Diagnostic reports

When you open a ticket and attach a report, it contains only the client version, protocol type, handshake result, error codes and link quality samples. It does not contain destination domains, transferred content or connection timing. You can stop the upload at any point and ask us to delete submitted attachments.

6. Third parties

  • Payment providers: receive only the order information needed to settle a transaction, never network usage data.
  • Facility and bandwidth suppliers: provide bare-metal resources and cannot read inside the encrypted tunnel.
  • Website analytics: aggregate measurement that does not rely on third-party cookies, with no cross-site tracking or profiling.

We do not sell, rent or share your personal information for marketing purposes.

7. Your rights

  • Access and export: review the account information we hold in the account centre.
  • Correction: change your email address and account settings at any time.
  • Deletion: request closure and we delete related data within 30 days, except records we must keep for tax purposes.
  • Withdraw consent: unsubscribe from email at any time without affecting your account.

Submit such requests through the support page and we will respond within 15 business days.

8. Policy updates and contact

If this policy changes materially we update the "last updated" date at the top and notify registered users by email. Continuing to use the service means you accept the revised policy.

This page is demonstration copy for the website template. It shows the structure and expression of a privacy policy but is not legal advice. Have your legal team review and adapt it to the actual business and applicable jurisdictions before launch.