Security
Tuskway holds your team's plans, designs and tickets, and lets AI agents read and write them. This page says who can do what, what we store, and what we never see. The full detail is in the privacy policy.
Agents act as you
Each person connects their AI tool by signing in with their own Tuskway account. The agent then has the same access that person has in the workspace, and nothing more. Guests use Tuskway in the browser only and cannot connect an AI tool.
Background jobs, such as cloud agents and CI, connect with a workspace token that an owner creates. A token is limited to one workspace and is either read-only or read and write.
People approve what changes
Every workspace member can read the workspace's epics. Editing an epic is limited to its lead, the people the lead added, and workspace owners. Everyone else, and their agents, can comment and suggest changes. A suggestion changes nothing until an editor accepts it.
When an epic ships you can archive it. An archived epic stays readable and rejects every change.
Every version is kept
Tuskway keeps earlier versions of each note and records whether a person or a connected tool made each change. You can see who changed what and bring back an earlier version.
Tokens you control
- A workspace token is stored only as a hash. We keep the start of the token, its name, whether it can read or also write, when it was last used and when it expires, so you can recognise it and turn it off.
- Tokens can have an expiry date. Revoking one stops the next request.
- When an AI tool signs in with your account, we store a hash of the token that keeps it connected, not a readable copy.
What we store, and what we never see
We store what your team and its agents write in Tuskway: epics, notes, design documents, tickets, line comments, suggested changes and earlier versions of notes.
We do not read your source code. Your agents read your code where they already run. Tuskway does not receive your chats with an AI assistant either. The assistant you connect receives the notes and tickets it reads through Tuskway, and that use is covered by the assistant provider's own terms.
Search runs on our server. The search index of your notes stays there.
Trackers are optional
A workspace owner can connect GitHub, GitLab, Linear or Jira to publish tickets as issues and keep them in step. Connecting one is optional.
- For GitHub we store the installation, not your user token. When we need to create or update an issue we ask GitHub for a short-lived token.
- For GitLab, Linear and Jira the access tokens are encrypted before they are stored.
- Disconnecting a tracker stops Tuskway from reading or updating its issues. Issues already published stay in your tracker.
Accounts and sign-in
You can sign in with a password, or with GitHub or Google. Passwords are stored as a hash; we do not keep the password itself.
Where it runs
The application and its database run on a virtual server from OVH, behind Cloudflare, and are served over HTTPS. When backups are on, a full copy of the database is uploaded to Cloudflare R2 once a day. The services that handle data for the hosted product are listed in the privacy policy.
Your data stays yours
A workspace owner can download every note and ticket at any time, on every plan, including a read-only workspace. If you stop paying, the workspace turns read-only and nothing is deleted. You can delete a workspace, or your account, yourself.
Report a security issue
If you think you have found a security problem, write to [email protected]. Please include the steps to reproduce it and do not share it publicly until we have answered. We read every report.