QATS Cookies and Storage Policy

SHA-256 of the exact text

sha256:6e2b71613cd94a9cee08082f1f9fae8ef901797bc0b95168d5c4e8be04eddc2d

Verify it yourself

Download the text the hash was taken over

1Scope and technologies

1.1This policy explains cookies and similar storage or access technologies used for QATS Prop by QUANT ALGORITHM TREE SYSTEM LTD, company number 517208377, Israel. Contact support@qats.us for privacy questions. Read it with the Privacy Policy, which covers purposes, recipients, transfers, retention and your personal-data rights.

1.2Cookies are small records a browser stores and may send with requests. Local storage persists in a browser until removed or replaced; session storage normally lasts for the browser tab’s session, subject to browser restoration. Scripts, embedded content and event requests can also access device information. The absence of a traditional cookie does not make tracking exempt from applicable rules.

1.3Section 4 identifies QATS storage on the site or application origin you use. Section 5 also identifies optional tools and external recipients. A first-party cookie can support a third-party service, and optional event requests can transmit information without a stored cookie. An identifier may be linked to an account or order; it is not necessarily anonymous. Browser deletion and deletion of information already sent to a server are separate actions.

2Necessary functions and choices

2.1QATS uses authentication and security storage to keep your session secure, and preference records to remember your privacy choice. Storage strictly necessary for a service you request may operate without optional consent where the applicable exception permits it. The exception covers only the necessary purpose, not unrelated monitoring or marketing.

2.2Language, theme, chart and terminal settings remember the interface you select. Sign-in prefill and pending-command records help complete the relevant action; support state maintains a conversation you request. These functions use an applicable storage exception only to the extent its conditions are met; otherwise QATS requests your permission. They are not used as permission for unrelated analytics or advertising.

2.3Optional uses include referral attribution under Section 3.1; website analytics and diagnostics using Google Analytics 4 (GA4), Google Tag Manager and PostHog; session replay using Microsoft Clarity; and advertising conversion measurement using Meta Pixel and Reddit Pixel. Cookie settings provides two independent switches: Analytics and Advertising. The Analytics switch controls GA4 analytics tags through Google Tag Manager, PostHog and Clarity. The Advertising switch controls Meta Pixel, Reddit Pixel and advertising uses of Google tags where configured. Accepting Analytics does not enable Advertising, and accepting Advertising does not enable Analytics. Google's tag-management layer applies the choice relevant to each tag and purpose. Microsoft's possible further uses are described in Section 5.6. Browsing, scrolling, closing a notice or accepting trading terms does not turn optional tracking on. Declining optional tracking does not prevent ordinary access to the service; you can still submit an available referral code directly for a particular transaction.

2.4Use the Analytics and Advertising switches in Cookie settings to accept or reject each category independently. Each switch controls its category as a whole; there is no event-by-event or provider-by-provider selection within a category. Neither optional category is preselected. You can reopen settings and turn either or both switches off without losing ordinary service access. Withdrawing one category does not automatically withdraw the other. Your choices apply to that browser; another browser or cleared storage may require new choices. Essential financial and security records are separate from optional tracking and are not erased by switching either category off. Refusal and withdrawal must be readily accessible and must not require materially more effort than acceptance.

2.5QATS records each optional-category choice, notice version, choice time and the limited browser or account reference needed to honour and demonstrate that choice, under the Privacy Policy's retention rules. That evidence is not permission for an undisclosed purpose or recipient. Refusal or withdrawal must not be bypassed through fingerprinting, hidden server events or a substituted identifier; genuinely necessary processing remains separately limited to its own purpose.

2.6Optional analytics and replay collection remain off before affirmative Analytics consent and stop after its refusal or withdrawal. Advertising collection and event transmission, including Meta Pixel and Reddit Pixel, remain off before affirmative Advertising consent and stop after its refusal or withdrawal. Google's advertising-storage and advertising-use consent signals, and advertising collection by Meta Pixel and Reddit Pixel, follow the Advertising switch; Google's analytics consent follows the Analytics switch. Analytics consent alone does not grant advertising permission. Disabling cookies alone is insufficient: optional cookieless pings, memory-only tracking and server-side copies of the same events are subject to the relevant category choice. Consent signals sent to Google, Meta, Reddit or Microsoft must reflect permission actually obtained; they are not themselves evidence of valid consent. Any provider's independent advertising use requires the applicable advertising permission and cannot be enabled solely through Analytics consent. Where a further purpose-specific choice is legally required, QATS must provide it or keep that use disabled. Sections 3.8 and 3.8(a) describe the deployed advertising pixels.

