Trust

Privacy approach

BrewLogs public pages use a privacy-conscious measurement approach and avoid hardcoded analytics credentials. Production records remain behind authenticated workspace access.

Start Free

Public-site analytics hooks

The static public site emits local conversion-event hooks that can be connected to an analytics provider. No private analytics credentials are hardcoded into the repository.

Authenticated production data

Brewery production records are part of authenticated workspaces. Public marketing pages and demo pages use static sample content rather than real customer data.

Sensitive event hygiene

The app analytics utility redacts sensitive property keys such as email, token, password, secret, authorization, cookie, and notes before events are passed to a configured provider.

Security and data practices Learn how BrewLogs approaches workspace access, role-based permissions, email verification, audit logs, backups, and responsible production-record security. Data ownership and planned export Understand BrewLogs data ownership, backup planning, planned self-serve export, and how kombucha breweries can keep production records portable. Support and contact Find support options for BrewLogs, including in-app feedback, production contact configuration, planned export questions, and security-related requests.

Start building cleaner kombucha production records

BrewLogs helps breweries track batches, recipes, pH, gravity, flavor production, and fermentation trends in one organized system.

Start Free View Demo