Privacy overview

The product stores account and membership records, customer-authored knowledge, direct support conversations, configuration, audit events, privacy-reduced usage events, and feature-specific workflow records. Secrets, support-message bodies, and raw customer content are excluded from ordinary application logs.

Owners can prepare an authenticated, expiring structured export, configure supported retention periods, and request organisation deletion with confirmation and a cooling-off period. The archive includes safe uploaded files, assessment responses, evidence metadata and certificate records with a manifest and completion checksums. Unsafe or unscanned files are listed but excluded; provider copies, backups and complete rights-request coverage remain separate.

The customer determines the purpose of workspace content processing. Beetl is intended to act as an operator or processor for that data, subject to an approved agreement. Final legal roles and lawful bases require counsel.

The draft Copyright and takedown policy explains notices, counter-notices and repeat infringement. Complaints require authorised human review and limited sharing of notice information with affected parties. Designated-agent registration is not yet verified; Beetl does not currently claim DMCA safe-harbor eligibility. Registration and an operating complaint process require separate verification.

The production hosting region, backup locations and cross-border safeguards are deployment and contract facts. They are not inferred from the source code.