Data that passes through the Connector
See which data passes between TEISENDA and the connected application and which logs are created.
On this page
What the application receives through the Connector
- the name TEISENDA, an icon and the docs address used to introduce the Connector
- the Connector's instructions
- the catalogue of tools
- from
whoamiyour name and, for each Space in the connection, its Space ID, name, whether it is locked and its products - the result of each tool call
A hosting tool's result starts with the Space
Hosting results first name the Space and give a message in your account language, or in German if the language is unsupported. Then comes JSON data with English field names. A Space is a shared workspace in the app.
whoamiresponds with a single text block containing JSON, without the Space line or a structured part.- TEISENDA returns the contents of a file the application reads with
hosting_read_fileonly in a separate, framed block marked as data; at most 40,000 characters per call. hosting_get_visibilityonly gives the number of selected people and teams, never other members' names. The hosting node's English error codes never appear in a result.- A rejection is a sentence in your account language or, if the Connector rejects the request, a fixed English sentence. Sometimes there is only an HTTP status. See Troubleshoot the Connector.
That is what the Connector returns. The application writes what you read in the conversation.
What TEISENDA receives from the application
TEISENDA receives the tool call's arguments, together with the user, connection and request ID.
Several logs record information about use
Project-log details and app error messages can contain individual values from tool arguments. The request ID is the same in the Connector and project log; it can be used to find a call in both.
| Log | Maintained by | Contents |
|---|---|---|
| Authentication | Connector | The user for each sign-in, revocation and sign-out. For sign-in, also the application's name and the host it returned to. |
| Tool calls | Connector | Tool name, user, request ID and time; errors may add lines containing app error messages. These may contain individual data such as a Space ID. whoami does not create this kind of entry. Revocations are logged with the authentication state, application identifier and, if available, user. |
| Access | Connector web server | IP address, time, method and full address including query parameters, HTTP status, response size, referring page and requesting program. Another field may contain the application identifier for HTTP Basic authentication. For tool calls, the IP belongs to the provider; during sign-in, it belongs to the browser. |
| Project log | App | Changes with Space, project, account, channel, request ID, action, detail and time. Details may contain individual argument values, but no filenames or file contents. Reading, writing and deleting files create no entry; creating a draft and removing older versions are recorded. |
| Versions and connections | App | A version retains the channel, account and request ID used to create it. A connection retains its last-used time. |
| Error output | App | Errors only: if a tool aborts, a line contains the tool name, request ID and error, which may contain argument values. |
| Background job errors | App database | If a background job fails, its error message is stored. |
During sign-in, the parameters of the authorization and callback addresses are also logged, including the app’s one-time code. The web server does not log request or response bodies, tokens, cookies or the Authorization header. Complete tool arguments and results are not recorded in the service journal; error messages may still contain individual values.
These retention periods apply to the logs
- Authentication log: entries older than twelve months are deleted when a new sign-in starts.
- The Connector’s service log of tool calls and revocations: no more than three months; entries may be deleted sooner when the size limit is reached. Weekly rotation retains the additional copy in the system log for roughly four to five weeks.
- The web server’s access log in front of the Connector: 14 daily files plus the current file. Daily rotation deletes entries after 14 to 15 days. This period does not apply to the web server’s error logs.
The project log has no fixed retention period: its entries remain until the Space is deleted, even if the project is deleted first.
Deleting an account removes the entry’s link to the person who performed the action. An account ID in the details of an earlier sharing entry remains, however.
There is no retention period in days for output from the app, its Connector listener or background jobs. Each container’s log file rotates when it reaches 10 MB, removing older output. Removing the container also deletes its output. A new deployment alone does not delete it: stopped predecessor containers retain their logs until they are removed.
Background job error messages also remain in the database without an automatic deletion rule. Deleting a Space does not remove these entries.
What TEISENDA records for each connection
- the name supplied by the application, unchanged and never verified by TEISENDA
- the host that sign-in returned to
- the time it was connected and last used
- its Spaces and whether it also covers Spaces you join later
Last use includes rejected requests and is updated at most once every five minutes. It does not prove that a tool ran.
The privacy policy is on the website
Find TEISENDA's privacy policy at teisenda.com/en/privacy.