Privacy notice.

01 / The controller.

Ruxden, trading at ruxden.com, operates this website under the RUXDEN name. RUXDEN is an independent music project with an inquiry-only digital release catalogue. The controller's full postal address is 21 Station Road, Floor 2, Austin, Texas 72864, Austin, Texas, United States.

This notice applies to browsing RUXDEN music releases, sending a form, and using support chat. There is no account, password, payment, or card data collected through a purchase flow. Nothing is sold on this site and no payment is taken. A licensing conversation is not a completed transaction.

02 / What is recorded.

The inquiry form receives your name, phone, email, address, kind of inquiry, message, requested specification, and consent tick. Name and consent are required. Phone and email are optional individually, but at least one reply route is needed. You choose what to write in the message and specification fields.

The form also records the IP address, browser user-agent string, referring URL, the moment the form was rendered, and the moment it was sent. The page source field identifies the inquiry route. Server and access logs record requests and technical information needed to serve the site.

Support chat keeps the conversation and a token in your browser so you can return to it, together with the contact details you supply. Browser storage records consent under site_consent_v2. Advertising links carry click identifiers including gclid, msclkid, and fbclid; identifiers in a referring URL can form part of that URL's record.

03 / What each record does.

Contact details let RUXDEN answer the person who sent a music collaboration inquiry or licensing brief. The inquiry kind and specification help distinguish a request for an edit from a question about release use. The message is the working context, not permission to use your material outside that conversation.

Technical records support delivery, fault investigation, and protection against automated or abusive submissions. The chat token connects a returning browser to its conversation. The consent record keeps the visitor's storage choice separate from their inquiry consent. Advertising identifiers and permitted measurement help attribute paid visits and understand which campaigns lead to inquiries.

04 / Grounds for processing.

For visitors covered by European data protection law, the basis depends on the purpose. A required form tick acknowledges and authorizes handling the inquiry; it does not turn every later use into consent-based processing.

You may object to processing based on legitimate interests. RUXDEN must consider that objection rather than treating a previous inquiry as blanket permission.

05 / Paid traffic.

Google Ads, Microsoft Advertising and Meta Ads send traffic here. Google Ads links carry gclid; Microsoft Advertising links carry msclkid; Meta Ads links carry fbclid. These values identify an advertising click. They are not the text of your music inquiry.

The google ads and microsoft advertising click parameters can appear in a page or referring URL even when you refuse optional storage. A refusal changes the permitted storage and advertising signals; it does not rewrite the link already used to arrive here. Do not put private project details in a URL. The cookie notice explains the distinction between a click parameter and a stored cookie.

06 / Storage starts denied.

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. These consent mode signals govern advertising storage, advertising user data, personalization, and analytics storage respectively.

Selecting “Allow storage” in the banner gives that permission. “Decline” leaves the optional signals denied. Open “Cookie settings” in the footer to change the choice. Inquiry consent is separate: you can decline ad measurement storage and still ask about a release. Denied storage is not a claim that every network request or limited consent signal stops.

07 / Who receives data.

Google Ireland Ltd / Google LLC operates Google Ads, attaches gclid to a click, and receives consent signals. Microsoft Ireland Operations Ltd operates Microsoft Advertising, which attaches msclkid; its handling is described at privacy.microsoft.com, Microsoft privacy statement. Meta Platforms Ireland Ltd operates Meta Ads, which attaches fbclid where a campaign runs there.

The hosting provider serves this site and stores the inquiry database. The mail provider carries notifications to the operator's inbox. Those providers receive the technical or inquiry data needed for those functions; their company names are not supplied in this notice. You can ask RUXDEN about the provider relevant to a particular record.

The typography is delivered through Google Fonts, so a font request also exposes ordinary request information to Google. Advertising platforms handle data under their own policies as well as the signals sent by this site. An inquiry is not permission to publish your message in an advertisement.

08 / Processing across borders.

RUXDEN operates in the United States. A visitor outside the United States sends inquiry data to an operation in another country, and the named advertising providers can process information across borders. The exact processing location depends on the recipient and the service used, not just the country shown in a company's name.

Where European transfer rules apply, a transfer requires a lawful mechanism, such as an applicable adequacy decision or standard contractual clauses with required safeguards. This notice does not assert certification or a particular provider's eligibility for a transfer framework. Ask RUXDEN for the mechanism and safeguards relevant to your record before sending material that needs a specific geographic restriction.

09 / Retention periods.

Inquiries and their email copies are retained for 36 months. Chat transcripts are retained for 12 months. Server and access logs are retained for 30 days. The record of a consent choice is retained for 12 months. These are separate records: closing chat does not delete its transcript, and declining storage does not delete an inquiry already sent.

A click identifier held inside an inquiry's referring URL follows the inquiry record's 36-month period; one present in an access log follows the 30-day log period. Platform-held records follow the platform's retention rules. Browser-held chat tokens can be removed using browser site-data controls; clearing a token removes that browser's return route, not the server's conversation record. Ask for deletion when you want the stored record considered as well.

