Privacy notice

Who is responsible

BoCo Research B.V., Leiden, the Netherlands (KvK 89932056), of which BoundaryComputing is a registered name. For anything on this page, write to dev@bocores.com.

This website

bocores.com is a static site. It sets no cookies, has no sign-in, and has no forms. It is hosted by Vercel, which processes the technical data of each request (such as your IP address and browser type) to serve and secure the site. We use Vercel Web Analytics to count page views; it works without cookies and does not identify you across sites. We use no other trackers, pixels, or advertising.

The demo clip on the home page, and its poster image, are loaded from salpa.app, our product site, which is hosted on Google Firebase — so fetching them sends the same technical request data to Google. Nothing else on this site calls a third party.

Links to GitHub, LinkedIn, YouTube, and salpa.app take you to those services, whose own privacy notices then apply.

If you email us

We keep the correspondence for as long as we need it to handle the conversation and anything that follows from it. We don’t add you to a mailing list, and we don’t share your message beyond the people who need to answer it.

Salpa and Salpa Compute

The Salpa application runs on your own computer. Salpa Compute — where you register with an email address or Google sign-in and run selected AI models as cloud nodes on hardware we run — processes your account details and a record of each job, and your job data only for the duration of the job. Exactly what that means, where it happens and who processes it is in the Salpa privacy notice, with the terms of service alongside it. We do not sell data.

The Salpa assistant (early access)

Salpa accounts that we invite to our early-access programme can use an assistant beside a project in the Salpa app. It is a test: we invite the people who use it, and it may change or stop. Nothing on this website uses it.

What it sends. When you write to the assistant, the app sends:

• your message and the earlier messages of the same conversation, as you wrote them;
• where you are in the app: the project’s page or a workflow’s canvas, which workflow is on screen, and which are open in tabs;
• what the assistant reads to answer you: the project’s name and description and the name of its folder; the workflows it opens, which can be any of yours, not only this project’s, with their steps, settings and runs; a step’s results, log lines and errors; text files it opens in a workflow’s folder; the documentation and workflow templates of the installed packages; a summary of a PDB entry; the outcome of the steps it prepares and of the changes you apply, including an error the canvas reports; which packages are installed; Salpa’s version; and your account’s assistant allowance and whether the assistant is on for it.

In everything the assistant reads, the app replaces full paths before sending them: your home folder becomes ~, the project’s and its workflows’ folders become placeholders, and so do the folders of any other full path, so where your files sit on your computer stays there. What you type is sent as you wrote it.

Where it goes. From your computer to our API gateway, which runs in Google Cloud’s us-central1 region in the United States, and on to Google Cloud’s Vertex AI, which runs the model, GLM-5.2. The model is served from Google’s global endpoint, so where it is processed is not pinned to a region and may be outside the EU. One message can take up to eight requests to the model, each sending the conversation so far. Your sign-in token goes with each request to our gateway, which uses it to know your account and check its allowance; it is not passed to Vertex AI. Google states that it does not use prompts and responses to train models and does not share them with third parties, including the model’s publisher. GLM-5.2 is a preview offering on Vertex AI. When the assistant looks up a protein’s PDB entry, your app asks the RCSB Protein Data Bank (data.rcsb.org) for its public record, as Salpa’s own nodes do.

When the assistant looks up a tool in Salpa’s tool database, our private record of the tools Salpa’s packages run and their known errors, your app sends our API gateway the tool’s name or the phrase it searches for, such as an error message, with your sign-in token. The answer comes from that database, not from the model.

If Salpa Library is open for your account, the assistant can also search it: our private collection of nodes that we checked by running them. A search sends our API gateway what the assistant asks for (a file format, a role such as a trajectory, input or output, a tool’s name or a package’s name) with your sign-in token, and the answer comes from the library’s index, not from the model. When you apply a card to install a package from it, your app sends the package’s name and version and the one line on the card saying what you are working on; the package’s files come back from our gateway and are installed on your computer like any other package. When the assistant reads one of the library’s workflow templates, your app fetches it from our gateway by its identifier.

What we keep. For each request to the model we keep a record that includes your user ID, a request identifier, the model and the version of the assistant’s instructions, when it started and ended, the number of tokens sent and received, the cost, how it ended, and what was held and charged against your allowance. We do not keep the text of your messages or of the replies. These records are deleted when you ask, like the rest of your account’s records: email hello@salpa.app from the address on the account. Google Cloud keeps ordinary operational logs of the requests for a limited time under its own terms. The conversation itself, and a record of what the assistant read and did, stay on your computer.

For each lookup in the tool database we keep a count of your lookups in that hour, for a limit of 120, deleted about two days later, and a log line, kept 30 days, with the tool’s or package’s name, the kind of lookup, whether it was answered, the answer’s length, that hour’s count and a code derived from your user ID. We do not keep the phrase or the answer.

For Salpa Library we keep a count of your searches and of your deliveries in each hour, for limits of 120 searches and 10 packages or templates, deleted about two days later, and a log line for each call, kept 30 days, with the package’s name and version or the template’s, how the call ended, the size of the answer, that hour’s count and a code derived from your user ID. Of a search we keep a package’s name only when you searched by a name the library holds, and nothing else of what was asked. Of the line saying what you are working on we keep its length and a code computed from it with a key we hold, so that a line you show us can be checked against the log; we do not keep its words.

What you send us. A thumbs-up or thumbs-down on a reply sends which conversation, which reply and which way, with your user ID, the assistant’s version and the time; no text.

If you choose Send this conversation, the app first shows you what it will send, with the full text a click away, and a box for a note. What leaves is what you were shown, plus your note, and nothing else: the app checks this before it sends. It is the conversation as Salpa recorded it on your computer:

• your messages and the assistant’s replies, the reasoning the model wrote, any error a reply met, and the time of each step;
• each tool the assistant used, what it asked of it and what it returned, which can include the project’s name, description and folder name, workflows with their settings and runs, steps’ results, logs and errors, text files it opened, documentation, PDB summaries and your remaining allowance;
• the thumbs you gave in it, and the identifiers of its earlier sends, if any;
• the record of the conversation’s events: token counts, the model’s request identifiers, workflow and template identifiers, and the names of workflow folders;
• Salpa’s and the assistant’s versions, and your note.

Before it is sent, full paths are replaced everywhere in it as described above, in your own messages too; the note is sent as you write it.

It goes through our gateway to a private Google Cloud Storage bucket in the us-central1 region (United States), with an index entry in our database that holds your user ID, the conversation’s identifier, where it is stored, its size and checksum, the versions and the time, and none of its text. A thumb is kept in the same database as that index entry. Only the Salpa team can read them. We read what you send to improve the assistant and keep it as a test case; we do not use it to train a model.

Both are kept, with no expiry, until you ask us to delete them. Write to hello@salpa.app with the identifier the app showed you when you sent a conversation (its Ask us to delete it link writes that email for you), or from your account’s email address to cover everything you sent, thumbs included, and we delete it: a conversation leaves the bucket at once, with its index entry.

The full notice is the Salpa privacy notice.

Legal basis and your rights

We process this data on the basis of our legitimate interest in running and securing the site and answering you, and — for Salpa Compute and the early-access assistant — to provide the service you asked for or were invited to. Under the GDPR you can ask what we hold about you, have it corrected or deleted, or object to its use; email us and we will act on it. You can also complain to the Dutch supervisory authority, the Autoriteit Persoonsgegevens.

Changes

If this notice changes, the date at the top changes with it. Every step we take is also in the build log.