Kokto

Website privacy and analytics

Short answer

Kokto uses cookieless PostHog analytics to understand which public pages and tools are useful; PostHog does not set an analytics cookie or store a persistent analytics identifier in your browser. The public website also uses Google Analytics 4 (G-K27SJ98VN2), which may use first-party analytics cookies to measure visits and page views. Kokto does not create PostHog person profiles or record session replays. Search text and shared party-menu details are excluded.

Updated · Kokto Editorial

How cookieless measurement works

Kokto uses its own PostHog US Cloud project in cookieless mode. PostHog does not write an analytics cookie or analytics identifier to local or session storage. It creates a server-side, daily rotating hash from limited request information to estimate unique visitors without recognizing the same visitor across different days.

The technical request reaches PostHog's US service. In cookieless server-hash mode, the IP address is used only as an input to the daily hash and is stripped before later transformations. Kokto also respects a browser's Do Not Track setting.

What we measure

Kokto measures page views, broad interaction events, conversion steps and Core Web Vitals. The setup does not create PostHog person profiles, identify visitors across days or record session replays, and Kokto does not send names or email addresses through these website events.

Useful events include recipe sharing outcomes, the number of results returned by a website search, party-planner starts, menu sharing outcomes and sample shopping-list downloads. These measurements help us improve navigation, content and the path from a useful page to interest in the Kokto app.

What we deliberately exclude

Kokto does not send the words you type into cocktail search or party-planner search. Tracked URLs exclude fragments and query parameters except recognized source and medium categories, such as chatgpt.com and referral. External referrers are reduced to their origin; raw campaign terms and search keywords are not retained.

The two public search fields are excluded from automatic interaction capture. Recipe paths and aggregate counts may still be measured because they describe public content rather than text entered by a visitor.

Website and mobile app are separate

This notice covers the public website at kokto.app. It does not change the Kokto mobile application's data practices. The mobile app has a separate privacy policy linked below.

Kokto analytics is isolated in its own PostHog organization and project. Data from unrelated products is not combined with this website's analytics.

Questions and requests

Contact Kokto Support if you have a privacy question or want to request access, correction or deletion relating to information you believe Kokto holds. Include enough context for the team to find the relevant record, but do not send passwords or payment details.

Google Analytics

The public website also uses Google Analytics 4 (measurement ID G-K27SJ98VN2) to measure visits and page views. Google Analytics may use first-party analytics cookies to distinguish visitors and sessions. This is separate from Kokto’s cookieless PostHog analytics. You can limit cookies through your browser settings.

Your bar, your next drink

Keep the ingredients. Find the possibilities.

Use Kokto to organize your home bar, find recipes you can make and see what one more ingredient unlocks.

Explore the Kokto app
GET IT ONGoogle Play