RECORDING GUIDANCE

Quiet does not mean covert.

Haberdash should only be used where recording is permitted, appropriately disclosed, and aligned with your own policies and obligations. If you are unsure whether a meeting can be recorded, the safest default is not to record it.

Before you record

  • Confirm that recording is allowed for the meeting, jurisdiction, and workplace context.
  • Give notice to participants when notice is required or expected.
  • Use clear meeting invites, agendas, or verbal reminders so the room understands the workflow.

What not to do

  • Do not use Haberdash for covert or deceptive recording.
  • Do not bypass company policy, venue policy, or local consent rules.
  • Do not route sensitive material into external providers unless your deployment and approvals allow it.

Operational good practice

  • Keep access scoped to the people who need the briefings and themes.
  • Review retention and deletion settings before broader rollout.
  • Choose local, hosted, or provider-backed workflows deliberately based on the sensitivity of the material.

Responsibility stays with the operator

This guidance is informational only and is not legal advice. The person or organization using Haberdash remains solely responsible for notice, consent, legality, policy compliance, and the choice to record in any particular setting.