Cookies and consent.
You can browse RUXDEN music releases and send a music licensing inquiry without allowing advertising storage. Paid clicks still reach this digital music catalogue. This notice explains what the choice changes and what remains necessary.
Storage is not one category.
A cookie is a small record stored by a browser and sent with relevant requests. Local storage also keeps information in the browser, but it does not send that information automatically in the same way. This notice covers both. A parameter attached to an advertising link is different again: it can be present in the address you opened before anything is stored.
Strictly necessary storage remembers whether you declined or allowed optional storage, and supports returning to a support conversation you chose to start. Keeping a refusal is part of respecting it. The chat token is functional storage for that conversation, not an advertising preference or an account password.
Analytics storage supports measurement of visits and interactions so that traffic and inquiry activity can be understood. It is optional. Advertising storage supports click attribution and advertising measurement; the related user-data and personalization signals control those advertising uses. These permissions do not turn the contents of your licensing brief into public promotional copy.
Necessary server processing remains separate from optional browser storage. The server needs request information to deliver a page, investigate a fault, and receive an inquiry. For the legal basis of each purpose and the complete record categories, read the privacy notice's legal-bases section.
The known records have different lifetimes.
The table distinguishes a browser key from a server record and a link parameter. It does not pretend that every visitor receives the same set of platform cookies. Platform storage depends on the storage choice and the advertising service involved. A click identifier is not itself a cookie name.
| Name or record | Who sets it / purpose | Lifetime |
|---|---|---|
site_consent_v2 | RUXDEN. Browser record of the visitor's allow or decline choice; necessary to apply that choice. | 12 months. You can remove it using browser site-data controls. |
ruxden_chat_token | RUXDEN chat. Stored in the browser so a returning visitor can reconnect to the same conversation. | Browser storage persists until cleared; no separate fixed token expiry is stated. The server transcript is retained for 12 months. |
gclid | Google Ads. Link parameter used to identify a Google advertising click, rather than a cookie set by the catalogue. | No independent browser expiry for a URL parameter. If captured in a site record, that record's retention applies. |
msclkid | Microsoft Advertising. Link parameter associating a visit with a Microsoft advertising click. | Present in the URL containing it. Server record retention and Microsoft's own handling are separate. |
fbclid | Meta Ads. Link parameter identifying a click from Meta traffic. | Present in the URL containing it. A copied link can retain the parameter; platform-held data follows Meta's policy. |
The 12-month consent period concerns the site's choice record. It is not an expiry promise for all Google, Microsoft, or Meta records. For a cookie you see in browser settings, send its name and domain to RUXDEN rather than assuming that it is the same as an advertising click parameter.
An inquiry's referring URL can contain a click identifier. Inquiries and their email copies are retained for 36 months; server and access logs are retained for 30 days. Those periods explain why clearing the address bar or deleting a browser cookie does not erase a submitted record.
Advertising links arrive with identifiers.
Google Ads, Microsoft Advertising and Meta Ads send traffic to ruxden.com. Google attaches gclid, Microsoft attaches msclkid, and Meta attaches fbclid to their advertising links. The google ads identifier records the click context, not a person's written brief. The same distinction applies to the other platforms.
Google Ireland Ltd / Google LLC receives Google Ads consent signals. Microsoft Ireland Operations Ltd handles Microsoft Advertising data. Meta Platforms Ireland Ltd handles Meta Ads data where a campaign runs there. A click through a platform can involve that platform's own records before the visitor reaches this site.
The site's choice governs its optional storage and signals. It does not change the privacy settings of a separate Google, Microsoft, or Meta account. Use the provider links below for those controls, including their retention and international processing information.
Four signals follow the storage choice.
Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until the visitor allows storage. It sets all four back to denied the moment the visitor declines or withdraws. This consent mode state is the starting point, not a permission inferred from scrolling or opening another page.
| Signal | Scope |
|---|---|
ad_storage | Storage associated with advertising, including advertising cookies. |
ad_user_data | Consent for sending user data for advertising purposes. |
ad_personalization | Consent for personalized advertising uses. |
analytics_storage | Storage associated with analytics and visit measurement. |
A denied signal is not the same as severing the network connection. Limited consent and measurement signals can still be transmitted under a denied state without permission to write optional storage. The claim here is specific: optional storage and the associated advertising permissions remain denied until allowed, and return to denied on refusal.
Global Privacy Control, supplied in the Sec-GPC header, is honoured as an opt-out without asking again. That browser-level instruction concerns sale or sharing and targeted advertising where applicable. It is not a request to delete a conversation, and it does not prevent you from sending a music licensing inquiry.
Your choice is reversible.
Choose “Allow storage” in the cookie banner to permit optional storage. Choose “Decline” to refuse it. Both controls are available without signing in, and you do not have to submit a music inquiry to make the choice. The browser stores the result under site_consent_v2; this site does not keep a second consent-choice key.
To change or withdraw permission, go to the legal row in the footer of any page, select “Cookie settings,” then select “Decline.” The four Consent Mode v2 signals are set back to denied immediately. Withdrawing does not undo processing already performed lawfully before withdrawal.
On a shared device, the stored choice belongs to that browser. A different browser or a new device may not carry it. Clearing site data removes the saved choice and can also remove the chat token. The next visit starts with optional storage denied; a recognized Global Privacy Control opt-out is respected without another request for permission.
Browser controls can block or delete cookies independently of this site's banner. Deleting an identifier from a device is not the same as requesting deletion of server-held information. If you want both, change the browser setting and make a data request.
Declining does not close the site.
The digital music catalogue remains readable. Release notes and the contact form remain available, as do email and phone. There is no cookie wall and no purchase flow to lose. RUXDEN offers an inquiry route, not a cart or checkout.
Optional advertising and analytics storage are not allowed after refusal, and the four advertising and analytics consent signals remain denied. Necessary processing of a form you choose to send still occurs. Refusing storage does not remove your name from a message already delivered or erase the referring URL already attached to it.
The support chat keeps a functional token only for returning to the conversation you open. If you block all local storage, that return function may be unavailable. Email remains an alternative. The form's required consent concerns answering the inquiry; it does not overrule a refusal of advertising storage.
Provider policies cover their own records.
These links lead away from ruxden.com. Read the policy for the platform whose cookie or identifier you are asking about. RUXDEN's consent controls do not act as an account-setting screen for those services.
- Google privacy policy at policies.google.com covers Google's handling, including its advertising services.
- Microsoft privacy statement at privacy.microsoft.com explains Microsoft Advertising and Microsoft's wider personal data practices.
- Meta privacy policy explains Meta's handling of advertising and other service data.
- Google's cookie technology notice provides additional detail about cookies and related technologies.
The hosting provider serves the site and stores the inquiry database. The mail provider delivers the inquiry notification to RUXDEN's inbox. Those operational roles are distinct from the advertising platforms. The site's Google Fonts requests also involve Google's delivery infrastructure and ordinary technical request information.
RUXDEN's recipient and transfer disclosures explain the limits of the information available about providers. Ask for the recipient relevant to a particular record rather than sending a full browser history.
Ask about the record you can see.
Email office@ruxden.com with the cookie or storage name, the domain shown in browser settings, and whether you selected allow or decline. You can also call +1 (871) 555-5442. Do not send the contents of a chat token or a complete URL containing private information.
The operator is Ruxden, trading at ruxden.com. Postal address: 21 Station Road, Floor 2, Austin, Texas 72864, Austin, Texas, United States. For access, correction, deletion, or a request about sharing, use the data request page. A data request is answered within 10 days.
If you cannot operate the cookie controls, describe the page and the barrier by email or phone. The accessibility statement provides another route to report the problem. You do not need to disclose a medical condition. For the distinction between an inquiry and permission to use a track, read the terms of use.