Home / Documentation / Privacy, Security & Trust
How Nektur Protects Customer Information
Implemented controls described at a customer-safe level.
Last updated 2026-10-31
Controls customers can rely on in-product
- Organization isolation — members see their organization's data.
- Authentication and roles — sign-in required for the console; Admin vs Agent separations for sensitive pages.
- Database access controls — organization membership checks gate customer data.
- Public endpoint protection — rate limits on anonymous consent and request intake paths.
- Minimized identifiers — consent logging stores hashed IP-style identifiers rather than unnecessary raw analytics identity.
- Audit trails — operational actions are recorded for the organization.
- Human oversight — publishing policies and closing privacy requests remain human actions.
- Host separation — marketing, app, admin, and help surfaces are separated by host routing.
Claims we do not make here
The Hive does not claim SOC 2, ISO 27001, HITRUST, HIPAA certification, guaranteed regulatory compliance, zero retention, or end-to-end encryption unless those programs are separately and accurately attested outside this article.
