Law Enforcement Requests

Valid and appropriately scoped process

• BusyBi should require valid legal authority before disclosing user information unless an emergency or mandatory-reporting duty applies.
• Requests should identify the requesting agency, legal basis, account or record sought, time period, and return contact.
• Overbroad, defective, informal, or jurisdictionally invalid demands should be narrowed, challenged, or rejected where lawful.
• BusyBi should disclose only the information the valid process actually compels and that the service actually holds.

Notice and records

Member notice should be provided before disclosure when legally allowed and operationally safe. Each request, review decision, preservation step, disclosure, legal restriction, and later deletion should be logged with tightly limited access.

Emergency and child safety

A credible imminent threat, possible child sexual abuse material, trafficking, or another mandatory-reporting situation requires urgent trained review. An emergency request should explain the specific danger, why ordinary process is too slow, and how the requested records relate to preventing harm.

Pre-launch limitation

A dedicated verified-agency intake, counsel-approved response playbook, preservation schedule, and transparency reporting process must exist before the member service launches. General support is not yet a production legal-process channel.