Cookie notice
The browser storage and analytics technology used on weftlabs.com.
Analytics storage
When analytics is enabled, we use PostHog to record pseudonymous page views, a small set of named interactions, and session replay when a visit matches the recording rules configured in PostHog. PostHog assigns a random identifier that is held only in memory for the current browser page session. The website does not write that analytics identifier to cookies, local storage, or session storage.
Session replay captures the public page structure and interaction changes. Visible public-page text can appear in a replay. We configure PostHog to mask all form inputs in the browser before replay data is sent, disable console-log recording, and sanitize captured page URLs. We also disable automatic event capture, heatmaps, performance monitoring, exception capture, and automatic saving of full referrer URLs or unallowlisted campaign data. We do not configure PostHog for advertising.
- Purpose: understand public-page use, identify usability problems, and measure whether visitors use selected calls to action.
- Data: a temporary random identifier, sanitized page URL, referring host, allowlisted campaign fields, event name, website version, replayed public-page structure and interaction changes, and standard request metadata. The temporary distinct and session identifiers can be handed to the weft.network signup app through the URL fragment to connect the website visit with the signup journey.
- Browser duration: the identifier exists only in memory for the current page session and is not retained in browser storage. Server-side event retention is described in our privacy notice.
Site test cookie
When we run a test of two versions of this website, we set one first-party cookie, weft_site, so you see the same version on every page and every visit. It holds only the name of the version. It holds no identifier, and we do not use it for advertising or to follow you on other websites.
To choose a version for a new visitor, our server asks PostHog with a random key that is used once and not stored. Analytics events from your visit carry the version name, so we can compare how the two versions are used. When the test ends, the website removes a version or "off" cookie on your next page load. A preview cookie stays until it expires after 30 days or you delete it.
- Name: weft_site. Set by weftlabs.com while a site test runs, or when you open a preview link that shows one version.
- Value: the version you see ("ascii" or "control"), "off" when you are not in the test, or "preview-new" or "preview-old" after a preview link. A preview is not part of the test.
- Duration: 90 days for a version; 1 hour for "off"; 30 days for a preview.
- Attributes: first-party, SameSite=Lax, Secure on HTTPS. Page scripts read it to show the correct version before the page appears.
Essential technology
Apart from the site test cookie above, the marketing website does not set a first-party account, preference, or analytics cookie. Our hosting and security infrastructure still processes requests and may use short-lived technical measures when needed to deliver and protect the site.
Submitting the beta form sends the email address you enter to our server and then to Resend. The form does not need a separate marketing cookie.
No advertising cookies
We do not use advertising cookies, social-media tracking pixels, or cross-site targeted advertising on this website.
Your controls
The website's PostHog configuration does not write analytics identifiers to browser storage. Browser extensions and network-level content blockers can block PostHog analytics and replay requests without preventing you from reading the public website.
Because this analytics configuration does not use browser persistence, the website does not show an analytics-cookie preference dashboard. You can still block analytics requests with browser or network-level controls.
You can delete the weft_site cookie in your browser settings at any time. While a test runs, you then get a version again on your next visit.
Changes
We may update this notice when our use of browser technology changes. We will post the revised notice here and change the effective date.
Contact
Questions about this notice can be sent to patrick at weftlabs.com. Our privacy notice explains more about how we use personal information and the rights that may apply to you.