Security and trust

Written for a QA team reviewing a supplier. Read what we do not claim first, then the known limits. Every section ends with the date it was last checked.

What LabDesk does not claim

  • No SOC 2 report.
  • No ISO 27001 certificate.
  • No independent penetration test.
  • LabDesk itself is not ISO/IEC 17025 accredited.
  • No claim of 21 CFR Part 11 compliance, validation or certification.
  • No Part 11 electronic signatures.
  • The audit log covers key events such as transfers, disposals, calibration records and ownership changes, not every edit.

Last checked: 2026-11-17

Who builds and runs LabDesk

One owner builds and runs LabDesk, using AI-assisted engineering tools, with no second reviewer; security is reviewed in-house, not by an independent party. Two LabDesk staff accounts existed in production when last counted on 2026-10-26.

Contact: support@labdeskinc.com.

Last checked: 2026-11-17

Hosting and sub-processors

These providers host LabDesk or can see customer data in the course of running it. The list is not confirmed complete: the full set of Heroku add-ons, and the regions of Heroku, its database, Sentry and Papertrail, are not yet confirmed. Each row says what the provider does and what customer data it can see.

Providers that host LabDesk or can see customer data
ProviderWhat it doesCustomer data it can see
Heroku Hosting, database, backups and log routing. All structured data.
Amazon Web Services (S3) File storage. All uploaded and generated files.
Mailgun Outbound application email and inbound email, including mail sent to support. Message content and addresses, including scheduled reports with data attachments and inbound vendor emails.
Google Workspace (Gmail) Receives mail sent to support in the owner's Gmail; the account type is not confirmed. Messages sent to support and replies, replies to system email, customer correspondence and the files customers send.
Sentry Error tracking. Error events, which can quote record values, with request paths that include record identifiers, user and organization identifiers and log breadcrumbs.
Papertrail (SolarWinds) Logs: the application and router log stream, including background job output and the output of console sessions. Client IP addresses, request paths and identifiers, and any record content that appears in job or console output.
Anthropic (AI features) The AI features, described under AI features. What the AI features send, as stated under AI features.
Anthropic (engineering assistant) The AI coding assistant used to build and run LabDesk. Which terms govern it is not confirmed. Whatever LabDesk personnel retrieve while working: production query results, logs, error data, and customer names and contacts in engineering notes. By default the assistant's database access is read-only: it cannot write and cannot see password, token or encrypted columns, but it can read the other data of every organization.
GitHub, GitHub Actions and Dependabot Source code hosting, automated workflows and dependency update pull requests. Source code and engineering notes, which name customer organizations and contacts and include business email addresses and operational counts. Historical equipment photos and 23 possible secrets remain in the repository history (see Known limits).
GitGuardian (GitHub app) Secret scanning of pull requests. Repository content on pull requests.
Cursor (GitHub app) AI coding assistance on the repository. The full repository content, including the engineering notes and history. The app has asked for permission to write code and workflows; what is granted is not confirmed.
Claude (GitHub app, Anthropic) AI assistance on the repository. The full repository content, including the engineering notes and history. The app has asked for permission to write code and workflows; what is granted is not confirmed.
Heroku GitHub integration Builds and deploys from the repository. Repository events and the code pulled for deploys.
CodeRabbit (GitHub app) AI code review of pull requests. It shares code with third-party AI providers (OpenAI and/or Anthropic) and keeps a knowledge base unless opted out; the opt-out is not confirmed. Listed as of 2026-10-30 and not seen on recent pull requests, to be confirmed. Pull request content, including the engineering notes.
Google sign-in Sign-in with Google, for organizations that use it. The sign-in request, name and email.
PointDNS DNS. None.
Better Stack Uptime checks. None.
Script CDNs (Telerik Kendo UI, jQuery, jsDelivr) Script libraries loaded in the signed-in application. Their code runs inside those pages, no integrity check is applied to it, and the page security policy allows scripts from any HTTPS source. The user's IP address and browser, and anything shown on the page that their code could read.

