Privacy Policy

Effective date: November 11, 2026.

Scope

This policy covers DischargeNow's AWS development workspace and optional development sign-in text messages. The development workspace is limited to authorized test users and synthetic resident information. Do not enter real patient or resident information. This is not a production healthcare privacy notice, a HIPAA Notice of Privacy Practices, or a representation of HIPAA readiness. It does not describe unreviewed data collection on the separate public website.

Who we are

DischargeNow LLC, a privately owned for-profit company 522 W Riverside Ave, Ste N, Spokane, WA 99201, United States Website: https://dischargenow.com Privacy and support contact: Emeka Nwankwo Email: ccnwankwo91@gmail.com Telephone: +1 786-218-3332

Information covered

We process account identity and contact information, organization memberships and roles, authentication and security events, and synthetic application records. If you voluntarily enroll in SMS verification, we also process your mobile number, consent and withdrawal records, verification requests, and delivery or opt-out information made available by our messaging providers. Technical information can include IP addresses, request identifiers and timestamps used for security and service operation.

Authentication providers necessarily process passwords and one-time codes to authenticate you. Our application must not record passwords, authenticator setup keys, one-time codes or tokens in application logs. Do not send them to our support contact.

How information is used

We use this information to authenticate authorized users, enforce organization access, deliver requested verification codes, operate the development workspace, prevent abuse, investigate errors and maintain security and consent records. SMS is for sign-in verification, not advertising or clinical communications. Text messages must not contain resident names, diagnoses, referral details or other clinical information.

Planned SMS program — not currently available

SMS verification is not yet active. No enrollment or messages are authorized by this notice. The following SMS provisions describe the planned program and apply only if it is separately launched after its controls are verified. SMS enrollment requires a separate, affirmative consent action. Acceptance of general terms alone is not SMS consent. SMS is optional; the existing authenticator method remains available. Message frequency varies with your requests. Message and data rates may apply. Reply STOP to opt out or HELP for assistance, or contact us using the details above. A carrier or messaging platform may send a confirmation or help response. Opting out of SMS does not close your account or remove your authenticator method. Re-enrollment requires a new consent process that respects carrier opt-out rules.

Sharing and mobile consent

We do not sell or rent mobile numbers or share mobile information with third parties or affiliates for marketing or promotional purposes. Mobile opt-in data and consent are not shared for their independent use. We disclose only information necessary for contracted service providers, such as AWS, messaging delivery providers and mobile carriers, to operate authentication, deliver messages and honor opt-outs on our behalf. This service processing is not permission for their independent marketing. We may disclose information when legally required or necessary to protect users and the service, subject to applicable law. No general sharing provision authorizes sale or marketing use of mobile opt-in data.

Storage and safeguards

The development application uses AWS services for authentication, APIs, operational storage and security logging. Messaging delivery also involves telecommunications providers. We use access restrictions, organization authorization, encryption and audit controls appropriate to the approved development design. No system can guarantee absolute security. Choosing AWS does not itself establish HIPAA compliance.

Retention and requests

Current development records remain subject to existing security and preservation requirements. The numerical schedule below is the approved design for the future SMS program, not a claim that automated deletion, suppression synchronization or backup-expiry controls are deployed. Those controls must be verified before SMS enrollment starts.

Planned SMS retention schedule:

- Active enrolled mobile details: while enrolled, then remove unnecessary live details within 30 days after withdrawal. Existing development accounts and authenticator methods remain separate. - Incomplete enrollment: expire after 24 hours and remove pending phone details within 7 days. - SMS delivery/request metadata: 90 days; no verification codes or message bodies in application logs. Non-identifying monthly usage totals: 12 months. - Consent and withdrawal evidence: enrollment duration plus 4 years, limited to the information necessary to establish consent history. - Minimal opt-out suppression: while the program operates, reviewed annually; remove within 90 days after permanent program closure unless a documented legal hold applies. - SMS support/privacy cases: 2 years after closure. Routine SMS security logs: 90 days; necessary incident evidence up to 1 year after case closure. - Proposed backup expiry: no more than 35 days after active deletion, with deletions and suppression reapplied before restored data is used.

These are planned operational periods, not statutory minimums or a guarantee about independent carrier records. Protected historical evidence and legal holds require documented exceptions. Existing infrastructure retention is not changed by publishing this notice. No real resident information is permitted in development.

Contact Emeka Nwankwo at ccnwankwo91@gmail.com to request access, correction, deletion or SMS withdrawal. Do not email passwords or verification codes. We verify requests through an appropriate authenticated channel. Our proposed service targets are acknowledgement within 7 calendar days and resolution within 30 calendar days, subject to applicable deadlines. Necessary consent, suppression, security or legal-hold evidence may be retained; we will explain any applicable exception.

Audience and changes

This development program is for authorized adult facility and provider staff, not children. We will identify the effective date when this notice is published and date subsequent revisions. Material changes to SMS purpose or consent require appropriate notice and renewed consent where necessary; an updated policy is not permission to send unrelated messages.

Related SMS Terms: https://policies.dischargenow.com/sms-terms