Trust

Personal progress needs visible boundaries.

Coralio may handle goals, routines, trackers, reflections, optional analytics, AI-assisted planning, and selected read-only health signals. The trust path should be short.

Coralio settings screen with connections and privacy controls
Trust should be visible where users already manage settings, connections, support, and account routes.
Coralio connections screen for supported read-only health signals

Connection boundaries

Show users what is connected and what stays manual.

The trust page should prove that privacy, analytics, AI personalization, notifications, support, and account routes are visible inside the app, not buried in legal text.

Usage Analytics AI Personalization Notifications Account deletion path

Principles

Clear control beats vague reassurance.

Trust pages should say what the product does, what it does not do, and where users can manage or remove their data.

Consent-aware analyticsOptional analytics should be explained and controllable.
AI as supportAI can assist planning, but users stay responsible for choices.
Read-only health signalsSupported health connections can fill trackers, not write back.
Account deletionDeletion paths stay visible from support and legal pages.
Privacy

Policy access

Review what data may be collected, why it is used, and how consent-based analytics are described.

Read privacy policy

Terms

Use boundaries

Review terms, AI feature notes, professional-advice disclaimers, and usage responsibilities.

Read terms

Deletion

Remove account data

Find the in-app deletion path and email route for data removal requests.

Account deletion