3Optional tracking and its purposes

3.1Optional referral storage records the partner or Friend referral code, as applicable, capture time, visit identifier and landing path to support attribution and the relevant offer. The listed browser-storage window is 30 days from capture. Programme eligibility and registration or purchase windows follow the relevant accepted offer; storing a code does not extend them. A confirmed server-side attribution or commission record may remain for administration and evidence under the Privacy Policy even after the browser record expires or is deleted. An expired browser value is not used to create a new attribution merely because it has not yet been physically removed. Clearing browser storage or withdrawing its optional purpose does not itself cancel a previously lawful server attribution or an accepted discount; correction, detachment and benefit reversal follow the relevant programme terms and lawful server processing.

3.2After the optional analytics switch is turned on, QATS uses Google Analytics 4 (GA4) and PostHog to understand navigation, completion of service flows and technical errors, and to improve the website and support diagnostics. Google Tag Manager manages the tags and event routing. The container includes Google Analytics tags, and the events collected through Google Tag Manager are sent to GA4 for analysis. PostHog also receives analytics events; the parameters sent to each destination depend on the configured event. The following event categories may be measured on the website and application, including signed-out and signed-in journeys, subject to Sections 3.4 and 3.5:

3.2(a) Navigation and registration: page and site-section views; registration started; registration completed successfully; registration error.

3.2(b) Account access: sign-in started; sign-in completed successfully; sign-in error; sign-out; email confirmation completed. The email-confirmation event records the outcome, not the email address or verification token.

3.2(c) Purchases: checkout started; payment completed successfully or a plan activated; purchase failed, cancelled or payment declined. Events may include the amount, plan, promotional code and checkout reference described in Section 3.4. These are transaction-context parameters, not bank or payment-card details.

3.2(d) Withdrawal requests: request flow started; request submitted successfully; request-submission error. In the current event implementation, withdrawal events include the requested withdrawal amount. They do not contain bank or wallet details or the full contents of the request. A withdrawal amount is financial activity information, even when no payment credentials are sent; its disclosure does not remove the restrictions in Sections 3.4 and 3.5.

3.2(e) Partner programme: partner application submitted; partner-application error; partner campaign created, changed or deleted; partner link or promotional code copied; partner offer changed. A promotional code may be included as a structured event parameter under Section 3.4. Free-text campaign contents and a full copied link containing personal information or tokens are excluded.

3.2(f) Contact: contact-form submission. The event does not contain the message, sender details or other field contents.

3.3Turning the Analytics switch off stops new analytics and replay collection and transmission. Turning the Advertising switch off stops new advertising collection and event transmission, including Meta Pixel and Reddit Pixel; QATS deletes the Meta cookies _fbp and _fbc and the Reddit cookies _rdt_uuid and _rdt_cid on its domains and prevents them from being recreated while advertising permission remains off. Unsent events for the withdrawn category are discarded, and its optional browser identifiers under QATS's control are cleared or deactivated. Withdrawing one category leaves the other subject to its own choice. Where optional referral storage is covered by a withdrawn choice, it is also cleared or deactivated. QATS propagates changed choices to the relevant tags and recipients and takes any required deletion steps for information already collected on that consent. Withdrawal does not affect the lawfulness of processing before withdrawal. Continued retention requires a specific lawful reason, such as a legal obligation or the establishment, exercise or defence of legal claims, and is limited to that reason; consent-based tracking cannot simply be relabelled as necessary processing. Deleting browser cookies does not itself erase data already received by a provider. Essential order, payment, security and complaint records continue under their separate purposes and legal bases. Section 6 explains controls and requests.

3.4Analytics event payloads include the event type or outcome, time, sanitised page or section reference, and proportionate browser, session and technical metadata. Depending on the event, they also include an amount, the selected or activated plan, a promotional code and a checkout number or identifier. Amounts may relate to a service purchase or a withdrawal request. These structured parameters may originate from a selection or transaction associated with a form and are sent as event properties rather than as complete forms. Pseudonymous browser or session identifiers, and an internal account reference where needed for the disclosed diagnostics, may link events. The tools also receive device or browser information and connection information, including an IP address at the network layer. The resulting data is not necessarily anonymous merely because names and email addresses are omitted. Meta Pixel's and Reddit Pixel's advertising events and address information are separately described in Section 3.9; the analytics parameters in this section are not a list of data sent to Meta or Reddit.

