Privacy Policy

Effective Date: April 8, 2026  |  Last Updated: November 12, 2026

1. Introduction

VeriOp.ai ("Company," "we," "us," or "our") is committed to protecting the privacy and security of the information we collect and process.

VeriOp.ai is operated by VeriOp AI, LLC, a Florida limited liability company formerly named MyPreOp.Ai, LLC (the same legal entity; name changed July 20, 2026). The Service was previously offered as MyPreOp.ai, and mypreop.ai now redirects to veriop.ai. References in this policy to VeriOp.ai, the Company, MyPreOp.ai, or MyPreOp.Ai, LLC all mean this one entity, and this is the only privacy policy for either name. This Privacy Policy describes how we collect, use, disclose, and safeguard information when you use our AI-powered pre-operative clearance platform (the "Service").

We comply with the Health Insurance Portability and Accountability Act of 1996 ("HIPAA"), the HITECH Act, applicable state privacy laws, and all other relevant federal and state regulations governing protected health information ("PHI").

2. Information We Collect

2.1 Account Information

When you register for the Service, we collect your name, email address, NPI number (optional), and payment information processed through Stripe.

2.2 Protected Health Information (PHI)

Through your use of the Service, you may input patient health information including but not limited to: medical histories, medication lists, laboratory results, vital signs, diagnoses, and surgical procedure details. All PHI is processed in accordance with our Business Associate Agreement (BAA) and HIPAA regulations.

2.3 De-Identified Health Data

With your consent, we create de-identified versions of patient data processed through the Service. De-identification is performed in strict compliance with the HIPAA Safe Harbor method under 45 CFR § 164.514(b)(2). All 18 categories of identifiers specified by HIPAA are removed or transformed, including:

  • Names (patient, provider, and family)
  • Geographic data smaller than state level (ZIP codes truncated to 3 digits)
  • All dates (except year) related to an individual
  • Phone numbers, fax numbers, email addresses
  • Social Security numbers
  • Medical record numbers, health plan beneficiary numbers
  • Account numbers, certificate/license numbers
  • Vehicle identifiers, device identifiers and serial numbers
  • Web URLs, IP addresses
  • Biometric identifiers (fingerprints, voiceprints)
  • Full-face photographs and comparable images
  • Any other unique identifying number, characteristic, or code

Additionally, ages 90 and over are aggregated into a single "90+" category, and all remaining ages are grouped into 5-year ranges to provide additional privacy protection beyond minimum HIPAA requirements.

3. How We Use Information

3.1 Service Delivery

We use PHI solely to provide the pre-operative clearance analysis service as directed by our authorized users (healthcare providers and surgical coordinators) under the terms of our BAA.

3.2 De-Identified Data Usage

Under HIPAA, once data has been properly de-identified in accordance with 45 CFR § 164.514(b), it is no longer considered PHI and is not subject to HIPAA restrictions. With your explicit consent provided at account registration, we use de-identified data for:

  • Healthcare Research: Contributing to medical knowledge, procedure safety studies, and population health analytics
  • Quality Improvement: Analyzing trends in pre-operative assessments to improve our AI models and service quality
  • Aggregate Analytics: Producing statistical reports on procedure types, comorbidity prevalence, clearance outcomes, and medication trends
  • Licensed Data Products: Making de-identified, aggregated datasets available to qualified healthcare researchers, academic institutions, pharmaceutical companies, and medical device manufacturers under strict data use agreements

3.3 What We Never Do

  • We never sell PHI. We disclose PHI only as our BAA and HIPAA permit
  • We never attempt to re-identify de-identified data
  • We never combine de-identified data with external datasets in a manner that could enable re-identification
  • We never use PHI for marketing, advertising, or any purpose unrelated to the Service

4. Analytics and Session Recording

To improve the product, we use Mixpanel to collect anonymized usage analytics (page views, button clicks, feature adoption, flow completion) and may record anonymized user interaction sessions (“session replay”) on non-clinical pages.

Never recorded:

  • Any page that displays patient records (patient detail pages)
  • The clearance analysis flow once a chart has been uploaded
  • The contents of any form field — every input, textarea, and password field is masked at the browser level before any data is transmitted

What is recorded on general pages (signup, dashboard home, settings, pricing, blog, validation study):

  • Cursor movements, clicks, page navigations, and general element interactions
  • All text content remains masked in recordings
  • Browser, device, and viewport size (for debugging display issues)

How to opt out: Enable your browser’s “Do Not Track” (DNT) setting. We honor DNT requests and will not record sessions for browsers that send that header.

We do not sell this analytics data. Mixpanel processes it solely as our service provider under their privacy policy. Analytics data is strictly separate from the PHI protected under our HIPAA-covered safeguards described in sections 2 and 5.

5. Data Security

We implement industry-standard administrative, technical, and physical safeguards including:

  • AES-256 encryption at rest for all stored data (AWS DynamoDB)
  • TLS 1.2+ encryption for all data in transit
  • JWT-based authentication with secure token management
  • Role-based access controls ensuring users access only their own patient data
  • Automated de-identification pipeline with no human access to raw PHI during processing
  • Separate storage tables for PHI and de-identified data with distinct access controls
  • Regular security monitoring and logging

6. Data Retention

PHI: Patient records are retained for the duration of your active subscription plus 30 days after account termination, after which they are permanently deleted. Users may delete individual patient records at any time.

De-Identified Data: Because de-identified data contains no PHI and cannot be linked to any individual, it may be retained indefinitely for research and analytics purposes as permitted under HIPAA.

