Skip to content
CHARGE™
HandbookTriageIdeasDirectory

© 2026 CHARGE Healthcare LLC

CHARGE™ — Clinical Hub and Resource Guide for the ED

Terms of UsePrivacy Policy
HomeHandbookDirectoryTriageIdeas
HomePrivacy Policy

Privacy Policy

Effective March 19, 2026|Updated November 14, 2026|CHARGE Healthcare LLC

CHARGE Healthcare LLC ("we", "us", "our") operates the CHARGE platform. This policy describes how we collect, use, store, and protect information when you use CHARGE. Your organization has separately agreed to our data processing terms.

1. Information We Collect

When you use CHARGE, we may collect:

  • Account information — name, email, mobile phone number, department, and role. Collected during onboarding and updatable via your profile.
  • Authentication data — phone number or email used for OTP verification, and session tokens. We do not store passwords.
  • Usage data — pages viewed, searches performed, articles accessed, votes cast, issues submitted, and comments posted.
  • Search preferences — a random browser cookie lasting 30 days lets anonymous result selections help improve search in your department. We store a department-specific hash of this identifier with click events. A shared browser counts as one source, and no browser fingerprint or IP address is used for this ranking signal.
  • Device and network information — IP address, browser type, OS, and whether access originates from your organization's campus network.
  • Uploaded content — images attached to issue reports or knowledge base articles.

2. How We Use Your Information

  • Authenticate your identity and manage platform access
  • Deliver knowledge base articles, issue reports, and role-relevant content
  • Enable AI-powered semantic search
  • Process inbound emails and generate knowledge base update proposals
  • Send transactional communications (OTPs, status updates, digests)
  • Generate aggregate analytics for department dashboards
  • Maintain platform security and enforce rate limits

3. SMS Messaging and Consent

CHARGE uses SMS as a primary authentication method. By providing your mobile phone number, you consent to receive SMS messages for OTP delivery. Operational alerts and digests may also be sent according to your notification settings.

Frequency: One (1) SMS per sign-in request; operational message frequency varies with your settings and department activity. No marketing messages.

Rates: Standard messaging and data rates may apply. CHARGE is not responsible for carrier charges.

Opt out: Reply STOP to any message, or contact administration to switch to email OTP or SSO.

Help: Reply HELP or contact daniel.seitz@eskenazihealth.edu.

Carriers: Delivered via Twilio to all major U.S. carriers (AT&T, T-Mobile, Verizon, MVNOs).

Your phone number is used for authentication and configured operational notifications. Phone numbers and SMS message content are transmitted to Twilio for delivery. No mobile information, opt-in data, or consent will be shared with third parties or affiliates for marketing or promotional purposes. SMS consent is not a condition of employment — alternative methods (email OTP, SSO/CAS) are available.

4. AI and Automated Processing

  • OpenAI — processes search queries and indexed content to generate embeddings for semantic search. When configured, it also back-translates answer translations to help check their meaning.
  • Anthropic Claude — processes search context to generate answers, analyzes submitted material and forwarded emails, assists with article drafts and review, translates answers, and checks translations. Supported attachments undergo local text extraction and PHI screening before they are sent for AI analysis. Article proposals require human editor review.

CHARGE is not intended for patient data, medical records, or PHI. Do not submit patient-identifying information. Automated screening can miss identifiers and does not guarantee that accidentally submitted information will be blocked.

5. Data Storage and Security

  • Cloud-hosted PostgreSQL (Supabase) with encryption at rest and in transit (TLS 1.2+)
  • Row-Level Security (RLS) policies enforce role-appropriate access
  • Cookies support browser authentication and session management; OTPs expire after a short window
  • Uploaded files are stored in Supabase Storage; access controls depend on the type of content and the workflow
  • Rate limits help protect abuse-sensitive requests
  • Security headers including Content Security Policy (CSP), clickjacking/MIME protections, and Strict-Transport-Security on secure production traffic

6. Data Sharing

We do not sell, rent, or trade personal information. Data may be shared only with:

  • Service providers (Supabase, OpenAI, Anthropic, Twilio, Resend, Postmark, and Sentry when error monitoring is configured) — processing data needed to operate the relevant features, subject to their privacy policies
  • Institutional compliance — if required by organizational policies, law, or legal process
  • Aggregate analytics — de-identified usage statistics for department leads

7. Your Rights

  • View and update your profile via the Profile page
  • Request deletion of your account by contacting administration (some contributed content may be retained anonymized)
  • Opt out of SMS by replying STOP or switching authentication method
  • Opt out of emails via notification preferences

8. Data Retention

Accounts are retained for the duration of your affiliation with your organization. Upon departure, accounts may be deactivated and data retained per institutional retention policies. Search logs and search-click events older than 90 days are deleted by scheduled maintenance. Feedback submitted about an answer is stored separately.

9. HIPAA Notice

CHARGE is an operational and educational tool, not designed for PHI as defined by HIPAA (45 CFR §160.103). Never enter patient-identifying information into any field.

Automated PHI detection screens supported free-text inputs for patterns consistent with MRNs, SSNs, phone numbers, and dates of birth. Supported image-upload workflows screen printed text that may contain PHI. Warnings and scans are safeguards, not a determination that content is de-identified under HIPAA. Review your content before submitting it, even when no warning appears.

If patient information is accidentally submitted, contact your administrator immediately.

10. Changes

We may update this policy to reflect platform changes or regulatory requirements. Material changes will be communicated through the platform.

11. Contact

Questions about this policy should be directed to daniel.seitz@eskenazihealth.edu.

← Terms of Use© 2026 CHARGE Healthcare LLC