Privacy at VYKIX
Cookie Policy
Read about VYKIX's necessary storage, optional analytics, planned advertising tools, and your consent choices.
Effective 2026-10-17
1. Scope
This Cookie Policy explains how LIMITBRAVITY - LDA, trading as VYKIX, uses cookies and browser storage on vykix.com, privacy.vykix.com, and portal.vykix.com. Read it with our Privacy Policy (https://www.vykix.com/legal/privacy-policy/).
Portuguese Law 41/2004 generally requires consent before information is stored on or read from your device, except where it is strictly necessary to transmit a communication or provide a service you requested. Where the information is personal data, the GDPR and, where applicable, the UK GDPR and Data Protection Act 2018 also apply.
2. Your Choice
VYKIX uses a self-hosted c15t consent service. The website and client portal offer one optional purpose in this release: Analytics. It is off until you allow it. Necessary storage remains active because it secures the site, remembers your privacy choice, and supports services such as login, checkout, and payment.
One choice covers the VYKIX website and client portal in the same browser. A necessary cookie shares your choice between the two sites. Each site checks the current signed receipt and notice revision before enabling Analytics. Browser storage can keep Analytics off, but cannot authorize it. Use Cookie settings on either site to change or withdraw your choice. Each application serves its own banner before contacting Google. A material scope or notice change requires a fresh choice before Analytics can be enabled.
Google Tag Manager and Google Analytics are not contacted before you allow Analytics. VYKIX uses Google's basic consent approach, so declining does not send a cookieless measurement request.
Allow all and Decline all are available on the first screen. Choose Customize to review the optional Analytics control, then use Save choices. Optional choices are off by default. Refusing is as easy as accepting.
Your browser stores the shared choice in a vykix_consent_v3 cookie for .vykix.com, with a localStorage copy on each site. A current verified receipt can restore your choice in the consent interface without creating a new decision or renewing its expiry. VYKIX records the decision against a random, device-scoped subject in its own consent database. The public consent endpoint does not accept your name, email address, VYKIX account ID, IP evidence, or user-agent evidence.
The browser choice expires after 180 days. This is a VYKIX retention choice, not a statutory period. A material notice or purpose change invalidates the current signed receipt and requires a fresh choice before Analytics can be enabled.
Use Cookie settings in the website footer or client portal at any time. Withdrawing Analytics stops future optional browser events, reloads the page to stop loaded Google code, and attempts to remove accessible first-party _ga cookies. It also prevents queued WHMCS analytics from sending under the withdrawn proof. Allowing Analytics again does not reactivate that proof. Withdrawal does not delete information previously sent to Google; our Privacy Policy describes your rights and contact route. You can also clear VYKIX site data in your browser.
The client portal has its own Cookie settings control, available on its client pages. The portal addon loads its banner from the portal itself, so the banner can show a privacy-service outage without first contacting Google. Google Tag Manager and Google Analytics remain unloaded until Analytics consent is verified. If verification fails, optional analytics stay off. An acceptance that cannot be confirmed leaves Analytics off and asks you to try again. Refusals are saved locally and retried automatically. You can use the portal and complete an order after declining Analytics.
When you open the Client Portal payment step, WHMCS initializes both the Stripe and PayPal browser libraries so it can display the available methods and let you change your selection without leaving checkout. Both providers may receive IP address, browser, device, request, and security information before your final selection. VYKIX treats only the processing needed to present and secure the requested checkout, support method switching, authenticate transactions, prevent fraud, and process payments as necessary. The provider you confirm receives the additional payment information needed to complete that transaction.
3. Technologies Used in This Release
Technology: vykix_consent_v3 (shared .vykix.com cookie and origin-specific localStorage); Provider: VYKIX / c15t; Purpose: Stores your allowed or declined purposes, their decision times and notice references, and a random device subject. The signed receipt and current notice revision are checked separately before optional processing.; Duration: The cookie expires after 180 days. localStorage has no browser-set expiry, but VYKIX rejects and clears an expired copy. Reading a verified receipt does not renew the choice.; Basis: Necessary to remember the privacy choice you requested
Technology: vykix_consent_v3_withdrawal_pending (shared .vykix.com cookie and origin-specific localStorage); Provider: VYKIX; Purpose: Keeps optional analytics off while a refusal is waiting to be recorded or an acceptance could not be confirmed. It stores the decision time and, for a refusal made in an older banner, its original notice reference. It cannot authorize tracking.; Duration: The cookie lasts up to 180 days; the localStorage marker remains until the refusal is confirmed, a newer choice is confirmed, or you clear site data.; Basis: Necessary to enforce the withdrawal you requested while recording is unavailable
Technology: vykix_consent_v1 and vykix_consent_withdrawal_pending (legacy cookie and localStorage); Provider: VYKIX; Purpose: Earlier choices stay separate during the upgrade. An explicit refusal can keep Analytics off. A newer refusal can be recorded with its original time and notice reference. An old acceptance cannot enable Analytics. The current application reads these records without overwriting them.; Duration: The old cookie keeps its existing expiry. localStorage remains until the older application or you clear it. Expired choices are ignored.; Basis: Necessary to respect an earlier privacy choice during the upgrade
Technology: __Host-vykix-consent-receipt; Provider: VYKIX; Purpose: Host-only, Secure, HttpOnly proof on privacy.vykix.com that the consent decision was recorded. Website scripts cannot read it.; Duration: Up to 180 days; Basis: Necessary to prevent optional tools from relying on an unrecorded or stale browser choice
Technology: c15t-v3-pending-consent-saves:v1 (localStorage); Provider: VYKIX / c15t; Purpose: Remembers a choice waiting to reach the consent service. Unconfirmed acceptances cannot enable Analytics and require a fresh choice. Refusals can retry automatically.; Duration: Entries older than 7 days or past 10 retry attempts are ignored and removed when the queue next updates. The separate refusal marker continues to keep Analytics off.; Basis: Necessary to save the privacy choice you requested
Technology: c15t-v3-subject-reassignments:v1 (localStorage); Provider: VYKIX / c15t; Purpose: Links an old random consent subject to its replacement if the service reports a conflict. It keeps pending choices consistent and does not link your VYKIX account.; Duration: Old links are ignored after 7 days unless a pending choice still needs them; browser data remains until a later queue update or you clear site data.; Basis: Necessary to record the privacy choice against the correct random subject
Technology: vykix_consent_v3-epoch (cookie and localStorage) and vykix_consent_v3-cookie-miss (localStorage); Provider: VYKIX / c15t; Purpose: The first remembers when an old choice was cleared so another tab cannot restore it. The second records that a choice could not be written to a cookie.; Duration: The cookie lasts up to 180 days. Local markers remain until replaced, removed by a successful save or you clear site data.; Basis: Necessary to keep cleared choices and browser storage consistent
Technology: c15t-pending-consent-submissions and c15t:pending-consent-sync (legacy localStorage); Provider: VYKIX / c15t; Purpose: Old retry queues removed before the current consent code starts. Their values are not sent and cannot enable Analytics.; Duration: Deleted at startup when browser storage is accessible; Basis: Necessary cleanup of obsolete consent retries
Technology: c15t-pending-identify-submissions (localStorage); Provider: VYKIX / c15t; Purpose: Unsupported identity-linking queue that VYKIX deletes before the hosted consent manager starts. Its value is not sent or used by this release.; Duration: Deleted when the current consent code starts and browser storage is accessible; Basis: Necessary cleanup because identity linking is disabled
Technology: vykix-analytics-consent and rackfps-consent (legacy localStorage keys); Provider: VYKIX; Purpose: Removed during startup as migration cleanup. Their values are not retrieved and cannot authorize analytics.; Duration: Deleted when the current consent code next runs and browser storage is accessible; Basis: Necessary to prevent an obsolete preference from being treated as current consent
Technology: privacy-consent-storage (legacy c15t localStorage key and cookie); Provider: VYKIX / c15t; Purpose: An earlier choice may be read for compatibility. Reading it does not create a new decision or extend its expiry. An old acceptance cannot enable Analytics without a current compatible signed receipt.; Duration: Rejected when expired and removed when consent storage is cleared; Basis: Necessary to read or reject an earlier privacy choice safely
Technology: starlight-theme (localStorage); Provider: VYKIX / Starlight; Purpose: Remembers the light, dark, or automatic display preference you select in the documentation.; Duration: Until you change it or clear site data; Basis: Necessary to remember the interface choice you requested
Technology: sl-sidebar-state (sessionStorage); Provider: VYKIX / Starlight; Purpose: Remembers expanded documentation sections and sidebar position in the current tab.; Duration: Until the tab session ends; Basis: Necessary to preserve the documentation navigation state you requested
Technology: vykix-dayz-mobile-cta-dismissed, vykix-mobile-trial-cta-dismissed, vykix-rust-mobile-cta-dismissed, vykix-games-mobile-cta-dismissed, vykix-game-vps-mobile-cta-dismissed, vykix-blog-mobile-cta-dismissed, and vykix-frankfurt-mobile-cta-dismissed (sessionStorage); Provider: VYKIX; Purpose: Remember that you dismissed a mobile call-to-action during the current tab session.; Duration: Until the tab session ends; Basis: Necessary to remember the interface choice you requested
Technology: _ga and _ga_*; Provider: Google Analytics; Purpose: Distinguishes browsers and stores GA4 session and property state after Analytics consent.; Duration: Google's default may be up to 2 years; VYKIX attempts first-party deletion on withdrawal; Basis: Consent
Technology: __cf_bm, cf_clearance, and other Cloudflare security cookies when the matching protection is triggered; Provider: Cloudflare; Purpose: Bot management, traffic security, and remembering a completed security challenge.; Duration: __cf_bm: 30 minutes of inactivity. cf_clearance: the configured challenge-passage period, normally 30 minutes.; Basis: Necessary security
Technology: WHMCSInstanceID; Provider: VYKIX / WHMCS; Purpose: Maintains the portal session, cart, login state, and anti-forgery protections.; Duration: Until the browser closes; Basis: Necessary for the requested portal service
Technology: WHMCSUser, only when you choose Remember Me; Provider: VYKIX / WHMCS; Purpose: Remembers the portal login you requested.; Duration: Up to 365 days or until logout; Basis: Necessary to provide the remembered-login choice
Technology: __stripe_mid, __stripe_sid, Stripe session storage such as _ab or _mf, and Stripe.js on the Client Portal payment step; Provider: Stripe; Purpose: Stripe technology may load when the payment step opens, before you select or change methods, so that WHMCS can keep card payment available and Stripe can secure the checkout, authenticate a payment, and assess fraud. VYKIX does not use it for website analytics or advertising.; Duration: __stripe_mid: up to 1 year. __stripe_sid: about 30 minutes. Session storage: the payment session.; Basis: Necessary to present and secure the payment options in the checkout you requested
Technology: PayPal JavaScript SDK and payment security storage on the Client Portal payment step; Provider: PayPal; Purpose: PayPal technology may load when the payment step opens, before PayPal is selected, so that WHMCS can present the available option, determine eligibility, let you change methods, authenticate a payment, and prevent fraud. VYKIX does not authorize separable Pay Later promotional messaging, website analytics, or advertising components in this release.; Duration: Depends on the PayPal technology used in the checkout; see PayPal's cookie statement; Basis: Necessary to present and secure the payment options in the checkout you requested
Affiliate cookies: separate from Analytics
Customers can become VYKIX affiliates through the client portal (https://portal.vykix.com/) and share their referral links. Affiliate attribution uses WHMCSAffiliateID to remember a referring affiliate for up to 90 days and associate a qualifying order with their commission. The optional affiliate-recruitment feature uses VYKIXAffiliateSponsor to remember an affiliate sponsor for up to 30 days; it is removed after a successful sponsor assignment.
These cookies serve referral attribution and affiliate recruitment. They are separate from necessary login and payment storage and require an applicable optional cookie choice. Allowing Analytics or accepting the Terms does not itself give that permission. These optional cookies must remain disabled until that choice is available.
The separate WHMCS link-tracking cookie, WHMCSLinkID, is outside this release. Cloudflare Web Analytics, Browser Insights, Zaraz, CookieYes, advertising pixels, remarketing tags, and optional chat widgets remain outside this release and must remain disabled.
4. Optional Analytics
After you allow Analytics and the current consent receipt is verified, the website or portal loads the approved Google Tag Manager container and Google Analytics tag. Website events include page views, navigation and button clicks, plan/configurator choices, and clicks through to the portal. Portal browser events include public catalogue and product views, cart changes and cart views. Google browser tags and optional page events are excluded from account, payment, support, invite and verification pages. Login, registration and support-action analytics are disabled. Consented paid-invoice and refund reporting comes from the portal backend without loading Google code on private payment pages. analytics_storage is granted only for the verified Analytics choice. ad_storage, ad_user_data, and ad_personalization remain denied.
The WHMCS addon also measures eligible consented paid purchases and refunds directly with Google Analytics. It sends amounts, tax, currency, public product labels, opaque product/transaction references, quantities, billing term, and finite service location. Analytics client/session identifiers are included when available. The addon checks the relevant consent before each queued send. Withdrawal, expiry, or a superseded proof blocks that send; a temporary verification outage postpones it within the delivery limits. Payment, refunds, and service delivery do not depend on allowing this optional measurement. It does not enable advertising or export customer contact details, payment credentials, ticket content, or hosted files.
A sale can be reported without a matching website visit. Where the browser identifiers are unavailable, the addon uses a pseudonymous transaction-scoped identifier and records the attribution gap. Free trials and unpaid orders are not paid purchases.
If the consent service is unavailable, declining or withdrawing Analytics is saved in your browser and applies when you next open either site, provided your browser allows this storage. The browser retries recording the refusal automatically while a VYKIX page is open. The central record distinguishes the browser-reported decision time from the time our service received it. Until delivery, our service has no record of that refusal. Closing every VYKIX page or clearing site data before delivery can prevent it from reaching us. The portal stops new optional processing when it receives the local refusal; other queued processing can apply the central withdrawal only after it is recorded. An acceptance that cannot be confirmed leaves Analytics off and requires a fresh choice.
Planned advertising tools
VYKIX plans to introduce Google Ads measurement, Meta Pixel for Facebook and Instagram, and Reddit Pixel if we launch Reddit campaigns. These website tools are not enabled at present. Running an advertisement that links to our website does not switch them on.
When introduced, Advertising will be a separate, optional choice alongside Analytics. The choice will name the providers enabled for this website and explain that they receive website activity and device identifiers to measure campaigns and show relevant ads. Both optional choices will start off. Accepting our Terms or subscribing to marketing emails will not turn them on.
Before enabling these tools, we will update the technology table with the cookies and storage used, their purposes and durations, and the provider details in our Privacy Policy. We will issue a new notice revision and ask again; an earlier Analytics choice will not authorize Advertising. Declining Advertising will prevent advertising tags from loading, including cookieless advertising requests.
You will be able to withdraw Advertising through Cookie settings. Withdrawal will stop future website advertising collection, reload the page to stop code already loaded, and attempt to remove accessible advertising cookies. It does not undo an earlier lawful disclosure or delete information already held by a provider; the rights and contact routes in our Privacy Policy remain available. Customer-list uploads, enhanced matching using contact details, and server-to-server advertising APIs are not included in this planned advertising setup. WHMCS purchase/refund Analytics is described separately above and does not enable advertising.
5. Consent Records and Retention
The browser choice lasts up to 180 days. VYKIX keeps pseudonymous server-side consent and audit records for 730 days after the recorded decision, unless a longer period is required for a specific legal claim or regulatory request. The record contains the random subject, decision time, policy fingerprint, and allowed or denied purposes. The consent database does not store a VYKIX client-account ID in this record.
6. Managing Your Choice
Use Cookie settings in the website footer or client portal to allow, decline, or withdraw Analytics. Analytics begins off. You can also delete or block browser storage. Blocking necessary portal or payment storage may prevent login, checkout, fraud checks, or another service you requested from working.
7. Changes
We update this notice and its date when our actual storage use changes. A material change to optional processing invalidates the signed consent receipt so that we can ask again.
8. Contact
LIMITBRAVITY - LDA, trading as VYKIXRua Das Costeiras 103, 4835-421 GuimarĂ£es, PortugalVAT: PT517675110Email: info@vykix.com (mailto:info@vykix.com)