OPENLATCH / BRIEFING PRIVACY
What this briefing records.
The OpenLatch briefing is shared with prospective customers. To open it, you enter your work email. This page explains what happens to that email and to what you do in the briefing.
Your work email
- We read your company name and domain from the address. We do not check that you own the address or work at that company.
- The OpenLatch team receives a notification in our internal Slack workspace with your email, company, and approximate location and network. Cloudflare derives the location and network from your connection (city, country, and the network operator's name).
- Your email is attached to your activity in our product analytics (PostHog, hosted in the EU), so the team can see which parts of the briefing you viewed. PostHog also receives your IP address and derives an approximate location from it.
What you do in the briefing
- Which scenes you view, whether you download the one-pager, and how long you spend in the briefing.
- When you leave, a short summary (scenes viewed, time spent, one-pager downloaded) is posted to the same internal Slack channel.
- If your browser sends Do Not Track, no product analytics are recorded. You still receive access, and the Slack notifications are still sent.
Cookies and storage
- ol_briefing is a signed, HTTP-only cookie that remembers your access for 30 days. It holds your email, company name and domain. No database stores it.
- PostHog keeps an analytics identifier in a first-party cookie and in local storage.
- To personalise the briefing, your browser loads your company website's favicon directly from that site.
Retention and your choices
Slack messages and PostHog records are kept only as long as they help us follow up on the briefing. To have your data removed, write to [email protected].