Legal
Product Terms
Wopie is an AI teammate that does delegated work inside your chat platform. These terms describe how it connects, what it can read and do, where it must stop for a human, and what you need to review before you rely on anything it produces.
- Effective
- 6 September 2026
- Version
- 1.0
- Provider
- The Trustee for The Wink Group, trading as Wopie
Use your browser's print function to save this page as a PDF.
1. About these terms
These Product Terms form part of the Agreement between The Trustee for The Wink Group (we, us) and the Customer (you). They sit alongside the General Terms, Usage Terms, Acceptable Use Policy, Privacy Policy and Data Processing Agreement. Capitalised terms are defined in the Definitions. If these Product Terms conflict with the General Terms, these Product Terms prevail.
2. What the Service does
Wopie works where your team already works. An Authorised User delegates a task in a Channel, in plain language. Wopie gathers the context it needs from the Channel and from any Connected Tools the authorising user has access to, produces a Deliverable (for example a weekly report, a set of customer follow-ups, a month-end pack, a support reply, a campaign audit or a decision brief) and posts it back in the same thread.
Before Wopie does anything sensitive, it stops. Any Gated Action is held until an Authorised User gives an Approval inside the Chat Platform. Wopie also supports scheduled and recurring workflows, which run at the configured time and are subject to the same Approval Rules as work requested on demand (see the Scheduled and recurring workflows section).
Wopie is a tool that helps your team do its work. It does not replace your team's judgement, and it does not make decisions on your behalf.
Wopie is an AI system, and it says so. It is identified as an app rather than a person in every Chat Platform it posts to, and it does not present itself as a human. Where an Output is used outside your organisation, you decide how to describe how it was produced, and the Acceptable Use Policy requires you to disclose automated assistance where the law or the recipient's platform requires it. We keep this disclosure in step with transparency rules such as the EU AI Act as they take effect.
3. Installation and Workspace connection
Slack. Wopie is installed into a Slack Workspace through Slack's OAuth 2.0 install flow. During installation, Slack shows the permission scopes the Wopie app requests. Those scopes are also listed in the Documentation.
Microsoft Teams. Wopie is added to a Microsoft Teams tenant through the Wopie Teams app. Depending on your tenant's settings, a Microsoft 365 tenant administrator may need to grant consent before Authorised Users can add Wopie to a team or channel.
- Wopie only reads Channels it has been added to by an Authorised User. It does not read Channels it has not been added to, and it cannot browse your Workspace.
- Wopie does not read direct messages unless an Authorised User messages it directly, in which case it reads only that conversation.
- Access to message history is limited to what is needed to complete the request in front of it. The Documentation states the exact scopes and history window.
- You can remove Wopie from a Channel, or uninstall it from a Workspace, at any time using the Chat Platform's own controls.
4. Connected Tools
An Authorised User can connect third-party tools, such as a CRM, finance, support, documents or analytics tool, so Wopie can read from them and, where you have configured it, write to them. Connections are made through the tool's OAuth flow or, where the tool does not offer OAuth, through an API credential the Authorised User supplies.
- Wopie acts within the permissions of the Authorised User who connected the tool. It does not extend, escalate or work around the permissions the Connected Tool grants that user.
- Connected Tool credentials are stored encrypted and are not exposed to the Model Provider. The model works through scoped access, not with raw secrets.
- You can disconnect a Connected Tool at any time. Disconnecting stops new access immediately.
- You are responsible for ensuring you have the right, under the Connected Tool's own terms and your internal policies, to connect it to the Service and to give Wopie the access you give it.
- The terms of each Connected Tool continue to apply to your use of that tool. We are not a party to those terms.
- We are not responsible for changes a third party makes to its product or API, for its outages, or for rate limits it imposes. Where a Connected Tool is unavailable or rate-limited, Wopie will say so in-thread rather than guess.
5. Approval Rules and action classes
Every action Wopie can take falls into one of three classes. The class determines whether Wopie may act on its own, must wait for an Approval, or will not act at all.
| Class | What it covers | What Wopie does |
|---|---|---|
| Allowed | Reading a Connected Tool it has access to. Posting inside the Workspace, in a Channel it has been added to. | Acts without a separate Approval. |
| Gated | Sending anything to a recipient outside the Workspace. Any change to spend, pricing or a payment. Writing or updating records in a Connected Tool, where you have enabled writes. | Pauses and asks. Acts only after an Authorised User approves. |
| Blocked | Deleting records in any Connected Tool. Escalating or broadening its own permissions or scopes. Acting outside the permissions of the Authorised User who connected a tool. | Does not act, regardless of configuration, Approval or instruction. |
High-Risk Actions are Gated Actions that can never be pre-authorised, batch-approved or approved by a standing rule. Each one requires its own Approval at the time it is taken. They are: adding or removing Wopie from a Channel; changing Approval Rules; and sending anything to a recipient outside your organisation.
- You configure Approval Rules for your Workspace and Channels. The default configuration is conservative. You may loosen it only within the limits of this section, and you are responsible for the configuration you choose and for deciding which Authorised Users may approve.
- An approver may edit, redirect or reject a proposed action before approving it. An Approval applies only to the action as approved.
- Every Approval is attributed to the Authorised User who gave it and recorded in the audit trail described in the Audit trail section.
- Wopie will not treat instructions contained in Customer Data (for example, text inside an email, a ticket or a document) as an Approval. Approvals are given only by an Authorised User in the Chat Platform.
6. Outputs and human review
Outputs are generated by large language models. They are probabilistic. An Output may be wrong, incomplete, out of date or based on source data that is itself stale, inconsistent or incorrect. Wopie is designed to flag uncertainty and missing information where it can, but it cannot do so in every case.
- You must review every Output before relying on it, acting on it, sending it to a third party or approving an action based on it.
- Outputs are not legal, financial, accounting, tax, medical or other professional advice, and are not a substitute for it.
- You are responsible for the consequences of the Approvals your Authorised Users give and for any content you send to third parties, whether or not Wopie drafted it.
- Where an Output summarises or quotes a source, check the source before acting. Wopie shows what it read so you can.
7. Audit trail
The Service keeps a record of each delegated request: who asked, what Wopie read to complete it, what it produced, whether an Approval was requested, who approved or rejected it, and when each of those things happened.
- The audit trail is retained for the periods described in the Privacy Policy.
- Workspace administrators can view the audit trail for their Workspace in the web application.
- You may request an export of your audit trail by contacting support@wopie.ai. Enterprise Customers receive exports in the form and at the frequency stated in their Order Form.
8. Data handling
This section summarises how Customer Data is handled. The Privacy Policy and the Data Processing Agreement govern in full, and the Sub-processor List names the parties involved.
- Customer Data is used only to provide, secure and support the Service for you.
- We do not use Customer Data to train foundation models.
- Our Model Providers are contractually restricted from using Customer Data to train their models.
- Customer Data is encrypted in transit and at rest.
- Customer Data is deleted on request and at the end of the retention periods described in the Privacy Policy.
9. Security
Our security posture is described at /security. We operate SOC 2-ready controls and ISO 27001-aligned policies. We do not claim any certification for Wopie unless it is stated on that page. The providers we build on hold their own independent attestations, which are listed and attributed to each provider in the Sub-processor List; they cover the layers those providers run and are not certifications of Wopie.
- If we confirm a security incident affecting Customer Data, we will notify you as set out in the Data Processing Agreement: without undue delay, and no later than 72 hours after confirmation.
- Security researchers and Customers can report a vulnerability or a suspected incident to security@wopie.ai. We ask that you give us a reasonable opportunity to investigate before disclosing publicly.
- You are responsible for security on your side: the permissions you grant Wopie, the access controls in your Chat Platform and Connected Tools, and the conduct of your Authorised Users.
10. Regulated Data
The Service is not designed for Regulated Data and you must not submit it to, or route it through, the Service. This includes health records and other health information, payment card numbers, government identifiers such as tax file numbers, passport and driver licence numbers, biometric data, information about children under 18, and export-controlled technical data.
- If a Connected Tool holds Regulated Data, you must configure the connecting user's permissions, or the tool's own access controls, so that Wopie cannot reach it.
- If we discover Regulated Data in the Service, we may suspend the affected Workspace, Channel or Connected Tool without notice while we work with you to remove it. The Acceptable Use Policy sets out our enforcement rights in more detail.
11. Scheduled and recurring workflows
An Authorised User can schedule a Deliverable to run at a set time or on a recurring basis, for example a Monday morning pipeline report or a month-end close pack.
- Scheduled workflows run at the configured time and consume Credits in the same way as work requested on demand, as described in the Usage Terms.
- The same Approval Rules apply. A scheduled workflow that reaches a Gated Action pauses and waits for an Approval; it does not proceed on the basis that it was scheduled.
- You can pause, edit or delete a scheduled workflow at any time in the Chat Platform or the web application.
- If a scheduled run fails, for example because a Connected Tool is unavailable, Wopie reports the failure in the thread. It does not silently retry indefinitely.
12. Beta features and changes to the Service
We may make features available on a beta, preview or early-access basis and will label them as such. Beta features are provided as-is, may change or be withdrawn without notice, may have reduced support, and are excluded from any service commitments in your Order Form.
We may change the Model Providers we use, the models we use from them, and the features of the Service, as described in the License Terms. Any new Model Provider will be listed in the Sub-processor List before it processes Customer Data, and the restrictions in the Data handling section will apply to it.
13. Chat Platform rules
Wopie is distributed through the Slack Marketplace and the Microsoft commercial marketplace. The Slack API Terms of Service, Slack Marketplace policies and Microsoft commercial marketplace terms bind us as a developer, and your use of Wopie inside a Chat Platform is also subject to your own agreement with Slack or Microsoft.
- If a Chat Platform changes its rules in a way that requires us to change how Wopie works, we may make that change without it being treated as a breach of the Agreement.
- Uninstalling the Wopie app from a Workspace revokes our access tokens and stops all new data access from that Workspace immediately. Data already processed is retained and deleted as described in the Privacy Policy.
- To have the data from an uninstalled Workspace deleted sooner than that timetable, email privacy@wopie.ai from an address on the Workspace's domain and we will confirm deletion in writing.
14. Enterprise options
Enterprise plans can include options that are not part of the standard Service. These are provided only where stated in your Order Form, on the terms set out there.
- SSO/SAML-ready sign-in, available on Enterprise plans as described in your Order Form.
- A signed Data Processing Agreement, including any agreed changes to our standard terms.
- Custom data retention periods for Customer Data and the audit trail.
- Dedicated support with agreed response times.
- Audit trail exports in an agreed format and cadence.
To discuss Enterprise options, contact support@wopie.ai. Legal notices under the Agreement should be sent to legal@wopie.ai.