Data retention policy
Connection data is kept until you disconnect with /rebrand logout or ask us to
delete it. Uninstalling the app from Slack alone does not remove it.
Branded links created with the /rebrand command are stored in your Rebrandly
account and follow the retention terms of your Rebrandly plan, not the Slack
integration.
Data archiving and removal policy
Running /rebrand logout in Slack disconnects the Rebrandly account and deletes the
stored connection record, including the stored tokens.
Removing the connection does not delete branded links that were already created.
Those remain in the Rebrandly account and can be deleted from the Rebrandly
dashboard.
Data storage policy
When a Slack workspace is connected to Rebrandly we store only what is needed to
link the two accounts: the Slack workspace ID, the Slack user ID of the person who
connected the app, the Slack token issued at install, the Rebrandly account ID, the
Rebrandly access and refresh tokens, the selected Rebrandly workspace, and the
default branded domain. This is stored in Amazon DynamoDB within our AWS
infrastructure and encrypted at rest.
The app requests only the "commands" and "team:read" permissions. It has no access
to the content of your messages, channels or files, and never stores them.
App/service has sub-processors
yes
Guidelines for sub-processors
App/service uses large language models (LLM)
no