Product and company help

Support

One accountable route for technical questions, access problems, documentation, privacy, and security escalation.

Support begins with a reproducible, non-sensitive description. Biosystems One does not currently publish guaranteed response times or a contractual support SLA.

Product support

Identify the Biosystems One product; include the page or app version, device or browser, approximate time, expected behavior, observed behavior, and sanitized steps.

Start a support request

Documentation help

Ask about intended use, supported formats, outputs, validation statements, privacy boundaries, or licensing information.

Review documentation first

Security reporting

Suspected vulnerabilities require the private reporting process and safe-testing boundaries in the Trust Center.

Report a vulnerability

Privacy requests

Requests concerning access, correction, deletion, or website privacy should identify the relevant interaction without resending sensitive content.

Review privacy information
01

Include in a technical request

A useful report is short, specific, and sanitized.

  • Product and exact page or workflow
  • Browser and operating system
  • Approximate date and time
  • Expected and observed behavior
  • Minimal reproduction steps
  • Non-sensitive screenshot only when necessary
02

Never include

Do not send passwords, authentication codes, API keys, medical records, personal health information, confidential workplace data, customer records, payment information, or unpublished sensitive research.

Ready to contact support?

Send a clear, non-confidential description.

General support uses the central Biosystems One contact path.