Last updated: September 22, 2026
This policy describes how Infera Biosystems, Inc. handles information through our website, web application, API, and BioBase desktop application.
When you use Infera, we may collect the following information:
We use collected information to:
Your research data is yours. We do not sell it. We process it to provide the Service, including through the service providers described below, and disclose it when required by law. We use technical and organizational measures to protect information. No method of transmission or storage is completely secure.
You connect BioBase to your Infera account by signing in through your browser and approving access. You choose a project folder where the app works and writes its outputs. Signing out disconnects the device.
Your requests and conversation, and the contents of files a request needs, are sent to the selected language model, whether or not backup is on. Depending on the model, requests are processed by Anthropic, OpenAI, NVIDIA, or Amazon Web Services through Amazon Bedrock. Some models are developed by other companies. Model providers process requests under their own terms and may retain content. We do not guarantee that they delete content when a request completes.
An account administrator sets the default model. You can select a different model for a workspace.
Code the Data Agent writes runs in a cloud analysis environment operated for us by Modal. Files needed for a turn are copied there. With backup off, BioBase attempts to clear those copies after bringing the outputs back to your folder. If an output transfer fails, the cloud copy is kept for recovery. If clearing fails, the app reports the failure and tries again before the next analysis. Copies remain in the environment until clearing succeeds; removal is not guaranteed within a fixed time. This clearing applies only to workspaces with backup off.
Commands you run in BioBase's terminal run in your project folder. Terminal transcript recording and backup are currently unavailable.
Backup is off for a new workspace. With backup off, Infera does not save outputs as a cloud workspace. Your account shows the session as “Private workspace” while its actual title stays on your device. Infera still keeps operational records, including status, run timing, and token counts for billing.
Turning backup on uploads files in the workspace folder to Infera Cloud, except excluded credential stores, environment files, private keys, version-control directories, and log files. The exclusions do not cover every sensitive file: files ending in .key are uploaded. Review the folder before enabling backup. While the app is open, it syncs every 30 seconds and keeps the latest 30 versions per workspace and device.
Deleting a file on one device synchronizes the deletion to the cloud and your other devices. There is no trash. A file can be restored from version history while a retained version still contains it. An optional local-clearing setting removes verified local copies that backup can restore; this is separate from synchronized deletion.
Turning backup off brings the cloud conversation to your device and requests removal of cloud content. If removal cannot reach Infera, the app keeps the local copy and retries when the workspace is next opened. A pending request does not mean all stored copies have been erased.
We retain account information and content while your account is active and as needed to provide the Service. We retain some records longer where required or permitted by law, including billing records and evidence needed for legal obligations or disputes. Laboratory execution records, including audit entries, signatures, and results, are append-only; a deletion request requires review of their applicable retention obligations.
Infera Biosystems, Inc. handles account and personal-data deletion requests. Email hello@infera.bio to make a request. We may need to verify your identity and authority over the account. We respond within the time required by applicable law and explain any lawful exception that prevents deletion of particular data.
If we cannot determine which account an older record belongs to, we keep that record pending ownership review rather than risk deleting another customer's data. We tell you when this affects your request. Earlier storage versions and copies under a retention lock require separate removal when that storage permits it. A deletion request remains subject to identity review, lawful retention obligations, and storage cleanup.
We use service providers for hosting and storage, model processing, cloud analysis, payments, email delivery, voice features, sign-in, bot protection, web-application analytics, and website form submissions. They receive information needed for their function. Integrations you connect receive information you direct them to receive. Processing may take place in the United States or other countries where our providers operate.
Depending on applicable law, your rights include:
Email hello@infera.bio to exercise these rights. Requests are handled as described in section 7.
The web application uses analytics and session recordings to understand use of the Service. Its analytics configuration masks typed inputs in session recordings, removes query strings from the page views it records, and respects a browser's Do Not Track signal. The marketing website does not use an analytics service. Service providers may process information across the services they operate under their own policies.
BioBase is not a clinical system. Do not submit identifiable patient data.
We post changes on this page with an updated date. For a material change, we also notify account holders by email or through the Service.
For privacy-related inquiries, contact us at hello@infera.bio.