Risks of installing a non-official addon
Last updated: 25 August 2026
1. Who runs it
A community addon is a service the publisher hosts. Its code never runs inside Prototype and we never see it. What you are approving is an external system reading your organisation over the API, in the same way a Slack app reads a Slack workspace.
The publisher is named on the listing. We hold a contact address for them and require them to accept the publisher agreement, which covers how they must handle your data. That is a contractual commitment, not a technical guarantee.
2. What it can read
Exactly the scopes shown on the authorization screen, for your organisation only, and read-only. An addon cannot publish a specification, approve a change, or act as one of your members.
Private projects are out of reach: a token is scoped to the organisation, not to a person, so it only sees projects visible to the whole organisation.
Once data reaches the publisher it is held under their terms and their security, not ours. Assume anything within the approved scopes may be stored on their systems.
3. What we do not do
- We do not audit, review, or test community addons. Listing one is not an endorsement.
- The Verified badge means we confirmed who the publisher is. It says nothing about what their code does.
- We give no warranty about a community addon, and we are not liable for what one does with data you approved it to read.
- We cannot delete data a publisher already holds. Only they can.
4. Revoking access
An admin can revoke a grant at any time from Admin, Integrations. Revoking is immediate: every token the grant issued stops working, and further calls are refused.
Revoking stops future access. It does not reach back and delete anything the publisher already copied. If you need that, ask them directly, using the support link on their listing.
5. Before you approve
- Check the scopes. An addon asking for more than its description needs is the clearest warning sign there is.
- Check the address in the Redirects to row. It should belong to the publisher you expect.
- Check who the publisher is, and whether anyone on your team knows them.
- If something looks wrong, cancel. An addon can always ask again.