3.4(a) A plan identifier describes the service selected or activated. A promotional code describes an offer or attribution associated with an event, not permission to disclose a code containing personal contact details. A checkout number is an internal reference and may allow QATS to link an event to an order or account; it must not expose bank credentials, personal contact details or a payment-access token. Purchase values and requested withdrawal values have different meanings and must not be treated as interchangeable. Amounts and transaction references linked to a person are personal data and can reveal financial activity. They require data minimisation and recipient-specific controls, not only removal of email addresses.

3.5Apart from the limited structured parameters expressly described in Sections 3.4 and 3.9, we do not send form-field contents or complete submitted forms to optional tracking tools. Names, email addresses, telephone numbers, passwords, authentication or email-verification tokens, identity documents, contact-message text, bank or payment-card details and wallet addresses are excluded, including hashed copies of contact or payment details. Error events use non-sensitive categories rather than raw submitted values or full error dumps. For analytics and replay, page addresses, titles, referral information and other event properties must be sanitised to prevent personal identifiers, tokens and excluded content from being transmitted through paths, query strings, fragments or metadata. The advertising pixels' transmission of full page addresses, Meta's referrer address and the controls required for those addresses are described in Section 3.9(b). Financial activity parameters require a purpose and recipient-specific assessment: a parameter that is unnecessary or prohibited by the recipient's terms must not be sent merely because it is listed here or optional consent was given. Information submitted to QATS or a payment or identity provider to perform a requested service is governed separately by the Privacy Policy.

3.6With the optional analytics switch on, Microsoft Clarity records sessions only on QATS pages eligible for recording. The /admin route and all pages containing or displaying confidential or sensitive personal information are excluded from Clarity collection and session replay. This includes pages containing financial-account details, balances, withdrawal information, trading positions, payment details or identity-verification materials. QATS enforces these exclusions in the application before Clarity can collect or transmit information from an excluded page, including when navigation occurs without a full page reload. Masking is not a substitute for excluding those pages. On eligible pages, session replay reconstructs navigation, clicks, scrolling, pointer movement and page layout to identify usability problems. It is not an audio or camera recording and does not record activity outside the instrumented QATS pages. The protections in Section 3.7 apply to eligible pages. QATS limits Clarity to uses permitted by Microsoft's terms.

3.7On pages eligible for recording under Section 3.6, input-field contents are masked or excluded from Clarity session replay and are not visible in the recordings. Masking means that content is concealed or omitted; it is different from encrypting data in transit or storage. These protections operate before excluded content is collected or transmitted. If a page displays confidential or sensitive personal information, including through dynamically updated content, Clarity collection and recording are disabled before that information can be captured. Such a page remains excluded even if its fields could be masked. Field masking does not by itself protect page addresses, clicked links, referral URLs, images or other metadata; these must be separately restricted under Section 3.5. Interaction and identifier data from eligible pages may still be personal data after masking.

3.8Reddit Pixel is in use to measure conversions and the effectiveness of QATS advertisements on Reddit. It operates only after the Advertising switch is turned on; Analytics consent alone does not enable it. Reddit receives the permitted events, purchase parameters and full page address described in Section 3.9, together with advertising click or browser identifiers, event timing and device or connection information, including an IP address at the network layer. The deployed domains are www.redditstatic.com, alb.reddit.com and pixel-config.reddit.com. Advanced Matching, including automated advanced matching, is disabled. Reddit may match permitted signals to advertising interactions for attribution, reporting and campaign optimisation. Retargeting audiences or a server-side Conversions API require an updated disclosure and any corresponding permission before use.

3.8(a) Meta Pixel is in use for measuring conversions from QATS advertising and assessing campaign effectiveness on Meta services. It operates only after the Advertising switch is turned on, independently of Analytics consent. The Pixel sends the permitted events, transaction parameters and address information described in Section 3.9 to Meta Platforms through connect.facebook.net and www.facebook.com, together with browser or advertising identifiers, event timing and device or connection information, including the IP address received with a request. Meta may match these signals to advertising interactions. Omitting contact details does not make Pixel data anonymous or prevent Meta from recognising a browser or linking signals using its own information. Any additional QATS use, including retargeting audiences or server-side conversion reporting, requires a corresponding notice and any required permission before activation.

