Record protection enabled
PassedAll public application tables have row-level security enabled.
Limit: Enabled protection does not prove every access rule is correct.
MyHealth-Passport · VitaCresto Health
A public check of five privacy configurations—not a promise that the whole platform is safe.
Last checked: 10/28/2026, 6:00:00 AM UTC
Daily at 06:00 UTC · No current grade after 26 hours
The checks inspect protection settings, not patient records. No names, record contents, credentials or internal findings are published.
All public application tables have row-level security enabled.
Limit: Enabled protection does not prove every access rule is correct.
Profiles, medications, allergies, conditions, immunizations, dose logs, consents and visibility settings have read policies; none is a literal allow-everyone rule.
Limit: This is a configuration check, not a test of every recipient or complex policy expression.
Wearable authorization states, wearable tokens and consent signing keys have row protection and no permissive visitor or signed-in read policy.
Limit: Other credentials, server code and provider settings are outside this check.
Clinical sharing and passport disclosure audit tables have row protection and no permissive client update or delete policy.
Limit: Does not verify every event was logged or validate cryptographic audit chains.
The core record tables have restrictive multi-factor rules for both reading and writing.
Limit: Checks rule presence, not a live authenticator challenge or every endpoint.
A means all five checks passed. F means at least one failed. A dash means missing, incomplete, unavailable or overdue evidence. Each check matters; failures are not averaged away.
This is an internal automated configuration report, not an independent audit, security certification, clinical safety rating or AI safety evaluation. It does not test every consent change, access path, AI request, backup, device, encryption setting or provider agreement. Changes between daily checks may take up to 24 hours to appear.