Cookies & Storage Choices

You can read about remote administrative support and send a task inquiry without allowing optional advertising or analytics storage. This notice separates that optional storage from the preference record and the conversation token needed when you ask to use chat.

01 / Storage categories.

Strictly necessary storage supports a function you request or remembers a privacy instruction. The consent preference records whether optional storage is allowed. The functional chat token is created when you initiate a conversation, so the same browser can return to it. Starting a chat is not a requirement for reading the service pages.

Analytics is an optional category used for measuring site activity. Advertising is an optional category used to relate visits to paid campaigns and support permitted advertising measurement or personalization. Those categories are held denied before permission; they are not made necessary merely because this website receives advertising traffic.

“Cookies” is used here as a familiar label for browser storage. Local storage is different from a cookie: it is held by the browser for the site rather than automatically attached to every request. The distinction matters when removing data. A browser's cookie-only deletion command may not clear all local storage.

02 / Paid-click identifiers.

Google Ads, Microsoft Advertising and Meta Ads send traffic to opryq.com. A Google link can include gclid; a Microsoft link can include msclkid; a Meta link can include fbclid. These are click identifiers, not names that you type into the inquiry form.

The Google Ads identifier can appear in a landing URL before a visitor interacts with the banner. The Microsoft Advertising identifier and the Meta Ads identifier follow the same rule. Arrival with a parameter does not grant permission to persist it. Optional click identifiers are not stored before consent.

A parameter in an incoming address, an optional browser identifier and a server log are different records. Technical request information can reach the server to deliver the page. A referring URL recorded with an inquiry can contain query information. The Privacy Notice explains those submission records; they are not a claim that optional storage is always necessary.

04 / Decline and withdrawal.

After you decline, the service directory and the task descriptions remain readable. You can use the inquiry form or contact Opryq directly. Requested chat can still use its functional conversation token. Optional advertising and analytics storage is not enabled, and optional identifiers are no longer persisted under the withdrawn permission.

Withdrawal changes the current consent state; it cannot recall information already received by another party under an earlier permission. Clear browser site data to remove remaining browser-held records, and use the data request route for records held by Opryq. A browser deletion is not a deletion request for an inquiry in the operator's inbox.

Global Privacy Control is honored. The Sec-GPC header is treated as an opt-out without asking again. A global privacy control signal does not stop a requested service discussion. Your browser or device may need its own setting, so a choice in one browser should not be assumed to configure every other one.

05 / Returning to a chat.

The support chat stores a conversation token in localStorage only when a chat is initiated. It allows the browser to reconnect to the conversation. While the widget is open it checks for new messages every five seconds; closing it stops that polling. Closing the panel does not remove the token.

On a shared computer, another person using the same browser profile may be able to reopen the conversation. Remove the site's local storage when you no longer want that browser to have access. The token is not an advertising identifier, and declining optional storage does not erase a requested chat.

The browser token and the transcript have different lifetimes. Chat transcripts are retained for 12 months. A local token can remain until browser data is cleared; its presence does not extend retention of the server-side conversation. Losing a token can also mean losing the browser's route back to an existing chat.

06 / Workload links are not cookies.

The workload planner puts selected tasks and your entered quantities into a shareable URL. It does not put inquiry contact details in that URL. Anyone with a link can see the task configuration, so use it for a workload outline rather than confidential descriptions.

Browser history and copied links can keep a configuration even after site storage is removed. Deleting cookies does not remove a link from somebody else's messages. The homepage task lookup works locally and does not store the search query in a URL.

Browser storage inventory

Names, purposes and lifetimes

