Privacy policy / Effective September 29, 2026
We keep an inquiry for 24 months, a chat for 12, and answer a data request within 10 days.
This is what Gudzen, an interior remodeling crew in Austin, takes from this site, who else sees it, and how long it sits on a server before it goes.
When this policy took effect
This policy takes effect on September 29, 2026, and that is also the date of its last amendment. It covers gudzen.store and every page on it: the home page, the services, the about and contact pages, the inquiry form and the support chat. It does not cover what happens on a job site. That is between you and the crew, in the written estimate.
Who is responsible for your data
The controller is Gudzen, trading at gudzen.store, an interior renovation crew working in and around Austin. Post reaches us at 73 Market Street, Apt 3, Austin, Texas 03119, Austin, Texas, United States. The person who reads your inquiry is the same person who comes out to walk the job. There is no call center and no outside sales team between you and the crew.
What we collect, and from where
Only what the site itself records. Nothing is bought from a list broker. No account is created, no password is set, and no card number or payment ever passes through this site, because nothing is sold here.
The inquiry form
When you send the form, baze957.php writes your name, phone, email, the address of the job, the kind of inquiry you picked, your message, the specification you asked for and the consent tick. Alongside those, automatically, it records your IP address, your browser's user-agent string, the referring URL, the moment the form was rendered and the moment it was sent. The two timestamps are there to catch bots that fill a form in half a second.
The support chat
The chat stores the conversation on our server: your messages, our replies, and the name, phone and email you chose to give when you started it. Your browser keeps a token under gudzen_chat_token and the last message you read under gudzen_chat_seen, so you can close the panel and come back to the same thread.
Technical and log data
Like every web server, ours writes an access log line per request: IP address, time, the page asked for, the response code and the user-agent.
Cookie identifiers and the consent record
Your consent choice is stored in your browser under site_consent_v2. Nothing else on this site stores a choice. If you allow storage, the Google, Microsoft and Meta tags may set their own cookies; the full list is on the cookie and storage page.
Advertising click identifiers
If you arrived from a paid ad, the link carries a click identifier: gclid, msclkid or fbclid. It ends up in the referring URL and in the access log. What happens to it depends on your consent choice, below.
What each piece is used for
- Form fields are used to call or write back, book the walk-through, and write the estimate for the drywall repair, strip-out or finishing job you described.
- The job address tells us whether the house is inside the area we drive to, and how long the trip is.
- Chat messages are used to answer you and to carry the conversation into a walk-through if it gets that far.
- IP, user-agent and timestamps are used to stop spam and abuse of the form and chat, and to trace a fault if the site breaks.
- Click identifiers and ad cookies, once you allow them, are used to tell Google Ads, Microsoft Advertising and Meta Ads that a click led to an inquiry, so we stop paying for ads that bring nobody.
- The consent record is used to remember your answer so the banner does not ask on every page.
We do not sell any of it. We do not build profiles of visitors, and we do not use your inquiry to send you a newsletter. There is no newsletter.
The legal basis for each use
For visitors reaching us from Europe, each use rests on one stated basis under the GDPR. The same split guides how we treat everyone else.
| Purpose | Data | Legal basis |
|---|---|---|
| Answering an inquiry and writing an estimate | Form fields, chat messages | Steps taken at your request before a contract, and your consent tick |
| Carrying out the job you book | Name, phone, email, job address | Contract |
| Spam and abuse prevention | IP, user-agent, timestamps, logs | Legitimate interest in keeping the form and chat usable |
| Ad measurement and conversion reporting | gclid, msclkid, fbclid, ad cookies | Consent, given through the banner |
| Analytics | Analytics cookies | Consent, given through the banner |
| Remembering your choice | site_consent_v2 | Legal obligation to record consent, and legitimate interest |
The ad platforms that send people here
This site runs paid advertising today. Google Ads and Microsoft Advertising send traffic to it, and Meta Ads does when a campaign runs there. Each platform adds its own click identifier to the link you tap:
- Google Ads attaches
gclid. - Microsoft Advertising (Bing) attaches
msclkid. - Meta Ads (Facebook and Instagram) attaches
fbclid.
The identifier arrives in the address bar whether or not you consent; that is how the platform built the link. What we control is whether it is ever stored in a cookie or reported back. Until you press Allow, it is not. Buying ads from a platform means that platform takes our money. It does not mean any platform has checked or vouched for this crew's work, and we make no such claim.
How Consent Mode v2 holds the tags back
The site uses Google Consent Mode v2. Before any tag can fire, four signals are set to denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. They stay denied until you press Allow in the banner. Ad data redaction is on while they are denied, so the click identifiers are not written to cookies.
Press Decline, or withdraw later with the Cookie settings button in the footer, and all four are set back to denied at that moment. The site also deletes the Google, Microsoft and Meta ad and analytics cookies it can reach on this domain. Your choice is kept under site_consent_v2 for 12 months, then the banner asks again.
Global Privacy Control is honored
If your browser sends Global Privacy Control (the Sec-GPC signal), we treat it as an opt-out of sale and sharing and record it without asking you again. The banner does not appear. Even if you later press Allow, the three advertising signals stay denied while your browser sends GPC; only analytics storage can be granted.
The companies that receive data
- Google Ireland Ltd / Google LLC, for Google Ads. It attaches gclid to a click and receives the Consent Mode signals. Its policy: policies.google.com/privacy.
- Microsoft Ireland Operations Ltd, for Microsoft Advertising. It attaches msclkid. Its own handling is set out in the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
- Meta Platforms Ireland Ltd, for Meta Ads, which attaches fbclid where a campaign runs there. Its policy: facebook.com/privacy/policy.
- The hosting provider that serves this site and stores the inquiry database and chat transcripts.
- The mail provider that carries the notification of a new inquiry to our inbox at office@gudzen.store.
Nobody else. We do not pass your details to a supplier or a subcontractor. If your job needs a licensed electrician or plumber, we give you their number and you call them.
Data leaving the country
The crew and the site sit in the United States, so a European visitor's data is transferred to the US when it is sent. Google, Microsoft and Meta also move data between their US and Irish entities. Those transfers rely on the EU-US Data Privacy Framework where the company is certified under it, and on the European Commission's Standard Contractual Clauses in each platform's data processing terms. We do not send your data to any other country ourselves.
How long each thing is kept
| Category | Kept for | Then |
|---|---|---|
| Inquiries and their email copies | 24 months | Deleted from the database and the inbox |
| Chat transcripts | 12 months | Deleted from the server |
| Server and access logs | 90 days | Rotated out and overwritten |
| Record of a consent choice | 12 months | Expires; the banner asks again |
Twenty-four months for inquiries is not arbitrary. People ask about a bathroom strip-out in spring and book it the next winter, and a callback on a seam that opened needs the original scope to hand. If you want yours gone sooner, ask. Invoices for a job we actually did are business records and are kept as tax law requires, separately from this site.
How the data is protected
The whole site runs over HTTPS, so the form and chat travel encrypted. The inquiry database and transcripts sit outside the public web folder and behind a password-protected panel that only the crew lead opens. Forms carry honeypot fields and a timing check against bots. Logs rotate on the 90-day clock. No system is perfect; if a breach ever touches your data, we tell you and the authorities the law requires us to tell.
Your rights under the GDPR
If you reach this site from the European Economic Area or the UK, the GDPR gives you these rights over what we hold:
- Access: a copy of everything we hold on you.
- Rectification: fix a wrong phone number or address.
- Erasure: have it deleted.
- Restriction: have us keep it but stop using it.
- Portability: get it in a plain machine-readable file.
- Objection: object to uses based on legitimate interest.
- Withdrawing consent: at any time, with the Cookie settings button in the footer or by writing to us, without affecting what was done before.
Your rights under US state law
California residents have rights under the CCPA as amended by the CPRA: to know what personal information we collect and why, to get a copy, to correct it, to delete it, to limit use of sensitive information, and to opt out of the sale or sharing of personal information. We do not sell personal information. Allowing ad cookies can count as sharing for cross-context advertising under California law, so Decline, or a Global Privacy Control signal, is your opt-out. Residents of Texas, Colorado, Virginia, Connecticut, Oregon and the other states with privacy laws in force have matching rights, and we honor them the same way. Using a right never changes the price or the service you get from us.
Children
This site is for homeowners, tenants and property managers booking interior work. It is not meant for children and we do not knowingly take data from anyone under 16. If a child has sent us something, tell us and we delete it.
Complaining to a regulator
Write to us first; most things get fixed in a phone call. You can always complain to your state Attorney General, which in Texas is the Office of the Attorney General's consumer protection division, and in California also to the California Privacy Protection Agency. Visitors in Europe may complain to the data protection authority of the country they live or work in.
How to make a data request
Email office@gudzen.store with "Data request" in the subject, or write to Gudzen, 73 Market Street, Apt 3, Austin, Texas 03119, Austin, Texas, United States. Say what you want: a copy, a correction, deletion, or an opt-out. Give the name and the phone or email you used on the form or chat, so we can find the record and confirm it is yours. We do not ask for ID beyond that unless the request is for someone else's data.
We answer within 10 days. If a request is complicated and the law gives us longer, we still write within 10 days to say what is happening and when it will be done. There is no fee. An authorised agent can make a request for a California resident with written permission.
To stop ad cookies right now, without writing to anyone, use the Cookie settings button at the bottom of any page.
When this policy changes
A change goes up on this page with a new effective date at the top and on the rail. If it changes what we collect or who receives it, the consent banner is shown again so you can make the choice afresh. If you have an open inquiry and the change affects it, we email you.
Talking to a person about this
Email office@gudzen.store or call +1 (383) 555-7173. Post goes to 73 Market Street, Apt 3, Austin, Texas 03119. The same crew that does the drywall repair and finishing reads the privacy mail, so expect a plain answer. The rules for estimates and callbacks are in the terms; the storage keys are on the cookie page. Want to talk about a job instead? Request a walk-through.