3.9After Advertising consent, Meta Pixel and Reddit Pixel receive the same QATS event categories: public-page views; registration; checkout started; purchase completed; contact-form application submitted; and partner application submitted. Meta's checkout-start and purchase events include the amount, currency, plan, quantity and checkout number. Reddit's purchase events include the amount, currency, quantity and checkout number. These parameters describe a QATS service purchase, not a withdrawal, balance, investment holding or trading result. A checkout number is a transaction reference, distinct from the QATS account identifier, and may allow QATS to link an event to a transaction. Analytics events collected under Section 3.2 are not automatically sent to either advertising recipient.

3.9(a) QATS does not send Meta or Reddit withdrawal events or amounts, sign-in or sign-out events, other authenticated account-area actions, QATS account identifiers, email addresses or other contact data, including hashed copies. Registration and the application events listed above record the action, not submitted field contents, messages or identity materials. Checkout and purchase events listed in Section 3.9 are the permitted service-purchase conversions; they do not authorise tracking other account-area activity. Reddit Advanced Matching is disabled. Advanced matching or additional automatic collection must not send excluded data or events to either recipient.

3.9(b) Meta Pixel and Reddit Pixel transmit the full address of the page on which they operate, including query parameters where present. On the payment-return page, that address includes the checkout number. Meta also transmits the referring-page address made available by the browser; browser referrer controls can limit that address. These disclosures are not limited to anonymised page or section names. The disclosed checkout number is a transaction reference, not an account identifier or a payment-access token, but may be linked to an order and is not necessarily anonymous. QATS must prevent page and referrer addresses from exposing contact details, account identifiers, verification or authentication tokens, confidential financial information or other excluded data. If a page or address would expose excluded information, the affected Pixel must not collect or transmit until the disclosure is prevented. Disclosure of full addresses does not override those restrictions.

3.9(c) Sending an event to GA4 or PostHog does not mean that it is sent to Meta, Reddit, Microsoft Advertising or a Google advertising destination. QATS restricts advertising destinations to the permitted event set for that recipient and the applicable Advertising choice. Withdrawal events and amounts, balances, trading positions, financial-account details, identity-verification information, account-access errors and contact-message contents must not be forwarded to advertising destinations. A listed service-purchase parameter is not permission to send information prohibited by a recipient's terms. Removing a field or masking replay does not authorise a prohibited disclosure.

4First party storage inventory

4.1The table lists QATS key names or families, purposes and storage lifetimes. An account, user or instrument suffix identifies its context. “No automatic expiry” means the browser record remains until the site updates or clears it, or you or the browser remove it. Local storage is not automatically cleared by closing a tab. Limits on the number of saved items do not create an expiry date. Server retention is governed separately by the Privacy Policy.

4.2QATS Trade uses extension-origin storage separate from website cookies and optional website Analytics and Advertising choices. Its background IndexedDB vault qats-trade-vault holds OAuth access and refresh tokens. Access tokens are valid for 30 minutes. Refresh tokens rotate on use, expire after 30 days of inactivity and are limited by a grant lasting up to 180 days, unless revoked earlier. A one-time connection code is valid for 60 seconds. Token validity does not itself erase the corresponding local value or server evidence.

4.3Extension chrome.storage.local holds connected-account identifiers without OAuth tokens, a random installId, preferences, panel layout, leverage and slippage settings and cached chartLink data. Manually entered Advanced API keys are held separately in its keys field in that local storage and must be treated as sensitive. These records have no automatic storage expiry. Panel sessionStorage holds the selected account for that panel session, subject to browser behaviour. Website cookie deletion does not necessarily clear extension-origin storage.

4.4Extension storage supports the connection, security and settings you request; it does not authorise advertising, tracking unrelated browsing or reuse by website analytics. QATS applies any required device-storage permission or applicable strictly necessary exception to the actual purpose. The extension does not read website cookies or send browser session cookies with its QATS API requests. Its operational chart and order data are described in the Privacy Policy and QATS Trade privacy notice.

4.5Remove extension data with its available controls or Chrome extension controls, including removal where applicable. Revoke the connection in QATS to terminate server access; remove any Advanced API key separately. Local deletion and token expiry do not close positions, cancel accepted orders or delete server histories. Server retention, external alert removal and data-rights requests follow the Privacy Policy. The existing external_chart choice and embedded-chart controls remain separate and are not changed by these extension provisions.

