Effective September 7, 2026

This is how Tipuna Studio collects data, runs advertising and answers privacy requests.

Tipunaqe, trading as Tipuna Studio at tipunaqe.com, is the operator and the controller of the data described below. This policy covers what the inquiry form and support chat collect, how Google Ads, Microsoft Advertising and Meta Ads read this site, how Consent Mode holds storage back, and how to reach a person about any of it.

What Tipuna Studio collects, and on what basis

Five things: when this policy took effect, who runs the site, what the forms and logs actually capture, what each category is used for, and the legal basis behind each use.

Effective date

This policy took effect on September 7, 2026. Any version published before that date no longer applies.

Who controls this data

Tipunaqe, trading as Tipuna Studio at tipunaqe.com, is the controller of the data described in this policy. The studio operates from 127 Cedar Court, Austin, Texas 78904, United States, and that address is also where a written data request should be sent.

Data collected

The inquiry form on this site (which posts to submit.php) records the name, phone number, email address, the address or area named for a sitting, the kind of session selected, any notes typed into the message field, the session specification if one was built with the configurator tool, and the consent tick itself. Alongside that, the form records the visitor's IP address, browser user-agent string, the page that referred them, and the two timestamps marking when the form was rendered and when it was submitted.

The support chat widget (which talks to chat.php) keeps the message thread and a return token in the visitor's own browser, plus whatever name, phone or email the visitor volunteers when starting a conversation.

Separately from either form, this site reads cookie identifiers and the advertising click identifiers that a paid ad platform appends to a link a visitor arrives on: gclid from Google Ads, msclkid from Microsoft Advertising, and fbclid from Meta Ads where a campaign runs there.

Why each category is collected

Name, phone, email and address answer and schedule a specific sitting — without them the studio cannot reply. Notes and a session specification let the photographer prepare before a first call. IP address, user-agent and referrer data help identify abuse of the form and diagnose delivery problems, and the two timestamps confirm how quickly an inquiry was answered. Chat transcripts and the return token let a visitor pick a conversation back up without repeating themselves. The click identifiers and cookie identifiers measure which advertising campaign produced an inquiry, so spend can be judged against results.

Legal basis for each use

Handling an inquiry or a chat message rests on contract — taking the steps needed to arrange a sitting a visitor asked for. Keeping technical and log data rests on legitimate interest in running a working, abuse-resistant site. Reading advertising click identifiers, and any advertising or analytics storage tied to them, rests on consent, gathered through the banner described in the next section and withheld by default until a visitor allows it.