opcHealth

Privacy & Support

What the app does

opcHealth shows the status of OCI Monitoring alarms for the tenancies you add, signing in exactly the same way as the OCI console. It also shows OCI's own maintenance and incident announcements for those tenancies — the same notices you'd see under the bell icon in the OCI Console — including which specific resources each one affects.

What data leaves your device

Your OCI username and password never pass through any server of ours — sign-in happens directly on OCI's own real login screen, inside Safari.

opcHealth has no backend at all. Every request it makes goes straight from your device to Oracle's own OCI APIs, using your own session token. Nothing about your account, your alarms, or your device is ever sent to us.

OCI permissions opcHealth needs

opcHealth only ever reads data from your tenancy — it never creates, modifies, or deletes anything in OCI. If you're signing in as a user whose access is scoped by an IAM policy (rather than a tenancy administrator), an administrator needs to grant this minimum, tenancy-level, read-only policy:

Allow group <your-group> to read alarms in tenancy
Allow group <your-group> to read metrics in tenancy
Allow group <your-group> to read announcements in tenancy
Allow group <your-group> to inspect compartments in tenancy
Allow group <your-group> to inspect tenancies in tenancy

What each line unlocks:

Alerts

opcHealth checks alarm status itself, on a schedule you control in the app, and shows a local notification the moment it detects an alarm has started firing — entirely on your device. No push service, no external server is involved in that process.

Support

Questions or issues? Write to javiermugueta@gmail.com.