Skip to content

Your data and privacy

Fadenstack runs on your organisation's own server. This page says what is kept there, who can see it, how personal data is protected when your organisation has set that up, and what leaves your organisation when a model runs at an outside provider.

What is kept, and where

On your organisation's server:

  • your account;
  • your chats: the messages, the replies and their titles;
  • your projects, with their settings;
  • the files you attach, and the text read from them;
  • your skills;
  • usage records: when you used which model, how much text went in and out, and which tools ran. They do not contain what was said.

The messages, the replies, chat titles, project names, descriptions and instructions, file names, the files you attach and the text read from them are stored encrypted. The server does not start without the key they are encrypted with. Chats from before your organisation's upgrade to this release are encrypted by the upgrade. A model's thinking is not saved at all.

On your own computer:

Its conversations Your sign-in
The browser agent In your browser, not on the server, encrypted In your browser too, not encrypted
The Office add-ins On your computer, encrypted Protected by Windows

Fadenstack keeps your chats until they are deleted. See Deleting.

Who can see what

Who What they see
You Your chats, projects, files and skills
Colleagues None of your chats or files. Skills you share with them. The organisation's knowledge base is shared by everyone
Administrators, in the console That a chat, a project or a file exists (who, when), not its title, name or content. The sizes and types of your files. Usage in totals for groups, never yours alone; the requests they look at do not name who sent them (see Your usage). Which tools ran and the kind of a failure, not what the tool answered. How often personal data was found, not the data itself. Every skill, including private ones. What they look at in the console is recorded in the audit log

The console does not show administrators your conversations. The people who run the server do hold the key the chats are encrypted with, so use the chat as you would your organisation's e-mail: private from colleagues, but within your organisation's IT.

Personal data protection

Your organisation can have Fadenstack find personal data, such as names, e-mail addresses, phone numbers or account numbers, in what you send, and mask it before it reaches a model. Your administrator decides this in a policy: whether it is on at all, for which models, and what is looked for. It is not always on. See Policies and personal data.

When it is on, personal data is masked in one of two ways:

Mode What happens to personal data
redact It is replaced by a label such as <PERSON> before the model sees it, and it does not come back. An answer that mentions it shows the label.
tokenize_reversible It is replaced by a placeholder such as [PERSON_1] on the way to the model, and the real value is put back in the answer you see.
If the check cannot run

If the check cannot run, the policy decides: your message is not sent, it is sent anyway, or it goes to one of your organisation's own models instead.

Detection is not always right

Personal data is found automatically, and how well that works depends on the language and on how the text is written: tables, lists, code and short fragments are harder than plain sentences. It finds most personal data in English text, not all of it; in German or other languages it often misses names and places. It can also mask words that are not personal data. Do not paste anything you are not allowed to share.

See and tighten it for one chat