5Third party services and external pages

5.1Google sign-in, hosted payments, identity verification and enabled third-party chart content can send the provider your IP address, browser information and the data needed for the selected feature. Relevant services include Google, Verifone, Didit and TradingView where used. Their flow identifies the provider and applicable notice. Provider-controlled storage names and durations can differ by feature and domain; any non-essential embedded technology on QATS pages is subject to the relevant choice. Before activating a non-essential embed on a QATS page, its applicable choice notice identifies the actual purpose, provider or recipient, relevant domain and storage duration. A generic provider link does not replace that information or the required prior choice.

5.2Selecting a third-party feature authorises only what is necessary to supply that feature under applicable rules. Non-essential storage or tracking requires its own applicable permission. QATS remains responsible for scripts and embeds it causes to load on its pages. Provider-controlled pages also carry their own notices. Browser settings can restrict third-party storage, although this may affect the selected feature.

5.3The optional tools disclosed in this version are listed below. GA4 analytics, PostHog and Clarity operate after Analytics consent; Meta Pixel and Reddit Pixel operate after independent Advertising consent. Google Tag Manager manages configured tags subject to the choice applicable to each purpose. The table identifies tool roles, storage families and deployed Meta and Reddit domains. Sections 2.6, 3.8 and 3.8(a) describe the applicable permission requirements.

Google Tag Manager

Google

Google Analytics 4

Google

PostHog

PostHog Inc. where hosted

Microsoft Clarity

Microsoft

Meta Pixel

Meta Platforms

Reddit Pixel

Reddit

5.4Cookie settings currently shows the Analytics and Advertising categories, category descriptions and two independent switches. It is not a per-tool panel displaying provider status, domains, storage keys or retention periods. The provider and technology information is supplied through this policy and any supplementary cookie notice, which must be readily accessible from the consent notice before a choice is made. Where needed for informed consent, that information must identify the deployed purposes, recipients, storage technologies and their actual durations, including renewal. Configured values, hosting or proxy domains and additional identifiers must not be inferred from a vendor default. Persistent local storage has no automatic browser expiry unless the site or tool clears it. Serving a provider script or event endpoint from a QATS domain does not remove consent or recipient-disclosure requirements.

5.5Browser lifetimes and server retention are separate. Optional information is kept only for the disclosed purpose and the applicable retention period or criteria. Google publishes a two-year default for the _ga and _ga_<id> cookies, but cookie lifetime and renewal can be configured; that default is not a statement of QATS's actual settings. Standard GA4 user and event retention can be set to two or fourteen months, with longer options for certain Analytics 360 event data; the selected period, reset-on-activity setting and any separate exports must be assessed. That GA4 setting does not govern all standard aggregated reports. QATS must disclose its configured GA4 and PostHog retention in the applicable published notice. Microsoft publishes 30 days for ordinary Clarity playback and nine months for labelled or favourited sessions and for click and heatmap data. Meta's _fbp and _fbc and Reddit's _rdt_uuid and _rdt_cid cookies end at configured expiry, earlier browser deletion or Advertising withdrawal under Section 3.3. The published cookie notice must identify their actual expiry and renewal settings. Meta's server retention follows its Privacy Policy and applicable Business Tools Terms. Reddit's recipient-side retention follows its applicable notice and terms. Provider periods do not extend QATS's lawful purpose or override a deletion requirement. Removing a browser identifier does not itself delete server data.

5.6QATS determines its purposes for these tools and remains responsible for collection and disclosure. Google processes GA4 customer data under the applicable Analytics and data-processing terms; optional data sharing and advertising integrations can involve additional Google uses governed by their corresponding terms and permissions. Google Tag Manager is the tag-management layer, not a substitute for identifying GA4 as a recipient service. Where PostHog is hosted by PostHog Inc. or a contracted affiliate, it processes customer event data for QATS under the applicable processing agreement; the actual hosting arrangement and region must be disclosed in the Privacy Policy or supplementary notice. Microsoft's Clarity terms treat QATS and Microsoft as independent controllers and permit further uses under the Microsoft Privacy Statement, including product improvement, analysis and advertising profiles. Advertising sharing through Clarity is also affected by its consent settings and must not be enabled solely by Analytics consent. Meta receives Pixel data under its applicable Business Tools Terms and Privacy Policy and may combine it with other information for measurement and permitted advertising and product purposes. Reddit receives the Pixel information described in Sections 3.8 and 3.9 for attribution and measurement and may use it for its disclosed advertising purposes. Loading a provider script can disclose connection information. A provider's independent role does not release QATS from notice, valid-consent, security or rights-handling obligations.

