Privacy and measurement
Analytics, session recording, and campaign measurement start enabled in memory on a fresh visit. You can reject or change each purpose at any time. Enquiry details and raw advertising identifiers are not sent to analytics.
Analytics and heatmaps
When analytics is enabled, PostHog EU receives pseudonymous page, device, coarse geographic, interaction, performance, and sanitized error data. On article pages this can include the article identifier and language, content-relative progress milestones, visible and focused reading-time ranges, loss-of-focus, background, page-exit or browser-history departure signals, and a finite onward-destination category with the depth and time range at selection. Article text, raw destination URLs, names, contact details, messages, event dates, enquiry references, and raw ad click identifiers are excluded. Mobile phone and WhatsApp selections are intent signals only; the site does not know from those selections whether a call connected or a message was sent. Scrolling is treated as a diagnostic signal, not proof that someone read or was persuaded. Analytics retention is one year.
Landing-page experiments
When a registered experiment is active and analytics is allowed, the site may retain a treatment assignment for up to 90 days and send only the registered experiment, treatment, and placement labels to PostHog. Forced preview links are marked for exclusion from results. Withdrawing analytics clears the stored assignment.
Session recordings
Session recording starts enabled for a fresh visit and can be disabled separately in Measurement settings. When enabled, recordings are retained for 30 days. All inputs, the enquiry form and confirmation, accessibility controls, and user-authored workbench content are masked or blocked. Console logs, network headers, and request or response bodies are not recorded.
Campaign and partner attribution
When analytics is enabled, the site keeps controlled first-touch, current-session, and last non-direct-touch labels for up to 90 days. When campaign measurement is enabled, raw campaign and click fields stay in the current tab and may accompany a deliberate enquiry to the operational lead destinations. Google Tag Manager then loads a Google Ads conversion tag only for allowlisted phone clicks, WhatsApp clicks, and accepted form deliveries; names, contact details, event dates, enquiry references, raw URLs, and form contents are excluded. PostHog never receives raw campaign or click fields. Approved creator and partner links are reporting tags, not a commission or payout system.
Enquiries, Dotallio and Supabase
Details you deliberately submit are validated and sent concurrently to the Dotallio enquiry board and a Supabase backup record so the enquiry can be answered even if one destination is temporarily unavailable. These operational records are separate from browser analytics. When analytics is allowed, a pseudonymous encrypted reference can connect delivery and later business outcomes without sending the enquiry contents to PostHog.
Google Search Console
Search Console provides aggregate search queries, impressions, rankings, and click-through reporting. Its site verification does not add a browser analytics tag or optional storage.
Your choices
A fresh visit receives an all-on measurement preference in memory; the site does not store that default as a manual acceptance. Rejecting measurement sends no further PostHog, replay, campaign, or advertising requests. You can change or withdraw a choice at any time; withdrawal stops the relevant collection and clears its browser persistence. The enquiry form, WhatsApp, and email continue to work.
Questions and data rights
Use the address below to ask about access, correction, deletion, objection, or the way measurement is handled. Include only the information needed to locate the relevant enquiry or interaction.
yonatan@yonatanlavy.comLast updated: