One connector, one clear scope
Access is requested when it becomes useful, with plain-language explanations and an obvious revoke path.
Privacy is not a footer promise. Cherish The Buddy is designed around explicit consent, inspectable memory, scoped connectors, and a visible history of actions.
Access is requested when it becomes useful, with plain-language explanations and an obvious revoke path.
Each memory can show where it came from, how confident the system is, and when it was last updated.
Externally visible, destructive, or broad actions require stronger confirmation.
Action history separates suggestion, approval, execution, result, failure, cancellation, and retry.
Choose respond-only, helpful suggestions, or explicitly delegated low-risk actions.
Data controls support category-level management as well as full export and deletion requests.