← Back to Home
Our Commitment: Lumen Innovations apps are designed with privacy as a core principle. We do not collect, store, or transmit Protected Health Information (PHI). Our apps are built to be HIPAA-exempt by design.
Overview
This Privacy Policy describes how Lumen Innovations ("we," "our," or "us") handles information in our applications: Lumenus (iOS app for procedure logging for medical trainees), CathDoc (iOS & Android app for CPT code management for cardiologists), Textify (Windows/macOS desktop app for PDF to text conversion for EHR documentation), Explify (Windows/macOS desktop app for AI-powered medical report explanations), and Systolic (iOS & Android app with web portal for remote patient monitoring of blood pressure).
All of our applications are designed to help healthcare professionals with documentation and billing workflows while ensuring patient privacy is never compromised.
Protected Health Information (PHI)
PHI Protection by Design: Lumenus, CathDoc, Textify, and Explify do not record patient names, medical record numbers, dates of birth, Social Security numbers, or any other identifying patient information. Systolic, Pulscribe, and YCAPortal are HIPAA-compliant healthcare platforms that do collect patient health data under appropriate safeguards and consent — see their individual sections below for full details.
How We Ensure PHI Protection
For Lumenus, CathDoc, Textify, and Explify:
- No Patient Identifiers: These apps do not include fields for patient names or identifying information
- Case ID System: Procedures are tracked using user-generated case IDs (e.g., "Case 001") rather than patient identifiers
- Date Range Only: Procedures are logged by date range (e.g., week or month), not specific dates, to prevent potential patient identification
- No EMR Integration: These apps do not connect to electronic medical records or hospital systems
For Systolic: Patient health data is collected with explicit consent under HIPAA-compliant protocols. See the Systolic section for full details on data handling, encryption, and access controls.
Lumenus - Procedure Logging App (iOS)
What Lumenus Stores
| Data Type |
Stored |
Purpose |
| User account (email, name) |
Yes |
Authentication and identification within training program |
| Procedure date range |
Yes |
Case logging by week/month (specific dates not stored to protect privacy) |
| Specific procedure date |
No |
Not stored - could be PHI when combined with other data |
| Procedure type |
Yes |
Training requirements tracking |
| Attending physician name |
Yes |
Attestation workflow |
| Facility/location |
Yes |
Multi-site training tracking |
| Operator role (primary/secondary) |
Yes |
Competency assessment |
| Duty hours/shift times |
Yes |
ACGME compliance tracking |
| Patient name or MRN |
No |
— |
| Patient date of birth |
No |
— |
| Social Security numbers |
No |
— |
Image Library & PHI Detection
Lumenus includes an optional image library feature for educational purposes. To protect patient privacy:
- On-Device PHI Detection: Images are automatically scanned for potential PHI (text overlays containing names, dates, MRNs) using on-device machine learning before upload
- Automatic Redaction: Detected PHI regions can be automatically redacted (blacked out) before saving
- Manual Review: Users are prompted to confirm images contain no PHI before sharing to the program's teaching library
- Crop Tools: Users can crop images to remove identifying information
- No Raw DICOM: The app does not accept DICOM files or extract embedded patient metadata
User Responsibility: While we provide PHI detection tools, users are ultimately responsible for ensuring any uploaded images do not contain patient identifiers. Always review images before sharing.
CathDoc - Billing Code Manager (iOS & Android)
What CathDoc Stores
| Data Type |
Stored |
Purpose |
| Case ID (user-entered) |
Yes (locally) |
Reference for billing workflow |
| Selected billing codes |
Yes (locally) |
Report generation |
| Selected ICD-10 codes |
Yes (locally) |
Indication documentation |
| Vessel/modifier selections |
Yes (locally) |
Accurate code documentation |
| RVU calculations |
Yes (locally) |
Reimbursement estimates |
| Patient name or MRN |
No |
— |
| Any patient identifiers |
No |
— |
HIPAA-Exempt by Design: CathDoc uses case IDs instead of patient names. No PHI is ever entered, stored, or transmitted. Reports generated by the app contain only billing codes, ICD-10 codes, and case IDs.
Report Sharing
When generating reports for billing purposes:
- Reports contain only case IDs, billing codes, ICD-10 codes, and RVU information
- No patient identifiers are included in generated reports
- Users are reminded to share reports only via secure, organization-approved email systems
- Report data is stored locally on the device only
Textify - PDF to Text Converter (Windows/macOS)
Complete Local Processing: Textify is a desktop application that runs entirely on your computer. No data is ever transmitted to external servers. All PDF processing happens locally on your machine.
What Textify Does NOT Store or Collect
| Data Type |
Collected |
Notes |
| PDF file contents |
No |
Files are processed in memory only; nothing is saved |
| Extracted text |
No |
Text is displayed for copy/paste but not stored |
| Patient names or identifiers |
No |
No PHI is ever collected or transmitted |
| Usage analytics |
No |
No tracking, telemetry, or analytics |
| User accounts |
No |
No login or account required |
| Internet connection |
No |
App works completely offline |
How Textify Works
- Local Processing Only: When you open a PDF, it is processed entirely on your computer using local resources
- No Cloud Upload: Your documents are never uploaded to any server or cloud service
- No Internet Required: Textify works completely offline with no network connectivity needed
- No File Retention: The application does not save, cache, or retain any files or extracted text after you close the application
- No Telemetry: We do not collect usage statistics, crash reports, or any other data from the application
Privacy by Architecture: Textify was intentionally designed with no network capabilities. It cannot transmit data even if it wanted to. Your documents stay on your computer.
Explify - AI-Powered Report Explanations (Windows/macOS)
PHI Scrubbing Before AI Processing: Explify automatically detects and removes Protected Health Information (PHI) from medical reports before any AI processing occurs. Patient identifiers are never sent to AI services.
How Explify Protects Patient Privacy
- On-Device PHI Detection: Before any report is sent to AI services, Explify scans and removes patient names, dates, MRNs, and other identifiers
- No PHI to AI: Only de-identified clinical content (measurements, findings, impressions) is sent to AI for explanation generation
- Local Processing: PHI scrubbing happens entirely on your computer before any network transmission
- No Data Retention: Reports are not stored after processing; explanations are generated and displayed without saving original documents
What Explify Uses
| Data Type |
Stored |
Purpose |
| User API key |
Yes (locally) |
Stored securely on your device for AI service access |
| Teaching points |
Yes (cloud) |
Personalized AI instructions you create are synced across devices |
| Report history |
Yes (cloud) |
De-identified summaries only; original reports with PHI are never stored |
| Template settings |
Yes (cloud) |
Letter templates and preferences |
| Patient names or MRNs |
No |
Removed before AI processing; never stored or transmitted |
| Original PDF/images |
No |
Processed in memory only; not retained after session |
AI Processing & Third-Party Services
- Your API Key: Explify uses your own API key (OpenAI, Anthropic, or other supported providers) for AI processing
- De-identified Content Only: Only scrubbed clinical content is sent to AI providers
- Provider Privacy: AI providers' privacy policies apply to the de-identified content they process. See OpenAI Privacy Policy or Anthropic Privacy Policy
User Responsibility: While Explify provides automated PHI scrubbing, users should review generated content before sharing with patients to ensure accuracy and appropriateness for clinical use.
Systolic - Remote Patient Monitoring (iOS/Android & Web Portal)
HIPAA-Compliant Healthcare Platform: Systolic is designed for Remote Patient Monitoring (RPM) of blood pressure and weight. Patient health data is collected with explicit consent and stored securely in compliance with healthcare privacy regulations.
Data Collection with Patient Consent
Unlike our other apps which are designed to be HIPAA-exempt, Systolic is a healthcare platform that collects patient health information. This data is collected only after patients provide informed consent during onboarding.
What Systolic Collects
| Data Type |
Collected |
Purpose |
| Blood pressure readings |
Yes |
Core RPM functionality for patient monitoring |
| Heart rate |
Yes |
Cardiovascular health monitoring |
| Weight entries |
Yes (optional) |
Weight management, heart failure dry weight monitoring, and AI-powered trend analysis |
| HealthKit data (weight) |
Yes (optional) |
Syncing weight data from Apple Health for comprehensive tracking |
| Patient name |
Yes |
Patient identification within healthcare context |
| Phone number |
Yes |
Authentication and reminders |
| Date of birth |
Yes |
Patient identification and age-appropriate care |
| Medications |
Yes (optional) |
Care coordination and medication management |
| Practice affiliation |
Yes |
Connecting patients with their healthcare providers |
How Patient Data is Protected
- Encryption: All data is encrypted at rest and in transit using industry-standard encryption
- Access Controls: Role-based access ensures only authorized staff can view patient data
- Audit Logging: All data access and modifications are logged for compliance and security
- Consent Workflows: Explicit patient consent is obtained for data collection and RPM enrollment
- Practice Isolation: Patient data is segregated by practice; providers can only access their own patients
Data Sharing
- Patient data is shared only with the healthcare practice the patient is enrolled with
- Data is never sold to third parties or used for advertising
- De-identified aggregate data may be used for quality improvement purposes
Healthcare Provider Responsibility: Practices using Systolic are responsible for maintaining their own HIPAA compliance, including Business Associate Agreements and appropriate use policies.
Data Storage & Security
Lumenus
- Cloud Storage: Case logs and account data are stored securely using Google Firebase with encryption at rest and in transit
- Authentication: Secure sign-in via Apple Sign-In, Google Sign-In, or email/password with Firebase Authentication
- Program Isolation: Data is segregated by training program; users can only access their own program's data based on role permissions
CathDoc
- Local Storage Only: All data is stored locally on your device using standard iOS secure storage
- No Cloud Sync: CathDoc does not sync data to any cloud services
- No Account Required: The app functions without user accounts or login
Textify
- No Storage: Textify does not store any data—files are processed in memory and discarded
- No Network Access: The application has no network capabilities and works entirely offline
- No Account Required: The app functions without user accounts, login, or registration
Explify
- Cloud Storage: User account, teaching points, preferences, and de-identified history are stored securely using Supabase with encryption at rest and in transit
- Local API Key Storage: Your AI provider API key is stored securely on your device only; it is never transmitted to our servers
- PHI Scrubbing: Original documents containing PHI are processed in memory only and never stored or transmitted; only de-identified content is sent to AI services
- Authentication: Secure sign-in via email/password authentication
Systolic
- Cloud Storage: Patient health data is stored securely using Google Firebase with encryption at rest and in transit
- Authentication: Phone number verification via OTP (one-time password) for patients; email/password for practice staff
- Practice Isolation: Data is segregated by practice; each practice can only access their own patients' data
- Audit Trail: All data access and modifications are logged with timestamps, user IDs, and IP addresses
- Biometric Lock: Patients can enable Face ID/Touch ID to protect app access on their device
Pulscribe - AI Medical Scribe (Web Application)
Audio Processing & AI Transcription: Pulscribe processes audio recordings of physician-patient encounters. Audio is streamed to Deepgram for transcription and encounter content is sent to AWS Bedrock (HIPAA-compliant mode) for AI note generation. Pulscribe is designed to minimize PHI retention — audio is not permanently stored after processing.
Data Collected by Pulscribe
| Data Type |
Collected |
Purpose |
| Audio recordings (encounter) |
Temporarily |
Transcription via Deepgram — not retained after transcription |
| Encounter transcripts |
Yes |
Note generation and encounter history for physicians |
| Patient name (in transcript) |
May be present |
Part of captured conversation — stored in encounter record |
| Clinical content (HPI, A&P, medications) |
Yes |
AI-generated clinical documentation |
| Physician account credentials |
Yes |
Authentication — bcrypt hashed passwords |
| Practice and provider information |
Yes |
Multi-provider workflow and practice management |
How Pulscribe Protects PHI
- HIPAA-Compliant AI Processing: All LLM calls use AWS Bedrock in HIPAA Business Associate Agreement (BAA) mode
- Deepgram Transcription: Audio is streamed via secure WebSocket; PHI handling is governed by Deepgram's BAA
- No Audio Retention: Audio recordings are processed and not permanently stored on our servers
- Encrypted Data Storage: Encounter data stored in JSON with server-side security
- Access Controls: JWT token authentication, bcrypt password hashing, rate limiting on all API endpoints
- Audit Logging: All API access logged with user ID, timestamp, and IP address
- PHI Cache Prevention: HTTP headers prevent PHI from being cached by browsers or proxies
YCAPortal - Cardiology Imaging Platform (Web)
DICOM Medical Imaging Platform: YCAPortal stores and manages DICOM cardiac imaging studies (echocardiograms, CT scans, etc.) containing patient health information. Data is handled under HIPAA-compliant protocols with AWS infrastructure.
Data Collected by YCAPortal
| Data Type |
Collected |
Purpose |
| DICOM imaging studies |
Yes |
Core platform functionality — cardiac imaging management |
| Patient name and date of birth |
Yes (from DICOM metadata) |
Patient identification extracted from imaging files |
| Echocardiogram measurements and findings |
Yes |
Structured clinical reporting |
| Physician account credentials |
Yes |
Authentication via AWS Cognito with MFA |
| Study access and sharing logs |
Yes |
HIPAA audit trail requirements |
How YCAPortal Protects PHI
- AWS Infrastructure: Studies stored encrypted on AWS S3 with server-side encryption
- Cognito MFA: AWS Cognito authentication with multi-factor authentication for all user accounts
- Role-Based Access: Admin and user roles restrict data access to authorized personnel only
- Audit Logging: All PHI access events logged with user ID, timestamp, and action for HIPAA compliance
- Secure Sharing: Shared study links are password-protected with limited access scope
- Practice Isolation: Studies are isolated per practice — cross-practice access is not permitted
Data We Do NOT Collect
Lumenus, CathDoc, Textify, and Explify do not collect (note: Systolic, Pulscribe, and YCAPortal are healthcare platforms that do collect patient data under HIPAA-compliant protocols—see their sections above):
- Patient names, dates of birth, or medical record numbers
- Social Security numbers or insurance information
- Precise device location or GPS data
- Contacts, photos (except user-initiated uploads in Lumenus), or other personal files
- Browsing history or data from other apps
- Advertising identifiers for ad targeting
Third-Party Services
Lumenus
- Firebase (Google): Authentication, database, and cloud storage. See Firebase Privacy Policy
- Apple/Google Sign-In: Optional authentication providers
CathDoc
- CathDoc does not use third-party analytics, advertising, or cloud services
Textify
- Textify does not use any third-party services, analytics, advertising, or cloud connectivity
Explify
- Supabase: Authentication, database, and cloud storage for user accounts and preferences. See Supabase Privacy Policy
- AI Providers (User's Choice): De-identified report content is sent to your chosen AI provider (OpenAI, Anthropic, etc.) using your own API key. See respective provider privacy policies
Systolic
Pulscribe
- Deepgram: Real-time speech-to-text transcription of encounter audio via secure WebSocket. See Deepgram Privacy Policy
- AWS Bedrock (Amazon): HIPAA-compliant LLM processing for clinical note generation, coding suggestions, and patient summaries. See AWS Privacy Policy
YCAPortal
Birdog
- Firebase (Google): Authentication, Firestore database, and cloud storage for trainer and client data. See Firebase Privacy Policy
- Stripe: Trainer subscription billing and client session pack payments. See Stripe Privacy Policy
- Twilio: Dedicated SMS phone numbers per trainer for client communications. See Twilio Privacy Policy
Your Rights
You have the right to:
- Access: Request a copy of your data stored in our systems
- Deletion: Request deletion of your account and associated data
- Correction: Update or correct your account information
- Export: Export your procedure logs (Lumenus) in standard formats
To exercise these rights, contact us at privacy@lumeninnovations.com
Children's Privacy
Our apps are intended for use by medical professionals and trainees. We do not knowingly collect information from children under 13 years of age.
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify users of significant changes through the app or via email. Continued use of our apps after changes constitutes acceptance of the updated policy.
Contact Us
If you have questions about this Privacy Policy or our data practices, please contact us:
Last Updated: March 13, 2026