Integrations Policy

Last updated: 20 October 2026

Storyvote runs inside chat and video apps and connects to issue trackers. This policy sets the rules every integration follows, today's and any we add later, and lists each one: who turns it on, what it reads and writes, what we keep and for how long.

1. What this policy covers

• Chat and video apps (Slack, Discord, Telegram, Google Meet): Storyvote runs inside them, and they tell it who you are, so you don't type a name.
• Issue trackers (Jira Cloud, Trello, Linear, Asana): a room connects to one to import stories and to write their estimates back.

Importing and downloading stories as CSV happens in your browser and involves no third party, so it isn't an integration in this sense. This policy is part of our Terms of Service; the personal data involved is described in our Privacy Policy.

2. Rules every integration follows

• Optional. Nothing connects by itself. Only a room's host or a facilitator can connect it to a tracker, and they see which account it is connected as. A chat app is added by someone in your workspace, as its admin settings allow.
• Still no Storyvote account. A chat app tells Storyvote who you are. A tracker connection belongs to the room, not to a person, and ends with it.
• Least access. We ask for the narrowest permissions the provider offers for what the integration does. Where a provider offers only broader ones, we use them only for what section 7 lists.
• Reads only what you pick. To show you what to import, Storyvote reads the names of boards, projects or teams and the titles and keys of their items, and doesn't store them. It stores only the items you import, as stories: their title, key, ID and link. It reads no descriptions, attachments or assignees, and reads an item's comments only to find the estimate comment it wrote there before.
• Writes only estimates. Storyvote writes the final estimate, as one comment on each imported item ending with a link to storyvote.app (updated when the estimate changes) and, where the tracker has one, in its estimate field. It never changes an item's status, assignee or other fields, and never creates or deletes items.
• Tokens stay on our server, encrypted. Access tokens are encrypted with AES-256-GCM, under a key for each integration that isn't kept in the database. They never reach anyone's browser and are never written to our logs.
• Short-lived. A tracker connection is deleted when the room is disconnected or ends, and otherwise 30 days after it was last used, and revoked at the provider where the provider lets apps do so. Imported stories are deleted with the room.
• Used for nothing else. Data from an integration is used only to run the room. It is never used for advertising, never sold, never passed to anyone but the provider it came from, and never used to train AI models.
• Listed before it goes live. We add an integration only once it follows these rules, and list it in section 7, and so in our Privacy Policy, before anyone can use it. If an integration ever needs something these rules don't cover, we change this policy first.

3. Private and confidential project data

You may import private issues and other confidential project data from Jira, Trello, Linear, Asana or any tool you connect, and you may type them into a room, as long as you are allowed to. That means:

• your organisation's policies allow you to use the data with Storyvote, and its admin settings allow the integration (if they don't, ask your admin rather than working around it);
• everyone you invite may see it: anyone with the room's link (and password, if one is set) sees every story, including imported titles and links, and doesn't need an account in the tracker to do so. Links lead back to the tracker, where its own permissions apply;
• it isn't sensitive personal data (such as health data), passwords, keys or other secrets, or data that the law or a contract requires to be kept only in certified systems.

We treat room content as confidential: we use it only to run the room, and we look at it only when you ask us to (for example, to investigate a problem in your room), when we handle a report of illegal content, or when the law requires it. For sensitive sessions, set a room password and share the link only with the people who may see the stories.

4. What stays in your tools

Comments and estimates Storyvote writes to Jira, Trello, Linear or Asana, and the room cards and replies it posts in Slack, are part of those tools. They stay after the room ends or is disconnected, under the provider's terms and your organisation's settings, and you can edit or delete them there. "End and delete room" deletes everything Storyvote holds, not what it wrote into your tools.

5. Your responsibilities

• Connect only accounts and workspaces you may use, and follow the provider's terms and your organisation's policies.
• Storyvote can do in a tracker only what the connected account is allowed to do, so connect an account whose access suits the room.
• You're responsible for what you import, and for whom you share the room with.
• Storyvote and its integrations are free. A plan, seat or licence that a provider charges for is between you and that provider.

6. The providers

Each provider runs its own service, under its own terms and privacy policy, as an independent controller of the data it processes. We don't control their services and aren't responsible for them. An integration may stop working when a provider changes its service, its interface or its terms. We may change or remove an integration, for example to keep it secure or because a provider no longer allows it; where we can, we'll say so on the site in advance.

7. The integrations

Each integration, with the same details for every one. Ending a room removes everything listed as kept "with the room" at once; the rest goes as stated.

8. Problems and reports

If you think an integration read or wrote more than this policy says, or you want a room's connection removed at once, email hello@storyvote.app with "Integrations" in the subject and the room code, and we'll remove the connection as soon as we can. For security issues, see Security.

9. Changes to this policy

We'll publish any new version here and update the date at the top. A new integration is listed in section 7 before it becomes available, and we'll point out significant changes on the site.