10 / Protecting an inquiry.

The public site uses HTTPS. Inquiry forms check submitted fields and include timing and hidden anti-spam fields to help distinguish an ordinary inquiry from automated submission. The support conversation uses a token rather than a public conversation link. Treat that token and any shared device as a route into the conversation.

No transmission or storage system offers absolute security. Do not send account passwords, card details, identity documents, or material that reveals someone else's private information. If you sent the wrong material, contact RUXDEN with enough context to identify the message, rather than sending it again in a second channel.

11 / Rights for European visitors.

Where the GDPR applies, you can request access to personal data and a copy, rectification of inaccurate or incomplete information, erasure, restriction of processing, and portability of eligible data. You can object to processing based on legitimate interests and to direct marketing. You can withdraw consent at any time without affecting the lawfulness of processing before withdrawal.

These gdpr rights depend on the processing involved. Portability concerns qualifying automated processing based on consent or contract; it is not a demand for another person's correspondence. A request can be limited where law requires retention or another person's rights need protection. RUXDEN explains a limitation rather than silently dropping the request. Use Data request for any of these rights.

12 / US state privacy rights.

US state privacy law applies, including California's CCPA/CPRA and other state laws in force to the extent they cover your situation. Eligible residents can request information about collection and disclosure, access, correction, deletion, and a portable copy. You can opt out of sale or sharing of personal information and targeted advertising where those rights apply.

Advertising disclosures can fall within a state's definition of sharing even without a payment for data. For ccpa requests and comparable state rights, use the data request route or write directly. You may use an authorized agent, subject to checks appropriate to the request. RUXDEN does not penalize a visitor for exercising a privacy right. If a request is refused, ask for the reason and an appeal where the applicable state law provides one.

13 / A browser opt-out counts.

Global Privacy Control, sent through the Sec-GPC header, is honoured as an opt-out without asking again. This global privacy control signal communicates a refusal of sale or sharing and targeted advertising where applicable. It is not an instruction to erase a music inquiry you have already sent.

Use browser settings or a supporting browser extension to send the signal. For a request about records outside the current browser, contact RUXDEN. An opt-out on one device does not identify an unrelated browser or remove a platform's independently held records.

14 / Not a children's service.

This site is not directed to children and does not knowingly collect personal data from children. The inquiry routes are for people discussing music use or their own work. Do not submit a child's contact details or private information through a project brief.

If a parent or guardian believes a child has sent personal data, email RUXDEN with the relevant conversation or submission context. RUXDEN uses that information to locate and remove the child's data rather than asking the child to continue the conversation.

15 / You can complain elsewhere.

You may complain to your state Attorney General. In California, you may also complain to the California Privacy Protection Agency. Visitors covered by European law have the right to complain to a competent data protection authority, including the authority where they live or work or where they believe an infringement occurred.

Contacting RUXDEN first can help resolve a record error, but it is not a condition of approaching an authority. Keep the relevant dates and the substance of the request. There is no need to send a complete private project brief to explain a cookie-choice problem.

16 / Request a record or a correction.

Use the data request form or email [email protected]. A data request is answered within 10 days. State the right you want to exercise and a reply route associated with the inquiry where possible. You do not need to know the name of a law to ask for access or deletion.

RUXDEN may need proportionate information to confirm that a record belongs to you before disclosing it. Do not send an identity document with the first request. The response explains the action taken or any information needed to proceed; answering within 10 days does not mean releasing records to an unverified requester. A postal request can be sent to 21 Station Road, Floor 2, Austin, Texas 72864, Austin, Texas, United States.

17 / Changes remain visible.

RUXDEN announces revisions by publishing the updated notice here and changing the effective and last-updated date at the top. A change that needs fresh consent is not authorized merely because this text changes. The storage choice remains a separate control.

Check this notice when making a new inquiry if the handling matters to your project. For an explanation of a change affecting a previous submission, quote its approximate date and the reply address used, without copying the whole submission into the request.

18 / Reach the operator.

Privacy questions reach a person at RUXDEN through [email protected] or +1 (871) 555-5442. Postal contact: 21 Station Road, Floor 2, Austin, Texas 72864, Austin, Texas, United States. Say that the question concerns privacy so it is not mistaken for a licensing brief.

For a music question, the contact page keeps the inquiry fields together. For a specific advertising cookie or stored choice, the cookies and consent notice gives the browser controls and provider links.

19 / An accessible request route.

You can ask about data without using chat, opening an animation, or accepting optional storage. If a form is difficult to operate, email or phone is an alternative. The accessibility statement covers keyboard use, reduced motion, image descriptions, and reporting an access barrier.

Describe the page and what prevented you from completing the request. Include the browser or assistive tool if useful, but do not disclose medical information to explain an access need. RUXDEN can discuss an accessible format for the response through the same human contact route.

20 / Records are not music rights.

This notice governs personal data, not permission to copy or publish a track. The terms of use explain the inquiry-only catalogue. For a use brief, see music licensing inquiries; for proposed shared work, see collaboration briefs.