Legal

Privacy policy

Last updated July 25, 2026

Protection of covered workspace content

Covered note bodies and meeting content are encrypted with per-workspace keys before storage. The wrapping key is held outside the database, so browsing or copying the database alone does not reveal that content. This is not zero-knowledge encryption: Beespo's application server can decrypt content when serving an authorized user.

Privacy-hardened product analytics

Beespo uses PostHog Inc., hosted in the United States, as a service provider for limited product analytics. On the public landing page, Beespo may record explicit events such as sections reached, demonstrator and call-to-action interactions, coarse device class, and whether an access request succeeded. The contents of access-request fields are never sent to PostHog.

Public landing events use a random identifier held only in memory for the current page visit. It resets when the page reloads or closes, is not stored in cookies or local storage, and does not create a person profile. Legal, support, and public participant pages are not tracked.

Authenticated product events use pseudonymous user and workspace identifiers created with a keyed hash. PostHog does not receive raw database identifiers, names, email addresses, ward or unit names, customer content, search terms, URLs, referrers, pathnames, or document titles. Beespo can recompute authenticated pseudonyms with its secret key, so they are pseudonymous rather than anonymous; Beespo does not re-link them except where legally required.

PostHog may receive technical details such as browser, operating system, device type, screen size, SDK version, and an ephemeral session identifier. GeoIP enrichment is disabled and PostHog is configured to discard client IP data. Autocapture, automatic pageviews, session replay, surveys, and remote configuration are disabled. Beespo uses these events to understand and improve product use—not for advertising, and never to sell personal information.