Know where your scans go and who sees them.
Nitsor connects scan labelling with expert review. Here is what it stores, who can sign in and where it runs.
A real chest CT series as its files: 140 DICOM Part 10 files, 73.7 MB. Armato et al., "Data From LIDC-IDRI", TCIA, case LIDC-IDRI-0003, CC BY 3.0 (opens in a new tab), modified: windowed and stacked by Nitsor. Sources
Your data
What Nitsor stores, and where.
Choose the destination for uploads while referencing existing scans in place. The browser reads viewed slices through short-lived signed links; model jobs use temporary copies.
- Where scans live
- Existing scans stay where they live. Upload to customer storage or a Nitsor-managed bucket, or let Nitsor manage all storage. Hosted uploads use Nitsor storage by default; the owner can switch it off.
- In Nitsor's records
- Source metadata, point, box and class labels, review history, audit events and dataset version manifests. For read-only connections, Nitsor keeps no scan pixels or files derived from them. These records live in a database that never holds scan pixels, in any storage mode.
- What reads your scans
- Your browser reads viewed slices from the selected storage through short-lived signed links. Nitsor's backend reads files to register a scan, to re-read it later and to check a storage connection. Hosted preview, model and dataset version jobs work on temporary copies while they run. A training job reads a dataset version through a Nitsor service that checks a time-limited lease on every request. On Community, the backend runs on your own infrastructure.
- What Nitsor's backend reads
- To register a scan or re-read it later, Nitsor reads each DICOM file whole and, for other formats, as little of each file as it can: usually headers and small samples. A storage connection check reads only enough to confirm access. Every read has a size limit, and Nitsor keeps the results and none of the bytes. The docs (opens in a new tab) list each read and its limit.
- Where hosted records live
- On Team and Enterprise, Nitsor stores its records in the United States. Requests first reach the nearest edge location.
- Storage keys
- Owners and admins submit keys through the dashboard or a personal token; Nitsor encrypts them. Agents cannot add keys. Connections start read-only. Grant write access to save masks, stored previews and model outputs. An owner or admin separately enables Accept uploads after the storage checks pass.
Sign-in
Sign in the way your plan allows.
Everyone signs in to a named account on every plan. Enterprise connects your own identity provider.
- Community
- Through your own OIDC identity provider.
- Team
- Email and password, Google or Microsoft.
- Enterprise
- Single sign-on through your SAML or OIDC identity provider, with automated user provisioning by agreement.
- Machines
- Scripts and services use agent credentials with the scopes you choose and an expiry of at most 365 days. Nitsor stores only a fingerprint of each token.
Roles and access
Give each person only the access they need.
Workspace roles cover the account. Project access covers the work. Enterprise adds advanced access policies by agreement.
- Workspace roles
- Each person holds one of four roles: owner, admin, member or billing. Only owners and billing can change billing.
- Project access
- Inside a project, access is read, contribute, operate or admin. A member opens no project until someone grants access.
- Review
- A reviewer cannot review their own work unless a coordinator assigns it, and the record notes the exception.
- Checks
- Nitsor checks permission before every change, and clients connect over HTTPS.

What each frame shows
- Choose a person and an access level
- A. Rivera is listed at Contribute
- Grant a role a stage can require
- M. Chen holds role reviewer
Audit history
Every change keeps a name.
The record shows who did what. Your quality process decides whether the work meets its requirements.
- What the record keeps
- Who drew each label, who reviewed it and which revision they saw. Events are only ever added, never edited.
- Read-only access
- Give auditors read-only access to labels, reviews and dataset versions, with no charge per person.
- Exports
- Labels, reviews and history stay readable on every plan: through the HTTP API on Team and Enterprise, and in your own deployment on Community. Enterprise adds administrative audit exports.
Deployment
Run Nitsor where your data rules require.
Teams with sensitive data can keep the whole stack on their own premises or in their private cloud.
- Community
- Free and self-hosted on your own infrastructure, on-premises or in your private cloud. Telemetry and billing are off.
- Team
- Hosted by Nitsor, with managed updates and backups of the hosted workspace data.
- Enterprise
- Hosted by Nitsor, or by agreement a private deployment on your premises or in your private cloud, set up with our help.
Assurance
Get the documents your review needs.
Enterprise customers receive security and procurement documentation. We agree deployment, support response times and data processing terms in the contract.
- Certifications
- Nitsor is working toward SOC 2 and HIPAA, including signing business associate agreements (BAAs).
- Security contact
- Write to security@nitsor.com with what you found and how to reproduce it. Do not include secrets or customer data, and do not report a vulnerability in a public issue.
Show us what you inspect.
Start with a public CT or MRI scan. See how a model suggestion becomes a reviewed label and a fixed training dataset.
