Keep data within its intended scope
Workspace and resource access checks apply to chat, files, and connected systems. Give a task only the material it needs. A person being in a team channel does not make every private source available to them.
Review publication separately
A generated file, artifact, or hosted application can have a different audience from the source conversation. Inspect its sharing controls and actual content before making a link public.
Use published policies
The Privacy, DPA, and Subprocessors pages describe Spinrun's published terms and data-handling arrangements. Ask the team about a contractual requirement that those pages do not answer.
Request deletion through the right route
Use Account or Data settings for the supported deletion controls. A workspace administrator may need to handle shared resources. Deleting access in Spinrun does not erase records already sent to an external provider.
Open the relevant screen
Use Data and privacy in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.