Guide 04 · For the Bee wearer

Manage privacy and consent

Know what is processed, what is kept, and which controls belong to whom.

Step 1

Before analysis

The local collector sends only conversation parts you approve, without topic filtering or identifier redaction, for short-lived encrypted processing. Approved text can contain spoken secrets and other sensitive information. Review the current processing policy and choose recordings you have permission to use. Conversation ingestion requires separate activation after consent and account verification.

Step 2

What remains

The intended durable record contains structured alerts, summaries, preferences, and content-free audit information - not full conversation text. A minimal redacted alert excerpt may be kept separately for no more than seven days. See the Data & AI Policy for details.

Step 3

Sharing is a separate decision

The wearer controls who may receive information and which categories or cadence are allowed. Each invited person separately controls verification and messaging opt-ins. Neither choice substitutes for the other.

Setup saves your preferences and consent, but does not itself connect Bee or start monitoring. The current manual-upload flow does not provide private-phrase exclusions or identifier redaction; approved text can include spoken secrets sent for AWS AI analysis. Full transcript-copy sharing is not offered while its enforcement is unfinished.