Privacy Policy

Scope and data we collect

This policy covers Trackside Austin. We may receive contact and studio information that you submit, including name, email, website, location, pricing and description. Our infrastructure may process IP address, browser, device, referring page, timestamps, security events and basic usage logs. Google and other linked services collect information under their own policies.

How and why we use data

We use information to operate and secure the site, review and respond to listing requests, verify directory facts, prevent abuse, comply with law, and improve performance. The legal bases where applicable include consent, contract, legitimate interests and legal obligations. We do not sell personal information or use sensitive personal data for profiling.

Sharing, retention and transfers

We disclose information to infrastructure, database, security and professional-service providers acting for us; to authorities when legally required; or in a business transfer. Public studio facts may be published. Submission records are retained while a request is evaluated and as reasonably needed for records, disputes, security and legal obligations; operational logs are kept only as needed. Providers may process data outside your region with lawful safeguards.

Choices and rights

You may request access, correction or deletion of personal information, object or withdraw consent where applicable, or lodge a complaint with a regulator. We will verify requests and honor rights required by applicable law. Texas residents may exercise rights available under Texas law and appeal a denied request. We do not discriminate for exercising privacy rights.

Children, security and contact

The service is not directed to children under 13 and we do not knowingly collect their personal information. We use reasonable safeguards, but no transmission or system is perfectly secure. Send privacy or rights requests through the listing form with “Privacy request” in the description until a dedicated contact channel is published.

Accounts, requests and Google Places

Optional accounts use Google Identity Services to receive a verified email address, name and Google profile picture. Trackside stores a hashed session token, profile fields, saved items and owner activity; it never receives a Google password. You may upload a public profile photo and bio. Studio claims, featured applications and quote requests may include contact details, project information and verification material. These submissions are stored for review and routed to the directory operator at caleb@madebyrodeo.co through an email-delivery processor.

Studio profiles may request current place details and photos from Google Maps Platform. Google may receive technical and request information and processes it under Google’s Privacy Policy and applicable Google Maps Platform terms. Required Google Maps and photo-author attribution is displayed with that content.

Optional analytics

If Google Analytics is configured, it loads only after you choose “Allow analytics.” Trackside uses it to understand aggregate page use and improve the directory, not for targeted advertising. You may decline without losing core functionality and can clear the saved choice through browser storage controls.

Directory accounts and verification records

Authenticated applicants and claimants may provide listing details, professional roles, portfolio links, images, contact information and evidence connecting them to a listing. We use this information to review claims, publish approved owner updates, prevent impersonation and maintain an editorial record. Claim status and public updates remain connected to the authenticated account until deleted, revoked or no longer reasonably needed.

Claim evidence and administrative review notes are not intentionally published. Public profile fields, approved images and portfolio links are public by design. Account deletion requests may require us to unpublish or reassign claimed information while retaining limited records required for fraud prevention, disputes or legal compliance.

Google authentication, reCAPTCHA and profile images

Google Identity Services verifies account identity. Google reCAPTCHA protects application and inquiry forms from automated abuse and may process device, browser, network and interaction signals under Google's Privacy Policy and Terms. Profile images uploaded to Trackside are resized in the browser and stored with the account for public display.