Here's exactly what QUEUE STUDIO collects, keeps and deletes, and for how long.

When this took effect

This policy took effect on September 14, 2026 and applies to the site live at siruhewu.com from that date. Anything you submitted before that date is handled under the same categories, purposes and retention periods described below; nothing about the studio's practices changed on that date, we simply wrote them down in this form.

Who operates this site

Siruhewu operates siruhewu.com and trades under the name QUEUE STUDIO. The business is based at 131 Station Road, Austin, Texas 08122, United States, and that is the address anything written to us in the mail should reach. QUEUE STUDIO is the controller for every category of data described on this page: we decide what's collected and why, rather than handing that decision to a third party.

What we actually collect

The inquiry form on the homepage asks for name, phone, email, address, the kind of engagement you're asking about, your notes, and the specification you'd like scoped, along with a tick confirming you consent to being contacted about it. Two hidden fields on that form, named company and website, are honeypots visible only to automated form-filling scripts; a human never sees or fills them, and anything submitted through them is treated as spam and discarded.

The support chat, when you open it, records the body of each message you send, and optionally the name, phone, email and consent tick you give it at the start of a conversation. A token identifying that conversation is stored in your browser's local storage so the thread survives a reload.

Every visit, regardless of whether you fill in a form, generates technical and log data: your IP address, your browser's user-agent string, the page that referred you, and the timestamps for when a page rendered and when anything on it was submitted. A cookie identifier, site_consent_v2, records your storage choice. If you arrive from a paid ad, the platform that sent you appends a click identifier to the landing link: gclid from Google Ads, msclkid from Microsoft Advertising, or fbclid from Meta Ads.

Why we collect each of those

Form data exists to let us reply to a real inquiry and scope a real job — we can't return a call to an address we were never given. Chat data exists so a conversation can continue if you close the tab and come back. Technical and log data exists to keep the site running, to catch abuse of the form, and to work out why a page broke if one ever does. The cookie identifier exists purely to remember the choice you made about storage, so we don't ask you twice. The advertising click identifiers exist to tell Google Ads, Microsoft Advertising and Meta Ads which of their ads actually produced a visit, which is how those platforms bill correctly and how we know which campaign is worth the spend.

The legal basis for each of those

We rely on consent for anything that isn't strictly necessary to run the site: the chat widget's optional contact details, the advertising click identifiers, and the analytics and advertising storage signals described below. We rely on contract, or the steps toward one, for the inquiry form: you're asking us to prepare a quote or a scope, and we need your contact details to do it. We rely on legitimate interest for server and access logs and for the honeypot fields, because keeping a site secure and readable is a legitimate interest that doesn't require asking permission first, and it's limited to what security actually needs.

The advertising platforms sending traffic here

This site runs paid traffic today from Google Ads and Microsoft Advertising, and may run it from Meta Ads. Each platform appends its own click identifier to the link a visitor follows, and on this page we refer to each platform by the lowercase name its own documentation uses next to that identifier: gclid comes from google ads, msclkid comes from microsoft advertising, and fbclid comes from Meta Ads. None of these platforms has reviewed, approved or verified this site; naming them here is a disclosure of how they measure a click, not a claim of endorsement.

Consent mode and what it holds back

We run Google's consent mode, version two. Four signals — ad_storage, ad_user_data, ad_personalization and analytics_storage — are held denied by default on every page load. They stay denied until you actively allow storage through the cookie banner. If you decline, or later withdraw an earlier "allow," all four signals are set back to denied immediately, not at the end of a session and not on your next visit.

Who receives this data

Google Ireland Ltd and Google LLC operate Google Ads and receive the consent signals and the gclid identifier tied to a click. Microsoft Ireland Operations Ltd operates Microsoft Advertising and receives the msclkid identifier; how it further handles that data is described in the Microsoft privacy statement at privacy.microsoft.com/privacystatement. Meta Platforms Ireland Ltd operates Meta Ads and receives the fbclid identifier where a campaign runs there. Beyond the ad platforms, two other parties touch this data in the ordinary course of running the site: the hosting provider that serves these pages and stores the enquiry database, and the mail provider that carries the form notification into our inbox. None of them may use your data for a purpose of their own.

Data leaving the country where you gave it

Our hosting sits inside the United States. Where a click identifier or a consent signal reaches Google, Microsoft or Meta, it may be processed on servers in Ireland, other parts of the European Union, or elsewhere those companies operate, and then may move back toward the United States as part of normal ad-serving infrastructure. Each of those platforms publishes the standard contractual clauses or equivalent safeguard it relies on for that movement; we do not run our own separate transfer mechanism on top of theirs, because we are not the party moving the data across that particular border — they are, under their own published terms.

How long each category actually stays

Inquiry messages and the email copy they generate: 18 months from the date you sent them, then deleted. Chat transcripts: 12 months from the last message in the thread. Server and access logs: 90 days on a rolling basis. The record of your cookie consent choice: 12 months, after which the banner simply asks again. We don't keep any of these "as long as necessary" in the abstract; these are the actual numbers, and we delete on schedule rather than waiting to be asked.

How it's protected

Every page on this site is served over an encrypted connection. The inquiry database and chat transcripts sit behind access controls limited to the four people who work at QUEUE STUDIO — there's no separate support team or contractor pool with a login. The two honeypot fields on the inquiry form catch a large share of automated submission attempts before they ever reach a human inbox. We don't store payment details or passwords anywhere on this site, because nothing on it is sold or logged into.

Rights for visitors covered by the GDPR

If you reach this site from the European Union or another jurisdiction covered by the gdpr, you have the right to access the data we hold on you, to have it corrected if it's wrong, to have it erased, to have its processing restricted, to receive it in a portable format, to object to processing based on legitimate interest, and to withdraw consent at any time with no effect on anything done before the withdrawal. None of these rights costs anything to exercise.

Rights for visitors in the United States

If you're a California resident, the ccpa and its amendment, the CPRA, give you the right to know what we've collected about you, to have it deleted, to correct it, and to opt out of the sale or sharing of your personal information. QUEUE STUDIO does not sell personal information and does not share it for cross-context behavioural advertising beyond the ad platforms already named on this page. Residents of other states with comparable privacy laws in force have equivalent rights under those laws; write to us and we'll apply whichever standard covers you.

Global Privacy Control

If your browser sends the Sec-GPC signal, we treat it as global privacy control and honour it as an opt-out of any sale or sharing of your data automatically, without making you find and click a separate toggle on this site first.

Children

This site is built for adults working on gaming and esports products and is not directed at children. We don't knowingly collect data from anyone under 13, and if we learn that we have, we delete it.

Where to complain if you're not satisfied

You can complain to your state Attorney General, and if you're a California resident, to the California Privacy Protection Agency. If you reached this site from the European Union, you can complain to your own country's data protection authority. Complaining doesn't require contacting us first, though we'd rather hear it first if you'll let us try to fix it.

How we announce a change to this policy

When this policy changes, the "Last updated" date at the top of this page moves to the date of the change. A change that affects what we collect, who we share it with, or how long we keep it gets its own short note added to this section describing what moved, rather than a silent rewrite of the paragraph above.