Some rows rest on earlier records: Papertrail was last recorded on 2026-06-30, PointDNS on 2026-09-28 and Better Stack on 2026-09-18. Destinations a customer chooses are not LabDesk sub-processors: the customer's identity provider, SCIM client, API clients and webhook endpoints, users' own calendars and the calendar services that poll the calendar feed, an AI assistant of the customer's choice where that feature is switched on, and any email address added as a report recipient.

Last checked: 2026-11-17

Access controls

  • Password sign-in.
  • Single sign-on (SAML and Google) for organizations that have it.
  • SCIM provisioning for organizations that have it.
  • Two-factor sign-in is available and "Remember me" does not bypass it.
  • Role-based permissions.

The limits of these controls are listed under Known limits.

Last checked: 2026-11-17

How customers are separated

Separation between customer organizations is enforced in the application, not by separate databases.

Additional tenancy safeguards are being added in stages. The first of them, which only observes and refuses nothing, has been on in production since 2026-11-13; none of them yet refuses a cross-organization request, and no date is set for when they will.

The database itself does not keep one organization's data from another: it has no row-level separation, six child tables carry no organization column, and background jobs and several entry points (single sign-on, the API, SCIM, calendar feeds and inbound mail) are not yet covered by the tenancy safeguards. Defects that might have let one organization reach another's data, or let customer files be reached without signing in, have been found and fixed during 2026.

Last checked: 2026-11-17

Encryption and files

Files are stored in a private bucket that is not open to the public. A file is opened through a link LabDesk generates. A link inside LabDesk expires after 12 hours and opens the file only for a signed-in member of the organization that owns it who has permission to see it. Links made before the file-access change of 2026-11-17 do not expire yet and open only under the same checks. A photo link in an exported equipment list works without signing in and expires after 7 days. Files are encrypted in transit and at rest. Each application has its own access key, scoped to its own bucket; LabDesk administrators have keys with wider access. Database encryption at rest is a property of the hosting provider that LabDesk has not confirmed.

Last checked: 2026-11-18

Backups

The database runs on Heroku Postgres standard-0 (PostgreSQL 18.7). Heroku backs it up once a day, at 08:00 UTC, and keeps 7 daily and 4 weekly backups, with room for up to 25 manual backups. Point-in-time recovery to any moment in the last 4 days has been available since 2026-11-18 03:44 UTC. There is no separate copy and no monitoring of whether a backup succeeded, and the only restore drill, on 2026-06-30, covered the database only and was run before this plan. Uploaded files are not backed up at all and file versioning has never been turned on, so a deleted or overwritten file cannot be recovered.

Last checked: 2026-11-17

AI features

  • Smart Suggest is on for one or more customer organizations; it sends the column-header names of an imported spreadsheet to Anthropic.
  • Read handwriting for scanned service reports is on for one or more customer organizations; it sends images of the scanned pages to Anthropic and only suggests a match for a person to confirm.
  • Ask LabDesk, Flag Copilot and the nameplate reader are off.

LabDesk staff can change these switches for any organization, and for Ask LabDesk and Flag Copilot that is a rule LabDesk sets itself rather than a technical control. LabDesk does not claim that no customer data has reached an AI provider, or that AI features have been off for every customer.

For these product features Anthropic keeps inputs and outputs for up to 30 days under its standard API terms, as recorded on 2026-10-30, and does not train on them. LabDesk has no zero-data-retention agreement with Anthropic. Which terms govern the AI coding assistant, and the Claude GitHub app, is not confirmed.

Last checked: 2026-11-17

Where customer data can exist outside the hosted systems

Customer data also exists outside the hosted systems: on the owner's workstation (a photo archive, a photo corpus and an ongoing capture of production logs), in a copy of production data restored once into staging, in the engineering repository history and notes, and in the AI coding assistant's context.

Last checked: 2026-11-17