7. Third-Party Services

We use the following third-party services to operate the platform:

  • Amazon Web Services (AWS): Cloud infrastructure, database hosting (DynamoDB), and email delivery (SES)
  • Anthropic (Claude AI): AI-powered medical analysis — PHI is processed per Anthropic's HIPAA-compliant API terms
  • Stripe: Payment processing — we do not store credit card information

8. Your Rights

You have the right to:

  • Access and review your account information
  • Delete patient records you have entered
  • Request account termination and data deletion
  • Withdraw consent for de-identified data collection (note: previously de-identified data cannot be recalled as it contains no link to your identity or your patients' identities)
  • Receive a copy of your data in a portable format upon request
  • File a complaint with the HHS Office for Civil Rights if you believe your privacy rights have been violated

9. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email to registered users at least 30 days before they take effect. Continued use of the Service after the effective date of changes constitutes acceptance of the updated policy.

10. SMS / Text Messaging Communications

If you are a patient and you opt in to text messages — by checking the separate, unchecked SMS consent box that reads "Text me a reminder before my telehealth clearance visit" when you set up your account after booking a visit, and typing the mobile number you want texts sent to — VeriOp.ai may send you a reminder text shortly before that visit. Licensed providers in the VeriOp network may separately opt in to a text alert when a new clearance request is available. A public description of the program and the consent step is at www.veriop.ai/sms. Providing your mobile number for text messages is optional and is never a condition of any purchase or of using the Service.

10.1 Types of messages

Text messages are transactional only. A patient receives a single reminder about 30 minutes before a scheduled telehealth clearance visit. Licensed providers receive an alert when a new clearance request is available. We do not send marketing or promotional text messages.

Texts contain no health information. A patient reminder carries no name, procedure, surgeon, date, or clinical instruction. Surgery-date reminders, fasting instructions, clearance results, and document requests are sent by email, never by text. Once a text is delivered, its record is deleted from our messaging provider's systems, so the provider retains no message content.

10.2 Message frequency

Message frequency varies with your bookings; typically one text per visit.

10.3 Message and data rates

Message and data rates may apply, depending on your mobile carrier and plan.

10.4 Opt-out and help

You can cancel text messages at any time by replying STOP to any message. After you reply STOP, we will send a one-time confirmation and you will receive no further texts. For help, reply HELP or contact us at support@veriop.ai.

10.5 We do not share your mobile information

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. No mobile information — including your phone number and your SMS opt-in and consent — will be shared with, or sold to, any third parties or affiliates for marketing or promotional purposes. Your mobile number and opt-in are used only to deliver the messages you asked for. This consent is separate from any other consent (such as email marketing) and from any purchase.

11. VeriOp Agent Browser Extension

VeriOp Agent is a Google Chrome extension for staff of practices that subscribe to the Service. It opens in Chrome's side panel and lets a signed-in user send a patient's documents to VeriOp.ai and bring the result back into the EHR. It works only for a person who signs in with their own VeriOp account, at a practice whose subscription is active.

11.1 What the extension handles

  • Patient documents and health information that the user chooses to send: files the user drags into the panel, a document link the user drags in, a PDF open in the current tab, or a screenshot of the visible part of the current tab. When the user asks to put a result into the EHR, the extension checks only which field the user clicked or how many upload boxes the page has. It reads a page or document only when the user takes one of these actions. It does not read browsing history and does not run in the background on any site.
  • A sign-in key, created for the person when they sign in to the extension through VeriOp's normal sign-in page, and stored only in the browser's local extension storage on that computer so they stay signed in. The extension never sees the person's VeriOp password. Signing out of the extension turns the key off and removes it.
  • Settings, such as language, kept in the browser's local extension storage, and the identifier of a review in progress, kept only until Chrome is closed. If the extension cannot put a result into the page, it copies the result to the user's clipboard so they can paste it. Removing the extension from Chrome deletes everything it stored on that computer.

11.2 Where it goes

Documents are sent directly from the browser to VeriOp.ai, either to our API or to our secure cloud file storage, over encrypted connections. Once received, they are protected and retained like any other upload to the Service, under sections 5 and 6 and our Business Associate Agreement with the practice. When the user asks, the extension places the result back into the EHR page that is open in their browser, as text in a field the user clicked or as a PDF in that page's own upload box.

To read a document from an EHR or other website, the extension asks for the user's permission for that site through Chrome's own permission prompt, only when the user drags a document link into the panel or adds the PDF open in the current tab. It then downloads that one document using the user's existing sign-in to that site, the same way the browser would. The extension never reads, stores, or sends the user's EHR password or sign-in cookies to VeriOp.ai. The user can withdraw a site's permission at any time in Chrome's extension settings.

11.3 Limited use

Information the extension handles is used only to provide the Service to the practice. It is not used for the purposes in section 3.2, and it is never included in de-identified datasets, Licensed Data Products, or anything shared with researchers or other outside parties. We do not sell it, use it for advertising, or use it to determine credit or lending eligibility. We transfer it only as needed to provide the Service (for example, to the service providers in section 7), to comply with law, to protect against fraud, abuse or security threats, or as part of a merger, acquisition or sale of assets, and in every case only within the limits of our Business Associate Agreement with the practice. The extension contains no analytics or advertising code. VeriOp.ai's use of information received from the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

12. Contact Us

For privacy-related questions, concerns, or requests:

VeriOp.ai
Email: support@veriop.ai
Privacy Officer: Dennis Diaz