HONEST DATA HANDLING. NO TRAINING ON YOUR DATA. MEDICAL PRIVACY MODE · FAILED RUNS AUTO-DELETED · TRANSPARENT THIRD-PARTY DISCLOSURE · TLS 1.2+ · AES-256 AT REST HONEST DATA HANDLING. NO TRAINING ON YOUR DATA. MEDICAL PRIVACY MODE · FAILED RUNS AUTO-DELETED · TRANSPARENT THIRD-PARTY DISCLOSURE · TLS 1.2+ · AES-256 AT REST
PRIVACY POLICY

Our Commitment to Privacy

OmniBioFex.Cloud is built with strict data minimization principles. Because the platform is not clinical-grade and is intended only for educational and research use, we designed our infrastructure to keep uploaded medical data private and controlled by you.

No training on your data Deletion on request Last updated: 2026-09-17

1. How We Handle Uploaded Images

We designed OmniBioFex to minimize data retention. Here is exactly what happens when you upload a scan.

WHAT ACTUALLY HAPPENS

UPLOADS ARE STORED IN YOUR PRIVATE FOLDER

When you run a report, the image you attach is uploaded to a private Cloud Storage folder scoped to your account. Only you can read it via the authenticated app.

WHAT ACTUALLY HAPPENS

FAILED ANALYSES ARE CLEANED UP

If the inference step fails, the uploaded image is deleted immediately and any wallet charge is refunded automatically.

WHAT ACTUALLY HAPPENS

DELETION ON REQUEST

You may request deletion of your account and all stored history at any time by emailing privacy@omnibiofex.cloud. Requests are completed within 30 days.

WHAT ACTUALLY HAPPENS

NO TRAINING

We never use your uploaded content to train, fine-tune, or otherwise improve any model.

IMPORTANT — OmniBioFex is not a HIPAA-compliant or clinically certified system. Do not upload identifiable patient data unless you have independent legal authority to do so under your local jurisdiction.

2. Information We Collect

We collect the minimum amount of information required to operate the service.

01

AUTHENTICATION DATA

Google OAuth provides your email address to create your account ID. We do not store passwords or phone numbers.

02

PATIENT METADATA

When you generate a report, you may optionally provide a patient name, age, and sex. Stored alongside your report in your private history.

03

REPORT OUTPUT

The structured clinical report is stored in Firestore to populate your historical dashboard.

04

CHAT HISTORY

Follow-up chat messages, model replies, and citation metadata are stored under your account so you can resume any session.

3. Third-Party Infrastructure

OmniBioFex is built on established cloud infrastructure. Each provider is governed by its own privacy policy.

ProviderPurposeData Retained
GroqOmniBioFex 1.0 47B inferenceSee Groq's inference privacy policy at groq.com/privacy (no images retained for training)
Google FirebaseAuthentication & FirestoreEmail, patient metadata, report text
RazorpayPayment ProcessingBilling details (no medical data)
ResendTransactional emailEmail address only
NOTE — Razorpay receives only billing information — no images, patient data, or report outputs are ever transmitted to our payment processor.

4. Cookies & Analytics

A

SESSION COOKIES

Required to keep you logged in after Google OAuth. Strictly necessary.

B

NO TRACKING PIXELS

We do not use advertising pixels, cross-site tracking cookies, or third-party analytics.

C

AGGREGATE METRICS ONLY

Any analytics we collect are aggregate, anonymized, and used solely to monitor uptime and error rates.

D

MEDICAL PRIVACY MODE

A client-side toggle. When enabled, chat previews are redacted in your sidebar and the terminal signs you out after 15 minutes of inactivity. No server-side tracking.

5. Your Rights

01

ACCESS

Request a copy of the account data we hold for you.

02

DELETION

Request full deletion of your account, uploaded images, and stored report history. Completes within 30 days.

03

CORRECTION

Request correction of inaccurate account information.

EXERCISING YOUR RIGHTS — Contact privacy@omnibiofex.cloud from the email address associated with your account. We respond to all verified requests within 30 days.

6. Data Security

SAFEGUARD

TRANSPORT ENCRYPTION

All traffic between your browser, our servers, Groq, and Google Cloud is encrypted in transit using TLS 1.2 or higher.

SAFEGUARD

ACCESS CONTROL

Production credentials and Firebase access rules are restricted to a minimal set of authorized engineers under the VantyrixTek organization.

YOUR RESPONSIBILITY — You are responsible for ensuring that any data you upload complies with your local privacy regulations.

7. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be announced on the main page and reflected in the "Last updated" date above.