Known limits

  • Changes ship without advance notice and there are no release notes.
  • LabDesk staff can and do change or delete customer records by console, outside the audit trail and without the customer's approval, and console access is not logged durably.
  • Best-effort availability: no SLA, no high availability and no disaster-recovery site; the service runs in one region on one web process, recovery depends on the owner, monitoring is by email only with no on-call, and LabDesk does not claim a business-continuity plan or source-code escrow.
  • There is no written incident-notification timeline and no commitment to notify customers: whether, when and how to notify is the owner's decision.
  • No full export of an account, and no working deletion of a customer organization. Uploaded files are in no export, audit rows with user names are kept indefinitely and cannot be removed for one customer, and deleted data stays in backups for as long as they are kept: 7 daily and 4 weekly backups, with room for up to 25 manual backups.
  • The additional tenancy safeguards do not yet refuse a cross-organization request, and no date is set for when they will.
  • Older file links, made before the file-access change of 2026-11-17, do not expire yet: they open only for a signed-in member of the owning organization with permission to see the file, and LabDesk plans to stop accepting them around 2026-12-17. Photo links in an exported equipment list work without signing in, for anyone who holds the link, for 7 days, and keep working after a user is deactivated. Calendar-feed links do not expire, work for anyone who holds the link, and keep working after a user is deactivated.
  • Changes are checked by a test run on one machine, not by a cloud service; as of 2026-10-30 no logs of those runs were retained and only 28 of 82 recent changes carried an attestation of a passing run. As of that date the owner had bypassed the check, for 6 changes on 2026-10-25 and 26, all later released to production.
  • There is no validation package (requirements, trace matrix, operational qualification) and no customer validation environment, so a customer's acceptance testing happens in production.
  • The audit log is tamper-evident, not tamper-proof: LabDesk has a tool that rebuilds its chain and used it on production once, and verification is manual, last recorded on production on 2026-06-28. It does not record password sign-ins, lockouts, password changes, role and permission changes made in LabDesk screens, equipment created or edited by web form or API other than owner and location changes on a single instrument, any equipment deletion, or location moves made by Bulk Location Assignment or inventory-walk scans.
  • Sign-in is weaker than the list above suggests: "Remember me" bypasses the 30-minute idle timeout for up to 2 weeks; two-factor sign-in and single sign-on are optional and no organization is made to use either; password sign-in has no limit by network address or across accounts; reset and unlock responses can reveal whether an email address has an account; a user disabled at an identity provider keeps LabDesk access through "Forgot password" until removed in LabDesk or through SCIM; automatic account creation on single sign-on gives a Viewer account to anyone in the configured domain who completes it, with no off switch; nothing warns before an identity provider certificate expires; a holder of the edit-users capability can set another user's password through the API, and that is not audited; only LabDesk staff can unlock an account on a customer's behalf or configure single sign-on, and staff unlocks are not audited; integration tokens may be set never to expire; whether LabDesk staff accounts use two-factor sign-in is not confirmed; hardware security keys are not supported.
  • Global search shows names and links across users, vendors, equipment, appointments and calibration records to every user in an organization whatever their role; there is no central permission layer and no automated check that every page is protected; LabDesk staff accounts bypass the permission checks inside any organization they enter; and SCIM cannot reactivate a deactivated user, can create duplicates, and removing members or a group through SCIM also removes roles granted by hand, including Administrator.
  • The source-code history holds 23 possible secrets found in a scan on 2026-08-12; one of them no longer exists, and the other 22 have not been reviewed, so any of them could still be a live credential.
  • The staging environment is not fully isolated from production: production data was copied there once, and the two environments shared a field-encryption key when last checked on 2026-06-30; the current state is not confirmed.
  • The certificate, nonconformance and audit-walk modules are built and tested but had no records in production on 2026-10-30.
  • The product records an electronic signature (user, time, meaning and content hash, with password re-entry) when a certificate is issued and a nonconformance is closed; LabDesk does not offer these as Part 11 signatures, and protection against editing a signed record is in the application, not the database.

Last checked: 2026-11-18

Agreements

No terms of service, privacy policy, data processing agreement or quality agreement is in effect yet. Drafts exist for review, and a supplier-qualification pack is being prepared and is not yet ready to share. Sub-processors operate under their own standard terms.

Last checked: 2026-11-17