OmniBioFex.Cloud is built with strict data minimization principles. Because MedGemma 1.5 4B IT is not clinical-grade and is intended only for educational and research use, we designed our infrastructure to keep your uploaded medical data ephemeral by default.
Medical files uploaded to the platform are processed using ephemeral storage. Data is scrubbed from our servers immediately following the completion of the AI inference block.
Your uploaded images, DICOM volumes, PDFs, and histopathology slides are held in memory only for the duration of the inference request. Once the model returns a response, the original upload is discarded.
We do not use your uploaded medical content to train, fine-tune, or otherwise improve MedGemma 1.5 4B IT or any downstream model. Model improvements come from the upstream Google MedGemma family only.
We collect the minimum amount of information required to operate the service, enforce fair usage, and provide you with a functional dashboard.
Google OAuth provides your email address to create your account ID. We do not store passwords, phone numbers, or any other personal identifiers beyond what Google OAuth returns.
The JSON text output is stored in Firebase Firestore to populate your historical dashboard. Original uploads are never stored — only the model's text response.
We track API call frequency to enforce plan limits (Community: 10/month, Pro: unlimited, API: pay-per-request). No content of your requests is logged.
OmniBioFex.Cloud is built on top of established cloud infrastructure. Each provider below is governed by its own privacy policy and terms of service.
| Provider | Purpose | Data Retained |
|---|---|---|
| Google Firebase | Authentication & Firestore | Email, JSON text output |
| Vertex AI | MedGemma 1.5 4B IT Inference | None (processed in memory) |
| Razorpay | Payment Processing | Billing details (no medical data) |
We implement industry-standard safeguards to protect the limited data we do retain. However, no system is perfectly secure, and MedGemma 1.5 4B IT is not a clinical-grade system.
All traffic between your browser, our servers, and Vertex AI is encrypted in transit using TLS 1.2 or higher.
Production credentials and Firebase access rules are restricted to a minimal set of authorized engineers under the VantyrixTek organization.
No system is perfectly secure — and this is not a clinical-grade platform.
You are responsible for ensuring that any data you upload complies with your local privacy regulations. Do not upload identifiable patient data unless you have independent legal authority to do so.
Because we retain very little data, most privacy requests can be fulfilled immediately. You have the following rights regarding your account data.
Request a copy of the account data we hold for you — this is limited to your email address and the JSON text outputs stored in your Firestore history.
Request full deletion of your account and its stored inference history. Deletion is irreversible and completes within 30 days.
Request correction of inaccurate account information. Since we only store your email, this is typically limited to updating your OAuth-linked address.
OmniBioFex.Cloud is not intended for use by anyone under 18. We do not knowingly collect personal information from minors. If we become aware of such data, we delete it.
Your email and stored JSON outputs are retained while your account is active. After account deletion, all data is removed within 30 days. Aggregate usage metrics may persist longer, but contain no personal identifiers.
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. Continued use of OmniBioFex.Cloud after changes constitutes acceptance.
Reach out to our team, or review the full terms governing MedGemma 1.5 4B IT access on OmniBioFex.Cloud.