5.7These services may process information outside Israel, including in the United States or other countries identified for the deployed service. QATS uses a valid transfer route and the required recipient undertakings and safeguards under applicable Israeli law. Where EEA or UK transfer rules apply, the relevant adequacy decision or appropriate safeguards, such as applicable standard contractual clauses and UK transfer instruments, must cover the transfer, with additional safeguards where required. Optional tracking consent is not a substitute for those transfer requirements. The Privacy Policy provides the relevant transfer information; contact support@qats.us to request details of the safeguards.

5.8Provider notices supplement this policy and are available through the following links. Google's business-data notice also explains collection and processing through services such as GA4. Provider links do not replace QATS's prior notice or your choices:

Google Privacy Policy; PostHog Privacy Policy; Microsoft Privacy Statement; Reddit Privacy Policy. Meta Privacy Policy; Meta Cookies Policy; Meta Business Tools Terms.

Google business data notice; Google Analytics opt-out browser add-on.

6Control deletion and policy updates

6.1Use the independent Analytics and Advertising switches in Cookie settings. Analytics consent does not enable Advertising. Advertising withdrawal stops Meta Pixel and Reddit Pixel and deletes _fbp, _fbc, _rdt_uuid and _rdt_cid under Section 3.3. You can also delete or block storage through browser controls; doing so may sign you out, clear preferences or interrupt a requested feature. Deleting local storage does not cancel an order, reverse a transaction, close an account or erase all server records. Browser session restoration may preserve some session storage after a window closes. Google's Analytics opt-out browser add-on is an additional Google-specific control; it does not turn off PostHog, Clarity, Meta Pixel, Reddit Pixel or either QATS category.

6.2Under EEA and UK rules where applicable, permission or an exception for device storage is a separate question from the legal basis for subsequent personal-data processing. A legitimate interest alone does not replace device consent where consent is required. QATS uses affirmative consent for the optional purposes described here, even where a narrower statutory exception might be available in a particular jurisdiction. Optional collection is voluntary: you are not legally required to provide it, and refusal leaves ordinary service access available. Processing is subject to the Israeli Protection of Privacy Law, 5741-1981, as amended, and other privacy laws to the extent they apply to the relevant processing.

6.3We update this policy and inventory when purposes, recipients or technologies change. A new version does not turn a refusal into agreement or retrospectively authorise collection. Before a materially new purpose or recipient is activated, QATS must update the notice and controls and obtain any required fresh consent. A choice under an earlier notice does not authorise a newly disclosed recipient or purpose. In particular, earlier Analytics acceptance does not authorise Meta Pixel or Reddit Pixel; Advertising permission must cover the disclosed advertising recipient and purpose. If Cookie settings is unavailable or does not apply your choice, contact support@qats.us; browser controls can also block or clear storage. The Privacy Policy explains rights requests and complaints, including regulatory routes.

6.4Contact support@qats.us to request access to, correction or deletion of information collected through these technologies, or to exercise other applicable privacy rights. In Israel, the statutory rights include inspection under Section 13 and correction under Section 14 of the Protection of Privacy Law. Additional rights, including deletion, restriction, objection or portability, apply where the relevant law provides them. Where withdrawal requires erasure of consent-based information, QATS treats it accordingly and notifies relevant recipients as required. We may request only proportionate information needed to identify the relevant data and handle the request. You may complain to the Israeli Privacy Protection Authority or another competent data-protection authority. Mandatory rights are not waived by accepting this policy.

6.5Where applicable privacy laws provide a right to opt out of targeted advertising or the sale or sharing of personal information, QATS must honour that right, including a recognised opt-out preference signal such as Global Privacy Control where legally required. Advertising-related disclosures can fall within those concepts even without a monetary payment. Turning the Advertising switch off and contacting support@qats.us are available routes; a Do Not Sell or Share My Personal Information control must also be provided where required. Creating an account is not required to exercise that opt-out. A required opt-out is not overridden by general optional-cookie acceptance. The Privacy Policy describes the applicable rights and request procedures.