Privacy
Flair is built to be useful without being slippery.
The beta trust model is simple: explicit account connection, explicit signal mode, explicit execution approval, and visible provenance when something matters.
Core commitments
- Flair only reads from the accounts and signal modes you connect.
- Multi-account provenance is preserved so one inbox or calendar does not silently contaminate another.
- Approval-based execution stays explicit for email drafts and calendar changes.
- Privacy and policy boundaries remain visible in product surfaces, not buried behind generic claims.
Launch-surface trust summary
Flair reads
- Gmail sender, thread timing, and message context only from the accounts you connect
- Calendar events and time pressure from the calendars you explicitly allow
- Accepted plan state, execution artifacts, and progress signals inside Flair
Flair does not do
- No hidden email sends
- No silent calendar writes
- No cross-account mixing when policy blocks it
- No background execution without an explicit user action