RenalShield
Public policy surface
beta-public

Privacy Policy

Current data-handling posture for the free no-account prototype.

Updated 2026-08-15. Beta policy draft; final paid launch still requires qualified legal, clinical, privacy, and tax review.

Current data model

The current free prototype does not provide user accounts or paid entitlements.

Food logs, daily limits, journal entries, and lab-note fields may be stored by the running app instance so the app can show today's budget and recent entries.

Do not enter emergency information, account credentials, Social Security numbers, insurance identifiers, full medical records, or anything you would not want stored in a beta prototype.

Health-adjacent information

RenalShield can include health-adjacent entries such as food logs, symptoms, weights, blood pressure notes, and lab notes.

Professional, clinic, organization, API, or multi-client use requires a separate privacy/security review and written license before use.

Before accounts or paid plans

RenalShield must define retention, deletion, export, backups, analytics, operator access, incident response, and HIPAA/BAA scope before accounts or paid plans launch.

If RenalShield is used for or by a covered entity or business associate, HIPAA obligations must be reviewed before deployment.

Source Ledger