The Privacy tab saying Using tenant defaults, with Cloud egress, Local egress, Mode and Fail Action, and the kinds of personal data looked for, each with a lock, above Add entity

  1. Open the tools panel with the wrench beside the message box.
  2. Select Privacy.
  3. Read the top line: Using tenant defaults (your organisation's policy) or Session override active (this chat has its own settings).
  4. To protect more in this chat, change a setting:
Setting What it does
Cloud egress Switch it on to protect what goes to models at outside providers
Local egress Switch it on to protect what goes to your organisation's own models
Fail Action Choose what happens when the check cannot run
Add entity, under Detection Settings Adds a kind of personal data to look for
Mode Switches between redact and tokenize_reversible, if your organisation allows it
Clear Session Override Goes back to your organisation's settings

You can only make the protection stricter than your organisation's policy, never looser. Settings the policy enforces show a lock.

In the browser agent and the Office add-ins

In the browser agent and the Office add-ins, a note Personal data protected says how many values were kept from the model, and of which kinds.

Models at outside providers

Your administrator can offer models that run at an outside provider, such as OpenAI or Azure, next to your organisation's own. When you pick one of those, everything the model needs to answer goes to that provider: your message, the earlier messages of the chat, the text of your attached files, project and skill instructions, tool results and knowledge passages. Personal data is masked first if the policy says so. The provider's own terms then apply.

The model list does not always show where a model runs. If it matters for what you write, ask your administrator, or pick a model you know runs inside your organisation. See Remote providers.

Your usage

My usage, in the menu behind your account button, shows how much you used: your tokens and estimated cost by day or month, by model, agent and project, and the limits that apply to everyone. Under Your data, Download as JSON and Download as CSV give you your data: your daily figures, your request records (time, model, tokens, cost, outcome; never what you wrote) and when someone looked at your figures, and why.

  • You see your own figures.
  • Administrators see totals for groups of at least five people, never your figures alone. When they look into a failed request, its record does not show who sent it.
  • If your organisation has switched on person-level reporting, My usage says so. A few named people may then look at your figures, by day or by month, each time giving a reason. My usage shows how often that happened; your download shows the date and the reason of each look, not who looked.

Your figures are kept for the time My usage names (90 days unless your organisation chose otherwise), and are erased when your account is deleted. Your organisation uses them for costs and capacity, not to judge your work; where it has a privacy notice for employees, My usage links to it. See Usage and privacy.

When a limit stops a request, the message names the limit, for example the instance's daily token limit. Ask your administrator if you need more.

Tools and the knowledge base

  • A tool your administrator connected receives what the model passes to it, often a search term or text from your conversation. Your administrator decides, per service, how personal data in those calls is handled. See Tools in the chat.
  • Everything in the organisation's knowledge base can come up in anyone's chat. Your attached files do not go into it. See Knowledge.

Deleting

You delete What happens
A chat It disappears from your list at once and cannot be brought back. The server keeps it for the time your organisation set (30 days unless it chose another), then erases it for good, with its files and what the assistant remembered from it.
A project It is erased at once, with all its chats and their files.
Your account (an administrator does it) Your chats, projects, files and what the assistant remembered are erased with it, and so is what your apps reported to the server: which tools ran and when, and your devices' reports.
A chat in Chat history, in the browser agent It is removed from your browser.
Remove my data…, under Your data in this browser in the browser agent's settings The chats, saved prompts, Allow always choices and record of tool calls kept for you in that browser are erased, with their key, and your connection ends. Remove all my Fadenstack data in this browser… does the same for every Fadenstack app there. Export my data saves them first, as a file.

If something must be erased sooner, for example personal data you pasted by mistake, ask your administrator: a chat they delete in the console is erased at once. Backups taken before keep it until they are replaced (the nightly ones after a week).

The sign-in page, About Fadenstack (in the menu behind your account button), the release notes on Updates, the footer of these Help pages and the chat panels of the add-ins link to fadenstack.com. Such a link tells the website where it was clicked (for example ref=console-about) and the release line (v=0.4), so Fadenstack can count how its software is used. It carries nothing about you, your organisation or this server, opens in a new tab, and does not pass on the address of the page you came from. Nothing is sent unless you click one.

The download links on Apps go to the site where an app is published (GitHub, the Chrome Web Store or the Nextcloud app store). That site sees your address (IP), as with any link; the links send no referrer, so it does not learn your organisation's server address. The server itself reads the public list of Fadenstack apps once a day, as it does the list of releases, and sends nothing about itself (see Apps).

Enterprise With Enterprise, administrators can take the console's links away (the sign-in page, About Fadenstack, the release notes on Updates): Settings → Branding → Show links to fadenstack.com.

When it does not work

You see What to do
A PII policy is set for this workspace, but the PII module is not running. Your organisation's policy needs the personal-data check, and the module that does it is switched off. Nothing was sent. Tell your administrator.
PII service unavailable and fail_action=block. The personal-data check could not run, and your organisation's policy says not to send messages without it. Try again later; if it keeps happening, tell your administrator.
An answer shows <PERSON> or [PERSON_1] where a name should be The name was masked before it reached the model. With redact this is expected. With tokenize_reversible the name should come back; if it does not, tell your administrator.
Your admin hasn't allowed changing the PII mode for this chat. Your organisation fixes the mode. The other settings in Privacy may still be open to you.
… is not applied. Choose it again to apply it. The mode you chose earlier did not take effect. Choose it again in Mode.