Permissions, data and privacy

This page is for anyone deciding whether to connect an assistant, and for IT administrators reviewing the Skybox connector. For Skybox's data handling in general, read the privacy policy; the section Third-party apps you connect is the legal counterpart of this page.

Permissions

An app asks for scopes, and Skybox shows them on the authorization screen before you decide:

Scope	Allows
mail:read	Listing and searching messages, reading messages and attachments, the folder tree, quota.
mail:send	Sending messages and saving drafts, including the compose window and file uploads for attachments.
mail:manage	Moving, copying, deleting and flagging messages; creating, renaming and deleting folders.
calendar:read	Listing calendars and events.
calendar:manage	Creating, changing and deleting events.
contacts:read	Listing and searching contacts.
contacts:manage	Creating, changing and deleting contacts.

An app receives exactly the tools its granted scopes cover; see What the assistant can do for which tool belongs where. An app that later asks for a scope it does not hold is sent through the authorization screen again, where you see the new request.

Account selection

Scopes say what kind of thing an app may do. The account selection says on which accounts. On the authorization screen every account you can open in Skybox is listed, grouped into mail, calendar and contacts, and only the kinds the app asked for are offered. Untick what the app should not reach.

• The selection is stored per app and per Skybox user, and checked on every request. An account that is not selected does not appear in any listing, and a call that names it anyway is refused.
• Change it any time under Settings → Connected Apps → Account Access. The change applies to the app's next request.
• A mail account that someone shares with you can be selected like your own. Calendar and contact accounts must be your own.

What the assistant sees

A tool returns what you asked for and nothing in advance: a search returns the matching headers, get_message returns one message's content, get_attachment one file. That content goes into your conversation with the assistant and from there is handled by the assistant's provider under its own terms. For Claude that is Anthropic's privacy policy. Skybox does not decide, and cannot see, what the assistant does with it afterwards.

What the assistant never receives:

• your Skybox password, or the passwords and tokens of your mail, calendar and contact accounts;
• accounts outside the selection;
• message content it did not ask for by naming the message.

An attachment is handed over as a signed download link valid for 15 minutes that names the one attachment and nothing else. Skybox checks your access again when the link is used; the file is read from your mail server at that moment, not stored.

What Skybox stores about the connection

• The consent record: which app, which scopes, when, and the optional name you gave the connection. It is what Settings → Connected Apps shows and what every request is checked against.
• The account selection for that app.
• Tokens the app uses to call Skybox, so that it does not have to send you through the sign-in again. They are bound to this one app and this one user, and are invalidated on revoke.
• Server logs record each tool call with the tool's name, the user and the app, so that misuse can be traced and errors investigated. They do not contain message content, subjects or addresses.

Skybox keeps no copy of your mail for the assistant. Everything a tool returns is fetched from your mail, calendar or contacts server when the tool runs. The Skybox app's own caches (folder names, message dates and flags, and a 24-hour cache of subjects and senders) exist whether or not an assistant is connected; the privacy policy describes them.

Files the assistant uploads to send as attachments are kept for at most 60 minutes and then deleted. Files sent as download links are kept until the expiry you chose, at most 365 days; see the privacy policy, Files sent as links.

Revoking

Settings → Connected Apps → Revoke deletes the consent record and invalidates every token of that connection. The app's next request is refused, and the connector in the assistant asks to be connected again. Removing the connector on the assistant's side has the same effect for that device; revoking in Skybox is the reliable way to be sure, because it does not depend on the assistant.

Deleting your Skybox account removes every connection with it.

For administrators

• Transport: HTTPS only, at https://api.skyboxmail.de/mcp (or your Enterprise instance's address). The server is stateless; it issues no session and stores nothing per conversation.
• Authentication: OAuth 2.1 with PKCE and dynamic client registration, as the MCP specification requires. Metadata is published at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. An access token issued for /mcp is valid nowhere else in Skybox.
• Authorization: scopes granted on the consent screen, intersected with the token's scopes, plus the per-app account selection; all three are checked on every request. A deactivated Skybox user is refused on every call.
• Plans: on skyboxmail.de, connecting an app requires Skybox Pro. On a Skybox Enterprise instance there are no plans.
• Hosting: skyboxmail.de runs on servers in Germany; details and sub-processors are in the privacy policy, Hosting and recipients. A Skybox Enterprise instance runs where you install it; the assistant then talks only to your instance.
• Contact: hello@skyboxmail.de.