Privacy Policy
Effective September 20, 2026. This policy covers emrfi.com, the provider portal, the patient payment pages, and the EMRfi API, all operated by Belmont Labs Inc.
Who this applies to
Providers (hospitals, practices, and billing organizations) that use EMRfi, and patients who open a payment page a Provider sent them.
What we collect
From Providers
Organization name, contact name, work email and phone, branding (logo, color, display name), API activity logs, and the identifiers Stripe assigns to your account. Bank details and identity documents go to Stripe directly and are not stored by EMRfi.
About patients
Only what a pay-over-time session needs: the balance amount, the Provider's reference numbers, an optional description, an optional email address the Provider supplies, and the outcome (funded, expired, cancelled). We do not collect names, addresses, dates of birth, Social Security numbers, diagnoses, or any other health information, and we instruct Providers not to send them. The payment plan application itself is completed with Affirm, under Affirm's privacy policy; payment details are collected by Stripe under Stripe's privacy policy. EMRfi never sees card numbers, bank numbers, or credit information.
Automatically
IP address, browser type, and request logs, kept for security and troubleshooting.
How we use it
- To create payment pages, route funds to the right Provider, and tell the Provider when a session funds.
- To operate, secure, and support the service and to prevent fraud.
- To send Providers service messages, such as verification codes and status notices.
We do not sell personal information and do not use it for advertising.
Who we share it with
- Stripe, to process payments and verify Providers.
- Affirm, to offer and service payment plans.
- Service vendors that host our servers and deliver email and text messages, bound to use data only for us.
- The Provider who created the session, who receives the outcome and identifiers they supplied.
- Authorities or others when the law requires it, or to protect rights and safety.
Cookies and local storage
We use essential cookies and browser storage to keep the provider portal signed in and to remember your cookie choice. Stripe sets cookies on payment pages for fraud prevention. We do not use advertising cookies. Optional analytics cookies load only if you choose "Yes, allow" in the banner; you can change that any time with "Cookie choices" in the footer.
Retention
Session records are kept for seven years to meet payment and tax record-keeping obligations. Provider account data is kept while the account is open and for the same period after. Logs are kept for 90 days.
Security
All traffic is encrypted in transit. Patient contact details are encrypted at rest with AES-256-GCM. API keys are stored as one-way hashes. Database access is restricted to the application server. Webhooks are signed so Providers can verify they came from us. See Security for details.
Your choices and rights
Patients can ask us what we hold about a session by contacting their Provider or us with the payment link. Providers can update or delete their account data from the portal or by request. Residents of Texas, California, and other states with privacy laws may have rights to access, correct, or delete personal information; write to us and we will respond within the time the law allows. We do not knowingly collect information from anyone under 18.
Changes
We will post changes here and, for material changes, notify Providers in the portal at least 30 days ahead.
Contact
Belmont Labs Inc. · contact form