> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/troubleshooting/contact-support/what-data-you-share-with-sbt.md).

# What data you share with SBT

What a device data bundle holds, and how we handle your data.

A device data bundle is a ZIP file with the system logs and the measurement data of your BactoBox®. It lets our support team see what your BactoBox® saw, so we can help you faster. You rarely handle it yourself. A support case from Access includes it when you check that option.

## What the bundle holds

* **Your measurement results.** For example the electrical measurements and the *Cells/mL* they give.
* **What you typed in yourself.** For example *Label*, *Dilution*, *Sampled at*, *CFU/mL*, *Measurement group* and your notes.
* **System logs.** They tell us how your BactoBox® ran.

## What we can see

We can read your labels, because you write them. If you label a measurement *E. coli*, we see *E. coli*. If you label it *Strain A7*, we see *Strain A7* and nothing more.

{% hint style="info" %}

### Use code names if you prefer

If your work is sensitive, use your own code names in your labels. Your measurements stay just as useful to you.
{% endhint %}

A measurement is an electrical signature of the particles in your sample. It is not a sequence or a species name. We cannot turn it into a biological identity.

## How we handle your data

We treat your data as confidential. We only look at a bundle when you share it with us to get help, and we only use it to support you.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sbtinstruments.com/troubleshooting/contact-support/what-data-you-share-with-sbt.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
