Skip to main content

Slack: data handling, retention and disconnection

Understand the data sent to Slack, the app permissions and the limits of cleanup.

Written by Elliot Boucher

A connection chosen by your administrator

This notice explains the Edusign Notifications integration for Slack. It supplements the service information and does not replace your institution’s contract, data processing agreement or the Edusign privacy policy. Your institution remains your contact for service data it controls.

An activated administrator or owner configures one institution subscription for a shared channel, selecting its types and language. Administrators may independently select personal direct messages. Old personal channels stay paused until explicit conversion; their audience never changes automatically. Availability depends on the integration rollout in your environment. Sign-in, password and security emails are excluded.

Data used and recipients

Edusign stores the Slack workspace ID, authorizing user ID, bot identity, workspace name, encrypted bot token, selected destination and preferences. The shared subscription belongs to the institution; its configuring administrator is retained as audit metadata. A personal connection belongs to the Edusign account within that institution.

Selected administrative notifications are copied to Slack. They may contain names and details in selected notification types. Shared channels exclude account-targeted events, private exports and types not approved for that audience. Members of the selected channel can read them: choose a workspace and audience appropriate for your institution’s data. Document links lead to an authenticated Edusign page.

The four permissions are chat:write (send notifications and remove proven owned bot messages during cleanup), im:write (open your private conversation with the bot), channels:read and groups:read (verify channel information and membership). No conversation history, email lookup or user token is requested. The app never joins channels automatically and excludes Slack Connect. It does not process conversations using AI.

Retention, disconnection and deletion

Tokens are encrypted with protection bound to the personal or institution scope and installation generation. OAuth state is single-use and expires after ten minutes. The delivery ledger stores delivery identities and status, destination, Slack receipt timestamp and a signed ownership proof; it does not store message bodies.

Disconnecting stops future sends only for the selected personal or shared subscription. It does not uninstall a shared bot or remove messages already sent. Historical encrypted installation credentials, receipts and configuring-administrator audit references remain available for cleanup while the institution exists, with no separate automatic expiry.

Institution deletion attempts to remove affirmatively owned bot messages before removing required references and credentials. An uncertain send result, missing proof, revoked access or Slack failure can block cleanup. References are then preserved for recovery; complete deletion cannot be guaranteed in these circumstances.

Shared delivery and dead-letter queues can retain the source event for up to fourteen days, accessible only to backend infrastructure roles. Idempotency identifiers without message content are retained for seven days. New API and delivery operational logs are retained for ninety days without OAuth codes, tokens or raw provider responses. Backups follow the applicable infrastructure retention policy.

Slack messages, exports, backups and legal holds also follow your workspace’s rules. Removing those copies may require the workspace owner’s cooperation. This notice does not promise their immediate or universal erasure.

Support and data requests

To configure or disconnect Slack, open Institution settings → Integrations for the shared channel, or My account → Notifications for direct messages. For support: support@edusign.com and the help centre.

For your rights concerning service data, contact the relevant institution first. For data protection questions: dpo@edusign.fr. See the Edusign Trust Center and applicable agreements for the processing relationship and international transfers.

Did this answer your question?