PRIVACY POLICY.

• Project, template, and scorecard forms — the contact details and brief you enter are used to deliver the requested resource, assess the request, reply, and manage the lead. Optional marketing email is added only when the form asks for and receives that choice.
• Email — newsletter addresses, inquiry messages, and delivery status may be handled by Supabase and Resend so the studio can store submissions and send requested or consented messages. Newsletter messages include an unsubscribe route.
• Purchases — Stripe or PayPal processes payment credentials; TAGDesigns does not receive a complete card number. The studio stores the identifiers, product, buyer email, amount, currency, and payment status needed for fulfillment, support, fraud review, and transaction records. See the providers' Stripe privacy notice and PayPal privacy statement.

The site uses the Meta Pixel in the browser and Meta Conversions API (CAPI) on the server to measure page views and selected actions such as leads, checkout steps, and purchases, and to understand advertising attribution. Meta can receive the page URL, referrer, event name and time, event identifier, browser or device information, and the identifiers described below.

Requests sent through CAPI can include the request IP address and user agent for event matching, along with a one-way SHA-256 hash of the random session identifier. The studio's site-events table does not intentionally store the IP address or user agent, but the hosting platform and Meta may process them. For a completed purchase, CAPI may also receive a one-way SHA-256 hash of the buyer email. Hashing changes the representation; it does not make the source data anonymous.

Analytics properties use an event-specific allowlist. Names, email addresses, phone numbers, website fields, and free-text form messages are not intentionally attached to ordinary page-view or Lead event properties. The purchase-email hash described above is the limited exception for server-side purchase measurement.

A random first-party session ID is kept in sessionStorage and included in studio site-event records so activity from one browsing session can be grouped. The Meta browser identifier _fbp and, after an ad-click URL contains fbclid, the click identifier _fbc may be kept in sessionStorage, localStorage, and first-party cookies for up to 90 days. These Meta identifiers accompany studio event records and Meta events. A temporary Meta test-event code may be kept in sessionStorage during diagnostics. Meta may also use cookies or similar technologies under its own Cookies Policy.

Browser controls, content blockers, and clearing cookies, localStorage, and sessionStorage can reduce or reset browser-side measurement. They may also affect site features and do not necessarily remove records already received by TAGDesigns, Meta, a payment processor, or another provider. Meta account holders can review Meta Ad Preferences and Meta's Privacy Policy.

To ask about, correct, or delete studio-controlled contact or subscription records, email contact@gerquiaabner.com. Identity may need to be verified before acting. A request cannot control copies held independently by Meta, Stripe, PayPal, or another provider, and some records may be retained when reasonably needed for transaction fulfillment, tax, accounting, fraud, security, disputes, chargebacks, or legal obligations.

TAGDesigns keeps lead, email, analytics, and transaction records only as long as reasonably needed for the purposes above, operational continuity, or applicable recordkeeping needs. Retention varies by record and provider. Access is limited to the studio and service providers used for hosting, database storage, email delivery, payment processing, and Meta measurement, subject to their own terms.

The TAGDesigns shop is intended for professional use; the studio does not knowingly collect data from anyone under 16.

Material changes to this policy will be announced via the journal newsletter and reflected in the "last updated" date below.