Security and deployment: run Databasin in your own Azure tenant
Databasin can run inside your own Azure tenant, installed from the Azure Marketplace, so PHI and other regulated data stay in your environment under your network, keys and policies. Your security review can examine where the platform runs, how people and agents access information, and the evidence available for oversight. We work with your team on the deployment and controls the project needs.
Security for business data
Databasin gives your team controls for who can use business data and records of how they use it.
Access
Your organization manages the identities people use to sign in. Data permissions apply to their work, and investigation agents have read-only access to production sources.
Regulated data
For work involving PHI or HR data, our team helps your security reviewers examine the requirements. Databasin is HIPAA-ready, with a BAA available.
Where data sits
You can use our hosted service, run Databasin in your own Azure tenant so PHI stays in your environment, or use it alongside Databricks, Snowflake or Microsoft Fabric.
Audit
An answer comes with its SQL for review. Your team can also examine query logs and lineage to understand the data behind it.
Access for people and automated work
Configuration rights and data permissions are separate. A project role governs the settings someone can change. A connection's credentials and scope govern the records it exposes, and a published Data App executes its queries through the viewer's connection.
Investigation tools read schema, run SELECT queries and fetch results. Each agent run has limits on turns, queries and returned rows. Its skill version, queries and output are recorded for examination. Tasks that transform data or operate on an external system are separate and require their own authorization.
Row-level security and column masking are supported in the governed layer, with engine-specific limits. Sail refuses tables protected by these controls. The technical review establishes which engine supports the access rules and workload required by the deployment.
Deployment, regulated data and agreements
| Item | Status and scope |
|---|---|
| Databasin Private in your Azure tenant | Installed from the Azure Marketplace into your own Azure tenant: your subscription, storage, keys and VNets. Databasin does not hold your storage account, your keys or a path into your network, and the language model runs behind your perimeter. Suited to PHI and other regulated data. |
| Hosted or alongside your platform | Databasin Cloud is operated by Databasin for data classifications that allow a hosted service. Teams can also keep Databricks, Snowflake or Microsoft Fabric and run Databasin over it. The same product runs in all three modes. |
| Business Associate Agreement | A Business Associate Agreement is available for work involving protected health information, on the standard plan rather than a tier upgrade. |
| HIPAA-ready | Databasin uses "HIPAA-ready" to describe architecture and contracting that can be reviewed for a regulated use case. It does not mean a certificate exists. The deployment, data flows, access controls and operating procedures remain part of your assessment. |
| SOC 1 and SOC 2 reports | Databasin does not currently hold its own SOC 1 or SOC 2 report. We will pursue SOC 2 Type II for the Databasin entity after its corporate separation completes, without promising a date. Until then, a security review can inspect the architecture, a deployment where data never leaves your tenant, and a signed agreement. |
| Security review | A security review can examine the architecture, applicable controls and contractual commitments for the proposed deployment. |
Security review documents
Data Use Agreement
Review the safeguards and commitments that apply to data use.
Privacy Policy
Read how Databasin describes its handling of personal information.
Terms of Service
Review the terms that govern use of the service.
Discuss the deployment you need
We can discuss your data, the proposed workflow and the controls your organization needs. The conversation can include where Databasin would run, how AI would access information and which evidence would help your security team evaluate the project.