Updated November 18, 2026. We use first-party website analytics to understand which public pages are useful, where visits come from, and which project, contact, booking and video controls are used.
A random browser-tab session ID, page paths from a fixed list, broad traffic source (such as Google or Instagram), approved campaign labels, bounded non-personal post IDs (post_0001 to post_9999), event type and safe destination labels. A visit expires after 30 minutes of inactivity. Each browser tab is separate, so visits are not unique people. Session information is kept in sessionStorage, not cookies or a persistent cross-visit identifier.
We do not store raw IP addresses, names, emails, form contents, full query strings, detailed referrer URLs or email-link contents in this analytics database. This feature does not record your screen, keystrokes or a replay of your browsing. Hosting providers may process technical request data to operate and secure the site separately.
Visit and event records have a 90-day reporting window. Older rows are removed in bounded batches when new traffic arrives, so physical deletion can take longer during periods without traffic. Dashboard reporting is limited to 90 days. Historical campaign-only aggregate counters remain separate. Only the studio owner can view analytics reports.
We respect browser Do Not Track and Global Privacy Control signals by not collecting these events. Blocking JavaScript or the analytics endpoint also prevents collection. Closing a tab clears its session storage. No advertising or third-party analytics service receives these measurements.
Known bots are filtered and a visible page running JavaScript is required, but automated traffic may still contribute. Email or booking clicks show intent, not proof of an email sent or a booking completed. Visitors who opt out or block collection will not appear. Full-site measurement begins with the new implementation; earlier overall traffic cannot be reconstructed.