← Back to docs

Data retention

Data retention

Tools stores data only for as long as it is needed to provide a feature, keep the service secure, diagnose operational failures, or satisfy an applicable audit requirement. Retention is scoped to the authenticated Tools user wherever user ownership exists.

Self-service retention controls

Authenticated users can open My Profile - Data retention at /users/profile/data-retention and clear selected categories of their own retained data.

SocialGPT retained content

The SocialGPT purge removes retained prompt, context, response, error-content and request/response payload fields from that user's SocialGPT request-log rows. Operational metadata such as timestamps, model, token totals, latency, status and request identifiers may remain so aggregate usage statistics and operational audit can continue without retaining the conversation content.

Usage statistics

The usage-statistics purge removes user-linked page and API visit rows for the authenticated user. It does not delete the Tools account or service configuration.

The backend derives ownership from the authenticated session. A client cannot choose another user id for these operations.

Slack data retention

Tornevall Networks retains Slack workspace installation metadata while a workspace remains connected and as required for secure operation, diagnostics and audit. Slack message content is not intended to be a permanent archive. Transient message content used for queued processing is cleared after terminal processing, while bounded conversation context is normally fetched from Slack on demand.

Slack OAuth credentials are encrypted at rest. Operational records may contain identifiers, timestamps, event types, result/status information and correlation identifiers, but are designed not to contain Slack message bodies or secrets. Data used for AI-powered requests may be sent to the configured AI provider only when needed to process the requested feature. Slack data is not used to train language models by Tools.

Disconnect cooldown

Disconnecting a Slack AI Bot workspace starts a 24-hour retention cooldown for remaining workspace-linked data. If the same workspace is reconnected to the same Tools user before the purge becomes due, the pending purge is cancelled. Once the cooldown expires, the remaining workspace-linked Slack data covered by this policy is removed automatically.

Account deletion

A user who requests deletion of their own Tools account receives a 30-day recovery period. The request can be cancelled from the Data retention page during that period. When the request becomes due, the account and user-scoped data are permanently purged.

An account deleted by an administrator, or removed by an automatic account-cleanup policy, does not receive the self-service recovery period. User-owned rows whose user_id no longer belongs to an existing account are also removed automatically.

Audit of retention actions

Retention actions produce a minimal structured audit record containing information such as the action, scope, result, timestamp and correlation id. Deleted message bodies, prompts, responses, secrets, tokens and credentials are not copied into the retention audit record.

Operational failures are reported through the normal ToolsAPI diagnostics path without including deleted content or secrets.

Access, transfer and deletion requests

Workspace owners and Tools users may also request access, transfer, purge or deletion of stored personal data through the public Tornevall Networks contact channels. Stored operational data is removed when it is no longer required for functionality, security or applicable audit requirements.