What users control
Users decide what they write and whether to create or share a selected export or summary.
For organizational buyers
Privacy answers before procurement.
A plain-language overview of user control, consent, organizational access, aggregate reporting, and the documents teams should review before adopting Umbrella.
The operating boundaries
What organizations see
Organizational reporting is designed around aggregate adoption and engagement trends, not raw personal journal content.
What teams must define
Agree on consent, access, retention, deletion, escalation, integrations, and the exact reporting configuration before launch.
Questions for your review
- Which jurisdiction, sector rules, and organizational policies apply to this use case?
- What is the role of each party, and what data processing or service agreement is required?
- What information is collected, where is it processed, how long is it retained, and how can it be deleted or exported?
- Which roles can access account administration, support data, analytics, or shared exports?
- What is the route for a privacy request, security incident, accessibility issue, or urgent mental-health concern?
Do not infer a certification: this page does not claim HIPAA, PHIPA, GDPR, SOC 2, or any other compliance status. Confirm the requirements and contractual terms for your specific program.
Documentation to start with
For broader risk-management context, organizations can also consult the voluntary NIST Privacy Framework and NIST Cybersecurity Framework.
Bring your review questions.
We can point you to the relevant product and legal documentation for your intended workflow.
Information on this page is general and may change as the product, contracts, and applicable requirements evolve.