Security and data

Before you start

• This page is the short version. The privacy policy and terms of service are the full ones.
• Questions or a security report: security@swiftcns.ai.

Steps

1. Check who can see your work

   Everything lives in a workspace. People reach it in one of three ways:

   • Workspace members, added under Settings → Team access, can open and edit every project in the workspace. Only the owner manages members and billing.
   • Shares give one signed-in account Viewer or Editor access to a conversation, a project or the whole workspace. You share by email; there are no public links.
   • Viewers can read everything they were given, including trackers and the record, and change nothing.

   See Team and roles.

2. Check what your AI tool can reach

   Your AI tool signs in as you and can only reach what you can reach. It holds only the permissions you approved when you connected it (Permissions), and its access tokens last five minutes at most before they refresh. An AI tool can't add people, change shares or manage its own access.

   To disconnect it, go to Settings → MCP client access, find it under Authorized applications and remove it.

3. Check what connected tools can reach

   Each plugin connection (Google Drive, GitLab, Jira and Confluence) belongs to one person in one workspace. SwiftCNS only searches and reads; it never writes back. It reads when you browse or import, or when you ask it in chat to look for evidence there. Google Drive asks for read access to your Drive files.

   What you import becomes a project document that your project's members can read. Disconnecting stops new imports; documents already imported stay in their projects until you delete them. See Documents and plugins.

4. Export or delete your work

   Export any time: Export PDF gives the experiment brief, Export CSV gives the tracker rows, and documents download as uploaded. For a full export of a workspace, or to have it deleted, email security@swiftcns.ai from the owner's address.

What you get

• You own everything you create.
• Access follows people: a person's AI tool and connected tools never reach more than that person can.
• A clear way out: export what you need, disconnect what you connected, and ask for deletion.

Done when

• You know who in your workspace can edit, and who only reads.
• You've removed any AI tool you no longer use under Authorized applications.

Common mistakes

• Adding a stakeholder as a workspace member to let them read. Members can edit every project. Share as Viewer instead.
• Connecting a shared or admin account to a plugin. Connect your own account, so imports reflect what you're allowed to see.

For agents: MCP tools and gotchas

• No MCP tool manages members, shares, plugin connections or agent access. Send the user to Settings.
• Every call is checked against the signed-in user's access to the workspace, project and conversation. A 403 means the user lacks access, not that the tool is broken.

Next

Troubleshooting and FAQ.