The site's own preference and functional storage, with paid-click identifiers distinguished from cookie names
Name or item	Who sets it and why	Permission	Lifetime and removal
`site_consent_v2` Consent preference	Opryq stores the browser's allow or decline choice. This is the site's only persistent consent-choice key.	Necessary to apply the choice. It records a refusal as well as an allowance.	The record of a consent choice is retained for 12 months. Change it through Cookie preferences or remove it with browser site-data controls.
`site_chat_token` Functional conversation token in localStorage	Opryq's support chat stores the token returned when you initiate a conversation, so that browser can reopen it.	Requested chat functionality, separate from optional advertising and analytics permission.	Remains in the browser until its storage is cleared. Server-side chat transcripts have a 12-month retention period; the token does not extend it.
`gclid` Google click identifier	Google Ads attaches it to a paid link. Opryq's optional attribution handling associates an allowed identifier with the visit.	No optional persistence before Allow storage. It is not the name of a guaranteed Google cookie.	Can exist in the incoming URL independently of browser storage. Withdraw to stop optional persistence and use browser controls to remove existing site data. Google explains its own retention.
`msclkid` Microsoft click identifier	Microsoft Advertising attaches it to a link to identify the paid click for advertising measurement.	Optional storage depends on permission; presence in a URL is not consent.	No fixed cookie expiry is represented by this parameter name. Browser-held data can be cleared; Microsoft describes retention of information it receives.
`fbclid` Meta click identifier	Meta Ads attaches it where a campaign sends the visitor to this destination.	Optional persistence is denied until storage is allowed and stops on withdrawal.	The landing parameter and any browser-held data are distinct. Clear site data for local removal; Meta's notice covers its processing and retention.
Optional analytics storage Consent category	Site measurement operates under the `analytics_storage` state. This row describes a category, not an asserted cookie key.	Denied before permission and when declined or withdrawn.	Browser controls show individual stored items and any browser-reported expiry. This notice does not assign an invented shared expiry to platform storage.

The functional conversation key is site_chat_token; the preference key is site_consent_v2. Neither is an advertising identifier. Click parameters are listed separately because they identify paid visits, not cookie names. The consent key has no automatic browser expiry in the current implementation. You can replace the choice using these controls or remove it through browser site-data settings.

07 / Platform privacy documents.

Google Ireland Ltd / Google LLC handles Google Ads information and receives consent signals. Read policies.google.com/privacy for Google's processing, including retention and international handling. The Google cookie explanation describes the purposes of its technologies.

Microsoft Ireland Operations Ltd handles Microsoft Advertising information. Its notice is at privacy.microsoft.com/privacystatement, with an English-language Microsoft Privacy Statement available. Microsoft describes its own use of information received through its advertising services.

Meta Platforms Ireland Ltd handles Meta Ads information where a campaign runs there. Read Meta's Privacy Policy and Meta's Cookies Policy. Leaving this site for a platform policy does not transfer your Opryq consent choice into that platform's account settings.

These links explain recipients' practices. They do not replace Opryq's responsibility for the choices and records on this destination.

08 / Browser removal.

Open the browser's privacy or site-data settings and find opryq.com. Review cookies and local storage, then remove the items you want cleared. Menu names differ by browser; look for site data rather than assuming that clearing only browsing history removes storage too.

Removing site_consent_v2 removes the browser's saved choice. On a later visit, the site may need a new choice, with optional consent states denied in the meantime. Removing the chat token can prevent that browser from returning to the same conversation. Neither action deletes an inquiry already stored by Opryq.

Private browsing may clear site data when the private session ends. It does not undo information already submitted through a form, and it does not guarantee that paid-link parameters never reach a server. For an earlier inquiry, use a privacy request rather than a browser cleanup as a substitute.

09 / Records outside the browser.

Enquiries and their email copies are retained for 36 months. Chat transcripts are retained for 12 months. Server and access logs are retained for 60 days. The record of a consent choice is retained for 12 months. These periods describe different records; none means that a cookie deletion erases everything associated with a visit.

To ask about a record, use the data request page. A data request is answered within 7 days. You can request access or deletion without allowing optional storage. The Privacy Notice's retention clause explains the purpose of each period and the handling of applicable legal exceptions.

10 / Ask about a specific item.

Write to [email protected] or call +1 (762) 555-0721. Tell us the storage item's name, the browser and the page where you noticed it. Do not send the token's value, a complete tracking identifier or a screenshot that exposes a conversation.

Opryq, trading at opryq.com, can also be reached at 42 Market Street, Büro 5, Austin, Texas 28921, Austin, Texas, United States. This is a contact address for a remotely delivered service.

If a control is difficult to use, the accessibility page gives alternative contact routes. Questions about the status of an administrative inquiry belong with the Service & Website Terms; a cookie preference does not create or cancel a service agreement.